Debian Bug report logs - #983719
Package is severely outdated

Display info messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Matthias Urlichs <matthias@urlichs.de>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: esptool: Version 3.0 fixes critical bugs

Date: Sun, 28 Feb 2021 20:58:54 +0100

Package: esptool
Version: 2.8+dfsg-1
Severity: serious
Justification: broken

$ esptool  erase_flash
esptool.py v2.8
Found 3 serial ports
Serial port /dev/ttyUSB0
Connecting....
Detecting chip type... ESP32
Chip is ESP32D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 3c:71:bf:03:2e:0c
Enabling default SPI flash mode...
Erasing flash (this may take a while)...

A fatal error occurred: ESP32 ROM does not support function erase_flash.

... umm ... YES IT DOES.

Version 3.0 works. Please upgrade.


-- System Information:
Debian Release: 10.8
  APT prefers stable
  APT policy: (700, 'stable'), (600, 'unstable'), (550, 'experimental'), (550, 'oldstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-13-amd64 (SMP w/8 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages esptool depends on:
ii  libc6           2.31-9
ii  python3         3.9.1-1
ii  python3-ecdsa   0.13-3+deb10u1
pn  python3-pyaes   <none>
ii  python3-serial  3.4-4

esptool recommends no packages.

esptool suggests no packages.

Message #14 received at 983719@bugs.debian.org (full text, mbox, reply):

From: Matthias Urlichs <matthias@urlichs.de>

To: 983719@bugs.debian.org

Subject: Update

Date: Wed, 12 May 2021 11:18:46 +0200

[Message part 1 (text/plain, inline)]

it seems that the most important bugfix that 3.0 has, compared to 2.8, 
is that it's upstream and thus not implicitly sets the --no-stub flag by 
default. This is bad because some boards require it.

TinyPICO:

$ PYTHONPATH=. python3 ./esptool.py  flash_id

esptool.py v3.1-dev

Found 3 serial ports

Serial port /dev/ttyUSB0

Connecting......

Detecting chip type... ESP32

Chip is ESP32-PICO-D4 (revision 1)

Features: WiFi, BT, Dual Core, 240MHz, Embedded Flash, VRef calibration in efuse, Coding Scheme None

Crystal is 40MHz

MAC: d8:a0:1d:54:76:20

Uploading stub...

Running stub...

Stub running...

Manufacturer: c8

Device: 4016

Detected flash size: 4MB

Hard resetting via RTS pin...


$ PYTHONPATH=. python3 ./esptool.py --no-stub  flash_id

esptool.py v3.1-dev

Found 3 serial ports

Serial port /dev/ttyUSB0

Connecting....

Detecting chip type... ESP32

Chip is ESP32-PICO-D4 (revision 1)

Features: WiFi, BT, Dual Core, 240MHz, Embedded Flash, VRef calibration in efuse, Coding Scheme None

Crystal is 40MHz

MAC: d8:a0:1d:54:76:20

Enabling default SPI flash mode...

Manufacturer: ff

Device: ffff

Detected flash size: Unknown

Hard resetting via RTS pin...


-- 
-- Matthias Urlichs

[Message part 2 (text/html, inline)]

[OpenPGP_signature (application/pgp-signature, attachment)]

Message #19 received at 983719@bugs.debian.org (full text, mbox, reply):

From: Sebastian Kuzminsky <seb@highlab.com>

To: 983719@bugs.debian.org

Subject: please upgrade to 4.4

Date: Thu, 2 Feb 2023 15:53:02 -0700

This is the version in Bullseye (and Bookworm and Sid):

$ esptool version
esptool.py v2.8
2.8

It does not correctly identify e.g. the ESP32-PICO-V3-02, as found on
the Adafruit ESP32 Feather V2, and it can not write the flash:
 
$ esptool --port /dev/ttyACM2 chip_id
esptool.py v2.8
Serial port /dev/ttyACM2
Connecting....
Detecting chip type... ESP32
Chip is unknown ESP32 (revision 3)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: e8:9f:6d:20:37:44
Enabling default SPI flash mode...
Warning: ESP32 has no Chip ID. Reading MAC instead.
MAC: e8:9f:6d:20:37:44
Hard resetting via RTS pin...

The latest version (installed with pip) is 4.4:

$ ~/.local/bin/esptool.py version
esptool.py v4.4
4.4

It works fine with this newer module, and it can write the flash:

$ ~/.local/bin/esptool.py --port /dev/ttyACM2 chip_id
esptool.py v4.4
Serial port /dev/ttyACM2
Connecting....
Detecting chip type... Unsupported detection protocol, switching and trying again...
Connecting....
Detecting chip type... ESP32
Chip is ESP32-PICO-V3-02 (revision v3.0)
Features: WiFi, BT, Dual Core, 240MHz, Embedded Flash, Embedded PSRAM, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: e8:9f:6d:20:37:44
Uploading stub...
Running stub...
Stub running...
Warning: ESP32 has no Chip ID. Reading MAC instead.
MAC: e8:9f:6d:20:37:44
Hard resetting via RTS pin...


An updated package would be appreciated.  Thanks!


-- 
Sebastian Kuzminsky

Message #24 received at 983719@bugs.debian.org (full text, mbox, reply):

From: Faidon Liambotis <paravoid@debian.org>

To: Matthias Urlichs <matthias@urlichs.de>, 983719@bugs.debian.org

Subject: Re: Bug#983719: esptool: Version 3.0 fixes critical bugs

Date: Tue, 21 Feb 2023 14:16:39 +0200

Control: retitle -1 Package is severely outdated
Control: severity -1 serious

This package is severely outdated. esptool v2.8, as currently packaged
in Debian, was released in October 2019, almost 3.5 years ago. Upstream
has regularly released newer versions every few months in the meantime,
with the latest being v4.5, released last week.

Newer versions bring a myriad of fixes, as well as equally importantly,
support for newer chips that can be found in the wild.

As I've also reported in #948096, esptool in Debian is crippled right
now by not including any flasher stubs, limiting its usefulness. The
removal was justified at the time, but some of the underlying reasons
have been resolved for a long time now for several of the supported
chips, and only require simple patches to be applied to restore.

(Also note: the packaging and DFSG-ness can be simplified quite a bit,
since the binary blobs are now split into JSON files in the build tree,
that can be cleaned up with Files-Excluded, removing the need for
modifying the source through the uupdate script.)

Given how outdated the source is, and the lack of responses from the
maintainer in the BTS, I do not believe the package is fit for the next
release, therefore I'm elevating the severity to RC.

I should note that while the package seems to meet the criteria for
Salvaging (DevRef 5.12) I don't currently have the bandwidth to maintain
it properly in the long run either. I'm happy to do a one-off NMU to
bring it to a more decent shape, however.

Best,
Faidon

Message #35 received at 983719@bugs.debian.org (full text, mbox, reply):

From: Faidon Liambotis <paravoid@debian.org>

To: 983719@bugs.debian.org

Subject: Re: Bug#983719: esptool: Version 3.0 fixes critical bugs

Date: Thu, 23 Feb 2023 12:16:41 +0200

On Tue, Feb 21, 2023 at 02:16:40PM +0200, Faidon Liambotis wrote:
> I should note that while the package seems to meet the criteria for
> Salvaging (DevRef 5.12) I don't currently have the bandwidth to maintain
> it properly in the long run either. I'm happy to do a one-off NMU to
> bring it to a more decent shape, however.

Update: I pushed a branch into the main repo, feature/2.8-update, that
just brings up the packaging to modern standards and switches to using
pybuild -- a step necessary given new upstream releases are now using
Python modules etc.

This is still tagged as a 2.8+dfsg-1.1 release that builds the package
as-is with enhancements and no regressions.

I also have changes underway for 4.5, but currently looking into what it
would take dependency-wise to accomplish this, as there are 1-2 new
Python module dependencies that are not present in Debian yet. I'll
follow up once I have something; I expect this to be in the next week or
so.

Regards,
Faidon

Message #42 received at 983719@bugs.debian.org (full text, mbox, reply):

From: Faidon Liambotis <paravoid@debian.org>

To: 983719@bugs.debian.org

Subject: Re: Bug#983719: esptool: Version 3.0 fixes critical bugs

Date: Thu, 9 Mar 2023 05:54:36 +0200

On Thu, Feb 23, 2023 at 12:16:41PM +0200, Faidon Liambotis wrote:
> I also have changes underway for 4.5, but currently looking into what it
> would take dependency-wise to accomplish this, as there are 1-2 new
> Python module dependencies that are not present in Debian yet. I'll
> follow up once I have something; I expect this to be in the next week or
> so.

I packaged the two new dependencies mentioned above:
 * python-reedsolo, which entered unstable this week; and 
 * python-pkcs11 (used only conditionally, for espsecure's HSM bits),
   which is waiting in NEW for about a week now.

I moved the repository to the DEP-14 layout, rebased the
feature/2.8-update branch, and then built on top of it in the new
debian/experimental branch. This now has 4.5.1, with lots of other fixes
and flasher stubs! I'd consider this a release candidate for an
experimental upload once pkcs11 passes through NEW.

Faidon

Message #47 received at 983719@bugs.debian.org (full text, mbox, reply):

From: Milan Kupcevic <milan@debian.org>

To: Faidon Liambotis <paravoid@debian.org>, 983719@bugs.debian.org, Matthias Urlichs <matthias@urlichs.de>

Subject: Re: Bug#983719: esptool: Version 3.0 fixes critical bugs

Date: Thu, 9 Mar 2023 07:17:37 -0500

Hi Faidon,

First of all thank you for your work on esptool update. I'm currently 
using my available time to work on avrdude for bookworm. If you wish to 
co-maintain esptool package feel free to add yourself to uploaders of 
this package.

I agree with your assessment. The best course at this point is to upload 
the updated package version together with the newly introduced 
dependencies to sid and let the system to auto-remove the old package 
from bookworm.

As soon as bookworm gets released we can make the updated esptool 
available via bookworm-backports.

Milan


On 2/21/23 07:16, Faidon Liambotis wrote:
> Control: retitle -1 Package is severely outdated
> Control: severity -1 serious
> 
> This package is severely outdated. esptool v2.8, as currently packaged
> in Debian, was released in October 2019, almost 3.5 years ago. Upstream
> has regularly released newer versions every few months in the meantime,
> with the latest being v4.5, released last week.
> 
> Newer versions bring a myriad of fixes, as well as equally importantly,
> support for newer chips that can be found in the wild.
> 
> As I've also reported in #948096, esptool in Debian is crippled right
> now by not including any flasher stubs, limiting its usefulness. The
> removal was justified at the time, but some of the underlying reasons
> have been resolved for a long time now for several of the supported
> chips, and only require simple patches to be applied to restore.
> 
> (Also note: the packaging and DFSG-ness can be simplified quite a bit,
> since the binary blobs are now split into JSON files in the build tree,
> that can be cleaned up with Files-Excluded, removing the need for
> modifying the source through the uupdate script.)
> 
> Given how outdated the source is, and the lack of responses from the
> maintainer in the BTS, I do not believe the package is fit for the next
> release, therefore I'm elevating the severity to RC.
> 
> I should note that while the package seems to meet the criteria for
> Salvaging (DevRef 5.12) I don't currently have the bandwidth to maintain
> it properly in the long run either. I'm happy to do a one-off NMU to
> bring it to a more decent shape, however.
> 
> Best,
> Faidon
> 

Message #52 received at 983719-close@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 983719-close@bugs.debian.org

Subject: Bug#983719: fixed in esptool 4.5.1+dfsg-0.1

Date: Fri, 17 Mar 2023 13:04:04 +0000

Source: esptool
Source-Version: 4.5.1+dfsg-0.1
Done: Faidon Liambotis <paravoid@debian.org>

We believe that the bug you reported is fixed in the latest version of
esptool, 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 983719@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Faidon Liambotis <paravoid@debian.org> (supplier of updated esptool 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 ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 17 Mar 2023 14:03:23 +0200
Source: esptool
Architecture: source
Version: 4.5.1+dfsg-0.1
Distribution: experimental
Urgency: medium
Maintainer: Milan Kupcevic <milan@debian.org>
Changed-By: Faidon Liambotis <paravoid@debian.org>
Closes: 948096 973031 983719
Changes:
 esptool (4.5.1+dfsg-0.1) experimental; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream release. (Closes: #983719)
     - Update debian/copyright to match upstream changes.
     - Update build dependencies: drop python3-pyaes, and add
       python3-bitstring, python3-cryptography, python3-reedsolo and
       python3-pkcs11.
   * Compile and ship the flasher stub for ESP8266, as well as the ESP32 RISC-V
     variants (currently ESP32-C2, ESP32-C3, ESP32-C6, ESP32-H2). Notably, this
     does not include the ESP32 Xtensa variants (ESP32, ESP32-S2 and ESP32-S3)
     as there is no working toolchain in Debian for these. (Closes: #948096)
   * While the full test suite is stripped out and cannot be executed, add a
     few superficial autopkgtests: an autodep8 one, as well as smoke tests by
     running --help in the target environment.
   * Various package hygiene changes:
     - Revamp the build process to use dh-python, pybuild and setuptools to
       build and install the binaries. This means we now ship the "esptool"
       Python module for other packages to use. (Closes: #973031)
     - Drop upstream patch "shebang", as that is not necessary with pybuild.
     - Add Rules-Requires-Root: no, to indicate that the package does not need
       root to build.
     - Drop debian/NEWS, as it only included a news item for a version older
       than oldstable.
     - Add support for the "nodoc" build profile.
     - Add upstream metadata.
     - Bump debhelper compatibility level from 10 to 13.
     - Bump Standards-Version to 4.6.2.
     - Add gbp.conf and switch to DEP-14 branch naming.
   * Stop shipping CONTRIBUTING.md and its respective .html. Contributors are
     encouraged to look in the upstream GitHub repository for the latest
     information on how to contribute to the upstream project.
Checksums-Sha1:
 36ceb2f748f4597e3a85353f64a22f55438acf0d 2200 esptool_4.5.1+dfsg-0.1.dsc
 85fe2fcd1a15bbb1ddc054b953b2e939f51887dd 357984 esptool_4.5.1+dfsg.orig.tar.xz
 84f7feb648860a09e7711303a9becbbe1f0894c8 8960 esptool_4.5.1+dfsg-0.1.debian.tar.xz
 88dddde98e72e48d837023066d6d156347bca35f 7729 esptool_4.5.1+dfsg-0.1_source.buildinfo
Checksums-Sha256:
 3824dd475d85ac565cfbcae7f9dbee307c15a2e416189cdee367944acff25de2 2200 esptool_4.5.1+dfsg-0.1.dsc
 b8ec8400b7f99c56921db0698d68f8868d8babcef3ce03a8f2eb3237677c8ee4 357984 esptool_4.5.1+dfsg.orig.tar.xz
 cfd1414a6264aa2bffd637434d976660bb28dae122a83b725f7d8743016bb8bb 8960 esptool_4.5.1+dfsg-0.1.debian.tar.xz
 fc4915e218b56a72f74167b4803675fe5dbd124639bd0bf51cae0c52b516f8cf 7729 esptool_4.5.1+dfsg-0.1_source.buildinfo
Files:
 d604cb23b5fee744e107e138215632be 2200 electronics optional esptool_4.5.1+dfsg-0.1.dsc
 09299c1738c8bcbec157c20c5be54d82 357984 electronics optional esptool_4.5.1+dfsg.orig.tar.xz
 4689482b5cb2d535cd2e464dd3ce81fe 8960 electronics optional esptool_4.5.1+dfsg-0.1.debian.tar.xz
 4b4afa2e2abe365ce4a3256e75c73b45 7729 electronics optional esptool_4.5.1+dfsg-0.1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEqVksUhy5BAd9ZZgAnQteWx7sjw4FAmQUWJ4ACgkQnQteWx7s
jw5mfA/+IlPeKnTDd36EMcLARlz7A1nYCOE+ykIXTCvVjaJuA2XMamGWRyRXpX57
ChW1QLKr2Vfakca7ralzzFT+C25y688nPO09gKSfmSNEfuNhHijNOuWV4QYseTTq
kKLc6pomVkoFbGBUkoiGWKH/JVGinGtF5Jcp2zQoyGg6b3gl3+BaNjIw/W4RgqRP
dkzKl+Xq/vl2bqlouFvk2ycQkDZLQDQy3YprohJF4vZmz3BkcwuwEO6HUEVkCx3q
DD6ALqdJaY5GODsmqrJ+R53a7DLDLXsIi3wBo3mJAjGOWWqmIKwlNajh+bElcLNt
hBE0r9fUWxr7HF3l8hKQEg9U7Y1sZSc4H0PE9kBT5bpA2UKOgH258ornPpqFp7/I
JFJXpbKgcqAJWu6/of4IiiRGyMfuFQib00nC24JKv0WdlpwLmMWAjtk0Cgf6dTLQ
o9fZ3xAt0eJiO8Oah7Wap0wE1mtxZkI1mf/4pDLMgUzax8hsp0aKZWH8dQuJJZdT
7FQkukUxOJdYiGJHFKsXWOl9Fa9y14VQ/2IsotktP0gzPUPokE2JzYZzwKzStqgb
i8tsltRIxWNgpWm50i2cfdeW3t1XoVoc0aP1B63sfYNlRZTONaAH7fYcaMT5un4b
zr3nBgkxLOS2KCckCbh06FvhP30vK8udh2GqkyJGodNSyOhUSQs=
=TLlM
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.