Your message dated Thu, 10 Jan 2013 19:47:46 +0000
with message-id <[email protected]>
and subject line Bug#697624: fixed in minicom 2.6.1-2
has caused the Debian Bug report #697624,
regarding minicom: can't use /dev/serial/by-path/*usb* device names
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.)
--
697624: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697624
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: minicom
Version: 2.6.1-1
Severity: normal
Dear Maintainer,
123456789012345678901234567890123456789012345678901234567890123456789012
minicom cuts off the name of the serial device file at the first colon,
so by-path persistent serial device names can't be used; at least not
for USB serial adapters.
I'm using several el-cheapo USB serial adapters that have no serial
number on the same host, so the only way to distinguish them reliably is
to identify them by the physical port of the USB hub they're plugged
into, which is exactly what the /dev/serial/by-path/*usb* symlinks do.
To reproduce:
1. Plug in a USB serial adapter
2. Check /dev/serial/by-path for the device name, e.g.
/dev/serial/by-path/platform-orion-ehci.0-usb-0:1.1:1.0-port0
3. Create a new minicom configuration file:
minicom -s P1
4. In "Serial port setup", enter the device name from 2. in
A - Serial Device.
5. Choose "Exit" (not "Exit from Minicom")
6. The following error message will appear:
minicom: cannot open /dev/serial/by-path/platform-orion-ehci.0-usb-0: No
such file or directory
As you can see, minicom cuts off the device name after the first
colon. Shortening the path (for testing purposes) or adding a backslash
for to escape the colon shows the same result.
minicom(1) mentions space, comma and semicolon as special characters in
the device name, but not colon.
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental')
Architecture: armel (armv5tel)
Kernel: Linux 3.2.0-4-kirkwood
Locale: LANG=en_GB, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages minicom depends on:
ii libc6 2.13-37
ii libtinfo5 5.9-10
Versions of packages minicom recommends:
ii lrzsz 0.12.21-5
minicom suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: minicom
Source-Version: 2.6.1-2
We believe that the bug you reported is fixed in the latest version of
minicom, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Martin A. Godisch <[email protected]> (supplier of updated minicom package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Thu, 10 Jan 2013 20:28:50 +0100
Source: minicom
Binary: minicom
Architecture: source amd64
Version: 2.6.1-2
Distribution: unstable
Urgency: low
Maintainer: Martin A. Godisch <[email protected]>
Changed-By: Martin A. Godisch <[email protected]>
Description:
minicom - friendly menu driven serial communication program
Closes: 692880 697624
Changes:
minicom (2.6.1-2) unstable; urgency=low
.
* Changed path delimiter handling, closes: #697624.
Thanks to the gentle upstream maintainer.
* Updated standards version:
+ Added build-arch and build-indep target to debian/rules.
+ Added $(shell dpkg-buildflags --export=configure) to configure call.
* Fixed debian/watch, closes: #692880.
Checksums-Sha1:
203672ef79b83bf4fa279a971a0b794686480eef 1085 minicom_2.6.1-2.dsc
48236c78ca6dec4cbd822894581b4508faa9d885 11821 minicom_2.6.1-2.debian.tar.gz
74e21d91cc41207c12b543c43952068bc0393ef1 324214 minicom_2.6.1-2_amd64.deb
Checksums-Sha256:
6a6215d34bcaad2d54e6e9cb72e6d377b994d348073bfc5be39a8b2c01aa8760 1085
minicom_2.6.1-2.dsc
1aa8aa2b2554bb7fb81a3277bb4b80ddb43c87c14e511f4a9322ff56073601ed 11821
minicom_2.6.1-2.debian.tar.gz
9db705313f8917f29e8e6c304fa37c06c541e6a481bb508f7c8482a7a3a6e997 324214
minicom_2.6.1-2_amd64.deb
Files:
e40755e0d294c60885a5f269246bd374 1085 comm optional minicom_2.6.1-2.dsc
a7ad6516a55a9249c6452cb622c2198f 11821 comm optional
minicom_2.6.1-2.debian.tar.gz
4bf2e922e8f6e7f1750e444119db8422 324214 comm optional minicom_2.6.1-2_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlDvFwoACgkQhOZKoAn8AVxqXQCfQH5ICJMp3FdvGPIU2UL9AdLP
dGkAn1w7df2i3sD3ifDsNopY41T89+Pp
=RRiG
-----END PGP SIGNATURE-----
--- End Message ---
