<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>13471</bug_id>
          
          <creation_ts>2019-08-08 14:33:29 +0000</creation_ts>
          <short_desc>Many packages do not have HOMEPAGE/DESCRIPTIONs</short_desc>
          <delta_ts>2021-03-18 10:58:59 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>7</classification_id>
          <classification>Build System, Metadata &amp; Runtime</classification>
          <product>OE-Core</product>
          <component>core</component>
          <version>3.0</version>
          <rep_platform>All</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard>NEWCOMER</status_whiteboard>
          <keywords></keywords>
          <priority>Medium</priority>
          <bug_severity>minor</bug_severity>
          <target_milestone>3.3</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Randy MacLeod">randy.macleod</reporter>
          <assigned_to name="Unassigned">unassigned</assigned_to>
          <cc>dorindabassey</cc>
    
    <cc>idadelm</cc>
    
    <cc>maxime.roussinbelanger</cc>
    
    <cc>meta.mr.watcher</cc>
    
    <cc>meta.watcher</cc>
    
    <cc>richard.purdie</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>No (bug/feature does not impact docs)</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>84607</commentid>
    <comment_count>0</comment_count>
    <who name="Randy MacLeod">randy.macleod</who>
    <bug_when>2019-08-08 14:33:29 +0000</bug_when>
    <thetext>Many packages do not have HOMEPAGE / DESCRIPTIONs.

This would be a good newcomer defect.
Should the commits be done one per recipe or as a batch?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>84613</commentid>
    <comment_count>1</comment_count>
    <who name="Randy MacLeod">randy.macleod</who>
    <bug_when>2019-08-08 14:55:45 +0000</bug_when>
    <thetext>Batches of a few to 10 recipes updates ideally as the recipes are being done would be good.
If someone wants to do all of these in batches, that would be great.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>84744</commentid>
    <comment_count>2</comment_count>
    <who name="Maxime Roussin-Bélanger">maxime.roussinbelanger</who>
    <bug_when>2019-08-23 19:00:29 +0000</bug_when>
    <thetext>I will work on this one.

I was thinking creating a batch patch. I feel having a patch for each recipe might be noisy in the git history?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>84746</commentid>
    <comment_count>3</comment_count>
    <who name="Randy MacLeod">randy.macleod</who>
    <bug_when>2019-08-23 19:44:19 +0000</bug_when>
    <thetext>Maxime, Thanks for taking on this work.
Perhaps it makes sense to do the work by directory:

$ ls -1 -d meta/recipes-* 
meta/recipes-bsp
meta/recipes-connectivity
meta/recipes-core
meta/recipes-devtools
meta/recipes-extended
meta/recipes-gnome
meta/recipes-graphics
meta/recipes-kernel
meta/recipes-multimedia
meta/recipes-rt
meta/recipes-sato
meta/recipes-support

and even by groups of ~ 10-20 recipes within those directories. 
That way you can send a few commits in at a time as you do the work. 
It will be a bit noisier but in some projects that I&apos;ve worked on, commits that touch most of the files in a single commit can interfere with cherry-picking patches when doing maintenance.

It&apos;s your call and thanks again!</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>86547</commentid>
    <comment_count>4</comment_count>
    <who name="Randy MacLeod">randy.macleod</who>
    <bug_when>2020-02-21 15:53:51 +0000</bug_when>
    <thetext>Hi Maxime,

Thanks again for working on this. 
I see your commits so far:

$ git log --oneline --author=maxime.roussinbelanger@gmail.com
b025b433c6 meta: add missing description for some recipes in graphics
5714e4fb5e meta: add missing description in recipes-gnome
9e5089dac1 meta: update and add missing homepage/bugtracker links
3a4a037450 meta: add missing description in recipes-extended
1c60c5744b shadow: update homepage and bugtracker
ca7570d8c3 meta: simplify over descriptive descriptions in devtools
57075f3ded meta: add missing some description in devtools
ec4fdfcc7b meta: add missing descriptions and homepage in bsp
e5f4e0df64 cmake: Use find_program if find_host_program is not available

Do you think you&apos;ll take time to finish the task?

Oh, it might be nice to have the layerindex report on missing homepages by layer.
   https://layers.openembedded.org/layerindex/about
but that should be a separate bug/enhancement.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>88491</commentid>
    <comment_count>5</comment_count>
    <who name="Maxime Roussin-Bélanger">maxime.roussinbelanger</who>
    <bug_when>2020-10-26 18:14:35 +0000</bug_when>
    <thetext>(In reply to comment #4)
&gt; Hi Maxime,

Hi Randy,

Sorry work has been crazy the last few months, taking more responsibility.

I&apos;ll continue to add more missing homepages/description.

I had a script running to check all the homepages that were not responding, so that&apos;s easy enough.

The descriptions are more work, but doable, to ease the work load I think I&apos;ll send smaller batches.
 
&gt; 
&gt; Thanks again for working on this. 
&gt; I see your commits so far:
&gt; 
&gt; $ git log --oneline --author=maxime.roussinbelanger@gmail.com
&gt; b025b433c6 meta: add missing description for some recipes in graphics
&gt; 5714e4fb5e meta: add missing description in recipes-gnome
&gt; 9e5089dac1 meta: update and add missing homepage/bugtracker links
&gt; 3a4a037450 meta: add missing description in recipes-extended
&gt; 1c60c5744b shadow: update homepage and bugtracker
&gt; ca7570d8c3 meta: simplify over descriptive descriptions in devtools
&gt; 57075f3ded meta: add missing some description in devtools
&gt; ec4fdfcc7b meta: add missing descriptions and homepage in bsp
&gt; e5f4e0df64 cmake: Use find_program if find_host_program is not available
&gt; 
&gt; Do you think you&apos;ll take time to finish the task?
&gt; 
&gt; Oh, it might be nice to have the layerindex report on missing homepages by
&gt; layer.
&gt;    https://layers.openembedded.org/layerindex/about

I went to look on that website, but I can&apos;t figure out what I should be looking for?

Thanks,
Max.

&gt; but that should be a separate bug/enhancement.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>88500</commentid>
    <comment_count>6</comment_count>
    <who name="Randy MacLeod">randy.macleod</who>
    <bug_when>2020-10-27 08:31:43 +0000</bug_when>
    <thetext>Maxime,

Thanks for the update, it&apos;s been a crazy year and I understand that it&apos;s hard to make time for YP work but keep pushing. :)

Randy said
&gt; &gt; Oh, it might be nice to have the layerindex report on missing homepages by
&gt; &gt; layer.
&gt; &gt;    https://layers.openembedded.org/layerindex/about
&gt;
&gt; Maxime said: 
&gt; I went to look on that website, but I can&apos;t figure out what I should be looking for?

I&apos;m not sure at this point either! :)  I guess I was thinking that you&apos;d try to
run the software that generates the layer index site and change it to either
report the recipes with missing info so that you don&apos;t have to go looking for them and/or generate a report per layer/repo about missing info. Does that make sense? It is somewhat beyond the scope of fixing the info but it could be useful.

I haven&apos;t tried to duplicate the layerindex so I&apos;m not sure how much work it would be.
../Randy</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>88501</commentid>
    <comment_count>7</comment_count>
    <who name="Maxime Roussin-Bélanger">maxime.roussinbelanger</who>
    <bug_when>2020-10-27 09:04:45 +0000</bug_when>
    <thetext>(In reply to comment #6)
&gt; Maxime,

Hello Randy!

&gt; 
&gt; Thanks for the update, it&apos;s been a crazy year and I understand that it&apos;s
&gt; hard to make time for YP work but keep pushing. :)
&gt; 
&gt; Randy said
&gt; &gt; &gt; Oh, it might be nice to have the layerindex report on missing homepages by
&gt; &gt; &gt; layer.
&gt; &gt; &gt;    https://layers.openembedded.org/layerindex/about
&gt; &gt;
&gt; &gt; Maxime said: 
&gt; &gt; I went to look on that website, but I can&apos;t figure out what I should be looking for?
&gt; 
&gt; I&apos;m not sure at this point either! :)  I guess I was thinking that you&apos;d try
&gt; to
&gt; run the software that generates the layer index site and change it to either
&gt; report the recipes with missing info so that you don&apos;t have to go looking
&gt; for them and/or generate a report per layer/repo about missing info. Does
&gt; that make sense? It is somewhat beyond the scope of fixing the info but it
&gt; could be useful.

Oh, I see what you mean now. If I choose this recipe: https://layers.openembedded.org/layerindex/recipe/555/

I see that the description is not available and there would be a way for me to figure out if a description is missing by regenerating this index on my side, with modifications. I see it now.

I went with the regex approach at the moment. Looking at all recipes that are missing the DESCRIPTION string. It has few drawbacks, one of them is I have to skip non-relevant files.

&gt; 
&gt; I haven&apos;t tried to duplicate the layerindex so I&apos;m not sure how much work it

I think this way is way more reliable than the regex way.

Thanks!
Max.

&gt; would be.
&gt; ../Randy</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>89247</commentid>
    <comment_count>8</comment_count>
    <who name="Maxime Roussin-Bélanger">maxime.roussinbelanger</who>
    <bug_when>2021-02-12 14:57:08 +0000</bug_when>
    <thetext>Hello Randy,

I a found a new job and it means that I&apos;ll leave the Yocto environment. It was great while it lasted. I&apos;ll unassigned my-self from the ticket.

Great community!

Cheers!
Max.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>89248</commentid>
    <comment_count>9</comment_count>
    <who name="Randy MacLeod">randy.macleod</who>
    <bug_when>2021-02-12 15:09:29 +0000</bug_when>
    <thetext>Hi Maxime, Congratulations that&apos;s great news. Good luck and thanks for your contributions! -- Randy</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>89251</commentid>
    <comment_count>10</comment_count>
    <who name="Randy MacLeod">randy.macleod</who>
    <bug_when>2021-02-12 19:18:26 +0000</bug_when>
    <thetext>Ida, Dorinda, Would one of you like to take this newcomer bug?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>89252</commentid>
    <comment_count>11</comment_count>
    <who name="Maxime Roussin-Bélanger">maxime.roussinbelanger</who>
    <bug_when>2021-02-12 19:26:29 +0000</bug_when>
    <thetext>For future contributors, I modified the Django backend Randy talked about, the layer index. It was the easiest way I found to find recipes with missing descriptions. 

I modified those files to only get recipes with empty descriptions:

poky/bitbake/lib/toaster/orm/models.py
poky/bitbake/lib/toaster/toastergui/tables.py

Project.get_available_recipes
Project.get_all_compatible_recipes
LayerRecipesTable.setup_queryset

```
.filter(description__exact=&apos;&apos;)
```

The last time I checked, there were ~300 recipes with missing descriptions.

Cheers,
Max.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>89258</commentid>
    <comment_count>12</comment_count>
    <who name="Ida Delphine">idadelm</who>
    <bug_when>2021-02-12 22:11:57 +0000</bug_when>
    <thetext>(In reply to comment #10)
&gt; Ida, Dorinda, Would one of you like to take this newcomer bug?
Sure. I will.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>89264</commentid>
    <comment_count>13</comment_count>
    <who name="Dorinda">dorindabassey</who>
    <bug_when>2021-02-14 13:42:33 +0000</bug_when>
    <thetext>Hi Ida,
I greped through recipes that don&apos;t have a DESCRIPTION and that&apos;s a lot, maybe we could work on it together taking sections. 
How about that :)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>89265</commentid>
    <comment_count>14</comment_count>
    <who name="Ida Delphine">idadelm</who>
    <bug_when>2021-02-14 20:11:08 +0000</bug_when>
    <thetext>(In reply to comment #13)
&gt; Hi Ida,
&gt; I greped through recipes that don&apos;t have a DESCRIPTION and that&apos;s a lot,
&gt; maybe we could work on it together taking sections. 
&gt; How about that :)

Yes. We definitely should :)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>89500</commentid>
    <comment_count>15</comment_count>
    <who name="Randy MacLeod">randy.macleod</who>
    <bug_when>2021-03-04 21:29:49 +0000</bug_when>
    <thetext>It&apos;s really nice to see several commits merged to master fixing the homepage and descriptions! Are there more to do or should this bug be closed?

6db24928d6 recipes-support: Add missing HOMEPAGE and DESCRIPTION for recipes
dad63dcd37 recipes-sato: Add missing HOMEPAGE and DESCRIPTION for recipes
312994268b recipes-multimedia: Add missing HOMEPAGE and DESCRIPTION for recipes.
16409694f1 recipes-kernel: Add missing HOMEPAGE and DESCRIPTION for recipes.
24eac1fef8 recipes-graphics: Add missing HOMEPAGE and DESCRIPTION for recipes.
e501e87b84 recipes-gnome: Add missing HOMEPAGE and DESCRIPTION for recipes</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>89501</commentid>
    <comment_count>16</comment_count>
    <who name="Dorinda">dorindabassey</who>
    <bug_when>2021-03-04 21:33:01 +0000</bug_when>
    <thetext>It&apos;s the meta-openembedded layer that&apos;s left to be worked on.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>89502</commentid>
    <comment_count>17</comment_count>
    <who name="Randy MacLeod">randy.macleod</who>
    <bug_when>2021-03-04 21:39:13 +0000</bug_when>
    <thetext>Dorinda, 
Ah, well meta-openembedded devs have never wanted to track bugs in the YP wiki so please close this issue when you get a chance. 

Oh wait... Is there a test to report on the number of packages that do NOT have Homepage, description entries? That could be a separate bug, I suppose, it&apos;s up to you.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>89503</commentid>
    <comment_count>18</comment_count>
    <who name="Dorinda">dorindabassey</who>
    <bug_when>2021-03-04 22:18:05 +0000</bug_when>
    <thetext>Okay will do, probably after the last patch series makes it&apos;s way into the source repository.

 Is there a test to report on the number of packages that do NOT have Homepage, description entries? That could be a separate bug

This is a cool idea, yes a separate bug entry, but there are something&apos;s to put into consideration, I noticed some recipes the likes of &quot;meta/recipes-extended/images&quot; does not have a homepage since there are no SRC_URI, and are not fetched from external sources. Would it be nice to make the test skip such recipes?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>89510</commentid>
    <comment_count>19</comment_count>
    <who name="Randy MacLeod">randy.macleod</who>
    <bug_when>2021-03-05 00:49:27 +0000</bug_when>
    <thetext>Yes, there will be exceptions such as:
   meta/recipes-extended/images

Perhaps it could be added to:
   meta/lib/oeqa/selftest/cases/distrodata.py
but I&apos;m suggesting it because I was looking at that test recently.
I think that would be a good start. Try it out and reply here to if you like or send an RFC to the email list.

Note: That you should use the poky tree to do those tests until:
   https://bugzilla.yoctoproject.org/show_bug.cgi?id=14277
is resolved.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>89511</commentid>
    <comment_count>20</comment_count>
    <who name="Dorinda">dorindabassey</who>
    <bug_when>2021-03-06 21:09:29 +0000</bug_when>
    <thetext>Alright, so i sent a RFC patch on the mailing list here:
https://lists.openembedded.org/g/openembedded-core/topic/81136066?p=,,,20,0,0,0::recentpostdate,,,20,2,0,0&amp;allview=1

and with this test i could still find a few recipes that didn&apos;t have HOMEPAGE but i find it weird that the &quot;check for recipes without DESCRIPTION&quot; is being bypassed :\

if not rd.getVar(&apos;DESCRIPTION&apos;):
     no_description.append((pn, fn))
if no_description:
     self.fail(&quot;&quot;&quot;
The following recipes do not have a DESCRIPTION. Please add an entry for DESCRIPTION in the recipe.
&quot;&quot;&quot; + &quot;\n&quot;.join([&apos;%s (%s)&apos; % i for i in no_description]))</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>89641</commentid>
    <comment_count>21</comment_count>
    <who name="Dorinda">dorindabassey</who>
    <bug_when>2021-03-18 10:58:59 +0000</bug_when>
    <thetext>To verify that recipes has HOMEPAGE or DESCRIPTION, this test has been added:
https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=a6932c2203cf89f072b7e9a266fd22b384ece6a4</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>