IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
this flag marks the file names as 'UTF-8' encoded if they are valid UTF-8.
By default, encoding of file names in zips are defined as code page 437,
but we save the filenames as bytes (like in linux fs).
For linux systems this would not be a problem since most tools
simply use the filenames as bytes, but for the zip utility under
windows it's important since NTFS uses UTF-16 for file names.
For filenames that are valid UTF-8, they are decoded as UTF-8 everywhere
correctly (Linux as UTF-8 bytes, Windows as correct UTF-16 sequence) and
for other filenames with a high bit set, it depends on the OS/Software
what exactly happens. Some cases below:
* Windows + Built-in/7zip: decoded as CP437
* Debian + zip: Bytes taken as-is
* Debian + 7z: interpreted as Windows1252, decoded as UTF-8
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
the doctest code uses non-public `fold`, up for re-evaluation if this
gets moved to proxmox-serde and made public..
Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
same as with sys/xattr, these touch files, so should use a tmpdir
provided by cargo, which requires them being integration tests.
if the tmpdir doesn't support O_TMPFILE (like overlayfs), the test is
not run (unfortunately, there is no way to indicate this via the test
result like with other test frameworks).
Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
these touch files, so should use the cargo-provided tmp dir, but that is
only available to benchmarks and integration tests, not unit tests.
Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
without these, the generated d/control files are incomplete and builds
fail on clean systems.
Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
will break usage of the `Result::Ok()' with anyhow 1.0.49+ as that
added a new Ok helper, so a glob-import would make that shadow the
core one.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
will break usage of the `Result::Ok()' with anyhow 1.0.49+ as that
added a new Ok helper, so a glob-import would make that shadow the
core one.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
like we do in pve. this breaks the (newly added) compute_next_event
method of CalendarEvent, but we can keep compatibilty with the
deprecated function
adapt the tests so that they add a ' UTC' by default
(so they can run reliably on any machine)
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
