summaryrefslogtreecommitdiff
path: root/debian/TESTING
blob: 641127aa6c70e3066d542241de5d63491a91ae40 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
Call for help testing new versions of mdadm
===========================================

The problem with being the mdadm maintainer is that it doesn't make any
friends but potentially quite a lot of enemies. Even though it's actually very
unlikely that a new mdadm version causes data loss (mdadm is only the remote
control into the kernel), people seem to exhibit unexpected reactions when
their MD arrays with important data don't want to start anymore. In such
a case, don't panic, don't do anything without understanding the implications,
and consider asking for help.

That said, I would appreciate if you guys helped me test the latest mdadm
releases a bit more thoroughly. I do extensive tests myself, but as Murphy
would be able to predict, the problem only ever occur on other people's
machines, and I'd much rather fix them sooner than later.

The easiest way to test new mdadm packages is by adding my package repository
(i386/amd64) to your sources.list file, and configuring the APT pins
appropriately:

---8<---
# cat <<_eof >> /etc/apt/sources.list
deb http://debian.madduck.net/repo sid main
_eof
# cat <<_eof >> /etc/apt/preferences
Package: *
Pin: release a=sid, release o=madduck
Pin-Priority: 50

Package: mdadm
Pin: release a=sid, release o=madduck
Pin-Priority: 600
_eof
# apt-get update; apt-get upgrade
---8<---

Alternatively, you can just download the package for i386[0] or amd64[1]:

  0. http://debian.madduck.net/repo/dists/sid/main/binary-i386/admin/
  1. http://debian.madduck.net/repo/dists/sid/main/binary-amd64/admin/

If you're running sarge and are willing to test, that would be great! I've
prepared backports, which you can use like so (note how you need backported
debconf and lsb-base packages too, which are to be found in the backports.org
archive [2]; see also further down for direct links):

  2. http://backports.org/dokuwiki/doku.php?id=instructions

---8<---
# cat <<_eof >> /etc/apt/sources.list
deb http://debian.madduck.net/repo sarge-backports main
## unless you have backports already enabled:
deb http://www.backports.org/debian sarge-backports main
_eof
# cat <<_eof >> /etc/apt/preferences
Package: *
Pin: release a=sarge-backports, release o=madduck
Pin-Priority: 50

Package: mdadm
Pin: release a=sarge-backports, release o=madduck
Pin-Priority: 600

Package: debconf
Pin: release a=sarge-backports
Pin-Priority: 600

Package: lsb-base
Pin: release a=sarge-backports
Pin-Priority: 600
_eof
# apt-get update; apt-get upgrade
---8<---

The mdadm backport can also be directly downloaded for i386[3] or amd64[4], the
needed debconf[5] and lsb-base[6] reside in the backports.org archive.

  3. http://debian.madduck.net/repo/dists/sarge-backports/main/binary-i386/admin/
  4. http://debian.madduck.net/repo/dists/sarge-backports/main/binary-amd64/admin/
  5. http://backports.org/debian/pool/main/d/debconf/
  6. http://backports.org/debian/pool/main/l/lsb/

Much appreciated!

 -- martin f. krafft <madduck@debian.org>  Thu, 09 Nov 2006 16:16:21 +0100

$Id$