Differences between revisions 502 and 503
Revision 502 as of 2016-01-02 09:20:56
Size: 8123
Editor: PaulWise
Comment: editing
Revision 503 as of 2016-01-02 09:25:29
Size: 4588
Editor: PaulWise
Comment: issue 40 sent
Deletions are marked like this. Additions are marked like this.
Line 16: Line 16:
=== new Debian packaging tool: cme with dpkg plugin ===

cme and its dpkg plugin provide a new tool to help maintain Debian packages.
cme provides a GUI to edit package files and a CLI to modify or check these
files. Editing or modifying package file with cme automatically upgrades package files to newer syntax.

cme stands "config model editor" and is a generic tool to edit configuration files. cme requires plugins to work. The dpkg plugin (aka model) enables cme to work on Debian package files. Currently, it supports control, copyright (DEP-5), patches (DEP-3) and some other files like compat.

For installation and usage instructions, please read [[https://github.com/dod38fr/config-model/wiki/Managing-Debian-packages-with-cme|Managing Debian packages wiki page]]

-- Dominique Dumont

=== Empty binary packages ===

Empty binary packages will [[https://lists.debian.org/87si9qyqzb.fsf@gkar.ganneff.de|now]] be automatically rejected by ftp-master. This can be overridden however. The archive software (dak) uses the lintian empty-binary-package tag to determine which binary packages are empty.

-- Paul Wise

=== Improving Large File Support (LFS) ===

Our [[https://lintian.debian.org/tags/binary-file-built-without-LFS-support.html|Large File Support]] on some 32-bit architectures is a bit poor, and this has been going on for a while now.

Please consider enabling LFS on packages containing programs at any point, and on shared library packages whenever there's a SONAME bump. Even if neither of these are supposed to handle large files, they might still fail if they need to operate on files with large metadata values (like inode numbers). See [[https://lists.debian.org/debian-devel/2015/07/msg00171.html|this mail]] and the above lintian tag for more details.

-- Guillem Jover

=== bts-link now watches over bug reports forwarded to upstream Allura trackers on sf.net ===

[[http://bts-link.alioth.debian.org/|bts-link]] has recently been improved to add support for Allura trackers that are used on Sourceforge. If Debian bug reports have a Forwarded-To link pointing to URL patterns of the form http://sourceforge.net/p/PROJNAME/TRACKERNAME/123456/, bts-link is now able to analyse the remote bug status to detect changes and notify. Allura support is not limited to sf.net, so adding other Allura trackers may be requested if needed.

-- Olivier Berger

=== Automatic debug symbols (dbgsym) packages ===

Since debhelper 9.20151219, [[https://lists.debian.org/debian-devel/2015/12/msg00262.html|debug symbols (dbgsym) packages are produced by default]] without *any* work/effort needed from maintainers.

They are available from a [[http://debug.mirrors.debian.org/debian-debug/|separate mirror]] and [[http://snapshot.debian.org/archive/debian-debug/|snapshot.debian.org]]. We currently only have an unstable and experimental suite for them right now. Testing (incl. the next stable release) needs a bit more work.

If you are concerned with extra upload speed/cost, please consider using "source-only" (or arch:all+source) uploads. These will be even faster/cheaper for you and will leave the heavy lifting to buildds.

-- Niels Thykier

=== Please plan for Stretch ===

In the 4th quarter of 2016, we will freeze Debian stretch. If you are hoping to do any larger changes for stretch, [[https://nthykier.wordpress.com/2016/01/01/debian-please-plan-for-stretch/|please consider starting on them now]]. This also includes features that need to be in APT/dpkg (etc.) in stretch, so we can start using them for buster.

-- Niels Thykier
Line 67: Line 19:
[[https://lists.debian.org/debian-devel-announce/2016/01/msg00001.html|40]]
<<BR>>

Translation(s) : English - Français - 日本語

News for Debian developers

This wiki page collects small news that all developers should know but that are not worth a dedicated mail to debian-devel-announce. Follow the template "Example of news" and add your news below it. See /Help for more information on how to write entries.

If you are able to post to debian-devel-announce (all Debian members can) and there are 5 or more items below, you might want to send out the news. To send out a new issue, you can use this helper script to generate the email version of this page. After generating the mail, proof-read it, correct any spelling, formatting or grammatical errors and send out the mail. Once the mail is sent and archived, please delete the items that were sent, add a link to the archived mail in the Previous news section and mention the mail in ProjectNews.

Example of news

This is a sample news. Copy it and edit the title, content and signature... You can use links like this. Put real news below this sample.

-- Your Name

Previous news

40
39 38 37 36 35 34 33 32 31 30
29 28 27 26 25 24 23 22 21 20
19 18 17 16 15 14 13 12 11 10
9 8 7 6 5 4 3 2 1


CategoryPermalink