Re: RFS: lebiniou (new upstream version 3.14)
Hi Nicolas, On Fri, 2012-01-20 at 07:54 +0100, Nicolas Bourdaud wrote: On 20/01/2012 01:11, Olivier Girondel wrote: Dear mentors, I am looking for a sponsor for my package lebiniou. Package name: lebiniou Version : 3.14-1 Upstream Author : Olivier Girondel oliv...@biniou.info URL : http://biniou.net/ License : GPL2+ Section : graphics I have not done a full review, but I think your debian/control file miss some Build-Depends like libpulse-dev or zlibg1-dev... I wouldn't see why they should lack - it builds perfectly fine without. Reviewed, built, signed, uploaded. Thanks to Olivier for the work! -- Cheers, Kilian signature.asc Description: This is a digitally signed message part
Re: GREAT news: My First Debian Package ! - vpcs
On 01/20/2012 06:27 AM, Alexey Eromenko wrote: GREAT news: I'm ready to upload my first Debian package ! Link: (source + amd64 binary) http://forum.gns3.net/post14018.html = NAME vpcs - A light-weight network virtual pc simulator. DESCRIPTION The VPCS can simulate up to 9 PCs. You can ping/traceroute them, or ping/traceroute the other hosts/routers from the virtual PCs when you study the Cisco routers in the Dynamips. VPCS is not the traditional PC, it is just a program, and only few network commands can be used in it. But VPCS can give you a big hand when you study the Cisco devices in the Dynamips. VPCS can replace the routers or virtual machine boxes which are used as PCs in the Dynamips net‐ work. It can connect to VirtualBox or to GNS3 Network Simulator. = I have tested the final package on a Debian 6.0 AMD64 box. And it works ! It passes lintian with only few warnings; Suggestions welcome ! Where to upload it ? This package is very small, but it is needed for my GNS3 users and to get me involved with Debian. That's why it is important. I patched the makefile with quilt + made a man page. Erik: Could you sponsor me ? Hi , you can use mentord.debian.org to upload the package . Here are some useful links about mentors [0] [1]. To create a proper debian/copyright file please read DEP5 proposal [2] . These are lintian warnings which should be fixed: W: vpcs source: dh-make-template-in-source debian/vpcs.doc-base.EX W: vpcs source: format-3.0-but-debian-changes-patch W: vpcs source: out-of-date-standards-version 3.8.4 (current is 3.9.2) W: vpcs: new-package-should-close-itp-bug W: vpcs: copyright-refers-to-deprecated-bsd-license-file E: vpcs: helper-templates-in-copyright W: vpcs: description-synopsis-starts-with-article W: vpcs: extended-description-line-too-long I usually run lintian -Iivcm *.changes to get more verbose output . Best regards , Alex [0] http://wiki.debian.org/DebianMentorsFaq#Packaging [1] http://mentors.debian.net/qa [2] http://dep.debian.net/deps/dep5/ -- 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/4f19289c.5070...@biotec.tu-dresden.de
RFS: libqsi
Dear mentors, I am looking for a sponsor for my package libqsi. * Package name: libqsi Version : 6.0.3-1 Upstream Author : Quantum Scientific Imaging * URL : http://www.qsimaging.com * License : BSD Section : libs It builds those binary packages: libqsi-dev - Quantum Scientific Imaging (QSI) CCD Libraries. libqsi6- Quantum Scientific Imaging (QSI) CCD Libraries. To access further information about this package, please visit the following URL: http://mentors.debian.net/package/libqsi Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/libq/libqsi/libqsi_6.0.3-1.dsc I would be glad if someone uploaded this package for me. Kind regards, Jasem Mutlaq -- 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/CAE0bU5=qij41qh4f9a2hxjasjuh-55myx8p5hnsw+h4uhk3...@mail.gmail.com
RFS: indi-qsi
Dear mentors, I am looking for a sponsor for my package indi-qsi. * Package name: indi-qsi Version : 0.4-1 Upstream Author : [fill in name and email of upstream] * URL : [fill in URL of upstreams web site] * License : [fill in] Section : science It builds those binary packages: indi-qsi - INDI QSI CCD Driver. To access further information about this package, please visit the following URL: http://mentors.debian.net/package/indi-qsi Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/i/indi-qsi/indi-qsi_0.4-1.dsc I would be glad if someone uploaded this package for me. Kind regards, Jasem Mutlaq -- 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/cae0bu5kwo3-3twa_c_qtelr5qedasstw1bi061-wq4ooh8f...@mail.gmail.com
Re: RFS: suckless-tools 39-1
Hi, thanks. Now i just need anybody who uploads it :) Regards, Michael -- 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/4f192d08.30...@stummi.org
Re: proposed new pseudo-package 'debian-mentors' for handling sponsoring requests
On Tue, Jan 17, 2012 at 10:59:14PM +0100, Ansgar Burchardt wrote: SUMMARY === We plan to ask for the creation of a new pseudo-package debian-mentors or mentors.debian.org [3] (contact: debian-mentors@lists.debian.org) in Debian's bug tracking system (the name is still subject to change). A workflow for handling sponsoring requests is proposed below. It is based on an earlier discussion on the debian-mentors list[1]. I would like to add that FreeBSD is successfully employing a very similar mechanism. Everyone can send patches to the ports tree (=~ Debian packages) to the bug tracker as problem reports (=~ bugs). The natural solution to these reports is that a committer (=~ Debian Developer) commits (=~ uploads) the patch (=~ package) and closes the report with a message most often looking like Thanks. Committed.. While I do agree that the Debian bts is difficult for new comers at times, it is also very convenient for long term usage. I would personally benefit from the implementation of this proposal. Helmut -- 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/20120120083939.ga26...@alf.mars
Re: GREAT news: My First Debian Package ! - vpcs
These are lintian warnings which should be fixed: W: vpcs source: dh-make-template-in-source debian/vpcs.doc-base.EX W: vpcs source: format-3.0-but-debian-changes-patch W: vpcs source: out-of-date-standards-version 3.8.4 (current is 3.9.2) W: vpcs: new-package-should-close-itp-bug W: vpcs: copyright-refers-to-deprecated-bsd-license-file E: vpcs: helper-templates-in-copyright W: vpcs: description-synopsis-starts-with-article W: vpcs: extended-description-line-too-long I usually run lintian -Iivcm *.changes to get more verbose output . Standard lintian gives me no errors, but only few warnings: user@xrig:/vm/tmp/vpcs-0.3$ lintian ../vpcs_0.3-1_amd64.deb W: vpcs: new-package-should-close-itp-bug W: vpcs: copyright-refers-to-deprecated-bsd-license-file W: vpcs: extended-description-line-too-long Why so huge diff ? -- -Alexey Eromenko Technologov -- 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/CAOJ6w=HppDry=zzs+7yex8ctrw3yxanvq3qv1d5drb5dv4z...@mail.gmail.com
Re: GREAT news: My First Debian Package ! - vpcs
On Fri, Jan 20, 2012 at 5:37 PM, Alexey Eromenko wrote: Standard lintian gives me no errors, but only few warnings: ... Why so huge diff ? pabs@chianamo ~ $ cat ~/.lintianrc info=yes display-info=yes display-experimental=yes pedantic=yes show-overrides=yes color=auto -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAKTje6Fuy9TLGYK2uGyWL-9YXOLu1e-6TY=yz5tJavT7hBEc=q...@mail.gmail.com
Re: GREAT news: My First Debian Package ! - vpcs
pabs@chianamo ~ $ cat ~/.lintianrc info=yes display-info=yes display-experimental=yes pedantic=yes show-overrides=yes color=auto I have copied your file, but now I get this: user@xrig:/vm/tmp/vpcs-0.3$ lintian ../vpcs_0.3-1_amd64.deb syntax error in configuration file: info=yes -- -Alexey Eromenko Technologov -- 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/CAOJ6w=gxt5hnnfpbmzc2co-83-4pbkrzp4krfg5knaz8ffp...@mail.gmail.com
RFS: tk-table
Dear mentors, I am looking for a sponsor for my package tk-table. * Package name: tk-table Version : 2.10-1 Upstream Author : Jeffrey Hobbs j...@hobbs.org * URL : http://tktable.sourceforge.net * License : BSD Section : interpreters It builds those binary packages: tk-table - Table extension for Tcl/Tk To access further information about this package, please visit the following URL: http://mentors.debian.net/package/tk-table Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/t/tk-table/tk-table_2.10-1.dsc This is a kind of adoption of the package tktable2.9 (binary package libtktable2.9) which was orphaned since 2008 and removed from unstable in Feb 2011. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465957. It is needed in order to bring the astronomical package saods9 back into Debian (ITP: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655648). I put tk-table under the maintenance of Debian-Science. I would be glad if someone uploaded this package for me. I would also very appreciate a review without an upload since I am not familar with tcl/tk and therefore I am unsure about whether the package fits into the Debian tcl/tk subsystem. Best regards, Ole Streicher -- 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/4f19371c.5050...@liska.ath.cx
Re: GREAT news: My First Debian Package ! - vpcs
On Fri, Jan 20, 2012 at 5:48 PM, Alexey Eromenko wrote: I have copied your file, but now I get this: user@xrig:/vm/tmp/vpcs-0.3$ lintian ../vpcs_0.3-1_amd64.deb syntax error in configuration file: info=yes I get no such error, hmmm. Also, you should run lintian on the .changes file so that both the source package and all binary packages are checked. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caktje6hrzfz9sugydtngujj5h-_9ceek3itb8z_qqwrxlvp...@mail.gmail.com
Re: GREAT news: My First Debian Package ! - vpcs
On 01/20/2012 10:48 AM, Alexey Eromenko wrote: pabs@chianamo ~ $ cat ~/.lintianrc info=yes display-info=yes display-experimental=yes pedantic=yes show-overrides=yes color=auto I have copied your file, but now I get this: user@xrig:/vm/tmp/vpcs-0.3$ lintian ../vpcs_0.3-1_amd64.deb syntax error in configuration file: info=yes It seems to me that your lintian is rather old . IMO it is always better to use lintian from sid . Best regards , Alex -- 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/4f193b18.9030...@biotec.tu-dresden.de
Re: GREAT news: My First Debian Package ! - vpcs
Hi! Am 20.01.2012 10:59, schrieb Alex Mestiashvili: It seems to me that your lintian is rather old . IMO it is always better to use lintian from sid . ... or just the one from backports.debian.org Best regards, Alexander -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f193d9d.9050...@debian.org
Re: RFS: lebiniou (new upstream version 3.14)
Hi all, On 20/01/2012 09:35, Kilian Krause wrote: Hi Nicolas, On Fri, 2012-01-20 at 07:54 +0100, Nicolas Bourdaud wrote: I have not done a full review, but I think your debian/control file miss some Build-Depends like libpulse-dev or zlibg1-dev... I wouldn't see why they should lack - it builds perfectly fine without. It compiles because they are indirect dependencies of the other packages listed in Build-Depends (for example libpulse-dev is pulled with libsdl1.2-dev). But what would happen if tomorrow, those are updated and drop one these dev dependencies: for example, imagine SDL package stops shipping the pulseaudio backend. In this case the libsdl1.2-dev will likely drop libpulse-dev (because it is needed it only for compiling with the static library). That day, your package can not be rebuilded in its state. Normally, as far I know, Build-Depends should list all packages that are necessary for compilation, and zlib1g-dev, libpulse-dev (among others) are needed for compilation of the package. Also having Build-Depends informs that something has to be done in case of an API change of the library dependence (without ABI break). Cheers, Nicolas signature.asc Description: OpenPGP digital signature
Re: Making mentors.debian.net a .org
On Fri, Jan 20, 2012 at 01:07:02AM -0500, Michael Gilbert wrote: On Thu, Jan 19, 2012 at 6:47 AM, Arno Töll wrote: That's the plan, but again: tracking sponsor requests as bugs, and integrate mentors.debian.net into Debian are unrelated problems. Any proposal can be implemented without touching the status-quo of the other. They are intimately related as we need a pseudo-package to even begin the bug-based workflow, and that needs to be a .org. So the official domain is required first. I fail to see any connection between the domain name and pseudo-package, unless you somehow want to name it debian-mentors.XXX.org rather than just debian-mentors. This reeks of openoffice.org as the package name. -- 1KB // Yo momma uses IPv4! signature.asc Description: Digital signature
Re: RFR: eegdev
Hi, On Fri, Jan 20, 2012 at 12:33:44AM +0100, Nicolas Bourdaud wrote: I would be glad if someone review this package. The packaging looks pretty good. There are a few things that you could take a look at. The comments at the top of debian/rules should go away -- it is no longer a sample rules file. When I build the package on my i386 laptop (up-to-date wheezy) the build hangs in one of the tests until I kill it (reproduced every time): make[4]: Entering directory `/home/michael/debian/cnbi/eegdev/tests' PASS: verify-cast.sh PASS: verifysplit PASS: syseegfile Testing biosemi with float data type Testing biosemi with double data type PASS: testfakeact2.sh error caught (97) Address family not supported by protocol ^C When I build the package with 'nocheck' it builds. I noticed the eegdev-plugins-free binary package name and that the build uses this configuration Core library build : yes -- EEG file support : yes Biosemi support : yes gTec support : no Neurosky support : no TobiIA support : yes Do the two missing plugins depend on something that is not in Debian? Or that is non-free? It looks like (at least some of) the code for these plugins is shipped with the package. I didn't see any copyright notice that would indicate 3rd-party code. It might make sense to put some information about the missing plugins into README.Debian or README.source, depending on why they are missing and whether there are plans to add them later on. I have updated the information on this package in the Debian Science taskfiles. Cheers, Michael -- Michael Hanke http://mih.voxindeserto.de -- 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/20120120122027.GA29830@meiner
Re: RFS: git2cl
Hi Paul, My apologies, I didn't mean to be rude for not replyng - I only noticed this email of yours just now. Sorry for missing it. On Sat, 14 Jan 2012 11:56:55 Paul Wise wrote: On Wed, Dec 7, 2011 at 11:47 AM, Dmitry Smirnov wrote: However you failed to clearly articulate the requirements you imposed on me before taking action, neither were you willing to discuss the possible solutions. I suppose that was unfair of me, my apologies. Thank you. In retrospect I would expect you'd say something like I can only accept the package if you do ...something... or if we discuss the alternative solutions like the one I've chosen (to drop the generated html and only package plain text source). I'm sorry for reacting too emotionally. I reckon we can always talk first, before engaging the punishment actions. :) How about the following compromise: File a bug (preferably with patch) on asciidoc about using the current time instead of the modification time of the input file. This wouldn't be a problem with responsive upstream. I already tried to contact him but he is not answering to emails. This was also confirmed by other people who tried to reach him. But wouldn't you agree that generated HTML file with few paragraphs of plain text is unnecessary duplication which we can safely drop? Ping the asciidoc uploader (formorer) about fixing #637006. Sure but I'm not too concerned about this. I think two issues I have are 1. Changing the meaning of document by updating a date which will reads like if upstream updated something in the document on the date of packaging. 2. The amount of time one would spend for relatively simple and straightforward packaging. Perfectionism is close to my heart. I'd like to ship the package as perfect as I can, and I'm not against regeneration of this file (without altering date). But how much time and effort one can afford in order to regenerate single HTML file? It may simply not worth the effort and I suspect that's might be a reasonable consideration. Moreover, if you're responsible for more than one package and other packages have more serious issues to resolve, wouldn't you close your eyes on this minor problem and try to address something more important first? In the end it may be a prioritising issue. Workaround this bug by running date -r on the source file and sed in debian/rules to replace the date after the HTML file is generated. As a last resort I can do that. Would you prefer this solution to dropping the file as I did in my commit on 7 of December? http://anonscm.debian.org/gitweb/?p=users/onlyjob-guest/git2cl.git Then I upload the package. That will be nice, thank you very much, I'll be looking towards your reply. Cheers, Dmitry. signature.asc Description: This is a digitally signed message part.
Re: RFS: git2cl
* Dmitry Smirnov only...@member.fsf.org, 2012-01-20, 23:49: But how much time and effort one can afford in order to regenerate single HTML file? Surely it wouldn't cost you more time than arguing about the issue takes. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120120132708.ga7...@jwilk.net
Re: RFR: eegdev
Hi, On 20/01/2012 13:20, Michael Hanke wrote: The comments at the top of debian/rules should go away -- it is no longer a sample rules file. Done When I build the package on my i386 laptop (up-to-date wheezy) the build hangs in one of the tests until I kill it (reproduced every time): make[4]: Entering directory `/home/michael/debian/cnbi/eegdev/tests' PASS: verify-cast.sh PASS: verifysplit PASS: syseegfile Testing biosemi with float data type Testing biosemi with double data type PASS: testfakeact2.sh error caught (97) Address family not supported by protocol ^C When I build the package with 'nocheck' it builds. It is the unit test of one particular plugin that fails. I think it is not related to the architecture but it more a bug in the plugin and its unit test which, if I am right, does not handle IPv6 correctly. To confirm this, could you tell me what localhost refers to in your configuration? If it is a IPv6 address, my theory is likely to be the right one! :-) I noticed the eegdev-plugins-free binary package name and that the build uses this configuration Core library build : yes -- EEG file support : yes Biosemi support : yes gTec support : no Neurosky support : no TobiIA support : yes Do the two missing plugins depend on something that is not in Debian? Or that is non-free? It looks like (at least some of) the code for these plugins is shipped with the package. I didn't see any copyright notice that would indicate 3rd-party code. Neurosky device corresponds to experimental hardware that the manufacturer has given us to test (for those who know, it is not the EEG device that Neurosky sells). I kept the code because it can be an example for writing the plugin of another bluetooth based acquisition device. The other one (gTec) is the plugin for hardware (g.USBAmp) which depends on a library that cannot be distributed, not even as non-free. The source code is provided because those who have bought the library (a kind of SDK) can compile it and use it. It might make sense to put some information about the missing plugins into README.Debian or README.source, depending on why they are missing and whether there are plans to add them later on. Good point, I will write a README that describes this. README.Debian or README.source, which one should I use? (what is the policy?) I have updated the information on this package in the Debian Science taskfiles. Thanks I will update all of this, Cheers, Nicolas signature.asc Description: OpenPGP digital signature
Re: RFS: libqsi
Hi, Jasem Mutlaq mutla...@ikarustech.com writes: * Package name: libqsi Version : 6.0.3-1 Upstream Author : Quantum Scientific Imaging * URL : http://www.qsimaging.com * License : BSD Section : libs dget -x http://mentors.debian.net/debian/pool/main/libq/libqsi/libqsi_6.0.3-1.dsc There is no license included in the upstream tarball, only a copyright notice and a disclaimer. Where did you get the information that it is licensed under a BSD license? You do not need to include 'debian/tmp' in d/*.install. dh_install looks there by default. The package description is a bit short. There seems to be no source for the PDF file in the doc/ directory. Regards, Ansgar -- 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/87vco65tw3@deep-thought.43-1.org
Re: RFS: indi-qsi
Jasem Mutlaq mutla...@ikarustech.com writes: indi-qsi - INDI QSI CCD Driver. To access further information about this package, please visit the following URL: http://mentors.debian.net/package/indi-qsi Alternatively, one can download the package with dget using this command: -- 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/87r4yu5trv@deep-thought.43-1.org
Re: RFS: tk-table
[I am not a DD, a DM, an experienced packager of any sort, or able to provide any review of this package at all. I'm just following the debian-mentors list. -- J] On Fri, Jan 20, 2012 at 4:42 AM, Ole Streicher debian-de...@liska.ath.cx wrote: I am looking for a sponsor for my package tk-table. * Package name : tk-table Version : 2.10-1 Upstream Author : Jeffrey Hobbs j...@hobbs.org * URL : http://tktable.sourceforge.net * License : BSD Section : interpreters It builds those binary packages: tk-table - Table extension for Tcl/Tk This is a kind of adoption of the package tktable2.9 (binary package libtktable2.9) which was orphaned since 2008 and removed from unstable in Feb 2011. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465957. It is needed in order to bring the astronomical package saods9 back into Debian (ITP: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655648). I put tk-table under the maintenance of Debian-Science. I would be glad if someone uploaded this package for me. I would also very appreciate a review without an upload since I am not familar with tcl/tk and therefore I am unsure about whether the package fits into the Debian tcl/tk subsystem. I would suggest that a more obvious and natural fit for a maintenance home for this package would be: Debian Tcl/Tk Packagers - mailto:pkg-tcltk-de...@lists.alioth.debian.org QA Page - http://qa.debian.org/developer.php?login=pkg-tcltk-devel%40lists.alioth.debian.org Mail Archive - http://lists.alioth.debian.org/pipermail/pkg-tcltk-devel/ Just from the short description, it sounds to me like tk-table is more of a general purpose and utility sort of Tk package, and not something of interest uniquely to someone doing science type work; just from their name, Debian Tcl/Tk Packagers sound like the sort of group interested in general purpose and utility Tk packages. Also, the Tcl/Tk Packagers would be the obvious source of information on how to fit this package into the already existing Tcl/Tk ecosystem within Debian. (They might even have a language-specific policy and packaging guide; I haven't looked.) FWIW, I found this by searching the Debian package archive (http://www.debian.org/distrib/packages) for package names including tk, and seeing who the maintainers of those packages were, in case you wanted to know how I found this. I had not previously known about this group within Debian. Thanks for your time. Hope this is of some use, interest. Good luck with getting this package and the one depending on it into Debian. Be well. Joseph -- 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/CAC58tq-PZ2aYdHvLfr0gKgB19Vj1TeZRF23XcmEZ1mre...@mail.gmail.com
Re: RFS: indi-qsi
Hi, Jasem Mutlaq mutla...@ikarustech.com writes: indi-qsi - INDI QSI CCD Driver. dget -x http://mentors.debian.net/debian/pool/main/i/indi-qsi/indi-qsi_0.4-1.dsc Please do use dpkg-shlibdps for library dependencies instead of listing them in d/control by hand. The package description is also very short. I cannot say what it is used for by just reading it. Please document cmake_modules/* in the copyright information. Please include a reference to the full text of the LGPL license in /usr/share/common-licenses. Documenting which versions of the LGPL the program is licensed under would also be good. Regards, Ansgar -- 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/87k44m5td2@deep-thought.43-1.org
Re: RFS: libqsi
There is no license included in the upstream tarball, only a copyright notice and a disclaimer. Where did you get the information that it is licensed under a BSD license? I contacted the company to get explicit BSD-2 clause in the COPYING file. Awaiting their reply. You do not need to include 'debian/tmp' in d/*.install. dh_install looks there by default. Ok, will correct that. The package description is a bit short. Ok, will expand the description. There seems to be no source for the PDF file in the doc/ directory. Is this recommended or mandatory? Your help is appreciated! -- Best Regards, Jasem Mutlaq -- 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/cae0bu5noz6_rc-jg9b4nukhytsq9lqrdewjeigzl5qod46p...@mail.gmail.com
Re: RFS: tk-table
Joseph R. Justice jayare...@gmail.com writes: I would suggest that a more obvious and natural fit for a maintenance home for this package would be: Debian Tcl/Tk Packagers - mailto:pkg-tcltk-de...@lists.alioth.debian.org QA Page - http://qa.debian.org/developer.php?login=pkg-tcltk-devel%40lists.alioth.debian.org I forwarded my review request to the tcl-tk mailing list. If they ask me to move the whole stuff to debian-tcltk, I'll do that. However, since I am not a tcl/tk developer at all, I would not like getting a member of this packager team. Best Ole -- 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/ytzpqeeietl@news.ole.ath.cx
Re: RFS: python-x2go
Hi Jakub, thanks a lot for taking your time on this!!! On Fr 20 Jan 2012 01:06:47 CET Jakub Wilk wrote: (I don't intend to sponsor this package.) * Mike Gabriel mike.gabr...@das-netzwerkteam.de, 2012-01-19, 23:41: dget -x http://mentors.debian.net/debian/pool/main/p/python-x2go/python-x2go_0.1.1.8-4.dsc [...] I will take care as best as I can about all points given. Then I will reply to your mail and maybe someone else might want to sponsor the package. Thanks so much, Mike -- DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419 GnuPG Key ID 0xB588399B mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpMkR5rWO8ew.pgp Description: Digitale PGP-Unterschrift
Re: Making mentors.debian.net a .org (was: proposed new pseudo-package 'debian-mentors' for handling sponsoring requests)
Jan Hauke Rahm wrote: On Fri, Jan 20, 2012 at 01:07:02AM -0500, Michael Gilbert wrote: Like I've said before, this is not about eliminating ambiguity. Every single word in every single language is ambiguous. It's simply unavoidable. It's about choosing the word with the right context for the goals of the service. That's the primary goal, yes, absolutely. Though the past shows clearly how un ambiguous terms served us with confusion, may they have been as appropriate as possible (see the DM != DM != DD != maintainer debacle). My point being, we should look for a perfectly describing term, and then make sure it's not used already in a different (or worse: a similar) context. I can see the appeal of sorting out the confusion, but whatever the new .debian.org subdomain and BTS pseudo-package get called, aren't they still going to be tied to a debian-mentors mail archive? This should be a place for contributors to come together to collaborate and make their work better before pestering a DD about it; with minimal experienced intervention (mentoring). Well, I'm not a native english speaker, though what you're describing doesn't sound like mentoring but rather training. I suspect there's a misunderstanding here; the way I read it is that Michael would like the new service to advertise itself as a place where contributors assist one another *without* experienced developers needing to train them, because that's how debian-mentors currently works; despite the name, it's a place for finding an upload sponsor, not a mentor. To mentor, as I understand it, is an action someone skilled performs in order to teach or train another person. As you said, the service provided here is for those who still learn, who are being mentored, i.e. it's actually not for mentoring. Now, I'm not sure training is the right term, as it suggests (to me) the service is something like a playground, but I can be mistaken. A native speaker should probably say something here. Are you perhaps thinking of trainers (en_US sneakers)? -- JBR - and today's single word in West Greenlandic is: Allattuivvissaaliqisarsimaqaanga I was really short of notebooks -- 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/20120120151146.ga11...@xibalba.demon.co.uk
Re: RFS: acetoneiso (same upstream, closing 2 debian bugs)
Hi, Nick Andrik nick.and...@gmail.com writes: http://mentors.debian.net/debian/pool/main/a/acetoneiso/acetoneiso_2.3-2.dsc debian/control: - libqt4-dev ( 4:4.7.0~beta2) | libqtwebkit-dev, + lbqtwebkit4, This should have given you an error when building the package as dpkg-buildpackage checks the build dependencies by default. You also need to build-depend on the -dev package (as before); the binary package should pick up the new package name for libqtwebkit automatically via the dpkg-shlibdeps mechanism. Regards, Ansgar -- 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/87bopy5r2y@deep-thought.43-1.org
Re: RFS: libqsi
Hi, Jasem Mutlaq mutla...@ikarustech.com writes: There seems to be no source for the PDF file in the doc/ directory. Is this recommended or mandatory? Source needs to be present for everything part of Debian. That includes documentation and files that are not shipped in the binary packages. If you cannot provide the source, you need to repack to upstream tarball and remove the sourceless files. Regads, Ansgar -- 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/877h0m5qpt@deep-thought.43-1.org
Re: How to warn the user with debconf
Il 16/01/2012 00:19, Martin Eberhard Schauer ha scritto: Hi Stefano, in my postinst script I need to warn the user in case the script was unable to remove a non empty directory. How can I do this and have a lintian clean package? I thought to use a debconf note but lintian issues possible-debconf-note-abuse warning. TIA Stefano please have a look at the Developer's Reference (1). Why not issue the error message when the error occurs? The shortest way to a problem solution for you way may be an informal mail to debian-l10n-english asking for a review of your debconf templates and package description. Of course you can upload your package as is, but this slows down the process. »Bubulle« will find your new debconf template and propose a more formal process lasting up to three weeks. Cheers, Martin 1: http://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html#s6.5.1 Thanks for the suggestions. Bye Stefano -- Stefano Canepa aka sc: s...@linux.it - http://www.stefanocanepa.it Three great virtues of a programmer: laziness, impatience and hubris. Le tre grandi virtù di un programmatore: pigrizia, impazienza e arroganza. (Larry Wall) -- 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/4f199158.5020...@linux.it
Re: RFS: libqsi
Source needs to be present for everything part of Debian. That includes documentation and files that are not shipped in the binary packages. If you cannot provide the source, you need to repack to upstream tarball and remove the sourceless files. Ok, I got a confirmation from QSI that the source code for libqsi is proprietary. They grant you the right to distribute source and binary forms of the library, but not to modify the source itself. Can this be added to Debian 'non-free' ? Regards, Jasem -- 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/cae0bu5nmq2wpotnf5v59cidzbo4+e8xuarhfi0738z-kmzj...@mail.gmail.com
Re: RFS: libpam-abl , bug fix , package is already in Debian
* Alex Mestiashvili a...@biotec.tu-dresden.de, 2012-01-16, 20:16: http://mentors.debian.net/debian/pool/main/libp/libpam-abl/libpam-abl_0.4.2-2.dsc The changelog says debian/control added DM-Upload-Allowed, but 0.4.2-1 had already this field. What do you mean by other architectures (in the patch header)? Hi Jakub , It failed to built on many archs - https://buildd.debian.org/status/package.php?p=libpam-abl With this patch it suppose to be better , but I agree that the description sounds ambiguous. I've uploaded a new version with the corrected description . Assuming that the patch header was meant to follow DEP-3, then please note that the Description field is supposed to be like Description in debian/control: there are two parts, short and long one (though the latter is optional). But let's go to more important things. This: printf(PAD %s (%lu)\n, buf, (unsigned long)data.size / sizeof(time_t)); is surely better than: printf(PAD %s (%ld)\n, buf, (long int)data.size / sizeof(time_t)); (which you had in the previous version). But to be pedantically correct, it really should be: printf(PAD %s (%zu)\n, buf, (size_t)data.size / sizeof(time_t)); I also modified changelog such a way that line debian/control added DM-Upload-Allowed appears in the correct section , but I have some doubts if it is ok to edit old changelog sections . That's fine with me. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120120172858.ga8...@jwilk.net
Re: RFS: tk-table
Hello,
On Fri, 20 Jan 2012 10:42:52 +0100
Ole Streicher debian-de...@liska.ath.cx wrote:
http://mentors.debian.net/debian/pool/main/t/tk-table/tk-table_2.10-1.dsc
Depends: ${tcl:Depends}, ${tk:Depends}, ${misc:Depends},
${shlibs:Depends}
For that to work properly, you have to call tcltk-depends during
package build process.
Tcl manpages need to be installed within section 3tcl or 3tk, not 3.
Also, why compat level 5? If you used 7 or later, dh_installchangelogs
would automagically pick the upstream-supplied changelog up.
--
WBR, Andrew
signature.asc
Description: PGP signature
Re: RFS: tk-table
Andrew Shadura bugzi...@tut.by writes:
Depends: ${tcl:Depends}, ${tk:Depends}, ${misc:Depends},
${shlibs:Depends}
For that to work properly, you have to call tcltk-depends during
package build process.
How do I do that?
Tcl manpages need to be installed within section 3tcl or 3tk, not 3.
OK, I'll change that.
Also, why compat level 5? If you used 7 or later, dh_installchangelogs
would automagically pick the upstream-supplied changelog up.
I just copied the template from another package. I'll change that.
Best
Ole
--
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/87hazqs0op@news.ole.ath.cx
Re: proposed new pseudo-package 'debian-mentors' for handling sponsoring requests
Michael Gilbert michael.s.gilb...@gmail.com writes: On Thu, Jan 19, 2012 at 1:07 PM, Russ Allbery wrote: For the main archive, the NEW check I think is best thought of as a spot check to ensure maintainers are doing their jobs. The real responsibility of not uploading non-redistributable material lies with the Debian project members with upload rights. ftpmaster is just checking for mistakes (at the point at which most mistakes are made). The difference for mentors is that the uploaders are not (yet) Debian project members and are not guaranteed to be trained in our licensing policies, and have not agreed to follow our rules. So, I think these concerns can be abated by thinking of mentors more of an alternative NEW queue for newcomers; rather than as an alternative package pool, which it's not (binary packages are not served, and files hosted are not widely distributed since most users wouldn't know what to do with a source package even if they got one). The problem with thinking of mentors as a NEW queue is that one of the key properties of the NEW queue is that Debian does not distribute the files in that queue. In other words, they are not retrievable by people other than those doing NEW processing until they've been approved. As long as files are kept within the project, Debian is unlikely to get in much trouble (although historically we've had to be careful about US export regulations as well), even if the software is non-redistributable. But once Debian is serving out copies of the files to the general public, via whatever means, the project (insofar as the project has a legal existence, which is admittedly weird) is responsible for that distribution, could be sued, etc. So, it would work to think of mentors as a NEW queue provided that things uploaded to it are only available to Debian project members. If they're available to the general public, it's something else. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87obtyyubr@windlord.stanford.edu
Re: proposed new pseudo-package 'debian-mentors' for handling sponsoring requests
IANAL, etc., but how about getting some legal advice on this? It seems to me it wouldn't be nearly as cut and dried as all that; have you examined whether or not such a scheme could be set up in such a way that makes it a DMCA safe harbour? Cheers, Michael On Sat, Jan 21, 2012 at 7:47 AM, Russ Allbery r...@debian.org wrote: Michael Gilbert michael.s.gilb...@gmail.com writes: On Thu, Jan 19, 2012 at 1:07 PM, Russ Allbery wrote: For the main archive, the NEW check I think is best thought of as a spot check to ensure maintainers are doing their jobs. The real responsibility of not uploading non-redistributable material lies with the Debian project members with upload rights. ftpmaster is just checking for mistakes (at the point at which most mistakes are made). The difference for mentors is that the uploaders are not (yet) Debian project members and are not guaranteed to be trained in our licensing policies, and have not agreed to follow our rules. So, I think these concerns can be abated by thinking of mentors more of an alternative NEW queue for newcomers; rather than as an alternative package pool, which it's not (binary packages are not served, and files hosted are not widely distributed since most users wouldn't know what to do with a source package even if they got one). The problem with thinking of mentors as a NEW queue is that one of the key properties of the NEW queue is that Debian does not distribute the files in that queue. In other words, they are not retrievable by people other than those doing NEW processing until they've been approved. As long as files are kept within the project, Debian is unlikely to get in much trouble (although historically we've had to be careful about US export regulations as well), even if the software is non-redistributable. But once Debian is serving out copies of the files to the general public, via whatever means, the project (insofar as the project has a legal existence, which is admittedly weird) is responsible for that distribution, could be sued, etc. So, it would work to think of mentors as a NEW queue provided that things uploaded to it are only available to Debian project members. If they're available to the general public, it's something else. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87obtyyubr@windlord.stanford.edu -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAFBbO2S_=+zpnpfrubx+oj8kz5k5g82zvgyebh7-tqj83d7...@mail.gmail.com
Re: proposed new pseudo-package 'debian-mentors' for handling sponsoring requests
Michael van der Kolff mvanderko...@gmail.com writes: IANAL, etc., but how about getting some legal advice on this? It seems to me it wouldn't be nearly as cut and dried as all that; have you examined whether or not such a scheme could be set up in such a way that makes it a DMCA safe harbour? DMCA safe harbor is a property of a US law and does nothing to prevent lawsuits in Europe. That's part of the complexity. I didn't say that debian-mentors would pose legal problems necessarily, only that it's not equivalent to NEW. I know that the way Debian handles NEW is fairly legally safe because it was set up that way on the advice of lawyers. I don't know if there are other ways to set this up with different requirements and a different profile that would be equally safe. I suspect that someone would need to ask. The Debian project gets pro bono legal counsel, but one of the disadvantages of that relationship is that it's very slow to get advice on specific subjects because we ask a lot of strange questions and the amount of legal advice we can get is fairly limited. I believe the DPL is already managing a fairly long backlog of legal questions, so I wouldn't be too hopeful about getting legal advice in a particularly timely fashion. The problem with all legal issues like this is that they're very much like security issues: doing things properly and doing things improperly are almost indistinguishable in practice until a problem occurs, at which point you discover you were doing things improperly. It's very difficult to distinguish between doing the right thing and being too cautious, since they both look exactly the same on a day-to-day basis (nothing happens), and very similar to doing the wrong things and just getting lucky (likewise, nothing happens). That's why people tend towards being conservative and doing exactly the same thing as was done somewhere else, since there *is* safety in numbers in legal precedent and even accepted best practice, and you have a better chance of being warned in advance by a lawsuit against someone else. Right now, my guess is that the current debian-mentors setup is doing the wrong thing (in that few effective precautions are being taken against distributing unredistributable material) and getting lucky, in that it's both not really a target and the people using the service are generally trying to do the right thing and any uploads of non-redistributable material is both by mistake and not of the sort of thing people would sue over. But in the current environment where nonsense like SOPA and PIPA in the US are actually being seriously considered (if, thankfully, not yet passed), it's probably worth being somewhat paranoid about things that get the official imprimatur of the project. And I'm certainly not a lawyer and this is just my guess. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87y5t2xc4w@windlord.stanford.edu
Re: proposed new pseudo-package 'debian-mentors' for handling sponsoring requests
But in setting it up in the US, don't you only have to care about US law? Cheers, Michael On Sat, Jan 21, 2012 at 9:06 AM, Russ Allbery r...@debian.org wrote: Michael van der Kolff mvanderko...@gmail.com writes: IANAL, etc., but how about getting some legal advice on this? It seems to me it wouldn't be nearly as cut and dried as all that; have you examined whether or not such a scheme could be set up in such a way that makes it a DMCA safe harbour? DMCA safe harbor is a property of a US law and does nothing to prevent lawsuits in Europe. That's part of the complexity. I didn't say that debian-mentors would pose legal problems necessarily, only that it's not equivalent to NEW. I know that the way Debian handles NEW is fairly legally safe because it was set up that way on the advice of lawyers. I don't know if there are other ways to set this up with different requirements and a different profile that would be equally safe. I suspect that someone would need to ask. The Debian project gets pro bono legal counsel, but one of the disadvantages of that relationship is that it's very slow to get advice on specific subjects because we ask a lot of strange questions and the amount of legal advice we can get is fairly limited. I believe the DPL is already managing a fairly long backlog of legal questions, so I wouldn't be too hopeful about getting legal advice in a particularly timely fashion. The problem with all legal issues like this is that they're very much like security issues: doing things properly and doing things improperly are almost indistinguishable in practice until a problem occurs, at which point you discover you were doing things improperly. It's very difficult to distinguish between doing the right thing and being too cautious, since they both look exactly the same on a day-to-day basis (nothing happens), and very similar to doing the wrong things and just getting lucky (likewise, nothing happens). That's why people tend towards being conservative and doing exactly the same thing as was done somewhere else, since there *is* safety in numbers in legal precedent and even accepted best practice, and you have a better chance of being warned in advance by a lawsuit against someone else. Right now, my guess is that the current debian-mentors setup is doing the wrong thing (in that few effective precautions are being taken against distributing unredistributable material) and getting lucky, in that it's both not really a target and the people using the service are generally trying to do the right thing and any uploads of non-redistributable material is both by mistake and not of the sort of thing people would sue over. But in the current environment where nonsense like SOPA and PIPA in the US are actually being seriously considered (if, thankfully, not yet passed), it's probably worth being somewhat paranoid about things that get the official imprimatur of the project. And I'm certainly not a lawyer and this is just my guess. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87y5t2xc4w@windlord.stanford.edu -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cafbbo2q5lj095vujzpc0j-zjhu0nkhyyrnbc8kggbinudcu...@mail.gmail.com
RFS: sqlbuddy
Dear mentors, I am looking for a sponsor for my package sqlbuddy. * Package name: sqlbuddy Version : 1.3.3-1 Upstream Author : Calvin Lough * URL : http://www.sqlbuddy.com * License : MIT Section : web It builds those binary packages: sqlbuddy - Web based MySQL administration To access further information about this package, please visit the following URL: http://mentors.debian.net/package/sqlbuddy Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/s/sqlbuddy/sqlbuddy_1.3.3-1.dsc I would be glad if someone uploaded this package for me. Sincerely, -- Medhamsh Hacktivist | http://medhamsh.org -- 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/54108.14.99.114.184.1327098447.squir...@mail.medhamsh.org
Re: RFS: jbigkit
OK, I've simplified and renamed the debian revision to 2.0-1 (Yeah, I know, the history went backward...) Is anything else required? Cheers, Michael On Thu, Jan 19, 2012 at 10:33 PM, Jakub Wilk jw...@debian.org wrote: * Michael van der Kolff mvanderko...@gmail.com, 2012-01-19, 20:19: What do you mean by simplify debian/changelog? Well, your changelog has currently 11 entries. For an initial upload a single one would be more typical. (Also, lintian would tell you then that you forgot to close the ITP bug.) -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120119113349.ga2...@jwilk.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/CAFBbO2QTsL1UMjN+dKtd=_+=au+dzivwgpekrj7bgmyuvhx...@mail.gmail.com
Re: proposed new pseudo-package 'debian-mentors' for handling sponsoring requests
Michael van der Kolff mvanderko...@gmail.com writes: But in setting it up in the US, don't you only have to care about US law? I think that because Debian itself has a legal presence (in the sense of having a bank account and therefore assets that can be confiscated in judgement) in Europe as well as the US (and in other countries as well), things that are officially blessed by the project have to care about multiple jurisdictions. In general, you can be sued in either the location where you're doing whatever it is that you're doing or in your home location. If debian-mentors is run as a private service by a few Debian project members but not as an official part of the project, then I think only the nationality of the server and of those project members would matter. But this is all based on my very vague understanding of the complexities of international civil law, which is of course a whole field of expertise in and of itself. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87d3aexaq6@windlord.stanford.edu
Re: Making mentors.debian.net a .org
Michael Gilbert michael.s.gilb...@gmail.com writes: This should be a place for contributors to come together to collaborate and make their work better before pestering a DD about it; with minimal experienced intervention (mentoring). I'm confused as to what your referent is. When you say “this should be a place for […] minimal experienced intervention (mentoring)”, what place do you mean? The ‘debian-mentors’ resource is for contributors to find willing DDs to mentor them in the art of Debian package maintenance, as part of sponsoring a package into Debian. This is to attempt to help solve the problem that practically no DDs want to be burdened with mentoring. Let's make this about contributors primarily helping themselves. You seem to be referring to something other than ‘debian-mentors’, am I right? -- \ “When I turned two I was really anxious, because I'd doubled my | `\ age in a year. I thought, if this keeps up, by the time I'm six | _o__) I'll be ninety.” —Steven Wright | Ben Finney -- 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/87k44l3o6n@benfinney.id.au
Re: RFS: git2cl
On Sat, 21 Jan 2012 00:27:08 Jakub Wilk wrote: * Dmitry Smirnov only...@member.fsf.org, 2012-01-20, 23:49: But how much time and effort one can afford in order to regenerate single HTML file? Surely it wouldn't cost you more time than arguing about the issue takes. True, especially if you believe it shouldn't be regenerated. signature.asc Description: This is a digitally signed message part.
Re: RFS: git2cl
On Sat, 21 Jan 2012 00:27:08 Jakub Wilk wrote: * Dmitry Smirnov only...@member.fsf.org, 2012-01-20, 23:49: But how much time and effort one can afford in order to regenerate single HTML file? Surely it wouldn't cost you more time than arguing about the issue takes. Another argument is that to obey without good understanding why is a poor strategy for learning. How would you know if there are better ways to deal with the problem? To me it's a question how I might need to approach similar challenges in other packages so in the end this knowledge may pay off (and likely will). Dmitry. signature.asc Description: This is a digitally signed message part.
main-guide: dquilt: completion
Hello List: In the section 3 of the main-guide, `set up quilt', the tool dquilt is set up as an alias in ~/.bashrc (to be frank, I avoid `alias' in general): is there a simple way to make dquilt inherits the quilt completion stuff ? Thanks in advance, Jerome -- 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/4f1a1b33.20...@rezozer.net
Re: RFS: libqsi
On Sat, Jan 21, 2012 at 1:27 AM, Jasem Mutlaq wrote: Ok, I got a confirmation from QSI that the source code for libqsi is proprietary. They grant you the right to distribute source and binary forms of the library, but not to modify the source itself. Can this be added to Debian 'non-free' ? The non-free part of the archive only requires that Debian and our mirrors have permission to distribute. Also see these parts of policy for some things related to non-free: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile http://www.debian.org/doc/debian-policy/ch-archive.html#s-non-free Please ask upstream to switch to a well known and understood Free Software license (such as MIT/BSD/GPL). -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caktje6eb+0df65rsm1+atsy5cuvq+v1c5sgbgr5p08vhjcm...@mail.gmail.com
RFS: gcc-4.5-doc-non-dfsg
Dear mentors, I am looking for a sponsor for my package gcc-4.5-doc-non-dfsg. It provides the manuals for GCC 4.5, including its many compilers, and paves the way for gcc-4.6-doc-non-dfsg. (Figuring out what this package will do is left as an excercise for the reader.) * Package name: gcc-4.5-doc-non-dfsg Version : 4.5.3-1~naesten4 Upstream Author : Free Software Foundation * URL : http://gcc.gnu.org/ * License : GFDL with invariant sections Section : non-free/doc It builds those binary packages: cpp-4.5-doc - documentation for the GNU C preprocessor (cpp) gcc-4.5-doc - documentation for the GNU compilers (gcc, gobjc, g++) gcc-doc-base - several GNU manual pages gcj-4.5-doc - documentation for the GNU Java tools (gcj, gij) gfortran-4.5-doc - documentation for the GNU Fortran Compiler (gfortran) gnat-4.5-doc - documentation for the GNU Ada 95 Compiler (gnat) To access further information about this package, please visit the following URL: http://mentors.debian.net/package/gcc-4.5-doc-non-dfsg Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/non-free/g/gcc-4.5-doc-non-dfsg/gcc-4.5-doc-non-dfsg_4.5.3-1.dsc It would be nice if someone could upload the package or, failing that, tell me what I must still change before it can be uploaded. Thanks, Samuel Bronson -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! -- 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/E1RoTeW-000805-4f@hydrogen
Re: RFS: libqsi
On Sat, Jan 21, 2012 at 8:06 AM, Paul Wise p...@debian.org wrote: On Sat, Jan 21, 2012 at 1:27 AM, Jasem Mutlaq wrote: Ok, I got a confirmation from QSI that the source code for libqsi is proprietary. They grant you the right to distribute source and binary forms of the library, but not to modify the source itself. Can this be added to Debian 'non-free' ? The non-free part of the archive only requires that Debian and our mirrors have permission to distribute. Also see these parts of policy for some things related to non-free: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile http://www.debian.org/doc/debian-policy/ch-archive.html#s-non-free Please ask upstream to switch to a well known and understood Free Software license (such as MIT/BSD/GPL). The driver that requires this library (INDI QSI driver) is released under the LGPL v2.1. However, the library itself (QSI) is proprietary and there is no open source alternative as this is a very special purpose library for controlling astronomical CCDs. Therefore, I think the INDI QSI driver can end up in contrib and libqsi end up in non-free ? Is there a procedure to ask the inclusion of these packages into those respective archives? -- Best Regards, Jasem Mutlaq -- 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/cae0bu5mdmhhr8gac0u96uxg0mjefnmea-hv6hshemrtl7fo...@mail.gmail.com
