- Nov 02, 2022
-
-
Guido Gunther authored
-
Guido Gunther authored
They were a plain copy of what Debian uses.
-
Guido Gunther authored
-
- Aug 14, 2022
-
-
Evangelos Ribeiro Tzaras authored
1.0-ds1-4pureos2 got rejected because we target `unstable` by mistake. See https://lists.community.puri.sm/pipermail/librem5-builds/2022-August/004135.html
-
- Aug 13, 2022
-
-
Evangelos Ribeiro Tzaras authored
-
Evangelos Ribeiro Tzaras authored
-
Evangelos Ribeiro Tzaras authored
See packaging practices at https://tracker.pureos.net/w/development/
-
- Aug 12, 2022
-
-
Evangelos Ribeiro Tzaras authored
-
- Aug 10, 2022
-
-
Federico Ceratto authored
-
- Aug 08, 2022
-
-
Federico Ceratto authored
Packaging tweaks and bump version See merge request debian/tootle!2
-
- Jul 28, 2022
-
-
Evangelos Ribeiro Tzaras authored
The old version in the archive was 1.0-alpha2-1+b1. We need to use a version considered greater than this: > $ dpkg --compare-versions '1.0-4' '>>' '1.0-alpha2-1+b1' && echo true || echo false false > $ dpkg --compare-versions '1.0-really1.0-1' '>>' '1.0-alpha2-1+b1' && echo true || echo false true
-
Evangelos Ribeiro Tzaras authored
-
Evangelos Ribeiro Tzaras authored
-
Evangelos Ribeiro Tzaras authored
This warning arises because sed invocation gets rid of the %u originally present in the desktop file. Change the sed invocation to the following: $ sed 's/^Exec=.*\s\(.*\)/Exec=tootle \1/g' Exec=com.github.bleakgrey.tootle %u Exec=tootle %u
-
Evangelos Ribeiro Tzaras authored
-
Federico Ceratto authored
Fix a couple of build related issues and prepare 1.0-4 release See merge request debian/tootle!1
-
- Jul 21, 2022
-
-
Evangelos Ribeiro Tzaras authored
-
Evangelos Ribeiro Tzaras authored
The old version used optional construct (only?) setters in Widgets/Status.vala like so: publi API.NotificationType? kind { get; construct set; } With newer vala this leads to build failures, because "construct" is not allowed for this property (presumably because '?' marks it as optional). The constructor uses a default value of `null` for the kind (API.NotificationType). We emulate the old behaviour by making the property mandatory (removing '?'), adding an 'UNSET' to the enum, defaulting to it and adjusting the `== null` checks to use `UNSET`.
-
- Jul 12, 2022
-
-
Evangelos Ribeiro Tzaras authored
These are related to newer vala having introduces some additional constrains on e.g. property naming.
-
Evangelos Ribeiro Tzaras authored
-
- Sep 19, 2021
-
-
Federico Ceratto authored
-
Federico Ceratto authored
-
Federico Ceratto authored
-
- Sep 05, 2021
-
-
Federico Ceratto authored
-
- Aug 19, 2021
-
-
Federico Ceratto authored
-
- Jul 03, 2021
-
-
Federico Ceratto authored
-
Federico Ceratto authored
Changes-By: lintian-brush Fixes: lintian: out-of-date-standards-version See-also: https://lintian.debian.org/tags/out-of-date-standards-version.html
-
- Feb 03, 2021
-
-
Federico Ceratto authored
-
Federico Ceratto authored
-
Federico Ceratto authored
Update to upstream version '1.0' with Debian dir 8ca43dd97f20ac75a2ac0848a256049be5534344
-
Federico Ceratto authored
-
- Feb 02, 2021
-
-
Federico Ceratto authored
-
- Oct 30, 2020
-
-
Federico Ceratto authored
-
Federico Ceratto authored
-
Federico Ceratto authored
-
Federico Ceratto authored
Update to upstream version '1.0-alpha2' with Debian dir 21778437822725ff3f8aaf27d3154d4b3e2ed46d
-
Federico Ceratto authored
-
Federico Ceratto authored
-
- Sep 20, 2020
-
-
Federico Ceratto authored
-
Federico Ceratto authored
-