Skip to content

BUG: creating package brow6el-main.tar.gz generates unexpected PURL values #449

Open

Description

@DennisClark

Describe the bug
Creating a package in DejaCode from https://codeberg.org/janantos/brow6el/archive/main.tar.gz results in unexpected PURL values.

To Reproduce
Steps to reproduce the behavior:

  1. Go to Packages user list view
  2. Click on Add Package
  3. enter https://codeberg.org/janantos/brow6el/archive/main.tar.gz and click Add
  4. Note that the generated PURL is pkg:generic/main.tar.gz?download_url=https://codeberg.org/janantos/brow6el/archive/main.tar.gz even though it correctly generates the Filename field as brow6el-main.tar.gz and it correctly records the Download URL.

Expected behavior
The Name value in the PURL should be brow6el-main-tar-gz rather than main.tar.gz

Context (OS, Browser, Device, etc.):
DejaCode v5.5.0

Activity

  1. added
    bugSomething isn't working
    enhancementNew feature or request
    design neededDesign details needed to complete the issue
    on Jan 2, 2026
  2. tdruez commented on Jan 5, 2026

    @tdruez
    Contributor

    @DennisClark The "Download URL" to "PURL" is handled by the packageurl-python library.

    The packageurl-python is only aware of the provided Download URL string: https://codeberg.org/janantos/brow6el/archive/main.tar.gz

    To figure out the brow6el-main.tar.gz filename value, an HTTP request is required.

    Note that DejaCode does this HTTP request to get and set the filename value of the Package model but it does not mess with the PURL values as it relies on the packageurl-python library output.

    The Name value in the PURL should be brow6el-main-tar-gz rather than main.tar.gz

    I don't remember seeing this syntax for a Package name before. The package name here seems to be brow6el.


    A better PURL for this should be something like pkg:codeberg/janantos/brow6el@main but this would need to happen on the packageurl-python side first.

  3. DennisClark commented on Jan 5, 2026

    @DennisClark
    MemberAuthor

    @tdruez thanks for the explanation

  4. DennisClark commented on Jan 5, 2026

    @DennisClark
    MemberAuthor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingdesign neededDesign details needed to complete the issueenhancementNew feature or request

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions