Differences between revisions 412 and 413
Revision 412 as of 2013-10-09 02:13:45
Size: 7665
Editor: PaulWise
Comment: identica/debian
Revision 413 as of 2013-12-18 03:27:58
Size: 8149
Comment: added article about pgpsigurlmangle in debian/watch
Deletions are marked like this. Additions are marked like this.
Line 39: Line 39:

=== Cryptographic verification of upstream packages ===

As of devscripts 2.13.3, {{{uscan}}} now supports verifying cryptographic signatures on upstream source via the {{{pgpsigurlmangle}}} option in {{{debian/watch}}}. See {{{uscan(1)}}} for details and examples. If your upstream provides cryptographic signatures, set up your workflow to verify them automatically! If your upstream doesn't provide cryptographic signatures, nag them until they start doing so! :)

--dkg

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. When we have collected 5 items, we'll send the content of this wiki page 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.

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

Email notifications for git commits on git.debian.org

Many projects rely on the git-commit-notice script provided on git.debian.org to send mail notifications of the activity of the git repositories hosted there. Up to now, this script was based on (a very old copy of) the "post-receive-email" contrib script from Git upstream. I recently updated it and it's now based on git-multimail which generates more usefuls mails (with better subjects, with commit ordering per push, with proper support of merge, etc.). I have tweaked the script to auto-migrate the old git configuration settings so most of you shouldn't have anything to do but you might want to review/tweak the generated configuration (multimailhook.* git config settings) and drop the old one (hooks.* git config settings).

-- Raphaël Hertzog

Alioth.debian.org now exports project meta-data as RDF (using DOAP/ADMS.SW)

The alioth.debian.org forge now runs the ADMS.SW FusionForge plugin, which publishes projects meta-data as RDF / Linked Data. Every project's homepage https://alioth.debian.org/projects/PROJNAME/ is then available as RDF for harvesting robots (using proper content-type negociation, for instance : $ curl -k -H "Accept: text/turtle" https://alioth.debian.org/projects/PROJNAME/). The two main ontologies used are DOAP and ADMS.SW, rendering such meta-data compatible with other project indexes (such as meta-data published by the PTS). Note that due to the big number of hosted projects on Alioth (950+) some package indexes can't be exported as RDF yet. More details in ADMS.SW plugin for FusionForge deployed on Alioth.

-- Olivier Berger

Animate the Debian microblogging accounts!

The Debian publicity team is seeking help to re-animate the Debian microblogging accounts. If you or your team are are looking for help, working on something, did something interesting, are holding a Debian related event or have something short and Debian-related to say, please propose a short message on the team IRC channel. We also welcome folks who want to watch Debian IRC/lists/forums/planets and propose short messages. We will use deb.li for link shortening. Messages will be posted to identica and propagated to other microblogging systems and social networks. Help us tell the world about the Debian community!

-- Paul Wise

DEP-12 supported by the PTS

Source packages that contain a debian/upstream file now have an "upstream info" link on their PTS pages. The link currently points at the yaml-all page of the upstream metadata gatherer. The debian/upstream file is a useful way to inform people about upstream version control systems, donation pages, scientific publications and other interesting metadata. Please add it to your packages before your next upload.

-- Paul Wise

/!\ It didn't appear to be consensus that the current file format is a good idea, and as such promoting it seems hasty.

Cryptographic verification of upstream packages

As of devscripts 2.13.3, uscan now supports verifying cryptographic signatures on upstream source via the pgpsigurlmangle option in debian/watch. See uscan(1) for details and examples. If your upstream provides cryptographic signatures, set up your workflow to verify them automatically! If your upstream doesn't provide cryptographic signatures, nag them until they start doing so! :)

--dkg

Previous news

If you want to send out a new issue on debian-devel-announce, you can use this helper script to generate the email version of this page. Once the mail is sent and archived, please add a link on this page and mention the mail in ProjectNews.


CategoryPermalink