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

Bug#1059929: marked as done (release.debian.org: gobject-introspection_1.78.1-9 is said to have an unsatisfiable dependency)

Your message dated Thu, 11 Jan 2024 12:32:33 +0100
with message-id <49eda68c-9a49-41f0-9975-b95fa491f673@debian.org>
and subject line Re: Bug#1059929: release.debian.org: gobject-introspection_1.78.1-9 is said to have an unsatisfiable dependency
has caused the Debian Bug report #1059929,
regarding release.debian.org: gobject-introspection_1.78.1-9 is said to have an unsatisfiable dependency
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.)


-- 
1059929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059929
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
X-Debbugs-Cc: gobject-introspection@packages.debian.org, debian-cross@lists.debian.org

gobject-introspection in experimental has this in
https://release.debian.org/britney/pseudo-excuses-experimental.html#gobject-introspection:

gobject-introspection (1.78.1-6 to 1.78.1-9)

    Migration status for gobject-introspection (1.78.1-6 to 1.78.1-9): BLOCKED: Rejected/violates migration policy/introduces a regression
    Issues preventing migration:
        gobject-introspection/amd64 has unsatisfiable dependency
        gobject-introspection/arm64 has unsatisfiable dependency
    Additional info:
        uninstallable on arch amd64, not running autopkgtest there
        uninstallable on arch arm64, not running autopkgtest there

The gobject-introspection binary package *is* installable, and in fact
I have it installed locally. Taking the amd64 version as an example,
it depends on:

- binutils-x86-64-linux-gnu:any, a real Multi-Arch: allowed package

- gcc-x86-64-linux-gnu, a virtual package provided by gcc:amd64

- gobject-introspection-bin | qemu-user | qemu-user-static, where
  g-i-bin is a Multi-Arch: allowed package from the same source

- gobject-introspection-little-endian:any, a virtual package provided
  by g-i-bin, which is Multi-Arch: allowed
  (experimentally, apt and dpkg both seem to be happy to assume that
  this makes the gobject-introspection-little-endian virtual package
  behave as though it was also Multi-Arch: allowed)

- pkgconf, a real package

- python3:any, a real Multi-Arch: allowed package

I think all of those are correct?

Or do I need to make gobject-introspection-bin Multi-Arch: foreign,
drop the :any from gobject-introspection-little-endian:any, and
replace the gobject-introspection-bin | qemu-user | qemu-user-static
dependency by python3 | qemu-user | qemu-user-static or similar?

My goal here is that you can install gobject-introspection:amd64 on an
amd64 machine, or on any other little-endian machine that will be able to
cross-compile amd64 binaries and then run them by explicitly invoking them
via qemu-user, as discussed with Helmut Grohne at the recent Cambridge
miniDebconf. (It has to be little-endian because g-ir-inspect and similar
tools don't currently support byte-swapping fields in binary typelibs.)

Thanks,
    smcv

--- End Message ---
--- Begin Message --- 
Hi Simon,,

On 05-01-2024 21:57, Paul Gevers wrote:

Control: tags -1 pending

Hi,

On 03-01-2024 20:40, Paul Gevers wrote:

On 03-01-2024 20:22, Simon McVittie wrote:

I think all of those are correct?
I think that if apt allows you to install it, chances are that it's a britney2 bug. I'll try to debug it tomorrow.
I have a first proposal for a fix in https://salsa.debian.org/release-team/britney2/-/merge_requests/89 

This is pushed, so these two issues should be solved now.

Paul

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: