Re: [UDD] Packages flagged 'error' in DEHS import
Andreas Tille wrote: Hi, I was wondering, why DEHS claims ncbi-tools6 as not 'uptodate' but rather 'error'. The DEHS page[1] says for experimental [...] I'm actually running into an error. What I really do not understand is, that the package in unstable has the very same watch file and does not seem to produce an error because it correctly detects outdated and is linking to the new version. Any reasonable explanation for this? Experimental: Last time checked: 2011-01-04 18:07:05 Unstable: Last time checked: 2011-01-04 18:07:24 Something must have went wrong between the two checks. -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- 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/ih8f3q$v9c$3...@dough.gmane.org
Re: [php-maint] RFS: php-gearman
On Monday 02 August 2010 13:39:25 Clint Byrum wrote: Dear mentors and Debian PHP Maintainers, I am looking for a sponsor for my package php-gearman. * Package name: php-gearman Version : 0.7.0-1 Upstream Author : James Luedke cont...@jamesluedke.com * URL : http://pecl.php.net/package/gearman * License : PHP v3.01 Section : php It builds these binary packages: php5-gearman - PHP wrapper to libgearman The package appears to be lintian clean. The upload would fix these bugs: 573894 Do you realise that the bug says that it is an Intent To Package and that I submitted the report and I own it (in terms of the BTS?) I think that asking people to _read_ what the pages and documents say is not asking too much. The package has been ready even before I filed the report but it is waiting for upstream to change the licence. I haven't heard from him since he said he would discuss with the PECL community if it was okay to do it, in spite of my other attempts to contact him. Regards, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- 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/201008021528.01964.geiss...@debian.org
Re: RFS: phpunit (updated package)
Hi, Ivan Borzenkov wrote: The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/phpunit - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/phpunit/phpunit_3.4.15-1.dsc I would be glad if someone uploaded this package for me. Have you contacted your previous sponsor already? maybe he is willing to continue working with you. Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- 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/4c5329ab.8b18e60a.6e9b.4...@mx.google.com
Re: RFS: php-simpletest
nikro...@gmail.com wrote: http://mentors.debian.net/debian/pool/main/p/php-simpletest/php- simpletest_1.0.1-1.dsc debian/changelog: * You made more changes other than adopting the package, document them. debian/control: * do you have a vcs already? * the dependency is incorrect: php4 no longer exists, and php5 only ensures one of the web SAPIs is installed, but the package can also be used wih php5-cli. debian/dirs: * you most likely don't need to list the usr/share/doc directory debian/source/format: * any special reason why you don't use 3.0? Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- 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/4c533c95.5f83e60a.60f0.5...@mx.google.com
Re: Help for watch file
David Paleino wrote: On Fri, 9 Jul 2010 16:02:13 +0800, Paul Wise wrote: On Fri, Jul 9, 2010 at 3:58 PM, Andreas Tille andr...@an3as.eu wrote: I wonder how I might get a watch file for code.google.com working. Sounds like Google changed their HTML again, which broke the redirector too: http://googlecode.debian.net/p/freemedform/ Please do not continue spreading the use of that redirector. Just because there's one for sourceforge it doesn't mean it is okay to have one for other hosting services. We ideally want *none*. Also, I never saw a reply to Iustin Pop's email (basically saying nobody had actually contacted google code.) Neither a +1 or something to the ticket[1] opened by somebody else. [1] http://code.google.com/p/support/issues/detail?id=4042 I would've had tons of emails from angry users asking why it didn't work, if the redirector was actually broken :) 16 packages use it, there should be none. Regards, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- 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/i1ijfc$k0...@dough.gmane.org
Packages with DMUA but no DM (was: Re: RFS: mpg321 (updated package with AudioScrobbler support))
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paul Wise wrote: On Sat, Jun 26, 2010 at 8:42 AM, Nanakos Chrysostomos nana...@wired-net.gr wrote: I am looking for a sponsor for the new version 0.2.11-4 of my package mpg321. According to the PTS the package has DMUA set on it, so you should be able to build and upload it yourself. Except that Nanakos isn't a DM according to [1] and [2], which makes me wonder why Michal sponsored an upload that sets the field. Not to mention that some bugs were closed in the changelog when they should have been closed by manually sending a message to the report explaining why it is not a bug. Examples: * Tried to reproduce the same experiment as Bug #388587 and i don't see any problem. If someone else can simulate the same problem, please report the bug and the way to simulate it again.So i am closing thsi bug also. (Closes: Bug#388587) * Anyone who wants to use the -a option can follow the information from the manpage. To give an example: mpg321 -a /dev/dsp song.mp3. So Bug #286176 should close.The -a option seems to work fine. (Closes: Bug#286176). I wonder if there should be a list of packages with DMUA but no DM Uploader[s] or Maintainer. [1]https://nm.debian.org/dm_list.html [2]http://bugs.debian.org/cgi-bin/pkgreport.cgi?archive=both;package=debian- maintainers -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkwmu0YACgkQYy49rUbZzlrWAwCfZZMeB1aBdt1jauTDj4YXqa0j FuIAn0TlAwL39bTW4Tpoxfx2ktRVhKwh =oy+V -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/4c26bb53.5770e70a.1d64.4...@mx.google.com
Re: RFS: fritzing
Paul Wise wrote: Please don't use HTML email on Debian lists: A text/plain version of the message was included, so it's not a case I would jump on. It's just a matter of disabling HTML emails (on both ends: writer and reader.) Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- 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/i06khk$4j...@dough.gmane.org
Re: RFS: checksec
Hi Michael, Michael Gilbert wrote: It builds these binary packages: checksec - A script that reveals standard security features currently in use [...] This script is provides useful information about which security features have been compiled in There's a similar script already in the archive: hardening-check, from the hardening-includes package. Please talk to Kees to come up with the best solution (either checksec is uploaded and and hardening-check dropped, or checksec is not uploaded and missing features added to hardening-check, or hardening-check is uploaded and both co-exist in the archive.) Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- 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/i06lf4$7u...@dough.gmane.org
Re: question about debian/watch
José Manuel Santamaría Lema wrote: http://qa.debian.org/watch/sf.php/radiotray/ at the moment the last line says: Last database update: Sat, 05 Jun 10 23:58:50 + I fixed it the other day (lock file was still around.) Next time please report it to debian...@lists.d.o as soon as it is two days out of date. Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- 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/i0171p$vj...@dough.gmane.org
embedded-zlib and fpc (was: Re: RFS: easymp3gain (updated package), fixes RC bug)
Patrick Matthäi wrote: There is also an lintian error, which can not be overwritten and would reject it from the repository: E: easymp3gain-gtk: embedded-zlib ./usr/bin/easymp3gain This is added by fpc, see #472304. Not sure what the real status is, though. @ftp-masters: was the removal of embedded-zlib from the list of tags that can be overridden just temporary (because of the klibc incident)? A new version of lintian is about to be released and would like to know whether that change should be propagated. Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- 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/4bc3f946.1402be0a.12fe.5...@mx.google.com
Re: debian/watch sourceforge
Jaromír Mikeš wrote: $ uscan uscan warning: In watchfile debian/watch, reading webpage http://qa.debian.org/watch/sf.php/jcgui/ failed: 500 Can't connect to qa.debian.org:80 (connect: timeout) The whole server is down at the moment. Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: insserv: warning: current stop runlevel(s) ... overwrites defaults
Michael Hanke wrote: [...] Can anyone please point me to the problem and its solution? When making changes to the runlevels either via update-rc.d or the lsb header, the init script needs to be removed first (via update-rc.d, as simply removing the symlink won't work in the case of file-rc). In other words: you need to check if the user is upgrading from an affected version (probably anything lt the new version) and then do an update-rc.d remove. All that before the #DEBHELPER# mark so that the rest is done for you. And like Rogéiro Brito said, remove the S runlevel. First of all, S is only used by some special cases where the script only needs to be run once, second, syslog daemons are only available from post-rcS (which at some point would render your package uninstallable because of unmet init script dependencies). Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Lintian pickiness and packaging improvements
Manoj Srivastava wrote: On Thu, Oct 22 2009, Raphael Geissert wrote: Manoj Srivastava wrote: I also think that style issues should not be a part of even Pedantic checks. If a package is using a different, and arguably better style, then lintian should keep its nose out. If there's a better style I guess nobody would object to consider recommend it or You are not getting it. Better is subjective. You can have a dozen better styles, all contradictory. Are you planning on having checks that can never all be met simultaneously? That is what you get when you go for subjectively better styles. Yeah, I noticed that my argument was poor some minutes after posting the message, but forgot to correct it. The whole idea is to standardise, and preferably reduce to only two standard styles if possible. at least make sure lintian doesn't complain about it. Ah. I have a few of those. For example, take this warning from Lintian: description-synopsis-might-not-be-phrased-properly This is not policy, but dev-ref, and when it was proposed, it was argued that if we had a non clause, the front ends can make it look nicer, by completing the sentence, adding the period, etc, (perhaps by showing Package is a short description . That was around 6 years or so ago. This should probably be brought up on -devel and the new concensus applied and by lintian. [...] And why is this a warning as opposed to an informational message? How is the package impacted by having a gosh darned period in the short description? This is the same level of impairment as the other non info warnings? seriously? Thisis not a severity normal bug. It is not even a severity wishlist bug. It is a style issue. Agreed, the severity is over inflated. Things like that are why I take every lintian warning with a huge grain of salt. Would be great if you could help out by pointing those out. Even a short message on IRC with a short reasonable, initial, argument is enough. Please remember that lintian has many many checks (counting 832 different tags here), and that verifying each and every of them requires a lot of time and effort so any help is welcome (and by that I don't mean you should do anything else other than running lintian as usual and point out possible issues). Lintian is a great tool. But it has long standing flaws, and previous maintainers of lintian have been resistant to changing that. Feedback is very welcomed. P.S. Last post about this in -mentors, as Charles suggested/requested. Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Lintian pickiness and packaging improvements
Manoj Srivastava wrote: I also think that style issues should not be a part of even Pedantic checks. If a package is using a different, and arguably better style, then lintian should keep its nose out. If there's a better style I guess nobody would object to consider recommend it or at least make sure lintian doesn't complain about it. Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: ampache (updated package)
Hi Manoj, Manoj Srivastava wrote: On Tue, Oct 20 2009, Raphael Geissert wrote: Hi Manoj, Manoj Srivastava wrote: [...] I find that experimental and pedantic add far too much irrelevant chatter, and that it tends to mask the problems one should actually fix. Could you please elaborate a bit more? I'd like to know how I can improve lintian so that it is more useful for others. ,[ Manual page lintian(1) ] | --pedantic | Display pedantic (P:) tags as well. They are normally | suppressed. | | Pedantic tags are Lintian at its most pickiest and include | checks for particular Debian packaging styles, checks that are | very frequently wrong, and checks that many people disagree | with. Expect false positives and Lintian tags that you don't | consider useful if you use this option. Adding overrides for | pedantic tags is probably not worth the effort. ` Pretty much covers it, neh? Also: ,[ http://lintian.debian.org/manual/ch2.html#s2.3 ] | Experimental: | This means that the code that generates this message is not as well | tested as the rest of Lintian, and might still give surprising | results. Feel free to ignore Experimental messages that do not seem to | make sense, though of course bug reports are always welcomed. ` Well, experimental checks are not to be considered irrelevant chatter, hence my question. The current experimental checks are: Tag: spelling-error-in-binary Severity: normal Certainty: wild-guess It is based on the output of strings(1) so it can't tell for sure whether a string is actually displayed or it is just a symbol or something else, or whether it is really an error or not (although it is pretty accurate in most cases). -- Tag: template-uses-unsplit-choices Severity: normal Certainty: possible Erm, IIRC this one should no longer be marked as experimental ever since lenny was released. -- Tag: embedded-pear-module Severity: normal Certainty: possible PEAR modules are a bit tricky to detect properly without making it too specific, in which case the check itself wouldn't be of much use. -- Tag: shlib-calls-exit Severity: wishlist Certainty: possible There's no way for lintian to tell whether the usage of exit or _exit is correct at all in the shared library, and it is based only by looking at the symbols. Now, people experienced in packaging stuff for Debian ought to be looking at pedantic and experimental tags and giving feedback to Lintian, to improve it (I certainly do). But I only look at experimental and pedantic tags when I want to see f I want to give feedback to Lintian, not as a package check. As a package check it is very inefficient, and definitely not what I would recommend to a novice. I would personally recommend checking pedantic tags here in mentors, it is a great way to introduce people to best practises. If anyone refuses to make the change suggested by lintian elaborating a bit more why could be a good exercise as well. As a reference, the current pedantic checks are: no-upstream-changelog experimental-to-unstable-without-comment debian-control-has-unusual-field-spacing copyright-refers-to-symlink-license source-contains-cvs-control-dir source-contains-svn-control-dir source-contains-bzr-control-dir source-contains-arch-control-dir source-contains-git-control-dir source-contains-hg-control-dir source-contains-bts-control-dir source-contains-svn-commit-file source-contains-svk-commit-file source-contains-arch-inventory-file source-contains-hg-tags-file source-contains-cvs-conflict-copy source-contains-svn-conflict-file source-contains-prebuilt-binary source-contains-prebuilt-windows-binary no-homepage-field direct-changes-in-diff-but-no-patch-system example-unusual-interpreter example-interpreter-in-usr-local example-shell-script-fails-syntax-check maintainer-script-without-set-e Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Lintian pickiness and packaging improvements
Pedantic tags are Lintian at its most pickiest and include checks for particular Debian packaging styles, *checks that are very frequently wrong*, and checks that many people disagree with. Expect false positives and Lintian tags that you don't consider useful if you use this option. Adding overrides for pedantic tags is probably not worth the effort. As the person who pushed and introduced pedantic support I always felt a bit hesitant regarding the highlighted statement, maybe I should bring this up on the lintian mailing list and ask Russ for his reasons behind it (maybe what he wanted to express could be paraphrased). If a check is wrong I don't think it should belong to the pedantic category, IMHO. Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: ampache (updated package)
Hi Manoj, Manoj Srivastava wrote: [...] I find that experimental and pedantic add far too much irrelevant chatter, and that it tends to mask the problems one should actually fix. Could you please elaborate a bit more? I'd like to know how I can improve lintian so that it is more useful for others. Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: fslint (updated package)
Hi, Maximiliano Curia wrote: Hola Pádraig Brady! El 23/07/2009 a las 16:53 escribiste: [...] A few comments: - Standards-Version are a bit old 3.8.0, while 3.8.2 is the current one, please check that in furter uploads. - Concerning bugs: * #511805, should have been answered and closed. findutils is an essential package, there is no need to declare essential packages as dependecies, you added the dependency, and the bug will be closed in this upload, there is no harm in this but it's not the best solution. * You closed a few debian bugs in a version that never hit Debian repositories, that requires some manual tweaking to process the correct part of the changelog, please avoid it. That's ok, it was me who forgot to include the changelog entries when uploading it. * You package version is 2.40-2, which would not include the original source in the upload, and requires some manual tweaking to do so, please avoid that. This shouldn't be discouraged either. - You need to keep in contact with your mentors, that will accelerate your uploads, once you gain their trust you might prefer to advocate as a debian maintainer, so you can upload your own packages, it might be educational to have a new mentor in every upload, but it's quite inefficient (you are encouraged to ask for help, though). He actually sent me a copy of his RFS and I was going to take a look at it and require him to do proper cleanup this time (on the BTS and the package itself). I can't get 2.28 into debian because the mentor process sucks., that's not it. I'm uploading your package, please consider the previous comments in further changes. Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: libphp-pclzip (updated package)
Hi, debian/copyright: version 2 of the License, or (at your option) any later version. Upstream releases the source code under the GNU LGPL version 2.1, not version 2. Copyright (c) 2005-2009 Jose Carlos Medeiros deb...@psabs.com.br 2009? his last changes is dated 2007 on the changelog. and is licensed under the GPL version 3, see /usr/share/common-licenses/GPL-3. Which is not really accurate, as Jose Carlos didn't really say under what licence he released his packaging work. I guess it could be implied that his work was released under the terms of the same licence as upstream. This it nitpicking, but in theory no assumption could be made and the only (right) solution is to contact him. The debian/rules contains plenty of useless stuff, and installing the readme via debian/docs and later renaming it on the rules file looks ugly. There are also some debhelper scripts being called that don't anything on the package. debian/control: Please fix the dependencies, and improve the description (start by not repeating the name of the package all over the place). In case you need help improving the description don't hesitate to contact the English i10n mailing list. pclzip.lib.php: Using the current directory as the default directory for the temporary files is *not* a good idea at all (think about permissions) and it should therefore default to the TMPDIR environment variable, or at least /tmp. Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: deejayd (updated package)
Alexandre Rossi wrote: And the script doesn't correctly handle the case where the default file has been removed (it expects the vars to be always defined). The Xsession script doesn't handle an unset DEEJAYD_DISPLAYNAME and DEEJAYD_XAUTHORITY vars either. [ -r ] is evaluated to true. [ -r ] behaves correctly both with bash and sh on my lenny box. Not sure I understand what to do here. What I meant was that: $ foo=/foo/bar; [ -r $foo ] echo hello world $ unset foo; [ -r $foo ] echo hello world hello world $ unset foo; [ -r $foo ] echo hello world nothing Thanks a lot for the comments. I'll upload an updated version once I have implemented something to ensure the X server is ready in debian/deejayd.deejayd-xserver.init do_start() (and something better than sleep 2). Okay Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: pyspi (NMU - RC bug fix)
Charles Plessy wrote: [...] If he does not show interest for his package, then unless you want to adopt it, I would rather recommend that you file a request for removal. If for more than one year there was no manpower to take care of this package (and its reverse dependancy), then NMUing it will only have the effect of drawing some time of another developper at the next RC bug… I'll track its status, but am uploading the NMU in the meanwhile. Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: deejayd (updated package)
[Sending you a copy in case you are not subscribed] Hi, Alexandre Rossi wrote: Dear mentors, I am looking for a sponsor for the new version 0.8.3-1 of my package deejayd. [...] The package appears to be lintian clean. The informational messages can be ignored because both debhelper and python are needed to run the clean target. $ lintian -IE --pedantic deejayd_0.8.2-1.dsc I: deejayd source: build-depends-without-arch-dep debhelper I: deejayd source: build-depends-without-arch-dep python Whenever that happens you should report them. I just did it: #536405 To sum up the changelog, this new version : - is a new upstream version that fixes a lot, - fixes the build with python 2.6 (change of install locations), Which fixes an ubuntu bug but you are not closing it. The syntax is LP: # - handles pyinotify = 0.8 API changes, - closes #535374 (bashism in debian/rules) which is not in the changelog because it has been fixed a while ago, - eases the connection with Xorg (this is a daemon running with its own privileges, so connection to Xorg is tricky). debian/50...: tmpauthfile=`mktemp -p /tmp deejayd-reuse.XX` why do you specify a directory instead of letting mktemp find one on its own? debian/deejayd?deejayd-xserver.init if [ -z `hostname --version 21 | grep GNU` ]; then if ! hostname --version 21 | grep -q GNU; then xserverauthfile=`mktemp -p /tmp serverauth.XX` same as above And the script doesn't correctly handle the case where the default file has been removed (it expects the vars to be always defined). The Xsession script doesn't handle an unset DEEJAYD_DISPLAYNAME and DEEJAYD_XAUTHORITY vars either. [ -r ] is evaluated to true. And: $ checkbashisms -x debian/50deejayd_steal-session script debian/50deejayd_steal-session does not appear to have a #! interpreter line; you may get strange results possible bashism in debian/50deejayd_steal-session line 7 (should be 'b = a'): if [ $DEEJAYD_XSERVER_METHOD == reuse ]; then I've added a new rule to force the check of files in /etc/Xsession.d to the script I use on my archive-wide runs. There are probably other issues, but that's my review for now. Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: siege (updated package)
Charles Plessy wrote: Dear Tristan, lintian is easy to backport. Just debcheckout lintian, git checkout the tag that corresponds to the latest release, and build the package. It is much easier to take the package from sid and install it; it won't make any difference. Have a nice day, Cheers, -- Raphael Geissert - Debian Maintainer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: libsvm (bug fixed)
Hello, What about improving the short description? The LIBSVM shared library only tells me something, twice, I alread know: it is a library (*lib*svm2, The *LIB*SVM shared *library*), but doesn't tell me at all what SVM stands for, or what exactly that library does. Cheers, -- Raphael Geissert - Debian Maintainer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Re: RFS: xinha
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Mathieu, Daniel, Sorry for the late response, it's until now that I'm reading old messages from -mentors. Mathieu Parent wrote: 2008/11/29 Mathieu Parent math.par...@gmail.com: 2008/11/27 Raphael Geissert atomo64+deb...@gmail.com: [...] There are a couple of issues in xinha itself that I will be reporting later (security issues). Do you happen to have an email address of upstream? I couldn't find it anywhere on the website. Nope. But there are some webpages: James Sleeman: http://code.gogo.co.nz/contact/index.html Raimund Meyer: http://xinha.raimundmeyer.de/ (email may be ray AT openplans.org) Since those issues are rather minor it should be fine if xinha is, in the meanwhile, uploaded to unstable so that it goes through NEW. I'm back here to know if anything is missing to upload xinha to unstable. I think I've addressed all the tips. Just this: in debian/rules check-dfsg should be marked as a PHONY target as well. Daniel, since you are involved with other js packages: could you please take a look at xinha and sponsor it? Mathieu has done an amazingly great job preparing the package, and IMO it is perfect. The current dsc can be found at: http://mentors.debian.net/debian/pool/main/x/xinha/xinha_0.95-1.dsc Cheers, - -- Raphael Geissert - Debian Maintainer www.debian.org - get.debian.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkmAvoQACgkQYy49rUbZzlosGwCggcrIIkW0beecWmslfdmCKNO8 AlsAnjA5V/5JreSv9rsdXeQYY5HskeW2 =UDVt -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: sl-modem (updated package)
أحمد المحمودي wrote:
On Mon, Jan 26, 2009 at 09:04:42PM -0600, Raphael Geissert wrote:
Have you read the tag's description? it is not as to what the package does.
You mean the long description ? I fixed it uploaded.
No, I mean this:
$ lintian-info -t debhelper-but-no-misc-depends
N: debhelper-but-no-misc-depends
N:
N: The source package uses debhelper but it does not use ${misc:Depends}
N: in the given binary package's debian/control entry. This is required
N: so the dependencies are set correctly in case the result of a call to
N: any of the dh_ commands cause the package to depend on another
N: package.
N:
N: Refer to the debhelper(7) manual page for details.
N:
N: Severity: normal; Certainty: certain
N:
I fixed uploaded, except for one patch (04_sregs_init.diff). That was
introduced by previous maintainer. And I don't know what it does.
Then that's your homework :)
Thanks for the push ! I found out that it is an obsolete patch !
Previous maintainer had to remove it since 2.9.9e-pre1a. (I had to dig
into snapshot.debian.net to find out).
Good
Cheers,
--
Raphael Geissert - Debian Maintainer
www.debian.org - get.debian.net
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: whohas (bugfix)
http://mentors.debian.net/debian/pool/main/w/whohas/whohas_0.22-2.dsc Why do you think the information in README.Debian is relevant to anyone installing the package? Also, some typos in README.Debian: Intrebid wih upsream Cheers, -- Raphael Geissert - Debian Maintainer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: tkgate (updated package)
http://mentors.debian.net/debian/pool/main/t/tkgate/tkgate_2.0~b4-1.dsc $ lintian --pedantic -IE --show-overrides tkgate*dsc I: tkgate source: duplicate-short-description tkgate tkgate-data tkgate-doc I: tkgate source: quilt-patch-missing-description 01_paths.diff I: tkgate source: quilt-patch-missing-description 02_manpages.diff Please improve the packages descriptions. Typos in debian/control: langauge Cheers, -- Raphael Geissert - Debian Maintainer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: sl-modem (updated package)
The package appears to be lintian clean. Not really: $ lintian --pedantic -IE --show-overrides sl-modem*dsc W: sl-modem source: debhelper-but-no-misc-depends sl-modem-source I: sl-modem source: quilt-patch-missing-description modem_group.diff I: sl-modem source: quilt-patch-missing-description 02_dial_string_size.diff I: sl-modem source: quilt-patch-missing-description 03_Makefile_2.6.12.4.diff I: sl-modem source: quilt-patch-missing-description 04_sregs_init.diff I: sl-modem source: quilt-patch-missing-description 05_st7554_license.diff I: sl-modem source: quilt-patch-missing-description 06_slmodem-class-simple-to-class-meins.diff I: sl-modem source: quilt-patch-missing-description 08_ungrab_winmodem.diff I: sl-modem source: quilt-patch-missing-description 10_drop_privileges.diff I: sl-modem source: quilt-patch-missing-description 11_logfile.diff I: sl-modem source: quilt-patch-missing-description kernel-ver.diff I: sl-modem source: quilt-patch-missing-description README.diff I: sl-modem source: quilt-patch-missing-description debug_level.diff I: sl-modem source: quilt-patch-missing-description fortify_source.diff I: sl-modem source: quilt-patch-missing-description class_device.diff Cheers, -- Raphael Geissert - Debian Maintainer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: sl-modem (updated package)
Hi Neil, Neil Williams wrote: On Mon, 26 Jan 2009 13:08:53 -0600 Raphael Geissert atomo64+deb...@gmail.com wrote: The package appears to be lintian clean. Not really: $ lintian --pedantic -IE --show-overrides sl-modem*dsc W: sl-modem source: debhelper-but-no-misc-depends sl-modem-source That one is fine, but I'm concerned with your use of --pedantic. I: sl-modem source: quilt-patch-missing-description modem_group.diff Is that the result of --pedantic or just normal lintian? Michal already explained that pedantic tags are P, not I. In this case just demonstrates that the package is --pedantic clean as of lintian 2.0.0, nothing else. Raphael - are you saying that full compliance with the very new --pedantic option to lintian is now part of your sponsoring requirements? I'm not, yet, a DD so I still can't sponsor. But compliance with pedantic will be, at some extent, a requirement, yes. But please keep on reading before you comment on this. I'm not looking at this package in particular, but IMHO --pedantic needs quite a lot of care in handling - Russ admits that pedantic has less certainty than ordinary lintian checks with more room for false positives and false negatives. Those statements are true but also false, depends on the interpretations of each word. They are less certain or more likely to be false positives in the sense that for example no-upstream-changelog may be emitted even for multi bin packages, or even when upstream doesn't provide a changelog at all. http://www.eyrie.org/~eagle/journal/2009-01/019.html People should only use --pendantic if they're willing to see tags that are inaccurate or don't fit their personal style and take them with a grain of salt. Sure. It might be worth qualifying your use of --pedantic as your own preference. Do you filter some of the messages from --pedantic? Keep reading. I know you wanted --pedantic and worked on the implementation, but --pedantic does have problems and the results of using --pedantic are, IMHO, highly unreliable and in need of filtering one a package-by-package basis. FTR, I won't be using --pedantic *unless* it reveals a particular issue that I would like to have fixed anyway, i.e. where lintian provides some help on how to fix the issue. I plan to require an explanation to why the cause of the tag being emitted is not fixed/changed as suggested. There are currently only three tags: no-upstream-changelog no-homepage-field direct-changes-in-diff-but-no-patch-system As you can see the first two fit in the maintainer missed it or its upstream's problem case, while the last one is up to the maintainer, and would be happy if a good and strong explanation is provided as to not use a patch system nowadays. The following check requests have been considered to be implemented as pedantic: 497344, 497346, 474590, 409124, 127494, 236232, 339829, 119045, 483845, 42936. Note that some are indeed questionable but are a good start point for discussing the results with the maintainer, they are no necessarily meant to be just fix it because it's The Right Thing tags. At least that's my POV, others may of course differ. Cheers, -- Raphael Geissert - Debian Maintainer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: sl-modem (updated package)
أحمد المحمودي wrote: On Mon, Jan 26, 2009 at 07:41:08PM +, Neil Williams wrote: On Mon, 26 Jan 2009 13:08:53 -0600 Raphael Geissert atomo64+deb...@gmail.com wrote: The package appears to be lintian clean. Not really: $ lintian --pedantic -IE --show-overrides sl-modem*dsc W: sl-modem source: debhelper-but-no-misc-depends sl-modem-source That one is fine, but I'm concerned with your use of --pedantic. Sorry that I said that the package is lintian clean, I used the template that was in mentors.debian.net (seems that there is an old version of lintian there), and I totally forgot about this warning. mentors.d.n is not perfect, and you should get used to running lintian on your own :). I think that it is fine too, because that package actually builds another package (if module-assistant is used), or just builds some module files (if DKMS is used). Have you read the tag's description? it is not as to what the package does. I: sl-modem source: quilt-patch-missing-description modem_group.diff Is that the result of --pedantic or just normal lintian? Pedantic messages are prefixed with P: I fixed uploaded, except for one patch (04_sregs_init.diff). That was introduced by previous maintainer. And I don't know what it does. Then that's your homework :) Again, please advise me about the use of usermod in the postinst. Looks fine, but I have one question: why did you disable the version check? Cheers, -- Raphael Geissert - Debian Maintainer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Added requirement for translation of debconf templates
Hi Neil, One concern I have with your proposal/personal requirement is that: a) it depends on the time and availability of translators, and b) [ITP-only] it means that if a package is not in shape, doesn't fit in Debian, or there's any reason not to include it in the archive it would mean wasted time and work (depends on the POV of course[1]) for the translators, and am sure the majority won't be very happen. For a) not much can be done about, but for b) what I suggest is sending the first RFC as usual, and once the package gets an ok in terms of yes, looks good and I'm willing to help it get in the archive, the package maintainer should then send the request for translations. Other than that, +1 for pushing this idea. Cheers, -- Raphael Geissert - Debian Maintainer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RFS: ganttpv (was: Re: Processed: owner 509061)
Hello Brian, [CC'ing debian-mentors] 2008/12/19 Brian C. Christensen br...@pureviolet.net: Raphael, This is my first time submitting a request to get a package into Debian, so I don't know whether I'm supposed to contact you or not. If not, please ignore this email. You can contact me, just like anybody else, if you wish to; but there's no requirement ;) I'm just another folk working on Debian. I have taken my best shot at packaging GanttPV for Debian. I have posted requests for a sponsor on the sponsors web site and on the mentors web site. I have also sent the template email to the mentors mailing list and uploaded the .change file. Is there anything else that I am supposed to be doing to move this forward? First of all, have you seen the two replies sent to your email to the mentors mailing list? You can see your thread at http://comments.gmane.org/gmane.linux.debian.devel.mentors/34499 or in a different view: http://thread.gmane.org/gmane.linux.debian.devel.mentors/34499 or all alone: http://article.gmane.org/gmane.linux.debian.devel.mentors/34499 If you are not subscribed to the mailing list then say so when sending your messages, so that people can send you a copy of the message when replying. From what I can see, I've had nibbles but no bites. I am hoping that someone will be able to look it over and let know if something is wrong. One problem I know about is that I don't know how to set it up so that double clicking on a .ganttpv file would open the file with GanttPV. It appears that I need to add a new mime type and icon somewhere, but I can't find the documentation that says where and how to do that. That's done thanks to the .desktop files and to some other magic trick which I don't remember very well right now. You can start by taking a look at the .desktop files specifications at: http://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html In the mean time I'm trying to get people to try out my deb file. Assuming it works for them, I'll get the deb file posted on the GanttPV download site. Regards, Brian C. Christensen On Dec 18, 2008, at 8:27 PM, Debian Bug Tracking System wrote: Processing commands for cont...@bugs.debian.org: owner 509061 Brian C. Christensen br...@pureviolet.net Bug 509061 [wnpp] ITP: ganttpv -- project scheduling software Owner recorded as Brian C. Christensen br...@pureviolet.net. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) Cheers, -- Raphael Geissert - Debian Maintainer www.debian.org - get.debian.net Douglas MacArthur - We are not retreating - we are advancing in another direction. signature.asc Description: This is a digitally signed message part.
Re: RFS: webcpp
Cyril Brulebois wrote: Jonathan Wiltshire deb...@jwiltshire.org.uk (09/12/2008): This upload adds the VCS-* fields to debian/control and fixes some minor lintian warnings. Hi, thanks for your attention to details. That doesn't really look like needing an upload right now, though. I'd wait for a bugfix or a new upstream release to push those fixes (get them uploaded) if I were you. Why? there's no need to wait until work piles up. The only reason why I would recommend to wait is because the package currently in sid should probably be unblocked. Then the new upload could be made. OR The new package could be uploaded and the RT contacted so that it gets unblocked once the 10 days delay is over. Mraw, KiBi. Cheers, -- Raphael Geissert - Debian Maintainer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: webcpp
Jonathan Wiltshire wrote: On Thu, Dec 11, 2008 at 04:39:04PM -0600, Raphael Geissert wrote: The only reason why I would recommend to wait is because the package currently in sid should probably be unblocked. Then the new upload could be made. OR The new package could be uploaded and the RT contacted so that it gets unblocked once the 10 days delay is over. In this case should I apply for an unblock to allow one or the other into lenny? I hadn't thought it major enough but I'm not experienced in this bit, would appreciate your guidance. You can request the unblock for the current version in sid, but providing the debdiff for the new/proposed package and request the latter to be reviewed as well. I think the release team will tell you it is fine and that you should upload, and ping them when done. Cheers, -- Raphael Geissert - Debian Maintainer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: webcpp
Jonathan Wiltshire wrote: On Thu, Dec 11, 2008 at 11:55:35PM +0100, Cyril Brulebois wrote: No need to generate buildd, mirror, and upgrade noise only to fix some lintian warnings with no real bug IMHO. If it is lintian warning or error then chances are high that there *is* a bug. 1) ancient-libtool is about porting, 2) debhelper-but-no-misc-depends is about missing dependencies, 3) patch-system-but-direct-changes-in-diff and configure-generated-file-in-source are both, in this case, related to the same bug: lack of proper cleanup. FWIW the version curently in sid fixes a fairly nasty bug, but it doesn't cause data loss or anything so I don't know if it should qualify as an RC bug. If the diffstat is not large, and the changes are not just cosmetic, it is very likely that it will get unblocked. Cheers, -- Raphael Geissert - Debian Maintainer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Re: RFS: xinha
Hi, 2008/11/23 Mathieu Parent [EMAIL PROTECTED]: Hi, Thanks for all your help 2008/11/23 Raphael Geissert [EMAIL PROTECTED]: [...] Build-Depends: debhelper (= 6.0.7~) what is that tilde doing there? (lintian should probably warn about it) the tilde is for eventual backports of debhelper (see http://lintian.debian.org/tags/debhelper-script-needs-versioned-build-depends.html). Cite: Giving the version followed by ~ is recommended so that backports will satisfy the dependency. Yeah, Russ Allbery pointed that out in -mentors right after I sent the email. [...] debian/uupdate-wrapper: | gzip xinha_$version.orig.tar.gz use max compression (a.k.a -9) Done But looks like you didn't re-compress the tarball using -9, please do. * better use the same file name as in $file (there should be no worries about replacing the file while reading from it because tar requires the whole tarball to be available/read). Original tarbal is bzip2. that's why I rename it. I missed that part, sorry. [...] Regards Mathieu Parent There are a couple of issues in xinha itself that I will be reporting later (security issues). Do you happen to have an email address of upstream? I couldn't find it anywhere on the website. Cheers, -- Raphael Geissert - Debian Maintainer www.debian.org - get.debian.net Yogi Berra - I never said most of the things I said. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: RFS: xinha
Hi,
debian/control:
What about adding a replaces: htmlarea? or maybe some other mention so that
people looking for htmlarea actually find something (better).
Build-Depends: debhelper (= 6.0.7~)
what is that tilde doing there? (lintian should probably warn about it)
debian/rules:
(cleanup) build-stamp is not needed, you can get rid of it ('build' is a PHONY
target anyway).
#marking files as not executable (lintian warnings)
find debian/xinha/usr/share/xinha/www -type f -exec chmod -x '{}' \;
find debian/xinha/usr/share/doc/xinha/examples -type f -exec chmod -x '{}'
\;
chmod -R -x,+X debian/xinha/usr/share/xinha/www
chmod -R -x,+X debian/xinha/usr/doc/xinha/examples
cp contrib/php-xinha.php $(CURDIR)/debian/xinha/usr/share/doc/xinha/examples
dh_installchangelogs -i release-notes.txt
Why are these in binary-indep and not in install just like the rest?
(I know must packages do something similar, even some (if not all) of mine).
debian/copyright-REMOVED:
nice work :)
debian/uupdate-wrapper:
| gzip xinha_$version.orig.tar.gz
use max compression (a.k.a -9)
You should also:
* use 'set -e'
* better use the same file name as in $file (there should be no worries about
replacing the file while reading from it because tar requires the whole tarball
to be available/read).
debian/copyright:
Format-Specification:
http://wiki.debian.org/Proposals/CopyrightFormat?action=recallrev=REVISION
You are actually supposed to replace REVISION with the revision of the page you
based your copyright file on.
debian/examples:
I can see some references to the php-xinha.php file in xinha itself, are you
sure it should be installed just as an example?
Cheers,
--
Raphael Geissert - Debian Maintainer
www.debian.org - get.debian.net
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#495542: RFS: libcas-php
Hi,
[No need to CC me as long as -mentors is]
Olivier Berger wrote:
Hi.
Thanks for your review. I'll respond bellow.
Le lundi 17 novembre 2008 à 15:20 -0600, Raphael Geissert a écrit :
Olivier Berger wrote:
[...]
The corresponding ITP is found at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495542
Note that this package would allow the dependency of a number of
packages such as moodle and glpi on that package instead of shipping a
copy of phpCAS (http://packages.debian.org/sid/all/moodle/filelist and
http://packages.debian.org/sid/all/glpi/filelist).
While you are at it, as your package also uses domxml-php4-php5.php why don't
you also package it? (it would be better if the code was finally ported
instead of using a wrapper, though).
I can see a couple of reasons why packaging domxml-php4-php5.php may not
be needed :
* it's a one file library, so I'm not sure it's really a habit of
packaging individual files ?
* it may be included in Debian packages only by those which include a
copy of phpCAS (but confirmation would be welcome)
* It will probably be no longer needed in phpCAS when future releases
will be rewritten (as you suggest) to only support php5, thus using the
php5 DOM API instead of the old PHP4 one. But that's not something that
would be done only for Debian, and I'll wait until a decision is taken
upstream (although I may also again contribute to upstream development
for that). More details here :
http://www.ja-sig.org/issues/browse/PHPCAS-25 about a rewrite to get rid
of that wrapper.
So until usptream phpCAS releases a new version which allows to get rid
of domxml-php4-php5.php, I'll stick with it in.
Yeah, I forgot that all the matches I found of the dom lib were because of the
embedded copy of phpCAS
debian/control:
Depends: ${misc:Depends}, php5, php5-curl, php-db
Does it really need a web SAPI?
Uh, SAPI ?
SAPI: Server Application Programming Interface
E.g. apache, apache2, cgi, cli, embedded, roxen, etc.
or can it be used with php5-cli? in the latter
case add an ORed dependency on php5-cli in addition to php5.
I have no clue.
Typical use of CAS is traditionally on web apps, and the protocol
involves redirections between the CAS server and clients, so I'm not so
sure a non web use is something interesting.
I saw that, but CAS.php looked like a more general pourpose script, although I
didn't examine it very well.
I suppose most of the use cases would be satisfied as is... unless in
CGI mode, where php5-cgi would be ORed too ?
No, php5-cgi is already covered by php5.
debian/README.Debian:
This packaging needs testing as I'm not fully sure there ain't
regressions introduced by this upgrade of the DOM parsing library.
Have you at lest tested the basic functionality of the library with the newer
version of domxml-php4-php5.php or are you blindly packaging stuff?
No I have tested it, but you never exactly know for corner cases like
error messages hard to test.
Btw, my main motivation for packaging it is to use it on a production
server, so I'd better have it tested of course.
In any case I preferred some explicit mention that it's not exactly
upstream's version, to let people know who's to blame in case of
problem.
Will rephrase as :
Differences from upstream version :
---
This package includes a Debian specific patch, to replace
domxml-php4-php5.php version 1.5.5 (shipped with version 1.0.1
of
phpCAS) by version 1.20a of domxml-php4-to-php5.php, which is
now
under LGPL, making it DFSG-free.
Best care was taken by the Debian packager to make sure there
ain't
regressions introduced by this upgrade of the DOM parsing
library. Please report to the Debian BTS if you experience
problems
related to that change.
Ok, looks better now.
CAS.php:
define(CAS_PGT_STORAGE_FILE_DEFAULT_PATH,'/tmp');
..
define(CAS_PGT_STORAGE_FILE_FORMAT_PLAIN,'plain');
Doesn't look good at all.
Hmmm... I guess that needs to be fixed indeed. Thanks for spotting that.
CAS/client.php:
if ( $this-isProxy() ) {
// pass the callback url for CAS proxies
$validate_url .=
'pgtUrl='.$this-getCallbackURL();
}
Improper sanitation of getCallbackURL which uses data like REQUEST_URI; and
there's more about this, but I'm better going to test it and send the info to
bugtraq.
Feel free to notify me and/or [EMAIL PROTECTED] please (or have a
look at http://www.ja-sig.org/wiki/display/CASC/phpCAS+bug+reports .
What about also shipping the api docs?
Well maybe in a separate -doc package, then ?
IIRC it was pretty small, so there's no need, IMHO, to ship it in another
package.
I
Re: Re: RFS: xinha
Mathieu Parent wrote: Hi, ./plugins/Linker/dTree/dtree.css:| Copyright (c) 2002-2003 Geir Landr? | ./skins/inditreuse/README:This work is licensed under the Creative Commons Attribution-ShareAlike License. ./skins/titan/README:This work is licensed under the Creative Commons Attribution-ShareAlike License. And the many other copyright owners which you can find via grep -r c_owner TODO. A bit more complex. I will dot it next. I've done a first try. there are some CC-by-sa files. Are they dfsg? or Should I remove them from tarballs? Quoting [1]: Attribution-ShareAlike 2.0 debian-legal contributors think that works licensed solely under the Attribution-ShareAlike 2.0 [BY-SA] are not free according to the DFSG and should not be included in Debian. The Attribution-ShareAlike has the same problems as the Attribution 2.0 license. IOW: you either get a licence change or you have to remove them from the tarball. [1]http://web.archive.org/web/20070912053256/http://people.debian.org/~evan/ccsummary.html (http://evan.prodromou.name/ccsummary/ccsummary.html) ^^^ Nice, this is the same file :) Mathieu Parent Cheers, -- Raphael Geissert - Debian Maintainer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#495542: RFS: libcas-php
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Olivier Berger wrote:
[...]
The corresponding ITP is found at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495542
Note that this package would allow the dependency of a number of
packages such as moodle and glpi on that package instead of shipping a
copy of phpCAS (http://packages.debian.org/sid/all/moodle/filelist and
http://packages.debian.org/sid/all/glpi/filelist).
While you are at it, as your package also uses domxml-php4-php5.php why don't
you also package it? (it would be better if the code was finally ported instead
of using a wrapper, though).
debian/control:
Depends: ${misc:Depends}, php5, php5-curl, php-db
Does it really need a web SAPI? or can it be used with php5-cli? in the latter
case add an ORed dependency on php5-cli in addition to php5.
debian/rules:
What about cleaning it up?
debian/copyright:
Upstream Author:
Pascal Aubry
What about also displaying his email address?
License: (stated at : http://www.ja-sig.org/wiki/display/CASC/phpCAS)
what about docs/README?
- In case of jurisdiction dispute, the French law is authoritative.
let's see what ftpmasters say about this.
debian/dirs:
empty? delete it
debian/docs:
ditto
debian/README.Debian:
This packaging needs testing as I'm not fully sure there ain't
regressions introduced by this upgrade of the DOM parsing library.
Have you at lest tested the basic functionality of the library with the newer
version of domxml-php4-php5.php or are you blindly packaging stuff?
CAS.php:
define(CAS_PGT_STORAGE_FILE_DEFAULT_PATH,'/tmp');
..
define(CAS_PGT_STORAGE_FILE_FORMAT_PLAIN,'plain');
Doesn't look good at all.
CAS/client.php:
if ( $this-isProxy() ) {
// pass the callback url for CAS proxies
$validate_url .= 'pgtUrl='.$this-getCallbackURL();
}
Improper sanitation of getCallbackURL which uses data like REQUEST_URI; and
there's more about this, but I'm better going to test it and send the info to
bugtraq.
What about also shipping the api docs?
I would be glad if someone uploaded this package for me.
Kind regards
Olivier Berger
Cheers,
- --
Raphael Geissert - Debian Maintainer
www.debian.org - get.debian.net
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkkh4DgACgkQYy49rUbZzlpidACdHdyy2K2FNo2334O5aYeJBE3N
UuMAnitV2FwS6aXckmPYlucnoaLBivPm
=bYUb
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Fwd: Re: RFS: xinha
ping
--- Forwarded message (begin)
Subject: Re: RFS: xinha
From: Raphael Geissert [EMAIL PROTECTED]
Date: Sat, 30 Aug 2008 14:43:51 -0600
Newsgroup: gmane.linux.debian.devel.mentors
Mathieu Parent wrote:
On Sat, Aug 30, 2008 at 4:30 AM, Raphael Geissert
[EMAIL PROTECTED] wrote:
Hi Mathieu,
Mathieu PARENT wrote:
Dear mentors,
I am looking for a sponsor for my package xinha.
* Package name: xinha
Version : 0.95~rc2-1
Version 0.95 has now been released, could you please update the package?
This is already done since june, see:
http://mentors.debian.net/debian/pool/main/x/xinha/xinha_0.95-1.dsc
Ok, sorry for not looking at mentors. So, let's review it so it can be
uploaded to the archive soon (won't make it for lenny, of course).
debian/control:
Standards-Version: 3.7.3
Should be updated if the package comforms to 3.8.0
debian/rules:
...
cp -r plugins $(CURDIR)/debian/xinha/usr/share/xinha/www/plugins
cp -r popups $(CURDIR)/debian/xinha/usr/share/xinha/www/popups
cp -r skins $(CURDIR)/debian/xinha/usr/share/xinha/www/skins
install -t $(CURDIR)/debian/xinha/usr/share/xinha/www/ \
htmlarea.js Xinha.css XinhaCore.js XinhaLoader.js
why not just use dh_install and debian/install?
find debian/xinha/usr/share/xinha/www -type f -exec chmod -x '{}'
\;
find debian/xinha/usr/share/doc/xinha/examples -type f -exec
chmod -x '{}' \;
chmod -X debian/ ?
debian/copyright:
See `/usr/share/common-licenses/LGPL'.
You should be more specific and point to LGPL-2
is licensed under the GPL, see `/usr/share/common-licenses/GPL'.
same here (and you should really think about that licence, as a mix of BSD +
LGPL + GPL can cause troubles).
Btw, it doesn't mention:
./XinhaCore.js:-- Copyright (c) 2005-2008 Xinha Developer Team and
contributors
./popups/about.html: Copyright (c) 2005-2008 Xinha Developer Team and
contributors
./plugins/Linker/dTree/dtree.css:| Copyright (c) 2002-2003 Geir
Landr? |
./skins/inditreuse/README:This work is licensed under the Creative Commons
Attribution-ShareAlike License.
./skins/titan/README:This work is licensed under the Creative Commons
Attribution-ShareAlike License.
And the many other copyright owners which you can find via grep -r c_owner
debian/docs:
debian/dirs:
release-notes.txt should actually be installed as upstream's changelog
(dh_installchangelogs).
Please fix the above mentioned issues (and investigate on the copyright
owner line which has a '?', and the licences of the plugins and skins).
Mathieu Parent
Cheers,
--
Atomo64 - Raphael
Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
--- Forwarded message (end)
--
Raphael Geissert - Debian Maintainer
www.debian.org - get.debian.net
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Using pbuilder to test packages with gcc-snapshot
Paul Wise wrote:
On Fri, Nov 14, 2008 at 11:19 AM, Kumar Appaiah
[EMAIL PROTECTED] wrote:
1. Is there a way to set an arbitrary environment variable while
running pbuilder (in my case, LD_LIBRARY_PATH).
grep export ~/.pbuilderrc
export CCACHE_DIR=/var/cache/pbuilder/ccache
export PATH=/usr/lib/ccache:${PATH}
export DPKG_GENSYMBOLS_CHECK_LEVEL=4
export DEBUILD_DPKG_BUILDPACKAGE_OPTS=-j2
export MAKEFLAGS=-j2
2. Is there a better way of doing gcc-snapshot testing with pbuilder?
I would add a hook to get an interactive shell before pbuilder
installs build-deps and install gcc-snapshot from that shell.
This is much easier:
export LD_LIBRARY_PATH=/usr/lib/gcc-snapshot/lib:$LD_LIBRARY_PATH
export PATH=/usr/lib/gcc-snapshot/bin:$PATH
EXTRAPACKAGES=gcc-snapshot ${EXTRAPACKAGES}
My pbuilder configuration contains the interactive shell hook(s):
http://people.debian.org/~pabs/tmp/pbuilder.tar.gz
Cheers,
--
Raphael Geissert - Debian Maintainer
www.debian.org - get.debian.net
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: question
Hi, Dionysis Kalofonos wrote: Dear mentors, i have a program that i want to compile, but i miss the file 'curl-config' and so the process stops with an error. My questions is. How can i find the package the provides the above file (it can be more than one)? You can either use the apt-file command or packages.debian.org. i am currently searching on google for such cases, but i was wandering whether there is a better way. Mainly i want to provide a suggestion when such failures occur. For instance in this case i could say that possible candidate packages for this file are x,y,z... That's what Build-Depends are for: there you specify the name of the packages required to build the package; and of course you can use ORed dependencies, e.g. Build-Depends: foo | bar many thanks Cheers, -- Raphael Geissert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Automated checks for correct ‘build’ and ‘clean’ behaviour
Ben Finney wrote: Howdy mentors, I've seen some discussion around the topic of Debian packages which don't clean properly in their ‘clean’ target, and others that fail if the ‘build’ target is invoked twice in succession. Are there automated checks one can invoke on a local machine to make sure a package behaves properly in these respects? Perhaps using a ‘pbuilder’ environment? If you rebuild a package twice in a row (source and binary builds) and compare the .diff.gz, or if the second build fails then you will find some of those bugs. pbuilder support hook scripts which can help you do most of the stuff automagically (once coded, of course). Cheers, -- Raphael Geissert - Debian Maintainer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt-proxy, apt-cacher approx
Thomas Goirand wrote: Hi, We've been using apt-proxy for about a year, and then found it quite buggy. So we moved to using apt-cacher. Now we have loads of problems with apt-cacher as well (like currently, a recurring tzdata size They will go away if you unlink the .deb file in /var/cache/apt-cacher/packages/. I've been using apt-cacher for over a year and despite some bugs it has worked fine. I've been tempted to give apt-cacher-ng a try, though. mismatch error). I was wondering if approx is any better than the other two. Did any of you try? Thomas Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Choosing a sensible name for a new package split from octave3.0
Rafael Laboissiere wrote: ... octave3.0-mscripts (although, there will be other files than *.m in the package) ... Suggestions? Why not just octave3.0-scripts? (note the missing 'm'). It would make more sense than a -data or -common package to me as it really describes the content. Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: libmarkdown-php
Daniel Watkins wrote: Hi Raphael, Thanks for the continuing attention. On Sun, 24 Aug 2008 19:16:14 -0500 Raphael Geissert [EMAIL PROTECTED] wrote: debian/rules: The package FTBFS twice in a row because it moves the PHP Markdown Readme.text in the main directory without rolling back that change at the clean target (another possible solution would be to rename the file once it is under debian/). Fixed. Hmmm, not quite right: libmarkdown-php_1.0.1m-1_all.deb new debian package, version 2.0. size 28602 bytes: control archive= 911 bytes. 1009 bytes,24 lines control 311 bytes, 4 lines md5sums Package: libmarkdown-php Version: 1.0.1m-1 Architecture: all Maintainer: Daniel Watkins [EMAIL PROTECTED] Installed-Size: 96 Depends: php5 | php5-cli Section: web Priority: optional Homepage: http://michelf.com/projects/php-markdown/ Description: PHP library for rendering Markdown data Markdown is two things: a plain text markup syntax, and a software tool that converts the plain text markup to HTML for publishing on the web. . The Markdown syntax allows you to write text naturally and format it without using HTML tags. More importantly: in Markdown format, your text stays enjoyable to read for a human being, and this is true enough that it makes a Markdown document publishable as-is, as plain text. If you are using text-formatted email, you already know some part of the syntax. . PHP Markdown can work as a plug-in for WordPress and bBlog, as a modifier for the Smarty templating engine, or as a replacement for textile formatting in any software that support textile. drwxr-xr-x root/root 0 2008-09-07 14:15 ./ drwxr-xr-x root/root 0 2008-09-07 14:15 ./usr/ drwxr-xr-x root/root 0 2008-09-07 14:15 ./usr/share/ drwxr-xr-x root/root 0 2008-09-07 14:15 ./usr/share/php/ -rw-r--r-- root/root 48310 2008-06-21 01:58 ./usr/share/php/markdown.php drwxr-xr-x root/root 0 2008-09-07 14:15 ./usr/share/doc/ drwxr-xr-x root/root 0 2008-09-07 14:15 ./usr/share/doc/libmarkdown-php/ -rw-r--r-- root/root 9535 2008-06-21 01:58 ./usr/share/doc/libmarkdown-php/PHP Markdown Readme.text.gz -rw-r--r-- root/root 1475 2008-09-07 14:12 ./usr/share/doc/libmarkdown-php/copyright -rw-r--r-- root/root 165 2008-09-07 14:12 ./usr/share/doc/libmarkdown-php/changelog.Debian.gz You have to rename the file before debhelper builds the package, I.e. after install and before binary. Oh, and: debian/copyright: The Debian packaging is (C) 2008, Daniel Watkins [EMAIL PROTECTED] and is licensed under the BSD, see above. N: The copyright file contains dh-make's incomplete Debian packaging N: copyright boilerplate. As (C) is not considered as a valid way to N: express the copyright ownership the word Copyright or the © symbol N: should be used instead or in addition to (C). (based on a check I wrote for lintian, but not yet merged) Cheers, Dan Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: libmarkdown-php
Daniel Watkins wrote: On Sun, 07 Sep 2008 14:22:32 -0500 The updated package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/l/libmarkdown-php - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/l/libmarkdown-php/libmarkdown-php_1.0.1m-1.dsc With the sole exception being the fact that the Readme also contains the changelog, it looks fine to me now (you could actually add a 'changelog.gz' - 'README.gz' symlink). It is now up to a DD to sponsor the package (I'm stuck on NM, so can't do it), which shouldn't be so hard now. Cheers, Dan Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: copher
Hi,
Jonathan Wiltshire wrote:
The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/c/copher
- Source repository: deb-src http://mentors.debian.net/debian unstable
main contrib non-free
- dget
http://mentors.debian.net/debian/pool/main/c/copher/copher_0.1.2-1.dsc
Makefile:
This file is useless, you don't need it, you should drop it.
debian/watch:
http://qa.debian.org/watch/sf.php/copher copher-(.*).tar.gz debian
Did you know that the first part can be written as http://sf.net/copher ?
Also note that the unquoted dots after the closing parenthesis is actually
interpreted as part of the regex and could actually match anything?
debian/control:
Priority: extra
why?
Architecture: any
Depends: libwww-mechanize-perl, ${shlibs:Depends}
The perl script is architecture-dependent, isn't it?
Copher makes a SourceForge release automatically. It is useful as part
of a build and release system.
This doesn't really tell me much about Copher; I am the admin of a project
at sf.net and that description doesn't tell me it could be useful to me.
of a build and release system. Support for other GForge-based sites is
in development.
SF.net is not 'GForge-based', that sentence should be rephrased.
debian/copher.1:
DESCRIPTION
Copher makes a SourceForge release automatically. It is useful as
part
of a build and release system. Support for other GForge-based
sites is
in development. copher is a program that...
same here, although here it looks worst as it just ends with '...'
debian/rules:
debian/compat:
debian/control:
You build-depend on debhelper 7 but use none of its features? you
should/could use a lower compat level such as 5 instead.
debian/rules:
Please remove the commented commands, do what you do on the Makefile here,
and build the package in binary-indep, not in binary-arch.
debian/dirs:
file is useless, remove it
$ xlintian -I -E copher*changes
W: copher: extra-license-file usr/share/doc/copher/COPYING.gz
I: copher: package-contains-empty-directory usr/sbin/
Thank you for taking the time to consider sponsoring me.
Cheers,
--
Atomo64 - Raphael
Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: xinha
George Danchev wrote: On Saturday 30 August 2008 04:30:21 Raphael Geissert wrote: Hello, * Package name: xinha Version : 0.95~rc2-1 Version 0.95 has now been released, could you please update the package? DD's: can anyone take a look at the package when updated? there are several packages shipping their own copy of xinha or htmlarea and would be nice to have just one copy in the whole archive. Do you happen to know which are these packages and if bugs (normal) was filed against them. Sometimes, it is not possible to avoid code dups, since there might be significant incompatible deviations from the original, but sometimes it worth the effort. These should also be identified at: http://wiki.debian.org/EmbeddedCodeCopies Sure, finding them is as easy as grep'ing Contents-arch: axyl horde3 And for htmlarea: moodle serendipity typo3-src-4.2? (rtehtmlarea) And no, no bugs have been filed yet (well, at least *I* haven't filed any); what I've been doing is collect the list of packages shipping their own copy, and file a RFP CC'ing their respective @packages.d.o address. My plan was to make lintian aware of those libs too as soon as the packaged js libs were uploaded. Oh, and you might also be interested in: http://lintian.debian.org/tags/embedded-javascript-library.html Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: xinha
Mathieu Parent wrote:
On Sat, Aug 30, 2008 at 4:30 AM, Raphael Geissert
[EMAIL PROTECTED] wrote:
Hi Mathieu,
Mathieu PARENT wrote:
Dear mentors,
I am looking for a sponsor for my package xinha.
* Package name: xinha
Version : 0.95~rc2-1
Version 0.95 has now been released, could you please update the package?
This is already done since june, see:
http://mentors.debian.net/debian/pool/main/x/xinha/xinha_0.95-1.dsc
Ok, sorry for not looking at mentors. So, let's review it so it can be
uploaded to the archive soon (won't make it for lenny, of course).
debian/control:
Standards-Version: 3.7.3
Should be updated if the package comforms to 3.8.0
debian/rules:
...
cp -r plugins $(CURDIR)/debian/xinha/usr/share/xinha/www/plugins
cp -r popups $(CURDIR)/debian/xinha/usr/share/xinha/www/popups
cp -r skins $(CURDIR)/debian/xinha/usr/share/xinha/www/skins
install -t $(CURDIR)/debian/xinha/usr/share/xinha/www/ \
htmlarea.js Xinha.css XinhaCore.js XinhaLoader.js
why not just use dh_install and debian/install?
find debian/xinha/usr/share/xinha/www -type f -exec chmod -x '{}'
\;
find debian/xinha/usr/share/doc/xinha/examples -type f -exec
chmod -x '{}' \;
chmod -X debian/ ?
debian/copyright:
See `/usr/share/common-licenses/LGPL'.
You should be more specific and point to LGPL-2
is licensed under the GPL, see `/usr/share/common-licenses/GPL'.
same here (and you should really think about that licence, as a mix of BSD +
LGPL + GPL can cause troubles).
Btw, it doesn't mention:
./XinhaCore.js:-- Copyright (c) 2005-2008 Xinha Developer Team and
contributors
./popups/about.html: Copyright (c) 2005-2008 Xinha Developer Team and
contributors
./plugins/Linker/dTree/dtree.css:| Copyright (c) 2002-2003 Geir
Landr? |
./skins/inditreuse/README:This work is licensed under the Creative Commons
Attribution-ShareAlike License.
./skins/titan/README:This work is licensed under the Creative Commons
Attribution-ShareAlike License.
And the many other copyright owners which you can find via grep -r c_owner
debian/docs:
debian/dirs:
release-notes.txt should actually be installed as upstream's changelog
(dh_installchangelogs).
Please fix the above mentioned issues (and investigate on the copyright
owner line which has a '?', and the licences of the plugins and skins).
Mathieu Parent
Cheers,
--
Atomo64 - Raphael
Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: phpmyid
Vincent Bernat wrote:
OoO En ce début d'après-midi ensoleillé du jeudi 28 août 2008, vers
15:04, Andreas Schildbach [EMAIL PROTECTED] disait :
In debian/control, your dependencies are too strict.
I relaxed the dependencies. However, how can I know that my package
actually works with all HTTP daemons? I cannot test them all.
It is not really your matter. You provide a configuration file for the
one or several HTTP daemon and let the user handle other cases. The
point here is to not force the user install Apache while he wants to use
another daemon to run this package.
Depends: apache2 | httpd, php5
This should actually be apache2 | httpd-cgi, php5; as a simple httpd like
dhttpd Provides: httpd but won't be of any use when the user wants to run
php5-cgi (which is the only web server non-apache SAPI of php being shipped
atm).
I think that you should not ship htaccess file (or as documentation).
It is usually better to put all configuration in Apache configuration
file. For example, by default, rewrite rules are not authorized in
htaccess. You can put the content of htaccess in your apache2.conf
file for example.
What do you mean by rewrite rules are not authorized? Is it perhaps
better to not deviate from upstream in this case (htaccess comes from
upstream)? I could try to convince upstream to change this with the next
version.
The default configuration of Apache does not allow to put rewrite rules
in .htaccess files. In post-lenny, nothing will be authorized by default
in .htaccess. Therefore, a user modifying .htaccess will get a non
working configuration unless it also modifies an AllowOverride clause.
Upstream ships .htaccess because it allows user to just unpack the soft
in some directory and make it work without modifying anything else (but
as pointed above, this won't work on a default Debian system). Since you
are packaging the software for Debian, you don't need to use .htaccess
because you can alter Apache configuration (usually by dropping a file
in /etc/apache2/conf.d).
The file is actually useless as it only provides a couple of examples on
what need to add when php5-cgi is used (it actually doesn't make any
sense that you need those).
There is no mandatory document about this. You can look at the draft
policy here:
http://webapps-common.alioth.debian.org/draft/html/ch-httpd.html
...
Besides that, taking a quick look at the code:
// if neither, offer the trust request
$q = strpos($profile['req_url'], '?') ? '' : '?';
wrong assumption, strpos returns false but might also return 0 which in that
case would be evaluated just like false.
Oh, and by looking at the code:
# 'allow_gmp' = false,
# 'allow_test'= false,
# 'allow_suhosin' = false,
Enabling allow_gmp requires the user to have the php5-gmp extension
installed, so it might be a good idea to Suggests (probably not Recommends
as it can fall back to use bcmath which is a built-in extension of the php5
packages) it.
I don't see any real reason for this:
$extension_b = array('suhosin');
foreach ($extension_b as $x) {
if (extension_loaded($x) ! $profile[allow_$x])
error_500(phpMyID is not compatible with '$x');
}
phpMyID is NOT compatible with Suhosin or other hardened PHP systems
(Debian
users take note).
*) Received error: phpMyID is not compatible with 'suhosin'
Suhosin is a security add-on for PHP which, amongst other things,
removes
PHP's ability to open and access multiple sessions at one time. Simply
put,
phpMyID is reliant upon this feature, and will therefore not work with
a
hardened PHP.
To make phpMyID work with Suhosin, you can try the following:
1) Set the profile key 'allow_suhosin' to true in your config file.
2) Set suhosin.session.encrypt Off in either your PHP/Suhosin config
file,
or as a php_flag in your httpd.conf (or .htaccess).
See: https://www.siege.org/forum/viewtopic.php?pid=3167
You should really clarify that.
Anyway, the code is prone to XSS attacks (I could actually be more specific
if you want me to, but better let upstream review all the code) on the html
it prints and the headers it sends. It even relies on HTTP_HOST and doesn't
perform any sanity check on it.
IMHO the code is not ready to be uploaded as there are security issues that
need to be addressed first and not after it is uploaded to Debian.
Cheers,
--
Atomo64 - Raphael
Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: wordpress-openid
Andreas Schildbach wrote:
Dear mentors,
I am looking for a sponsor for my package wordpress-openid.
* Package name: wordpress-openid
Version : 2.2.1-1
Upstream Author : Will Norris, Alan J. Castonguay, Factory Joe
* URL : http://wordpress.org/extend/plugins/openid/
* License : GPL modified BSD, Apache License 2.0
Section : net
logic.php:
script prints the content of QUERY_STRING directly probably without any kind
of sanitation.
interface.php:
similar issue when printing $_REQUEST['page']
logic.php:
I don't understand why there's such kind of, bogus, exception:
// use email address for username if URL is from emailtoid.net
$username = $identity_url;
if (null != $_SESSION['openid_login_email'] and
strpos($username, 'http://emailtoid.net/') == 0) {
if($user_data['user_email'] == NULL) {
$user_data['user_email'] =
$_SESSION['openid_login_email'];
}
$username = $_SESSION['openid_login_email'];
unset($_SESSION['openid_login_email']);
}
Also, the strpos usage is completely incorrect, see the following example:
$ php -n -r '$foo=bar; var_dump(strpos($foo, moo) == 0);'
bool(true)
$ php -n -r '$foo=bar; var_dump(strpos($foo, moo) === 0);'
bool(false)
(again) logic.php:
if( strpos( $claimed_url, '@' ) ) {
and
if (strpos($wp_version, '2.5') != 0) {
are also incorrect.
files/jquery.xpath.*:
files are jquery plugins that should be shipped in a separate package.
files/jquery.textnode.*:
same as above, but I couldn't find its homepage
Kind regards
Andreas Schildbach
P.S. there is also phpmyid, an OpenID identity provider, still waiting to
be sponsored:
http://mentors.debian.net/debian/pool/main/p/phpmyid
Cheers,
--
Atomo64 - Raphael
Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: xinha
Hi Mathieu, Mathieu PARENT wrote: Dear mentors, I am looking for a sponsor for my package xinha. * Package name: xinha Version : 0.95~rc2-1 Version 0.95 has now been released, could you please update the package? DD's: can anyone take a look at the package when updated? there are several packages shipping their own copy of xinha or htmlarea and would be nice to have just one copy in the whole archive. * URL : http://xinha.webfactional.com/ * License : BSD Section : web It builds these binary packages: xinha - powerful WYSIWYG HTML editor The package appears to be lintian clean. The upload would fix these bugs: 479708 (ITP: xinha -- powerful WYSIWYG HTML editor) The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/x/xinha - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/x/xinha/xinha_0.95~rc2-1.dsc I would be glad if someone uploaded this package for me. Kind regards Mathieu Parent Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: No sponsor found for weeks, what to do now?
[Please don't send me a copy of the message, thanks.] Kartik Mistry wrote: On Thu, Aug 28, 2008 at 5:53 AM, Raphael Geissert [EMAIL PROTECTED] wrote: (xlintian is an alias to the dev copy of lintian on my machine, which also happens to have a couple or more checks that should/will be added to lintian). Probably, people on mentors will love to use your xlintian :) Because it is an *x*lintian? or why? :) The official lintian vcs can be found at git.d.o, as well as my own lintian repository. But, as you can imagine, I try to get all my changes mainstream. Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: wordpress-openid [was: Re: No sponsor found for weeks, what to do now?]
Andreas Schildbach wrote: Hi Raphael, On Wed, 2008-08-27 at 19:23 -0500, Raphael Geissert wrote: Andreas, please don't take these wrong but your packages really need a lot of changes and reading the documentation and looking at different packages and even reading the reviews posted for other packages could help you understand what needs to be changed in your packages. Once they are in a better shape they could then be polished. By the way, is there any PHP-related policy or best practice for PHP packaging, like there is for Java? Mauro Lizaur already commented on that, but currently the best practise is not documented and you should try to follow what other php packages do. I: wordpress-openid source: debian-watch-file-is-missing What if there is no site to watch on? The download link is http://downloads.wordpress.org/plugin/openid.2.2.2.zip but the containing folder http://downloads.wordpress.org/plugin/ does not allow directory listing. uscan doesn't only work on directory listings, it actually works on directory listings because they contain links to the files and that's all it needs. (Working) example for that package: version=3 http://wordpress.org/extend/plugins/openid/download/ \ http://downloads.wordpress.org/plugin/openid.(.+)\.zip (I just noticed that there is a new upstream version. I will update my Debian package to reflect that.) X: wordpress-openid: embedded-pear-module usr/share/wordpress/wp-content/plugins/openid/Log/error_log.php Looks like I have to create a dependancy to 'php-log' and remove the offending files from my package. I hope that by 'remove' you mean not install them on the .deb package. Thanks for your hints. Best regards, Andreas Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: No sponsor found for weeks, what to do now?
Vincent Bernat wrote: OoO Lors de la soirée naissante du mercredi 27 août 2008, vers 18:24, Andreas Schildbach [EMAIL PROTECTED] disait : phpmyid - standalone, single user, OpenID identity provider http://mentors.debian.net/debian/pool/main/p/phpmyid You can try to ask for sponsorship in Debian PHP team. However, this team is essentially dedicated to maintaining PHP. Therefore, I am not sure that you will get an answer for this one. I not being a DD have reviewed several php packages on -mentors hoping to increase a little bit the quality of php packages around but these have so many 'issues' that I haven't had enough time to write something appropriate. Andreas, please don't take these wrong but your packages really need a lot of changes and reading the documentation and looking at different packages and even reading the reviews posted for other packages could help you understand what needs to be changed in your packages. Once they are in a better shape they could then be polished. Oh, and of course, here I'm just talking about the Debian packaging, but the code often needs a review to attempt to prevent security problems right from the start. wordpress-openid - OpenID consumer plugin for WordPress http://mentors.debian.net/debian/pool/main/w/wordpress-openid Wordpress maintainer may be interested to help you in sponsoring this package. Unfortunately, Wordpress maintainer is not a DD... (xlintian is an alias to the dev copy of lintian on my machine, which also happens to have a couple or more checks that should/will be added to lintian). $ xlintian -I -E *.dsc I: wordpress-openid source: debian-watch-file-is-missing I: wordpress-openid source: package-lacks-versioned-build-depends-on-debhelper 7 I: phpmyid source: package-lacks-versioned-build-depends-on-debhelper 7 $ xlintian -I -E *.changes X: wordpress-openid: embedded-pear-module usr/share/wordpress/wp-content/plugins/openid/Log/error_log.php X: wordpress-openid: embedded-pear-module usr/share/wordpress/wp-content/plugins/openid/Log/file.php X: wordpress-openid: embedded-pear-module usr/share/wordpress/wp-content/plugins/openid/Log/null.php X: wordpress-openid: embedded-pear-module usr/share/wordpress/wp-content/plugins/openid/OpenIDLog.php W: wordpress-openid: copyright-lists-upstream-authors-with-dh_make-boilerplate E: phpmyid: copyright-should-refer-to-common-license-file-for-gpl Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: libmarkdown-php
Hi, Please take liboauth-php's review and fix the same applying issues on this package. Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Lintian error
Charliej wrote: With that said this is a quote from my upstream: Whee, is this something you could take care of at install, delete and then create a symlink. Or would this still violate this policy Would this be a viable solution? (I told upstream I would ask) I don't think this is a viable solution because the lintian error would still remain. You should symlink the file provided by the other package, if lintian still complains it is a bug in lintian then. I think one of the reasons he is hesitant is that the removal of prototype from the .tar.gz that he hosts would severely impact his M$ Windows users (he has a rather large M$ Windows community). Actually I could care less about M$ Windows users, but he does. As I see it to comply with Policy 4.13 prototype will have to be removed from upstreams .tar.gz.. Am I correct in this assumption? No, he doesn't need to remove his copy of prototype, it is _you_ who needs to prevent it from being installed in the package you build. This brings me to the next point what if upstream refuses to remove prototype from the .tar.gz? Thx Charlie Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Lintian error
[Please respect the CoC[0] and avoid sending me copies of the message] [0]http://www.debian.org/MailingLists/#codeofconduct Charliej wrote: Raphael Geissert wrote: Charliej wrote: With that said this is a quote from my upstream: Whee, is this something you could take care of at install, delete and then create a symlink. Or would this still violate this policy Would this be a viable solution? (I told upstream I would ask) I don't think this is a viable solution because the lintian error would still remain. You should symlink the file provided by the other package, if lintian still complains it is a bug in lintian then. I think one of the reasons he is hesitant is that the removal of prototype from the .tar.gz that he hosts would severely impact his M$ Windows users (he has a rather large M$ Windows community). Actually I could care less about M$ Windows users, but he does. As I see it to comply with Policy 4.13 prototype will have to be removed from upstreams .tar.gz.. Am I correct in this assumption? No, he doesn't need to remove his copy of prototype, it is _you_ who needs to prevent it from being installed in the package you build. This I can do, but to clarify your above statement does that mean that I remove it from the .orig.tar.gz or do I adjust the rules and or postinst to insure that it does not get installed? The latter :) hmm I think I may have answered my own question. Upstreams .tar.gz and the .orig.tar.gz must have the same md5sum correct? if so then that s/must/should, there are situations where one must repackage the tarball, but I don't believe this is the case. means the rules and or postinst have to be modified. Is my thinking here correct? Besides what I just clarified, yes. This brings me to the next point what if upstream refuses to remove prototype from the .tar.gz? Thx Charlie Cheers, Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Question about watch-file
Ben Finney wrote: Raphael Geissert [EMAIL PROTECTED] writes: Ben Finney wrote: Bug report: The file contents should be interpreted as UTF-8 encoding. Fixed. htmlentities() was messing the special characters instead of making them display properly. An improvement, but now it shows the same (wrong) output as described here: Yeah, that's another known issue. DEHS currently treats all its input data as ISO-8859-1 and converts it into UTF-8 without first checking if the input is already UTF-8. Will try to fix it next time I dig on DEHS' code. Ben Finney [EMAIL PROTECTED] writes: Possibly related: The link provided to view the watch file URL:http://dehs.alioth.debian.org/wwiz_detail.php?id=11448238type=watch leads to content served as UTF-8 but apparently not interpreting its source correctly: = # # Fetching these files for inclusion in a Debian source package is # automated in the Debian package with 'debian/rules get-orig-source', # as per Policy 3.8.0 §4.9. = The package's watch file is encoded as UTF-8, so apparently something is getting the encoding wrong somewhere along the line to producing the [document] at that URL. Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Question about watch-file
Russ Allbery wrote: Patrick Schoenfeld [EMAIL PROTECTED] writes: Well, the problem with your solution is that you silence an indicator for a problem anyway. Someone who looks at the lintian status of the package can do this from the outside and can decide to act upon. If you add a comment in a watch file then you have a comment in a hidden place for a lot of people who could potential fix the problem. They would need to look *into* that specific package, which is unlikely. This is a problem that can be easily fixed if desired by, for instance, having the Debian External Health Status system extract watch files containing only comments and put the text of the comments up on the DEHS web site. Is that a feature request? it sounds like one :) Implemented: http://dehs.alioth.debian.org/report.php?package=lojban-common Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DEHS bug report [was Re: Question about watch-file]
David L. Anselmi wrote: Ben Finney wrote: [...] DEHS already clearly shows packages for which the upstream version can't be checked; e.g. see URL:http://dehs.alioth.debian.org/maintainer.php?name=lojban-common. What does Tot Upstream Bugs: mean? E.g., for html2ps there are 10 bugs tagged upstream but DEHS reports 0. So it must mean something else. But what? Exactly that, it is supposed to display the number of bugs tagged upstream; but it tries to parse the html pages and sometimes it doesn't do it right. I've actually considered dropping that information, unless it is extracted at some other place and just incorporated in DEHS. Thanks, Dave Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Question about watch-file
David L. Anselmi wrote: Raphael Geissert wrote: Russ Allbery wrote: This is a problem that can be easily fixed if desired by, for instance, having the Debian External Health Status system extract watch files containing only comments and put the text of the comments up on the DEHS web site. Is that a feature request? it sounds like one :) Implemented: http://dehs.alioth.debian.org/report.php?package=lojban-common Not to complain but I thought the view link was sufficient. It is only displayed when no upstream version was found and uscan didn't complain at all. Under all the other circumstances (even if there are no comments of course :) it won't be displayed. Dave Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Question about watch-file
Ben Finney wrote: Bug report: The file contents should be interpreted as UTF-8 encoding. Apparently it's not: the output I see at that URL today is (in part): Fixed. htmlentities() was messing the special characters instead of making them display properly. Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: libzendframework-php
Andrea Giardina wrote: I meant on the report; there are copyright and licence issues in some of the files. I read your copyright notes in svn and i found all copyright problems in tests and demos but i deleted these directory in my first package release so I deleted also copyright notices. Now I'm going to package also test files so I'll restore some of that in copyright info. Then why doesn't the package version, package directory, and copyright file reflect those changes? Btw, that package naming schema is used by perl but not php. IMHO it would be better to use zend-framework or if you really insist: libphp-zenf-framework. For the naming I used the PHP Policy Draft 4.1 http://webapps-common.alioth.debian.org/draft-php/html/ch-php-libs.html#s-php-libs-naming This document is valid or outdated? If this is correct probably the best name is libzend-framework-php As you can see, that section has several 'XXX' in front of those self questions, which I think you can understand that it means that there's no current policy on php packages naming. Quickly greping apt-status there are: 13 packages using the libphp-foo naming convention 3 packages using the libfoo-php naming convention 0 packages using the php-pear-foo naming convention 0 packages using the libpear-foo-php naming convention And after all, that section is meant for PEAR packages, and the Zend Framework isn't. [1] And there's a patch that is needed for one the pdf generation tests which is in SVN. Uhm... the patch seems to be for the demo pdf s/tests/demo then :) And finally, don't forget to retitle the WNPP bug and set yourself as the owner, and consider joining the pkg-php group so you use the team's svn repo and co-maintain it with the others (at least Aleksey Zapparov was also interested in packaging it). Ok. Thank you for your help. Andrea Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: libzendframework-php
Andrea Giardina wrote: Please don't use such generic packaging and actually read what I already wrote. Of cource I read your code but I had a different approach. I chose to not package differents upstream's archives in the same deb source so I packaged _only_ the library. I meant on the report; there are copyright and licence issues in some of the files. Btw, that package naming schema is used by perl but not php. IMHO it would be better to use zend-framework or if you really insist: libphp-zenf-framework. Oh, and also consider shipping the extra documentation (either in the same or different package); and running the test suite[1] at build time would be even better JFTR. [1] And there's a patch that is needed for one the pdf generation tests which is in SVN. And finally, don't forget to retitle the WNPP bug and set yourself as the owner, and consider joining the pkg-php group so you use the team's svn repo and co-maintain it with the others (at least Aleksey Zapparov was also interested in packaging it). Best regards Andrea Giardina Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: libzendframework-php
Andrea Giardina wrote: ... http://mentors.debian.net/debian/pool/main/l/libzendframework-php/libzendframework-php_1.5.2-1.dsc I would be glad if someone uploaded this package for me. If it had been so simple I'd have uploaded the package several months ago. Please don't use such generic packaging and actually read what I already wrote. Kind regards Andrea Giardina -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: P4A - PHP For Applications
Andrea Giardina wrote: WEBSERVERS=apache apache-ssl apache2 the first two no longer exist. ok, right... why don't you just ship the file directly into apache2's config dir? because p4a it's a library (in your application you must require p4a/p4a.php) but it has also to be available from document_root (for icons, javascript, etc.). Maybe I must rename the package libphp-p4a? I think p4a package must be similar to cakephp package. So what? that still doesn't explain why you are symlinking it instead of just dropping it in apache2/conf.d debian/postrm: purge|remove) config files must not be removed on 'remove', only on purge. yes, I think this is correct, but if I call a simple remove I'll get a broken apache alias. What's the right way? You have to disable the configuration in prerm; I don't have your package around but makes me wonder if conf.d is the right place for your file. p4a/libraries/Zend/: please don't do that, package the zend framework separately so other packages and projects can use it, and then make the necessary changes in your application to use the shared version. Yes, I think so but I have a problem about that. The zend framework deb package it's already available on ubuntu repositories, so I think repackaging it is not a good idea. So, what's the right way? I must ask the collaboration of Utnubo team to port it to Debian? IIRC the utnubu team is dead; And whether Ubuntu has foo package and Debian not isn't a reason to ship the files in your package. You either find someone interested in packaging and maintaining the zend framework in Debian or you do it yourself. same as for fckeditor, jquery, and all the other stuff that isn't from p4a. uhm, fckeditor it's been patced to work with p4a so I think it must stay in p4a package. What kind of patches are those? have you talked to Debian's fckeditor maintainer? to upstream? To jquery I can try to use the deb package. It's actually a _must_. Thanks for your time. Andrea Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: lockrun
Noah Slater wrote: I am dropping my intended maintainership for the `lockrun` package. Details can be found here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=461915 What has upstream's response? If you really want the package in Debian but upstream doesn't want to integrate your patches without a good reason you could anyway package it, drop a few lines in debian/README.Debian and look for a sponsor. Thanks, Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: P4A - PHP For Applications
Andrea Giardina wrote:
...
Sorry, my bad.
I'm used to dealing with apache modules (which are managed via a
{en,dis}mod).
The behaviour of your post{inst,rm} are right.
uhm, fckeditor it's been patced to work with p4a so I think it must
stay in p4a package.
What kind of patches are those? have you talked to Debian's fckeditor
maintainer? to upstream?
The fckeditor packaged with p4a has been modified to specifs needs of
p4a, not to solve some problems or to add some features to fckeditor.
But what kind of changes are those?
And what files were changed?
Cheers
ag
Cheers,
--
Atomo64 - Raphael
Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: P4A - PHP For Applications
Andrea Giardina wrote: Hello to everybody, I'm searching a sponsor to upload p4a dep package on Debian. ... Could you please provide more information? and not just marketing-like information please. You can find the debian package and changes here: http://p4a.crealabsfoundation.org/deb/ Next time please provide the uri of the .dsc and _sign_ your package. debian/copyright: This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 2.1 of the License. looks like some part of it is missing debian/control: Like above, please improve the description debian/changelog: What about telling _what_ changes you made, instead of just telling 'fix on file foo'? Otherwise the changelog is not very useful. debian/debhelper.log: Should not be there debian/Makefile: debian/postinst: WEBSERVERS=apache apache-ssl apache2 the first two no longer exist. why don't you just ship the file directly into apache2's config dir? debian/postrm: purge|remove) config files must not be removed on 'remove', only on purge. p4a/libraries/Zend/: please don't do that, package the zend framework separately so other packages and projects can use it, and then make the necessary changes in your application to use the shared version. ... same as for fckeditor, jquery, and all the other stuff that isn't from p4a. There are some other issues but the above mentioned should be addressed first. Thanks for the help Andrea Giardina Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: --as-needed
Jeffrey Ratcliffe wrote:
...
that defaulted to 4.2.4-1. Why didn't I get 4.3? How do I force 4.3 in
the sid pbuilder?
did you update your chroot? gcc in sid is 4.3, in lenny is 4.2.
To force it, in your .pbuilderrc (I've never tried by using them directly on
the shell):
EXTRAPACKAGES=gcc-4.3 g++-4.3 ${EXTRAPACKAGES}
export CC=gcc-4.3 CXX=g++-4.3
And try again.
Cheers,
--
Atomo64 - Raphael
Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: lockrun
Noah Slater wrote: On Thu, May 29, 2008 at 07:04:30PM -0500, Raphael Geissert wrote: debian/copyright: By the way, where did you get this line from? Copyright: Copyright 2008, Stephen J. Friedl [EMAIL PROTECTED] I don't see any statement in the .c file that it is copyrighted. And as the file is in public domain, it may actually be possible that there's no copyright at all. License: PD [...] License: GAP [...] I am not an expert in this, but AFAIK those shouldn't be in separate lines. No, blank lines are allowed in the debian/copyright file. What I meant was that I don't know if you should place the extra lines for License: _after_ their usage. It's strange, nothing else. debian/patches/command-option.patch: Did you notice the patch is not clean? :) Binary files lockrun-1.orig/lockrun and lockrun-1.orig.new/lockrun differ debian/rules: else CC=cc endif ... My debian/rules doesn't have these lines. The one I downloaded from mentors.d.n to review _had_ those lines. rm -f lockrun lockrun.1 better written as $(RM) lockrun lockrun.1 make's default $(RM) already sets -f. rm -fr $(PACKAGE_DIRECTORY) Like above, but also set -r, e.g. $(RM) -r ... What is the value in doing this? As I understand it, this is only used by implicit rules in make and so isn't really useful for this scenario as it's not going to be overridden by anything. I tend to prefer the usage of $(RM). It is not a requirement, though. Your package still FTBFS twice in a row because of: sed -i s/@version@/$(PACKAGE_VERSION)/ lockrun.c not being reverted. I have fixed this now. You could simply revert the sed call in clean, rather than creating a second file, but... :) The package has been re-uploaded to mentors.debian.net. As George Danchev, did you notice that you built the source package as a native one? Thanks, Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: lockrun
Hi there, Noah Slater wrote: ... Would you mind taking another look at this package following these changes? debian/copyright: Debianized-By: Noah Slater [EMAIL PROTECTED] Debianized-Date: Sat, 08 Mar 2008 22:58:05 + You should read the wiki page again now, those have a different name now. License: PD In the public domain. License: GAP Copying and distribution of this package, with or without modification, are permitted in any medium without royalty provided the copyright notice and this notice are preserved. I am not an expert in this, but AFAIK those shouldn't be in separate lines. Example: Files: debian/* Copyright: Copyright 2008, Noah Slater [EMAIL PROTECTED] License: GAP Copying and distribution of this package, with or without modification, are permitted in any medium without royalty provided the copyright notice and this notice are preserved. debian/patches/command-option.patch: - else if ( STRMATCH(arg, -T) || STRMATCH(arg, --maxtime)) + else if ( STRMATCH(arg, -t) || STRMATCH(arg, --maxtime)) Is this really needed? I don't think you should be so intrusive. Unless, of course, upstream agrees to make that change and does it at upstream too. debian/rules: include /usr/share/cdbs/1/rules/buildcore.mk That line is useless, as including debhelper.mk already takes care of that. If you include that file before debhelper.mk, not all parts of debhelper are used, as cdbs doesn't know that you are later going to load debhelper.mk PACKAGE_NAME = lockrun ... Isn't the cdbs-provided var more than enough? or is it bogus? SOURCE_URI=http://www.unixwiz.net/tools/lockrun.c Have you considered using debian/copyright's Original-Source-Location: instead of hard-coding the uri twice? ;-) else CC=cc endif Didn't you say make already defines one by default: ? Just strip the 'else' and 'CC=cc' lines. rm -f lockrun lockrun.1 better written as $(RM) lockrun lockrun.1 make's default $(RM) already sets -f. rm -fr $(PACKAGE_DIRECTORY) Like above, but also set -r, e.g. $(RM) -r ... Your package still FTBFS twice in a row because of: sed -i s/@version@/$(PACKAGE_VERSION)/ lockrun.c not being reverted. Thanks, Please fix those issues. Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: php-ssh2, php-geoip (new packages)
Vincent Bernat wrote: The licence (2.02) is not suitable for main but for php itself. You should convince upstream to upgrade to 3.01 or to a more common license like GPL. Please don't request to move to GPL, as the packages would then need an exception because of a licence conflict. Thanks Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Easy way to retrieve build logs from buildd.d.o?
Frank S. Thomas wrote:
# Retrieve all build logs of the package hello.
$ getbuildlog.sh hello
# Retrieve mips and mipsel build logs of hello 2.2-{1,2}.
$ getbuildlog.sh hello '2\.2-.' 'mips(|el)'
Do you think this script would be a useful addition for devscripts?
Better ask at their ML and not here ;-)
Or: just file a bug report against devscripts
Cheers,
Cheers,
--
Atomo64 - Raphael
Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: lockrun
Neil Williams wrote: Just re-reading what you said: ... CC=cc endif That will cause troubles when using CC=gcc-4.3 dpkg-buildpackage (for example in i386, where 4.3 is not the default gcc). Something like CC=$(CC) should be used (the intention is to preserve the original $(CC), but of course that line won't work). Something like: ifneq ($(DEB_HOST_GNU_TYPE),$(DEB_BUILD_GNU_TYPE)) OURCC=$(DEB_HOST_GNU_TYPE)-$(CC) else OURCC=$(CC) endif $(OURCC) $(CFLAGS) lockrun.c -o lockrun Maybe someone with more knowledge of make could provide some feedback. Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: lockrun
Noah Slater wrote: On Fri, May 02, 2008 at 10:54:56AM -0500, Raphael Geissert wrote: Please upload your key to a public keyserver. Very strange, my key has been uploaded for months. [EMAIL PROTECTED]: ~ $ gpg --recv-key 0x8FBFCFBF gpg: requesting key 8FBFCFBF from hkp server subkeys.pgp.net gpg: key 61D50B88: public key Noah Slater [EMAIL PROTECTED] imported gpg: no ultimately trusted keys found gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) I had changed it around the time I sent the original email, maybe this effected it somehow, I'm not sure. Could you try again please? $ gpg --verbose --recv-key 0x8FBFCFBF gpg: requesting key 8FBFCFBF from hkp server pgp.mit.edu gpgkeys: key 8FBFCFBF not found on keyserver gpg: no valid OpenPGP data found. gpg: Total number processed: 0 $ gpg --verbose --keyserver hkp://subkeys.pgp.net --recv-key 0x8FBFCFBF gpg: requesting key 8FBFCFBF from hkp server subkeys.pgp.net gpg: armor header: Version: SKS 1.0.10 gpg: pub 4096R/61D50B88 2008-02-06 Noah Slater [EMAIL PROTECTED] gpg: key 61D50B88: invalid subkey binding gpg: using PGP trust model gpg: key 61D50B88: public key Noah Slater [EMAIL PROTECTED] imported gpg: signature packet without keyid ... strange :-/ ... I haven't checked your new package, waiting your reply to George Danchev's message. Btw, IANADD. Thanks, Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: lockrun
Neil Williams wrote: On Sun, 2008-05-25 at 16:37 -0500, Raphael Geissert wrote: $(OURCC) $(CFLAGS) lockrun.c -o lockrun OUR is the wrong prefix, CROSSCC is probably better. The thing is that it is not always used for cross compiling, so I don't think CROSSCC is the best name either. Seems like we are lacking ideas here :) ... You might want to set a default for $(CC) if using that: CC:=cc make already defines one by default: 8---8 $ cat cc.mk foo: echo $(CC) $ make -f cc.mk foo echo cc cc 8---8 Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#478387: glunarclock: bashism in debian/rules
[CC'ing -mentors] Hi Fabian, 2008/5/3 Fabian Greffrath [EMAIL PROTECTED]: Hi Raphael, thanks for the pointer. Would you mind sponsoring the upload? I'm afraid I can't sponsor your package, I am not a DD. But hopefully a potential sponsor in -mentors will read this message, review the package and upload it :). Btw, while Chris Lamby reviewed your package...: [Sat May 3 2008] [14:32:14] lamby Atomo64: Sorry, no. Btw, the copyright file on that package is out of date. It is missing references to some files in screen-exec/ as well as a number of .po files. So please also correct that :) http://mentors.debian.net/debian/pool/main/g/glunarclock/glunarclock_0.32.4-11.dsc Thank you! Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: lockrun
Noah Slater wrote:
...
- dget
http://mentors.debian.net/debian/pool/main/l/lockrun/lockrun_1-1.dsc
$ dget -x
http://mentors.debian.net/debian/pool/main/l/lockrun/lockrun_1-1.dsc
dget: retrieving
http://mentors.debian.net/debian/pool/main/l/lockrun/lockrun_1-1.dsc
% Total% Received % Xferd Average Speed TimeTime Time
Current
Dload Upload Total SpentLeft
Speed
100 1768 100 17680 0 5471 0 --:--:-- --:--:-- --:--:--
0
dget: retrieving
http://mentors.debian.net/debian/pool/main/l/lockrun/lockrun_1.orig.tar.gz
% Total% Received % Xferd Average Speed TimeTime Time
Current
Dload Upload Total SpentLeft
Speed
100 2897 100 28970 0 7315 0 --:--:-- --:--:-- --:--:--
253k
dget: retrieving
http://mentors.debian.net/debian/pool/main/l/lockrun/lockrun_1-1.diff.gz
% Total% Received % Xferd Average Speed TimeTime Time
Current
Dload Upload Total SpentLeft
Speed
100 2537 100 25370 0 2610 0 --:--:-- --:--:-- --:--:--
13146
gpg: Signature made Fri 02 May 2008 07:50:49 CDT using RSA key ID 8FBFCFBF
gpg: Can't check signature: public key not found
dpkg-source: extracting lockrun in lockrun-1
dpkg-source: info: unpacking lockrun_1.orig.tar.gz
dpkg-source: info: applying lockrun_1-1.diff.gz
$ gpg --recv-key 0x8FBFCFBF
gpg: requesting key 8FBFCFBF from hkp server pgp.mit.edu
gpgkeys: key 8FBFCFBF not found on keyserver
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
Please upload your key to a public keyserver.
Version: 1-1
I don't see any version number in the source code. Please use 0~MMDD
instead (where MMDD is the download date, or if possible, the
modification date of upstream's .c file), just in case upstream decides to
use version numbers at some point, if ever.
debian/rules:
gcc lockrun.c -o lockrun
Please don't do that, at least call gcc with CFLAGS:
gcc $(CFLAGS) lockrun.c -o lockrun
debian/control:
Depends: ${shlibs:Depends}
also use ${misc:Depends}
Btw, linda is no longer in the archive, you should get rid of the linda
overrides (lintian will complain if you keep them).
The package FTBFS twice in a row with the following message:
/usr/bin/make -f debian/rules reverse-config
make[1]: Entering directory `/tmp/lockrun-1'
make[1]: Nothing to be done for `reverse-config'.
make[1]: Leaving directory `/tmp/lockrun-1'
if [ reverse-patches = reverse-patches ]; then rm -f
debian/stamp-patched; fi
patches: debian/patches/command-option.patch
Trying reverse patch debian/patches/command-option.patch at level 1 ...
0 ... 2 ... failure.
make: *** [reverse-patches] Error 1
dpkg-buildpackage: failure: fakeroot debian/rules clean gave error exit
status 2
Please fix those issues.
I would be glad if someone uploaded this package for me.
Thanks,
Cheers,
--
Atomo64 - Raphael
Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: greenwich (updated and adopted package)
Hi David, David Paleino wrote: The package appears to be lintian clean; I've added a lintian override for You forgot that :) $ licensecheck src/greenwich.pl src/greenwich.pl: GPL (v2 or later) (with incorrect FSF address) $ grep Version LICENSE Version 2, June 1991 However, in debian/copyright you state that: Files: * Copyright: © 2003-2004, Gavin Brown [EMAIL PROTECTED] License: Artistic | GPL-1+ which appears incorrect, and the lintian override is incorrect anyway (the address should be updated). debian/control: Build-Depends-Indep: libgnome2-perl, imagemagick, menu Is the menu dependency really needed? and the imagemagick one? debian/control: debian/rules: You have an incorrect dependency on debhelper: ... dh_installmenu dh_gconf dh_lintian make: dh_lintian: Command not found make: *** [binary-indep] Error 127 pbuilder: Failed autobuilding of package ... dh_lintian was introduced in debhelper (6.0.7), but you have a Build-Depends: debhelper (= 5). Please fix the above mentioned issues (tough there might be more). Kindly David Paleino Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: greenwich (updated and adopted package)
David Paleino wrote: Updated package at usual URI: http://mentors.debian.net/debian/pool/main/g/greenwich/greenwich_0.8.2-4.dsc debian/rules: dh_installexamples ... dh_strip ... dh_shlibdeps you don't need them, do you? :) Btw, don't you think there's a better place for the contents of debian/README.Debian? Thanks, David Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: greenwich (updated and adopted package)
David Paleino wrote: On Fri, 02 May 2008 12:57:26 -0500, Raphael Geissert wrote: Btw, don't you think there's a better place for the contents of debian/README.Debian? I've not written that, it's from the old maintainer. I believe it could go in NEWS, but I'm open to any suggestion! NEWS is not for that kind of stuff. IMHO you could simply install it as usr/share/doc/greenwich/TODO (upstream doesn't ship one anyway, and it isn't a Debian TODO). Thanks for reviewing, David Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Call for help: please read (bashisms)
Paul Wise wrote: On Tue, Apr 29, 2008 at 8:27 AM, Raphael Geissert [EMAIL PROTECTED] wrote: I would like to request everybody to check for bashisms in the packages they: prepare, review, and upload. lintian is currently not able to check for bashisms in files other than maintainer scripts (debian/rules excluded), so it is not as easy as saying 'just check with the latest lintian'. How to do it: I've written a script called checkbashisms-in-package.sh[4] which can be used to easily check for bashisms in a .deb once checkbashisms is in $PATH. Please be aware that this script only looks for bashisms in some directories and not _everywhere_, which means there might be some bashisms left in other places (suggestions and patches welcome!). Any particular reason this hasn't been merged into lintian, since that is the right place for it? I don't know the exact details, but I remember there are some kind of limitations. For more information please refer to #253012 (CC'ing Russ so he can give his two cents). I've been working on making the checkbashisms code a .pm, adding some features lintian is very likely to require (e.g. adding custom checks, getting/setting a file content/cache). But I still need to fix some stuff. Russ: given the fact that most development of the checkbashisms code is done right now at devscripts, don't you think it would be better if lintian used devscript's .pm (when done)? updating the file from devscript's subversion every now and then doesn't sound hard at all (of course the devscripts maints/devs, or me, would ping you when changes are done). Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: php5-rar
Hi, [Really, please, _stop_ sending a copy of the message to my email address. Please _only_ send it to the mailing list.] Deepak Tripathi wrote: Hi , I am really sorry for spam but i have checked both license and i found that both is 3.01. Please check the following links http://pecl.php.net/package/rar But the one in the .tar.gz is 3.0, not 3.01, so no matter what the site says, the tarball says something different. Other than that, seems like something changed in-between: $ diff 3_0.txt 3_01.txt 2,3c2,3 The PHP License, version 3.0 Copyright (c) 1999 - 2006 The PHP Group. All rights reserved. --- The PHP License, version 3.01 Copyright (c) 1999 - 2008 The PHP Group. All rights reserved. 41,42c41,42 This product includes PHP, freely available from http://www.php.net/. --- This product includes PHP software, freely available from http://www.php.net/software/. 67c67 This product includes the Zend Engine, freely available at --- PHP includes the Zend Engine, freely available at AFAIR there were some other changes in 3.01. Thanks Deepak Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RFH: kgb FTBFS in arm (ignoring packed attribute because of unpacked non-POD field)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, After having several troubles getting kgb to be built and be functional on all the architectures, with my -8 upload I tried to make it work by using the packed attribute, as the code relies on the size of the structures (I've already contacted upstream, and even after a set of changes, bytes order in arm causes the built binary to break binary compatibility of the compressed files). Before uploading I asked somebody to attempt to build the package in arm, and that person said it did build. So I uploaded, but acc to [1] the assertion still fails (i.e. binary compatibility would break). I'm a bit puzzled by the warnings which are the only sign of why the assertion still fails: kgb_arch_posix_by_slawek.cpp: At global scope: kgb_arch_posix_by_slawek.cpp: In instantiation of 'HashtableCounter::HashElement': kgb_arch_posix_by_slawek.cpp:1124: instantiated from 'HashtableT::Hashtable(U32) [with T = Counter]' kgb_arch_posix_by_slawek.cpp:1366: instantiated from here kgb_arch_posix_by_slawek.cpp:1064: warning: ignoring packed attribute because of unpacked non-POD field 'Counter HashtableCounter::HashElement::c [15]' I've added some __attribute__((__packed__)) on the places where I though it still needed, and removed the ifeq (,$(findstring arm,$(DEB_BUILD_ARCH))) condition from debian/rules and tried to build on my i386, but I still get the warnings. I'm out of ideas, what am I missing? .dsc: http://i386-geomirror.debian.net/debian/pool/main/k/kgb/kgb_1.0b4-8.dsc [1]http://buildd.debian.org/fetch.cgi?pkg=kgb;ver=1.0b4-8;arch=arm;stamp=1209449475 TIA. Sincerely, - -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIF8VrYy49rUbZzloRAl1wAJ9vnO/IuqKx/OCmI2WqMKzDnXAr7QCfUAF0 7zLRM7c1ce3M6r9tTjwphio= =300F -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: php5-rar
Deepak Tripathi wrote: Yes it does contain the PHP 3.01 license but it is now acceptable. You were talking about php-rar, weren't you? Well, I was talking about php-rar too when I said it was released under the PHP licence version 3.0, not 3.01. Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Call for help: please read (bashisms)
Dear sponsors, mentors, maintainers,
Introduction:
Please be aware that although bash is currently the default /bin/sh there's a
release goal for Lenny to make dash the default /bin/sh[1].
This release goal affects every single /bin/sh script and every single
makefile not defining a different SHELL. Although they are 'affected',
everything is ok unless 'bashisms'[2] are used.
There is a tool called 'checkbashisms' which is shipped by the 'devscripts'
package, which is able to find several kind of bashisms in /bin/sh scripts
and makefiles (since version 2.0.26 and above when using -f, but version from
SVN[3] is recommended). This is the tool being used to generate reports for
the goal's mass bug filing.
With the recent improvements made to checkbashisms a lot of bashisms were
found in makefiles such as debian/rules. Based on the last archive wide check
there are about 312 (spread between 306 packages) bashisms in debian/rules.
Although the number of false positives when using checkbashisms on makefiles
is higher than the number of false positives when checking /bin/sh scripts,
there are still way too many bashisms around.
Request:
I would like to request everybody to check for bashisms in the packages they:
prepare, review, and upload.
lintian is currently not able to check for bashisms in files other than
maintainer scripts (debian/rules excluded), so it is not as easy as
saying 'just check with the latest lintian'.
How to do it:
I've written a script called checkbashisms-in-package.sh[4] which can be used
to easily check for bashisms in a .deb once checkbashisms is in $PATH.
Please be aware that this script only looks for bashisms in some directories
and not _everywhere_, which means there might be some bashisms left in other
places (suggestions and patches welcome!).
Examples:
Running checkbashisms-in-package.sh without any argument will display:
$ ./checkbashisms-in-package.sh
checkbashisms-in-package.sh foo.deb [bar.deb [...]]
Simple script to run checkbashisms on files inside a .deb, v0.0.1
Copyright 2008 Raphael Geissert [EMAIL PROTECTED]
To check for bashisms in a give .deb (or several .debs):
$ ./checkbashisms-in-package.sh kopete_3.5.9-1_i386.deb
Processing kopete_3.5.9-1_i386.deb...
possible bashism in ./usr/bin/kopete_latexconvert.sh line 225 (let ...):
let OPTIND=$OPTIND+1
done
To check for bashisms in debian/rules use:
$ checkbashisms -f -debian/rules
possible bashism in debian/rules line 740 (brace expansion):
builddir-$(TARGET) {configure,build,install}-$(TARGET)-stamp
*Note* that --force/-f is required for checkbashisms to check for bashisms in
makefiles.
I hope that this will make people more aware of bashisms and help the release
goal.
If you want more information about dash as /bin/sh, you can read:
http://lists.debian.org/debian-release/2008/01/msg00189.html
Fixing bashisms is pretty simple, you can get some ideas at:
https://wiki.ubuntu.com/DashAsBinSh
If the bashism you found is not there you can always ask in [EMAIL PROTECTED],
or
even here in -mentors.
Other ways to help include:
* Providing patches for the goal-dash bugs[5].
* Switching your /bin/sh to dash!
(apt-get install dash dpkg-reconfigure dash))
* Helping others to fix their bashisms
* Spread the word! bashisms are not allowed by policy.
[1]
http://release.debian.org/lenny/goals.txt
[2]
'bashism': in the context of the release goal a bashism is any kind of shell
feature not required by the Debian Policy section 10.4.
[3]
svn://svn.debian.org/svn/devscripts/trunk/scripts/checkbashisms.pl
[4]
http://git.debian.org/?p=users/atomo64-guest/misc-devscripts.git;a=blob_plain;f=checkbashisms-in-package.sh;hb=master
[5]
http://bugs.debian.org/cgi-bin/[EMAIL PROTECTED]tag=goal-dash
Thanks in advance.
Sincerely,
--
Atomo64 - Raphael
Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
signature.asc
Description: This is a digitally signed message part.
Re: RFS: php5-rar
Paul Wise wrote: On Sun, Apr 27, 2008 at 3:25 PM, Cyril Brulebois [EMAIL PROTECTED] wrote: On 27/04/2008, Deepak Tripathi wrote: It builds these binary packages: php5-rar - rar module for PHP 5 Ah, I forgot that point: is the algo the same as in unrar? unrar-free? You might need to adjust the section in the former case; and to adjust the description for the latter, to be more precise about what that extension can do. Looking at the upstream tarball, it seems that it embeds a non-free rar library. I hardly see the ftpmasters allowing this package to go in, as it embeds some non-free source code, and the extension is released under the PHP licence version _3.0_ which usually gets pseudo-auto-REJECTED. Please change the section to non-free. Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: php5-rar
[Please reply to the list, I _do_ read it] 2008/4/27 Deepak Tripathi [EMAIL PROTECTED]: Hi, Yes it does contain the PHP 3.01 license but it is now acceptable. check the php-apc package in mirror it also has PHP license 3.01. No it doesn't, it is released under the PHP licence version 3.0, not 3.01; the former it REJECTED the latter is also REJECTED unless the code was written by the PHP Team themselves. Thanks Deepak Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Test suites
Neil Williams wrote: make check Please use $(MAKE) instead of calling make directly. Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFC: kgb -- Archiver for .kgb files (doesn't work on non-32bits archs, changes made to address that issue)
Hi Laszlo, Laszlo Boszormenyi wrote: Hi Raphael, On Sat, 2008-04-05 at 20:19 -0600, Raphael Geissert wrote: This package is already in the archive, and I have DM upload rights for it. A few days ago I noticed this package doesn't work on non 32bits architectures so I've done a few changes to the package. The relevant part of changelog of the next upload is: * debian/test.sh: add a simple test suite to be run at the build target * debian/control: Build-Depend on gcc-multilib + Not building 64bits bins as the code is designed for 32bits archs The changes I made, as suggested by Goswin von Brederlow, until I get it to work on non 32bits archs were: adding a Build-Depends: gcc-multilib [amd64 kfreebsd-amd64 ppc64] calling gcc with -m32 Your package has some problems. It FTBFS on my x86_64 arch: dh_testdir g++ -Wall -fno-strict-aliasing -m32 -O3 -gstabs -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -o kgb kgb_arch_posix_by_slawek.cpp /usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.2.3/libstdc++.so when searching for -lstdc++ /usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.2.3/libstdc++.a when searching for -lstdc++ /usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.2.3/libstdc++.so when searching for -lstdc++ /usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.2.3/libstdc++.a when searching for -lstdc++ /usr/bin/ld: cannot find -lstdc++ collect2: ld returned 1 exit status make: *** [kgb] Error 1 I don't understand why this occurs. Can you provide me the full build log? 4.2.3/ is supposed to be a symlink to 4.2/, which is created by some unknown package (dpkg -S doesn't find anything, and looking at the postinst scripts of gcc-4.2* doesn't show anything useful). Removing -m32 from CFLAGS make it compile, but the test assert on U32 size. I have commented that out, but your package can't be build again: debian/rules clean debian/rules:36: warning: overriding commands for target `debian/stamp-patched' /usr/share/quilt/quilt.make:16: warning: ignoring old commands for target `debian/stamp-patched' QUILT_PATCHES=debian/patches quilt --quiltrc /dev/null pop -a -R || test $? = 2 Patch lfs.patch does not remove cleanly (refresh it or enforce with -f) make: *** [unpatch] Error 1 You first have to clean, then edit the source, and finally build. Otherwise quilt doesn't like the hand made changes. What does upstream say about 64 bits support? Upstream has been dead for a while. Though I haven't talked to the original author of the code. Thanks for taking a look at it. Regards, Laszlo/GCS Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFC: kgb -- Archiver for .kgb files (doesn't work on non-32bits archs, changes made to address that issue)
Raphael Geissert wrote: Hi Laszlo, Laszlo Boszormenyi wrote: Your package has some problems. It FTBFS on my x86_64 arch: dh_testdir g++ -Wall -fno-strict-aliasing -m32 -O3 -gstabs -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -o kgb kgb_arch_posix_by_slawek.cpp /usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.2.3/libstdc++.so when searching for -lstdc++ /usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.2.3/libstdc++.a when searching for -lstdc++ /usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.2.3/libstdc++.so when searching for -lstdc++ /usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.2.3/libstdc++.a when searching for -lstdc++ /usr/bin/ld: cannot find -lstdc++ collect2: ld returned 1 exit status make: *** [kgb] Error 1 I don't understand why this occurs. Can you provide me the full build log? 4.2.3/ is supposed to be a symlink to 4.2/, which is created by some unknown package (dpkg -S doesn't find anything, and looking at the postinst scripts of gcc-4.2* doesn't show anything useful). Adam Barratt provided me a full build log so I just noticed my silly mistake, it should depend on g++-multilib, not gcc-multilib. And thanks to an other build attempt by Ingo Saitz I confirmed it now works, as expected. Anyway, thanks for your time :) Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kgb -- Archiver for .kgb files (doesn't work on non-32bits archs, changes made to address that issue)
Joe Smith wrote: I am not a DD or DM, nor have I checked your actual packaging, but your explanations of the changes made sound reasonable sane. Obviously it would be nice for true 64 bit versions to eventually be built, but those changes sound like they should result in working 32 bit executables for all architectures. (Warning: I have no actual experence with that, this is just merely a comment that what you said sounds sane). HTH. Thanks for your comments. As no other issue found, now uploading the package. Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RFC: kgb -- Archiver for .kgb files (doesn't work on non-32bits archs, changes made to address that issue)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, This package is already in the archive, and I have DM upload rights for it. A few days ago I noticed this package doesn't work on non 32bits architectures so I've done a few changes to the package. The relevant part of changelog of the next upload is: * debian/test.sh: add a simple test suite to be run at the build target * debian/control: Build-Depend on gcc-multilib + Not building 64bits bins as the code is designed for 32bits archs The changes I made, as suggested by Goswin von Brederlow, until I get it to work on non 32bits archs were: adding a Build-Depends: gcc-multilib [amd64 kfreebsd-amd64 ppc64] calling gcc with -m32 So before I upload the package I'd like some feedback on the subject. Note: I added the simple test suite just to make sure the compiled binaries are ok, and prevent any similar problem (not knowing it doesn't work under non-32) in the future. 2nd note: the package is still Arch: any, as suggested by Goswin. The .dsc file can be found at: http://mentors.debian.net/debian/pool/main/k/kgb/kgb_1.0b4-6.dsc TIA. Kind regards, - -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFH+DM1Yy49rUbZzloRAo0gAJ4lXN1cn0yWNSouA0ViuC1u+72MbwCggLhZ LiyvA6Rp58pMk32UaRn9nXU= =3ToV -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Lintian: outdated-autotools-helper-file
Adam Borowski wrote: On Sun, Feb 10, 2008 at 01:40:07PM -0600, Luis Rodrigo Gallardo Cruz wrote: On Sun, Feb 10, 2008 at 08:27:52PM +0100, David Paleino wrote: E: gnome-translate source: outdated-autotools-helper-file config.guess 2003-07-02 What am I supposed to do? I believe that Build-Depending on autotools-dev | automake is not sufficient, as it seems that those files won't be updated anyways. Should I update them manually? This will introduce those changes in the .diff.gz outside the debian/ dir Build-Depend on autotools-dev, move the ofending files aside and put the new copy in thier place before running ./configure, copy the originals back at the end of clean. Or, instead of saving the originals, just delete them. dpkg-source ignores all deletions. Quoting the Debian Policy, section 4.9 Main building script: debian/rules[1] clean This must undo any effects that the build and binary targets may have had, except that it should leave alone any output files created in the parent directory by a run of a binary target. So according to the policy the clean target must put the original files back on place. [1]http://www.debian.org/doc/debian-policy/ch-source.html#s-debianrules Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: List of out-of-date packages on a given architecture.
Charles Plessy wrote: Dear Mentors, I was just wondering if there was a tool accsssible to non-DDs, that would allow to get the list of packages that have been uploaded more than 10 days ago, but never built on a given architecture. I am about to write an email to the buildd admin of mips and mipsel to ask for my packages to be built but before I would like to see if I am just unlucky, or if this is a more general dysfunctioning. What about checking on http://people.debian.org/~igloo/status.php?packages=PACKAGE ? Have a nice day, Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
