Bug#739695: Convenient copy of mtio.h in source

2014-07-19 Thread Iustin Pop
On Fri, Feb 21, 2014 at 01:30:23PM +0100, Mathieu Malaterre wrote: > Package: mt-st > > It is not clear what the impact would be, but I think it would be > easier to maintain this package if the mtio.h copy would not be used > and instead the system installed one would be used instead. Thanks for

Bug#739694: Invalid file ref in documentation (man page)

2014-07-19 Thread Iustin Pop
severity 739694 minor thanks On Fri, Feb 21, 2014 at 01:27:56PM +0100, Mathieu Malaterre wrote: > Package: mt-st > > > man page refers to: > > [...] > Otherwise, >a default device defined in the file /usr/include/sys/mtio.h is used. > [...] > > I believe this is inacurate as it does no

Bug#739693: Add homepage for mt-st

2014-07-18 Thread Iustin Pop
On Fri, Feb 21, 2014 at 01:25:44PM +0100, Mathieu Malaterre wrote: > Package: mt-st > > It would be nice to have the Homepage set in d/control and/or in the > debian/watch file. For example: The watch file already has correct information (see https://qa.debian.org/cgi-bin/watch?pkg=mt-st_1.1-5).

Bug#754593: mt erase is a full (long) erase, document it as such

2014-07-12 Thread Iustin Pop
in/sh linked to /bin/dash Versions of packages mt-st depends on: ii libc6 2.18-7 mt-st recommends no packages. mt-st suggests no packages. -- Configuration Files: /etc/stinit.def changed [not included] -- no debconf information Author: Iustin Pop Description: Improve manual page for the erase

Bug#520258: This is a very old version

2010-08-25 Thread Iustin Pop
I just took a quick look at this bug, but it's against version 4.0b7, and current upstream version is 6.1, so the easiest way out would be to first test a new upstream version. regards, iustin signature.asc Description: Digital signature

Bug#464631: RFC 2616 crazy paragraph

2010-08-04 Thread Iustin Pop
On Fri, Feb 08, 2008 at 09:00:56AM +0800, jida...@jidanni.org wrote: > Package: doc-rfc-std > Version: 20030621-1 > File: /usr/share/doc/RFC/links/rfc2616.txt.gz ? > > What is up with this crazy paragraph? > >4.If the message uses the media type "multipart/byteranges", and the > ransfer-