Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1033617: libopenexr-dev: Cannot just upgrade libopenexr-dev to 3.1.5-4 because of file conflict with older version of libilmbase-dev
67 views
Skip to first unread message
Felix Stupp
Mar 28, 2023, 2:40:04 PM3/28/23
to
for documentation purposes, I now fixed the issue for my systems by force-removing the old package first with dpkg and then installing its replacements with markauto:
sudo dpkg --remove --force-depends libilmbase-dev
sudo aptitude install lib{imath,openexr}-dev+M # or apt install --mark-auto lib{imath,openexr}-dev
sudo dpkg --remove --force-depends libilmbase-dev
sudo aptitude install lib{imath,openexr}-dev+M # or apt install --mark-auto lib{imath,openexr}-dev
Felix Stupp
Mar 28, 2023, 2:40:04 PM3/28/23
to
Package: libopenexr-dev
Version: 3.1.5-4
Severity: serious
Justification: Policy 7.4
X-Debbugs-Cc: me+debi...@banananet.work
Dear Maintainer,
I cannot upgrade this package from version 2.5.7-1 to version 3.1.5-4
due to a file conflict with the package libilmbase-dev on version
2.5.4-1. I tried with apt & aptitude as well. Both want to replace
libilmbase-dev with libopenexr-dev in a single execution of them, but
fail to do that in a way that dpkg allows that (tries first to install
the new package and then uninstall the old one).
Currently I see no other solution than removing the old one first aside
with all packages depending it on it, and then installing the new one
with all packages which were removed before.
They already have a "Breaks" & a "Replace" relationship, which seems to
be right, but I assume adding a "Conflicts" relation will fix that,
for "Breaks" "dpkg will refuse to allow the package […] to be unpacked
unless the broken package is deconfigured first", while for "Conflicts"
it says that "dpkg will refuse to allow them to be unpacked on the
system at the same time".
I marked this bug as serious as I think, even if another solution may be
found, that still a Conflicts field on this package referring to the
older one may be required unless that is not possible. However, I'm not
100% sure, so feel free to change the severity. Maybe I just ran into
this problem due to other circumstances a stable user will not run into.
Also I assume that if this configuration will be released into bookworm,
others will having problems as well.
Best Regards,
Felix Stupp
-- System Information:
Debian Release: 12.0
APT prefers testing
APT policy: (550, 'testing'), (500, 'testing-security'), (400, 'stable-updates'), (400, 'stable-security'), (400, 'stable'), (110, 'unstable'), (102, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libopenexr-dev depends on:
pn libilmbase-dev <none>
ii libopenexr25 2.5.7-1
libopenexr-dev recommends no packages.
libopenexr-dev suggests no packages.
-- no debconf information
Version: 3.1.5-4
Severity: serious
Justification: Policy 7.4
X-Debbugs-Cc: me+debi...@banananet.work
Dear Maintainer,
I cannot upgrade this package from version 2.5.7-1 to version 3.1.5-4
due to a file conflict with the package libilmbase-dev on version
2.5.4-1. I tried with apt & aptitude as well. Both want to replace
libilmbase-dev with libopenexr-dev in a single execution of them, but
fail to do that in a way that dpkg allows that (tries first to install
the new package and then uninstall the old one).
Currently I see no other solution than removing the old one first aside
with all packages depending it on it, and then installing the new one
with all packages which were removed before.
They already have a "Breaks" & a "Replace" relationship, which seems to
be right, but I assume adding a "Conflicts" relation will fix that,
for "Breaks" "dpkg will refuse to allow the package […] to be unpacked
unless the broken package is deconfigured first", while for "Conflicts"
it says that "dpkg will refuse to allow them to be unpacked on the
system at the same time".
I marked this bug as serious as I think, even if another solution may be
found, that still a Conflicts field on this package referring to the
older one may be required unless that is not possible. However, I'm not
100% sure, so feel free to change the severity. Maybe I just ran into
this problem due to other circumstances a stable user will not run into.
Also I assume that if this configuration will be released into bookworm,
others will having problems as well.
Best Regards,
Felix Stupp
-- System Information:
Debian Release: 12.0
APT prefers testing
APT policy: (550, 'testing'), (500, 'testing-security'), (400, 'stable-updates'), (400, 'stable-security'), (400, 'stable'), (110, 'unstable'), (102, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libopenexr-dev depends on:
pn libilmbase-dev <none>
ii libopenexr25 2.5.7-1
libopenexr-dev recommends no packages.
libopenexr-dev suggests no packages.
-- no debconf information
Andreas Metzler
Mar 29, 2023, 1:10:06 PM3/29/23
to
On 2023-03-28 Felix Stupp <me+debi...@banananet.work> wrote:
> Package: libopenexr-dev
> Version: 3.1.5-4
> Severity: serious
> Justification: Policy 7.4
> X-Debbugs-Cc: me+debi...@banananet.work
> Dear Maintainer,
> I cannot upgrade this package from version 2.5.7-1 to version 3.1.5-4
> due to a file conflict with the package libilmbase-dev on version
> 2.5.4-1. I tried with apt & aptitude as well. Both want to replace
> libilmbase-dev with libopenexr-dev in a single execution of them, but
> fail to do that in a way that dpkg allows that (tries first to install
> the new package and then uninstall the old one).
> Currently I see no other solution than removing the old one first aside
> with all packages depending it on it, and then installing the new one
> with all packages which were removed before.
[...]
> Package: libopenexr-dev
> Version: 3.1.5-4
> Severity: serious
> Justification: Policy 7.4
> X-Debbugs-Cc: me+debi...@banananet.work
> Dear Maintainer,
> I cannot upgrade this package from version 2.5.7-1 to version 3.1.5-4
> due to a file conflict with the package libilmbase-dev on version
> 2.5.4-1. I tried with apt & aptitude as well. Both want to replace
> libilmbase-dev with libopenexr-dev in a single execution of them, but
> fail to do that in a way that dpkg allows that (tries first to install
> the new package and then uninstall the old one).
> Currently I see no other solution than removing the old one first aside
> with all packages depending it on it, and then installing the new one
> with all packages which were removed before.
Hello,
I cannot reporoduce this from your description because the original
setup you started with
libopenexr-dev + libopenexr25 2.5.7-1
libilmbase-dev + libilmbase25 2.5.4-1
is not installable, libopenexr25 2.5.7-1 depends on libilmbase25 (>= 2.5.7).
cu Andreas
Felix Stupp
Mar 30, 2023, 4:40:03 PM3/30/23
to
Hello,
that's true, somehow I messed up the version number, sorry.
I had libilmbase-dev version 2.5.7-2+b1 installed when I ran into this issue according to my aptitude log.
I also tried out to reproduce the issue again in Docker & succeeded, see the attached Dockerfile.
However, after seeing how old both package versions are and that these exact versions were not available at the same time,
I do not know how I ended up with exactly these versions and using them until just a few days ago.
Maybe another package which wasn't updated for quite a while had a hardlocked dependency.
To know for sure, I would need to restore the full list of packages & versions I had installed before upgrading by reading the dpkg logs.
Best Regards,
Felix Stupp
Am Mittwoch, 29. März 2023, 19:06:29 CEST schrieben Sie:
that's true, somehow I messed up the version number, sorry.
I had libilmbase-dev version 2.5.7-2+b1 installed when I ran into this issue according to my aptitude log.
I also tried out to reproduce the issue again in Docker & succeeded, see the attached Dockerfile.
However, after seeing how old both package versions are and that these exact versions were not available at the same time,
I do not know how I ended up with exactly these versions and using them until just a few days ago.
Maybe another package which wasn't updated for quite a while had a hardlocked dependency.
To know for sure, I would need to restore the full list of packages & versions I had installed before upgrading by reading the dpkg logs.
Best Regards,
Felix Stupp
Am Mittwoch, 29. März 2023, 19:06:29 CEST schrieben Sie:
Paul Gevers
Apr 20, 2023, 6:24:35 AM4/20/23
to
Hi Andreas,
On Fri, 31 Mar 2023 15:06:14 +0200 Andreas Metzler <amet...@bebt.de> wrote:
> I think 2.5.7-2 was the last sourceful < 3 upload, so (<< 2.5.7-3)
> should work.
And to be backports and other local packages, I think that could/should
be (<< 2.5.7-3~).
Can a/this fix be uploaded soon please? We're trying to pick a bookworm
release date and a fix should be in.
Paul
On Fri, 31 Mar 2023 15:06:14 +0200 Andreas Metzler <amet...@bebt.de> wrote:
> I think 2.5.7-2 was the last sourceful < 3 upload, so (<< 2.5.7-3)
> should work.
And to be backports and other local packages, I think that could/should
be (<< 2.5.7-3~).
Can a/this fix be uploaded soon please? We're trying to pick a bookworm
release date and a fix should be in.
Paul
0 new messages