Bug#522298: marked as done (RFP: truncate -- truncate files)
Your message dated Tue, 10 Jan 2023 14:54:04 +0100
with message-id <Y71t/OBV6vM9ClYb@angband.pl>
and subject line NAK
has caused the Debian Bug report #522298,
regarding RFP: truncate -- truncate files
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 owner@bugs.debian.org
immediately.)
--
522298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522298
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: RFP: truncate -- truncate files
- From: Folkert van Heusden <folkert@vanheusden.com>
- Date: Thu, 02 Apr 2009 17:13:33 +0200
- Message-id: <20090402151333.15821.48515.reportbug@belle.intranet.vanheusden.com>
Package: wnpp
Severity: wishlist
* Package name : truncate
Version : 0.7
Upstream Author : Folkert van Heusden <folkert@vanheusden.com>
* URL : http://vanheusden.com/Linux/#truncate
* License : GPL
Programming Lang: C
Description : truncate files
truncate truncates files to a given new size.
It is command-line compatible with the version found in FreeBSD.
-- System Information:
Debian Release: 5.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
> Well, the latest version (0.8) dates back to 2009:
> We have "truncate" in the Debian GNU coreutils package:
> And the FreeBSD truncate syntax is not that different:
> So I doubt this program really needs Debian packaging.
No need to keep this open, thus.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Bestest pickup line:
⢿⡄⠘⠷⠚⠋⠀ "Cutie, your name must be Suicide, cuz I think of you every day."
⠈⠳⣄⠀⠀⠀⠀
--- End Message ---
Reply to: