releng/tickets

Fork 2

No component `nodejs26` in Fedora bugzilla #13354

New issue

Closed

opened 2026-05-15 14:11:38 +00:00 by jstanek · 7 comments

jstanek commented

2026-05-15 14:11:38 +00:00

Describe the issue

I'm trying to open a bug against the nodejs26 package that is currently being imported (so we have the dist-git repo, but no build yet). I'm unable to select nodejs26 as a component in bugzilla UI, and I'm getting the following error from the CLI:

Server error: <Fault 51: "There is no component named 'nodejs26' in the 'Fedora' product.">

To explain why I would submit a bug against a package that is not yet been built: We are encountering some rough edges in the import (e.g. LTO enablement) and we will likely be work-arounding them to get something built. But I would still like to have those recorded as bugs/issues to be addressed later.

When do you need this? (YYYY/MM/DD)

N/A – No concrete date, but I would expect to be able to open bugs once the dist-git repo is ready. At the latest once we release the first build to rawhide.

When is this no longer needed or useful? (YYYY/MM/DD)

N/A

If we cannot complete this, what is the impact? [Dependencies/Blocker]

We cannot file bugs against nodejs26 component, which would be significant work disruption.

Checklist

I have checked existing issues for duplicates
I have filled out all the fields above
I have provided relevant links or references (if applicable)

## Describe the issue I'm trying to open a bug against the `nodejs26` package that is currently being imported (so we have the [dist-git repo](https://src.fedoraproject.org/rpms/nodejs26), but no build yet). I'm unable to select `nodejs26` as a component in bugzilla UI, and I'm getting the following error from the CLI: ``` Server error: <Fault 51: "There is no component named 'nodejs26' in the 'Fedora' product."> ``` To explain why I would submit a bug against a package that is not yet been built: We are encountering some rough edges in the import (e.g. LTO enablement) and we will likely be work-arounding them to get something built. But I would still like to have those recorded as bugs/issues to be addressed later. ## When do you need this? (YYYY/MM/DD) N/A – No concrete date, but I would expect to be able to open bugs once the dist-git repo is ready. At the latest once we release the first build to rawhide. ## When is this no longer needed or useful? (YYYY/MM/DD) N/A ## If we cannot complete this, what is the impact? [Dependencies/Blocker] We cannot file bugs against `nodejs26` component, which would be significant work disruption. --- ## Checklist - [x] I have checked existing issues for duplicates - [x] I have filled out all the fields above - [x] I have provided relevant links or references (if applicable)

jnsamyak self-assigned this

2026-05-18 13:57:49 +00:00

jnsamyak added the

labels

2026-05-18 13:58:14 +00:00

jnsamyak added this to the Sprint ( 2026-05-18 to 2026-05-31 ) project

2026-05-18 13:58:18 +00:00

kevin commented

2026-05-18 16:13:27 +00:00

Owner

Something clearly went wrong with automation here... but I am not sure what. ;(

I looked in logs and could not find any errors here. It's like it just didn't see the new package creation. ;(

Something clearly went wrong with automation here... but I am not sure what. ;( I looked in logs and could not find any errors here. It's like it just didn't see the new package creation. ;(

tjuhasz commented

2026-05-19 11:49:51 +00:00

There is also the issue that the repository was created without any branch.

There is also the issue that the repository was created without any [branch](https://src.fedoraproject.org/rpms/nodejs26/branches).

kevin commented

2026-05-20 14:11:05 +00:00

Owner

Yes, thats definitely a problem.

So, how about we just delete the existing broken repo and you can request it again (with a nice valid request from fedpkg request-repo)?

Failing that we will have to figure out exactly whats broken and manually fix it, which I think will be more trouble and error prone.

If that seems ok to you, let me know and we can delete it and you can re-request?

Yes, thats definitely a problem. So, how about we just delete the existing broken repo and you can request it again (with a nice valid request from fedpkg request-repo)? Failing that we will have to figure out exactly whats broken and manually fix it, which I think will be more trouble and error prone. If that seems ok to you, let me know and we can delete it and you can re-request?

jstanek commented

2026-05-21 10:38:06 +00:00

Author

Ack, please delete the repo, and I'll try the re-request; see what happens.

kevin commented

2026-05-21 17:05:12 +00:00

Owner

Done.

jstanek commented

2026-05-25 09:38:52 +00:00

Author

New request: https://pagure.io/releng/fedora-scm-requests/issue/83746. 🤞

jstanek commented

2026-05-26 08:43:51 +00:00

Author

After the recreation, the repo has both rawhide and main branch, and I can see the nodejs26 component when filing bugzilla bugs. 🎉

A minor detail is that the description ("JavaScript runtime") did not seem to propagate into the component description. When selecting nodejs26 from the component dropdown in bugzilla, the description (the second line) reads just "NA". That is however on the level of cosmetic details, so I consider this request fulfilled and this ticket can be closed.

Thanks @kevin for the help!

After the recreation, the repo has both `rawhide` and `main` branch, and I can see the `nodejs26` component when filing bugzilla bugs. 🎉 A minor detail is that the description ("JavaScript runtime") did not seem to propagate into the component description. When selecting `nodejs26` from the component dropdown in bugzilla, the description (the second line) reads just "NA". That is however on the level of cosmetic details, so I consider this request fulfilled and this ticket can be closed. Thanks @kevin for the help!