From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Tim Marx <t.marx@proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>,
Shan Shaji <s.shaji@proxmox.com>
Subject: Re: [pve-devel] [PATCH pve_flutter_frontend v1] chore: update `compileSdkVersion` to 35 and `targetSdkVersion` to 36
Date: Thu, 3 Jul 2025 16:28:12 +0200 [thread overview]
Message-ID: <071ad35a-7647-4258-ae6d-c0b01ea89581@proxmox.com> (raw)
In-Reply-To: <1587343457.1306.1751552427256@webmail.proxmox.com>
Am 03.07.25 um 16:20 schrieb Tim Marx:
>> Dominik Csapak <d.csapak@proxmox.com> hat am 03.07.2025 16:03 CEST geschrieben:
>>
>>
>> LGTM, and built + tested fine here,
>> but maybe someone else also wants to take a look too... (@thomas?)
>>
>> Does it even make sense to set the targetSdkVersion higher than the compiled one?
>>
> I don't think so, this is the version the app should be tested against.
> https://developer.android.com/guide/topics/manifest/uses-sdk-element?hl=en
>
> The only combination that is probably valid, would be a lower targetsdkversion than the compilesdkversion.
You probably meant to say invalid - but yes, that combination cannot work.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-07-03 14:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 9:10 Shan Shaji
2025-07-03 14:03 ` Dominik Csapak
2025-07-03 14:20 ` Tim Marx
2025-07-03 14:28 ` Thomas Lamprecht [this message]
2025-07-03 14:25 ` Thomas Lamprecht
2025-07-03 14:45 ` Dominik Csapak
2025-07-03 14:56 ` Thomas Lamprecht
2025-07-03 15:18 ` Tim Marx
2025-07-04 6:52 ` Shan Shaji
2025-07-04 8:53 ` Thomas Lamprecht
2025-07-04 11:15 ` Shan Shaji
2025-07-07 9:51 ` Shan Shaji
2025-07-03 14:36 ` [pve-devel] applied: " Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=071ad35a-7647-4258-ae6d-c0b01ea89581@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.shaji@proxmox.com \
--cc=t.marx@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.