View Issue Details

IDProjectCategoryView StatusLast Update
0007816Kali LinuxGeneral Bugpublic2023-05-08 01:15
ReporterCondom Assigned Torhertzog  
Status closedResolutionduplicate 
Product Version2018.1 
Summary0007816: [REPOS] Repository is missing DEP-11 / appstream metadata

when ever i launch my gnome software all i can see is extensions ...... i have updated my packages ..upgraded packages and distribution ...but it doesn't work at all

Attached Files


duplicate of 0004653 assignedrhertzog [REPOS] Repository is missing DEP-11 / appstream metadata 




2018-03-28 07:48

administrator   ~0016427

I believe that the reason is the lack of appstream metadata in Kali repositories:

Debian repositories have this. But we are using reprepro to manage the repository and it doesn't offer this feature currently.



2022-07-09 16:38

reporter   ~0016429

Hello friends,

Upping this one with a KDE Discover screenshot demonstrating the same issue.

I added comments in both Debian bug discussion and aptly's issue on GH ( in the hope it will revive will to improve the situation.

@rhertzog like said there, don't know what the amount would be, but again I'd gladly help funding the resolution of this here and anywhere upstream. Kali is AFAIC the very best Debian based KDE workstation OS and this one is a pain for UX.

Thanks for all the amazing work folks. Have a beautiful WE :)

PS: Can't Kali infrastructure make use of appstream-generator on its own without depending on repository management software ? As I understand it, it looks like KDE Neon is doing so with Aptly:

Screenshot_20220709_182757.png (91,285 bytes)   
Screenshot_20220709_182757.png (91,285 bytes)   


2022-07-18 07:14

administrator   ~0016430

At some point the appstream files must be recorded in the "Release" file managed by reprepro. There might be ways to script a change to this file with some hook but it's non trivial (and nobody has done it yet on the Kali side).



2022-12-03 18:29

reporter   ~0017130

Duplicate of 0004653 (another wrongly cloned issue...)



2023-05-06 10:13

reporter   ~0017886

Still open but a duplicate of 0004653 (wrongly cloned in the past)

Issue History

Date Modified Username Field Change
2022-07-24 20:16 Condom New Issue
2022-07-24 20:16 Condom Issue generated from: 0004653
2022-12-03 18:29 kali-bugreport Note Added: 0017130
2023-05-06 10:13 kali-bugreport Note Added: 0017886
2023-05-08 01:15 arnaudr Status assigned => closed
2023-05-08 01:15 arnaudr Resolution open => duplicate
2023-05-08 01:15 arnaudr Relationship added duplicate of 0004653