dpkg-shlibdeps --version or --help broken on mantic

Bug #2039308 reported by Lucas Detje
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-images
Confirmed
Undecided
Unassigned
dpkg (Ubuntu)
Triaged
Undecided
Unassigned

Bug Description

After the recent update of ubuntu:rolling to point to mantic we noticed that one of our package scripts that relies on checking the version of dpkg-shlibdeps failed with the following error message:

`error: cannot read debian/control: No such file or directory`

It worked (and still works) on ubuntu:lunar.

The issue can be reproduced with the following Dockerfile:

```
ARG variant

FROM ubuntu:${variant}

RUN apt-get update && apt-get install -y --no-install-recommends dpkg-dev

RUN dpkg-shlibdeps --version
```

And then the following succeeds:
```
docker build --build-arg variant=lunar-20231004 .
```
While the following fails with the above mentioned error:
```
docker build --build-arg variant=mantic-20231011 .
```

Running the mantic version with a perl debugger shows that the following line which is added in the mantic version is the cause:
```
my $control = Dpkg::Control::Info->new();
```

Edit: This behavior was observed for linux/amd64, linux/arm/v7 and linux/arm64/v8 images if that is relevant.

Tags: docker
Lucas Detje (ltdsauce)
tags: added: docker
Lucas Detje (ltdsauce)
description: updated
Revision history for this message
Cristovao Cordeiro (cjdc) wrote :

I can reproduce and confirm the issue

Changed in cloud-images:
status: New → Confirmed
Changed in dpkg (Ubuntu):
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.