apertis-flatdeb merge requestshttps://gitlab.apertis.org/pkg/apertis-flatdeb/-/merge_requests2023-08-08T13:05:32Zhttps://gitlab.apertis.org/pkg/apertis-flatdeb/-/merge_requests/28Fix lintian tags2023-08-08T13:05:32ZDylan AïssiFix lintian tagshttps://gitlab.apertis.org/pkg/apertis-flatdeb/-/merge_requests/27Update debian/apertis/copyright2023-06-14T08:25:17ZVignesh RamanUpdate debian/apertis/copyrighthttps://phabricator.apertis.org/T9521https://phabricator.apertis.org/T9521Apertis CI robotApertis CI robothttps://gitlab.apertis.org/pkg/apertis-flatdeb/-/merge_requests/26Add debian/apertis/lintian2023-01-24T13:34:47ZVignesh RamanAdd debian/apertis/lintianAdd debian/apertis/lintian to enable lintian job.
https://phabricator.apertis.org/T9470Add debian/apertis/lintian to enable lintian job.
https://phabricator.apertis.org/T9470https://gitlab.apertis.org/pkg/apertis-flatdeb/-/merge_requests/25Merge changes from apertis/v2022-updates into apertis/v20222022-09-21T06:28:15ZRitesh Raj SarrafMerge changes from apertis/v2022-updates into apertis/v2022https://gitlab.apertis.org/pkg/apertis-flatdeb/-/merge_requests/24Merge changes from apertis/v2021-updates into apertis/v20212022-09-15T10:55:15ZRitesh Raj SarrafMerge changes from apertis/v2021-updates into apertis/v2021https://gitlab.apertis.org/pkg/apertis-flatdeb/-/merge_requests/23Backport bundle-related fixes from v20222022-08-10T01:36:29ZRyan GonzalezBackport bundle-related fixes from v2022ci-flatdeb-builder always builds bundles, but that doesn't work out too well on v2021.
https://phabricator.apertis.org/T8509ci-flatdeb-builder always builds bundles, but that doesn't work out too well on v2021.
https://phabricator.apertis.org/T8509https://gitlab.apertis.org/pkg/apertis-flatdeb/-/merge_requests/22Merge updates from -v2023dev32022-07-26T10:56:32ZRitesh Raj SarrafMerge updates from -v2023dev3https://phabricator.apertis.org/T8219
Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>https://phabricator.apertis.org/T8219
Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>https://gitlab.apertis.org/pkg/apertis-flatdeb/-/merge_requests/21Merge changes from apertis/v2021-updates into apertis/v20212022-03-16T17:34:05ZRitesh Raj SarrafMerge changes from apertis/v2021-updates into apertis/v2021https://gitlab.apertis.org/pkg/apertis-flatdeb/-/merge_requests/20[Backport v2023dev1 -> v2022] apt-install: Pass --allow-remove-essential2022-03-02T16:36:49ZRyan Gonzalez[Backport v2023dev1 -> v2022] apt-install: Pass --allow-remove-essentialThis is needed in many cases when replacing packages from the target
repos, e.g. replacing busybox-gzip with GNU gzip. I considered making
this configurable, but it would have to be enabled for a large number of
SDKs regardless, so the r...This is needed in many cases when replacing packages from the target
repos, e.g. replacing busybox-gzip with GNU gzip. I considered making
this configurable, but it would have to be enabled for a large number of
SDKs regardless, so the risk isn't significantly greater by having it
always on.
Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>
<hr>
Note that I didn't backport the other v2023dev1 change for rust-findutils, since that would be higher risk given the v2022 freeze and wouldn't fix anything here.https://gitlab.apertis.org/pkg/apertis-flatdeb/-/merge_requests/19Fix compatibility with rust-findutils2022-01-28T14:38:28ZRyan GonzalezFix compatibility with rust-findutilsSigned-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>https://gitlab.apertis.org/pkg/apertis-flatdeb/-/merge_requests/18v2021: Import latest upstream changes2021-12-28T18:41:36ZEmanuele Ainaemanuele.aina@collabora.comv2021: Import latest upstream changesSync with Apertis 0.2021.2 to import the upstream changes.
Pull 44aa78d278d6 "Include flatpak metadata in OSTree commits" in
particular to fix errors when trying to use on v2022 flatpaks generated
on v2021:
Error: Commit metadata f...Sync with Apertis 0.2021.2 to import the upstream changes.
Pull 44aa78d278d6 "Include flatpak metadata in OSTree commits" in
particular to fix errors when trying to use on v2022 flatpaks generated
on v2021:
Error: Commit metadata for runtime/org.apertis.mildenhall.Platform/x86_64/v2021 not matching expected metadata
Task: https://phabricator.apertis.org/T8507https://gitlab.apertis.org/pkg/apertis-flatdeb/-/merge_requests/17apt-install: Pass --allow-remove-essential2021-11-29T10:01:34ZRyan Gonzalezapt-install: Pass --allow-remove-essentialThis is needed in many cases when replacing packages from the target
repos, e.g. replacing busybox-gzip with GNU gzip. I considered making
this configurable, but it would have to be enabled for a large number of
SDKs regardless, so the r...This is needed in many cases when replacing packages from the target
repos, e.g. replacing busybox-gzip with GNU gzip. I considered making
this configurable, but it would have to be enabled for a large number of
SDKs regardless, so the risk isn't significantly greater by having it
always on.
Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>Arnaud FerrarisArnaud Ferrarishttps://gitlab.apertis.org/pkg/apertis-flatdeb/-/merge_requests/16Fix a quoting error in the runtime YAML2021-11-09T09:42:43ZRyan GonzalezFix a quoting error in the runtime YAMLRemoving the `echo; ` resulted in the first character of the string
being a `"`, thus YAML only interpreted the text up until the next `"`
as the value, resulting in a syntax error.
This was definitely my bad for testing everything up u...Removing the `echo; ` resulted in the first character of the string
being a `"`, thus YAML only interpreted the text up until the next `"`
as the value, resulting in a syntax error.
This was definitely my bad for testing everything up until the last-minute removal of `echo;` 😅 Apologies for that!https://gitlab.apertis.org/pkg/apertis-flatdeb/-/merge_requests/14Add several features used for the reference runtime2021-11-04T17:06:19ZRyan GonzalezAdd several features used for the reference runtimeThis adds various functionality that I've been adding over the past few days for the [new reference runtime](https://gitlab.apertis.org/infrastructure/apertis-flatpak-runtime). The gist of it is:
- Runtimes can extend each other (used s...This adds various functionality that I've been adding over the past few days for the [new reference runtime](https://gitlab.apertis.org/infrastructure/apertis-flatpak-runtime). The gist of it is:
- Runtimes can extend each other (used so the HMI runtime can extend the headless one).
- `pre_apt_script` is available in an SDK-specific form (used to make sure `development` repos never end up in the platform variant).
- `--override-package` can be used to override specific packages to custom deb files (this is mostly just useful for testing purposes).
- Locales can be extracted into their own extension.
- Bundles now end in `.flatpak`, to make them easier to install.
- Custom overlays can be added on top of the runtime's filesystem (used to add custom fontconfig files).
- The font cache can be preserved after building.https://gitlab.apertis.org/pkg/apertis-flatdeb/-/merge_requests/15Fix build issues for arm64 applications2021-11-03T21:20:34ZArnaud FerrarisFix build issues for arm64 applicationsWhile building an application Flatpak from .deb packages, we experience
failures when targeting the arm64 architecture. This MR fixes those by:
- allowing to run commands without calling them through `fakeroot`
- working around an issue ...While building an application Flatpak from .deb packages, we experience
failures when targeting the arm64 architecture. This MR fixes those by:
- allowing to run commands without calling them through `fakeroot`
- working around an issue where the arm64 `ldconfig` makes qemu crash on
amd64 hosts.Ryan GonzalezRyan Gonzalezhttps://gitlab.apertis.org/pkg/apertis-flatdeb/-/merge_requests/12Enable ED25519 signatures2021-10-14T10:27:55ZArnaud FerrarisEnable ED25519 signaturesIn order to publish verified runtimes and applications that can be
checked using ED25519 keys, this commit adds the `--sign` and
`--sign-type` command-line options with the same semantic as their
`flatpak` and `ostree` counterparts:
- `-...In order to publish verified runtimes and applications that can be
checked using ED25519 keys, this commit adds the `--sign` and
`--sign-type` command-line options with the same semantic as their
`flatpak` and `ostree` counterparts:
- `--sign` must be followed by a base64-encoded secret key
- `--sign-type` indicates the signature type (default, and only valid
value, is `ed25519`)https://gitlab.apertis.org/pkg/apertis-flatdeb/-/merge_requests/11Merge changes from apertis/v2021-updates into apertis/v20212021-09-21T06:28:45ZRitesh Raj SarrafMerge changes from apertis/v2021-updates into apertis/v2021https://gitlab.apertis.org/pkg/apertis-flatdeb/-/merge_requests/10Add Priority: optional to package2021-09-14T14:00:14ZRitesh Raj SarrafAdd Priority: optional to packageWithout it, other tools fall apart, like:
```
Sep 14 11:53:57 niobium bs_publish[6672]: .changes put in a distribution not listed within it!
Sep 14 11:53:57 niobium bs_publish[6672]: Ignoring as --ignore=wrongdistribution given.
Sep 14 ...Without it, other tools fall apart, like:
```
Sep 14 11:53:57 niobium bs_publish[6672]: .changes put in a distribution not listed within it!
Sep 14 11:53:57 niobium bs_publish[6672]: Ignoring as --ignore=wrongdistribution given.
Sep 14 11:53:57 niobium bs_publish[6672]: No priority specified for '/srv/obs/repos/apertis:/v2022dev3:/sdk/default/x86_64/apertis-flatdeb_0.2021.1bv2022dev3b3_amd64.changes'!
```
Never the less, per Debian Policy too, this is a must have attribute
```
Each package must have a priority value, which is set in the metadata for the Debian archive and is also included in the package’s control files (see Priority). This information is used to control which packages are included in standard or minimal Debian installations.
```
Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>https://gitlab.apertis.org/pkg/apertis-flatdeb/-/merge_requests/9Add Priority: optional to package2021-09-14T13:10:53ZRitesh Raj SarrafAdd Priority: optional to packageWithout it, other tools fall apart, like:
```
Sep 14 11:53:57 niobium bs_publish[6672]: .changes put in a distribution not listed within it!
Sep 14 11:53:57 niobium bs_publish[6672]: Ignoring as --ignore=wrongdistribution given.
Sep 14 ...Without it, other tools fall apart, like:
```
Sep 14 11:53:57 niobium bs_publish[6672]: .changes put in a distribution not listed within it!
Sep 14 11:53:57 niobium bs_publish[6672]: Ignoring as --ignore=wrongdistribution given.
Sep 14 11:53:57 niobium bs_publish[6672]: No priority specified for '/srv/obs/repos/apertis:/v2022dev3:/sdk/default/x86_64/apertis-flatdeb_0.2021.1bv2022dev3b3_amd64.changes'!
```
Never the less, per Debian Policy too, this is a must have attribute
```
Each package must have a priority value, which is set in the metadata for the Debian archive and is also included in the package’s control files (see Priority). This information is used to control which packages are included in standard or minimal Debian installations.
```
Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>https://gitlab.apertis.org/pkg/apertis-flatdeb/-/merge_requests/8Merge latest upstream version into apertis-flatdeb2021-06-17T18:46:06ZArnaud FerrarisMerge latest upstream version into apertis-flatdebNewer versions of flatpak, including the one currently in v2022dev2, require metadata to be added to the OSTree commit. This has been implemented in upstream `flatdeb`, so merging the latest commits should be enough to get the missing bits.Newer versions of flatpak, including the one currently in v2022dev2, require metadata to be added to the OSTree commit. This has been implemented in upstream `flatdeb`, so merging the latest commits should be enough to get the missing bits.