Bug#681687: missing mime entry
Steve Langasek writes (Bug#681687: missing mime entry): On Thu, Jul 26, 2012 at 04:48:59PM +0100, Ian Jackson wrote: 3. We agree with the Release Team that it is now too late to deploy such automation in wheezy. I don't actually agree that it's too late, but I would vote for a resolution that says: Right. Thanks. As discussed on IRC, I would prefer vote on this. That gives us two versions to vote on. I will prepare a ballot. 3. We defer to the Release Team's decision that it is now too late to deploy such automation in wheezy. I'll take your email as a formal proposal for an amendment. (Alternatively if that's not what you meant then please consider me to have proposed but not accepted your amendment.) Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681687: missing mime entry
On Sun, Jul 22, 2012 at 01:51:32PM -0700, Steve Langasek wrote: If it's the solution that the TC decide on to resolve the issue, it sounds like something we could work with, at least imho, from what I've seen so far. I've CCed -release for any further comments, as I don't know how many members of the team are following -ctte and/or this bug. Broadly speaking, I think the correct long-term solution is to first add support to update-mime for reading both .desktop files and mime files, and then to update policy to tell maintainers to use .desktop files instead of mime files. And I think it's better for Debian if we can get the first part done prior to the wheezy release. But I would like the release team to make their own determination of whether the patch that's currently up for consideration is of sufficient quality, and sufficiently safe, to be granted a freeze exception. I completely agree with getting rid of the manual mime entries where they can be automatically generated. I have concerns that the .desktop format means that it won't work for some packages, but those could always carry manual entires. However, I really do think that pushing in a system wide change at this stage in the release is not desireable at all, so woudn't be happy to see it in Wheezy. If we wanted to do this, it should have been started about two years ago. I *would* however, be very happy to have this as a release goal for wheezy+1. Neil -- signature.asc Description: Digital signature
Bug#681687: missing mime entry
Neil McGovern writes (Bug#681687: missing mime entry): However, I really do think that pushing in a system wide change at this stage in the release is not desireable at all, so woudn't be happy to see it in Wheezy. If we wanted to do this, it should have been started about two years ago. I agree. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681687: missing mime entry
I hereby propose the following TC resolution (and withdraw my previous version): 1. The Technical Committee agrees with Neil McGovern's analysis of the situation regarding evince's missing mime type entry. 2. If changes are desirable to our system for dealing with mime type entries and desktop files, including changes to policy or additional automation, these should be made via the usual development and policy amendment processes. 3. We agree with the Release Team that it is now too late to deploy such automation in wheezy. 4. We do not disagree with the Release Team's assessment that the failure of the evince package to provide a mime type entry is a release critical bug. 5. We therefore decline to overrule the Release Team. The bug remains RC against evince. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681687: missing mime entry
Le jeudi 26 juillet 2012 à 12:50 +0100, Ian Jackson a écrit : 4. We do not disagree with the Release Team's assessment that the failure of the evince package to provide a mime type entry is a release critical bug. Before you vote on that: with the maintainer’s hat, I’d appreciate if the ruling could also make explicit which MIME types it applies to. From what I understand, it is only application/pdf, not the 20 other MIME types that evince can handle, nor their non-standard aliases (like application/x-pdf) which are handled automatically by the XDG system. -- .''`. Josselin Mouette : :' : `. `' `- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681687: missing mime entry
Josselin Mouette writes (Bug#681687: missing mime entry): Le jeudi 26 juillet 2012 à 12:50 +0100, Ian Jackson a écrit : 4. We do not disagree with the Release Team's assessment that the failure of the evince package to provide a mime type entry is a release critical bug. Before you vote on that: with the maintainer’s hat, I’d appreciate if the ruling could also make explicit which MIME types it applies to. I am content to leave that decision to the release team. I'm happy to clarify. So I hereby propose the following TC resolution (and withdraw my previous versions): 1. The Technical Committee agrees with Neil McGovern's analysis of the situation regarding evince's missing mime type entry. 2. If changes are desirable to our system for dealing with mime type entries and desktop files, including changes to policy or additional automation, these should be made via the usual development and policy amendment processes. 3. We agree with the Release Team that it is now too late to deploy such automation in wheezy. 4. We do not disagree with the Release Team's assessment that the failure of the evince package to provide a mime type entry is a release critical bug. 5. We therefore decline to overrule the Release Team. The bug remains RC against evince. 6. The release team should clarify which mime types the RC-bugginess applies to. We recommend that the starting point should be those mime types advertised by evince via the mime system in squeeze. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681687: missing mime entry
On Thu, Jul 26, 2012 at 04:48:59PM +0100, Ian Jackson wrote: Josselin Mouette writes (Bug#681687: missing mime entry): Le jeudi 26 juillet 2012 à 12:50 +0100, Ian Jackson a écrit : 4. We do not disagree with the Release Team's assessment that the failure of the evince package to provide a mime type entry is a release critical bug. Before you vote on that: with the maintainer’s hat, I’d appreciate if the ruling could also make explicit which MIME types it applies to. I am content to leave that decision to the release team. I'm happy to clarify. So I hereby propose the following TC resolution (and withdraw my previous versions): 1. The Technical Committee agrees with Neil McGovern's analysis of the situation regarding evince's missing mime type entry. 2. If changes are desirable to our system for dealing with mime type entries and desktop files, including changes to policy or additional automation, these should be made via the usual development and policy amendment processes. 3. We agree with the Release Team that it is now too late to deploy such automation in wheezy. I don't actually agree that it's too late, but I would vote for a resolution that says: 3. We defer to the Release Team's decision that it is now too late to deploy such automation in wheezy. 4. We do not disagree with the Release Team's assessment that the failure of the evince package to provide a mime type entry is a release critical bug. 5. We therefore decline to overrule the Release Team. The bug remains RC against evince. 6. The release team should clarify which mime types the RC-bugginess applies to. We recommend that the starting point should be those mime types advertised by evince via the mime system in squeeze. Otherwise I have no objections here. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Bug#681687: missing mime entry
On 21.07.2012 23:40, Adam D. Barratt wrote: On Sat, 2012-07-21 at 23:12 +0200, Michael Biebl wrote: On 21.07.2012 09:11, Steve Langasek wrote: Now, I think providing a tool to auto-translate .desktop files into mailcap entries is a perfectly appropriate way to go about solving this bug, if [...] The new mime support maintainer team, which took over the package just a few days ago, did ask the release team, if it would be possible to still apply this patch for wheezy [2]. [...] [2] https://lists.debian.org/debian-release/2012/07/msg01048.html As far as I can tell, that's very much not what that message says. In fact, it doesn't appear to request anything of the release team at all. Well, Charles did not specifically ask the release team, but he CCed the release team and his email contains: 4) Postpone any other change on the main branch until either #681687 (tech. comittee) is solved or Wheezy released. This reads to me as if Charlees is waiting for a decision from the ctte. If Steve and other members of the ctte consider such a tool as an approriate way to solve this bug, would the release team also acknowledge this approach or not? Anyway, let's put Charles and Laszlo on CC so they have chance to comment on it. My position is clearly, that this issue should be solved for good. Postponing this for another release just doesn't seem right to me, as simply adding back a single mime file would be an incomplete workaround at best. From past experience we still have around 5 months until we release. This should be enough time to get this ready for wheezy. And as said, if unsurmountable problems turn up which can't be addressed within say two months, we can simply drop the converter again and then add back the evince mime file. Is this a proposal that the ctte, release team and mime-support maintainers could agree with? Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#681687: missing mime entry
On Sun, 2012-07-22 at 15:24 +0200, Michael Biebl wrote: On 21.07.2012 23:40, Adam D. Barratt wrote: On Sat, 2012-07-21 at 23:12 +0200, Michael Biebl wrote: On 21.07.2012 09:11, Steve Langasek wrote: Now, I think providing a tool to auto-translate .desktop files into mailcap entries is a perfectly appropriate way to go about solving this bug, if [...] The new mime support maintainer team, which took over the package just a few days ago, did ask the release team, if it would be possible to still apply this patch for wheezy [2]. [...] [2] https://lists.debian.org/debian-release/2012/07/msg01048.html As far as I can tell, that's very much not what that message says. In fact, it doesn't appear to request anything of the release team at all. Well, Charles did not specifically ask the release team, but he CCed the release team Well, he hit reply all on a thread that was already CCed to the release team. I'm not sure it would otherwise have been copied. and his email contains: 4) Postpone any other change on the main branch until either #681687 (tech. comittee) is solved or Wheezy released. This reads to me as if Charlees is waiting for a decision from the ctte. Agreed. It's still not even implicitly a request for release team comment on the solution imo, but let's leave that particular horse in peace before the discussion gets any more circular. :-/ If Steve and other members of the ctte consider such a tool as an approriate way to solve this bug, would the release team also acknowledge this approach or not? If it's the solution that the TC decide on to resolve the issue, it sounds like something we could work with, at least imho, from what I've seen so far. I've CCed -release for any further comments, as I don't know how many members of the team are following -ctte and/or this bug. For clarity, the current proposal would be http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=35;filename=mime-support-desktop.patch;att=1;bug=497779 , or something similar? [...] From past experience we still have around 5 months until we release. This should be enough time to get this ready for wheezy. And as said, if unsurmountable problems turn up which can't be addressed within say two months, we can simply drop the converter again and then add back the evince mime file. With my release hat on, it feels like there's still a while until we release is being used more often recently as a justification for trying to get larger scale changes incorporated or fixes delayed. While I'm not implying that's the intention in this case, I do think we need to be wary of saying there'll be plenty of time to fix that still. /soapbox Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681687: missing mime entry
Adam D. Barratt writes (Bug#681687: missing mime entry): If it's the solution that the TC decide on to resolve the issue, it sounds like something we could work with, at least imho, from what I've seen so far. I've CCed -release for any further comments, as I don't know how many members of the team are following -ctte and/or this bug. Right. So far I think my personal view is that I'm happy for the release team to carry on doing whatever they think is best, on this issue. For clarity, the current proposal would be http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=35;filename=mime-support-desktop.patch;att=1;bug=497779 , or something similar? I would be worried that this would make a widespread and radical change to the behaviour of the mime-support-using packages. Are we sure that that's the right thing to do at this stage of the release ? If we were wanting to do this properly, we would compare the automatically-generated entires with the previous manually-written ones, to see what behavioural changes we would expect. With my release hat on, it feels like there's still a while until we release is being used more often recently as a justification for trying to get larger scale changes incorporated or fixes delayed. While I'm not implying that's the intention in this case, I do think we need to be wary of saying there'll be plenty of time to fix that still. /soapbox I certainly don't think we failed to get the automatic machinery deployed and tested properly before the freeze is a good excuse for insisting on a freeze exception for it. I can see why the evince maintainers are reluctant to keep on with an approach they regard as obsolete and deprecated, but until the replacement is properly deployed and tested that's what we should do. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681687: missing mime entry
On Sat, Jul 21, 2012 at 11:12:25PM +0200, Michael Biebl wrote: A patch providing this converter has been available for a few months [1]. The mime-support maintainer just never got around to upload it or even comment on it. The new mime support maintainer team, which took over the package just a few days ago, did ask the release team, if it would be possible to still apply this patch for wheezy [2]. I think this should be the solution we should aim for and I would appreciate if the release team could give the mime-support maintainers a green light for the unstable upload. I agree that we should aim for such an automated, long-term solution. In the meantime, I think it's correct to say that evince has a release-critical bug. I think that the right thing for the evince maintainers to do is to upload the package *now* with re-added mime-support handling, and worry about dropping it only after mime-support .desktop support has proven itself - knowing that this may not happen in time for the wheezy release. (And if you disagree, well, it's an RC bug... so someone can upload an NMU for it...) If the converter solution turns out to be too buggy or requires larger changes, we have a simple contigency plan, i.e. just drop the converter again. I would really appreciate if we could try to fix this *whole* issue for good for *wheezy*. Re-adding the mime file in evince can still be done if the proper mime-support fix has not been done in say a month or two. From the discussion so far, there are two issues that in the release managers' position, I would be concerned about seeing addressed before endorsing this as a solution for wheezy. - The .desktop format does not include an equivalent to the mailcap 'priority' field; it's not clear what the expected / desirable handling is when multiple packages provide .desktop files for the same mime type. The documented default priority is '5', which is probably a reasonable starting point, but there's still a loss of expressiveness that seems to require an extension of the .desktop file format (especially since priority values are meant to be per-mime-type). - It's not clear what the transitional behavior should be when a package includes both a .desktop file and a usr/lib/mime/packages file. There's no reliable way to associate the contents of the two files, so this probably ends up with duplicated entries in /etc/mailcap, possibly with small variations; just from a quick look on my system, I find that the libreoffice .desktop and mime files use quite different program invocations. This is of course exactly why we want to not maintain duplicate information in multiple files, but we should have a clear idea about which we expect to take precedence, and make sure this is implemented, so that users don't wind up with buggy behavior on their systems due to random ordering. If this update-mime change is accepted for wheezy, the transition will most definitely be ongoing at release time, so we really ought to get this right. But that's just my two cents; the release managers may have a different set of concerns. Either way, my recommendation to the GNOME maintainers is that if you think it's important to not have to re-add the mime file to evince for wheezy, you should participate in finding a solution to these issues and not regard it as the mime-support maintainer's problem to fix - which I have the impression has been the general approach up to this point. On Sun, Jul 22, 2012 at 03:43:10PM +0100, Adam D. Barratt wrote: If Steve and other members of the ctte consider such a tool as an approriate way to solve this bug, would the release team also acknowledge this approach or not? If it's the solution that the TC decide on to resolve the issue, it sounds like something we could work with, at least imho, from what I've seen so far. I've CCed -release for any further comments, as I don't know how many members of the team are following -ctte and/or this bug. Broadly speaking, I think the correct long-term solution is to first add support to update-mime for reading both .desktop files and mime files, and then to update policy to tell maintainers to use .desktop files instead of mime files. And I think it's better for Debian if we can get the first part done prior to the wheezy release. But I would like the release team to make their own determination of whether the patch that's currently up for consideration is of sufficient quality, and sufficiently safe, to be granted a freeze exception. For clarity, the current proposal would be http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=35;filename=mime-support-desktop.patch;att=1;bug=497779 , or something similar? Yes. The nascent mime-support maintenance team has also committed a patch to the repo at http://anonscm.debian.org/gitweb/?p=collab-maint/mime-support.git;a=summary, probably best to reference the version there. -- Steve
Bug#681687: missing mime entry
Steve Langasek vor...@debian.org writes: - It's not clear what the transitional behavior should be when a package includes both a .desktop file and a usr/lib/mime/packages file. There's no reliable way to associate the contents of the two files, so this probably ends up with duplicated entries in /etc/mailcap, possibly with small variations; just from a quick look on my system, I find that the libreoffice .desktop and mime files use quite different program invocations. This is of course exactly why we want to not maintain duplicate information in multiple files, but we should have a clear idea about which we expect to take precedence, and make sure this is implemented, so that users don't wind up with buggy behavior on their systems due to random ordering. If this update-mime change is accepted for wheezy, the transition will most definitely be ongoing at release time, so we really ought to get this right. I think the mime/packages file should obviously take precedence for programs using mailcap, since that's the target of the automated conversion. You always want the manually-maintained file to override the results of any automated conversion, since that way you can work around any bugs in the conversion (or missing features, like priority) by providing a manually-maintained file. Broadly speaking, I think the correct long-term solution is to first add support to update-mime for reading both .desktop files and mime files, and then to update policy to tell maintainers to use .desktop files instead of mime files. And I think it's better for Debian if we can get the first part done prior to the wheezy release. But I would like the release team to make their own determination of whether the patch that's currently up for consideration is of sufficient quality, and sufficiently safe, to be granted a freeze exception. This sounds right to me as well. I think we should ensure the most critical media types are working in both systems for the wheezy release and then aim at removing the requirement to support update-mime for all packages providing .desktop files for wheezy+1. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681687: missing mime entry
On Sun, 2012-07-22 at 15:24 +0200, Michael Biebl wrote: [...] The new mime support maintainer team, which took over the package just a few days ago, did ask the release team, if it would be possible to still apply this patch for wheezy [2]. [...] [2] https://lists.debian.org/debian-release/2012/07/msg01048.html Dear all, about the mail discussed above: while it is addressed to Brian and Laszlo, I made sure that the release team, the technical comitte and the evince maintainers get a copy so that they can see that things are moving. But before getting Laszlo's and Brian's replies, I did not feel like making promises. Nevertheless, earlier in http://bugs.debian.org/658139#117, I also wrote the following to everybody, with the release team, the tech. comittee and the evince maintainers copied: Wouldn't one of the following solutions be acceptable for you ? - Add the function to mime-support in Wheezy to update /etc/mailcap using the FreeDesktop menu entry files in /usr/share/applications via dpkg triggers. - Do this in Sid, and add back the MIME entries in evince in Wheezy as a temporary compromise. To keep both possibilities open - without expressing a particular preference for one or another - me and Laszlo are limiting ourselves to work on the conversion from Desktop to mailcap, with exceptions limited to packaging updates that I hope will not prevent our package to be reviewed by the release team if the consensus is to update mime-support in Wheezy. We are getting ready to upload to experimental; things go a bit slowly because time zone effects inserts some delays between our email exchanges, but on the other hand, I think that it is a good thing as mime-support will be the first time I work on a package of standard priority. Also, it happens that the previous and next week-ends I am not avaiable for Debian work, which postpones more extensive tests on my side, but I think that an upload to experimental would be appropriate now. The last piece missing is that we are looking for a mailing list address for the Maintainer field, as the trick to send messages to the PTS do not work because it would create loops. Or perhaps we can enhance the PTS to not transmit messages to itself... I intend to announce on debian-devel that the adoption has been completed after we uploaded to experimental (Laszlo, you are of course free to do so yourself if you are the one who uploads). As Steve noted later in this thread, the package is already in collab-maint, although I would like to keep an option option just in case until we upload, that in case we find a defect in the conversion we might reset it. http://anonscm.debian.org/gitweb/?p=collab-maint/mime-support.git Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681687: missing mime entry
On Thu, Jul 19, 2012 at 12:34:19AM +0100, Ian Jackson wrote: Neil McGovern writes (Bug#681687: missing mime entry): As I understand it, there are still a number of issues with this approach (.desktop files do not contain enough information to get argument ordering correct in all cases, and it's far too late to start using a new auto-generation system this late in the cycle). I don't think it likely that the TC will want to overrule the Release Team's decision on this point. So I hereby propose the following TC resolution: 1. The Technical Committee agrees with Neil McGovern's analysis of the situation regarding evince's missing mime type entry. 2. If changes are desirable to our system for dealing with mime type entries and desktop files, including changes to policy or additional automation, these should be made via the usual development and policy amendment processes. It is now too late to do this for wheezy. 3. We do not disagree with the Release Team's assessment that the failure of the evince package to provide a mime type entry is a release critical bug. 4. We therefore decline to overrule the Release Team. I concur with this. update-mime is a Policy requirement; maintainers don't get to unilaterally decide that bits of Policy are obsolete and ignore them on the basis that the applications they care about are using a different interface. Maintainers have a duty to either follow the Policy, or engage the Debian community to get Policy changed. And I think the GNOME Maintainers haven't done the latter because they know it wouldn't fly - this is a change that breaks compatibility with other software and renders the system as a whole buggier, and changing Policy doesn't paper over that. I'm inclined to think that this should be considered RC for a lot more packages than just evince. I'm not going to go hunting those, but I definitely support the release team's position that it be RC for evince in particular, because evince is the default pdf viewer and pdfs are a very common document type to be passed around between applications that don't yet implement the freedesktop standard. Now, I think providing a tool to auto-translate .desktop files into mailcap entries is a perfectly appropriate way to go about solving this bug, if someone chooses to do that. If such a tool emerges, I think that's great for Debian as a whole, and we can consider revising Policy to consider .desktop files the primary interface instead. But until we have such a tool working in the release, it's the responsibility of the evince maintainers to make sure their package complies with policy. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Bug#681687: missing mime entry
On 21.07.2012 09:11, Steve Langasek wrote: Now, I think providing a tool to auto-translate .desktop files into mailcap entries is a perfectly appropriate way to go about solving this bug, if someone chooses to do that. If such a tool emerges, I think that's great for Debian as a whole, and we can consider revising Policy to consider .desktop files the primary interface instead. But until we have such a tool working in the release, it's the responsibility of the evince maintainers to make sure their package complies with policy. A patch providing this converter has been available for a few months [1]. The mime-support maintainer just never got around to upload it or even comment on it. The new mime support maintainer team, which took over the package just a few days ago, did ask the release team, if it would be possible to still apply this patch for wheezy [2]. I think this should be the solution we should aim for and I would appreciate if the release team could give the mime-support maintainers a green light for the unstable upload. If the converter solution turns out to be too buggy or requires larger changes, we have a simple contigency plan, i.e. just drop the converter again. I would really appreciate if we could try to fix this *whole* issue for good for *wheezy*. Re-adding the mime file in evince can still be done if the proper mime-support fix has not been done in say a month or two. Michael [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497779 [2] https://lists.debian.org/debian-release/2012/07/msg01048.html -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#681687: missing mime entry
On Sat, 2012-07-21 at 23:12 +0200, Michael Biebl wrote: On 21.07.2012 09:11, Steve Langasek wrote: Now, I think providing a tool to auto-translate .desktop files into mailcap entries is a perfectly appropriate way to go about solving this bug, if [...] The new mime support maintainer team, which took over the package just a few days ago, did ask the release team, if it would be possible to still apply this patch for wheezy [2]. [...] [2] https://lists.debian.org/debian-release/2012/07/msg01048.html As far as I can tell, that's very much not what that message says. In fact, it doesn't appear to request anything of the release team at all. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681687: missing mime entry
Neil McGovern writes (Bug#681687: missing mime entry): As I understand it, there are still a number of issues with this approach (.desktop files do not contain enough information to get argument ordering correct in all cases, and it's far too late to start using a new auto-generation system this late in the cycle). Yes. I don't think it likely that the TC will want to overrule the Release Team's decision on this point. So I hereby propose the following TC resolution: 1. The Technical Committee agrees with Neil McGovern's analysis of the situation regarding evince's missing mime type entry. 2. If changes are desirable to our system for dealing with mime type entries and desktop files, including changes to policy or additional automation, these should be made via the usual development and policy amendment processes. It is now too late to do this for wheezy. 3. We do not disagree with the Release Team's assessment that the failure of the evince package to provide a mime type entry is a release critical bug. 4. We therefore decline to overrule the Release Team. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
