#9745 Delete the modules/ruby wip/2.7
Closed: Fixed 3 years ago by pingou. Opened 3 years ago by jaruga.

  • Describe the issue
    Yesterday I created "wip/2.7" branch on modules/ruby by my mistake.
    Though I intended to push it to my forked repository..
    https://src.fedoraproject.org/modules/ruby/branches
    Could you remove it?
    "wip/2.7" branch is just a branch from "2.7" branch + empty commit.

  • When do you need this? (YYYY/MM/DD)
    2020/09/10

  • When is this no longer needed or useful? (YYYY/MM/DD)
    2020/09/10

  • If we cannot complete your request, what is the impact?
    When we see branches on modules/ruby, the wrong branch makes us confused.


Metadata Update from @mohanboddu:
- Issue tagged with: low-gain, low-trouble, ops

3 years ago

@churchyard Is there a way to know what module builds are submitted from what branches? Just like the one for rpms/ ?

Maybe matching the context in a build with the git hash?

I have no idea at all, sorry.

The below "Stream" = the branch of the git, isn't it?

The 455108eb is the commit hash?

$ dnf module list ruby
Name                                    Stream                                    Profiles                                   Summary                                                                               
ruby                                    master                                    default                                    An interpreter of object-oriented scripting language  
$ dnf module info ruby
RCM Tools for Fedora 32 (RPMs)                                                                                                                                                     0.0  B/s |   0  B     00:00    
Errors during downloading metadata for repository 'rcm-tools-fedora-rpms':
  - Curl error (6): Couldn't resolve host name for https://download.devel.redhat.com/rel-eng/RCMTOOLS/latest-RCMTOOLS-2-F-32/compose/Everything/x86_64/os/repodata/repomd.xml [Could not resolve host: download.devel.redhat.com]
Error: Failed to download metadata for repo 'rcm-tools-fedora-rpms': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
Ignoring repositories: rcm-tools-fedora-rpms
Last metadata expiration check: 0:00:24 ago on Fri 11 Sep 2020 04:15:06 PM CEST.
Name             : ruby
Stream           : master
Version          : 3220200214171107
Context          : 43bbeeef
Architecture     : x86_64
Profiles         : default
Default profiles : 
Repo             : fedora-modular
Summary          : An interpreter of object-oriented scripting language
Description      : Ruby is the interpreted scripting language for quick and easy object-oriented programming.  It has many features to process text files and to do system management tasks (as in Perl).  It is simple, straight-forward, and extensible.
Requires         : platform:[f32]
Artifacts        : ruby-0:2.7.0-127.module_f32+7982+455108eb.i686
                 : ruby-0:2.7.0-127.module_f32+7982+455108eb.src
...

Currently we dont know of a easy way to identify what builds are submitted from what branches in modules/ namespace.

We are closing this ticket as cant fix. Sorry for the trouble.

Metadata Update from @mohanboddu:
- Issue close_status updated to: Can't Fix
- Issue status updated to: Closed (was: Open)

3 years ago

As we can not identify what builds are submitted, we can not remove the branch?
Really? can you check ruby module build's timestamp?

After I created wip/2.7 branch 13 days ago, there is no builds for module ruby.
That's a evidence to show the branch is not submitted, isn't it?

I think we can remove the branch according to this ticket's decision.
https://pagure.io/fesco/issue/2340#comment-628281

I think we can remove the branch according to this ticket's decision.
https://pagure.io/fesco/issue/2340#comment-628281

From what other branch is this branch reachable?

From what other branch is this branch reachable?

"2.7" branch.
The wrongly created "wip/2.7" branch is just a branch created from "2.7" branch + empty commit.

We agreed to removed it in releng meeting, I will get to it asap.

Metadata Update from @mohanboddu:
- Issue status updated to: Open (was: Closed)

3 years ago

Thanks for your help!

This should be fixed now.

Metadata Update from @mohanboddu:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

Issue status updated to: Open (was: Closed)

3 years ago

Issue status updated to: Closed (was: Open)
Issue close_status updated to: Fixed

3 years ago

Login to comment on this ticket.

Metadata
Boards 1
Ops Status: Done