Re: Ad hominem attacks (was: Re: RFS: ripit (updated package))
On Sun, Apr 26, 2009 at 20:16, Neil Williams codeh...@debian.org wrote: On Sun, 26 Apr 2009 19:40:57 +0200 Sandro Tosi mo...@debian.org wrote: Your work is appreciated, as the latest upload from other DDs (sorry, I came late ;) ) shows clearly, and I want to encourage you do to more :) Neil, I don't think you can argue that much, since your last sponsored package goes back at the dinosaur ages... ? Umm, where does that come from ? ehm, it came out very bad, apologize for that. I haven't had much time since Lenny (certainly nowhere near as much as before the Lenny freeze began last year) but I have sponsored 2 uploads since Lenny via mentors.debian.net and reviewed one other. That's not bad for two months, considering my other workload. I don't upload massive numbers of packages but I do sponsor when I can. Let me rephrase the above concept like: you don't seem to sponsor that much, probably because of your too high expectation from sponsoree (see the other thread). Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: ripit (updated package)
On Sun, Apr 26, 2009 at 20:25, Neil Williams codeh...@debian.org wrote: On Sun, 26 Apr 2009 19:55:59 +0200 Sandro Tosi mo...@debian.org wrote: I strongly think that even sponsoring a single package let the sponsoree be really happy for the work he did and was accepted as valuable. I agree too. And also the user base would be happy to see an improved package (with bugs fixed, new features and so) and also we developers should be thankful for the time the guy dedicate to learn how to do packaging in the Debian way and apply to the current package. Also agree. I'm happy we share this vision :) As a side note: I think Neil wrote his sponsorship notes with the only goal to avoid sponsorship at all That was definitely not my intention. (as I experienced in the past directly). ? I have not changed the notes in order to prevent any sponsoring. I have merely updated the notes as a direct result of issues that have arisen when reviewing packages in order to ensure that I can provide a sensible review of the package prior to upload. It also reflects the amount of work I do elsewhere and the impact that this has on the amount of time that I can assign to areas with which I am not directly familiar. Well, I think they are too many, too complex, and you put too much expectation into new comers packages. They are supposed (well, sort of ;) ) to do some mistakes, and we are here to correct them. What I always felt reading your guidelines is something only some skilled DD can respect (so even some DD would fail). I do not remember what could have given you that impression, Sandro. That happen on August '08, with dbishell. The feeling I got was demotivational and angry. I did some work, in order to have a better package in Debian, and you tried to push it back as hard as possible. You could have been right about all the notes you made, but the taste left in my mouth was bad. And I think Rogério feels the same. I think that we should help new people to find something they like in Debian, and work on it (and hopefully become valuable contributors), instead of attack them or being demotivational. Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: How to build-depend on linux-headers
+ Luca Niccoli (Mon, 27 Apr 2009 01:25:18 +0200): 2009/4/27 Jonas Meurer jo...@freesources.org: Hey, I'm not absolutely sure about it, but linux-libc-dev might be the answer to your questions. Yes! I was completely mistaken, I thought the headers I needed were in my system because I had linux-headers-whatever installed... But then do I have to explicitly depend on it? I see libc6-dev depends on it, and in turn build-essentials depend on libc6-dev (that's why the package builds in pbuilder even with the wrong dependency...) No, you don’t have to build-depend on linux-libc-dev because of the reasons you explained (libc6-dev depending on it and libc6-dev being build-essential). Cheers, -- - Are you sure we're good? - Always. -- Rory and Lorelai -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: shutter
Hello, On Mon, Apr 27, 2009 at 07:41, Ryan Niebur ryanrya...@gmail.com wrote: Dear mentors, I am looking for a sponsor for my package shutter. * Package name : shutter Version : 0.70.2-1 Upstream Author : Mario Kemper and Shutter Team * URL : http://shutter-project.org/ * License : GPL-3+ Section : graphics It builds these binary packages: shutter - feature-rich screenshot program The package appears to be (mostly) lintian clean. There is an info from lintian, desktop-entry-contains-encoding-key, but I don't want to use quilt for just that, and it doesn't hurt to leave it in for now. I have reported a bug upstream and it's already been fixed in their VCS for the next release. The upload would fix these bugs: 522721 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/s/shutter - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/s/shutter/shutter_0.70.2-1.dsc I would be glad if someone uploaded this package for me. sounds OK for me, but a few question: 1. why it build depends on debhelper = 7.2 (instead of = 7) 2. do you use any version control on this package? thanks. -- Best Regards LI Daobing -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: ripit (updated package)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sandro Tosi wrote: On Sun, Apr 26, 2009 at 20:25, Neil Williams codeh...@debian.org wrote: ? I have not changed the notes in order to prevent any sponsoring. I have merely updated the notes as a direct result of issues that have arisen when reviewing packages in order to ensure that I can provide a sensible review of the package prior to upload. It also reflects the amount of work I do elsewhere and the impact that this has on the amount of time that I can assign to areas with which I am not directly familiar. Well, I think they are too many, too complex, and you put too much expectation into new comers packages. They are supposed (well, sort of ;) ) to do some mistakes, and we are here to correct them. What I always felt reading your guidelines is something only some skilled DD can respect (so even some DD would fail). I am new at deb packaging. I think Neil's guidelines [1] is good and reasonable. I am not an DD nor an DM. I have not start my NM process yet. I am not an experienced programer. I only know a little C and shell programing. Neil's guidelines is clear, simple, and helps new maintainers to keep their packages good. I do know some Debian official packages maintained by some DDs would fail to meet Neil's guidelines. It is their problem, not Neil's. It is good for new maintainers to read the checklist [2] on Debian wiki. Kind regards Wen-Yen Chuang [1] http://people.debian.org/~codehelp/#sponsor [2] http://wiki.debian.org/SponsorChecklist -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkn1lBAACgkQdEpXpumNYVl3agCfYTeHSyrL/KUszm4oYwd/5MSi LxIAnjMhrLBclby0NObCyeOVP/eSUdEV =uI7X -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: boats
Hello, On Sun, Apr 26, 2009 at 07:31, Thibaut GRIDEL tgri...@free.fr wrote: Dear mentors, I am looking for a sponsor for my package boats. * Package name : boats Version : 200904-1 Upstream Author : Thibaut GRIDEL tgri...@free.fr * URL : http://boats.berlios.de * License : GPLv3 Section : x11 It builds these binary packages: boats - a race scenario drawing tool The package appears to be lintian clean. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/b/boats - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/b/boats/boats_200904-1.dsc The corresponding ITP is #525611. I would be glad if someone reviewed and uploaded this package for me. comments: 1. does not close ITP bug in changelog 2. no menu and no desktop file, please consider provide at least one of them. 3. Vcs-Git in debian/control should point to the debian branch you powered Debian, thanks. -- Best Regards LI Daobing -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: kcometen4
On Tue, Apr 21, 2009 at 22:50, LI Daobing lidaob...@debian.org wrote: Hello, On Tue, Apr 21, 2009 at 07:18, John Stamp jst...@users.sourceforge.net wrote: Dear mentors, I am looking for a sponsor for my package kcometen4. * Package name : kcometen4 Version : 1.0.4-1 Upstream Author : John Stamp jst...@users.sourceforge.net * URL : http://www.mehercule.net/staticpages/index.php/kcometen4 * License : GPL-2+ Section : kde It builds these binary packages: kcometen4 - An OpenGL KDE screensaver with lightning and comets The package appears to be lintian clean. The upload would fix these bugs: 441351 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/k/kcometen4 - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/k/kcometen4/kcometen4_1.0.4-1.dsc I would be glad if someone uploaded this package for me. +1 sounds good, also lintian clean. any other sponsor can have a double check? uploaded. -- Best Regards LI Daobing -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RFS: scid (updated package)
Dear mentors, I am looking for a sponsor for the new version 3.7.3-1 of my package scid. It builds these binary packages: scid - chess database with play and training functionality The package appears to be lintian clean. The upload would fix these bugs: 465788, 487771 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/s/scid - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/s/scid/scid_3.7.3-1.dsc I would be glad if someone uploaded this package for me. I have contacted the previous maintainer (see also #487771). He agreed that I may continue maintaining the package for Debian. Since the previous upload (aug-08) I have made massive changes in the build proces after some feedback from (Sandro Tosi). One thing I cannot resolve. I cant get in my full name because the key is not known then :( Kind regards W. van den Akker -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Question about README.source
I didn't found any standard template for DFSG and various files removing for README.source, so can I use the following generic sentence ? The following files were removed from the original source tree: CMakeLists.txt~ ftp.cpp~ ftp.h~ ftp.protocol~ README~ rfc4217.txt Or do I have to specify the reason of the removing ? Do I have to separate DFSG-compliance removing and other removing (in this case useless temporary backup files) ? Thank you, -- Laurent Léonard signature.asc Description: This is a digitally signed message part.
Re: RFS: scid (updated package)
Hi Dne Mon, 27 Apr 2009 14:25:00 +0200 (CEST) W. van den Akker list...@wilsoft.nl napsal(a): I have contacted the previous maintainer (see also #487771). He agreed that I may continue maintaining the package for Debian. Since the previous upload (aug-08) I have made massive changes in the build proces after some feedback from (Sandro Tosi). One thing I cannot resolve. I cant get in my full name because the key is not known then :( How about adding new uid? Comments on package (I just did quick look, not full review): Following files seems to be useless: debian/scid-doc.docs debian/scid2-doc.install Watch file fails: http://scid.sourceforge.net/download/ failed: 403 Forbidden -- Michal Čihař | http://cihar.com | http://blog.cihar.com signature.asc Description: PGP signature
RFS: scid (updated package)
Dear mentors, I am looking for a sponsor for the new version 3.7.3-1 of my package scid. It builds these binary packages: scid - chess database with play and training functionality The package appears to be lintian clean. The upload would fix these bugs: 465788, 487771 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/s/scid - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/s/scid/scid_3.7.3-1.dsc I would be glad if someone uploaded this package for me. I have contacted the previous maintainer (see also #487771). He agreed that I may continue maintaining the package for Debian. Since the previous upload (aug-08) I have made massive changes in the build proces after some feedback from (Sandro Tosi). One thing I cannot resolve. I cant get in my full name because the key is not known then :( Kind regards W. van den Akker -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Skipping check of source package
hi, i just uploaded an update to the redmine package, and i see that : Lintian report: N: Skipping check of source package redmine is displayed in my mentor console. did i do something wrong ? Regards, Jérémy Lal -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Question about README.source
2009/4/27 Laurent Léonard laur...@open-minds.org: I didn't found any standard template for DFSG and various files removing for README.source, so can I use the following generic sentence ? I personally prefer to write a get-orig-source target that shows exactly how the orig.tar.gz was constructed. Usually a couple of comments about the reasons for file removal are appropriate in that target. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: shutter
Hi! On Mon, Apr 27, 2009 at 07:22:45PM +0800, LI Daobing wrote: sounds OK for me, but a few question: 1. why it build depends on debhelper = 7.2 (instead of = 7) sorry, it should have been 7.0.50, but out of habbit I wrote 7.2.. fixed now. anyway, the newer version is needed because I'm using override_* targets in debian/rules. 2. do you use any version control on this package? yep, forgot to add Vcs-* fields. Added now, same URL. Thanks, Ryan -- _ Ryan Niebur ryanrya...@gmail.com signature.asc Description: Digital signature
Writing debian/watch for project located at ohloh
Hi, I am currently trying to create a package for something which hosts its files only on ohloh's download services. The files can be found at https://www.ohloh.net/p/mereo/download?package=stable I started with following file: --- version=3 https://www.ohloh.net/p/mereo/download?package=stable \ /p/mereo/download\?filename=mereo_(.*)_src.zip --- This works quite good to get informed about the current version, but the download doesn't work at all. $ uscan --download cppcheck: Newer version (1.8.0) available on remote site: https://www.ohloh.net/p/mereo/download?filename=mereo_1.8.0_src.zip (local version is 1.3) cppcheck: Successfully downloaded updated package download Will (as you can read above) only create a file called 'download'. Inside is a html file with the link hidden somewhere. Does anyone has experience or an idea how to write a working debian/watch file for such a project? Greetings, Resul Cetin -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Writing debian/watch for project located at ohloh
On Mon, Apr 27, 2009 at 11:01 PM, Resul Cetin resul-ce...@gmx.net wrote: Will (as you can read above) only create a file called 'download'. Inside is a html file with the link hidden somewhere. Does anyone has experience or an idea how to write a working debian/watch file for such a project? Potential options: Use your current watch file and manually do the download every time you have a new upstream version. Create an ohloh.debian.net redirector site. Ask upstream to also host their downloads on another site. Ask ohloh if they could remove the javascript redirector page. Ask ohloh to provide an alternate view of the download page without the javascript redirects. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Writing debian/watch for project located at ohloh
Am Montag, den 27.04.2009, 17:01 +0200 schrieb Resul Cetin: Hi, I am currently trying to create a package for something which hosts its files only on ohloh's download services. The files can be found at https://www.ohloh.net/p/mereo/download?package=stable I started with following file: --- version=3 https://www.ohloh.net/p/mereo/download?package=stable \ /p/mereo/download\?filename=mereo_(.*)_src.zip --- This works quite good to get informed about the current version, but the download doesn't work at all. $ uscan --download cppcheck: Newer version (1.8.0) available on remote site: https://www.ohloh.net/p/mereo/download?filename=mereo_1.8.0_src.zip (local version is 1.3) cppcheck: Successfully downloaded updated package download Will (as you can read above) only create a file called 'download'. Inside is a html file with the link hidden somewhere. Does anyone has experience or an idea how to write a working debian/watch file for such a project? You can manipulate the download URL and the filename via an opts line and downloadurlmangle and filenamemangle in your watch file. As far as I understand the cloudfront-concept, the distribution ID is always the same for a project. Check the attached watch file. It works here. Regards, Daniel watch.mereo Description: application/fluid
Re: RFS: dnshistory (updated package)
Matthias Julius li...@julius-net.net writes: I am looking for a sponsor for the new version 1.3-2 of my package dnshistory. It builds these binary packages: dnshistory - Translating and storing of IP addresses from log files The package appears to be lintian clean. The upload would fix these bugs: 434881 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/d/dnshistory - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/d/dnshistory/dnshistory_1.3-2.dsc I have contacted my previous sponsor twice in the last couple of weeks. He did not respond to my emails. I would be glad if someone uploaded this package for me. I would really be grateful if someone could take a look at this package and possibly upload it for me. Besides fixing that minor man page bug this is essentially a house-keeping upload. Here is the changelog entry for this upload: , | dnshistory (1.3-2) unstable; urgency=low | | * Acknowledge NMU | * Fix default location of database file in man page (Closes: #434881) | * Update Standards-Version to 3.8.1 | * Don't ship config.guess and config.sub in source package, we take them from | autotools-dev anyway | * Make Homepage its own field in debian/control | * Now using quilt; added debian/README.sources | | -- Matthias Julius m...@julius-net.net Fri, 13 Mar 2009 13:27:43 -0400 ` Matthias -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Question about README.source
Laurent Léonard laur...@open-minds.org writes: I didn't found any standard template for DFSG and various files removing for README.source, so can I use the following generic sentence ? The following files were removed from the original source tree: CMakeLists.txt~ ftp.cpp~ ftp.h~ ftp.protocol~ README~ rfc4217.txt I'd put that information in debian/copyright instead. (What you have sounds fine, or you could just say that you removed rfc4217.txt for DFSG reasons and, since you were repackaging the source anyway, removed all *~ files.) -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RFS: fsprotect (try #3)
Dear mentors, I am looking for a sponsor for my package fsprotect. In this message there is also a summary of everything that was discussed in this list. * Package name: fsprotect Version : 1.0.2 Upstream Author : Stefanos Harhalakis v...@v13.gr (me) * URL : http://www.v13.gr/proj/fsprotect/ * License : GPL Section : admin It builds these binary packages: fsprotect - Helper scripts to make filesystems immutable The package appears to be lintian clean (with an override, but see bellow). Description: fsprotect is a set of scripts that make immutable the root and other filesystems. Using aufs they pack a tmpfs filesystem and the filesystem forcing changes to be written to the tmpfs. The root filesystem is protected by an initramfs script. Other filesystems are protected by an init script. All protected filesystems become read-only ensuring their immutability even on power-offs. This can be used for public computers to prevent damage or changes. It is ideal for: * Public computers. It keeps all files intact, no matter what the user does. * Testing. i.e. KDE3 - KDE4 or etch - lenny upgrades * Security (also requires adequate paranoia) Fsprotect can be seen as an opensource alternative to deepfreeze for linux. Example usage: -- * apt-get install aufs-modules-2.6-amd64 fsprotect * read /usr/share/doc/fsprotect/README.Debian and/or /usr/share/doc/fsprotect/fsprotect.pdf.gz * add line fsprotect=1000M to /boot/grub/menu.lst as a kernel parameter * run update-grub * possible modify /etc/default/fsprotect to include a line like: PROTECT=/var=1000M /home=2000M * reboot At this point you can do rm -rf /bin/* -or- upgrade to KDE4 -or- do apt-get dist-upgrade -t unstable -or- perform whatever destructive action you never dared to (except messing with the partitions and doing raw writes on block devices). To check that the filesystems are actually protected, just run 'is_aufs / echo OK' After rebooting, the system will be in the same condition as when it was before the fsprotect installation. Debian native: -- fsprotect is 100% tied to a distribution. It cannot be an independent program that is packaged for debian or other distributions. The core functionality is provided by one init script and one initramfs script/hook and those are depending very much to the distribution. I.e the init script must run immediately after the filesystems are mounted and before anything else is ran. fsprotect cannot be practically spliced to .orig and .diff. There is no clear distinction between what will go in debian/ and what will be left out. Attempting to make it a non-native package will result in a package that does one or more of the following: a) includes debian specific scripts outside of debian/ b) contains debian specific scripts in .orig.tar.gz c) uploads a new .orig.tar.gz when other debian packages change The source code is small and the most part of it is inside debian/. The output of the du is: $ du -sk fsprotect/* 264 fsprotect/debian 156 fsprotect/doc 56 fsprotect/initramfs-tools 20 fsprotect/lib 20 fsprotect/sbin while doc/ contains debian-specific documentation in pdf form. NMUs may use versions like 1.0.2+nmu1 Lintian overrides: -- fsprotect overrides the virtual-package-depends-without-real-package-depends lintian warning. This is done because it depends on aufs modules which are provided as debian packages and it isn't a good idea (or even possible) to depend on packages like this one: aufs-modules-2.6.29-v2-v (which for example, is the module compiled for the custom kernel of my system). I've made fsprotect depend on aufs-modules which is provided my aufs-modules-* packages. In general, it isn't possible to depend on a specific modules version. Changes: fsprotect used to create the directory /fsprotect upon installation. This is no longer happening. The directory is created in the volatile space whenever fsprotect is active. This means that such a directory will never be written in the disk and will never be visible when fsprotect isn't active. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/f/fsprotect - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/f/fsprotect/fsprotect_1.0.2.dsc I would be glad if someone uploaded this package for me. Kind regards Stefanos Harhalakis -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#523338: ITP: radare -- Free advanced command line hexadecimal editor
On Sun, Apr 26, 2009 at 07:41:09PM +0200, Reinhard Tartler wrote: AFAIUI sponsor requests should go to debian-mentors. Please not that I'm not a mentors regular, so I'm not really sure of the exact procedures here. Nevertheless, I'm copying the mailing list. I know, but you told me before to just answer to the ITP, so I did so. My preliminary review of http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=radare * spurious configure target, please remove it. done in 1.3-3 * build-target could be improved, e.g. by placing both variants in different make targets. also consider a VPATH build. there is build-gtk, built-nongtk and build-doc target in 1.3-3 * clean rules unpatches before running clean. This will break if you had modifications to the clean parts of the build system. You don't do that here, but I'm mentioning it just in case. I didn't change this, since I'll ask upstream to fix problems in the clean parts of the build system. The lua change is just needed because it's debian specific. In general, run the tool `devscripts -r .` in the top level root directory to get a brief license check. AFAIUI this is the tool ftpmaster uses to examine NEW packages. uhm where do I get devscripts? The devscripts package does not contain it! I fear debian/copyright needs to mention all this. Are there other opinions on that from mentors? I've updated debian/copyright with all licenses I found. -- Sebastian signature.asc Description: Digital signature
Re: Bug#523338: ITP: radare -- Free advanced command line hexadecimal editor
On Mon, 27 Apr 2009 21:34:50 +0200 Sebastian Reichel elektra...@gmail.com wrote: In general, run the tool `devscripts -r .` in the top level root directory to get a brief license check. AFAIUI this is the tool ftpmaster uses to examine NEW packages. uhm where do I get devscripts? The devscripts package does not contain it! I fear debian/copyright needs to mention all this. Are there other opinions on that from mentors? $ licensecheck -r . (from the devscripts package) -- Neil Williams = http://www.data-freedom.org/ http://www.linux.codehelp.co.uk/ http://e-mail.is-not-s.ms/ pgpWCSNb79vOU.pgp Description: PGP signature
Re: Writing debian/watch for project located at ohloh
On Monday 27 April 2009 17:45:32 Daniel Leidert wrote: You can manipulate the download URL and the filename via an opts line and downloadurlmangle and filenamemangle in your watch file. As far as I understand the cloudfront-concept, the distribution ID is always the same for a project. Check the attached watch file. It works here. Thanks. It looks quite good. I hadn't checked if the ID is always the same, but I looked at it after you mentioned it. I thought that it was somehow autogenerated each time. Regards, Resul -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: scid (updated package)
On Monday 27 April 2009 14:32:37 Michal Čihař wrote: Hi Dne Mon, 27 Apr 2009 14:25:00 +0200 (CEST) W. van den Akker list...@wilsoft.nl napsal(a): I have contacted the previous maintainer (see also #487771). He agreed that I may continue maintaining the package for Debian. Since the previous upload (aug-08) I have made massive changes in the build proces after some feedback from (Sandro Tosi). One thing I cannot resolve. I cant get in my full name because the key is not known then :( How about adding new uid? Comments on package (I just did quick look, not full review): Following files seems to be useless: debian/scid-doc.docs debian/scid2-doc.install Watch file fails: http://scid.sourceforge.net/download/ failed: 403 Forbidden removed the scid-doc.docs and scid2-doc.install Also changed the Watch file. Uscan doesnt report an error Gr, Willem -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: boats
Hello again, * LI Daobing [2009-04-27 13:34]: Hello, On Sun, Apr 26, 2009 at 07:31, Thibaut GRIDEL tgri...@free.fr wrote: Dear mentors, It builds these binary packages: boats - a race scenario drawing tool The package appears to be lintian clean. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/b/boats - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/b/boats/boats_200904-1.dsc I would be glad if someone reviewed and uploaded this package for me. comments: 1. does not close ITP bug in changelog Done. 2. no menu and no desktop file, please consider provide at least one of them. I have provided upstream desktop file, sharedmimeinfo and icons then used those in debian/rules 3. Vcs-Git in debian/control should point to the debian branch AFAIU, it is not possible to specify a particular branch with Vcs-Git naming (seen #508433 and didn't find better Vcs-Git info with regards branches). Hence I removed the entry. you powered Debian, thanks. still L plates... Best Regards, Thibaut -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: mimelib 1.1.2 packages: strlcpy/strlcat vs. strcpy/strcat
Hi, On Fri, Apr 24, 2009 at 2:17 AM, Jonas Meurer jo...@freesources.org wrote: Hello, I plan to package libmimelib 1.1.2 for debian/unstable. Until now this has been built/provided by kdepim from kde3, but as part of the kde4 transition kdepim3 has been removed from debian/unstable. Still lurker depends on libmimelib1c2a, and migrating to libmimelib4 is not an option as it would introduce tons of kdelibs dependencies that lurker doesn't need at all. So I copied kdepim-3.5.9/mimelib/ from the kdepim 3.5.9-5 source package in order to build a standalone source package from it. Now I've one problem: kde developers have patched mimelib heavily since it has been added to kdepim, and one of the changes is to use strlcpy/strlcat at some places. Unfortunately, strlcpy/strlcat seems not to be available on a standard linux system. Only stncpy/strncat and strcpy/strcat are. The original standalone mimelib used strcpy/strcat, but mimelib is in fact unmaintained upstream since 1997, so there is no real upstream version available. Instead I found more than five different patched versions of mimelib in the web, all of them differing a lot. I am not a Debian Developer, and as a matter of fact this is my very first mail to this list. But I am a regular programmer, and I shortly looked into this issue. Your assumption that strlcpy is not available on a standard Linux system does not seem to be entirely correct, as the corresponding wikipedia article will tell you: http://en.wikipedia.org/wiki/Strlcpy There you can also find a link to an article which gives you some more background information: http://lwn.net/Articles/33812/ A simple grep -r 'size_t strlcpy' in the source directory of the kernel shows that the function is indeed defined for the kernel in $source/include/linux/string.h and is implemented in $source/lib/string.c. As the wikipedia article also mentions, it is not part of the GNU C library. But in glib you have a function called g_strlcpy which is a wrapper for strlcpy. I would like to package the kdepim 3.5.9 version of mimelib. So what to do? As far as I understand, there are three possibilities: - patch mimelib from kdepim to use strcpy/strcat again, but I guess this is not a good idea as strcpy/strcat seem to be insecure. - patch mimelib from kdepim to use strncpy/strncat instead of strlcpy/strlcat. - define strlcpy/strlcat in a custom header file and include that one where appropriate. I cannot really tell you how this issue should be addressed in Debian, but it seems to be a known, and rather old issue, so I am sure some DD must know the proper solution, or rather, the accepted Debian way. However, from your three proposed options, only the third seems sensible to me, since the other two would require serious patching in order to keep the code bug free. I could also imagine that kde defines its own version of the function somewhere. Kind regards, Aljoscha -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: mimelib 1.1.2 packages: strlcpy/strlcat vs. strcpy/strcat
Aljoscha Lautenbach aljoscha.lautenb...@gmail.com writes: A simple grep -r 'size_t strlcpy' in the source directory of the kernel shows that the function is indeed defined for the kernel in $source/include/linux/string.h and is implemented in $source/lib/string.c. That unfortunately doesn't help unless you're writing kernel modules. That's an implementation inside the kernel only for code running inside the kernel; it isn't available to normal programs. I just provide replacement implementations of strlcpy and strlcat with all of the software I write that ends up needing to use it. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: gnome-inm-forecast (updated package)
On Sun, Apr 19, 2009 at 04:24:15PM +0200, Gustavo Iñiguez Goya wrote: On Mon, Apr 06, 2009 at 01:13:30AM +0200, Gustavo Iñiguez Goya wrote: Dear mentors, I am looking for a sponsor for the new version 0.8.0-1 of my package gnome-inm-forecast. It builds these binary packages: gnome-inm-forecast - Spanish weather forecast applet for the GNOME panel The package appears to be lintian clean. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/g/gnome-inm-forecast - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/g/gnome-inm-forecast/gnome-inm-forecast_0.8.0-1.dsc I would be glad if someone uploaded this package for me. I would be glad if someone could take a look at it. Thank you very much in advance. After reading the ripit package thread, I'd like to explain myself a bit more about this package. I did not realize either, that the RFS template not included the long description, otherwise I would have added it. gnome-inm-forecast displays on the gnome-panel, the weather forecast for the following 7 days. Unlike others applets like gweather, this applet does not display the current weather for a particular location, but as I've said, the weather forecast for the next days. It gets the information from the Spanish Meteorological Agency, which offers several weather services that no others sites do. For example, you can display specific satellite images of different types: evolution of the air masses, last lightnings detected, storms evolution, etc. There're several interestings maps as well for the next day: rainfall probability, weather forecast map, max and minimum temperatures map. And probably, the most valuable feature of this applet (site), is that you can read the latest avalanches reports/warnings for the Pyrenees. Besides general conditions reports for the most important mountains chains of Spain (added in this version). By the technical side, an important bug has been fixed, which caused to not work on GNOME 2.26: https://bugs.launchpad.net/ubuntu/+source/gnome-inm-forecast/+bug/351398 GNOME 2.26 is not yet in unstable, but in experimental (hopefully): http://packages.qa.debian.org/g/gnome-panel.html It used to crash on 64bit architectures, and that is fixed as well. Regarding the debian/ files: watch file improved to match correctly the new upstream releases. control file updated with the new added features. Here are some screenshots: http://kutxa.homeunix.org/trac/gnome-inm-forecast/wiki/ScreenShots Thanks in advance if someone have enough time for review/upload it for me. Regards, Gustavo. Kind regards Gustavo Iñiguez Goya -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: ripit (updated package)
Neil Williams codeh...@debian.org writes: On Sun, 26 Apr 2009 19:55:59 +0200 Sandro Tosi mo...@debian.org wrote: As a side note: I think Neil wrote his sponsorship notes with the only goal to avoid sponsorship at all That was definitely not my intention. Well, I have to say that upon reading them when first visiting mentors.debian.net with a new package in my hands, hoping for a sponsor, I was a bit put off. I am not too interested in being sponsored by your kind, to be honest. (Which probably makes us both happy, so it's a winwin. :) I understand that you want people to come to you with a very good package already, and that you don't want to waste time on a hopeless case. Some prepared documents and checklists are certainly useful for potential sponsorees, but there is more than one way to convey the message, of course. I think your list of requirements is great, technically, and they would be much better if you would teach more than you scold, and emphasize success over failure. E.g., you say Do not resort to cp or mv hacks. Use the tools and use them properly. How should this be understood by a fledgling who has made hist first barely working debian/rules files that has a cp in it? That the mere act of using cp makes him not worthy of ever being shown how to do it right? Isn't it nicer to read something like this following? Here are some rules that I follow in my own packages, and you should follow them, too. I have found that they make package maintaince easier in the long run, and lead to high quality packages. If you have questions about how to follow some of these rules, please ask on debian-mentors@lists.debian.org instead of asking me personally. You will reach more people that are able to answer your questions that way. [...] - Use CDBS or debhelper in debian/rules. Try to avoid the explicit use of cp, mv, chmod, etc. CDBS and debhelper are quite flexible and can do a lot of things that make explicit file manipulations unnecessary. Invest the time to learn them well. If really needed, prefer patching the upstream Makefile to do the right thing to using cp etc in debian/rules. (See the section on how to maintain patches below.) Fwiw, I enjoy being a smug asshole from time to time, but it's never good to abuse a position of power for that little delight. You are in a position of power and have exposed yourself, so don't be an asshole about it. I am not saying you are, don't get me wrong. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: gnome-inm-forecast (updated package)
Hi Gustavo, On Tue, Apr 28, 2009 at 02:03:58AM +0200, Gustavo Iñiguez Goya wrote: Here are some screenshots: http://kutxa.homeunix.org/trac/gnome-inm-forecast/wiki/ScreenShots Please consider uploading some screenshots of it on Debian to http://screenshots.debian.net/ Thanks in advance if someone have enough time for review/upload it for me. I cannot upload it, as I am not a DD, however I tried to check this package, but can't seem to build it in cowbuilder or sbuild chroots. The problem under sbuild looks to be not your fault, but maybe a bug should be filed against the package causing it? The problem under cowbuilder definitely seems to be a missing build dependency. Perhaps a build dependency on libglade2-dev is needed? anyway, I'm leaving now, so can't check. I haven't check anything else but building in chroots yet, I may be able to do more reviewing later. My build logs are available here: http://ryan52.info/~ryan52/gnome-inm-forecast/1/ Thanks, Ryan -- _ Ryan Niebur ryanrya...@gmail.com signature.asc Description: Digital signature
Criteria for sponsoring packages (was: RFS: ripit (updated package))
Wen-Yen Chuang ca...@calno.com writes: I am new at deb packaging. I think Neil's guidelines [1] is good and reasonable. I am not an DD nor an DM. I have not start my NM process yet. I am not an experienced programer. I only know a little C and shell programing. Neil's guidelines is clear, simple, and helps new maintainers to keep their packages good. I have found Neil's guidelines invaluable ever since I've been packaging, even though Neil and I have never even discussed the possibility of him becoming my sponsor. I'm glad to see them clearly laid out online and, even better, updated From time to time as his personal sponsoring policies adapt. I do know some Debian official packages maintained by some DDs would fail to meet Neil's guidelines. Note that not everything in Neil's guidelines are appropriate to *every* package. Rather, it's best to see them as a coherent set of questions to *have good answers to*, for every package that one prepares. Neil's guidelines, and other similar checklists by other sponsors, are very helpful to prompt me to think about my package from a critical perspective, which is very difficult to achieve in isolation. -- \ “Why, I'd horse-whip you if I had a horse.” —Groucho Marx | `\ | _o__) | Ben Finney pgpwbsbFJD3zx.pgp Description: PGP signature
Documenting new upstream version in ‘debian/c hangelog’ (was: Uploaded)
Adeodato Simó d...@net.com.org.es writes: * Please only close bugs with a “New upstream version” message if they’re actually a wishlist bug asking for the new version to be packaged. In case they are actual bugs, please do something like: * New upstream release: + does not prepend “fast” to the “insane” preset. (Closes: #501925) + copes with lame sending --genre-list output to stderr. (Closes: #490082) + fixes genre parsin or whatever. (Closes: #517561) I hope you’ll agree that’s more useful for the person reading the changelog, and it only takes a bit more effort. No need to retroactively edit the changelog, though. I wholeheartedly agree with this, and would go further: even if there are no Debian BTS reports to close, you should *still* give the highlights of a new upstream version in the ‘debian/changelog’. I'm utterly uninformed by a bare “New upstream release.”; of course it's a new upstream release, I can already see that from the version number. This is a changelog, tell me *what changed* in this new upstream version. That's my morning rant out of the way, I hope you all enjoyed it as much as I did. -- \ “An idea isn't responsible for the people who believe in it.” | `\ —Donald Robert Perry Marquis | _o__) | Ben Finney -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Documenting new upstream ver sion in ‘debian/changelog’ (was: Uploaded)
Hi, On Tue, Apr 28, 2009 at 11:31:35AM +1000, Ben Finney wrote: I wholeheartedly agree with this, and would go further: even if there are no Debian BTS reports to close, you should *still* give the highlights of a new upstream version in the ‘debian/changelog’. I'm utterly uninformed by a bare “New upstream release.”; of course it's a new upstream release, I can already see that from the version number. This is a changelog, tell me *what changed* in this new upstream version. I don't see the need for this. For most packages upstream's changelog is installed in /usr/share/doc/$PACKAGE/, which will (hopefully) explain all you need to know. Of course, when you're closing bugs, I agree that there should be more verbosity than New upstream release. Cheers, Ryan -- _ Ryan Niebur ryanrya...@gmail.com signature.asc Description: Digital signature
Re: Documenting new upstream version in ‘debian /changelog’
Ryan Niebur ryanrya...@gmail.com writes: On Tue, Apr 28, 2009 at 11:31:35AM +1000, Ben Finney wrote: I wholeheartedly agree with this, and would go further: even if there are no Debian BTS reports to close, you should *still* give the highlights of a new upstream version in the ‘debian/changelog’. I'm utterly uninformed by a bare “New upstream release.”; of course it's a new upstream release, I can already see that from the version number. This is a changelog, tell me *what changed* in this new upstream version. I don't see the need for this. For most packages upstream's changelog is installed in /usr/share/doc/$PACKAGE/, which will (hopefully) explain all you need to know. The upstream changelog isn't displayed by apt-listchanges, so is much, much less useful. It's also often pretty bad, either including way more details than the average user cares about or including almost nothing. I'm with Ben; I try to summarize major changes for all of my packages that are likely to affect users in the Debian changelog. I don't always manage, but I try. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: gnome-inm-forecast (updated package)
Hi, I am about to leave again, so haven't looked much more, but... On Tue, Apr 28, 2009 at 02:03:58AM +0200, Gustavo Iñiguez Goya wrote: By the technical side, an important bug has been fixed, which caused to not work on GNOME 2.26: https://bugs.launchpad.net/ubuntu/+source/gnome-inm-forecast/+bug/351398 why have you closed this bug in Ubuntu? afaict, it has not yet been fixed in Ubuntu itself. you should reopen that bug, and make your changelog look like this: * New upstream release. - initialize GNOME VFS, fixing this under GNOME 2.26 (LP: #351398) then it will be automatically closed when this package gets uploaded. Thanks, Ryan -- _ Ryan Niebur ryanrya...@gmail.com signature.asc Description: Digital signature
Re: Documenting new upstream version in ‘debian /changelog’
Ryan Niebur ryanrya...@gmail.com writes: Hi, On Tue, Apr 28, 2009 at 11:31:35AM +1000, Ben Finney wrote: I wholeheartedly agree with this, and would go further: even if there are no Debian BTS reports to close, you should *still* give the highlights of a new upstream version in the ‘debian/changelog’. I don't see the need for this. For most packages upstream's changelog is installed in /usr/share/doc/$PACKAGE/, which will (hopefully) explain all you need to know. Not if I'm trying to see what has changed *before* installing the package. With many of the Debian package manager tools (apt-listchanges, aptitude, maybe Synaptic?, even the packages.qa.debian.org site) I can see ‘debian/changelog’ before making the decision to install or not. If all I see there is “New upstream version” I am no wiser as to what new upstream changes will rock my system. -- \ “I went to the cinema, it said ‘Adults: $5.00, Children $2.50’. | `\ So I said ‘Give me two boys and a girl.’” —Steven Wright | _o__) | Ben Finney pgpIzUq56k3sh.pgp Description: PGP signature
