maemo.org Bugzilla – Bug 8788
Maemo5 packages have Debian maintainers listed but are not from Debian
Last modified: 2011-02-17 15:01:03 UTC
You need to log in before you can comment on or make changes to this bug.
SOFTWARE VERSION: 51.1 EXACT STEPS LEADING TO PROBLEM: 1. apt-cache show libc6 2. check "Maintainer" field EXPECTED OUTCOME: Maintainer: Joe Average <joe.average@nokia.com> (or any other email @nokia.com as package was created by nokia) ACTUAL OUTCOME: Maintainer: GNU Libc Maintainers <debian-glibc@lists.debian.org> REPRODUCIBILITY: always OTHER COMMENTS: There are many packages in Maemo5 which still have Debian maintainers listed as package maintainers. This should be fixed as Maemo5 is not Debian (it is even hard to tell that it is based on any release of Debian) so original maintainers do not know how those packages were built, by who, with which patches so they can not help users in case of problem.
Adding Daniel to CC:
(In reply to comment #0) > There are many packages in Maemo5 which still have Debian maintainers listed as > package maintainers. Any idea how to get a list of it? It's nearly impossible to process here as it's a generic report covering many packages. :-/
(In reply to comment #2) > Any idea how to get a list of it? Something like this should do it: $ egrep -h '^(Package|Maintainer):' /var/lib/apt/lists/*Packages | grep -B1 '@.*debian\.org' The above currently lists over 1000 packages in the SDK. Of course there are other mislabelled packages with a non-debian maintainer address so season the last part to taste. > It's nearly impossible to process here as it's a generic report covering many > packages. :-/ I see it more as a distribution-wide packaging policy issue. If there were just handful of problematic packages it would be probably better to file individual reports about each one, but that would be unworkable as things are now.
first of all sorry, that I have overseen this bug earlier. My suggestion would be to add "moreinfo" to this bug, and list which packages have the wrong maintainer, so that we could push that forward.
Created an attachment (id=2657) [details] List of SDK packages with non-nokia.com/maemo.org maintainer. > first of all sorry, that I have overseen this bug earlier. My suggestion would > be to add "moreinfo" to this bug, and list which packages have the wrong > maintainer, so that we could push that forward. Attaching a more specific (just from the SDK repositories) list of packages with a Maintainer: address not under nokia.com or maemo.org. Some of these might be correct (eg subcontractors like igalia.com or collabora.co.uk).
Created an attachment (id=2658) [details] List of tools packages with non-nokia.com/maemo.org maintainer. Same for the tools repository.
Daniel: Complete list available here. Any idea how to proceed?
(In reply to comment #7) > Daniel: Complete list available here. Any idea how to proceed? > Now we should file a bug report to each of the packages with "PE1 prop" keyword and add me to Cc and I will make sure that these are going to be fixed for PE1 latest.
(In reply to comment #8) > Now we should file a bug report to each of the packages Marcell, we talk about several hundreds of packages here. I could waste two workdays for filing reports but I wonder whether there is a better way (request on an internal maintainers mailing list or something)?
Lucas: Thanks for the lists. The question is now how to identify those packages from the list that have a wrong maintainer.
WONTFIX for Maemo5 according to Nokia, keeping this opened to handle this for the version after Maemo5.
No plans to fix this in Fremantle/Harmattan according to Nokia.