Bug#1018173: libreoffice: Please upload final releases
Hi,
Am 26.08.22 um 17:41 schrieb Rene Engelhard:
Am 26.08.22 um 15:55 schrieb Itaï BEN YAACOV:
1. I understand that unstable is the place to stage pre-release
software. But this
does not mean it must only contain such. Moreover, given Debian's
slow release cycle
some users (such as myself) use it for daily work, rather than for
testing new software.
Come on, it's not as if I uploaded alphas or betas to unstable. Just RCs.
Addendum to that: That's not what unstable and testing are for. It's
sole purpose is to prepare for the next release. That people use it like
you do is also true, but that is not it's purpose.
There is backports, too.
(Though I have been uploading those rcs there anyway, though less often,
I skipped 7.4.0 rcX for example. And the backports' rules demand of the
packages being in testing first.
So that would even mean uploading the final. wait for it to migrate. do
the thing.)
If the final release is indeed equal to some rc#, then, as pointless
as this may seem
to you, could you please just bump up the version number and upload
again as final?
And do a fuill build cycle on all architectures just for this? No.
Would you want to upload a release just to replace it with the next rc
when it gets out? Even more unneeded build cycles.
And not only that.
All the tests: see e.g.
https://qa.debian.org/excuses.php?package=libreoffice right now:
Issues preventing migration:
missing build on arm64
missing build on s390x
arch:arm64 not built yet, autopkgtest delayed there
arch:s390x not built yet, autopkgtest delayed there
autopkgtest for apparmor/3.0.7-1: amd64: Pass, armel: Test in progress,
armhf: Test in progress, i386: Test in progress, ppc64el: Test in progress
autopkgtest for grammalecte/2.1.2+ds2-1: amd64: Pass, armel: Test in
progress, armhf: Test in progress, i386: Test in progress, ppc64el: Test
in progress
autopkgtest for libnumbertext/1.0.10-1: amd64: Pass, armel: Test in
progress, armhf: Test in progress, i386: Test in progress, ppc64el: Test
in progress
autopkgtest for libreoffice/1:7.4.1~rc1-2: amd64: Pass, armel: Test in
progress (will not be considered a regression), armhf: Test in progress
(will not be considered a regression), i386: Test in progress (will not
be considered a regression), ppc64el: Test in progress (will not be
considered a regression)
autopkgtest for lloconv/6.1.0-3: amd64: Pass, armel: Test in progress,
armhf: Test in progress, i386: Test in progress, ppc64el: Test in progress
autopkgtest for natbraille/2.0rc3-13: amd64: No test results, armel:
Test in progress, armhf: Test in progress, i386: Test in progress,
ppc64el: Test in progress
autopkgtest for openlp/2.9.5-1: amd64: No test results, armel: Test in
progress, armhf: Test in progress, i386: Test in progress, ppc64el: Test
in progress
autopkgtest for paperwork/2.1.1-1: amd64: Pass, armel: Test in progress,
armhf: Test in progress, i386: Test in progress, ppc64el: Test in progress
autopkgtest for parlatype-libreoffice-extension/3.1.1-1: amd64: Pass,
armel: Test in progress (will not be considered a regression), armhf:
Test in progress, i386: Test in progress, ppc64el: Test in progress
and if you look at the build times, amd64 even takes 10 hours+, some
slower archs even 1 day or more. Just doing this for something which
will be overwritten anyway is a waste.
Would you want *only* upload of releases? Thus e.g. not getting all the
bugfixes in 7.4.1? That would be the consequence. I'll then tell you on
any bug "try the version in experimental, since that one is developed".
Do you want that instead?
Note that at some point in time I'll stick to releases, let alone for
the freeze.
I see that you didn't want that but that would be the consequence, let
alone not to do a "useless", time-wasting upload.
I actually even planned to just stick to releases when I uploaded a
release. (and already updated debian/watch for it)
Regards,
Rene
Reply to: