1,574
edits
Changes
Jump to navigation
Jump to search
Line 355:
Line 355: − + − − Line 383:
Line 381: − + − − Line 402:
Line 398: − + − + − + − + − + − + − + − + − + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
→UNDERSTANDING PACKAGES IN SMETEST AND SMEUPDATES-TESTING
They may not need to be released, but at least they need to be understood.
They may not need to be released, but at least they need to be understood.
Packages found in smetest:
Packages found in smetest: /smeserver/releases/7/smetest/SRPMS (includes contribs & upstream)
/smeserver/releases/7/smetest/SRPMS (includes contribs & upstream)
:clamav-0.97.6-1.rf.src.rpm
:clamav-0.97.6-1.rf.src.rpm
:e-smith-base-5.0.0-17.el4.sme.src.rpm
:e-smith-base-5.0.0-17.el4.sme.src.rpm
:unrar-4.2.3-1.rf.src.rpm
:unrar-4.2.3-1.rf.src.rpm
Packages found in smeupdates-testing
Packages found in smeupdates-testing: /smeserver/releases/7/smeupdates-testing/SRPMS/
/smeserver/releases/7/smeupdates-testing/SRPMS/
:clamav-0.97.5-2.rf.src.rpm
:clamav-0.97.5-2.rf.src.rpm
:e-smith-apache-2.0.0-7.el4.sme.src.rpm
:e-smith-apache-2.0.0-7.el4.sme.src.rpm
Packages to be moved from smetest into smeupdates-testing fall into two distinct categories:
Packages to be moved from smetest into smeupdates-testing fall into two distinct categories:
a) “SME Server Core packages”
:a) “SME Server Core packages”
e-smith-base-5.0.0-17.el4.sme.src.rpm * Wed Jul 18 2012 Ian Wells <esmith@wellsi.com> 5.0.0-17.sme - Make CipherSuite secure by default [SME: 6141]
:*e-smith-base-5.0.0-17.el4.sme.src.rpm * Wed Jul 18 2012 Ian Wells <esmith@wellsi.com> 5.0.0-17.sme - Make CipherSuite secure by default [SME: 6141]
qpsmtpd-0.83-0.9.el4.sme.src.rpm * Wed Jul 18 2012 Ian Wells <esmith@wellsi.com> 0.83-0.9.sme - Fix fatal errors when mail has no headers [SME: 6386]
:*qpsmtpd-0.83-0.9.el4.sme.src.rpm * Wed Jul 18 2012 Ian Wells <esmith@wellsi.com> 0.83-0.9.sme - Fix fatal errors when mail has no headers [SME: 6386]
smeserver-qpsmtpd-2.0.0-9.el4.sme.src.rpm * Wed Jul 18 2012 Ian Wells <esmith@wellsi.com> 2.0.0-9.sme - Revert the 2.0.0-8 change and fix properly in e-smith-base [SME: 6141]
:*smeserver-qpsmtpd-2.0.0-9.el4.sme.src.rpm * Wed Jul 18 2012 Ian Wells <esmith@wellsi.com> 2.0.0-9.sme - Revert the 2.0.0-8 change and fix properly in e-smith-base [SME: 6141]
b) “upstream” packages
:b) “upstream” packages
clamav-0.97.6-1.rf.src.rpm
:clamav-0.97.6-1.rf.src.rpm
perl-DBI-1.621-1.rfx.src.rpm
:perl-DBI-1.621-1.rfx.src.rpm
perl-NetAddr-IP-4.061-1.rf.src.rpm
:perl-NetAddr-IP-4.061-1.rf.src.rpm
pv-1.3.1-1.rf.src.rpm
:pv-1.3.1-1.rf.src.rpm
Once all the relevant packages are in smeupdates-testing some sensible discussion can be had on what testing is outstanding, and what can be released.
Once all the relevant packages are in smeupdates-testing some sensible discussion can be had on what testing is outstanding, and what can be released.
==PACKAGES UPDATE CYCLE==
The life of packages under the responsibility of the updatesteam starts in smetest. Leaving aside contribs (they are the responsibility of individual maintainers), there are three distinct scenarios:
First scenario: SME modified packages
- Step one. Packages created in smetest should be summarely tested by the developer to ensure that it installs correctly. Particular attention should be given to accurate changelog including a reference to the bug report. The bug is then resolved FIXED, and a copy of the changelog including package name provided at time of resolution.
-Step two. The package can then be moved by the developer to smeupdates-testing. In practice, members of the updatesteam should ensure that the move has been done, and move all relevant packages on a weekly basis.
- Step three. Verification takes place, the bug is either REOPENED or resolved VERIFIED. Updatesteam to circulate request for comment about release after having ensured that all deps are satisfied. This could be scheduled in batch weekly unless urgent fix.
- Step four. The package is then moved to smeupdates for release, release notes issued and possibly announce in the Forums if applicable. This could be scheduled in batch weekly unless urgent fix.
Second scenario: clamav packages
- Step one. Updatesteam raises a bug as soon as packages appear in smetest.
- Step two. Moved to updates-testing.
- Step three. Fast track verification and release + release notes.
Third scenario: Upstream packages and kernel mods excluding clamav
- Step one. Identify relevant packages by looking at all the RPMs, Changelogs, and Bugzilla. To find the upstream RPMs compare smetest to smeos. Rnotes simplify this process.
- Step two. Relevant packages are moved to updates-testing.
- Step three. Some testing may take place.
[To be clarified.]
- Step four. If satisfied, packages are moved to updates.
- Step five. No formal release notes, but Ian usually send an email and post to the forums a list of packages, e.g:
Subject: [updatesannounce] SME Server 7 Update: Upstream packages 01 December 2012
Date: Sat, 01 Dec 2012 18:28:21 -0800
From: Ian Wells <esmith@wellsi.com>
To: updatesannounce@contribs.org
SME Server 7 Update: Upstream packages 01 December 2012
Here is the list of upstream packages that were pushed as updates.
gifsicle-1.67-1.el4.rf.i386.rpm
perl-DBI-1.621-1.el4.rfx.i386.rpm
perl-NetAddr-IP-4.061-1.el4.rf.i386.rpm
pv-1.3.1-1.el4.rf.i386.rpm
___________________________________________
Announcement of maintenance updates for SME Server
To unsubscribe, e-mail updatesannounce-unsubscribe@lists.contribs.org
Searchable archive at http://lists.contribs.org/mailman/public/updatesannounce/
Issues to clarify for upstream packages NOT found in smeos:
For version 7.6, in test, we find a package not listed in Rnotes dated June 2012 (test tab):
/home/chris/smereleases/releases/7.6/smetest/SRPMS/unrar-4.2.3- 1.rf.src.rpm
An older package can be found in smeaddons dated Jan 2012:
/home/chris/smereleases/releases/7.6/smeaddons/SRPMS/unrar-4.1.4- 1.rf.src.rpm
how do you deal with this class of packages?
How do you generally deal with upstream packages not found in smeos?
==ABOUT THE MIRRORS==
Ibiblio appears to be unreliable, making it difficult to track changes. This is because Ibiblio is experiencing intermittent full hard drive issues. All downstream mirrors from them thus also have issues. Historically ibiblio was the place to see if packages had propagated out of the buildsys. We've recently moved our primary mirror to the CA mirror (mirror.canada.pialasse.com). That is the one that you should check for what should actually be on the mirrors.
Observation: I just refreshed (rsync) my tree against
distro.ibiblio.org::smeserver
1354247245 - www.smeserver.org - Fri, 30 Nov 2012 03:47:25 +0000
Traces are:
Fri Nov 30 03:48:16 UTC 2012
Used ftpsync version: 80387
Running on host: canada.canada.pialasse.com
Fri Nov 30 03:48:27 UTC 2012
Used ftpsync version: 80387
Running on host: login1.ibiblio.org
Question: When doing rsync from Ibilbio, are we pulling packages from
the new primary mirrors at pialasse.com only, or a mix of Ibiblio and CA?