Skip to content

Hardcoded /tmp/wheel2deb causes problems #62

@tbleher

Description

@tbleher

I started using wheel2deb today, and want to first of all say that it is a great tool :)

However, I found one problem: it uses a hardcoded /tmp/wheel2deb folder. This causes two problems:

The first is that it caches information for too long (at least from the point of a new user like me). I built a whl from source, and built a Debian package from it. Then I noticed a wrong dependency in the whl, rebuilt the whl and rebuilt the Debian package. But very surprising for me, the Debian package still had the wrong dependency, even though the whl had the correct dependency. Running strace on wheel2deb I saw that it accessed /tmp/wheel2deb. After removing the folder, the problem went away.

The second problem is that this makes wheel2deb unusable in a multi-user environment, where /tmp is shared between different users. Because after one user has used wheel2deb, another cannot use wheel2deb until /tmp is manually cleaned.

I suggest using temporary directories with unique names, and removing them after wheel2deb has run, in order to avoid these problems.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions