Re: Re: start mysqld from debian/rules?
Hi Ben, Cédric Boutillier cedric.boutill...@gmail.com writes: A best practice instaured in the Ruby Extras Team is to run the test suite at build time to ensure that it will work with the versions of the Ruby interpreter supported by Debian. Where is that documented? I couldn't find it at URL:http://wiki.debian.org/Teams/Ruby/Packaging. That is _very_ briefly mentionned on this page as one item in the description of gem2deb, the packaging tool we are using. gem2deb is a replacement for our current cdbs-based packaging suite. It: [...] * runs the test suite as part of the build, for each ruby implementation (yes, it's possible to override this) There is some more information in dh_ruby(1), in the gem2deb package. Instead, disable the tests which require that, since they are not unit tests and hence are irrelevant to the goal of testing the code against the Ruby interpreter. The package is meant to interact with a mysqld server, so the test suite provided by upstream contains mainly (if not only) tests requiring a working instance of mysqld somewhere. Except running a syntax check, that is the only thing I can do to test automatically if the software works or not with the Ruby interpreters and other Ruby libraries we have in Debian. I must admit that it is very helpful to have some pieces of code to test the software we are packaging, as it is very easy to forget a dependency (most of the time, there is no compilation, so missing libraries are detected at runtime). Cédric signature.asc Description: Digital signature
Re: Re: start mysqld from debian/rules?
Thomas Goirand wrote: On 10/31/2011 08:54 AM, Paul Wise wrote: On Mon, Oct 31, 2011 at 6:04 AM, Cédric Boutillier wrote: I was wondering what would be the best way to start (and possibly stop) the mysql server from the debian/rules makefile. Could anyone help me on this? Run mysqld from debian/rules Hi, We've done that in the libdbi-drivers package. The way to do it is like this: [snip] Thank you very much, Thomas. I managed to reuse parts of your script to have something working almost as expected. There are still a few details to polish, but at least I could get started. Best, Cédric signature.asc Description: Digital signature
Re: Re: start mysqld from debian/rules?
Bonjour Charles, Charles Plessy wrote: Le Sun, Oct 30, 2011 at 11:04:38PM +0100, Cédric Boutillier a écrit : For the test suite to run for this package, an instance of the mysqld server needs to be started. Installing mysql-server-5.1 as a build-dependency does not start the daemon in a pbuilder chroot, because of policy-rc.d Bonjour Cédric, I am also a big fan of regression testing at build time, but indeed, it makes build dependancies more complex. I think that the way to go is to use frameworks like autopkgtest. I hope that in the future, our infrastructure will systematically run such tests on new packages. To help this happen, we need to provide packages that implement auopkgtest tests. How about using it in your case ? http://dep.debian.net/deps/dep8/ That is indeed a great idea. I believe though that it is something that has to be taken care of inside the packaging tool we use, instead of inside every single package. There is a whishlist bug reported against gem2deb (#637917) to integrate gem2deb with DEP-8. So that is something we could adopt in the (near?) future. Cédric signature.asc Description: Digital signature
Re: Overriding .desktop file with localized version (QasMixer)
In the progress of separating localizations for QasMixer into a separate package qasmixer-l10n I've stumbled over the following linitan warning: W: qasmixer-l10n: desktop-command-not-in-package usr/share/applications/qasmixer.desktop qasmixer [..] qasmixer-l10n installs a new version of /usr/share/applications/qasmixer.desktop with additional localized strings and diverts the original file to /usr/share/qasmixer/qasmixer.desktop.no_l10n Why? Why not install the desktop file with the localized strings in with the proper package? And by keeping the localized desktop file in the same package as the application gives also translated entries in the menu, so that it doesn't say Sound Mixer Qasmixer in a danish environment, but rather Lydmikser Qasmixer (I don't know what Qasmixer is or how it is properly capitalized) It's just an artificial name going back to Q - Qt a - ALSA s - Sound Mixer The translations in the desktop file is not for the application, but for the desktop shell or window manager or whatever is providing the menu. That's true. But translated menu entries will also appear once qasmixer-l10n was installed. -- Sebastian -- 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/4eb114b0.8060...@gmx.de
Re: Overriding .desktop file with localized version (QasMixer)
1. It allows to add new translations or update existing ones without having to change/revalidate the (fat) qasmixer package. 2. The l10n package can be used for all architectures. This should save some precious bytes on the package servers. It is possible to use this structure: package qasmixer, depends on: package qasmizer-data The -data package may then contain all stuff that works on all architectures, including all the localized strings in the .desktop file. Of course, you'll get the same lintian warning. Yes, right, the warning would remain. :/ Here's the more details current upstream scenario. qasmixer_X.Y.tar.bz2 - Two number version qasmixer-l10n_X.Y.Z.tar.bz2 - Three number version X and Y always match, but Z grows with every new l10n submit. What I can do is to create either 1. two packages, qasmixer_X.Y and qasmixer-l10n_X.Y.Z - Has the lintian warning issue 2. one package qasmixer_X.Y.Z with both tarballs merged - Most package data would be duplicated with every l10n submit - Binary would be recompiled on every l10n submit I suppose I was being a bit glib. If you have a corner case where the lintian warning can be safely ignored and it is not something that should be fix in lintian, I think you should just override the lintian warning. I see linitian supports warning overrides. http://lintian.debian.org/manual/section-2.4.html Then I'd like to stick with 1 which reflects the upstream situation better. Thanks for the feedback so far! -- Sebastian -- 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/4eb11bcc.5080...@gmx.de
What is the proper way to rename scripts?
Because of Debian Policy Manual section 10.4 (Scripts) I must rename a script. What is the proper way to accomplish this when using dh 7? It seems to me to be a useless waste of time an energy. Somebody will have to maintain this change. Upstream is not going to rename it, they have real problems to deal with. -- Paul Elliott 1(512)837-1096 pelli...@blackpatchpanel.com PMB 181, 11900 Metric Blvd Suite J http://www.free.blackpatchpanel.com/pme/ Austin TX 78758-3117 signature.asc Description: This is a digitally signed message part.
Re: What is the proper way to rename scripts?
Hi! Am 02.11.2011 11:36, schrieb Paul Elliott: Because of Debian Policy Manual section 10.4 (Scripts) I must rename a script. What is the proper way to accomplish this when using dh 7? Use a dh_install_override to install normaly, and rename the file afterwards. It seems to me to be a useless waste of time an energy. Somebody will have to maintain this change. Oh, what a waste of time to add three lines to your rules file, which you'll never have to change again, unless upstream decides to change something... Best regards, Alexander -- 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/4eb12075.6030...@schmehl.info
Re: What is the proper way to rename scripts?
Le Wed, Nov 02, 2011 at 05:36:29AM -0500, Paul Elliott a écrit : Because of Debian Policy Manual section 10.4 (Scripts) I must rename a script. Hi Paul, if the script is not an interface, you can consider leaving its name as it is. Why would foo.pl unacceptable and pyfoo acceptable ? In any case, please pay attention to the risk of becomming incompatible with upstream's documentation, examples, scripts, as well as users scripts if you rename a program. In my work environment using Debian isolates me from my colleagues for this reason… The best solution to the problem is to convince Upstream to rename the file if you think it is worth doing so. Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan -- 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/2002112638.gf20...@merveille.plessy.net
Re: mentors.d.o
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, On 02.11.2011 00:07, Stefano Zacchiroli wrote: On Tue, Nov 01, 2011 at 10:24:54PM +, Iain Lane wrote: In attendance will be myself, Allison Randal and zack. I plan on arguing for the increased use of mentors (debexpo) and the medium-term deprecation of Ubuntu's equivalent, REVU. I'll AOL that and, as far as I've seen, people on the Ubuntu side are interested as well. please note, for the time being mentors can not be used as platform for Ubuntu mentoring. We allow uploads of source packages targeting a Debian distribution only, and we neither support vendor profiles in Lintian and other QA checks. Thus, currently mentors.d.n can be used regarding Ubuntu only insofar as packages entering Debian end up in Ubuntu anyway. I'm not arguing against the idea at all, but it needs some people willing to join our (tiny) development team which are interested to push things forward. We have quite a huge backlog already, but as far as I can say, nobody is actively developing Debexpo (i.e. the software running mentors.d.n) right now due to lack of time or interest. On this specific point, have you discussed the matter with DSA yet? I'd be very useful to know if they have technical objections on adopting the maintenance of the service or not. The company I am working for is sponsoring a well sized virtual machine already. It's (currently) not the hardware which blocks adoption of mentors.d.n to mentors.d.o but just someone who would explore interest and possibilities to make mentors and official service among you, Stefano, and other developers in seek of consensus. If nothing else, we are probably lacking people you could delegate here, as the only people who actively worked on Debexpo / mentors.d.n in the recent past were Asheesh (paulproteus@d.o) and me among a handful of smaller contributors who provided smaller patches, translation fixes, templates and so on (but yet, thanks for that!). - -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJOsT4JAAoJEMcrUe6dgPNtEucQAMqQMUgtsNYBbyGPDp+d8p21 psuYwTEkTMbhhyGd8DZkVawZXqUfZfk1D/zhDuf9k3OM9N5f2XKXAu5pZiNf99mM WmF3ydwZkisCWQ3O93Sz4tj14CKQym2Nb4cIDRHsJBgdkJHGPpf4ZrFQGYAbVuwc mAiTNT4QwTJqm96llEu0dN/t0CmHlQbpD3QnG91XvWsmju2/uZhhGu2B32WOkkAD gPYIP4ABDjwFwFc9MpbIi8eb2UHWsK+08Q9zaBtgX2oYu8pWyYnzQW7ZSqlyykrG bkqw/J9I3P5Tq2OuP1VboJ0bx+1b6P2wAqQ5dweRWkKhXyJy/w/3+zur+JJUGZJN eEAc/tFUS3dmLpghFLVniibduBy9XTJAhRiF4AqVQo80kFSJfMANQQb8wY9sWaTB xpseA4xT+cditmbYAKS1Tk3JkZJ9VKJchj7gE0hYlgej5TH4XQA+ADpgBijK4trg BFZac09JIj6z2W327DTtlTNeTJz3FOeIvJwlVfaRl4IAkvBbGPmw2bgcP3o7R8ht +/DH68YIJEdLOuD/EGmISlKqWHFNrvmrqL54G8IpYVQiMQaIJbXB/0rjgmpXSC/Y EWKQBwRSGNFwFFsZvBC//elqqP2gLmwXcSmsnIyTNVYX2AwH82CT4hwDqUBXriN0 oeyeNaprM57jzETC5vGA =ZqdH -END PGP SIGNATURE- -- 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/4eb13e09.4000...@toell.net
Re: package errors requiring human judgment to detect?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, additionally to what Jakub says you may want to check: * Are package names and descriptions really expressive? * Are sections and priorities in debian/control all good? * Check (build-)dependencies + Are all dependencies declared? In particular: Does the package make use of external commands/includes only insofar they are (build-)essential? + Can they be satisfied in main? + Are they properly versioned if required? * Does the package build cleanly two times in a row * Can the package be upgraded, removed, purged * Does the watch file work (if any) * Does the package ship files where they are expected to be (/var/lib vs. /var/cache; /usr/bin vs. /usr/sbin; etc ...) * Does the package tell apart binary packages in a sane way (if it builds multiple packages out of a single source package) * Does the package make use of embedded code copies (Lintian does not detect all of them) ... and probably much more I forgot right now. But please keep posting, I'll add this list to http://mentors.debian.net/intro-reviewers in future. - -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJOsUFPAAoJEMcrUe6dgPNt4KwQALRa1Q8HxxWKhlzBSwqPlirL aE3QgPor6n6hBouzCzs6p/+JrAFqdt2zQH1P8JVR/CrMyuU0jf3gwxqrXlJnpMPV OsR1riYaPLLS6MnHVWe7/hv53WrD2e5b81tMgdo5Xc5XOnEmGbneGZtdPsNDNbyv ElNlyin3HzrYFrGRI+pgxFhQV1VSqDB6lzr6W9jqDqbveXJRl+c+M2EbcOLHXnH3 wRsvUCp2xS4iYQe6FT3NEcESweJw0M42/gTZjF+kV/+YHNthU7Yt0teAEqEJUtfe 45z1gP/O8tb3OTvYftt3P6Gc8L62P0TJejrwW3EEqeVM8qmhARd0hYuUrN86BOsB R7sesgWaaVYK37KN6v1ZEDBNLJ1m11WjORw4IOTpOFwZeCMqWoxpuhaEVKAQjOQL z/wFILFxRpyXi05LCwVgySzbCyURCGHxaelBEnn5ykfRrpH6c+Hxba/WreEM4G8l h04twLIcFXqiUytBBSWnma0cMPhdfnEMTu2cPBHHNdx6yprskyH8lhuh2Z04gBCk b6sxOUHAwg4OV9950l7Q4lKazErOSpJkty3FCluQDFVkHI8LwQymw5tO4iLoN2iL 0BlNjH1X3cQO8xT+pTcNRG6CtHPv4RJ0sLFd5Fr2Zp0AxWKy28yhLLbdX+crHo5m loYJb6FZu6HKxlA0Mz2z =LBss -END PGP SIGNATURE- -- 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/4eb1414f.50...@toell.net
Re: package errors requiring human judgment to detect?
Hi! Am 01.11.2011 19:07, schrieb Jakub Wilk: - debian/copyright is incomplete or inadequate. FWIW: That's by far the most common reason for a Reject from the NEW queue. Best regards, Alexander, who by incident didn't had to reject a package today ;) -- 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/4eb14356.20...@debian.org
Re: mentors.d.o
On Wed, Nov 2, 2011 at 8:56 AM, Arno Töll deb...@toell.net wrote: On 02.11.2011 00:07, Stefano Zacchiroli wrote: On Tue, Nov 01, 2011 at 10:24:54PM +, Iain Lane wrote: In attendance will be myself, Allison Randal and zack. I plan on arguing for the increased use of mentors (debexpo) and the medium-term deprecation of Ubuntu's equivalent, REVU. Thus, currently mentors.d.n can be used regarding Ubuntu only insofar as packages entering Debian end up in Ubuntu anyway. That is in fact the goal, AFAIKT. -- Andrew Starr-Bochicchio Ubuntu Developer https://launchpad.net/~andrewsomething Debian Maintainer http://qa.debian.org/developer.php?login=a.starr.b%40gmail.com PGP/GPG Key ID: D53FDCB1 -- 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/CAL6k_Azvq3_ry1-_q=ifoihoinesyc9_ttakcsyr13pximz...@mail.gmail.com
Re: package errors requiring human judgment to detect?
On Wed, Nov 02, 2011 at 02:10:39PM +0100, Arno Töll wrote: * Check (build-)dependencies + Are all dependencies declared? In particular: Does the package make use of external commands/includes only insofar they are (build-)essential? + Can they be satisfied in main? + Are they properly versioned if required? * Does the package build cleanly two times in a row That can be automatically tested but requires more than a text analyzer. * Can the package be upgraded, removed, purged I think there is a tool for it. * Does the watch file work (if any) This requires network access but can be tested automatically, isn't it? -- WBR, wRAR signature.asc Description: Digital signature
Re: package errors requiring human judgment to detect?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Andrey, On 02.11.2011 15:02, Andrey Rahmatullin wrote: * Does the watch file work (if any) This requires network access but can be tested automatically, isn't it? Yes, it can. We do so at Debexpo. However, the question originally was what /Lintian/ can't (as static analysis tool). Piuparts can do some of the things I mentioned though. - -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJOsU6SAAoJEMcrUe6dgPNtqKEQANWGs3OcDUdepPd3lxD2DcaW XlFwQua+YMKbo47h3TCnrbl1X5buAlkDFj9kgkyeofHQns5ZyZqUKfZgiBVfVoc9 h6+kBaJQNuIgXSEohhdS3gRlj+qwMbhmVNJxpoBTftbpKbJGdl67MhWdl46+K2TB kijgAB76jcw2fv/KqH2fesGhBdXm8kSKSoczvkfeCjYgE5A1WIta89UaGi75XiZs bL0mwmlDp3enEURj5bBsOhA07AFuxn18s1nN9lLUmlZe6N3Ewo3jIv3+H/ws0jeJ h+704gxfHA8vUnYx/yZfoL8G7Lmn/+KymZC1Ns9vej0V43YdhK00y9DaD3P95jIa 57Da8FRKjcLjZavA/mjGAzgqyTYDiBznl+sdoi9nlSWVUSIAHjsQe/7Se/gZ1ma8 /FTxmV9u9E/pE4xKkoa4m2PyuZdPNj+QbvWgQhMfbjLH6r58oq2p263PoiEw3TbA 4bxHkEIp5p9CVwoQmUcTxzgA76J6JYQaaEf0Q00OOLBxtDWHG1KhDjeouLc14cap l0P2HZBXg9+gp4v8nmPecnxsGQCZVNcLrMl6Jisga5rwg0tqDzXRSQTp/4hXk79W obGyGno0P629xtUs+gdU25Ai2KHENjNaRbz2u2VjPizXu5npfZ8XhWiNs1c9kGPA tIuFW+Jhp43Kwg2chn1P =XUkg -END PGP SIGNATURE- -- 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/4eb14e93.60...@toell.net
Re: package errors requiring human judgment to detect?
Le mercredi 2 novembre 2011 15:02:13, Andrey Rahmatullin a écrit : On Wed, Nov 02, 2011 at 02:10:39PM +0100, Arno Töll wrote: * Check (build-)dependencies + Are all dependencies declared? In particular: Does the package make use of external commands/includes only insofar they are (build-)essential? + Can they be satisfied in main? + Are they properly versioned if required? * Does the package build cleanly two times in a row That can be automatically tested but requires more than a text analyzer. * Can the package be upgraded, removed, purged piuparts. I think there is a tool for it. * Does the watch file work (if any) This requires network access but can be tested automatically, isn't it? Indeed, since the PTS can report such failure. Thomas Preud'homme signature.asc Description: This is a digitally signed message part.
RFS: couriergrey
Dear mentors, I am looking for a sponsor for my package couriergrey. * Package name: couriergrey Version : 0.2.2-1 Upstream Author : Matthias Wimmer m...@tthias.eu * URL : http://couriergrey.com * License : GPL-3 Section : net It builds those binary packages: couriergrey - Mail filter interface of Courier-MTA to support greylisting To access further information about this package, please visit the following URL: http://mentors.debian.net/package/couriergrey Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/c/couriergrey/couriergrey_0.2.2-1.dsc I would be glad if someone uploaded this package for me. Kind regards, Marco Balmer signature.asc Description: GnuPG Signature
Re: RFS: shedskin
* Paul Boddie p...@boddie.org.uk, 2011-11-02, 01:12: I suppose that the following is asking a bit much... Files: shedskin/lib/(itertools|heapq).?pp ...but surely the following should be OK: Files: shedskin/lib/itertools.?pp shedskin/lib/heapq.?pp That's right. You probably want to add a paragraph about files in debian/ directory to the copyright file. OK, but I did have a comment like this... Comment: This package was debianized by Paul Boddie p...@boddie.org.uk. Comments are... well, comments. Copyright files in DEP-5 format are supposed to be machine-interpretable, and according to yours, the debian/ directory is Copyright 2005-2010 Mark Dufour. Note that older versions of DEP-5 were explicit about how (past) maintainership should be documented: http://anonscm.debian.org/viewvc/dep/web/deps/dep5.mdwn?r1=166r2=173 -- Jakub Wilk -- 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/2002155204.ga1...@jwilk.net
Re: What is the proper way to rename scripts?
On Wednesday, November 02, 2011 05:50:29 AM Alexander Reichle-Schmehl wrote: Hi! Am 02.11.2011 11:36, schrieb Paul Elliott: Because of Debian Policy Manual section 10.4 (Scripts) I must rename a script. What is the proper way to accomplish this when using dh 7? Use a dh_install_override to install normaly, and rename the file afterwards. I have put in a patch to change all references to this script. This includes references in the build procedure. Therefore, the renaming must take place before any part of the build procedure runs. Just like it always had the new name. What is the canonical way to do this? Thank You. I can not change references outside the package, like references in web pages referring to the software, emails people have sent to each other telling them how to use it, and so-forth, therefore the change is sure to cause problems. But this is an objection that applies to many programs. People should really reconsider this policy. -- Paul Elliott 1(512)837-1096 pelli...@blackpatchpanel.com PMB 181, 11900 Metric Blvd Suite J http://www.free.blackpatchpanel.com/pme/ Austin TX 78758-3117 signature.asc Description: This is a digitally signed message part.
Re: What is the proper way to rename scripts?
2011/11/2 Paul Elliott pelli...@blackpatchpanel.com: I have put in a patch to change all references to this script. This includes references in the build procedure. Therefore, the renaming must take place before any part of the build procedure runs. Just like it always had the new name. What is the canonical way to do this? Thank You. Whenever I've encountered this situation I just change all references after the build procedure, invoking sed from debian/rules (I find this much cleaner than using patches, since it doesn't require any changes if the files change, etc., you just have to be cautious that the clean rule reverts the changes correctly). -- Siegfried-Angel Gevatter Pujals (RainCT) Free Software Developer -- 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/CALF0CpDmD=L7=svzDQFXvFx=wY41fFFh3=Mm994Q7m8Fpyzc=g...@mail.gmail.com
Re: RFS: cxxtest - xUnit-like framework for C/C++ applications
Hi Michael, Il 01/11/2011 20:18, Michael Tautschnig ha scritto: I've looked at your package and would be interested in sponsoring it's upload. Great! - None of the source files contains license or copyright information. Yet even the included COPYING file highly suggests that: [...] Do you think you could convince upstream to get that fixed really soon? I can try. I'll write immediately to the authors. - Those packages: cxxtest-gui-qt4 cxxtest-gui-x11 seem to be almost empty, and I can't see why they actually ship a GUI - isn't it just a single header file each? (Plus suitable dependencies, of course, but adding them as Suggests to the main package doesn't feel too wrong.) The headers contained in cxxtest-gui, cxxtest-gui-qt4 and cxxtest-gui-x11 can be used to create GUIs for each test suite. Probably the appended -gui can be misleading because users could suppose that they contain a GUI for cxxtest, but I couldn't find a better name. Any suggestion? I decided to create those packages because the contained headers require huge packages (i.e. libqt-dev) but they are not necessary to create test-suites. I have used those headers only during deb package creation to test them, but never actually used for testing. So I supposed that allowing users to install them separately was better in order to save space if they do not need to create a GUI. Besides that, a watch file would be nice. Just take a look at subversion's watch file to figure out how to handle tigris.org. I didn't create the watch file because the link to the upstream source is strange: http://cxxtest.tigris.org/files/documents/6421/43281/cxxtest-3.10.1.tar.gz and those numbers could change with the new releases. In addition none of the URLs - http://cxxtest.tigris.org/files/ - http://cxxtest.tigris.org/files/documents/ - http://cxxtest.tigris.org/files/documents/6421/ - http://cxxtest.tigris.org/files/documents/6421/43281/ are browsable and I couldn't create a watch file. I don't think a watch file with http://cxxtest.tigris.org/files/documents/\d+/\d+/cxxtest-([\d\.]+)\.tar\.gz will work. Am I wrong? Thanks, bye Simone signature.asc Description: OpenPGP digital signature
Re: RFS: cxxtest - xUnit-like framework for C/C++ applications
Hi Simone, [...] The headers contained in cxxtest-gui, cxxtest-gui-qt4 and cxxtest-gui-x11 can be used to create GUIs for each test suite. Probably the appended -gui can be misleading because users could suppose that they contain a GUI for cxxtest, but I couldn't find a better name. Any suggestion? Maybe really just remove the -gui in the package name and fix the description? [...] Besides that, a watch file would be nice. Just take a look at subversion's watch file to figure out how to handle tigris.org. I didn't create the watch file because the link to the upstream source is strange: http://cxxtest.tigris.org/files/documents/6421/43281/cxxtest-3.10.1.tar.gz and those numbers could change with the new releases. In addition none of the URLs - http://cxxtest.tigris.org/files/ - http://cxxtest.tigris.org/files/documents/ - http://cxxtest.tigris.org/files/documents/6421/ - http://cxxtest.tigris.org/files/documents/6421/43281/ are browsable and I couldn't create a watch file. I don't think a watch file with http://cxxtest.tigris.org/files/documents/\d+/\d+/cxxtest-([\d\.]+)\.tar\.gz will work. Am I wrong? Following the subversion example, this should work: version=3 http://cxxtest.tigris.org/servlets/ProjectDocumentList?folderID=9766expandFolder=9766 \ http://cxxtest.tigris.org/files/documents/\d+/\d+/cxxtest-([\d\.]+)\.tar\.gz But ok, that might depend on whether upstream retains 9766 as a good folderID (note that subversion has a folder Source Code to provide all the releases instead of creating one folder per release). Might require more discussion with upstream. Best, Michael pgp6qOvQNGK9k.pgp Description: PGP signature
Re: What is the proper way to rename scripts?
On Wednesday, November 02, 2011 12:26:21 PM Siegfried-Angel Gevatter Pujals (RainCT) wrote: 2011/11/2 Paul Elliott pelli...@blackpatchpanel.com: I have put in a patch to change all references to this script. This includes references in the build procedure. Therefore, the renaming must take place before any part of the build procedure runs. Just like it always had the new name. What is the canonical way to do this? Thank You. Whenever I've encountered this situation I just change all references after the build procedure, invoking sed from debian/rules (I find this much cleaner than using patches, since it doesn't require any changes if the files change, etc., you just have to be cautious that the clean rule reverts the changes correctly). That will not work. The build procedure, (the part comming from upstream), has been changed to use the new name. I do not care to figure out which references to the script are in the build procedure and which need to exist at runtime. There may be some references to the script that are used by both. The rename really needs to happen before build or installation. Is there an dh override that is commonly used to hook in before the build procedure runs? -- Paul Elliott 1(512)837-1096 pelli...@blackpatchpanel.com PMB 181, 11900 Metric Blvd Suite J http://www.free.blackpatchpanel.com/pme/ Austin TX 78758-3117 signature.asc Description: This is a digitally signed message part.
Re: What is the proper way to rename scripts?
2011/11/2 Paul Elliott pelli...@blackpatchpanel.com: Is there an dh override that is commonly used to hook in before the build procedure runs? Sure, override dh_auto_build. -- Siegfried-Angel Gevatter Pujals (RainCT) Free Software Developer -- 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/calf0cpa7-qmgsauuztajsorwn8rvpr6p8nphyoz2ckxbc4s...@mail.gmail.com
RFS: procmeter3
Dear mentors, I am looking for a sponsor for my package procmeter3. * Package name: procmeter3 Version : 3.5d-1 Upstream Author : Andrew M. Bishop a...@gedanken.demon.co.uk [Please put procmeter in the subject line] * URL : http://www.gedanken.demon.co.uk/procmeter3/ * License : GPL2+ Section : utils It builds those binary packages: procmeter3 - graphical system status monitor To access further information about this package, please visit the following URL: http://mentors.debian.net/package/procmeter3 Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/p/procmeter3/procmeter3_3.5d-1.dsc I would be glad if someone uploaded this package for me. The package is lintian clean and is a new upstreamer release. Kind regards, Wences Arana -- Wences Arana nacido para ser libre Debian FTW 9455 B304 491E 1165 43C8 1B34 8678 4112 D3AC 9B13 -- 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/CAF=1_yxkTz=eokw-tcqgaghyhh5zf1dxhixz-y5hteek5tu...@mail.gmail.com
Re: RFS: blogofile
Am Mon, 31 Oct 2011 22:44:55 -0400 schrieb Andrew Starr-Bochicchio a.star...@gmail.com: [...] I'm not a DD, so I can't actually sponsor this. It sounds like an interesting package, so I did a quick review. [...] It took me awhile to figure it out, but it seems you have a one character typo. Your rules file has: [...] It should be: %: dh $@ --buildsystem=python_distutils --with python2 Notice, no hyphen between with and python. Thank you very much for reviewing my package and especially for discovering this hard to find typo. I fixed this and also some other points: - remove --buildsystem=python_distutils from dh options. Seems to make no difference because debhelper recognise by himself that python_distutils should be used - Fixing Depends fields in debian/control. After fixing the typo in the dh options, debhelper identifies the right python dependencies. This should also resolve the lintian warning you got. - Adding a debian/pydist-overrides file - Adding also a no-upstream-changelog lintian override for blogofile-converters I would be glad if you (or anybody else) will review my new version which I uploaded a few minutes ago to mentors.d.n. It should be available through: dget -x http://mentors.debian.net/debian/pool/main/b/blogofile/blogofile_0.7.1-1.dsc Kind regards, Andreas -- Andreas Rütten mailto : andreasruet...@gmx.de PGP, 6C9DFFB2, 8394 99DA 59BD BCE2 3FC8 3A9E 6633 0089 6C9D FFB2 -- signature.asc Description: PGP signature
Re: RFS: blogofile
* Andreas Rütten andreasruet...@gmx.de, 2011-11-02, 22:44: - Adding a debian/pydist-overrides file According to dh_python2 author, you should not do that (unless it's necessary): 10:23 POX please use pydist-overrides only if dh_python2 guesses incorrectly -- Jakub Wilk -- 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/2002220255.ga2...@jwilk.net
Re: RFS: procmeter3
2011/11/2 Wences René Arana Fuentes ara...@debian.org.gt: Dear mentors, I am looking for a sponsor for my package procmeter3. snip... To access further information about this package, please visit the following URL: http://mentors.debian.net/package/procmeter3 This is by no means a full review, just something I noticed. Also, I am not a DD so I can't upload the package. That above page lists your package's Vcs-Browser as: http://anonscm.debian.org/git/collab-maint/procmeter3.git That isn't a particularly useful link. This might be more appropriate for that field: http://anonscm.debian.org/gitweb/?p=collab-maint/procmeter3.git Thanks, -- Andrew Starr-Bochicchio Ubuntu Developer https://launchpad.net/~andrewsomething Debian Maintainer http://qa.debian.org/developer.php?login=a.starr.b%40gmail.com PGP/GPG Key ID: D53FDCB1 -- 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/CAL6k_AxN+Nr_0qodih=Wa8WsX=jr-97o7zuh2da83huyywr...@mail.gmail.com
