Re: I have a error on dput
Yes, you are right, that's my mistake. Now package comes to right server and a mail comes to mention success. Thank you. 2011/8/18 Kyle Willmon kylewill...@gmail.com: On Thu, Aug 18, 2011 at 01:17:04PM +0800, Shell Xu wrote: my ~/.dput.cf is like this: [debexpo] fqdn = mentors.debian.net incoming = /upload/shell909...@gmail.com/. method = http allow_unsigned_uploads = 0 Is that right? That is correct, but your dput command from the earlier email was not. You will need to run dput like this: dput debexpo blah.changes and NOT like this: dput blah.changes The latter uploads to ftpmaster, which is not what you want. Thanks - Kyle Willmon -- 无能者无所求，饱食而遨游，泛若不系之舟 blog: http://shell909090.com/blog/ twitter: http://twitter.com/shell909090 -- 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/cadextbxb7x1enfx8etge6u2bwln93gadhkds0m_4lql-tdm...@mail.gmail.com
I need help to solve lintian messages about NMU and linking with openssl
Dear debian-mentors, I'm trying to build a package for s3fs. The package was originally built by Loïc Minier and I started with his files in the debian directory. But there are some lintian messages that I'm trying to solve now. This is my very first debian package and I don't really know how to fix this issues: E: s3fs_1.40-2_amd64 changes: bad-distribution-in-changes-file NMU W: s3fs source: changelog-should-mention-nmu W: s3fs source: source-nmu-has-incorrect-version-number 1.40-2 W: s3fs source: out-of-date-standards-version 3.9.1 (current is 3.9.2) E: s3fs: possible-gpl-code-linked-with-openssl I think the debian/changelog doesn't have the correct version number (and I'm not sure about NMU at all) and that's causing the WARNINGS. For the GPL ERROR: I build s3fs with gnutls instead of openssl, but I have no idea if that solves the issue with the openssl BSD license. Can someone please explain that to me or point me to a document about it? Carsten Ringe -- www.kopis.de cars...@kopis.de skype://cringe Verschlüsselte Emails bitte mit diesem GPG Fingerprint: 1A3A 6CE1 402D E24F 54C3 9D7D 2654 1EA9 BD9F EE46 -- 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/cafizzhh-ubkbm8preis2l8c7vk8ldcna91x4gigm9uzhhxx...@mail.gmail.com
Re: I need help to solve lintian messages about NMU and linking with openssl
On 2011-08-18 08:24, Carsten Ringe wrote: Dear debian-mentors, Hi I'm trying to build a package for s3fs. The package was originally built by Loïc Minier and I started with his files in the debian directory. But there are some lintian messages that I'm trying to solve now. This is my very first debian package and I don't really know how to fix this issues: E: s3fs_1.40-2_amd64 changes: bad-distribution-in-changes-file NMU You usually unstable as distribution. To mention an NMU (Non-Maintainer Upload) the first entry in the changelog should mention NMU. Though if you are the new maintainer, this is not what you want. W: s3fs source: changelog-should-mention-nmu W: s3fs source: source-nmu-has-incorrect-version-number 1.40-2 These are triggered if the name and email in the changelog is not byte-for-byte identical with an Uploader or the Maintainer in d/control. If you are doing a NMU, the version should be 1.40-1.1 (or 1.40-2.1, depending on the last uploaded version; I am guessing the former) and (as mentioned above) the first entry in the changelog should mention an NMU. W: s3fs source: out-of-date-standards-version 3.9.1 (current is 3.9.2) Valid, check the upgrading checklist and then update Standards-Versions in d/control E: s3fs: possible-gpl-code-linked-with-openssl This is triggered if your d/copyright mentions GPL and openssl without having what looks like a GPL with OpenSSL exception. You may have to add an override for this. I think the debian/changelog doesn't have the correct version number (and I'm not sure about NMU at all) and that's causing the WARNINGS. For the GPL ERROR: I build s3fs with gnutls instead of openssl, but I have no idea if that solves the issue with the openssl BSD license. Can someone please explain that to me or point me to a document about it? Carsten Ringe In all cases, Lintian comes with a feature to tell you what the warnings are about. Either re-run lintian with -i or use lintian-info -t $tag. ~Niels -- 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/4e4cb302.20...@thykier.net
RFS: python-formalchemy
Dear mentors, I am looking for a sponsor for my package python-formalchemy. * Package name: python-formalchemy Version : 1.4.1-2 Upstream Author : Alexandre Conrad, Jonathan Ellis, Gaël Pasgrimaud formalchemy at googlegroups com * URL : http://docs.formalchemy.org/ * License : MIT Section : python To access further information about this package, please visit the following URL: http://mentors.debian.net/package/python-formalchemy Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/p/python-formalchemy/python-formalchemy_1.4.1-2.dsc I would be glad if someone uploaded this package for me. Kind regards, Shell Xu -- 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/CADexTbyRPLgLnpi6x=4qro9v4_fw7vrm-bedxdnmqw5a30s...@mail.gmail.com
Re: Solving lintian warnings for multi-package roxterm
On Thu, Aug 18, 2011 at 01:39, Tony Houghton h...@realh.co.uk wrote:
package too, eg to roxterm-gtk3. In the latter case would adding
Replaces: roxterm cause it to automatically replace roxterm at apt-get
upgrade (or only dist-upgrade?) or would I have to make a meta-package?
No. 'Replaces: A' is just a hint for dpkg that some (or _maybe_ all) files
of package A are replaced with files from your package. (d-policy §7.6 [0])
Especially, this doesn't say anything about the functionality!
Some hints on how to correctly rename a package can be found in the wiki [1].
Bonus: With my APT hat on i want to add that i will beat the hell out of you
if you try to remove the old package with an unversioned Breaks/Conflicts.
That is a dist-upgrade nightmare as it does what the maintainer intended
only in a subset of situations and in all others the opposite will happen
(= no upgrade) - and before someone adds Provides to the list:
Remember that dependencies on Provides need to be unversioned.
Sidenote: I am not sure why the usage of 'disappearing packages' was
removed from the wiki as dpkg and APT support them in squeeze -
at least in my eyes it looked like the holy grail to prevent maintainers
from using all these half-working tricks in battle against APT, but
i will leave that up to decide for others as IANAD{D,M}.
Oh, and regarding the name as is: What does upstream intend:
Do they treat gtk2 as legacy and will remove support in the long-run or
do they want to support it for… lets say 2 years at least?
Best regards
David Kalnischkies
[0] http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces
[1] http://wiki.debian.org/Renaming_a_Package
--
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/caaz6_fadhpxlk5b655v0j_+28xg6mvqtnpjpmdzo40xtrax...@mail.gmail.com
Re: RFS: dfu-programmer
Le vendredi 05 août 2011 à 13:53 +0200, Niels Thykier a écrit : On 2011-08-05 01:01, Rodolphe Pelloux-Prayer wrote: […] Hi Thanks for your interest in contributing to Debian. Could you include some more information about this package? What is it (copying from the description/synopsis is okay)? What is your motivation for the packaging etc. Why is it (done as) an NMU (Non-Maintainer Upload)? The two former will help you get the attention of reviewers (and potential sponsors) and the last one... most likely they will ask you that. Even if most of this information is readily available through various links and in the package itself, it saves reviewers / sponsors time as they can quickly determine if they can review the package or if we have a relevant team that could do it. Thanks for your comments. Dfu-programmer is a tool to flash atmel chips. For answer the question for nmu, I've contacted Andrew to see if he still wanted to maintain the package. Unfortunatly, he doesn't enough time to do it so he orphaned it. So the new upload is not a NMU anymore and it could be my first official package :) * Package name: dfu-programmer Version : 0.5.4-1 Upstream Author : weston_schm...@alumni.purdue.edu * URL : http://dfu-programmer.sourceforge.net/ * License : GPL-2+ Section : devel * Short description : device firmware update (DFU) based USB programmer for Atmel chips To access further information about this package, please visit the following URL: http://mentors.debian.net/package/dfu-programmer Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/d/dfu-programmer/dfu-programmer_0.5.4-1.dsc Git repo : http://gitorious.org/debian-packaging/dfu-programmer signature.asc Description: This is a digitally signed message part
Re: Solving lintian warnings for multi-package roxterm
On Thu, 18 Aug 2011 10:41:33 +0200 David Kalnischkies kalnischk...@gmail.com wrote: On Thu, Aug 18, 2011 at 01:39, Tony Houghton h...@realh.co.uk wrote: package too, eg to roxterm-gtk3. In the latter case would adding Replaces: roxterm cause it to automatically replace roxterm at apt-get upgrade (or only dist-upgrade?) or would I have to make a meta-package? No. 'Replaces: A' is just a hint for dpkg that some (or _maybe_ all) files of package A are replaced with files from your package. (d-policy §7.6 [0]) Especially, this doesn't say anything about the functionality! Some hints on how to correctly rename a package can be found in the wiki [1]. I'd rather keep the name roxterm for the GTK3 version if that's OK. I don't really want the main package to be named after a library dependency and have to relegate roxterm to a dummy package. Bonus: With my APT hat on i want to add that i will beat the hell out of you if you try to remove the old package with an unversioned Breaks/Conflicts. That is a dist-upgrade nightmare as it does what the maintainer intended only in a subset of situations and in all others the opposite will happen (= no upgrade) - and before someone adds Provides to the list: Remember that dependencies on Provides need to be unversioned. Don't worry, I can easily see that abusing Conflicts like that would be stupid :-). Oh, and regarding the name as is: What does upstream intend: Do they treat gtk2 as legacy and will remove support in the long-run or do they want to support it for… lets say 2 years at least? I am upstream. I don't plan to drop gtk2 support soon, especially not before #632403 is resolved or I find a satisfactory workaround. But eventually I suppose gtk2 will be very much a legacy thing and only be used by poorly maintained packages (I can imagine that being at least 2 years away though) and then it will be advantageous to remove a lot of #if... blocks and configure checks - not just for GTK2 vs 3 but for features that only became available midway through gtk2's and vte's lives. -- 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/20110818135111.249202cd@junior
Re: RFS: dfu-programmer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Rodolphe, On 18.08.2011 14:11, Rodolphe Pelloux-Prayer wrote: So the new upload is not a NMU anymore and it could be my first official package :) Here are a few comments about your package: * Please consider using a more recent debhelper compatibility level. Version 5 is quite outdated (although still okish). Generally I suggest to bump debian/compat to 8 and depend in debian/control on a 8.0 version. That works down to Lenny with backports, although your package probably won't ever enter Stable or even Oldstable anyway. * You use a VCS not hosted by Debian. That's ok and legit, but Alioth is nice too, and eases life to other people, potentially interested to help you with the package. Regardless of the repository you choose, the VCS-Browser link should point to the trunk of your repository, not to the project home page [1] * If I understand the purpose of your program, the section devel is not really appropriate - maybe electronics [2] fits better. * Upstream's NEWS file you install as doc, is in fact a changelog. For archive-wide consistency you might consider installing it as upstream changelog through dh_installchangelogs(1). Figure, that would also make Lintian pedantically happy! * Please remove unneeded comments in debian/rules. Those are for your information, and not intended to be kept. Good work, your package looks good. As you might have noticed, my comments are minor pedantic notes. [1] http://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html#bpp-vcs [2] http://packages.debian.org/unstable/electronics/ - -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJOTQqUAAoJEMcrUe6dgPNtFcYP/i6fgDAh4cWtoC590bIR5lt9 RRmOF4/rfhy/f1lgOPUFm4UuUrlojus4uFHagVcKu9NxAQ7KGijwDXHO7hnc2iIE kvvwhjAXpiVFTRgnxX9Y5LHWUrl2geLAXva8VwyZO30Gg4ngGefwbSVT/dVb3kXq n5KU3DROh7h4xzIjzlaUxuOif8ha5AXKZO21qRw117ZPXZhiNCHIq5Cmxe3bpj8y AtLaVlgaKDIAdn8usDTGBlSWYC6Ub3vD+c3Iyku2XskkeWjwcUPkS5YoshsqBibe c+tXUP0VrL0sghDBouvYCEKfEutF459GmPr4d7JZaLPnn5/Fz1PDn9jVgqXDOwD+ 9quBXaD/3zAWVOI0yXvfCyIIrgedn+RaAovS/b75B4HDn5Kovh1a//lIv+6fAwCJ Skln0BZu6DWd4rQ1A5I0BBToAbCcXCkLHZgck2DA6xAuzVW8kDyUaDL2K4anNa5k sbK4oG4NiPDXkULta1WmVwrvQFg5adYOSZkNQ6aKQRBrrGr+yyIDIak5/i58+RXz G+YnafD6oYYM3jaDv4AJU03k9ZGgUvXI7Zc1q1nvoVvuiYrtWzr4nnVCA3Bg+0Aw MHWxNNr94xU38ED471O53/8kkYkdpjmkZ6FjqMw6aEMv7GsiNgYpkDDsZJ2i62a8 VrIMNx3i9M6L6j4HVAre =Ur9O -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/4e4d0a95.4080...@toell.net
Re: edbrowse
Hi, Here's the last history of this package. Actually Mario decided to orphan it, so I adopt it. As you see below, Gergely had started an ITA at the same time but lets me maintainer. I added him to uploaders, with Mario too. I added a new entry in changelog to close the bug opened by Mario with O: . I'm not sure of release number, but I put -2 as -1 was the NMU and I didn't want to remove this. The new package waits for sponsoring to be uploaded on http://demo.accelibreinfo.eu/debian/edbrowse At the same time I'm becoming member of collab-maint group to have a full control on the repo of the package. Thanks for sponsoring. Regards, Jean-Philippe MENGUAL Le jeudi 18 août 2011 à 13:50 +0200, Gergely Nagy a écrit : Just noticed I managed to step on your toes, and retitle the O: earlier. Sorry about that! It's all yours, happy edbrowsing! =) (Do drop me a line though, if you need help - but I assume you won't, so I'll just enjoy your work.) signature.asc Description: Ceci est une partie de message numériquement signée
Re: News about the mentors.debian.net transition to upgraded software
Hello, On Tue, Aug 16, 2011 at 09:13:04AM -0400, Asheesh Laroia wrote: I agree that this is a bug. I just filed a bug report: https://alioth.debian.org/tracker/index.php?func=detailaid=313293group_id=100127atid=413115 We're working through issues and making reasonably good progress. I don't know when precisely it'll be fixed, but I appreciate the clear instructions you've given here to identify the problem. I just reuploaded kbdd to mentors, and this bug appears to be fixed. Thank you! Also, when I download the sources with dget http://mentors.debian.net/debian/pool/main/k/kbdd/kbdd_0.6-1.dsc I get the newly uploaded source package, as it should be. However, now I have noticed another (minor) thing in the OA info report (marked with ^): QA information Info:/home/expo/data/live/incoming/kbdd_0.6-1_i386.changes Info:kbdd_0.6-1.dsc Info:Package is Lintian clean Info:Package is not native Info:The maintainer and uploader emails are the same Warning:-- Scanning for watchfiles in . -- Found watchfile in ./debian -- In debian/watch, processing watchfile line: https://github.com/qnikst/kbdd/downloads .*/kbdd-(.*)\.tar\.bz2 -- Found the following matching hrefs: /downloads/qnikst/kbdd/kbdd-0.6.tar.bz2 /downloads/qnikst/kbdd/kbdd-0.5.tar.bz2 /downloads/qnikst/kbdd/kbdd-0.4.4.tar.bz2 /downloads/qnikst/kbdd/kbdd-0.4.3.tar.bz2 /downloads/qnikst/kbdd/kbdd-0.4.1.tar.bz2 /downloads/qnikst/kbdd/kbdd-0.4.tar.bz2 /downloads/qnikst/kbdd/kbdd-0.3.2.tar.bz2 /downloads/qnikst/kbdd/kbdd-0.3.1.tar.bz2 Newest version on remote site is 0.6, local version is 0.6 = Package is up to date -- Scan finished Info:A watch file is present Info:The watch file works Info:Closes WNPP bug #636262: ITP: kbdd -- Per-window keyboard layout switching daemon for X Info:Homepage: https://github.com/qnikst/kbdd Info:The package uses straight debhelper For some reason, the report of uscan is shown as a Warning:, however, there is actually nothing to be warned about in it: it just says that the package is found on upstream's website and is up to date. I think, in this case the Info: tag should be more appropriate. -- Stanislav -- 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/20110818135729.GA22128@kaiba.homelan
Re: RFS: kbdd
Hello, The package is again available on mentors.debian.net website. Could someone please review and upload it if everything is ok? Thanks! Stas On Sat, Aug 13, 2011 at 02:42:52PM +0400, Stanislav Maslovski wrote: Dear mentors, I am looking for a sponsor for my package kbdd. * Package name: kbdd Version : 0.6 Upstream Author : Alexander V. Vershilov alexander.vershi...@gmail.com * URL : https://github.com/qnikst/kbdd * License : GPL 2 or later Programming Lang: C Description : Per-window keyboard layout switching daemon for X Long description: KBDD stands for keyboard daemon. It is a simple keyboard layout switching program, which is designed to run in an X11 session and remember keyboard layouts on a per-window basis. That can be very handy for a user of a non-US keyboard who does not want to jump through layouts back and forth while typing in terminals (mostly in latin) and some kind of chat (in native language). Another useful thing about KBDD is its D-Bus notification support — it can emit signals on layout change, thus, making it possible to create layout indicator widgets in such window managers as awesome, for example. Users of popular desktop environments such as GNOME or KDE most likely do not need this package, as a similar functionality should be already available within their environment. This package may be of interest, however, for the users of tiling or dynamic window managers such as dwm or awesome. More notes: There are already similar programs within Debian: 1) xxkb - Keyboard state indicator and switcher for xkb This program does not work with nonreparenting window managers. 2) xkbind - X Keyboard Extension Indicator This program has limitations regarding input focus change tracking with some X toolkits. KBDD covers all these use cases. To access further information about this package, please visit the following URL: http://mentors.debian.net/package/kbdd Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/k/kbdd/kbdd_0.6-1.dsc I would be glad if someone uploaded this package for me. Kind regards, Stanislav Maslovski -- Stanislav -- 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/20110818141705.GA23668@kaiba.homelan
Re: edbrowse
Jean-Philippe MENGUAL mengualjean...@free.fr writes: I'm not sure of release number, but I put -2 as -1 was the NMU and I didn't want to remove this. Since the NMU never hit the archive, and -1 is not an NMU version number anyway, I'd merge the two changelogs into one. Also, looking at the changelog, I see this line: * New upstream version (3.4.7). Closes: #598162, #631027, #506613 To me, this tells that all three of that bugs were reports that a new upstream version exists, while they're not. The first is, but the second is an FTBFS, and the third is a problem with edbrowse failing to work with linksys web uis. I'd reword it a bit like this: * New upstream version (Closes: #598162). * [describe how this was fixed (Closes: #631027). * Now works with Linksys routers' UIs again (Closes: #506613) This has a few advantages, in my opinion: - It makes it obvious which bug is about what, and how they were fixed, instead of the changelog viewer having to look up each issue in the BTS and figure out what they're about. For someone who likes to see a _changelog_, that's a huge plus. - It doesn't mention the upstream version twice (it's already in the package version). - I like it better that way! Furthermore, I couldn't figure out how #631027 was eventually fixed. Perhaps because I'm not familiar with the packaging itself, but neither the changelog, nor debian/control tells me much about it. And while I'm here, a couple of other cosmetic nitpickings: - In override_dh_auto_clean, if you use rm -f, there's no need for the - prefix: the rm will never fail, thus, it is pointless to ignore its exit status. - Wouldn't it be better to simply patch the upstream manpage instead of tweaking it in debian/rules? - Wouldn't exporting CFLAGS=... LIBS=... JSLIB=.. STATICLIBS=... LFLAGS=.. make the rules file simpler? With patching the upstream manpage and exporting instead of overriding, you could get rid of all the overrides, pretty much. Another option would be to modify the upstream Makefile - it is already patched anyway to add a clean target. - dh_installchangelog should recognise and install CHANGES as an upstream changelog, even without the override - Why is debian/compat 5 when you're using dh (ie, debhelper = 7; with correct build-depends)? These are all minor improvements, but I felt like sharing since I'm poking around in the package anyway. That's all I could find with a quick glance.. Oh, and if you insist adding me to Uploaders (not neccessary, I believe, I don't think edbrowse would need two, and I'm perfectly happy being Just an Ordinary User of it :), please use alger...@madhouse-project.org. Thanks for taking care of the package! -- |8] -- 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/878vqqojwm@balabit.hu
Re: News about the mentors.debian.net transition to upgraded software
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Stanislav, On 18.08.2011 15:57, Stanislav Maslovski wrote: For some reason, the report of uscan is shown as a Warning:, however, there is actually nothing to be warned about in it: it just says that the package is found on upstream's website and is up to date. I think, in this case the Info: tag should be more appropriate. I fixed that. Actually the problem was, that the watch-file plugin checked the wrong exit status and thought uscan failed. The new (correct) behavior is, not to display uscan output at all, unless there was a problem with it. Thanks for pointing out. - -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJOTSwlAAoJEMcrUe6dgPNta98QALWGW3rRsdSE9ciGMQtzfWwT IAJv5Jmx8+O1EpznkDinkNAsQ37BYWjzbr/pV2aQHefv5DIqnooCUFwFNqWrK5L0 BH3jQMwTLC2qw0rd57PaF4dzOnXeDQAefIzH4OuL8Bhtb03eLxjiK4+y7e3Q9MJs f74gKbzlzgkDznxGXY3sSj+q2l/VSAgy8yR4UALU9vUCOquL8EnvAQbQVzjGeiz6 Dzh4Mv7t16Mi2Nnuhn4eTrmpg88UOZcqMBBdGDLHQXfFw6swOEfeoU+iWShFSsHQ bJvLkz/HxAhupFt7SvbZMo+DQuT4s9wcm7yOsg01C3kbudFxw6joMcTmvKGDhChH Lw4MwDbtjiDeAWnjI3VRux3OCxOSMUvvMePgV1BO2MBJQ4Vksbj82lugbaq++Y4P 0hQzNsRNenhnAcsxDRkx887TRIgJROg2Nxktwdim45FDdhG9JYV46mvh0890VmUN J60H1f4J3goOBlW3GhynuKMCsorMrrfssF7tHGTkb+Tn9HlrNFk2epb7QRQs/gWs 6NQINfKBNT0MsQjtClJJm1iwjqFneN9kEnXiZ9lhOKWcm/t9CCOdg6Jlsk5Otf69 +HS51UEd5V/rpHp0A30FJ2JLrtkEItZ7SgT//EfAhq0Uz+5DThY+stgchBvW5zaQ 9BIBpbMqpgUp24PZvVSl =zy05 -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/4e4d2c26.3000...@toell.net
RFS: assimp
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear mentors, sponsors and fellow Debianistas, I am looking for a sponsor for my package assimp. * Package name: assimp Version : 2.0.863~dfsg-1 Upstream Author : ASSIMP Development team * URL : http://assimp.sf.net * License : BSD (3-clause) Section : graphics Assimp is a 3D model import library, meaing you can use it to import 3D scenes (as exported by blender, alias/wavefront, maya, 3dmax, and lots more) into your applications (typically game engines or 3D modellers / realtime renderers) To access further information about this package, please visit the following URL: http://mentors.debian.net/package/assimp Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/a/assimp/assimp_2.0.863~dfsg-1.dsc the repository for the packaging can be found at ssh+git://git.debian.org/collab-maint/assimp the package uses cdbs for packaging. the package has been repackaged to strip away non-dfsg parts from upstream tarball. i someone would be willing to have a look at it, i would be very thankful. i would especially like to hear comments on the following topics: - - repackaging (for dfsg-compliancy) - - the debian/libassimp2.symbols file - - python bindings package - - D bindings package - - ... and the last stanza from the RFS-template: I would be glad if someone uploaded this package for me. cheers, IOhannes m zmölnig -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk5NL9MACgkQkX2Xpv6ydvTSowCcDV8tCfKbt2DvKFvpYGEcBayf fYAAn3/MgZIuoaHNi9F7fXfBd4w81XHX =bdl+ -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature
Re: News about the mentors.debian.net transition to upgraded software
On Thu, Aug 18, 2011 at 05:13:42PM +0200, Arno Töll wrote: I fixed that. Actually the problem was, that the watch-file plugin checked the wrong exit status and thought uscan failed. The new (correct) behavior is, not to display uscan output at all, unless there was a problem with it. Thanks for pointing out. While you are at it: can you also make clickable the URL of the project homepage that appears in this field (my package just used as an example): Info:Homepage: https://github.com/qnikst/kbdd Currently, it is shown as simple text (not a link). -- Stanislav -- 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/20110818162653.GA29230@kaiba.homelan
Re: News about the mentors.debian.net transition to upgraded software
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On 18.08.2011 18:26, Stanislav Maslovski wrote: While you are at it: can you also make clickable the URL of the project homepage that appears in this field (my package just used as an example): Info:Homepage: https://github.com/qnikst/kbdd Currently, it is shown as simple text (not a link). at some point, yes. But for now, the QA plugin outcome is just a not-normalized blob, making it non trivial to put a htmlified view around. That is legacy a design issue we need to fix at some point, making the QA output more ... err ... readable. - -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJOTT5SAAoJEMcrUe6dgPNtkAYP+wXIiLwxT3hrlpWUdtzkykCl wh0tu0Ijl5mYe5oM2/O7sZI1TemQMG9QZXe7zTUaaYhmTuTX+0MML9s+zRC5wyLl vOXWwFSqNAfubrfIWb7KmZWzPvc8WBNvQ1ve2o+NkIIYKTl98ruN5vSrPq/IS0Rb ACGUeOKeSsGUGcnnNZ3/jsMnXWRw+zS16CZaz+BnNYdIopwhMIHSuuCXlsW5Jr3D Wyq+SBQQKDMSP8VmPd9utl2rRekAVjFtb1HqJm48QWt8O4kqrMo2Nqb2cs728azW A7q0ngbOt/4Iw3JsWkTXDV+KsEecKjcp3qckEWXcILau6JMEWnBKFlf91SQFeua3 t1HhJjCYjE9SejUR7l9ldbAEv+NH0Uiqex5ufsOXEQk2Kba8pFjvHsioSnkvawrm v1CrEIN0XDAlfLC8MsxzIe8WXLxDd+tpS2ppEh2c9tf5GqnSQELMdbnx33Mx+Tqq A7cpxVcidMBs3BuCt6PDNdE/kn0MyJX5/ktN0NDx4O/b37i/YkGJLux6VnN7AEY8 Fxhk+gENGELSfP9USy++Eece4/9Q6VoZ0O5v6uRyIWKWhgbjkO76iq3ECTvRpj2C xDf6bxtPZzKkdSW2cEHnVj/MO/v5u6DrZSkC8o4aylqwj6VdtGhfT0AbSdAY/k/g vYr03pQlYPGjAnJhV8m5 =eGJP -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/4e4d3e53.6050...@toell.net
Re: RFS: mspdebug
Hi all, [...] It builds these binary packages: mspdebug - free debugger for use with Texas Instruments MS430 MCUs The package appears to be lintian clean. The upload would fix these bugs: 637345 [...] As noted in the (already closed) bug 637345, this package is in Debian already and owned by a different person. Best regards, Michael pgpb4E6T452P8.pgp Description: PGP signature
Re: RFS: acsccid
Hi, Dear mentors, I am looking for a sponsor for my package acsccid. This release is to correct the udev rules filename (debian/libacsccid1.udev) to fix the problem that the udev rules file was not added to the package. The udev rules file is required by the latest pcscd. The smart card readers will not work if this file does not exist. [...] Thanks a lot for this update. Package built, signed, and uploaded. Best regards, Michael pgp3HEH8CVqXs.pgp Description: PGP signature
Re: RFS: kbdd
Hi Stas, The package is again available on mentors.debian.net website. Could someone please review and upload it if everything is ok? I've built, signed, and uploaded your package as-is. Yet the following issues should be resolved with future uploads: - I: kbdd: hyphen-used-as-minus-sign usr/share/man/man1/kbdd.1.gz:38 - The upstream sources seem to be unclean as there is m-kbdd-service-marshal.o in src/dbus/. Please make sure upstream gets their build process sorted. Thanks a lot for your work, Michael pgpAHNHaMAEx7.pgp Description: PGP signature
Re: Solving lintian warnings for multi-package roxterm
David Kalnischkies kalnischk...@gmail.com writes:
Sidenote: I am not sure why the usage of 'disappearing packages' was
removed from the wiki as dpkg and APT support them in squeeze - at least
in my eyes it looked like the holy grail to prevent maintainers from
using all these half-working tricks in battle against APT, but i will
leave that up to decide for others as IANAD{D,M}.
You can't use disappearing packages with Policy-compliant packages so far
as I can tell, since it would require both packages provide the same
/usr/share/doc directory and changelog file, which is a Policy violation.
--
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/871uwi9vjf@windlord.stanford.edu
Re: RFS: assimp
Hi, Dear mentors, sponsors and fellow Debianistas, I am looking for a sponsor for my package assimp. * Package name: assimp Version : 2.0.863~dfsg-1 Upstream Author : ASSIMP Development team * URL : http://assimp.sf.net * License : BSD (3-clause) Section : graphics Thanks a lot for looking into packaging this software. Definitively not the easiest one... [...] the package uses cdbs for packaging. If you must. the package has been repackaged to strip away non-dfsg parts from upstream tarball. I'm wondering whether it would make sense to remove other cruft as well - basically contrib/ entirely and workspaces could go as well. And, well, I think +dfsg would be preferable over ~dfsg, but you might have good reasons for your choice? i someone would be willing to have a look at it, i would be very thankful. i would especially like to hear comments on the following topics: - repackaging (for dfsg-compliancy) See above. Plus some missing copyright information: please check code/pstdint.h, code/BoostWorkaround/boost/tuple/tuple.hpp, code/MDCNormalTable.h. Remove the LGPL'ed code from tools/assimp_view/ or make upstream ship a proper license. This is a requirement of LGPL 4b), which I believe is what applies here. Obviously debian/assimp-utils.lintian-overrides then isn't needed anymore. - the debian/libassimp2.symbols file Please consider using the c++ tag after having applied c++filt; see several recent threads on debian-mentors, e.g., [1]. - python bindings package - D bindings package - ... I'm neither an expert on python nor D packaging, hence I'll leave this bit to others. Yet I do have further comments: - Package FTBFS: dpkg-source -b assimp-2.0.863~dfsg dpkg-source: info: using source format `3.0 (quilt)' dpkg-source: info: building assimp using existing ./assimp_2.0.863~dfsg.orig.tar.gz dpkg-source: error: unwanted binary file: debian/copyright_hints dpkg-source: error: detected 1 unwanted binary file (add it in debian/source/include-binaries to allow its inclusion). - Upstream seems to ship tests; it would be nice if those were run at build time. (But using Debian's cppunit, not the home-grown one in contrib/.) Hope this helps, Michael [1] http://lists.debian.org/debian-mentors/2011/07/msg00632.html pgpBZG3KtjIEe.pgp Description: PGP signature
Re: acsccid
Dear Michael Thank you for your upload. Regards Godfrey -Original Message- From: Michael Tautschnig Sent: Friday, August 19, 2011 6:33 AM To: Godfrey Chung Cc: debian-mentors@lists.debian.org Subject: Re: RFS: acsccid Hi, Dear mentors, I am looking for a sponsor for my package acsccid. This release is to correct the udev rules filename (debian/libacsccid1.udev) to fix the problem that the udev rules file was not added to the package. The udev rules file is required by the latest pcscd. The smart card readers will not work if this file does not exist. [...] Thanks a lot for this update. Package built, signed, and uploaded. Best 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/E3C29AC3BDEC44D8B20A82DE83692386@GODFREYPC
Re: RFS: assimp
* Michael Tautschnig m...@debian.org, 2011-08-19, 00:31: some missing copyright information DEP-5-enabled lintian (see bug #633779) also reports several issues: W: assimp source: missing-field-in-dep5-copyright paragraph 20 copyright W: assimp source: comma-separated-files-in-dep5-copyright W: assimp source: missing-license-paragraph-in-dep5-copyright paragraph 32 public domain W: assimp source: missing-license-paragraph-in-dep5-copyright paragraph 32 free for use however you like credits are appreciated!!! W: assimp source: missing-license-paragraph-in-dep5-copyright paragraph 32 reuse allowed for any purpose credits appreciated. W: assimp source: missing-license-paragraph-in-dep5-copyright paragraph 32 redistribution I'm neither an expert on python nor D packaging, hence I'll leave this bit to others. I think you could drop build-dependency on python-dev. I would consider stricter dependency between python-pyassimp and libassimp2. (It doesn't matter for the time being, but it might become a problem in the future.) Shared library loading mechanism is utterly broken: import pyassimp.pyassimp ['/usr/lib/'] Traceback (most recent call last): File stdin, line 1, in module File /usr/lib/python2.6/dist-packages/pyassimp/pyassimp.py, line 167, in module class AssimpLib(object): File /usr/lib/python2.6/dist-packages/pyassimp/pyassimp.py, line 171, in AssimpLib load, release, dll = helper.search_library() File /usr/lib/python2.6/dist-packages/pyassimp/helper.py, line 103, in search_library raise AssimpError, assimp library not found pyassimp.errors.AssimpError: assimp library not found Also, why did it print stuff on stdout? :/ -- 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/20110819012217.ga2...@jwilk.net
