# Mender-client 4.0.0-1+debian+bullseye **URL:** \ **Category:** General Discussions\ **Tags:** mender-client\ **Created:** [January 17, 2024, 1:42am UTC](https://hub.mender.io/t/mender-client-4-0-0-1-debian-bullseye/6485 "2024-01-17T01:42:55Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![bssi](https://avatars.discourse-cdn.com/v4/letter/b/ac91a4/32.png) [@bssi](https://hub.mender.io/u/bssi)\ **Post date:** [January 17, 2024, 1:42am UTC](https://hub.mender.io/t/mender-client-4-0-0-1-debian-bullseye/6485/1 "2024-01-17T01:42:55Z")
Hello, I noticed that the version of `mender-client` in your Debian bullseye repo has changed from `3.5.2-1+debian+bullseye` to `4.0.0-1+debian+bullseye`, but I don’t see any reference to 4.0.0 in your release notes or general documentation. When will you be publishing release notes and updating documentation? [https://docs.mender.io/release-information/release-notes-changelog/mender-client](https://docs.mender.io/release-information/release-notes-changelog/mender-client) [https://docs.mender.io/overview/compatibility](https://docs.mender.io/overview/compatibility) [https://docs.mender.io/release-information/release-schedule](https://docs.mender.io/release-information/release-schedule) Cheers, Zach ---
**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\ **Post date:** [January 17, 2024, 8:14am UTC](https://hub.mender.io/t/mender-client-4-0-0-1-debian-bullseye/6485/2 "2024-01-17T08:14:17Z")
Hi @bssi, We are just executing the release process for the 4.0 client, the corresponding resources will be updated soon. Greets, Josef ---
**Author:** ![mdbellrd](https://avatars.discourse-cdn.com/v4/letter/m/d07c76/32.png) [@mdbellrd](https://hub.mender.io/u/mdbellrd)\ **Post date:** [January 17, 2024, 3:45pm UTC](https://hub.mender.io/t/mender-client-4-0-0-1-debian-bullseye/6485/3 "2024-01-17T15:45:55Z")
Is the release process complete? When attempting to install mender on a new device via the install script, it seems to complete successfully, installing 4.0.0. However the mender binary /usr/bin/mender doesn’t exist, and causes other mender services to fail. Is there any way to install 3.5.2? We have that version working on other devices, however it doesn’t seem to be in the apt repo anymore. ---
**Author:** ![mmetzler](https://avatars.discourse-cdn.com/v4/letter/m/b38774/32.png) [@mmetzler](https://hub.mender.io/u/mmetzler)\ **Post date:** [January 17, 2024, 4:24pm UTC](https://hub.mender.io/t/mender-client-4-0-0-1-debian-bullseye/6485/4 "2024-01-17T16:24:08Z")
It appears the mender binary was renamed to mender-update, I was able to get around this without changing my application with: `ln -s /usr/bin/mender-update /usr/bin/mender` However, I am unable to get standalone updates to work as `mender-update commit` errors with no update pending; while `fw_printenv` does indicate one (`upgrade_avaliable=1`). Getting access to 3.5.2 for now so I can get this update shipped would be good. It appears I will need to alter my application to support 4.0.0. ---
**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\ **Post date:** [January 17, 2024, 4:44pm UTC](https://hub.mender.io/t/mender-client-4-0-0-1-debian-bullseye/6485/5 "2024-01-17T16:44:24Z")
Hi @mmetzler and @mdbellrd, I’m really sorry for the inconvenience this is causing! Yes, the `mender` binary has been split and renamed into `mender-auth`, `mender-update` and `mender-setup`. This offers a few benefits, like not shipping the setup logic to all devices which do not need them, or being able to install `mender-connect` without the update component. The release process is taking a bit longer as it is more moving parts therefore, and I want to apologise for the issues this causes while its going on. For the install script, its source is located at [mender-dist-packages/scripts/install-mender.sh at master · mendersoftware/mender-dist-packages · GitHub](https://github.com/mendersoftware/mender-dist-packages/blob/master/scripts/install-mender.sh), and you should be able to just use the last version for now, respectively stick with the releases on the 3.5.2 tag. We appreciate the feedback, it helps us make the new client better. Thank you for your contributions! Greets, Josef ---
**Author:** ![scscscsc](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/scscscsc/32/2090_2.png) [@scscscsc](https://hub.mender.io/u/scscscsc)\ **Post date:** [January 17, 2024, 5:16pm UTC](https://hub.mender.io/t/mender-client-4-0-0-1-debian-bullseye/6485/6 "2024-01-17T17:16:37Z")
@TheYoctoJester - Please put the 3.5.2 version back on [https://downloads.mender.io/repos/debian](https://downloads.mender.io/repos/debian) … it is absolutely crazy that the Mender team would nuke all 3.x.x versions off their Debian repo in order to post 4.x.x that is a major rev and is incompatible with how 3.x.x was used. Great that everything was split up, but as I’m sure you know, Mender is widely used in IoT device firmware builds that heavily depend on having a controlled setup - and, for us, that setup means knowing exactly where/how the mender-client is working and being able to replace mender-device-identity, which used to be part of the mender-client deb package … now all of our firmware builds are broken and we need to spend a bunch of time figuring out how to migrate to v4 and then do full integration testing after we make the migration before we have a usable build again… which is likely a week or more of downtime. Here is the full list of what we now have access to: ```auto $ apt update $ rmadison mender-client mender-client | 2.1.2-2 | focal/universe | source, amd64, arm64, armhf, ppc64el, s390x mender-client | 2.1.2-2ubuntu0.2 | focal-security/universe | source, amd64, arm64, armhf, ppc64el, riscv64, s390x mender-client | 2.1.2-2ubuntu0.2 | focal-updates/universe | source, amd64, arm64, armhf, ppc64el, riscv64, s390x mender-client | 3.0.0+ds1-2 | jammy/universe | source, amd64, arm64, armhf, ppc64el, riscv64, s390x mender-client | 3.4.0+ds1-5 | lunar/universe | source, amd64, arm64, armhf, ppc64el, riscv64, s390x mender-client | 3.4.0+ds1-5build1 | mantic/universe | source, amd64, arm64, armhf, ppc64el, riscv64, s390x mender-client | 3.4.0+ds1-5build1 | noble/universe | source, amd64, arm64, armhf, ppc64el, riscv64, s390x ``` On [Release version and schedule | Mender documentation](https://docs.mender.io/release-information/release-schedule) under `Current LTS releases` there is a note that says: > **Please note:** 3.5 was initially released as an LTS but has since been withdrawn because of technical reasons. Due to the delays in releasing the next LTS (3.6), the support duration for 3.3 has been extended. So, was 3.5.2 nuked because of this? If so, where is 3.6? ---
**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\ **Post date:** [January 17, 2024, 5:32pm UTC](https://hub.mender.io/t/mender-client-4-0-0-1-debian-bullseye/6485/7 "2024-01-17T17:32:55Z")
Hi @scscscsc, I fully agree that this is a problematic situation. Already doing my best to escalate things. Concerning the release notes, this is a bit confusing as the Mender Client version numbers move against each other. The 3.6 full release did not include a new client as there was no changes at that time, hence 3.5.2 is still the current one. Greets, Josef ---
**Author:** ![bssi](https://avatars.discourse-cdn.com/v4/letter/b/ac91a4/32.png) [@bssi](https://hub.mender.io/u/bssi)\ **Post date:** [January 17, 2024, 5:39pm UTC](https://hub.mender.io/t/mender-client-4-0-0-1-debian-bullseye/6485/8 "2024-01-17T17:39:48Z")
Hi @TheYoctoJester, I am glad you are escalating this. Much appreciated… Thank you! To give you more ammunition as you advocate on our behalf I would like to second @scscscsc’s motion to put 3.5.2 back in the repo… We are just about to start shipping a batch of production systems on a very tight timeline and absolutely the last thing we need at this juncture is to take additional precious time to migrate to and QA mender-client 4.0.0. In general we would never migrate directly to a X.0.0 release of anything if it could possibly be avoided. Especially something mission critical like our OTA update solution. Cheers, Zach ---
**Author:** ![cspensky](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/cspensky/32/2055_2.png) [@cspensky](https://hub.mender.io/u/cspensky)\ **Post date:** [January 17, 2024, 5:41pm UTC](https://hub.mender.io/t/mender-client-4-0-0-1-debian-bullseye/6485/9 "2024-01-17T17:41:34Z")
I am also seeing big issues here. I wanted to release an update yesterday, but during testing realized that the `mender` binary was missing, which meant the update would succeed, but the firmware would **NEVER** reconnect to mender. Had we not caught this, we could have nuked our entire fleet of deployed devices (the website still just says “rebooting”). Any help in the interim would be much appreciated. ---
**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\ **Post date:** [January 17, 2024, 5:44pm UTC](https://hub.mender.io/t/mender-client-4-0-0-1-debian-bullseye/6485/10 "2024-01-17T17:44:50Z")
@scscscsc @bssi I might have at least a workaround soon. Will keep you posted. ---
**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\ **Post date:** [January 17, 2024, 5:51pm UTC](https://hub.mender.io/t/mender-client-4-0-0-1-debian-bullseye/6485/11 "2024-01-17T17:51:53Z")
@bssi @scscscsc I could get the repository situation looked into. The packages are still there, just not in the index. You can still pull them via ```auto wget https://downloads.mender.io/repos/debian/pool/main/m/mender-client/mender-client_3.5.2-1+DIST+NAME_ARCH.deb ``` which for example Debian Buster on amd64 results in ```auto wget https://downloads.mender.io/repos/debian/pool/main/m/mender-client/mender-client_3.5.2-1+debian+buster_amd64.deb ``` Hope this gets you going again! Greets, Josef ---
**Author:** ![bssi](https://avatars.discourse-cdn.com/v4/letter/b/ac91a4/32.png) [@bssi](https://hub.mender.io/u/bssi)\ **Post date:** [January 17, 2024, 6:39pm UTC](https://hub.mender.io/t/mender-client-4-0-0-1-debian-bullseye/6485/12 "2024-01-17T18:39:51Z")
@TheYoctoJester Thank you. We’ll still have to adjust our build, but far preferred than having to make an unplanned migration to 4.0.0! ---
**Author:** ![scscscsc](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/scscscsc/32/2090_2.png) [@scscscsc](https://hub.mender.io/u/scscscsc)\ **Post date:** [January 17, 2024, 9:27pm UTC](https://hub.mender.io/t/mender-client-4-0-0-1-debian-bullseye/6485/13 "2024-01-17T21:27:53Z")
@TheYoctoJester - Thank you, this got our builds working again and should hold us over until this is properly resolved. ---
**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\ **Post date:** [January 18, 2024, 8:15pm UTC](https://hub.mender.io/t/mender-client-4-0-0-1-debian-bullseye/6485/14 "2024-01-18T20:15:51Z")
@scscscsc @bssi @cspensky @mmetzler @mdbellrd Please see [Update and statement on the Mender Client 4.0 Debian package incident](https://hub.mender.io/t/update-and-statement-on-the-mender-client-4-0-debian-package-incident/6497) for more details.