Incorrect syscall in some sandbox error messages

These are probably the result of some copy-pasting.

changed milestone to %Tor: 0.3.2.x-final in legacy/trac

added component::core tor/tor in Legacy / Trac milestone::Tor: 0.3.2.x-final in Legacy / Trac priority::medium in Legacy / Trac resolution::fixed in Legacy / Trac severity::minor in Legacy / Trac status::closed in Legacy / Trac type::defect in Legacy / Trac version::tor 0.2.5.1-alpha in Legacy / Trac labels

Trac:
0001-Use-the-proper-syscall-in-sandbox-error-messages.patch

The issue is present across multiple versions with the oldest being 0.2.5.1-alpha.

The commits that introduced the issues are 8a85a48b for function sb_stat64 on 0.2.5.1-alpha and dd7c9996 for functions sb_chmod and sb_chown on tor-0.2.8.2-alpha

I didn't feel like splitting such a simple patch in two and basing each part on a different maintenance branch so its based on master instead.

Trac:
Status: new to needs_review
Version: N/A to Tor: 0.2.5.1-alpha

I think it's fine to take these in master.

Trac:
Status: needs_review to merge_ready
Milestone: N/A to Tor: 0.3.2.x-final

Merged to master; thank you!

Trac:
Resolution: N/A to fixed
Status: merge_ready to closed

You've added your own changes file, but the patch already includes one so now there are two (changes/ticket22750 and changes/bug22750).

Trac:
Resolution: fixed to N/A
Status: closed to reopened

removed one. thanks!

Trac:
Status: reopened to closed
Resolution: N/A to fixed

closed

moved from legacy/trac#22750 (moved)

added Bug label and removed 1 deleted label

removed 1 deleted label