On versions 1.2.3, 2.2.1, and master, an import from fedorahosted does not create any tag data for issues. I ran them like this:
$ pgimport clone ssh://git@stg.pagure.io/tickets/gssproxy.git Cloning into bare repository '/tmp/gssproxy.git'... warning: You appear to have cloned an empty repository. $ pgimport fedorahosted https://fedorahosted.org/gss-proxy --tags Enter your FAS Username: rharwood Password: #### Repo available #### 1 - gssproxy.git Choose the import destination repo [1]: Updated gssproxy with issue :1/157 ... Updated gssproxy with issue :157/157 >$ pgimport push gssproxy.git Before executing this command, you must have "Pagure Tickets" enabled from pagure project's settings. Continue? [y/N]: y remote: Files changed by new commits: remote: remote: repo: gssproxy None None remote: To load: f1f5a0ef0e5940c49e216001b9782978 ... remote: To load: 5a59ad8d08af4fe4844f5461d1881fd0 To ssh://stg.pagure.io/tickets/gssproxy.git * [new branch] master -> master $
By --tags, the importer checks for keywords related to the issue. Are you sure, that you do have those keywords there?
--tags
keywords
I checked all of the current open tickets in the gss-proxy trac and they all have a component set, but none of them have any keywords.
So currently the importer does not import components, if this is critical for the project import to pagure. I can add components support in the next release .
I have a patch that does the markdown conversion and brings in all the custom fields i nfrom trac. It's not fully tested so I never submitted it. I'm having other importing issues though (need to open an Issue for that though).
PR #122 merges a lot of the extra metadata from Trac to Pagure.
Fixed in #122
Metadata Update from @vivekanand1101: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.