Your message dated Tue, 15 Dec 2020 18:42:00 +0200
with message-id <[email protected]>
and subject line Re: Bug#977293: Read .xlsx from stdin, write .csv to stdout
has caused the Debian Bug report #977293,
regarding Read .xlsx from stdin, write .csv to stdout
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.)
--
977293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977293
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: xlsx2csv
Version: 1:0.7.6-1
Severity: wishlist
Tags: upstream
Dear upstream authors,
Many thanks for this very convenient tool.
Would it please be possible to extend is so that "-" ban be specified
both as the name of the input file (meaning to read the .xlsx file
from standard input) and as the name of the output file, meaning that
the CSV file is written to stdout?
That way the program could be used in a pipe, which would be very
convenient. Of course that requires to make sure that all the
other messages the program could possibly produce are written to stderr.
Many thanks in advance!
Sébastien.
--- End Message ---
--- Begin Message ---
Dear Sébastien,
On 2020-12-14 08:24, Sébastien Hinderer wrote:
> My bad, sorry. Iwanted to write "dear maintainers" but while doing so I
> was thinking that it was an upstream bug. My reason for submitting it as
> a Debian bug was that I wanted to have a feedback not only in terms of
> whether the feature can be included or not but also in terms of in which
> version of the Debian package a fix would be included.
This can be done, but two bug reports will be needed. One has to be
filed on the upstream issue tracker, and the other here, on Debian BTS.
When filing the latter one, add "Forwarded: " pseudoheader to the bug
report indicating the URL of the upstream bug report. There is an
automated system checking upstream bug reports and informing the
maintainers whenever they are closed.
> No I didn't because, after almost 20 years of use of Unix, I was simply
> not aware of the existence of these files! So, many thanks for making me
> realise their existence!
Glad to help!
> Best wishes and thanks again, feel free to close the bug. If I submit an
> issue I can always write back to link it with the present bug report.
I will do so. Feel free to reopen this bug report after submitting your
request upstream.
Best,
Andrius
--- End Message ---
