Re: RFS: stx-btree (updated package)
On Thursday 19 May 2011 16:54:15 Ury Stankevich wrote: On Wed, May 18, 2011 at 7:42 PM, George Danchev danc...@spnet.net wrote: As a start your debian/changelog does not mention that a patch was dropped since it has been applied upstream. It is not a big deal in that particular case, but changelog entries are meant to be read by a much broader audience, than sponsoree and sponsor set. So, yes, expected behavior is to document every single change, since users draw conclusions we can hardly predict upon a release. Hi, Hi, i had uploaded an updated version. (add changelog entry about merged patch, restored patch for configure ) Package looks good, though I'd like to: 1) drop quilt from Build-Depends. 2) finally use upstream's bz2 tarball, instead of me diffing your orig.tar.gz against it to be sure nothing has been changed by accident. See, FAQ #2 and #5 at: http://wiki.debian.org/Projects/DebSrc3.0 Fine with you? ps: please, CC'me on reply. CC'ed. -- pub 4096R/0E4BD0AB people.fccf.net/danchev/key pgp.mit.edu -- 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/201105210929.32369.danc...@spnet.net
Re: RFS: mpd-sima (updated package)
EfriM, 2011-05-20 21:53 UTC+0200: Le 19/05/2011 22:45, Tanguy Ortolo a écrit : debian/clean What is that? I have never seen such a file, is it for a dh command I do not know yet? I may be interested for my own packages. :-) As answered before, this is dh_clean. I like it when I can keep debian/rules minimal. Anyway, debhelper rocks, kudos to Joey! Thank you for the information. I personally perfer to keep the clean logic for a file in debian/rules if its build logic is also there, so that nobody wonders why there is no cleaning for this file. debian/mpd-sima.postinst Do you have a reason to dpkg-statoverride files instead of installing them with these perms in the package itself? To install files with non-standard perms in dokuwiki, here is what I do in debian/rules: DESTDIR=$(CURDIR)/debian/dokuwiki override_dh_fixperms: dh_fixperms chown -R www-data.root $(DESTDIR)/var/lib/dokuwiki/data chmod 700 $(DESTDIR)/var/lib/dokuwiki/data I cannot use dh_fixperms because I need to set ownership to a non-standard system user (named mpd-sima) which might be created when the package is installed, hence the use of dpkg-statoverride. This should be documented in a comment, so that people like me will not ask next time. :-) -- ,--. : /` ) Tanguy Ortolo xmpp:tan...@ortolo.eu irc://irc.oftc.net/Elessar | `-'Debian Maintainer \_ signature.asc Description: Digital signature
RFS: lfm (updated package) (New Upstream release)
Dear mentors, I am looking for a sponsor for the new version 2.3-1 of my package lfm. It builds these binary packages: lfm- simple but powerful file manager for the UNIX console The package appears to be lintian clean. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/l/lfm - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/l/lfm/lfm_2.3-1.dsc I would be glad if someone uploaded this package for me. Kind regards Daniel Echeverry -- Epsilon http://www.rinconinformatico.net http://www.fitnessdeportes.com http://www.dragonjar.org Linux user: #477840 Debian user
Menu question: Sound Application
Dear Mentors I am packaging jampal. This is a sound related application for organizing mp3 files. It should go in the appropriate menu. According to the menu standards ( http://www.debian.org/doc/packaging-manuals/menu-policy/ch2.html ) the approved menu is Applications/Sound Sound players, editors, and rippers/recorders. Examples: beep-media-player, grip, audacity However, I have downloaded and installed the latest version of Debian, and there is no Applications/Sound menu but there is Applications/Sound Video containing the sound players editors and recorders. If I use Applications/Sound Video it is against the policy and lintian also complains that it is against the policy. Am I missing something here? If I use Applications/Sound according to standards and lintian the menu structure will be wrong I think, since it is not set up that way in Debian. Thanks Peter -- 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/4dd7f86a.1000...@comcast.net
Re: python-llfuse
Hi Jakub, Thanks for your feedback. A couple of questions: Jakub Wilk jw...@debian.org writes: Please use more useful subjects next time. TIA. * Nikolaus Rath nikol...@rath.org, 2011-05-20, 15:37: * URL : http://code.google.com/p/python-llfuse/ [...] The package appears to be lintian clean. If you use --display-info, you'll get: I: python-llfuse source: duplicate-short-description python-llfuse I'm quite confident that lintian 2.5 complains about binary packages too (though I didn't build them yet). Where is the source for src/llfuse.c? In src/llfuse.pyx and src/*.pxi. The latter were actually missing from the tarball, thanks for the pointer. Please rebuild documentation and src/llfuse.c from sources (once we have it for the latter). The documentation build requires an unreleased development version of Sphinx. What's the proper way to handle this? Is there some rationale for rebuilding documentation and llfuse.c when building the package? I (as upstream) am shipping llfuse.c in the release tarball, so that there is no build dependency on Cython, and that I can be sure that the generated file is actually working. You have both debian/pyversions and XS-Python-Version field. Please use either one or the other, not both. Any suggestions which one to keep? Dependency on python-distribute | python-setuptools is a bit pointless, since python-distribute is a virtual package provided by python-setuptools. You could just write python-distribute or python-setuptools. What is Conflicts: s3ql (= 0.28) for? Both of these are remnants from packaging for an Ubuntu PPA. I'll make sure to remove them. Thanks, -Nikolaus -- »Time flies like an arrow, fruit flies like a Banana.« PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C -- 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/874o4oc5ih@vostro.rath.org
Re: override_dh_auto_configure not called
* Scott Howard showard...@gmail.com, 2011-05-05, 12:17: from the dh manpage: Finally, remember that you are not limited to using override targets in the rules file when using dh. You can also explicitly define any of the regular rules file targets when it makes sense to do so. A common reason to do this is if your package needs different build-arch and build-indep targets. For example, a package with a long document build process can put it in build-indep to avoid build daemons redundantly building the documentation. #!/usr/bin/make -f %: dh $@ build: build-arch build-indep ; build-indep: $(MAKE) docs build-arch: $(MAKE) bins Unfortunately, this example is incorrect: http://bugs.debian.org/627534 -- 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/20110521182254.ga7...@jwilk.net
Re: python-llfuse
Nikolaus Rath nikol...@rath.org writes: You have both debian/pyversions and XS-Python-Version field. Please use either one or the other, not both. Any suggestions which one to keep? Sorry, obvious after reading the Python policy again. I removed the pyversions file and changed control to read: X-Python-Version: = 2.6 X-Python3-Version: = 3.0 What is Conflicts: s3ql (= 0.28) for? Both of these are remnants from packaging for an Ubuntu PPA. I'll make sure to remove them. On second thought, do I really need to remove them? I have been providing llfuse and s3ql .debs for a while, both on Ubuntu PPAs and by direct download. Before version 0.28, llfuse was part of the S3QL package, thus the conflict. I think conflicting may avoid problems for some people that used these old .debs. Best, -Nikolaus -- »Time flies like an arrow, fruit flies like a Banana.« PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C -- 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/871uzrdids@vostro.rath.org
Re: python-llfuse
* Nikolaus Rath nikol...@rath.org, 2011-05-21, 14:21: You have both debian/pyversions and XS-Python-Version field. Please use either one or the other, not both. Any suggestions which one to keep? Sorry, obvious after reading the Python policy again. I removed the pyversions file and changed control to read: X-Python-Version: = 2.6 Except that Python Policy (as usual...) doesn't match reality and python-support doesn't read X-Python-Version. X-Python3-Version: = 3.0 You don't seem to be building extension for Python 3... What is Conflicts: s3ql (= 0.28) for? Both of these are remnants from packaging for an Ubuntu PPA. I'll make sure to remove them. On second thought, do I really need to remove them? I have been providing llfuse and s3ql .debs for a while, both on Ubuntu PPAs and by direct download. Before version 0.28, llfuse was part of the S3QL package, thus the conflict. I think conflicting may avoid problems for some people that used these old .debs. Sound like a use case for Breaks+Replaces, not Conflicts. See Debian Policy 7.6.1 for details. Anyway, it's probably good idea to document purpose of such non-obvious parts of packaging in debian/changelog, even if it's first upload to Debian. -- 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/20110521185350.ga...@jwilk.net
Re: python-llfuse
* Nikolaus Rath nikol...@rath.org, 2011-05-21, 13:44: Where is the source for src/llfuse.c? In src/llfuse.pyx and src/*.pxi. The latter were actually missing from the tarball, thanks for the pointer. Please rebuild documentation and src/llfuse.c from sources (once we have it for the latter). The documentation build requires an unreleased development version of Sphinx. What's the proper way to handle this? Is there some rationale for rebuilding documentation and llfuse.c when building the package? Please see: http://lists.debian.org/debian-devel/2010/08/msg00095.html I (as upstream) am shipping llfuse.c in the release tarball, so that there is no build dependency on Cython, You are free to continue to do so, though IMO it doesn't make much more sense than shipping e.g. precompiled ELFs, so that there's no dependency on C compiler... and that I can be sure that the generated file is actually working. Then please write a test suite, so that it can be run at build time. You have both debian/pyversions and XS-Python-Version field. Please use either one or the other, not both. Any suggestions which one to keep? I'd keep the latter. -- 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/20110521191630.ga3...@jwilk.net
Re: python-llfuse
* Nikolaus Rath nikol...@rath.org, 2011-05-21, 13:44: The documentation build requires an unreleased development version of Sphinx. What's the proper way to handle this? Please file a bug against python-sphinx asking to backport the features that are needed by your package. -- 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/20110521193145.ga4...@jwilk.net
Re: python-llfuse
Jakub Wilk jw...@debian.org writes: and that I can be sure that the generated file is actually working. Then please write a test suite, so that it can be run at build time. There is a test suite, but it requires mounting a (FUSE) file system, which breaks at least on the Ubuntu build servers. Can the debian build daemons handle that? Thanks, -Nikolaus -- »Time flies like an arrow, fruit flies like a Banana.« PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C -- 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/87boyvwzeh@vostro.rath.org
Re: Menu question: Sound Application
Le Sat, May 21, 2011 at 01:37:46PM -0400, Peter Bennett a écrit : However, I have downloaded and installed the latest version of Debian, and there is no Applications/Sound menu but there is Applications/Sound Video containing the sound players editors and recorders. Dear Peter, I think that you are looking at the GNOME menu, that is defined by FreeDesktop files. You can enable the Debian menu within it, by clicking the right button and following the relevant options. You can see the differences between the two systems at the following page: http://wiki.debian.org/Proposals/DebianMenuUsingDesktopEntries 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/20110521234453.ga1...@merveille.plessy.net
Re: python-llfuse
On Sat, May 21, 2011 at 04:51:18PM -0400, Nikolaus Rath wrote: Jakub Wilk jw...@debian.org writes: and that I can be sure that the generated file is actually working. Then please write a test suite, so that it can be run at build time. There is a test suite, but it requires mounting a (FUSE) file system, which breaks at least on the Ubuntu build servers. Can the debian build daemons handle that? You'd need real root not fakeroot, and even that is not enough in vserver or lxc. -- 1KB // Microsoft corollary to Hanlon's razor: // Never attribute to stupidity what can be // adequately explained by malice. -- 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/20110522003120.ga15...@angband.pl
Re: New Backup Application
On Fri, May 20, 2011 at 10:47:34AM +1200, Paul Reddy wrote: I've built a reasonably comprehensive backup and disaster recovery app, and am looking for some help on the next steps, the first of which I believe is to find a mentor/sponsor from this group. Hello Paul, This does sound interesting but you probably should of put up a website or some more information about the program. Have you found someone to sponsor you yet? - Craig -- Craig Small VK2XLZhttp://www.enc.com.au/ csmall at : enc.com.au Debian GNU/Linux http://www.debian.org/ csmall at : debian.org GPG fingerprint: 1C1B D893 1418 2AF4 45EE 95CB C76C E5AC 12CA DFA5 -- 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/20110522014333.ga23...@enc.com.au
Re: Menu question: Sound Application
Charles answered your question, but I would like to point out that with GNOME 3, hierarchical menus have been removed in favour of a list of apps, a search box and a list of categories. Clicking the categories or typing in the search box filters the list of apps. If you install menu/menu-xdg with GNOME 3 you simply get your program in the list with an ugly icon (due to the scaling up of a small icon). If your app also supports the FreeDesktop menu standards then you get two icons for your app in the menu, one nice (if it is high res) and one ugly (XPM from the Debian menu). As a result GNOME upstream has been recommending that people remove menu/menu-xdg when running GNOME on Debian. I'm not sure if GNOME 3 will be the default for the release of wheezy but as a result it is important that any package with a Debian menu file also have a FreeDesktop menu file, at least until the day that all window managers and desktops in Debian support the FreeDesktop menu. -- 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 Archive: http://lists.debian.org/BANLkTi=mg91q+g2l-eggr45hss7na9m...@mail.gmail.com
