Differences between revisions 49 and 50
Revision 49 as of 2014-06-11 16:00:05
Size: 2647
Editor: ?SalvatoreBonaccorso
Comment:
Revision 50 as of 2014-06-14 17:41:14
Size: 2958
Editor: JensKorte
Comment: special permissions for lts-needed.txt needed
Deletions are marked like this. Additions are marked like this.
Line 24: Line 24:
In order to prevent duplication of effort, make sure the issue is listed in [[https://anonscm.debian.org/viewvc/secure-testing/data/lts-needed.txt?view=log|lts-needed.txt]] and
add your name to it.
In order to prevent duplication of effort, make sure the issue is listed in [[https://anonscm.debian.org/viewvc/secure-testing/data/lts-needed.txt?view=log|lts-needed.txt]] and add your name to it.

You need to be member of secure-testing alioth project. Unfortunatel
y it still does not work to commit to the repository being a Debian Developer (which should, as the roles are set accordingly, but permissions are still broken on alioth). [[https://lists.debian.org/debian-lts/2014/06/msg00107.html|Source]]

Debian squeeze (6.0) LTS development

Add squeeze-lts to your sources.list

The information moved to LTS/Using.

Contribute

You can help in many ways

Report Bugs

Please report bugs that you found in the packages to the debian-lts mailinglist

Preparing fixed packages for squeeze-lts

Claim the issue in lts-needed.txt

In order to prevent duplication of effort, make sure the issue is listed in lts-needed.txt and add your name to it.

You need to be member of secure-testing alioth project. Unfortunately it still does not work to commit to the repository being a Debian Developer (which should, as the roles are set accordingly, but permissions are still broken on alioth). Source

Building the update

Backport the fix to the version in squeeze or squeeze-lts (in case there's already been an earlier update). You need to set the target distribution in debian/changelog to "squeeze-lts". The versioning follows the conventions already used in security.debian.org. Historically codenames have been used as version numbers, but this was changed some time ago as version numbers are more deterministic.

  • If a package already e.g. had a +squeeze1 update, use +squeeze2 for the next update.
  • If a package hasn't seen an update, use +deb6u1 for the next update.

Now build the package and run your tests. You can generate a debdiff and post it to debian-lts@lists.debian.org for review.

Now test the fixed package. If you're satisfied, upload to ftp-master. If you use dput-ng, you need to apply the patch from 745806. After that "dput CHANGES file" is sufficient. Once uploaded the package will be auto-built for amd64 or i386 (if it's an arch:any package).

Announcing the update

Now that the update has been released, send a mail to the debian-lts-announce mailing list. The mail needs to be signed by a PGP key in the debian.org or debian-maintainers keyring. Both PGP/MIME and inline signatures should be fine.

 Package        : SOURCEPACKAGENAME
 Version        : VERSIONOFFIX
 CVE ID         : CVE-2014-0001 CVE-2014-0002

 Brief description of the issue. This can usually be copied from the DSA.

Recording the fix in the Debian Security Tracker

Finally the fix needs to be tracked in the Debian Security Tracker by adding a [squeeze] version tag, e.g. for GNUTLS:

CVE-2014-3466
        RESERVED
        {DSA-2944-1}
        - gnutls26 2.12.23-16
        - gnutls28 3.2.15-1
        [squeeze] - gnutls26 2.8.6-1+squeeze4


CategoryLts