Your message dated Sun, 3 Feb 2019 22:06:02 +0100 with message-id <[email protected]> and subject line Re: Bug#68624: why is this a bug? has caused the Debian Bug report #68624, regarding dupload: does not check current directory for .changes file before open. to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 68624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=68624 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: dupload Version: 2.4.1 Severity: wishlist omnic@aeon:~/debian/build/ppp/ppp-2.4.0b4> dupload --to master \ ppp_2.4.0b4-1_i386.changes dupload fatal error: Can't read ppp_2.4.0b4-1_i386.changes: No such file or directory at /usr/bin/dupload line 201 Maybe a check, and a meaningful mesage? and not a fatal error? -- System Information Debian Release: woody Architecture: i386 Kernel: Linux aeon 2.2.17 #1 Sun Jul 9 15:47:26 NZST 2000 i686 Versions of packages dupload depends on: ii libnet-perl 1.0703-4 Implementation of Internet protoco ii perl-5.005 [perl5] 5.005.03-7.1 Larry Wall's Practical Extracting
--- End Message ---
--- Begin Message ---Hi! On Wed, 2002-08-28 at 17:10:38 +0200, Josip Rodin wrote: > You wrote: > > omnic@aeon:~/debian/build/ppp/ppp-2.4.0b4> dupload --to master \ > > ppp_2.4.0b4-1_i386.changes > > dupload fatal error: Can't read ppp_2.4.0b4-1_i386.changes: No such file > > or directory at /usr/bin/dupload line 201 > > > > Maybe a check, and a meaningful mesage? and not a fatal error? > > Er, it is a check, and the message is both meaningful and about a fatal > error :) Right, I don't get the bug report. It states that the file is not present and it cannot be read. I'm not sure why this should not be a fatal error either. I'm thus closing the report. Thanks, Guillem
--- End Message ---
