Re: Long descriptions in RFS emails.
Ben Finney wrote: Neil Williams <[EMAIL PROTECTED]> writes: On Mon, 2008-02-11 at 08:37 +1100, Ben Finney wrote: A good policy except that I'd recommend you respond to at least some of them to say *why* you think they're worth ignoring. Those who take some time over the preparation of packages and show some level of effort in at least applying the principles of the FAQ deserve my support and as I have limited time, I therefore choose to prioritise my support to those who take the time to do the work. A reasonable position. Well, thanks for making your policies available for reference by others, and for keeping them up to date. And while Ben has a good point, I think there will be others who respond to some of these newcomers. I appreciate the policy Neil has espoused and will likely point out to others that a lurker like me expects them to consider it. I do not sponsor many packages, but before I seriously take a look at one I use these 'best practices' from my fellow developers as a guideline. Hopefully the newcomers will remember that there is no obligation to become a sponsor and therefore it is in their best interest to do the homework that makes it easier to look at their package. Richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Requests for sponsors to upload NMUs
Sune Vuorela wrote: .. the maintainer is MIA and the package can be orphaned beforehand, fine (but then it's no longer an NMU, it's a QA upload). Changing a SONAME is *not* acceptable in an NMU without permission from the maintainer. It is an especially bad idea when doing NMU's as part of a release bug You seem to be living in perfect-world where maintainers are always reachable. Or perhaps he had an experience similar to mine where the maintainer was available but no attempt was made to contact. MIA-process && orphaning is too slow for bugfixing. This isn't about anything else than bugfixing. So, in this case you claim it is only about "bugfixing." While you may want to look at it in that light, I am sure there are others who see it differently. Going back to a thread I previously (http://lists.debian.org/debian-mentors/2007/10/msg00229.html) participated in, I will again emphasize the need for communication. If the maintainer is truly MIA, that is a bigger issue than any single bug. Others have made this argument that we should focus on a bug to justify a NMU (even when it goes against established practice or breaks the rules). We may not live in a "perfect-world", but we should strive to improve our processes to handle these situations. It does not help if individual DDs promote their pet theories to those who agree with them. Richard P.S. In case it is not obvious, I am not directing my comments to any specific individual or incident. I explicitly reject this narrow bug fix only mindset. I want to promote and improve the entire Debian system where communication is critical. While a NMU is easy to focus on (and acceptable as our documentation shows ;-), we still need to look at the overall consequences and effects. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: information required
sadia jameel wrote: hello dear My name is sadia and i am student of MS(computer science). i want some information relating to bug #436681 that has been fixed now. i have two problems in checking this bug: Q 1- please tell me how can i install the new package of "backuppc_3.0.0- 4.diff.gz" on my PC ?? As i have already installed the old version of package "backuppc 2.1.2.6" directly through internet but can not install the new version of this package. I have also tried Hi Sadia; At the risk of spoon feeding you something you should already know, there is a difference between a *.diff.gz and a *.deb file. If you do not already understand these differences, you might be better served if you begin with the debian-user mailing list. This debian-mentors list is not tailored to answer these type of questions. Richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: nautilus-clamscan
Clement Lorteau wrote: .. Your GPG key is not signed by anyone. You should try to meet someone that can sign it, preferably a DD or someone whose key is signed by a DD. Look at this page: https://nm.debian.org/gpg.php If you live in Paris or near Paris, I can sign your key. I do live near Paris. I'll contact you in private. However, is the key signing needed for uploading the package? I had 2 versions of another package uploaded without having to have my key signed. If I were intimately familiar with a package and had looked at EVERYTHING, I would be comfortable uploading a package signed with an unverified key. But that is a lot of work (and I am basically asking everyone to hold me accountable for any problems ;-). It is much more likely that I would not duplicate someone else's effort. When I decide to accept what someone else has done, then it become much more important to be able to identify that person. At the point where I might want to say I got code from someone else, the signed key becomes critical. I could upload a package that was sent with an unverified key, but that would speak volumes about my judgement. When I sign a package (or another key for that matter), a person can rely on my judgement as input. I do not promote worthless input. It should be easy to understand why a person would hesitate to accept an unverified key since it could make their judgement worthless. Richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Which 64 bit cpu assembler to use ?
Basile STARYNKEVITCH wrote: Star Liu wrote: Greetings! I'm a newbie in assembly language programming, for I worked as a C# programmer on microsoft platform in the past years, but now I want to know clearly how operating system and softwares are executed, so I begin to learn assembly language programming, I have learned some 32 bit asm coding, and want to move to 64 bit coding. Is there any good toturial to follow? and which assembler should I use? I suggest avoiding coding in assembler. In 2008, this has no sense. If you really need some strange machine instruction, use the asm statement inside a GCC-compiled code. After all, long ago we learned that 640K was enough memory for all our needs ;-) Richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 0-day NMUs, DELAYED/n uploads
Cyril Brulebois wrote: The rules defined in [1] applied. And instead of pinging the maintainer, waiting, and then uploading (to DELAYED/0), it looked like (after talking with DDs during the BSP I mentioned) that DELAYED/n was a good means of notifying the maintainer, through the nmudiff sent to the bug, making the patch publicly visible, as well as the status of the bug (patch & pending tags), and letting the maintainer the time to react. 1. http://lists.debian.org/debian-devel-announce/2007/09/msg0.html While that link describes a temporary necessity, the regular NMU rules still apply. I do not know which DDs you talked with, but submitting an NMU to a "DELAYED/n" queue IS NOT "a good means of notifying the maintainer." You should always try to contact the maintainer first! I am not suggesting that a maintainer that refuses to respond will hold up the NMU. I want to explicitly note the disrepect that is shown when a maintainer first learns of the NMU from a DELAYED queue without prior notice. If a person cannot communicate with some email, being a 'lone wolf' submitting NMUs will not benefit the project in the long term. The NMU does not replace communication skills. The link above deals with a special need. Lack of communication will create other special problems. My response here is not directed to a specific person or conversation. I just want to prevent a flood of NMUs as "a good means of notifying the maintainer." Richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 0-day NMUs, DELAYED/n uploads
Lucas Nussbaum wrote: Hi, If I understand things correctly, we are discussing the NMU of grig by Cyril (#444509). .. And that is why I explicitly said my reply was not directed to any specific person or conversation. I see Bas was able to understand this. If a person cannot communicate with some email, being a 'lone wolf' submitting NMUs will not benefit the project in the long term. The NMU does not replace communication skills. Mails were sent to the relevant bugs on the BTS (and thus to the maintainer(s)). Do you need a personal email, because you filter out BTS mails? Then we probably have another problem. Yes, we do have a problem. From section 5.11.1 of our developers reference (http://www.debian.org/doc/developers-reference), the admonition is to "contact the developer first, and act later." It appears to me that people do not even understand what the usual rules are for NMUs. As another example, our Code of Conduct regarding mailing list usage (http://www.debian.org/MailingLists) specifically states that a CC should not be sent to a person unless they ask for it. But I suppose some clever sophist will make the pedantic claim "But I used a To: line instead of the CC: line." The inability to read English and communicate creates other problems. We do not need DDs creating their own rules. We have an existing reference guide to help us. If we follow the existing rules there is no need for a new "good means of notifying the maintainer." My point has been made, so there is no need to continue further unless you want to start with a pedantic definition of "properly notified." Richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
binfmt_elf module
Hi; I have been hacking on a system I upgraded from hamm to woody during a bunch of other modifications. I am about at wits-end so I will play the poor newbie_in_NM_queue role. I just tried downgrading to potato and now I find the following situation: dpkg --install --force-downgrade --force-conflicts ldso_1.9.11-9.deb libc6_2.1.3-10.deb You are using the binfmt_elf module to support ELF binaries. This will not work because the system programs required to load the modules will themselves be ELF binaries. Errors were encountered while processing: ldso_1.9.11-9.deb libc6_2.1.3-10.deb Could someone please explain what this means? TIA, Richard A. Heckers "if it isn't source, it isn't software" brought to you courtesy of NASA
binfmt_elf module
Hi; I have been hacking on a system I upgraded from hamm to woody during a bunch of other modifications. I am about at wits-end so I will play the poor newbie_in_NM_queue role. I just tried downgrading to potato and now I find the following situation: dpkg --install --force-downgrade --force-conflicts ldso_1.9.11-9.deb libc6_2.1.3-10.deb You are using the binfmt_elf module to support ELF binaries. This will not work because the system programs required to load the modules will themselves be ELF binaries. Errors were encountered while processing: ldso_1.9.11-9.deb libc6_2.1.3-10.deb Could someone please explain what this means? TIA, Richard A. Heckers "if it isn't source, it isn't software" brought to you courtesy of NASA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Becoming a Debian Developer [eol package]
David Caldwell wrote: .. - Do I really need my key signed by someone, or is a signed ID card ok? > If I need to meet someone in person, I live in Orange County, California (I > work very near John Wayne Airport)... Anyone live or work near here (who > can sign my key)? >- Is this the proper forum for these questions? > > Thanks, > David > This has gotten considerably easier. There is now a mailing list for those living south of Silicon Valley ;-) General information about the mailing list is at: http://opensource.lineo.com/mailman/listinfo/scd -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Becoming a Debian Developer [eol package]
David Caldwell wrote: .. - Do I really need my key signed by someone, or is a signed ID card ok? > If I need to meet someone in person, I live in Orange County, California (I > work very near John Wayne Airport)... Anyone live or work near here (who > can sign my key)? >- Is this the proper forum for these questions? > > Thanks, > David > This has gotten considerably easier. There is now a mailing list for those living south of Silicon Valley ;-) General information about the mailing list is at: http://opensource.lineo.com/mailman/listinfo/scd
