[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#905251: apt-listchanges: changelogs for tglase.lan.tarent.de



On Wed, 29 Aug 2018, root wrote:

> debian-policy (4.2.1.0) unstable; urgency=medium

>   * Fix inconsistent wording in 4.9 by dropping the word 'maximally'
>     (Closes: #905251).
>     Thanks to several people who pointed out this issue, both in the BTS
>     and in person.

>  -- Sean Whitton <spwhitton@spwhitton.name>  Sat, 25 Aug 2018 13:05:54 -0700

You have a stray colon left there:

| <p>The package build should be as verbose as reasonably possible, except                                         
| where the <code class="docutils literal notranslate"><span class="pre">terse</span></code> tag is included in <co
| +de class="docutils literal notranslate"><span class="pre">DEB_BUILD_OPTIONS</span></code> (see                  
| <a class="reference internal" href="#s-debianrules-options"><span class="std std-ref">debian/rules and DEB_BUILD_
| +OPTIONS</span></a>:).  This means that <code class="docutils literal notranslate"><span class="pre">debian/rules
                     ↑ here
| +</span></code>                                                                                                  

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

*************************************************

**Besuchen Sie uns auf der dmexco 2018!**

12**. **& 13. September 2018, Koelnmesse / **Halle 7,** **Stand A-031**

Digital Business, Marketing und Innovation

[www.tarent.de/dmexco](http://www.tarent.de/dmexco)

*************************************************

**Visit us at dmexco 2018!**

12th & 13th September, 2018, Koelnmesse / **Hall 7,** **Booth A-031**

Digital business, marketing and innovation

[www.tarent.de/dmexco](http://www.tarent.de/dmexco)

*************************************************


Reply to: