Bug#341839: Call for vote: coreutils: md5sum output format

2007-06-18 Thread Steve Langasek
On Thu, Jun 14, 2007 at 12:45:16AM -0400, Bdale Garbee wrote:
 - - -=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-
 [ 2 ] Choice 1: the output of md5sum should be changed as per bug #341839
 [ 1 ] Choice 2: the output of md5sum should not change despite bug #341839
 [ 3 ] Choice 3: Further discussion
 - - -=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-

We have a de facto standard behavior today that is shared among coreutils
upstream, coreutils in Debian, and other analogous tools such as sha1sum,
sha256sum, and sha512sum.  While the TC has the authority to change the
behavior of these tools within Debian, we do not have the authority to get
them changed upstream, and the coreutils maintainer does not agree that this
is a correct technical solution; so at best, overriding the maintainer in
this case would result in inconsistent behavior between Debian and upstream.

The benefits of this change are not so great that divergence from upstream
is warranted.

However, I don't believe any further discussion is likely to be of benefit
either, so I have ranked further discussion last.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/


signature.asc
Description: Digital signature


Bug#341839: Call for vote: coreutils: md5sum output format

2007-06-18 Thread Manoj Srivastava
Hi,

I think that maintaining compatibility counts for more than not
 doing so.

- - -=-=-=-=-=- Don't Delete Anything Between These Lines  =-=-=-=-=-=-=-=-
[ 2 ] Choice 1: the output of md5sum should be changed as per bug #341839
[ 1 ] Choice 2: the output of md5sum should not change despite bug #341839
[ 3 ] Choice 3: Further discussion
- - -=-=-=-=-=- Don't Delete Anything Between These Lines  =-=-=-=-=-=-=-=-

Since I am at Debconf, I do not have read access to my keys;
 I'll sign this mail in a week or so if doing so is critical.

manoj
-- 
If you're not part of the solution, you're part of the precipitate.
Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/~srivasta/
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#341839: Call for vote: coreutils: md5sum output format

2007-06-17 Thread Bdale Garbee
[EMAIL PROTECTED] (Bdale Garbee) writes:

 - - -=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-
 [ 3 ] Choice 1: the output of md5sum should be changed as per bug #341839
 [ 1 ] Choice 2: the output of md5sum should not change despite bug #341839
 [ 2 ] Choice 3: Further discussion
 - - -=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-

I don't have a strong personal opinion on this question.  Given that, I 
choose to let the package maintainer's decision stand.

Bdale


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#341839: Call for vote: coreutils: md5sum output format

2007-06-14 Thread Ian Jackson
Bdale Garbee writes (Bug#341839: Call for vote: coreutils: md5sum output 
format):
 As Anthony noted in his early March summary of open issues, the current 
 md5sum behavior matches the formats used by upstream, and by related tools 
 such as sha1sum, sha256sum, and sha512sum.  He suggested that we should 
 rescind the previous TC decision in favor of existing practice, which means 
 ranking choice 2 on this ballot first.

Obviously my view is that sha*sum should have the behaviour specified
in the previous resolution.

 - - -=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-
 [ 1 ] Choice 1: the output of md5sum should be changed as per bug #341839
 [ 3 ] Choice 2: the output of md5sum should not change despite bug #341839
 [ 2 ] Choice 3: Further discussion
 - - -=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-

Ian.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#341839: Call for vote: coreutils: md5sum output format

2007-06-14 Thread Anthony Towns
On Thu, Jun 14, 2007 at 12:45:16AM -0400, Bdale Garbee wrote:
 - - -=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-
 [ 3 ] Choice 1: the output of md5sum should be changed as per bug #341839
 [ 1 ] Choice 2: the output of md5sum should not change despite bug #341839
 [ 2 ] Choice 3: Further discussion
 - - -=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-

This horse has bolted already.

]   * Don't worry if md5sum from stdin adds a   - after the md5sum. Should
] make debootstrap more usable on non-Debian Linuxes.
] -- Anthony Towns [EMAIL PROTECTED]  Mon, 25 Jun 2001 18:38:35 +1000

Cheers,
aj



signature.asc
Description: Digital signature


Bug#341839: Call for vote: coreutils: md5sum output format

2007-06-14 Thread Ian Jackson
Anthony Towns writes (Re: Bug#341839: Call for vote: coreutils: md5sum output 
format):
 This horse has bolted already.
 
 ]   * Don't worry if md5sum from stdin adds a   - after the md5sum. Should
 ] make debootstrap more usable on non-Debian Linuxes.
 ] -- Anthony Towns [EMAIL PROTECTED]  Mon, 25 Jun 2001 18:38:35 +1000

debootstrap is far from the only script that needs to deal with the
output from md5sum.

Ian.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#341839: Call for vote: coreutils: md5sum output format

2007-06-13 Thread Bdale Garbee
I hereby call for an immediate TC vote on the question of what md5sum's
output format should be, requested by bug #341839.  

As Anthony noted in his early March summary of open issues, the current 
md5sum behavior matches the formats used by upstream, and by related tools 
such as sha1sum, sha256sum, and sha512sum.  He suggested that we should 
rescind the previous TC decision in favor of existing practice, which means 
ranking choice 2 on this ballot first.

Since this vote may overrule a developer, 6.1.3 of our Constitution requires
a 3:1 majority of the TC for choice 1.  However, a simple majority will 
suffice for choice 2 to defeat further discussion.

  In the brackets next to your preferred choice, place a 1. Place a 2 in
  the brackets next to your next choice.  Continue until you reach your last
  choice.  Do not enter a number smaller than 1 or larger than 3.  You may
  skip numbers.  You may rank options equally (as long as all choices X you
  make fall in the range 1 = X = 3).

  To vote no, no matter what rank Further discussion as more
  desirable than the unacceptable choices, or You may rank the Further
  discussion choice, and leave choices you consider unacceptable
  blank. Unranked choices are considered equally the least desired
  choices, and ranked below all ranked choices. (Note: if the Further
  Discussion choice is unranked, then it is equal to all other unranked
  choices, if any.)

- - -=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-
[   ] Choice 1: the output of md5sum should be changed as per bug #341839
[   ] Choice 2: the output of md5sum should not change despite bug #341839
[   ] Choice 3: Further discussion
- - -=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-

Bdale


pgpdSNhYuAB4z.pgp
Description: PGP signature