Differences between revisions 527 and 528
Revision 527 as of 2016-10-16 04:36:24
Size: 8344
Editor: PaulWise
Comment: add SF redirector
Revision 528 as of 2016-10-17 01:52:07
Size: 4735
Editor: PaulWise
Comment: new issue sent
Deletions are marked like this. Additions are marked like this.
Line 18: Line 18:
=== LeaseWeb offers discounts to Debian Developers ===

One of the major sponsors behind snapshot.debian.org, [[https://www.leaseweb.com|LeaseWeb]], is now offering discounts on their services to Debian Developers.

!LeaseWeb provides dedicated servers, bare metal servers, private clouds, virtual servers and content delivery networks. !LeaseWeb offers discounts to Debian Developers.

DDs should send emails to sales@us.leaseweb.com (for North America) or sales@nl.leaseweb.com (for Europe) from their @debian.org address referencing "debian.org membership special offer".

The specific amount of discount is dependent on the service requested and the availability of resources (eg, number of dedicated servers available at the time of the request).

=== git-series: track changes to a patch series over time ===

Josh Triplett [[https://lists.debian.org/debian-devel/2016/07/msg00535.html|announced]] a new git tool, [[https://github.com/git-series/git-series/|git-series]], to manage patch series with git, tracking
the "history of history". git series tracks changes to the patch series
over time, including rebases and other non-fast-forwarding changes. git
series also tracks a cover letter for the patch series, formats the
series for email, and prepares pull requests.

This makes it easier to collaborate on a patch series, distribution
package, backport, or any other development process that includes
rebasing or non-fast-forward development.

Debian package maintenance tends to have this exact family of problems: maintaining a set of patches to upstream code, rebasing those patches on new upstream versions, reorganizing/refining/adding/dropping patches, having individual patches merged upstream, and backporting changes *from* upstream.

If you're interested in developing workflows for package maintenance with git-series, please follow up to debian-devel. [[https://lists.debian.org/msgid-search/20160812035657.c72mu75x5bmygvva@x|More detail is available]].

-- Josh Triplett

=== PHP licence applicability to the Debian archive ===

The FTPMasters have published [[https://ftp-master.debian.org/php-license.html||specific guidance]] to allow PHP 3.0+ licensed works in the main archive.
This allows software published under the license to be included, but with specific guidance to the wording in the copyright file. It also serves to ensure compliance with the ''PHP'' trademark.

-- Neil McGovern

=== New #packaging IRC channel ===

There have been some folks who aren't satisfied with the level of signal to noise on the #debian-mentors IRC channel, mainly around people joining who are not aiming at creating policy compliant packages for upload to the Debian archive. People looking for help with private packaging, packaging for derivatives, packaging for their external repos and so on. As a result I've created the #packaging channel on OFTC to help such folks and reduce the noise on #debian-mentors. If you don't mind helping such folks out, please join us! If you have such questions, please join #packaging instead.

-- Paul Wise

=== SourceForge uscan redirector & subdirs ===

Some upstreams have identically named tarballs in different subdirectories in their SourceForge file area. The Debian uscan redirector for SourceForge now emits extra links that include the full path to upstream files. This means that you now can choose which particular upstream subdirectories that you want to match files from. Here is an example for the boost package:

opts="uversionmangle=s/_/./g,dversionmangle=s/\+dfsg$//" \
http://sf.net/boost/ .*/[.\d]+/boost_([\d_]*)\.tar.bz2

-- Paul Wise
Line 74: Line 21:

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

42 41 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