Re: RFS: nautilus-image-manipulator
Hi mentors, I'd appreciate if somebody could have a look at this package. Thanks! +Emilien 2011/2/9 Emilien Klein emilien+deb...@klein.st: Dear mentors, I am looking for a sponsor for my package nautilus-image-manipulator. * Package name : nautilus-image-manipulator Version : 0.2-1 Upstream Author : Emilien Klein (me...) * URL : https://launchpad.net/nautilus-image-manipulator * License : GPL 3 Section : graphics It builds these binary packages: nautilus-image-manipulator - Resize and send images from Nautilus The package appears to be lintian clean (I believe I did all the modifications to address lintian's messages) The upload would fix these bugs: 611690 My motivation for maintaining this package is: getting my first package into Debian to learn how to become a Debian maintainer. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/n/nautilus-image-manipulator - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/n/nautilus-image-manipulator/nautilus-image-manipulator_0.2-1.dsc I would be glad if someone could review and upload this package for me. FYI This is my first package, and I would be happy to get feedback on what I possibly might have done wrong. Kind regards +Emilien -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikxz0-5dfbehkveqmm2wmmg34ghzxo9vzafq...@mail.gmail.com
Re: RFS: scidavis (updated package) - FTBFS
On Thursday 17 March 2011 17:21:08 Ruben Molina wrote: Dear mentors, I am looking for a sponsor for the new version 0.2.4-3 of my package scidavis. It builds these binary packages: scidavis - application for scientific data analysis and visualization The package appears to be lintian clean. The upload would fix these bugs: 618199 (FTBFS) The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/s/scidavis - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/s/scidavis/scidavis_0.2.4-3.dsc Uploaded. Thank you for taking care of the bugs. -- pub 4096R/0E4BD0AB people.fccf.net/danchev/key pgp.mit.edu signature.asc Description: This is a digitally signed message part.
co-maintainer on parcellite?
Andrew, Can I become a co-maintainer with you on parcellite? I do apologize for any confusion I've caused. Kind Regards, Doug Springer -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d8614fc.5060...@rickyrockrat.net
RFS: lilo (updated package, RC bug fix)
Dear mentors, I am looking for a sponsor for the new version 1:23.1-2 of my package lilo. It builds these binary packages: lilo - LInux LOader - the classic OS boot loader lilo-doc - LInux LOader - Documentation for the classic OS boot loader The package appears to be lintian clean. The upload would fix these bugs: 258472, 312451, 445264, 504733, 613753, 615103, 615936, 616691, 617282, 618004, 618253, 618620, 618711, 618738, 618801, 618813, 618886 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/l/lilo - Source repository: deb-src http://mentors.debian.net/debian unstable main - dget http://mentors.debian.net/debian/pool/main/l/lilo/lilo_23.1-2.dsc Details can be seen here: http://git.debian.org/?p=lilo/debian.git I would be glad if someone uploaded this package for me. And I would be most grateful if a kind sponsor would set the DM-Upload-Allowed (DMUA) bit. FYI here is the last changelog entry: * debian/control: - Remove dependency to lilo in package lilo-doc. (Closes: #613753) * Fix: save errno for second command (device.c). * Fix: save file permissions for converted lilo.conf (Closes: #615103) and fix some typos in script lilo-uuid-diskid. * Fix: missleading error message in geometry.c. (Closes: #445264) * Reformatting of mkrescue manpage (thanks to M.E. Schauer). (Closes: #617282) * debconf scripts: - Fix typos in some debconf translation files. (Closes: #504733) - Use better style in debconf translations. (Closes: #312451, #504733) - Remove debconf code for managing old boot/boot.b and similar files. - Remove no more needed debian/lilo.lintian-overrides file. - Remove script liloconfig and all appropriate debconf code. - Update of German translation (de.po). - Update of French translation (fr.po). (Closes: #615936) - Update of Russian translation (ru.po). (Closes: #616691) - Update of Galician translation (gl.po). - Update of Danish translation (da.po). (Closes: #618004) - Update of Basque translation (eu.po). (Closes: #618253) - Update of Czech translation (cs.po). (Closes: #618711) - Update of Spanish translation (es.po). (Closes: #618813) - Update of Finnish translation (fi.po). (Closes: #618886) - Update of Italian translation (it.po). (Closes: #618801) - Update of Brazilian Portuguese translation. (Closes: #618738) - Update of Swedish translation (sv.po). (Closes: #618620) * Add new script liloconfig, using template with comments, works with UUID, LABEL and disk-id for root and boot options. * Add new manpage for liloconfig, update of other manpages. * Fix typos and phrases in manpage of lilo.conf. (Closes: #258472) Kind regards Joachim Wiedorn -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110320161820.2e7d8...@jupiter.home
RFS: driftnet (updated package)
Dear mentors, I am looking for a sponsor for the new version 0.1.7-1 of my package driftnet. It builds these binary packages: driftnet - Picks out and displays images from network traffic The package appears to be lintian clean. The upload would fix these bugs: 608369, 616451 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/d/driftnet - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/d/driftnet/driftnet_0.1.7-1.dsc I would be glad if someone uploaded this package for me. Kind regards David Suarez -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201103201840.17418.david.sephi...@gmail.com
Re: RFS: driftnet (updated package)
Hi, The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/d/driftnet - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/d/driftnet/driftnet_0.1.7-1.dsc I would be glad if someone uploaded this package for me. The debian/watch file , could have a comment like this: # This package is currently built from a CVS repository, so no # non-trivial watch file is possible. I've reviewed the new package that is on mentors, and only have a few observations * The Standars Version should be 3.9.1 not 3.9.1.0 * copyright file in the source field: should be the homepage of the upstream now we have to wait for a DD to check more thoroughly, and if there're no problems, you can upload your package. Regards Daniel -- Epsilon http://www.rinconinformatico.net http://www.fitnessdeportes.com http://www.dragonjar.org Linux user: #477840 Debian user
Re: GSoC 2011 project APT/dpkg declarative diversions
I think you are on slightly the wrong list. I understand your confusion, this is the Debian mentors mailing list, but instead of GSoc mentoring, this list handles package mentoring. The list you want is the soc-coordination [1] list. Chris [1] soc-coordinat...@lists.alioth.debian.org On 19 March 2011 20:56, Rahul Gaur rahul@gmail.com wrote: Hi, I am pursuing bachelors in engineering and my majors is in Computer Science.I am planning to apply for GSOC 2011 would like to work with Debian over my summer vacations. I've been using open source operating system since last 2 years and ever since I went open-source there was no turning back . I've learned C++ and java @ school .Now here in college i'm studying C and Python(linux platform),getting a good grip of it and I'm really fascinated by the python language as well as C is evergreen language. Familiar with building softwares from the source code, using svn now here I'm seeking some guidance so that I can start contributing to the OpenSource community.By the time with GSoC starts , I would be done with my university exams and so I am interested in doing some C or Python based project during my summer vacations. Well among the several intriguing projects listed on the ideas page of GsoC 2011 , as I would like to get more informations about APT/dpkg declarative diversions... Awaiting reply -- Regards Rahul Gaur irc : iamaregee2/iamaregee blog : aregee.wordpress.com fb: http://facebook.com/iamaregee -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTiki6BdAykc7R_Sweajw3b0joy=trk2kvtuk+...@mail.gmail.com
Re: RFS: driftnet (updated package)
On Domingo 20 Marzo 2011 20:02:26 Daniel Echeverry escribió: * The Standars Version should be 3.9.1 not 3.9.1.0 * copyright file in the source field: should be the homepage of the upstream now we have to wait for a DD to check more thoroughly, and if there're no problems, you can upload your package. Regards Daniel Fixed. Thanks David -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201103202037.30668.david.sephi...@gmail.com
Git Package Versioning
Can anyone point me in the direction of a appropriate package versioning scheme when packaging software taken directly from a git vcs? Thanks, Chris -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1300652323.2995.3.ca...@chris-desktop.home
Re: Git Package Versioning
Hi, Le dimanche 20 mars 2011 à 21:18:43 (+0100 CET), Chris a écrit : Can anyone point me in the direction of a appropriate package versioning scheme when packaging software taken directly from a git vcs? The best I have found is to use something like: latest_upstream_release+gitMMDD.githash You need the date as the git hash are not sorted, and the date alone doesn't make sense in case you need to package 2 snapshots at the same date. I use the abbreviated hash and get the last commit as follows: git log -1 --format='%cd.%h' --date=short | sed 's/-//g' Cheers, Julien -- .''`. Julien Valroff ~ jul...@kirya.net ~ jul...@debian.org : :' : Debian Developer Free software contributor `. `'` http://www.kirya.net/ `- 4096R/ E1D8 5796 8214 4687 E416 948C 859F EF67 258E 26B1 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110320204826.ga22...@kirya.net
Re: Git Package Versioning
Julien Valroff jul...@debian.org wrote on 2011-03-20 21:48: The best I have found is to use something like: latest_upstream_release+gitMMDD.githash Please be aware, that + is not the optimal connector. Try dpkg --compare-versions and see: a) 1.2.0 is less than 1.2.0+git2011 b) 1.2.0 is greater than 1.2.0~git2011 The version b) is the better way. So please use ~ as connector. --- Have a nice day. Joachim (Germany) -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110320222538.00c87...@jupiter.home
Re: Git Package Versioning
On Sun, 20 Mar 2011 22:25:38 +0100, Joachim Wiedorn ad_deb...@joonet.de wrote: Julien Valroff jul...@debian.org wrote on 2011-03-20 21:48: The best I have found is to use something like: latest_upstream_release+gitMMDD.githash Please be aware, that + is not the optimal connector. Try dpkg --compare-versions and see: a) 1.2.0 is less than 1.2.0+git2011 b) 1.2.0 is greater than 1.2.0~git2011 The version b) is the better way. So please use ~ as connector. Except that Julien did mention using the latest upstream release version, which implies that the git hash is later than the upstream release, so '+' is correct... Here's an example with a timeline: | | 1.2.0 is released (if packaged, version 1.2.0-1 or whatever) | | new Debian package version, including git changes since 1.2.0 | | 1.2.1 is released | V In this example, the Debian package version could be either 1.2.0+gitMMDD.githash-1, which could be read as everything in the 1.2.0 release plus all changes since, up to git hash ... on MMDD, or 1.2.1~gitMMDD.githash-1, which could be read as the 1.2.1 release currently being prepared, as of git hash ... on MMDD. Which you choose would depend on whether you're packaging the release plus some fixes, or you're packaging a preview of the next release... Regards, Stephen -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110320231647.13dc6...@sk2.org
Re: Git Package Versioning
On Sun, 20 Mar 2011 22:25:38 +0100, Joachim Wiedorn ad_deb...@joonet.de wrote:
Please be aware, that + is not the optimal connector.
Try dpkg --compare-versions and see:
[snip]
The version b) is the better way. So please use ~
as connector.
That rather depends on your goal. If the version number is before the
current snapshot, then + is appropriate.
I like to use the output of git-describe, along with sed, something like
the following:
,
| SOURCEPKG=$(shell dpkg-parsechangelog | sed -n 's/^Source: \(.*\)/\1/p')
| UPSTREAM=$(shell dpkg-parsechangelog | sed -n 's/^Version:
\(.*\)-[^-]*/\1/p')
| SHA1=$(lastword $(subst ~g, ,$(UPSTREAM)))
| ORIG=${SOURCEPKG}_${UPSTREAM}.orig.tar.gz
|
| describe-current-version:
| git describe --tags upstream | sed 's,^release-,,;s,-,+,;s,-,~,;'
|
| get-orig-source:
| git archive --format=tar $(SHA1) | gzip -9 ../$(ORIG)
`
The output from ./debian/rules describe-current-version is pasted into
debian/changelog, and it makes things like
0.7.1+706~g1157b91-1
So here + really makes sense because it is 706 commits after tag
release-0.7.1
The second ~ could be a + as well, doesn't matter.
Your mileage, may, as they say, vary.
d
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/878vw9mopa.fsf@zancas.localnet
Re: Git Package Versioning
On Sun, Mar 20, 2011 at 10:25:38PM +0100, Joachim Wiedorn wrote: Julien Valroff jul...@debian.org wrote on 2011-03-20 21:48: The best I have found is to use something like: latest_upstream_release+gitMMDD.githash Please be aware, that + is not the optimal connector. Try dpkg --compare-versions and see: a) 1.2.0 is less than 1.2.0+git2011 b) 1.2.0 is greater than 1.2.0~git2011 The version b) is the better way. So please use ~ as connector. From what you write, my understanding is: * if upstream is working on master *after* 1.2.0 has been released, you should use +git; * if upstream is working *towards* 1.2.0, ~git is the one for you. By the way, +git seems safer to me, because upstream might change his mind (remember when GNOME folks thought 2.30 would be 3.0?). -- Andrea Bolognani e...@kiyuko.org Resistance is futile, you will be garbage collected. signature.asc Description: Digital signature
Re: RFS: scidavis (updated package) - FTBFS
El dom, 20-03-2011 a las 15:15 +0200, George Danchev escribió: On Thursday 17 March 2011 17:21:08 Ruben Molina wrote: I am looking for a sponsor for the new version 0.2.4-3 of my package scidavis. Uploaded. Thank you for taking care of the bugs. Thanks a lot! Best regards Ruben signature.asc Description: This is a digitally signed message part
Re: Git Package Versioning
Hi, Le dimanche 20 mars 2011 à 23:16:47 (+0100 CET), Stephen Kitt a écrit : On Sun, 20 Mar 2011 22:25:38 +0100, Joachim Wiedorn ad_deb...@joonet.de wrote: In this example, the Debian package version could be either 1.2.0+gitMMDD.githash-1, which could be read as everything in the 1.2.0 release plus all changes since, up to git hash ... on MMDD, It is indeed what I meant. or 1.2.1~gitMMDD.githash-1, which could be read as the 1.2.1 release currently being prepared, as of git hash ... on MMDD. Though it is perfectly correct, I try and avoid using this scheme: what happens if upstream releases eg. 1.2.1 Beta1 which I would normally version as 1.2.1~b1? Even if contact with upstream are good, the may change their mind. Take Firefox 4 which should have been released after the 1st RC… before they decide to release a 2nd RC. I think there's no universal answer to the original question, but just common sense and good use of `dpkg --compare-versions'. Cheers, Julien -- .''`. Julien Valroff ~ jul...@kirya.net ~ jul...@debian.org : :' : Debian Developer Free software contributor `. `'` http://www.kirya.net/ `- 4096R/ E1D8 5796 8214 4687 E416 948C 859F EF67 258E 26B1 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110321053618.ga12...@kirya.net
