/mandos/release

To get this branch, use:
bzr branch http://bzr.recompile.se/loggerhead/mandos/release

« back to all changes in this revision

Viewing changes to plugins.d/usplash.xml

  • Committer: Teddy Hogeborn
  • Date: 2019-02-11 10:57:53 UTC
  • mto: (237.7.594 trunk)
  • mto: This revision was merged to the branch mainline in revision 382.
  • Revision ID: teddy@recompile.se-20190211105753-ncbbfxxuzkxon67c
Fix Debian package dependency when using GnuTLS < 3.6.0

Work around what is probably a bug in dpkg-shlibdeps; it sees the
"libgnutls28-dev (>= 3.6.6) | libgnutls28-dev (<< 3.6.0)," in the
build-dependencies not as two alternatives, but as an absolute
dependency on libgnutls30 >= 3.6.6.  So if we compiled with
libgnutls30 << 3.6.0, we have to hide this build dependency.

* debian/rules (override_dh_shlibdeps-arch): New; conditionally edit
                                             debian/control before
                                             running dh_shlibdeps.

Show diffs side-by-side

added added

removed removed

Lines of Context:
plugins.d/usplash.xml
135
135
        <para>
136
136
          These variables will normally be inherited from
137
137
          <citerefentry><refentrytitle>plugin-runner</refentrytitle>
138
 
          <manvolnum>8mandos</manvolnum></citerefentry>, which might
139
 
          have in turn inherited them from its calling process.
 
138
          <manvolnum>8mandos</manvolnum></citerefentry>, which will
 
139
          normally have inherited them from
 
140
          <filename>/scripts/local-top/cryptroot</filename> in the
 
141
          initial <acronym>RAM</acronym> disk environment, which will
 
142
          have set them from parsing kernel arguments and
 
143
          <filename>/conf/conf.d/cryptroot</filename> (also in the
 
144
          initial RAM disk environment), which in turn will have been
 
145
          created when the initial RAM disk image was created by
 
146
          <filename
 
147
          >/usr/share/initramfs-tools/hooks/cryptroot</filename>, by
 
148
          extracting the information of the root file system from
 
149
          <filename >/etc/crypttab</filename>.
140
150
        </para>
141
151
        <para>
142
152
          This behavior is meant to exactly mirror the behavior of
280
290
    <para>
281
291
      <citerefentry><refentrytitle>intro</refentrytitle>
282
292
      <manvolnum>8mandos</manvolnum></citerefentry>,
 
293
      <citerefentry><refentrytitle>crypttab</refentrytitle>
 
294
      <manvolnum>5</manvolnum></citerefentry>,
283
295
      <citerefentry><refentrytitle>fifo</refentrytitle>
284
296
      <manvolnum>7</manvolnum></citerefentry>,
285
297
      <citerefentry><refentrytitle>plugin-runner</refentrytitle>