Bug#688772: gnome Depends network-manager-gnome
On Thu, 27 Sep 2012, Josselin Mouette wrote: Recommends are not enough to ensure that packages are installed, especially upon upgrades. For example regarding NM, we definitely *want* people who upgrade from squeeze to get NM installed. What is still missing is the technical rationale for this desire. If there were specific technical reason(s) why everyone who uses gnome should have NM installed, then it would weigh more for forcing NM to be installed if the gnome meta package was installed. From what I know so far, the primary rationale appears to be that gnome upstream considers NM part of gnome, and so it should be installed. I believe the CTTE addressed this rationale in §2 of the decision. We decided that unacceptable upgrade behavior outweighed this, as outlined in §5 and §6. Don Armstrong -- Sometimes I wish I could take back all my mistakes but then I think what if my mother could take back hers? -- a softer world #498 http://www.asofterworld.com/index.php?id=498 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688772: gnome Depends network-manager-gnome
On Fri, 05 Oct 2012, Ian Jackson wrote: From the IRC meeting: * ACTION: dondelelcaro to follow this up with the gnome maintainers to get a clear argument from the GNOME maintainers about why this *must* be a depends and not a recommends (dondelelcaro, 18:08:51) I don't know if this was followed up, but there still doesn't seem to be any such clear argument as far as I'm aware. I've followed up just now; had sort of been working out precisely what I would like to say. Is there anyone who is unhappy with the draft below ? I personally don't support 8, 9 and 10. [I'd do something like 8, but I believe it assumes too much bad faith on the part of the gnome maintainers.] Don Armstrong -- For a moment, nothing happened. Then, after a second or so, nothing continued to happen. -- Douglas Adams http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688772: gnome Depends network-manager-gnome
On Sat, 06 Oct 2012, Josselin Mouette wrote: The code that makes it actually *work* without NM installed was added for kFreeBSD – incidentally, by the same NM maintainer whose work has been repeatedly thrown into mud in the discussions. So, besides the important goal of a complete gnome experience, there's no other technical reason why NM must be installed? I disagree with the contents of §5 and §6. What in particular about §5 and §6? The release notes are here precisely for this kind of cases. This is certainly one of the possibilities that the CTTE (or a maintainer) could proscribe to resolve this problem; I wouldn't be averse to seeing an additional option proposed for a vote which did just this. The resolution also doesn’t mention which problems upgrading from a squeeze system without NM to a wheezy system with NM causes. It attempts to avoid overriding local manual configuration, but it isn't able to detect all cases where the user is using some other component or system to manage networking. For these reasons, I consider resolution #681834 to be driven by religious motives rather than technical ones, It's inflammatory to accuse others of having religious motives.[1] I personally have no interest in punishing, persecuting, or otherwise attacking the gnome maintainers or any other maintainer in Debian, and I would be surprised if all of the other members of the CTTE don't feel the same way. We all want Debian to be a technically excellent distribution which users want to use, and while we *often* have very different ideas on what that actually means, we have come to those ideas by honest means. and that it was conducted in haste. I'm not sure if I would consider a two month long decision process hasty, but since we seem to be doomed to readdress this issue again, lets please try to make all of the arguments and solutions out front so we can make a ideal decision. I have not said anything so far because the wording allows (and again, I thought this was intentional) for the compromise to move the dependency to the gnome package. I certainly didn't expect that to be a compromise position given the underlying logic of the decision, and I certainly would have liked to have addressed that point during the decision. I concede, however, that it would be possible to construe the decision this way. But if people from either side start questioning this compromise, I am afraid they are going to do a lot of harm to the project. We're all on the same side together. Don Armstrong 1: Additionally, the negative connotation is offensive to the many people who are involved in or use Debian who have religious beliefs. -- -tommorow is our permanent address and there they'll scarcely find us(if they do, we'll move away still further:into now -- e.e. cummings XXXIX _1 x 1_ http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688772: gnome Depends network-manager-gnome
On Sat, 06 Oct 2012, Josselin Mouette wrote: Le vendredi 05 octobre 2012 à 16:46 -0700, Don Armstrong a écrit : So, besides the important goal of a complete gnome experience, there's no other technical reason why NM must be installed? Why would there be? If for example, network-manager was so inextricably linked to gnome that it caused a particular kind of breakage such that it wasn't reasonable for anyone who wanted the other gnome bits not have it installed. * The affirmation that this will cause undesirable upgrade behavior is grossly exaggerated. From what I understand, nm and wicd are not capable of co-existing.[1] Furthermore, nm does not always catch that other systems (such as ifupdown) are configuring the interfaces, and may lead to broken behavior on upgrade (such as #656584 and #688355, just glancing at it). * The reason for the historical Recommends instead of Depends is not mentioned, while this history is used as an excuse for the whole decision. What was the reason? * The claim that NM can be replaced by another component without functionality loss is preposterous. Which functionality loss are we talking about? For simple configurations, it seems quite possible to replace NM with ifupdown with no loss of functionality. * The excuse of the squeeze→wheezy upgrade serves as a basis for a seemingly irrevocable decision that affects all future versions of GNOME metapackages. No CTTE decision is irrevocable. It's trivial to come back to the CTTE and get us to sunset a decision. I personally would also not have had a problem making this decision for the gnome meta packages only in wheezy, with some transition plan to be worked out in the future. Finally, in the future, please bring forward all of these concerns about what the CTTE is deciding during the actual decision process so we can address them. I don’t think what we do with GNOME affects autopkgtest, curl or hashalot. It affects the users of Debian, which is what we're here for. [I'm certainly not spending a nice Friday evening trying to sort this all out for my own personal use of Debian.[2]] Don Armstrong 1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681834#215 -- Live and learn or die and teach by example -- a softer world #625 http://www.asofterworld.com/index.php?id=625 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#573745: Call for votes on Python Maintainer Question
I call for a vote on the following resolution to #573745. === BEGIN RESOLUTION === The technical committee was asked in #573745 to consider replacing the current maintainer of python (Matthias Klose.) Multiple issues were presented at the time, including a lack of communication from the python maintainer, delays in uploads of new versions of python to unstable/experimental, and a lack of coordination with packaging helpers such as python-support, and python-central. 1. The communication between the python maintainer and other individuals affected by python packaging has not been ideal. These breakdowns appear to be rooted in an unfortunate feedback loop, of which all parties involved share some blame. a) On multiple occasions, inflammatory comments regarding the employment and/or motives of individuals involved in python have been made. b) The target(s) of these inflammatory comments then decline to respond to any messages from the offending parties, and also reduce public communication to other parties lest further hurtful and demotivating comments ensue. c) The lack of response is taken as further confirmation of motives/bias, and decreases the threshold for additional terse or inflammatory comments. This reinforces b, completing the loop. Neither the inflammatory comments, nor the lack of response are acceptable outcomes. 2. No mediation was attempted by a party respected by the involved parties until the pattern was well established and very difficult to overcome. In the future, everyone would be better served if similar issues were resolved in a nascent stage. 3. To resolve this issue, the committee has two options. It can either replace the maintainer, or it can decide not to replace the maintainer. Either decision will appear to validate one problematic behavior or the other. 4. All relevant and interested parties have been canvassed, via the -python list, to find what the possible teams of maintainers are for the python interpreter packages. See https://lists.debian.org/msgid-search/20120403083658.gb30...@upsilon.cc and the ensuing thread. Therefore, 5. The committee expresses its disappointment in the communication problems which have lead to this issue, and strongly suggests that all involved parties be as awesome to each other as possible. In the advent of communication failures or problems, we request that any involved party contact a third party (such as a member of the technical committee) to mediate. 6. The committee requests that all major changes in the python interpreter packages which will affect other packages in Debian be announced on the appropriate mailing lists before they take effect so they can be planned for and/or unplanned problems discussed. 7. A The committee resolves that the maintainer of python interpreter A packages in Debian is a team made up of members decided by (and A including) Sandro Tosi mo...@debian.org B The committee resolves that the maintainer of python interpreter B packages in Debian is a team made up of members decided by (and B including) Jakub Wilk jw...@debian.org C The committee declines to change the maintainer of the python C interpreter packages in Debian. C C 8. The committee requests that Matthias Klose consider adding C additional co-maintainers to the python interpreter package. === END RESOLUTION === I believe any of these options requires a simple majority (under §6.1.2) but I could see arguments that A or B requires a 3:1 majority (under §6.1.4). If it becomes necessary, we will adhere to the Secretary's interpretation. Don Armstrong -- I learned really early the difference between knowing the name of something and knowing something -- Richard Feynman What is Science Phys. Teach. 7(6) 1969 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#573745: Call for votes on Python Maintainer Question
On Thu, 04 Oct 2012, Don Armstrong wrote: I call for a vote on the following resolution to #573745. I vote C [AB] F. Don Armstrong -- Junkies were all knitted together in a loose global macrame, the intercontinental freemasonry of narcotics. -- Bruce Sterling, _Holy Fire_ p257 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#573745: Initial draft of resolution of the Python Maintainer question
I have prepared the draft as discussed; please find it below and in 57375_python_maintainer/dla_draft.txt in the git repository. If there are no changes, I would like to begin a call for votes in the next 48 hours or so, with options A, B and C as below, and F being further discussion. === BEGIN DRAFT === The technical committee was asked in #573745 to consider replacing the current maintainer of python (Matthias Klose.) Multiple issues were presented at the time, including a lack of communication from the python maintainer, delays in uploads of new versions of python to unstable/experimental, and a lack of coordination with packaging helpers such as python-support, and python-central. 1. The communication between the python maintainer and other individuals affected by python packaging has not been ideal. These breakdowns appear to be rooted in an unfortunate feedback loop, of which all parties involved share some blame. a) On multiple occasions, inflammatory comments regarding the employment and/or motives of individuals involved in python have been made. b) The target(s) of these inflammatory comments then decline to respond to any messages from the offending parties, and also reduce public communication to other parties lest further hurtful and demotivating comments ensue. c) The lack of response is taken as further confirmation of motives/bias, and decreases the threshold for additional terse or inflammatory comments. This reinforces b, completing the loop. Neither the inflammatory comments, nor the lack of response are acceptable outcomes. 2. No mediation was attempted by a party respected by the involved parties until the pattern was well established and very difficult to overcome. In the future, everyone would be better served if similar issues were resolved in a nascent stage. 3. To resolve this issue, the committee has two options. It can either replace the maintainer, or it can decide not to replace the maintainer. Either decision will appear to validate one problematic behavior or the other. Therefore, 4. The committee expresses its disappointment in the communication problems which have lead to this issue, and strongly suggests that all involved parties be as awesome to each other as possible. In the advent of communication failures or problems, we request that any involved party contact a third party (such as a member of the technical committee) to mediate. 5. The committee requests that all major changes in the python interpreter packages which will affect other packages in Debian be announced on the appropriate mailing lists before they take effect so they can be planned for and/or unplanned problems discussed. 6. A The committee resolves that the maintainer of python interpreter A packages in Debian is a team made up of members decided by (and A including) Sandro Tosi mo...@debian.org B The committee resolves that the maintainer of python interpreter B packages in Debian is a team made up of members decided by (and B including) Jakub Wilk jw...@debian.org C The committee declines to change the maintainer of the python C interpreter packages in Debian. C C 7. The committee requests that Matthias Klose consider adding C additional co-maintainers to the python interpreter package. END DRAFT Don Armstrong -- There is no form of lead-poisoning which more rapidly and thoroughly pervades the blood and bones and marrow than that which reaches the young author through mental contact with type metal. -- Oliver Wendell Holmes (Tilton 1947 p67) http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688867: X-DebBugs-Cc: xxx...@bugs.debian.org does not seem to work
Control: tag -1 wontfix Control: severity -1 minor Control: retitle -1 Debbugs doesn't obey X-Debbugs-CC to other bugs On Wed, 26 Sep 2012, Andreas Beckmann wrote: setting X-Debbugs-Cc to another bugs address nn@bugs.d.o does not seem to work. I just submitted bug #688861 against release.d.o, it included a patch that I considered important for the original bug that is to be worked around, so I set X-DebBugs-Cc: 640...@bugs.debian.org The confirmation mail said: As you requested using X-Debbugs-CC, your message was also forwarded to 640...@bugs.debian.org, pkg-nvidia-de...@lists.alioth.debian.org (after having been given a Bug report number, if it did not have one). But the message didn't show up in #640499, while followup from me got through, so I forwarded the mail again manually. Debbugs doesn't obey -Cc messages to other bugs, primarily to avoid mail loops. Don Armstrong -- Let us chat together a moment, my friend. There are still several hours until dawn, and I have the whole day to sleep. -- Count Orlock in _Nosferatu (1922)_ http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688867: Fwd: Re: [Reportbug-maint] Re: Bug#688867: Debbugs doesn't obey X-Debbugs-CC to other bugs
On Wed, 26 Sep 2012, Andreas Beckmann wrote: Control: tag -1 wontfix Nope sorry, I don't think reportbug should report it, but more rightly it's something that debbugs should report back in the Ack email. Right, I agree that debbugs should tell you that it's not forwarding to that address instead of silently not doing it. Don Armstrong -- [I]t's true that some of the most terrible things in the world are done by people who think, genuinely think, that they're doing it for the best, especially if there is some god involved. -- Terry Pratchett _Snuff_ p185 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#171870: Wrong versions fixed in bug 171870
This bug (171870) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#196310: Wrong versions fixed in bug 196310
This bug (196310) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#212490: Wrong versions fixed in bug 212490
This bug (212490) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#350369: Wrong versions fixed in bug 350369
This bug (350369) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#598737: Wrong versions fixed in bug 598737
This bug (598737) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651304: Wrong versions fixed in bug 651304
This bug (651304) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#657904: Wrong versions fixed in bug 657904
This bug (657904) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#495344: Wrong versions fixed in bug 495344
This bug (495344) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#658997: Wrong versions fixed in bug 658997
This bug (658997) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666525: Wrong versions fixed in bug 666525
This bug (666525) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666734: Wrong versions fixed in bug 666734
This bug (666734) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656586: Wrong versions fixed in bug 656586
This bug (656586) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#668515: Wrong versions fixed in bug 668515
This bug (668515) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#348679: Wrong versions fixed in bug 348679
This bug (348679) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670651: Wrong versions fixed in bug 670651
This bug (670651) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672160: Wrong versions fixed in bug 672160
This bug (672160) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672340: Wrong versions fixed in bug 672340
This bug (672340) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675691: Wrong versions fixed in bug 675691
This bug (675691) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675843: Wrong versions fixed in bug 675843
This bug (675843) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681963: Wrong versions fixed in bug 681963
This bug (681963) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682138: Wrong versions fixed in bug 682138
This bug (682138) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681979: Wrong versions fixed in bug 681979
This bug (681979) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682363: Wrong versions fixed in bug 682363
This bug (682363) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682538: Wrong versions fixed in bug 682538
This bug (682538) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682837: Wrong versions fixed in bug 682837
This bug (682837) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682957: Wrong versions fixed in bug 682957
This bug (682957) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684089: Wrong versions fixed in bug 684089
This bug (684089) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684713: Wrong versions fixed in bug 684713
This bug (684713) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685016: Wrong versions fixed in bug 685016
This bug (685016) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685060: Wrong versions fixed in bug 685060
This bug (685060) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685082: Wrong versions fixed in bug 685082
This bug (685082) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685204: Wrong versions fixed in bug 685204
This bug (685204) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685214: Wrong versions fixed in bug 685214
This bug (685214) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685723: Wrong versions fixed in bug 685723
This bug (685723) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686124: Wrong versions fixed in bug 686124
This bug (686124) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686193: Wrong versions fixed in bug 686193
This bug (686193) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686377: Wrong versions fixed in bug 686377
This bug (686377) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686524: Wrong versions fixed in bug 686524
This bug (686524) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686694: Wrong versions fixed in bug 686694
This bug (686694) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686835: Wrong versions fixed in bug 686835
This bug (686835) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686836: Wrong versions fixed in bug 686836
This bug (686836) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687212: Wrong versions fixed in bug 687212
This bug (687212) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687388: Wrong versions fixed in bug 687388
This bug (687388) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688215: Wrong versions fixed in bug 688215
This bug (688215) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688031: Wrong versions fixed in bug 688031
This bug (688031) had an incorrect found or fixed version which was caused by 686106. I have removed the incorrect found or fixed version, and added it back as a correct version. [This was the source of the internal messages which you have received previously.] If you have any questions, please contact ow...@bugs.debian.org Don Armstrong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688109: debbugs does not process mails sent to control@ in Cc:
tag 688109 unreproducible moreinfo thanks On Wed, 19 Sep 2012, Mike Gabriel wrote: Considering the ATM latest Git code of debbugs: http://git.donarmstrong.com/?p=debbugs.git;a=tree;h=445ef2a66a2f6e97760ca319ac3d919834178f0b;hb=445ef2a66a2f6e97760ca319ac3d919834178f0b With that code base, debbugs fails to process mails that have a control header and the control@ address is used in Cc: field of the mail. Debbugs processes both correctly, actually. (As you can see in this example.) This sounds like your MTA has a configuration problem. [Debbugs doesn't actually parse the mail to figure out where it was sent, anyway; you can Bcc: it messages if you want.] Don Armstrong -- NASCAR is a Yankee conspiracy to keep you all placated so the South won't rise again. -- http://www.questionablecontent.net/view.php?comic=327 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688109: debbugs does not process mails sent to control@ in Cc:
On Wed, 19 Sep 2012, Mike Gabriel wrote: So, this might indeed be related to postfix as MTA and the way the receive scripts handles incoming mails. Yeah, that's almost definitely what it is. I don't use postfix with debbugs, so I haven't corrected the readme for it. [Debian uses exim, and I've used sendmail and exim previously.] I will send a patch for the MTA Readme in a minute. Awesome, thanks. Don Armstrong -- Let us chat together a moment, my friend. There are still several hours until dawn, and I have the whole day to sleep. -- Count Orlock in _Nosferatu (1922)_ http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686106: dealing with slash appended to version number
On Tue, 18 Sep 2012, Michael Tokarev wrote: For example, such slash appending affected one of my bugs, 686524, -- after found 686524 foo control message the list of versions this bug if fond it has grow to one more version, foo/. Except that it won't. [You can try it.] foo has to be a valid source version for this to happen. [Basically, because of the bug in dak, foo was reported to the bts as the source name with a version '', so it resolved versions correctly.] So, it isn't possible to remove such tagging, and more, a valid command (but maybe with a bogus version number) is int parsed correctly. The command is parsed correctly; 1.1.2+dfsg-1/ isn't a valid version, so doesn't pass the regex for the command, and is ignored. Don Armstrong -- It has always been Debian's philosophy in the past to stick to what makes sense, regardless of what crack the rest of the universe is smoking. -- Andrew Suffield in 20030403211305.gd29...@doc.ic.ac.uk http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525821: [PATCH] support having the same document id in different packages in the same source
This is a multi-part message in MIME format.
--1.7.10.4
Content-Type: text/plain; charset=UTF-8; format=fixed
Content-Transfer-Encoding: 8bit
---
debian/changelog |2 ++
dh_installdocs | 35 ++-
2 files changed, 32 insertions(+), 5 deletions(-)
--1.7.10.4
Content-Type: text/x-patch;
name=0001-support-having-the-same-document-id-in-different-pac.patch
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment;
filename=0001-support-having-the-same-document-id-in-different-pac.patch
diff --git a/debian/changelog b/debian/changelog
index 2ff9bfa..6eed10d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -14,6 +14,8 @@ debhelper (9.20120609) UNRELEASED; urgency=low
distutils installed. Closes: #683557
* dh_icons: Improve documentation. Closes: #684895
* Improve -X documentation. Closes: #686696
+ * Support installing multiple doc-base files which use the same doc-id.
+(Closes: #525821)
-- Joey Hess jo...@debian.org Thu, 05 Jul 2012 08:51:07 -0600
diff --git a/dh_installdocs b/dh_installdocs
index 104b796..bb09ee3 100755
--- a/dh_installdocs
+++ b/dh_installdocs
@@ -54,12 +54,17 @@ and FTODO files will be installed as FTODO.Debian in
non-native packages.
Installed as doc-base control files. Note that the doc-id will be
determined from the BDocument: entry in the doc-base control file in
-question.
+question. In the event that multiple doc-base files in a single source
+package share the same doc-id, they will be installed to
+usr/share/doc-base/package instead of usr/share/doc-base/doc-id.
=item debian/Ipackage.doc-base.*
-If your package needs to register more than one document, you need multiple
-doc-base files, and can name them like this.
+If your package needs to register more than one document, you need
+multiple doc-base files, and can name them like this. In the event
+that multiple doc-base files of this style in a single source package
+share the same doc-id, they will be installed to
+usr/share/doc-base/package-* instead of usr/share/doc-base/doc-id.
=back
@@ -298,9 +303,29 @@ foreach my $package (@{$dh{DOPACKAGES}}) {
doit(install,-g,0,-o,0,-d,$tmp/usr/share/doc-base/);
}
}
+ # check for duplicate document ids
+ my %used_doc_ids;
+ for my $fn (keys %doc_ids) {
+ $used_doc_ids{$doc_ids{$fn}}++;
+ }
foreach my $fn (keys %doc_ids) {
- doit(install,-g,0,-o,0,-m644,-p,debian/$fn,
-$tmp/usr/share/doc-base/$doc_ids{$fn});
+ # if this document ID is duplicated, we will install
+ # to usr/share/doc-base/packagename instead of
+ # usr/share/doc-base/doc_id. To allow for multiple
+ # conflicting doc-bases in a single package, we will
+ # install to usr/share/doc-base/packagename-extrabits
+ # if the doc-base file is
+ # packagename.doc-base.extrabits
+ if ($used_doc_ids{$doc_ids{$fn}}1) {
+ my $fn_no_docbase = $fn;
+ $fn_no_docbase =~ s/\.doc-base(?:\.(.*))?/
+ if (defined $1 and length $1) {-$1} else {''}/xe;
+ doit(install,-g,0,-o,0,-m644,-p,debian/$fn,
+$tmp/usr/share/doc-base/$fn_no_docbase);
+ } else {
+ doit(install,-g,0,-o,0,-m644,-p,debian/$fn,
+$tmp/usr/share/doc-base/$doc_ids{$fn});
+ }
}
}
--1.7.10.4--
Cc:
Bcc:
Subject:
Reply-To:
Don Armstrong
--
Quite the contrary; they *love* collateral damage. If they can make
you miserable enough, maybe you'll stop using email entirely. Once
enough people do that, then there'll be no legitimate reason left for
anyone to run an SMTP server, and the spam problem will be solved.
-- Craig Dickson in 20020909231134.GA18917@linux700.localnet
http://www.donarmstrong.com http://rzlab.ucr.edu
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686106: 1.2.3-4/ Actually caused by change in dak
Control: -1 tag confirmed pending This change was caused by a change in dak; I'm communicating with Ansgar about whether that change was intentional or not. [I will hack around it temporarily too.] Don Armstrong -- You have many years to live--do things you will be proud to remember when you are old. -- Shinka proverb. (John Brunner _Stand On Zanzibar_ p413) http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684817: lilypond: FTBFS: (process:29483): Pango-WARNING **: error opening config file '/root/.pangorc': Permission denied
On Sun, 16 Sep 2012, Lucas Nussbaum wrote: On 12/09/12 at 09:28 -0700, Don Armstrong wrote: On Wed, 12 Sep 2012, Lucas Nussbaum wrote: Just a note to say that I can still reproduce this. Can you please provide a backtrace and/or a coredump? [I believe that the build currently has them turned on, so it should just be a matter of pulling them out of sbuild.] I'm a bit low on free time. Do you want access to an amazon instance to get it yourself? Me too, but that might be best. [For those following, I'm going to followup via private mail.] Don Armstrong -- That is why I am still tyrant of [Ankh-Morpork]. The way to retain power, I have always thought, is to ensure the absolute unthinkability of oneself not being there. -- Terry Pratchett _Unseen Academicals_ p391 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684817: lilypond: FTBFS: (process:29483): Pango-WARNING **: error opening config file '/root/.pangorc': Permission denied
On Wed, 12 Sep 2012, Lucas Nussbaum wrote: Just a note to say that I can still reproduce this. Can you please provide a backtrace and/or a coredump? [I believe that the build currently has them turned on, so it should just be a matter of pulling them out of sbuild.] (Does this happen anywhere else? Or is it just in Amazon's farm?) Don Armstrong -- The computer allows you to make mistakes faster than any other invention, with the possible exception of handguns and tequila -- Mitch Ratcliffe http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681834: Call for votes on network-manager, gnome
On Tue, 11 Sep 2012, Ian Jackson wrote: Russ Allbery writes (Re: Bug#681834: network-manager, gnome, Recommends vs Depends): Here's what I now have: I asked for comments and no-one had any. So I hereby call for votes on the resolution below. The options are: A. Recommends not Depends (overrule maintainers). 3:1 required. F. Further Discussion. I vote AF. Don Armstrong -- life's not a paragraph And death i think is no parenthesis -- e.e. cummings Four VII _is 5_ http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686928: Makefile rule to fix failing templates installation
On Fri, 07 Sep 2012, Mike Gabriel wrote: the last two lines in the Makefile have to be replaced by these: # install the templates $(foreach dir, $(wildcard templates/*/*), $(install_exec) -d $(templates_dir)/$(patsubst templates/%,%,$(dir)) ; ) $(foreach tmpl, $(wildcard templates/*/*/*.tmpl), $(install_data) $(tmpl) $(templates_dir)/$(patsubst templates/%,%,$(tmpl)) ; ) Thanks for the report; I've fixed this in @f11e4. The git repository is available on bugs.debian.org/debbugs-source/ or github or http://git.donarmstrong.com/debbugs.git; feel free to submit patches to it. Don Armstrong -- I may not have gone where I intended to go, but I think I have ended up where I needed to be. -- Douglas Adams _The Long Dark Tea-Time of the Soul_ http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686940: Patch against pkgindex.cgi, fixes internal webserver error
Control: tag -1 fixed Control: thanks On Fri, 07 Sep 2012, Mike Gabriel wrote: attached to this mail you find a patch against pkgindex.cgi. The version in the package of the version named above is broken and let's apache2 react with an internal error. This was fixed a while ago in ed6a5cd2. I haven't released a new experimental version which resolves this issue, however. Don Armstrong -- Physics is like sex. Sure, it may give some practical results, but that's not why we do it. -- Richard Feynman http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685795: Possibly inviting a new TC member
Below, please find the current draft of the call for nominations. I'd like to send this e-mail out on Monday the 10th, so please make any changes in the git repository [685795_new_member/call_for_nominations.txt] (or suggest them in a response, and I will incorporate them.): To: debian-devel-annou...@lists.debian.org Subject: Call for nominations for technical committee seat First and foremost, the technical committee would like to thank Manoj Srivastava for serving on the committee in addition to his many other services to Debian. With his resignation from the technical committee,[1] there is currently one empty seat which can be filled. To fill this seat, we are soliciting nominations. To nominate yourself or someone else, please send e-mail to debian-ctte-priv...@debian.org with the subject CTTE Nomination of loginname, where loginname is the nominee's Debian account login.[2] Please let us know in the body of the e-mail why the nominee would be a good fit for the committee, specifically instances where the nominee was able to help resolve disagreements, both technical and non-technical, which you were a party to or observer of. We anticipate starting our selection process on or about the first of October. After the selection, the committee will then recommend a nominee to the project leader, who may appoint the nominee (§6.2). 1: http://lists.debian.org/msgid-search/502808cd.3090...@golden-gryphon.com 2: See http://db.debian.org/ if you need to look the login up Don Armstrong -- Religion is religion, however you wrap it, and like Quell says, a preoccupation with the next world clearly signals an inability to cope credibly with this one. -- Richard K. Morgan Broken Angels p65 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686788: lilypond: New upstream version available: 2.16.0
On Wed, 05 Sep 2012, Przemysław Pawełczyk wrote: it would be really nice to have LilyPond 2.16 in Wheezy, as it is the current stable version (since August 24, 2012). Lilypond 2.16 won't make it into wheezy, as wheezy is frozen. I will be making an experimental upload soon, and will probably backport 2.16 to wheezy once wheezy has released. Don Armstrong -- [I]t's true that some of the most terrible things in the world are done by people who think, genuinely think, that they're doing it for the best, especially if there is some god involved. -- Terry Pratchett _Snuff_ p185 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686788: lilypond: New upstream version available: 2.16.0
On Thu, 06 Sep 2012, Przemysław Pawełczyk wrote: Lilypond 2.16 has many engraving errors fixed and lot of things improved. And it didn't get a stable mark by chance. I don't see a good reason to punish Debian users and provide ~1.5y old version (assuming release in November, but I guess we'll have to wait till 2013 rather). Except that we've been frozen for multiple months now, and texlive is already in the archive. Regardless, before I even consider trying to get the release team to allow an upload to testing, I have to get the package into shape for experimental, and lots of people have to test it. Don Armstrong -- Americans can always be counted on to do the right thing, after they have exhausted all other possibilities. -- W. Churchill http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675971: Bug#682010: Call for votes on CELT in Mumble
With the vote of Andreas, the outcome is no longer in doubt. Therefore, the Technical Committee resolves: Context: 1. The questions surrounding the codecs in mumble, especially celt, have been referred to the Technical Committee. 2. The mumble maintainers have stated their willingness to follow our advice (Constitution 6.1(5)). This may or may not amount to a delegation to us of the decision (6.1(3)) but in any case we merely need to state our reasoning and conclusions and are not being asked to overrule the maintainer. Release Critical status of celt 0.7.1 in mumble: 3. mumble is a useful and fairly widely-used voice chat program. 4. Distributions of mumble (from other distros and upstream) currently implement the celt 0.7.1 codec as a baseline. It does not appear to the TC that (in wheezy) the provision of any other codec obviates the need for mumble to support celt 0.7.1. mumble with celt 0.7.1 has been tested and found to interoperate properly with nearly all other mumble versions. 5. Consequently, we consider the lack of celt 0.7.1 support in mumble a release-critical bug. Security risks from celt 0.7.1: 6. While the upstream security support situation for celt 0.7.1 is not ideal, the TC does not consider that the security risks associated with celt 0.7.1 in mumble are intolerable. 7. The Debian Security Team have stated that they have no objection to including celt 0.7.1 in mumble in wheezy. 8. Consequently, mumble should remain in wheezy with celt 0.7.1 (the alternative being to remove mumble as unfit for release). Packaging approach: 9. There are no other packages intended for wheezy which ought to want this codec. 10. Providing separate celt library in wheezy is undesirable because it might promote the use of a codec which we are planning to retire in the medium to long term. 11. While embedded code copies are in general to be avoided because lead to proliferation of multiple versions, that therefore does not apply in this case. 12. The upstream mumble source already contemplates building with various embedded versions of celt. 13. There is no reason to support any other version of celt in mumble. 14. Consequently, the mumble source package should be configured to use an embedded copy of celt 0.7.1. (If necessary the embedded copy of celt in the source package should be updated to the actual 0.7.1.) We therefore recommend that: 15. The mumble maintainers, with appropriate help from other interested parties, should prepare an upload of mumble for wheezy with - embedded celt 0.7.1 enabled - no other version of celt enabled - whatever other release-critical bugfixes they consider relevant (subject to any appropriate discussion with the release team as necessary) - closing #675971. 16. #675971 should remain at an RC severity, be untagged wontfix, and maintained open until it is closed as discussed above. 17. If the release team are content with the other changes in the new mumble package, the new version should be unblocked to propagate into wheezy. 18. After that propagation, the separate celt packages should be removed from wheezy. This should be requested by the celt maintainer filing a removal bug in the normal way, after mumble with embedded celt 0.7.1 has propagated to wheezy. Don Armstrong -- I learned really early the difference between knowing the name of something and knowing something -- Richard Feynman What is Science Phys. Teach. 7(6) 1969 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683616: www.debian.org: Please document usage of usertags on bugs pages
reassign 683616 bugs.debian.org forcemerge 351746 683616 thanks On Thu, 02 Aug 2012, Charles Plessy wrote: Le Thu, Aug 02, 2012 at 10:37:37AM +0200, Alexander Reichle-Schmehl a écrit : Package: www.debian.org It seems that the usage of usertags is not documented anywhere on www.debian.org/Bugs/. At least http://www.debian.org/Bugs/server-control should mention, that one can set them by specifing user email (if different from sender) and setting them via usertag bugnumber tag. Hello everybody, not sure in which direction to merge, but there is a similar request reported to the bugs.debian.org pseudopackage. http://bugs.debian.org/351746#69 Yeah, this really just needs someone to sit down and actually write the documentation, unfortunately. It's on my todo list. Don Armstrong -- Of course, there are cases where only a rare individual will have the vision to perceive a system which governs many people's lives; a system which had never before even been recognized as a system; then such people often devote their lives to convincing other people that the system really is there and that it aught to be exited from. -- Douglas R. Hofstadter _Gödel Escher Bach. Eternal Golden Braid_ http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682010: Call for votes on CELT in Mumble
On Fri, 24 Aug 2012, Ian Jackson wrote: I previously proposed this. I have added a sentence to para 4 about the results of Chris's interop tests and fixed the paragraph numbering. I'm calling for a vote. The options are: A Recommend to mumble maintainers to support bundled celt 0.7.1 F Further discussion I vote AF. Don Armstrong -- Sentenced to two years hard labor (for sodomy), Oscar Wilde stood handcuffed in driving rain waiting for transport to prison. If this is the way Queen Victoria treats her prisoners, he remarked, she doesn't deserve to have any. http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684679: RFS: nullmailer/1:1.11-2 (security bugfix upload request)
On Sun, 12 Aug 2012, Nick Leverton wrote: * New upstream release diff -Nru nullmailer-1.11/debian/postinst nullmailer-1.11/debian/postinst --- nullmailer-1.11/debian/postinst 2012-05-16 08:25:36.0 +0100 +++ nullmailer-1.11/debian/postinst 2012-08-12 20:23:46.0 +0100 @@ -24,10 +24,14 @@ fi db_get nullmailer/relayhost + # securely create nullmailer/remotes with mode 0600 + R=$( tempfile -d /etc/nullmailer -p nullm ) echo $RET | sed -r -e ':a s/(\[[^]:]*):/\1=/; ta' \ -e 's/[[:space:]]*:[[:space:]]*/\n/g' \ -e ':b s/(\[[^]=]*)=/\1:/; tb' \ - -e 's/[][]//g' /etc/nullmailer/remotes + -e 's/[][]//g' $R + chown mail:mail $R + mv $R /etc/nullmailer/remotes db_get nullmailer/adminaddr if [ $RET ]; then If bartm is unable to upload this, I will do it. However, you need to first check that /etc/nullmailer/remotes is a regular file, as it would be a perfectly reasonable configuration to have replaced /etc/nullmailer/remotes with a symlink. Secondly, you really should only do the replacement if /etc/nullmailer/remotes is world readable; otherwise you should assume that the administrator has modified things (for example, running nullmailer as an entirely different user). Don Armstrong -- He no longer wished to be dead. At the same time, it cannot be said that he was glad to be alive. But at least he did not resent it. He was alive, and the stubbornness of this fact had little by little begun to fascinate him -- as if he had managed to outlive himself, as if he were somehow living a posthumous life. -- Paul Auster _City of Glass_ http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685264: Control: pseudoheader does not work on -done@ messages
severity 685264 wishlist retitle 685264 allow control pseudoheader to work with -done@ reassign 685264 debbugs thanks On Sun, 19 Aug 2012, Andreas Beckmann wrote: is there a reason the Control: pseudoheader does not work on nn-done@b.d.o messages? Control: only works for nnn@b.d.o and submit@b.d.o currently. Other things may be supported in the future, but most of those other messages have side effects. Don Armstrong -- I really wanted to talk to her. I just couldn't find an algorithm that fit. -- Peter Watts _Blindsight_ p294 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684817: lilypond: FTBFS: (process:29483): Pango-WARNING **: error opening config file '/root/.pangorc': Permission denied
tag 684817 unreproducible retitle 684817 segfault in lilypond thanks On Tue, 14 Aug 2012, Lucas Nussbaum wrote: During a rebuild of all packages in *wheezy*, your package failed to build on amd64. I've rebuild this on wheezy on amd64. The actual error is a segfault in lilypond (or something which lilypond is calling) which I am unable to reproduce in a wheezy pbuilder chroot (nor have I seen this particular error before.) The pango warning is just a red herring; it happens all over the place and is a bug in pango. If you are able to reproduce this build failure, please send me a coredump and a backtrace so I have a chance of tracking down what is happening. If it doesn't reproduce, it should be downgraded, but I'd like to see a backtrace if you can possibly get one (and it doesn't look like stack smashing.) (process:29483): Pango-WARNING **: error opening config file '/root/.pangorc': Permission denied [century_schoolbook_l_bold_3.865234375Segmentation fault (core dumped) command failed: /«PKGBUILDDIR»/out/bin/lilypond -dbackend=eps --formats=ps,png,pdf -djob-count=10 -dinclude-eps-fonts -dgs-load-fonts --header=doctitle --header=doctitlecs --header=doctitlede --header=doctitlees --header=doctitlefr --header=doctitlehu --header=doctitleit --header=doctitleja --header=doctitlenl --header=doctitlezh --header=texidoc --header=texidoccs --header=texidocde --header=texidoces --header=texidocfr --header=texidochu --header=texidocit --header=texidocja --header=texidocnl --header=texidoczh -dcheck-internal-types -ddump-signatures -danti-alias-factor=2 -I /«PKGBUILDDIR»/out/lybook-db -I /«PKGBUILDDIR»/Documentation/de -I /«PKGBUILDDIR»/Documentation/de -I /«PKGBUILDDIR»/Documentation/de/out-www -I /«PKGBUILDDIR»/input -I /«PKGBUILDDIR»/Documentation -I /«PKGBUILDDIR»/Documentation/snippets -I /«PKGBUILDDIR»/input/regression -I /«PKGBUILDDIR»/Documentation/included -I /«PKGBUILDDIR»/mf/out -I /«PKGBUILDDIR»/mf/out -I /«PKGBUILDDIR»/Documentation/pictures -I /«PKGBUILDDIR»/Documentation/pictures/out-www -I /«PKGBUILDDIR»/Documentation/de/included -I /«PKGBUILDDIR»/Documentation -I /«PKGBUILDDIR»/Documentation/out-www --formats=eps --verbose -deps-box-padding=3.00 -dread-file-list -dno-strip-output-dir /«PKGBUILDDIR»/out/lybook-db/snippet-names-6294678324033531697.ly Child returned 139 lilypond-book.py (GNU LilyPond) 2.14.2 make[4]: *** [out-www/notation.texi] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/08/14/lilypond_2.14.2-3_wheezy.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. Don Armstrong -- It's brief and bright, dear children; bright and brief. Delight's the lightning; the long thunder's grief. -- John Frederick Nims Poetry in Motion p31 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681783: Call for votes on Recommends and metapackages
On Tue, 14 Aug 2012, Ian Jackson wrote: I'm calling for a vote on my proposal for a disposal of #681783, re Recommends and particularly metapackages. The options are: A Recommends policy is correct, clarification would be useful F Further discussion. I vote AF. Don Armstrong -- Some pirates achieved immortality by great deeds of cruelty or daring-do. Some achieved immortality by amassing great wealth. But the captain had long ago decided that he would, on the whole, prefer to achieve immortality by not dying. -- Terry Pratchet _The Color of Magic_ http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681687: Call for votes on evince MIME entry
On Tue, 07 Aug 2012, Ian Jackson wrote: I'm calling for votes on the following proposal. There are three options - two positive versions, and FD. In summary A. Do not overrule release team. It is too late for automation. B. Do not overrule release team. Defer to them on automation. F. Further Discussion. I vote BAF. Don Armstrong -- The major difference between a thing that might go wrong and a thing that cannot possibly go wrong is that when a thing that cannot possibly go wrong goes wrong it usually turns out to be impossible to get at or repair. -- Douglas Adams _Mostly Harmless_ http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684113: debbugs: marked as done messages are a pain to read
Control: retitle -1 put -done message first for all messages Control: reassign -1 debbugs Control: severity -1 wishlist Control: clone -1 -2 Control: retitle -2 send -done messages from submitter On Tue, 07 Aug 2012, Raphaël Hertzog wrote: What really matters to me is that we can see the bug closure mail as close to the top as possible. Thus you should probably reword the initial part because it takes close to a full screen in my mutt setup. What you are asking is for the -done messages to look like the messages we currently send to submitters; that's possible. Another thing that bothers me, is that those messages are sent from Debian Bug Tracking System ow...@bugs.debian.org effectively hiding from my mailer the person who sent the -done mail (and thus my searches by sender will not find those mails). It would thus be nice if the mail could keep the From of the -done mail. Probably, yeah. Don Armstrong -- Clean living is less fun and you wind up feeling stupid when you still die. -- a softer world #489 http://www.asofterworld.com/index.php?id=489 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681493: any followup on pet.debian.net pseudopackage?
On Mon, 06 Aug 2012, Daniel Kahn Gillmor wrote: what's the status with getting pet.debian.net as an official pseudopackage on the BTS? Was just waiting for some bugs, which have appeared now. [And a prod. ;-)] However, as I'm glancing at it now, I need a short description for the pet.debian.net pseudopackage. See http://bugs.debian.org/pseudopackages/pseudo-packages.description for some examples. Don Armstrong -- If god is always watching over us who's driving? -- a softer world #487 http://www.asofterworld.com/index.php?id=487 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683024: wamerican: /etc/dictionaries-common/words may be a broken symlink
Control: retitle -1 /etc/dictionaries-common/words may be a broken symlink Control: tag -1 moreinfo Please provide the output from the following commands: dpkg -l dictionaries-common wamerican; dpkg-divert --list /usr/share/dict/words ls -al /usr/share/dict/; Don Armstrong -- Clean living is less fun and you wind up feeling stupid when you still die. -- a softer world #489 http://www.asofterworld.com/index.php?id=489 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683171: bugs.debian.org: Greylisting delays too many messages, please keep auto whitelist for a longer period of time
On Mon, 30 Jul 2012, Andreas Metzler wrote: This should not make a difference. At least it does not in normal greylisting setups. There are two separate things happening here; the acceptance of mail after a delay for the helo,rcpt,from triple, and the auto white listing of ip addresses. (postgrey(1): client IP address will be automatically whitelisted if [...] At least 5 successfull attempts of delivering a mail). Yes, we start at 10, and expire at the default of 35 days. You're only showing a handful of deliveries. [And we've recently switched hosts, so you'll be greylisted until you get to the limit on the new host.] Don Armstrong -- There's no problem so large it can't be solved by killing the user off, deleting their files, closing their account and reporting their REAL earnings to the IRS. -- The B.O.F.H.. http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682010: Interoperability with speex patch
One of the possible technical solutions to #682010 is the use of the speex codex as a default. The CTTE would like to see the packages which incorporate this solution and a table of client/server compatibility so we can choose which solution is most desirable. If you (Ron) could work with Nicos to prepare such packages and test them, ideally within two weeks (say, before the 13th of August), that would be greatly appreciated. Don Armstrong -- Leukocyte... I am your father. -- R. Stevens http://www.dieselsweeties.com/archive.php?s=1546 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682010: Interoperability with speex patch
On Mon, 30 Jul 2012, Don Armstrong wrote: One of the possible technical solutions to #682010 is the use of the speex codex as a default. The CTTE would like to see the packages which incorporate this solution and a table of client/server compatibility so we can choose which solution is most desirable. If you (Ron) could work with Nicos to prepare such packages and test them, ideally within two weeks (say, before the 13th of August), that would be greatly appreciated. Err, that should be work with Thorvald, sorry. Don Armstrong -- Given that the odds of a miracle are one in one million, and events which could be a miracle happen every second, the odds of not seeing a miracle in a month are less than 8 in 100. Clearly miracles are not all that miraculous. http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682722: bts Internal Server Error
Package: bugs.debian.org Severity: normal On Sat, 21 Jul 2012, Bart Martens wrote: A few seconds ago I got an Internal Server Error for this url: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682035;users=sponsorship-reque...@packages.debian.org Ok; not sure why this is happening, but I'll check it out. Don Armstrong -- CNN/Reuters: News reports have filtered out early this morning that US forces have swooped on an Iraqi Primary School and detained 6th Grade teacher Mohammed Al-Hazar. Sources indicate that, when arrested, Al-Hazar was in possession of a ruler, a protractor, a set square and a calculator. US President George W Bush argued that this was clear and overwhelming evidence that Iraq indeed possessed weapons of math instruction. http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675971: Bug#682010: [mumble] Communication failures due to CELT codec library removal
On Mon, 23 Jul 2012, Chris Knadle wrote: On Monday, July 23, 2012 10:34:28, Ian Jackson wrote: Of these 2. would seem to be the best option. I agree. [...] I believe in order to actually evaluate any of these solutions, someone is going to have to prepare binaries, and do an table showing the tested (not theoretical) compatibility of with multiple different clients (and servers?) to their solution's server and client. I propose that whoever wants to see a particular solution actually sit down and do the work for their particular solution, with sources, binaries, interdiffs, and compatibility table conveniently available in some public location. FWICT, Ron and Thorvald feel that speex will be their favored solution and will have a version of it available no sooner than a week from now, so there's at least a week for other people to do the work. [And if no one wants to do the work for a solution, then there's no point in even considering it.] Feel free to coordinate using this bug or privately, but I don't believe that further theoretical discussions of client/server compatibility are useful. [At least, I'm personally not going to vote to override a maintainer without an actual tested solution that is technically superior, and I suspect that other CTTE members share that opinion.] Don Armstrong -- Frankly, if ignoring inane opinions and noisy people and not flaming them to crisp is bad behavior, I have not yet achieved a state of nirvana. -- Manoj Srivastava in 87n04pzhmh@glaurung.internal.golden-gryphon.com http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682010: [mumble] Communication failures due to CELT codec library removal
summary 682010 0 forwarded 682010 http://git.donarmstrong.com/?p=debian-ctte.git;a=blob;f=682010_celt_and_mumble/682010_celt_and_mumble.org thanks * Issue #682010 ** Mumble in unstable/testing currently cannot interact with other clients and servers + Due to the removal of celt 0.7.1 (?) * Possible solutions ** Include celt 0.7.1 as a convenience copy + Security Issues with embedded copies + Unspecified possible security issues ** Upload a celt 0.7.1 package + No maintainer desires to deal with this (apparently?) + Unspecified possible security issues ** Use speex instead + Server (and clients?) do not select speex as an option unless bandwidth is low ** Use only opus + Not yet (?) released upstream + May not communicate with non-opus clients * Open questions ** Can speex be made to be an option? ** Is a convenience copy acceptable, assuming mumble is the only thing with it? ** What are the other clients that we want to make sure the mumble servers can communicate with? * Involved parties ** chris.kna...@coredump.us, Ron r...@debian.org, 682...@bugs.debian.org, Nicos Gollan gt...@spearhead.de, Thorvald Natvig thorv...@natvig.com The above is my current understanding of this bug. Please correct anything that I've gotten wrong or misunderstood or missed. Don Armstrong -- If I had a letter, sealed it in a locked vault and hid the vault somewhere in New York. Then told you to read the letter, thats not security, thats obscurity. If I made a letter, sealed it in a vault, gave you the blueprints of the vault, the combinations of 1000 other vaults, access to the best lock smiths in the world, then told you to read the letter, and you still can't, thats security. -- Bruce Schneier http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681419: Alternative dependencies on non-free packages in main
forward 681419 http://git.donarmstrong.com/?p=debian-ctte.git;a=blob;f=681419_free_non_free_dependencies/681419_free_non_free_dependencies.org thanks I've been going through and doing summaries for the current status of the CTTE bugs; this is my understanding of where we are for 681419: * Issue http://bugs.debian.org/681419 ** May packages in main have a Depends: foo | foo-nonfree * Possible Solutions ** Yes + Possibility of automatically pulling in non-free during some dependency resolution ** Yes, with caveats + Under no circumstances should non-free be pulled in automatically *** Automatic: avoid in Release file + http://lists.debian.org/msgid-search/20120717083004.GB21400@frosties *** Only virtual packages ** No + Lots of packages will be insta-buggy * Open Questions ** How many total dependencies are there? (We're only interested in Depends or Recommends for this purpose, not Suggests.) *** 79 ** Are all of those dependencies alternative dependencies of the form: Depends: foo | foo-nonfree or are there other cases? *** Yes, save for two bugs ** Are any of these dependencies versioned? *** No ** What do packages already in the archive do? *** Already some alternative Depends: and Recommends: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681419#100 ** Do any packages pull in non-free automatically already? *** Apparently, no http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681419#100 * Involved Parties ** debian-pol...@lists.debian.org Don Armstrong -- Live and learn or die and teach by example -- a softer world #625 http://www.asofterworld.com/index.php?id=625 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682010: [mumble] Communication failures due to CELT codec library removal
I've updated the summary with the suggested changes (at the end). On Sat, 21 Jul 2012, Ron wrote: I think that's roughly right. If there's anything more people need clarified or answered, just ask. [...] And I'm still not quite clear what his objection was, because the response I got was: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682010#124 The objection is that the issue has been raised before the CTTE, so it needs to be resolved first before action is taken. From what I understand now, while we could fix up some of the RC issues with the client/server in testing and unstable, we'd need yet another upload of mumble to unstable with propagation to testing in order to actually fix the client inter-operation bug. From what I can tell now, the ideal solution is to wait until Thorvald has a chance to enable speex for all bandwidths. If that is impractical/impossible then we get to choose between a convenience copy of celt, not releasing mumble, or releasing with opus. Is that the understanding of everyone else? * Issue http://bugs.debian.org/682010 http://bugs.debian.org/675971 ** Mumble in unstable/testing currently cannot interact with other clients and servers + Due to the removal of celt http://bugs.debian.org/676592 and disabling of celt compilation options + Mumble dropping speex in unstable and speex not being selected at higher bandwidths + http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675971#51 + Interoperation: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675971#61 * Possible solutions ** Use speex instead + Server (and clients?) do not select speex as an option unless bandwidth is low + May be resolved by Thorvald Natvig with a hack + Clients cannot currently report speex version during codec selection process + Requires code modification for selection process and re-enabling speex ** Include celt 0.7.1 as a convenience copy + Security Issues with embedded copies + Mitigated as mumble would have the only copy + Unspecified possible security issues + Potential remote crasher + -348 is currently this way in testing ** Do not release with mumble + Unsatisfactory to users of mumble ** Upload a celt 0.7.1 package + No maintainer desires to deal with this (apparently?) + Upstream do not wish additional packages to use celt; wish transition to opus + Unspecified possible security issues + Proliferates celt library downstream + Deprecated upstream ** Use only opus + Opus itself released upstream + Code to enable opus in mumble has not been released + Will not communicate with non-opus clients or servers + Unlikely to be RM acceptable at this point * Open questions ** Can speex be made to be an option? + Thorvald thinks so; no patch as of yet (off for a week?) ** Is a convenience copy acceptable, assuming mumble is the only thing with it? + Possible remote crasher bug is the primary objection to allowing this ** What are the other clients that we want to make sure the mumble servers can communicate with? |+--++---+---| | client/server | Deb 1.2.2-6+squeeze1 | Deb 1.2.3-2+b2 | Deb 348 | Deb 349 | |+--++---+---| | Deb. Client 348 | Yes | Yes| Yes | Yes | | Deb. Client 349 | No | No | Yes | Yes | | Win. Client 1.2.3a | Yes | Yes| Yes | Yes | | Win. Client 361 | Yes | Yes| Yes | Yes | | Mac Client 1.2.2 | Yes | Yes| Yes | Yes | |+--++---+---| * Resolutions * Involved parties ** chris.kna...@coredump.us, Ron r...@debian.org, 682...@bugs.debian.org, 675...@bugs.debian.org, Nicos Gollan gt...@spearhead.de, Thorvald Natvig thorv...@natvig.com Don Armstrong -- Who is thinking this? I am. -- Greg Egan _Diaspora_ p38 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#544192: Please add debian-live pseudo package
outlook 544192 Need the proper name of the pseudopackage; debian-live is not ideal. live.debian.org or live.debian.net? thanks On Sat, 21 Jul 2012, Daniel Baumann wrote: after re-reading again trough this bug as i do every year that's passing by.. as the tag moreinfo suggests, what exactely is left open that you require to know from us in order to be able to create the pseudo package? The last time I touched this, no one had decided what the name of the actual pseudo package was going to be. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544192#25 Don Armstrong -- We must realize that today's Establishment is the New George III. Whether it will continue to adhere to his tactics, we do not know. If it does, the redress, honored in tradition, is also revolution. -- William O. Douglas _Points of Rebellion_ http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682281: Tag wontfix doesn't display the sad face icon correctly
On Fri, 20 Jul 2012, Félix Arreola Rodríguez wrote: I love the Debian BTS, I always like to walk around and read the bugs and tags. But recently, the sad face icon (associated with the wontfix tag) doesn't display correctly. I mean, with the tag fixed-version it displays a happy face, but not with wontfix. Instead, it shows a letter a with circumflex. Yeah, there's another double encoding problem there which I haven't had a chance to fix yet. Thanks for the report! Don Armstrong -- LEADERSHIP -- A form of self-preservation exhibited by people with autodestructive imaginations in order to ensure that when it comes to the crunch it'll be someone else's bones which go crack and not their own. -- The HipCrime Vocab by Chad C. Mulligan (John Brunner _Stand On Zanzibar_ p256-7) http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682010: [mumble] Communication failures due to CELT codec library removal
On Sat, 21 Jul 2012, Ron wrote: One very last thing then, before I hopefully stop bothering you for a while (: ** Use speex instead + Clients cannot currently report speex version during codec selection process I don't understand where that issue came from? Speex has been API and bitstream compatible since, like 2006, or maybe before. Maybe I totally misunderstand what that's saying, but anything relying on a speex version is almost surely Doing It Wrong. Chris asked for this to be added IIRC; I believe[1] that this should really be currently report speex support rather than speex version. Don Armstrong 1: Hopefully I'll be corrected if I'm wrong; it's likely that I introduced the incorrect wording too. -- Whatever you do will be insignificant, but it is very important that you do it. -- Mohandas Karamchand Gandhi http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#544192: Please add debian-live pseudo package
On Sat, 21 Jul 2012, Daniel Baumann wrote: On 07/21/2012 12:31 AM, Don Armstrong wrote: The last time I touched this, no one had decided what the name of the actual pseudo package was going to be. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544192#25 why exactly is 'debian-live' not ideal? Because it sure sounds like a package name to me. I understand now that you aren't planning on ever wanting to use it as a package name, but it also means that no one else will ever be able to use it as a package name. we already ruled your suspicion of 'that could potentially be a package name' out, it isn't a package name and never will be (debian-live tools are named live-* on purpose, so that they are derivatives friendly). If you all are fine with it never being a package name in the future, then that's fine by me. However, when I asked originally, it wasn't clear to me that this had been considered. if you insist on not using debian-live as name within the bts for a pseudo-package, can we have live.debian.org then? That's fine too. if we can't have live.debian.org without having the url first, let's have live.debian.net then, as this is what we use since many years consistently anywhere anyways. This is also fine. I'm also going to assume that the correct maintainer address for the psuedopackage is debian-l...@lists.debian.org? And the description should be something like: General problems with systems running Debian Live Once the name is settled, I'll create the pseudopackage. Don Armstrong -- The carbon footprint of a single human being is enormous. If you think about it, your honour, I'm an environmentalist. -- a softer world #283 http://www.asofterworld.com/index.php?id=283 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681853: bugs.debian.org: changing owner failed: Ignoring request to unset the owner of bug #NNNNNN which was not set
On Tue, 17 Jul 2012, Jakub Wilk wrote: I tried to change owner of a few bugs to myself. This failed, with an error message that makes little sense to me: owner 666243 ! Bug #666243 [sponsorship-requests] RFS: peg/0.1.9-1 [ITP] -- recursive-descent parser generators for C Ignoring request to unset the owner of bug #666243 which was not set owner 663916 ! Bug #663916 [sponsorship-requests] RFS: phonetisaurus/0.4-1 [ITP] -- Grapheme to Phoneme conversion tool Ignoring request to unset the owner of bug #663916 which was not set Thanks for the report! This was a bug in code that I recently introduced, which I've now fixed in my code, and will push out to the BTS shortly. As a side note, I'm surprised that the reply was CCed to the package maintainer, even though all commands failed: https://lists.debian.org/debian-mentors/2012/07/msg00213.html This is actually expected; if the BTS can figure out which bug the control command is for, it CC's appropriate people even if the command fails. [In this case, though, the special handling of ! was buggy, so it was equivalent to noowner.] Don Armstrong -- PowerPoint is symptomatic of a certain type of bureaucratic environment: one typified by interminable presentations with lots of fussy little bullet-points and flashy dissolves and soundtracks masked into the background, to try to convince the audience that the goon behind the computer has something significant to say. -- Charles Stross _The Jennifer Morgue_ p33 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681608: Testing control at submit
Package: bugs.debian.org Control: retitle -1 this is just a test of control at submit time This bug is just a test of control at submit time. Don Armstrong -- Miracles had become relative common-places since the advent of entheogens; it now took very unusual circumstances to attract public attention to sightings of supernatural entities. The latest miracle had raised the ante on the supernatural: the Virgin Mary had manifested herself to two children, a dog, and a Public Telepresence Point. -- Bruce Sterling, _Holy Fire_ p228 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681609: Testing control at submit
Package: bugs.debian.org Control: retitle -1 this is just a test of control at submit time This bug is just a test of control at submit time. Don Armstrong -- Miracles had become relative common-places since the advent of entheogens; it now took very unusual circumstances to attract public attention to sightings of supernatural entities. The latest miracle had raised the ante on the supernatural: the Virgin Mary had manifested herself to two children, a dog, and a Public Telepresence Point. -- Bruce Sterling, _Holy Fire_ p228 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681614: Testing control at submit
Package: bugs.debian.org Control: retitle -1 this is just a test of control at submit time This bug is just a test of control at submit time. Don Armstrong -- Miracles had become relative common-places since the advent of entheogens; it now took very unusual circumstances to attract public attention to sightings of supernatural entities. The latest miracle had raised the ante on the supernatural: the Virgin Mary had manifested herself to two children, a dog, and a Public Telepresence Point. -- Bruce Sterling, _Holy Fire_ p228 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681618: Testing control at submit
Package: bugs.debian.org Control: retitle -1 this is just a test of control at submit time This bug is just a test of control at submit time. Don Armstrong -- Miracles had become relative common-places since the advent of entheogens; it now took very unusual circumstances to attract public attention to sightings of supernatural entities. The latest miracle had raised the ante on the supernatural: the Virgin Mary had manifested herself to two children, a dog, and a Public Telepresence Point. -- Bruce Sterling, _Holy Fire_ p228 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681628: Plugins::URIDNSBL complains if tflags is not set
Package: spamassassin
Version: 3.3.1-1
Plugins::URIDNSBL complains about undefined values in tflags if an
additional rule has been added to the configuration which does not
have a tflag set. Instead, it should test for the existance of tflags
before testing the regex. The attached patch fixes this.
Don Armstrong
--
One day I put instant coffee in my microwave oven and almost went back
in time.
-- Steven Wright
http://www.donarmstrong.com http://rzlab.ucr.edu
Description: Do not complain if tflags are not set for a uridnsbl
Origin: Don Armstrong d...@debian.org
Forwarded: no
--- a/lib/Mail/SpamAssassin/Plugin/URIDNSBL.pm
+++ b/lib/Mail/SpamAssassin/Plugin/URIDNSBL.pm
@@ -953,7 +953,8 @@
my $rulecf = $scanner-{conf}-{uridnsbls}-{$rulename};
# ips_only/domains_only lookups should not act on this kind of BL
-next if ($tflags-{$rulename} =~ /\b(?:ips_only|domains_only)\b/);
+next if (defined $tflags-{$rulename} and
+$tflags-{$rulename} =~ /\b(?:ips_only|domains_only)\b/);
$self-lookup_single_dnsbl($scanner, $obj, $rulename,
$revip, $rulecf-{zone}, $rulecf-{type});
Bug#614907: Call for votes on node+nodejs
clone 614907 -1 -2 reassign -1 nodejs retitle -1 Provide /usr/bin/nodejs in nodejs with /usr/bin/node legacy package reassign -2 node retitle -2 Rename /usr/sbin/node to /usr/sbin/ax25-node with depended legacy package thanks On Sun, 08 Jul 2012, Steve Langasek wrote: === Resolution === The Technical Committee reaffirms the importance of preventing namespace collisions for programs in the distribution, while recognizing that compatibility with upstreams and with previous Debian releases is also important and that sometimes an imperfect balance must be struck between these three goals. The Committee therefore resolves that: 1. The nodejs package shall be changed to provide /usr/bin/nodejs, not /usr/bin/node. The package shall declare a Breaks: relationship with any packages in Debian that reference /usr/bin/node. 2. The nodejs source package shall also provide a nodejs-legacy binary package at Priority: extra that contains /usr/bin/node as a symlink to /usr/bin/nodejs. No package in the archive may depend on or recommend the nodejs-legacy package, which is provided solely for upstream compatibility. This package shall also declare a Conflicts: relationship with the node package. 3. The node source package shall rename its binary to /usr/sbin/ax25-node, and its binary package to ax25-node. 4. The node source package shall continue to build a transitional 'node' binary package for compatibility with deployed Debian installations, which provides /usr/sbin/node as a symlink to /usr/sbin/ax25-node. This package shall declare a reciprocal Conflicts: relationship with the nodejs-legacy package. Other packages may reference the 'node' package as a dependency or recommendation, but are encouraged to transition to 'ax25-node'. 5. The maintainers of these packages are required to implement the above changes immediately in unstable. Failing that, the Technical Committee reserves the right to NMU to implement these changes. 6. Once the above changes are implemented, the packages shall be considered suitable for release with respect to the Debian policy on conflicting packages. === End Resolution === With Colin's vote, the outcome is no longer in doubt, and the above resolution is adopted by the committee. Don Armstrong -- It's not Hollywood. War is real, war is primarily not about defeat or victory, it is about death. I've seen thousands and thousands of dead bodies. Do you think I want to have an academic debate on this subject? -- Robert Fisk http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681166: [bugs.debian.org] Replies to a ticket closure addressed to the ticket rather than to the closer
On Tue, 10 Jul 2012, Filipus Klutiero wrote: Notifications of ticket closures instruct: It has been closed by Foo. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Foo by replying to this email. But replying to that email actually replies to the ticket (x...@bugs.debian.org), not to the closer. Indeed, Reply-To is set to x...@bugs.debian.org. The right place to do so is by a mail to n...@bugs.debian.org, not Foo. Don Armstrong -- Facts are the refuge of people unwilling to reassess what they hold to be True. http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681375: Request for a debian-user-co mailing list
On Thu, 12 Jul 2012, Luis Uribe wrote: I'd like to ask for a new mailing list created: debian-users-co The appropriate mailing list for local coordination would actually be debian-dug...@lists.debian.org. [debian-user- mailing lists are specific to languages, not a country.] Post Policy: Moderated Mderators: Luis Uribe a...@eviled.org Jorge Guevara jguev...@debiancolombia.org Also, the posting policy should probably be open unless there's a very specific reason to not have it be open. Other than that, I believe the request is appropriate (but I don't approve mailing lists). Don Armstrong -- 6: I'm human. I have a thousand flaws. I break down. I get up or I don't get up. I get lost. I make the same mistakes over and over. I have scars and wounds. Sometimes when I can't bear them anymore, I drink. You can't fix me. You can't fix any of us. You can't make us perfect. -- The Prisoner (2009 Miniseries) _Checkmate_ http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#567849: install-info: warning: no info dir entry
On Fri, 29 Jun 2012, Julian Gilbey wrote: Hi Don! On Wed, Jun 13, 2012 at 07:45:43AM +0100, Julian Gilbey wrote: On Thu, Oct 06, 2011 at 04:17:59PM +0200, Paul Menzel wrote: When installing lilypond on unstable, I get following warnings. They pop up evertime install-info is triggered. install-info: warning: no info dir entry in `/usr/share/info/lilypond.info-images-dir-dep.gz' [...] I've fixed the problem. Attached is a diff of my proposed version; it would be great to upload it before the freeze. I'll upload it as an NMU tomorrow evening unless you either have a chance to apply the patch before then or tell me not to. Unfortunately, this patch is basically unusable, because it's screwed up the encoding. [It doesn't appear to be UTF8 any longer.] Don Armstrong -- Identical parts aren't. -- Beach's Law http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
