Your message dated Wed, 20 Jan 2021 09:17:37 +0000 with message-id <[email protected]> and subject line Re: Bug#980535: gdk-pixbuf: Inconsistent naming has caused the Debian Bug report #980535, regarding gdk-pixbuf: Inconsistent naming 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 [email protected] immediately.) -- 980535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980535 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Source: gdk-pixbuf Severity: normal X-Debbugs-Cc: [email protected] Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I tried to install ardour from Debian experimental on Ubuntu. I know this is unusual but worked in the past. Now there is a new dependency on libgdk-pixbuf-2.0-0 which does not exist on Ubuntu. It is called libgdk-pixbuf2.0-0 there (note the missing hypen). I managed to install ardour with --force-depends but now every time I am upgrading apt complains about missing dependencies. I noticed that the naming of binary packages in Debian is inconsistent, some include hypens (libgdk-pixbuf-2.0-dev) and some don't (libgdk-pixbuf2.0-bin). I suggest naming them consistently with or without an hyphen or, since there is no version 1 in the repository, to just name it libgdk-pixbuf-dev and libgdk-pixbuf-bin). This way Ubuntu wouldn't need to rename packages and I could cross-install ardour as before. * What exactly did you do (or not do) that was effective (or ineffective)? Install ardour from Debian experimental on Ubuntu. * What was the outcome of this action? Broken dependencies. * What outcome did you expect instead? Working upgrade with ardour installed. *** End of the template - remove these template lines *** -- System Information: Debian Release: bullseye/sid APT prefers groovy-updates APT policy: (500, 'groovy-updates'), (500, 'groovy-security'), (500, 'groovy'), (100, 'groovy-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.11.0-051100rc2-lowlatency (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---On Wed, 20 Jan 2021 at 09:50:28 +0100, Gon Solo wrote: > I tried to install ardour from Debian experimental on Ubuntu. I know > this is unusual but worked in the past. Sorry, this is not a supported or supportable thing to do. Debian experimental is only suitable for use as an overlay over Debian unstable. Debian does not provide packages intended for Ubuntu. If they sometimes work on Ubuntu by coincidence, nobody can stop you from building your own Debian/Ubuntu hybrid, but if you do that, it's your responsibility to make it work: when it breaks, neither Debian nor Ubuntu developers will support you. This is often referred to as a "Frankendebian" system and is discouraged. A better way to run this version of ardour on Ubuntu would be to take the source package from Debian experimental, and rebuild it on Ubuntu groovy, so that you get a package with dependencies that are appropriate for Ubuntu groovy. > Now there is a new dependency > on libgdk-pixbuf-2.0-0 which does not exist on Ubuntu. It is called > libgdk-pixbuf2.0-0 there (note the missing hypen). These two packages are not the same. The old libgdk-pixbuf2.0-0 contained two libraries, libgdk-pixbuf-2.0.so.0 and libgdk-pixbuf-xlib-2.0.so.0. The new libgdk-pixbuf-2.0-0 only contains libgdk-pixbuf-2.0.so.0, because upstream stopped providing the deprecated gdk-pixbuf-xlib library. It would be wrong for us to continue to use the libgdk-pixbuf2.0-0 name, because if we did, applications that require libgdk-pixbuf-xlib-2.0.so.0 would stop working. So we had to rename the package. The new name libgdk-pixbuf-2.0-0 is mechanically derived from the SONAME libgdk-pixbuf-2.0.so.0, following the rules in Debian Policy. > I managed to > install ardour with --force-depends but now every time I am > upgrading apt complains about missing dependencies. This should have been a hint that you were doing something that was not supportable... You need the transitional libgdk-pixbuf2.0-0 package, which exists in Debian and probably in Ubuntu hirsute, but not in Ubuntu groovy. It depends on libgdk-pixbuf-2.0-0 and libgdk-pixbuf-xlib-2.0-0. Or, rebuild ardour on Ubuntu. > the naming of binary packages in Debian is inconsistent, some include > hypens (libgdk-pixbuf-2.0-dev) and some don't (libgdk-pixbuf2.0-bin). Every time we rename a package it causes trouble for people like you, and also causes delays because it triggers legal review, so we don't rename packages when we don't strictly need to. libgdk-pixbuf-2.0-dev does not contain everything that the old libgdk-pixbuf2.0-dev did, so it had to be renamed. The content of libgdk-pixbuf2.0-bin did not change so no rename was required. smcv
--- End Message ---
