[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#164889: md5sum <FILE produces spurious ` -' in output

>>"Raul" == Raul Miller <moth@debian.org> writes:

 Raul> On Mon, Nov 11, 2002 at 03:49:29PM -0600, Manoj Srivastava wrote:
 Raul> y=`md5sum < blah*.deb | awk '{print $1}'`
 >> Fails for md5sum /some/file >> hash-file-to-be-parsed-later

 Raul> I'm not following you.  If you're not using md5sum on stdin,

	Sorry. This was a thinko. I had fallen into the mistaken
 belief that the output of the md5sums were always different, not just
 for the STDIN.

 Raul> Initially.  Priority should eventually be bumped up if the issue isn't
 Raul> addressed and the new interface is still important.

	I am unable to determine yet how important it is, especially
 since I had thought the problem was worse than it is. (ucf is not
 affected, BTW)

 Raul> Until all those bugs have been closed -- and until every package with
 Raul> a md5sum dependency has had a chance to be tested -- we should forbid
 Raul> deployment of the gnu version.
 >> How do we keep track of these bugs? 

 Raul> Hmm... I guess we don't have a tool that says "given these bug
 Raul> numbers, give me the status of each".  If we had such a tool
 Raul> (seems easy enough to write), package maintainer for the
 Raul> package with changing interface could run [maybe it once a week]
 Raul> to track progress.

	The problem also exists of discovery -- how is that list
 initially created? How are additions to the list tracked? Once the
 list exists, I guess one may coble together scripts that handle
 deletions from the list if the bugs are closed (and, with a little
 care, track reopenings)

	Assuming there is a real list of packages that actually shall
 be affected by a change, the list we shall have may not actually
 contain all dependent packages; and some may be added as the we
 discover the dependency.

	Since the changed interface is not permitted to be introduced
 until all (most?) packages have transitioned, some of the undiscovered
 bugs won't be known until they break on the day the interface
 changed. (I am speaking to your general case here).

 He is a man capable of turning any colour into grey. John LeCarre
Manoj Srivastava   <srivasta@debian.org>  <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

Reply to: