#42 Import wiki page Reporting Issues in Packages
Merged 2 years ago by ankursinha. Opened 2 years ago by oturpe.
fedora-docs/ oturpe/package-maintainer-docs import-reporting-issues-in-packages  into  main

file modified
+2
@@ -22,6 +22,8 @@ 

  

  * xref:Package_Update_Guide.adoc[Package Update Guide]

  

+ * xref:Reporting_Issues.adoc[Reporting Issues]

+ 

  * xref:Staying_Close_to_Upstream_Projects.adoc[Staying Close to Upstream Projects]

  

  * xref:Using_the_Koji_Build_System.adoc[Using the Koji Build System]

@@ -0,0 +1,30 @@ 

+ = Reporting Issues

+ :toc

+ 

+ When working with Fedora Packaging, you may run across issues

+ in packages,

+ with the buildsystem,

+ with policies or process,

+ or with any number of other things.

+ Here are some basic guidelines to assist you

+ in reporting such issues to the right people.

+ 

+ [#where]

+ == Where to Report Issues

+ 

+ Any issue that requires direct work on Fedora's infrastructure

+ should be reported using the

+ https://pagure.io/fedora-infrastructure/issues[Fedora Infrastructure issue tracker].

+ This would include frozen or failing build systems.

+ 

+ For issues within packages, see

+ https://docs.fedoraproject.org/en-US/quick-docs/howto-file-a-bug/[How to File a Bug].

+ This would include typical build errors.

+ 

+ Any questions about policy or processes should be reported to the

+ https://lists.fedoraproject.org/admin/lists/devel-announce@lists.fedoraproject.org/[devel] mailing list.

The URL is wrong here for two reasons:

  1. It points to devel-announce instead of devel
  2. It doesn't point to Hyperkitty, which is a more friendly place to send folks https://lists.fedoraproject.org/archives/list/devel%40lists.fedoraproject.org/

+ This would include questions of spec design, naming conventions or review concerns.

+ 

+ If ever you are unsure about which system to use,

+ feel free to report to whichever system seems best to you.

+ Your report can be redirected as needed.

Some of the information on the page was already stale,
it was rewritten to describe the current practices.
Also, instuctions for filing bugs in packages are replaced
with a link to similar article in the Quick Docs.

rebased onto 0761d62c82809acde9b24d3e01eea775a19efae0

2 years ago

rebased onto 7905d96e29c3e7d2f270228ba15fb75f6ed4ac54

2 years ago

Just FYI, this exists in quick-docs:

https://docs.fedoraproject.org/en-US/quick-docs/howto-file-a-bug/

It needs to be updated a little, I think there's a ticket in the quick-docs repo about that too.

Thank you for bringing that up.
I would say it is the best to just link to that page for bugs in packages.
Discussion of Infrastructure tickets and so on are can stay in this page I think.
That being so,
the page title could also be better,
seeing that the page is actually not about "bugs in packages",
but about "issues affecting packaging".

rebased onto d96fb31b865bcc504ecb7c6d1c0021b37a7dd142

2 years ago

@ankursinha I think this is ready.
Could you review and merge if everything is all right?
I will handle the wiki cleanup afterwards.

Metadata Update from @ankursinha:
- Request assigned

2 years ago

rebased onto 1eeacb3

2 years ago

Pull-Request has been merged by ankursinha

2 years ago

The URL is wrong here for two reasons:

  1. It points to devel-announce instead of devel
  2. It doesn't point to Hyperkitty, which is a more friendly place to send folks https://lists.fedoraproject.org/archives/list/devel%40lists.fedoraproject.org/

The URL is wrong here for two reasons:

  1. It points to devel-announce instead of devel
  2. It doesn't point to Hyperkitty, which is a more friendly place to send folks https://lists.fedoraproject.org/archives/list/devel%40lists.fedoraproject.org/

Good catch. Fixed in f442034.