6.2.33 beta 2 #34
6.2.33 beta 2 #34
Conversation
| @@ -76,6 +75,7 @@ BuildRequires: perl(Cwd) | |||
| BuildRequires: perl(Data::Password) | |||
| BuildRequires: perl(DateTime) | |||
| BuildRequires: perl(DateTime::Format::Mail) | |||
| BuildRequires: perl(DBD::SQLite) | |||
There was a problem hiding this comment.
I guess this is a new requirement from the test suite ?
There was a problem hiding this comment.
Yes, it is used by a new test t/02_Sympa_DatabaseManager.t in sympa-community/sympa#336
sympa.spec
Outdated
| Provides: bundled(js-modernizr) = 2.8.3 | ||
| Provides: bundled(js-placeholder) = 2.0.9 | ||
| Provides: bundled(js-sizzle) = 2.2.0 | ||
| %endif |
There was a problem hiding this comment.
This part shouldn't be removed but updated for foundation 6:
%if %{unbundle_foundation}
Requires: js-foundation6
%else
Provides: bundled(js-foundation) = 6.4.2
# Bundled in bundled js-foundation
Provides: bundled(js-what-input) = 4.2.0
%endif
There was a problem hiding this comment.
I repushed commits according to your suggestion.
sympa.spec
Outdated
|
|
||
| Name: sympa | ||
| Version: 6.2.32 | ||
| Version: 6.2.33 | ||
| Release: %{?pre_rel:0.}2%{?pre_rel:.%pre_rel}%{?dist} |
There was a problem hiding this comment.
Nitpick, the '2' in the release field above should be '1' and the corresponding change should be applied to the changelog entry.
The release field needs to be reset to 1 (or 0.1 for a pre-release, but here the macros in the release field take care of the leading '0.' automagically) each time the version field is incremented (and also when the software goes from a pre-release to the final release, but this is not the case with Sympa, as next stable will be 6.2.34).
|
I understood. I re-pushed. |
Updates according to changes on upstream: