dunetna debian

Building a backport

anonymous@undisclosed.example.com (Anonymous) — Thu, 12 Jan 2017 22:44:20 +0000

Description: Building a backport in the proper way. The goal is to upload the backport to the official backports repository.

Language(s): English

These notes are based on https://wiki.debian.org/BuildingFormalBackports

Create a cowbuilder image. If you are already using cowbuilder for other stuff, you must specify where the base will be and the distribiution where you want to backport:

$ sudo cowbuilder --create --basepath /var/cache/pbuilder/base-jessie.cow --distribution jessie

Add an entry to changelog

$ dch --bpo

Build the backport:

$ gbp buildpackage --git-pbuilder --git-ignore-new --git-dist='jessie' -d -vSTABLE_VERSION

where STABLE_VERSION is the stable version or the last backport.

Upload the package

$ dput PKG_NAME*changes

Check and upload a NMU of someone else

anonymous@undisclosed.example.com (Anonymous) — Mon, 09 Apr 2012 01:23:10 +0000

Description: Some times, there are non-DDs that upload NMUs to the BTS becaues they can't upload it. Here you have a workflow to review and upload these NMUs.

Language(s): English

Check if you can reproduce the bug(s):

PKG_NAME="package_name"; PKG_VERSION="version_number"; PKG_REVISION="revision_number"
apt-get source $PKG_NAME
sudo pbuilder --build ${PKG_NAME}_${PKG_VERSION}-${PKG_REVISION}.dsc

Apply NMU:

NMUDIFF_URL="nmudiff_url"; PKG_NMU_REVISION="nmu_revision_number"
wget -O ${PKG_NAME}_${PKG_VERSION}-${PKG_NMU_REVISION}.nmu.diff "$NMUDIFF_URL"
patch -p0 <  ${PKG_NAME}_${PKG_VERSION}-${PKG_NMU_REVISION}.nmu.diff
dpkg-source -b ${PKG_NAME}-${PKG_VERSION}
sudo pbuilder --build ${PKG_NAME}_${PKG_VERSION}-${PKG_NMU_REVISION}.dsc

Check if new package works as expected and run tools like debdiff and lintian.

PBUILDERRESULT="pbuilder_results_dirname"
debdiff ${PKG_NAME}_${PKG_VERSION}-${PKG_REVISION}.dsc $PBUILDERRESULT/${PKG_NAME}_${PKG_VERSION}-${PKG_NMU_REVISION}.dsc
lintian -F $PBUILDERRESULT/${PKG_NAME}_${PKG_VERSION}-${PKG_NMU_REVISION}*.changes

Sign and upload the package and send an email to BTS with nmudiff

debsign $PBUILDERRESULT/${PKG_NAME}_${PKG_VERSION}-${PKG_NMU_REVISION}*.changes
dput -e 5 $PBUILDERRESULT/${PKG_NAME}_${PKG_VERSION}-${PKG_NMU_REVISION}*.changes
cd ${PKG_NAME}-${PKG_VERSION}
nmudiff --delay=5

As the nmudiff is already uploaded, you can change the mail. A template could be:

Dear maintainer,

I've uploaded the previous NMU for $PKG_NAME (versioned as ${PKG_VERSION}-${PKG_NMU_REVISION})
to DELAYED/5. Please feel free to tell me if I should delay it longer.

Regards.

cowbuilder: Creating a proper image to build a package

anonymous@undisclosed.example.com (Anonymous) — Sat, 28 Nov 2015 15:45:14 +0000

Description: When packaging with cowbuilder, each time you want to build, all needed packages have to been configured. This recipe shows how to prepare a cowbuilder base to do all this configurations only once.

Language(s): english

Copy a basic image (or create it with sudo cowbuilder –create):

$ sudo cp -a /var/cache/pbuilder/base.cow /var/cache/pbuilder/base-PKGNAME.cow

Start a session within this image telling cowbuilder that all changes will be saved:

$ sudo cowbuilder --login --basepath /var/cache/pbuilder/base-PKGNAME.cow --save-after-login

Once inside the image, enable package sources:

# sed -i 's/#\(deb-src .*\)/\1/g' /etc/apt/sources.list
# aptitude update

Install build dependencies of the package:

# aptitude build-dep PKGNAME

Logout:

# exit

Now, to use this image for building:

$ sudo cowbuilder --build PKGNAME_VERSION.dsc --basepath /var/cache/pbuilder/PKGNAME.cow

If you use git-buildackage:

$ gbp buildpackage --git-pbuilder --git-dist='PKGNAME'

If you want to use this last command, your image must have the prefix 'base-' (see #721444)

Recipe under construction

anonymous@undisclosed.example.com (Anonymous) — Sun, 11 Jun 2017 22:57:58 +0000

Creating a new package with git

Description: Basic steps to create a new package with git. This page does not pretend to b a packging tutorial.

Language(s): English

Download the upstream package. Repack it if it is needed. Suppose you have a file with format package_name-version.tar.gz. Let's create our git repo:

PKGNAME=package_name
VERSION=version  
mkdir $PKGNAME; cd $PKGNAME
git init

Check that user.name and user-email have the right values:

git config user.name '<Your name>'
git config user.email '<Your email>'

Import upstream sources to your repository:

gbp import-orig -u $VERSION --pristine-tar ../$PKGNAME-$VERSION.tar.gz

If you miss to add –pristine-tar option, you can generate it later wit the following command:

pristine-tar commit ../$PKGNAME_-$VERSION.orig.tar.gz

In the parent folder you have a link named PKGNAME_VERSION.orig.tar.gz to your original .tar.gz upstream file. Let's create the debian directory:

# license can be gpl, gpl2, gpl3, lgpl, lgpl2, lgpl3, artistic, apache, bsd or mit. 
# See man dh_make, option -c
LICENSE=license 
dh_make -c LICENSE -f ../PKGNAME_VERSION.orig.tar.gz -p PKGNAME_VERSION
git add debian/
git commit -m "Create debian directory via dh_make"

Remove all unneeded files in debian directory (it depends on your package):

git rm debian/README.Debian debian/README.source ...
git commit -m "Remove all unneeded dh_make templates"

Stuff that always must be done:

Close the ITP bug
Add building dependencies (almost always)
Add runtime dependencies (not so frequently)

If you're impatient, you can try to build it now… In fact, after each change you do, you can try to build the package. See how to build the package below. More change you will do:

Update Section, Priority, Homepage and Description fields.
Update debhelper compatibility
Update copyright
Update menu file, adding an icon if it is necessary
Update watch file
Install files that are not installed automatically: icons, man pages,…
Adapt debian/rules to your needs
Unapply patches after building

If you have to change the source code, you should use quilt. First, add .pc directory (and optionally .gitignore) to .gitignore:

echo -e ".gitignore\n.pc" > .gitignore

Now you can change the code with:

quilt new new-patch-name.patch
quilt edit files-to-change
quilt refresh

To build the package you can use git-buildpackage:

git buildpackage

or better (but slower):

git buildpackage --git-pbuilder

To check that every thing is ok:

lintian -i -I --show-overrides --pedantic ../$PKGNAME_$VERSION-1_i386.changes

Sign the package:

debsign $PKGNAME*.changes

Upload the package

dput $PKG_NAME*changes

Remember to tag your last commit:

git-buildpackage --git-tag-only

And push if you haven't done it before:

git push alioth
git push alioth --tags

Set up a remote repository in collab-maint in allioth (or inthe corresponding team):

ssh git.debian.org
umask 002
cd /git/collab-maint/
./setup-repository $PKGNAME '$PKGNAME Debian packaging'
exit

git config gitweb.owner '<Your name>'

git remote add alioth ssh://git.debian.org/git/collab-maint/$PKGNAME.git
git push alioth master 
git push alioth upstream
git push alioth pristine-tar

More info: https://wiki.debian.org/Alioth/Git

Debian Developer recipes

anonymous@undisclosed.example.com (Anonymous) — Thu, 21 Jan 2016 08:59:29 +0000

Description: Here you will find some recipes I use for some Debian tasks

Language(s): English

NMUs

RCBW (Release Critical Bugs of the Week) work flow
Check and upload a NMU of someone else

QA Uploads

QA Upload work flow

Packaging

Creating a new package with git
Packaging a new upstream version
Packaging a new Debian release
Packaging with git
cowbuilder: Creating a proper image to build a package
pbuilder: tips
Building a backport

wnpp packages

Fix wnpp inconsistencies

Misc

Non-DD to DD steps
Managing GPG keys
Useful links

Debian Developer's Reference

anonymous@undisclosed.example.com (Anonymous) — Wed, 04 Apr 2012 23:27:15 +0000

Description: Provides an overview of the recommended procedures and the available resources for Debian developers.

Language(s): English

http://www.debian.org/doc/manuals/developers-reference/index.en.html

Debian New Maintainers Guide

anonymous@undisclosed.example.com (Anonymous) — Wed, 04 Apr 2012 15:34:14 +0000

Description: Describe the building of a Debian package to ordinary Debian users and prospective developers

Language(s): English

http://www.debian.org/doc/manuals/maint-guide/index.en.html

Debian Policy Manual

anonymous@undisclosed.example.com (Anonymous) — Wed, 04 Apr 2012 23:21:32 +0000

Description: Describes the policy requirements for the Debian distribution.

Language(s): English

http://www.debian.org/doc/debian-policy/

Debian reference card

anonymous@undisclosed.example.com (Anonymous) — Wed, 04 Apr 2012 13:05:09 +0000

Description: Reference card for the Debian system.

Language(s): Catalan, English, Spanish and more

debian-refcard (install it with apt-get/aptitude)

Talks about Debian

anonymous@undisclosed.example.com (Anonymous) — Tue, 14 May 2013 09:52:51 +0000

Description: Talks about Debian.

Language(s): Catalan, Spanish

Outreach Program for Women 2013-05-11 Festa Raring Ringtail, Barcelona
Taller: Com arreglar bugs a Debian 2012-12-17 Ateneu Rosa de Foc, Barcelona
Cómo empezar a colaborar en Debian 2012-10-13 Hackafou, Vallbona D'anoia
Debian QA: una puerta de entrada al proyecto Debian 2012-07-07 Debconf12, Managua
Debian. El sistema operatiu lliure creat per la comunitat. 2012-04-20 Institut Àusias March, Barcelona
Debian 2011-09-17 Dia de la Llibertat del Programari, Barcelona
Gestió de paquets amb Debian 2007-06 Escola del Treball, Barcelona

Fix wnpp inconsistencies

anonymous@undisclosed.example.com (Anonymous) — Tue, 13 Jan 2015 15:36:58 +0000

Description: When you want to package a Debian package there is a workflow to follow. Sometimes people make some errors that must be fixed. In this page I explain how I catch these errors and how I try to fix them.

Language(s): English

List of wnpp inconsistencies: https://qa.debian.org/~bartm/wnpp-rfs-mentors/wnpp-inconsistencies.txt

Program to generate some mails and actions to fix these inconsistencies: http://anonscm.debian.org/cgit/users/monica/wnpp-inconsistencies-suggestions.git/

Dependencies to be installed: libdbi-perl, libdbd-pg-perl

To run the program, first you should have an open connection to UDD:

ssh -NL 5452:udd.debian.org:5452 monica@alioth.debian.org

And then run the program:

./wnpp-inconsistencies-suggestions.pl

This program generates suggestions to do to fix the inconsistencies.

Sometimes you must send a mail to the BTS. You can use mutt. For example:

mutt -s "wnpp inconsistencies" -i wnpp-suggestions/control@bugs.debian.org control@bugs.debian.org

mutt -s "problem description" -i wnpp-suggestions/######@bugs.debian.org ######@bugs.debian.org

Sometimes you have to add a coment to mentors.debian.net.

If a suggestion has been done or you want to skip it, you can add it to the file done_suggestions, writing the line with the suggestion. The program will skip this inconsistency from the input file. If a suggestion does not appear in the input file the program will remove this line from done_suggestions file.

This program is not stable yet. If you use it and see any problem, please mail me at monica@debian.org.

Managing GPG keys

anonymous@undisclosed.example.com (Anonymous) — Tue, 16 Dec 2014 15:15:12 +0000

Description: A Debian developer must have a GPG key and be very careful with it. In fact, you need the key signed by other DDs to become a DD. And when you are a DD future DDs will need you sign their keys.

Language(s): English

Signing keys: GPG key signing with CAFF

Importing signed keys: Since I use notmuch, I run the following commands:

for thing in `notmuch search --output=files subject:signed and tag:inbox`; do 
  gpg --decrypt < $thing | gpg --import 
done
gpg --keyserver pgp.mit.edu --send-keys 1A49C0D2

These two lines are inspired (in fact, almost copied) from http://www.asheesh.org/scribble/code/gpg-caff.html

My Debian portfolio

anonymous@undisclosed.example.com (Anonymous) — Fri, 06 Apr 2012 01:23:42 +0000

Description: DDPortfolio summarizes Debian contributors activity. Here you have my Porfolio URLs.

Language(s): English

http://portfolio.debian.net/result?email=monica%40probeta.net&name=M%C3%B2nica+Ram%C3%ADrez+Arceda&gpgfp=&username=&nonddemail=monica%40probeta.net&aliothusername=dunetna-guest&wikihomepage=MonicaRamirezArceda&forumsid=&mode=html&submit=Build+DD+Portfolio+URLs

http://portfolio.debian.net/result?email=monica%40debian.org&name=M%C3%B2nica+Ram%C3%ADrez+Arceda&gpgfp=&username=&nonddemail=monica%40probeta.net&aliothusername=monica&wikihomepage=MonicaRamirezArceda&forumsid=&mode=html&submit=Build+DD+Portfolio+URLs

My Debian packages overview

anonymous@undisclosed.example.com (Anonymous) — Wed, 04 Apr 2012 15:38:30 +0000

Description: Debian packages that I maintain.

Language(s): English

http://qa.debian.org/developer.php?login=monica%40debian.org

Non-DD to DD steps

anonymous@undisclosed.example.com (Anonymous) — Mon, 09 Apr 2012 23:33:35 +0000

Description: If you've been collaborating to Debian as a non-DD and then you become a DD with uploading rights, you have to do some changes in all your configurations. Here you have the changes I did.

Language(s): English

Mail

Create a new identity in your mail client with the appropiate From: header. For example, if you use mutt, in .mutt/muttrc:

set from="ddnick@debian.org"

GPG key

Add an id to your gpg key:

$ gpg --edit-key your_key
...
gpg> adduid
Real name: your_real_name
Email address: ddnick@debian.org
Comment: 
...
Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? o
...
gpg> save

If you wish, set primary uid:

$ gpg --edit-key your_key
...
gpg> uid id_of_the_primary_key
...
gpg> primary
...
gpg> save

Send key to key server:

$ gpg --keyserver pgp.mit.edu --send-key your_key

DEBEMAIL

Update .bashrc:

export DEBEMAIL=ddnick@debian.org

Send RSA key

First, maybe you want to generate a new RSA pair of keys:

$ ssh-keygen
Generating public/private rsa key pair.
Enter file in which to save the key (/home/name/.ssh/id_rsa): /home/name/.ssh/id_rsa.debian
...

Then send it to changes@db.debian.org :

$ cat .ssh/id_rsa.debian.pub | gpg --clearsign | mail -s "Sending RSA key" changes@db.debian.org -- -f ddnick@debian.org

You'll receive a confirmation mail.

See https://db.debian.org/doc-mail.html for more info.

If you want that id_rsa.debian is the key by default:

mv id_rsa id_rsa.other
mv id_rsa.pub id_rsa.other.pub
cp id_rsa.debian id_rsa
cp id_rsa.debian.pub id_rsa.pub

When you connect to Debian machines, the fingreprint of the machine will be shown and you must check it in: https://db.debian.org/machines.cgi. Click on the machine you're interested in to see more details.

Alioth

See http://wiki.debian.org/Alioth/FAQ?action=show&redirect=AliothFAQ#How_can_I_migrate_my_-guest_account_to_my_new_official_Debian_account_.3F

VCS repos

If you had a good config like this in .ssh/config:

Host git.debian.org svn.debian.org alioth.debian.org
User nick-guest

You only have to change your debian nick:

Host git.debian.org svn.debian.org alioth.debian.org
User ddnick

If not, do previous config and change your remote branches. If you use git:

$ git remote -v
alioth ssh://nick-guest@git.debian.org/git/collab-maint/your_package.git (fetch)
alioth ssh://nick-guest@git.debian.org/git/collab-maint/your_package.git (push)
$ git remote rm alioth
$ git remote add alioth ssh://git.debian.org/git/collab-maint/xsol.git
$ git remote -v
alioth ssh://git.debian.org/git/collab-maint/your_package.git (fetch)
alioth ssh://git.debian.org/git/collab-maint/your_package.git (push)

Update .gitconfig:

[user]
      name = Your Name
      email = ddnick@debian.org

If you don't want this mail as the global one, see http://stackoverflow.com/questions/9063176/git-multiple-user-names-for-the-different-projects-within-the-same-system

Lists

if you want, subscribe with your new mail and unsubscribe with the other one, but it's not necessary as lists.d.o are open.

First uploads

debian/control: change the Maintainer field with your new mail.

debian/changelog: Annotate the debian/control change

No more:

dput mentors package*.changes

Now:

dput package*.changes

Packaging a new Debian release (using git)

anonymous@undisclosed.example.com (Anonymous) — Sat, 28 Nov 2015 14:54:22 +0000

Description: Basic steps to package a new Debian release of an existing package using git

Language(s): English

You can build the package without doing any change to ensure it is building right now:

gbp buildpackage --git-pbuilder -d

Make the changes you need and update debian/changelog:

dch -i

Write the change, closing bugs if needed:

  * Change description. (Closes: #nnnnn)

It's very important to update changelog before building. If we don't do it, a file in debian/patches will be created since it'll be understood that you are making changes to the code.

Build the package:

gbp buildpackage --git-pbuilder --git-ignore-new -d

If it builds, commit the change:

git commit -a -m "Change description"

Run lintian:

lintian -i -I --show-overrides --pedantic PKGNAME_NEWVERSION-1_ARCH.changes

Try to make the package lintian free, do all needed changes/commits and build as many times as you need to make the package ready to upload.

Install and test the package:

dpkg -i PKGNAME_NEWVERSION-1_ARCH.deb

Check that there are not weird changes comparing the new package with the old one:

debdiff PKGNAME_OLDVERSION-OLDREVISION.dsc PKGNAME_NEWVERSION-1.dsc

Do this last commit:

dch -r
git commit -a -m "Releasing to sid"

And build again:

gbp buildpackage --git-pbuilder -d

Add tags to the git repo:

gbp buildpackage --git-tag-only

Sign the package (if it has not been done during the last command):

debsign PKG_NAME*changes

Upload the package:

dput PKG_NAME*changes

Push changes (if you haven't done it before) and tags:

git push alioth
git push alioth --tags

Packaging a new upstream version (using git)

anonymous@undisclosed.example.com (Anonymous) — Mon, 17 Aug 2015 11:37:55 +0000

Description: Basic steps to package a new upstream version of an existing package using git

Language(s): English

Check that there is a new upstream version:

uscan --report

Download the new upstream version:

uscan

Import this new version to git:

gbp import-orig --pristine-tar ../PKGNAME_NEWVERSION.orig.tar.gz -u NEWVERSION

If you forget the –prisitne-tar option, you can cretae the pristine-tar with:

pristine-tar commit ../PKGNAME_NEWVERSION.orig.tar.gz

Update debian/changelog:

dch -v NEW_VERSION-1

Add the following item:

  * New upstream release.

It's very important to update changelog before building. If we don't do it, a file in debian/patches will be created since it'll be understood that you are making changes to the code.

Commit this change:

git commit -a -m "New upstream release"

Do whatever is needed.

Build the package:

gbp buildpackage --git-pbuilder -d

Or if you have uncommitted changes:

gbp buildpackage --git-pbuilder --git-ignore-new -d

Run lintian:

lintian -i -I --show-overrides --pedantic PKGNAME_NEWVERSION-1_ARCH.changes

Try to make the package lintian free, do all needed changes/commits and build as many times as you need to make the package ready to upload.

Install and test the package:

dpkg -i PKGNAME_NEWVERSION-1_ARCH.deb

Check that there are not weird changes comparing the new package with the old one:

debdiff PKGNAME_OLDVERSION-OLDREVISION.dsc PKGNAME_NEWVERSION-1.dsc

Do this last commit:

dch -r
git commit -a -m "Releasing to sid"

And build again:

gbp buildpackage --git-pbuilder

Sign the package (if it has not been done during the last command):

debsign PKG_NAME*changes

Upload the package:

dput PKG_NAME*changes

Add tags to the git repo:

gbp buildpackage --git-tag-only

Push changes (if you haven't done it before) anf tags:

git push alioth
git push alioth --tags

Recipe under construction

anonymous@undisclosed.example.com (Anonymous) — Thu, 26 Apr 2012 22:41:37 +0000

Packaging with git

Description: Basic steps to package with git

Language(s): English

Changes to a package

Make change

If you want to build without committing:

git-buildpackage --git-ignore-new

Commit:

git add affected_files
git commit -m "message"

or if all not staged files must be commited:

git commit -a -m "message"

Repeat this process for every change you want to add.

Generate new debian/changelog entry:

git-dch --full --meta

If you make more changes and want to add them to debian/changelog:

git-dch -s commit

pbuilder: tips

anonymous@undisclosed.example.com (Anonymous) — Fri, 27 Apr 2012 01:10:10 +0000

This recipe is under construction!!!

Description:

Language(s): English

Recipe under construction

anonymous@undisclosed.example.com (Anonymous) — Sat, 27 Feb 2016 22:04:24 +0000

QA upload work flow

Description: Orphaned packages are responsability of QA team and any DD can make an upload to have these packages well maintained. Here you have a workflow to do this kind of uploads. It is assumed that the package is not using any version control system. If it uses one, take a look at Packaging a new upstream version and Packaging a new Debian release

Language(s): English

Download the package and try to build it:

PKG_NAME="package_name"; PKG_VERSION="version_number"; PKG_REVISION="revision_number"
mkdir ${PKG_NAME}; cd ${PKG_NAME}
apt-get source ${PKG_NAME}
sudo cowbuilder --build ${PKG_NAME}_${PKG_VERSION}-${PKG_REVISION}.dsc

Now we have two possibilities: fix bugs and tidy up the package to have a new Debian release or package a new upstream version.

New Debian release

cd ${PKG_NAME}-${PKG_VERSION}
dch -q

New upstream version

uscan  
PKG_QA_VERSION="qa_version_number"; PKG_QA_REVISION="1"
cd ${PKG_NAME}-${PKG_VERSION}
uupdate -v $PKG_QA_VERSION ../${PKG_NAME}-${PKG_QA_VERSION}.tar.xz
cd ../${PKG_NAME}-${PKG_QA_VERSION}
dch -a

Add a first entry in the new chagelog blck with the text “QA upload”.

Both cases

Fix all you want to fix.

cd ..
dpkg-source -b ${PKG_NAME}-${PKG_QA_VERSION}
sudo cowbuilder --build ${PKG_NAME}_${PKG_QA_VERSION}-${PKG_QA_REVISION}.dsc

Check if new package works as expected. If it doesn't work, fix it, recreate the source package and rebuild it again until it works properly.

Run lintian:

lintian -i -I --show-overrides --pedantic /var/cache/pbuilder/result/${PKG_NAME}_${PKG_QA_VERSION}-1_${ARCH}.changes

Try to make the package lintian free, do all needed changes/commits and build as many times as you need to make the package ready to upload.

Install and test the package:

sudo dpkg -i /var/cache/pbuilder/result/${PKG_NAME}_${PKG_QA_VERSION}-1_${ARCH}.deb

Check that there are not weird changes comparing the new package with the old one:

debdiff /var/cache/pbuilder/result/${PKG_NAME}_${PKG_VERSION}-${PKG_REVISION}.dsc /var/cache/pbuilder/result/${PKG_NAME}_${PKG_QA_VERSION}-1.dsc

Prepare the package to upload:

cd ${PKG_NAME}-${PKG_QA_VERSION}
dch -r

Built it again:

cd ..
dpkg-source -b ${PKG_NAME}-${PKG_QA_VERSION}
sudo cowbuilder --build ${PKG_NAME}_${PKG_QA_VERSION}-${PKG_QA_REVISION}.dsc

Sign the package (if it has not been done during the last command):

debsign /var/cache/pbuilder/result/${PKG_NAME}*changes

Upload the package:

dput /var/cache/pbuilder/result/${PKG_NAME}*changes

RC Bugs

anonymous@undisclosed.example.com (Anonymous) — Sat, 02 Mar 2013 10:05:34 +0000

From time to time, I try to help to the RCBW initiative a little bit. I should say RCBM (M = month) in my case

I'm collecting all my previous contributions and adding my new ones.

Fixing Debian bugs is funny!

2013/02

~~#640851~~ evolution: Local mbox files inaccessible after upgrade/migration
This bug was already closed, but couldn't be archived. Reassigned the bug to the correct package and close the bug after a little bit mess.
~~#625956~~ src:doxygen: missing source for src/jquery.js
Attached a patch.

2012/11

~~#678786~~ haskell-llvm-base: FTBFS: error: 'class llvm::SMDiagnostic' has no member named 'Print'
This bug was already closed, annotated that it was not found in any version.

2012/10

~~#691729~~ qt4-designer: Main window unresponsive upon start
This bug was already closed, annotated that it was not found in any version.

2012/06

~~#665895~~ gadmintools: uninstallable due to dependency on removed gadmin-squid
QA Upload fixing this bug and some lintian issues.
~~#675714~~ tachyon [tachyon] libtachyon-dev must depend on libtachyon-0.99
Attached a patch. I'm waiting a little bit to upload the NMU… Thanks to Ana for finding this bug! (that makes a FTBFS of ovito package on amd archs). Finally, uploaded to DELAY/5.

2012/05

~~#672047~~ ovito: FTBFS: SimulationCell.cpp:192:2: error: 'GLUquadricObj' was not declared in this scope
Uploaded to DELAY/5. Package has been orphaned: uploaded new upstream version (fixing this bug) as a QA upload and tidied up the package a little bit.
~~#667372~~ sfst: ftbfs with GCC-4.7
Uploaded to DELAY/5.
~~#672607~~ pidgin-sipe 1.11 does not use NTLM type authentication and does not connect to Lync server
Sponsored new package version done by Jakub Adam.
~~#667326~~ polygraph: ftbfs with GCC-4.7
Uploaded to DELAY/5.
~~#667291~~ music: ftbfs with GCC-4.7
Uploaded to DELAY/5.
~~#666584~~ conglomerate: FTBFS: cong-editor-line-iter-simple.c:29:1: error: conflicting types for 'clone'
Also removed rpath setting in conglomerate binary. Uploaded to DELAY/5.

2012/04

~~#658956~~ php-radius-legacy Call-time pass-by-reference has been removed from php5 (>= 5.4)
Uploaded to DELAY/5.
~~#658874~~ phpreports Call-time pass-by-reference has been removed from php5 (>= 5.4)
Uploaded to DELAY/5.
~~#658876~~ zoph Call-time pass-by-reference has been removed from php5 (>= 5.4)
Uploaded to DELAY/5.
~~#665672~~ pidgin-sipe: FTBFS with glib 2.32 due to -Werror=deprecated-declarations
Uploaded to DELAY/5. This NMU also closes ~~#667323~~, a candidate to be a RC bug in the future.
#666659 comixcursors: FTBFS: rmdir: failed to remove `/ÃÂÃÂ«PKGBUILDDIRÃÂÃÂ»/debian/build/usr/share/icons/default': No such file or directory
Forcemerged with #666473 and sent a pacth to the BTS. Not uploaded as it is not a RC bug right now.
~~#643088~~ dia-newcanvas: FTBFS: dpkg-buildpackage: error: dpkg-source -b dia-newcanvas-0.6.10 gave error exit status 2
Applied patch of gregor herrmann and fixed some Werrors. Uploaded to DELAY/5.

2012/03

~~#663552~~ transgui: FTBFS: Error: Illegal parameter: -WG.
Uploaded to DELAY/5. Cancelled because NMU was merged with a new upstream version by the maintainer.
~~#662941~~ scute: FTBFS
Uploaded to DELAY/5.
~~#663053~~ terminatorx: FTBFS with current zlib
Uploaded to DELAY/5.
~~#662596~~ partimage: FTBFS
Uploaded to DELAY/5.
~~#662650~~ goffice: FTBFS
Uploaded to DELAY/5.
~~#663612~~ crossfire: Fails to build from source
Uploaded to DELAY/5. Finally canceled because a new upstream version was packaged before.
~~#663566~~ tightvnc: FTBFS: dpkg-source: error: aborting due to unexpected upstream changes
Uploaded to DELAY/5.
~~#643257~~ privbind: dpkg-buildpackage: error: dpkg-source -b privbind-1.2 gave error exit status 2.
Uploaded to DELAY/5.

2012/02

~~653290~~ firetray: FTBFS in unstable sh: 1: xpidl: not found

2012/01

~~655824~~ indicator-session: FTBFS: users-service-dbus.c:589:18: error: variable 'res' set but not used [-Werror=unused-but-set-variable]

2011/12

Here is my first virtual BSP. Thnaks Ana!!!

~~#646470~~ t1lib: FTBFS: objects.c:960:8: error: format not a string literal and no format arguments [-Werror=format-security]
~~#646469~~ torcs: FTBFS: maintexmapper.cpp:106:17: error: format not a string literal and no format arguments [-Werror=format-security]
~~#636009~~ torcs: FTBFS with libpng 1.5
~~#646487~~ slsqlite: FTBFS: sqlite-module.c:117:4: error: format not a string literal and no format arguments [-Werror=format-security]
~~#646499~~ webdruid: FTBFS: output.c:1867:13: error: format not a string literal and no format arguments [-Werror=format-security]
~~#646501~~ vilistextum: FTBFS: main.c:168:2: error: format not a string literal and no format arguments [-Werror=format-security]

2011/11

~~#554413~~ ftgl: FTBFS with binutils-gold

2011/09

~~#639059~~ z88: FTBFS: /usr/include/gtk-2.0/gdk/gdktypes.h:55:23: fatal error: gdkconfig.h: No such file or directory

RCBW (release critical bugs of the week) work flow

anonymous@undisclosed.example.com (Anonymous) — Tue, 30 Oct 2012 01:11:30 +0000

Description: If you want to collaborate in the RCBW initiative, a workflow is quite useful. Here you have the workflow I use.

Language(s): English

Download the package and try to build it:

PKG_NAME="package_name"; PKG_VERSION="version_number"; PKG_REVISION="revision_number"
mkdir ${PKG_NAME}; cd ${PKG_NAME}
apt-get source ${PKG_NAME}
sudo cowbuilder --build ${PKG_NAME}_${PKG_VERSION}-${PKG_REVISION}.dsc

If it is not a FTBFS, try to reproduce the bug. If it is a FTBFS, you have reproduced the bug while building.

cd ${PKG_NAME}-${PKG_VERSION}
dch -n

Fix the bug.

PKG_NMU_REVISION="nmu_revision_number"
cd ..
dpkg-source -b ${PKG_NAME}-${PKG_VERSION}
sudo cowbuilder --build ${PKG_NAME}_${PKG_VERSION}-${PKG_NMU_REVISION}.dsc

Check if new package works as expected. If it doesn't work, fix it, recreate the source package and rebuild it again until it works properly.

If it works run tools like debdiff and lintian:

PBUILDERRESULT="pbuilder_results_dirname"
debdiff ${PKG_NAME}_${PKG_VERSION}-${PKG_REVISION}.dsc $PBUILDERRESULT/${PKG_NAME}_${PKG_VERSION}-${PKG_NMU_REVISION}.dsc
lintian -F $PBUILDERRESULT/${PKG_NAME}_${PKG_VERSION}-${PKG_NMU_REVISION}*.changes

Sign and upload the package and send an email to BTS with nmudiff

debsign $PBUILDERRESULT/${PKG_NAME}_${PKG_VERSION}-${PKG_NMU_REVISION}*.changes
dput -e 5 $PBUILDERRESULT/${PKG_NAME}_${PKG_VERSION}-${PKG_NMU_REVISION}*.changes
cd ${PKG_NAME}-${PKG_VERSION}
nmudiff --delay=5

Workflows that inspired this one:

gregoa's workflow: http://info.comodo.priv.at/blog/articles/rcbw/
zack's workflow: http://upsilon.cc/~zack/hacking/debian/rcbw/

Workshop: Cóm arreglar bugs a Debian

anonymous@undisclosed.example.com (Anonymous) — Mon, 17 Dec 2012 13:24:15 +0000

Description: https://n-1.cc/event_calendar/view/1532341

Language(s): Catalan

El taller es va basar en la resolució del bug #692284. Aquí teniu els apunts que es van fer de manera col·laborativa a gobby.debian.org:

TALLER: COM ARREGLAR BUGS A DEBIAN
==================================

####################
#  Preparar entorn
##

## Instal·lar els següents paquets:

aptitude install build-essential devscripts fakeroot cowbuilder quilt

## Configuració de devscripts a ~/.devscripts: 

DEBSIGN_KEYID="email@example.net"
DEBUILD_LINTIAN=yes
DEBUILD_LINTIAN_OPTS="-i -I --show-overrides --pedantic"

BTS_SMTP_HOST=ssmtp://example.net
BTS_SMTP_AUTH_USERNAME=email@example.net

## Configuració de variables d'entorn a ~/.bashrc: 

export DEBEMAIL=xxxxxx@example.net
export DEBFULLNAME="Nom i cognoms"

## Configuració de pbuilder/cowbuilder a /root/.pbuilderrc: 

AUTO_DEBSIGN=yes
HOOKDIR="/var/cache/pbuilder/hooks"
USEPROC=yes
BUILDRESULT="/var/cache/pbuilder/result"
MIRRORSITE=http://ftp.fr.debian.org/debian/

sudo mkdir /var/cache/pbuilder/hooks

sudo cowbuilder --create --distribution sid

# Per actualitzar l'entorn de cowbuilder:

sudo cowbuilder --update

## Configuració del repositori dels paquets de codi font de la branca unstable:

sudo su -c 'echo "deb-src http://http.debian.net/debian/ unstable main contrib non-free" >> /etc/apt/sources.list.d/src-unstable.list'
sudo aptitude update


################################
# Instal·lar paquet amb el bug
##

# S'intenta resoldre el bug #692284

sudo aptitude install bluefish=2.2.3-4

## Comprovar que es reprodueix el bug.

#####################################
#  Descarregar codi font del paquet
##

mkdir -p debian/bluefish
cd $_
apt-get source bluefish=2.2.3-4

#######################
#  Compilar el paquet
##

## Si ho fem amb debuild

sudo apt-get build-dep bluefish=2.2.3-4
cd bluefish-2.2.3
debuild -us -uc

# netejar temporals de compilació

debuild clean

## Si ho fem amb cowbuilder

sudo cowbuilder --build bluefish_2.2.3-4.dsc

##################
# Solucionar bug
##

## Modificar debian/changelog (non-maintainer upload):
dch -n

## Veure el format del paquet
cat debian/source/format
3.0 (quilt)

##############################
#  Pedaços amb quilt
##

## Pedaços
cat debian/patches/series
ls debian/patches

## Visualitzar pedaços aplicats.
quilt applied

## Desaplicar un pedaç
quilt pop

## Desaplicar tots els pedaços
quilt pop -a

## Aplicar pedaç
quilt push

## Aplicat tots els pedaços
quilt push -a

## Afegir pedaç
quilt new add-x-www-browser.patch
quilt add src/rcfile.c

## Solucionar el bug
vim src/rcfile.c

quilt refresh

# Descriure patch segons DEP-3
quilt header -e

Description: add x-www-browser asd another built-in browser
Author: Nom i cognoms <email@example.net>
Date: 2012-12-16

# Visualitzar el patch

cat debian/patches/add-x-www-browser.patch

#####################
# Tornar a compilar
##

## Amb debuild

debuild -us -uc
debuild clean

## Amb cowbuilder

cd ..
dpkg-source -b bluefish-2.2.3
sudo cowbuilder --build bluefish_2.2.3-4.1.dsc

#################################
# Comprovar el bon funcionament
##

## Si hem treballat amb debuild:

cd ..
sudo dpkg -i bluefish-data_2.2.3-4.1_all.deb bluefish-plugins_2.2.3-4.1_i386.deb bluefish_2.2.3-4.1_i386.deb

## Si hem treballat amb cowbuilder:

cd /var/cache/pbuilder/result/
sudo dpkg -i bluefish-data_2.2.3-4.1_all.deb bluefish-plugins_2.2.3-4.1_i386.deb bluefish_2.2.3-4.1_i386.deb

# Si ho volem provar dins cowbuilder:

Afegir el hook F10vnc-interactive a /var/cache/pbuilder/hooks:

-------------------F10vnc-interactive---------------------------------
#!/bin/sh

# Let's plugin VNC!
export HOME=/root
echo force-confold >> /etc/dpkg/dpkg.cfg
DEBIAN_FRONTEND=noninteractive \
SHELL=/bin/true \
apt-get install -y twm xterm vnc4server xfonts-base expect
perl -i -pe 's/^force-confold//' /etc/dpkg/dpkg.cfg
mkdir -p /root/.vnc
cat<<EOF > $HOME/.vnc/xstartup
#!/bin/sh
xsetroot -solid grey
vnc4config -iconic &
xterm &
twm &
EOF
chmod 755 $HOME/.vnc/xstartup
vnc4passwd
vnc4server &
cat<<EOF >/usr/sbin/killvnc
export HOME=/root
ps -ef | grep [X]vnc | \
        awk '{ print \$9 }' | \
        xargs -l1 -i% --no-run-if-empty vnc4server -kill %
EOF
chmod 755 /usr/sbin/killvnc
echo "Run /usr/sbin/killvnc when you're done with VNC!"
echo "Otherwise, you will get an umount failure for /dev/pts!"
echo
---------------------------------------------------------------

sudo cowbuilder --login --inputfile bluefish_2.2.3-4.1_i386.deb --inputfile bluefish-plugins_2.2.3-4.1_i386.deb --inputfile bluefish_2.2.3-4.1_i386.deb

## Un cop hem entrat a cowbuilder:

xvnc4viewer

# i executem el programa.

#######################
# Reportar la solució
##

## Comprovem que el diff mostra només els canvis que hem fet:
debdiff bluefish_2.2.3-4.dsc bluefish_2.2.3-4.1.dsc

## Podem enviar al BTS directament aquest patch:
debdiff bluefish_2.2.3-4.dsc bluefish_2.2.3-4.1.dsc > add-x-www-browser.patch

## Podem usar nmudiff
cd bluefish-2.2.3
nmudiff

## si no s'és DD o no s'ha pujat la nova versió: esborrar tags 692284 + pending
## i canviar el text del mail

Més enllaços interessants:

Tutorial per aprendre a solucionar bugs a Debian: http://wiki.debian.org/BuildingTutorial

Cerca de RC Bugs: http://udd.debian.org/bugs.cgi

Diversos workflows per resoldre bugs:

http://info.comodo.priv.at/blog/articles/rcbw/

http://upsilon.cc/~zack/hacking/debian/rcbw/

http://dunetna.probeta.net/doku.php/debian:rcbw_release_critical_bugs_of_the_week_work_flow

Talk: Cómo empezar a colaborar en Debian

anonymous@undisclosed.example.com (Anonymous) — Thu, 18 Oct 2012 00:49:07 +0000

Description: Huge projects like Debian need a large amount of people that collaborate, but at the same time it's difficult to find where you can fit in such a big project. The talk has a brief introduction explaining the different channels of Debian organization and comunication and later gives some ways to collaborate: some of them very simple and others that need more knowledge and/or commitment.

Los proyectos de grandes dimensiones como Debian siempre necesitan una gran masa de gente que colabore, pero a la vez es difícil encontrar tu lugar en un proyecto tan grande. La charla contiene una breve introducción explicando los canales de organización y comunicación del proyecto Debian y después ofrece diferentes maneras de colaborar: desde las más simples hasta las que requieren más conocimientos y/o compromiso.

Language(s): Spanish

Slides files (with README): charla-debian-como-colaborar-en-debian.tar.gz

Slides online: http://dunetna.probeta.net/talks/charla-debian-como-colaborar-en-debian

Audio: charla-debian-como-colaborar-en-debian.ogg

Talk: Debian

anonymous@undisclosed.example.com (Anonymous) — Sun, 22 Apr 2012 19:59:48 +0000

Description: Talk about Debian.

Date: 2011-09-17

Place: Dia de la Llibertat del Programari

Language(s): Catalan

http://dunetna.probeta.net/talks/xerrada-debian-dia-llibertat-programari-2011-09-17/ xerrada-debian-dia-llibertat-programari-2011-09-17.tar.gz

Talk: Gestió de paquets amb Debian

anonymous@undisclosed.example.com (Anonymous) — Fri, 29 Mar 2013 20:44:59 +0000

Description: Talk about how to to manage packages in Debian.

Date: 2007-06

Place: Escola del Treball

Language(s): Catalan

paquetsdebian.odp paquetsdebian.pdf

Talk: Debian. El sistema operatiu lliure creat per la comunitat.

anonymous@undisclosed.example.com (Anonymous) — Tue, 24 Apr 2012 12:50:52 +0000

Description: Talk about Debian.

Date: 2012-04-20

Place: Institut Àusias March

Language(s): Catalan

http://dunetna.probeta.net/talks/xerrada-debian-institut-ausias-march-2012-04-20 xerrada-debian-institut-ausias-march-2012-04-20.tar.gz

Talk: Outreach Program for Women

anonymous@undisclosed.example.com (Anonymous) — Tue, 14 May 2013 10:26:52 +0000

Description: Talk about Outreach Progam for Women, lack of women in Debian and lack of women in FLOSS

Language(s): Catalan

Slides: xerrada-outreach-program-for-women.odp xerrada-outreach-program-for-women.pdf

Talk: Debian QA, una puerta de entrada al proyecto Debian

anonymous@undisclosed.example.com (Anonymous) — Mon, 17 Sep 2012 17:29:19 +0000

Description: Debian is a huge project. Some people want to get involved in the project but don't know where to start. Here you have a nice entrance gate: the Debian Quality Assurance Team. In this talk, there will be a basic introduction about what Debian QA is and we will see some tasks a newbie can do to help this Debian team.

Debian es un proyecto enorme. Cuando se quiere empezar a colaborar en el proyecto, muchas veces no se sabe por donde empezar. El Equipo de Calidad de Debian es una buena puerta de entrada. En esta charla, se dará una introduccón básica sobre qué es Debian QA y veremos algunas tareas que un principiante puede hacer para ayudar en este equipo de Debian.

Language(s): Spanish

Debconf page (with video): http://penta.debconf.org/dc12_schedule/events/917.en.html

Slides online: http://dunetna.probeta.net/talks/charla-debian-qa-una-puerta-de-entrada-proyecto-debian/

Slides files: charla-debian-qa-una-puerta-de-entrada-proyecto-debian.tar.gz

Useful links

anonymous@undisclosed.example.com (Anonymous) — Mon, 31 Dec 2012 14:39:55 +0000

Description: Links to Debian interesting resources.

Language(s): English

Allioth and git repositories: http://wiki.debian.org/Alioth/Git