Was this a site you upgraded to 3.4beta 1 or a fresh install

An Upgrade from 3.6

Is this the error message that you get

Warning
Package Uninstall: Missing manifest file

Yes

Marking as confirmed

Raising priority to urgent so it is a blocker for 3.4. Should be fixed before RC.

Anyone care to take a guess why this check is saying the weblinks.php file doesn't exist (which is how the package manifest would be removed)? And yes, the package manifest is in the update package.

@mbabker isn't that check for when we are updating the CMS and won't get called when you uninstall weblinks through extension manager after updating to beta?

The issue is the manifest is not present, hence the error message @brianteeman posted. I did a test update on a local 3.3.6 install and found that the manifest was not in place. The only possible ways for that to happen is the file not included in the package or the file being deleted by the update script.

Making things more intriguing, I've tested 2 updates via the update component and both of those don't place the weblinks manifest in the filesystem. I tried an update through the Extension Manager's Install from URL option and it showed up.

I just realized why this is failing. The update server is serving the Full install package versus the update package. The full package doesn't have the weblinks package manifest since weblinks isn't installed for new installations.

The update server has been updated to serve the update package now versus the full package. Please test updates and uninstalling weblinks now.

When updating, please ensure the package URL displayed on the update screen indicates it is the update package. If it still says full, your site is pulling from a CDN node that has not yet refreshed.

@test

Works fine now.
Remains to get it on JED.