[Bug 1254831] Re: plainbox needs packaging
I'd like to close this bug as PlainBox is now in Debian and should automatically sync to Ubuntu in a few hours. ** Changed in: ubuntu Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254831 Title: plainbox needs packaging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1254831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254831] Re: plainbox needs packaging
I've updated everything, please have a look at the packaging in Debian subversion repository as described in the bug description. I'll upload a trusty-specific version of this package to a test PPA soon. ** Description changed: Hi. The python package plainbox [1] needs to be packaged for Ubuntu. - I have prepared the initial set of packaging [2] and built it inside my - test PPA [3] + The package is now inside the python-modules SVN in Debian [2], I still + want to see it in Ubuntu faster, if possible, as it's still not even in + NEW. [1] https://pypi.python.org/pypi/plainbox - [2] https://github.com/zyga/debian.plainbox (specifically the trusty branch) - [3] https://launchpad.net/~zkrynicki/+archive/plainbox-motu - - PlainBox may also be packaged for Debian soon, if that happens (before - this MOTU process is complete) then this package can be synchronized - instead. + [2] http://anonscm.debian.org/viewvc/python-modules/packages/plainbox/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254831 Title: plainbox needs packaging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1254831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254831] Re: plainbox needs packaging
Good work. A few things: - ./plainbox/impl/signal.py is GPL (v3) and not GPL (v3 or later) - duplicate-short-description plainbox plainbox-insecure-policy plainbox-secure-policy python3-plainbox python3-plainbox-doc All the packages have the same short description, so will be hard to distinguish in a package manager - latest-debian-changelog-entry-without-new-date (minor) - It might be worth registering the docs in the -doc package with doc-base at some stage (Debian Policy Manual section 9.10) - Why can't the images of the python3 package be in /usr/share/? - ./plainbox/vendor/funcsigs/LICENSE needs to be specified in debian/copyright And a few small things about the man page: W: plainbox: manpage-has-bad-whatis-entry usr/share/man/man1/plainbox.1.gz N: N:Each manual page should start with a NAME section, which lists the N:name and a brief description of the page separated by \-. The NAME N:section is parsed by lexgrog and used to generate a database that's N:queried by commands like apropos and whatis. This tag indicates that N:lexgrog was unable to parse the NAME section of this manual page. N: N:For manual pages that document multiple programs, functions, files, or N:other things, the part before \- should list each separated by a comma N:and a space. Each thing listed must not contain spaces; a man page for a N:two-part command like fs listacl must use something like fs_listacl N:in the NAME section so that it can be parsed by lexgrog. N: N:Refer to the lexgrog(1) manual page, the groff_man(7) manual page, and N:the groff_mdoc(7) manual page for details. N: N:Severity: normal, Certainty: certain N: N:Check: manpages, Type: binary N: I: plainbox: hyphen-used-as-minus-sign usr/share/man/man1/plainbox.1.gz:4 N: N:This manual page seems to contain a hyphen where a minus sign was N:intended. By default, - chars are interpreted as hyphens (U+2010) by N:groff, not as minus signs (U+002D). Since options to programs use minus N:signs (U+002D), this means for example in UTF-8 locales that you cannot N:cut and paste options, nor search for them easily. The Debian groff N:package currently forces - to be interpreted as a minus sign due to N:the number of manual pages with this problem, but this is a N:Debian-specific modification and hopefully eventually can be removed. N: N:- must be escaped (\-) to be interpreted as minus. If you really N:intend a hyphen (normally you don't), write it as \(hy to emphasise N:that fact. See groff(7) and especially groff_char(7) for details, and N:also the thread starting with N: http://lists.debian.org/debian-devel/2003/debian-devel-200303/msg01481.html N: N:If you use some tool that converts your documentation to groff format, N:this tag may indicate a bug in the tool. Some tools convert dashes of N:any kind to hyphens. The safe way of converting dashes is to convert N:them to \-. N: N:Because this error can occur very often, Lintian shows only the first 10 N:occurrences for each man page and give the number of suppressed N:occurrences. If you want to see all warnings, run Lintian with the N:-d/--debug option. N: N:Refer to /usr/share/doc/groff-base/README.Debian and the groff_char(7) N:manual page for details. N: N:Severity: wishlist, Certainty: possible N: N:Check: manpages, Type: binary -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254831 Title: plainbox needs packaging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1254831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254831] Re: plainbox needs packaging
The man page stuff is something I don't know how to fix. I'm using help2man to produce a stub man page as plainbox itself doesn't have a proper man page (yet). Do you know if there is a way to influence help2man to not generate such problems? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254831 Title: plainbox needs packaging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1254831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254831] Re: plainbox needs packaging
Hi Daniel, thanks for looking at this. (for some reason launchpad didn't allow me to reply with your message fully quoted, please forgive me about the harder readability of the content below). A few things: - ./plainbox/impl/signal.py is GPL (v3) and not GPL (v3 or later) I understand that this applies to debian/copyright? I'll see if I can correct that. - duplicate-short-description plainbox plainbox-insecure-policy plainbox-secure-policy python3-plainbox python3-plainbox-doc All the packages have the same short description, so will be hard to distinguish in a package manager I'll correct those, I thought that is the standard as many packages seem to do that. - latest-debian-changelog-entry-without-new-date (minor) Hmm? - It might be worth registering the docs in the -doc package with doc- base at some stage (Debian Policy Manual section 9.10) I'll look at that but TBH I never understood the value of that system - Why can't the images of the python3 package be in /usr/share/? It would require patching the source as it is using pkg_resources to lookup data files relative to the source files. This is something the python community has strong opinion about but at the same time, works towards making better for distributions such as Debian. In particular there is a work-in-progress system that allows the python code to remain unchanged while re-arranging the layout of files in the filesystem, with the help of a mapping file. Still right now it would serve no purpose (the end result would be identical) so before a global solution is available I'd rather not patch the library. - ./plainbox/vendor/funcsigs/LICENSE needs to be specified in debian/copyright I'll correct those, I was under the incorrect assumption that if I remove things in the clean target (like I do with the vendorized modules) I don't need to list them in the copyright file. Thanks ZK -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254831 Title: plainbox needs packaging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1254831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254831] Re: plainbox needs packaging
- You could fix the header file of ./plainbox/impl/signal.py to be GPL (v3 or later). - You could have the short description of the packages say something like toolkit for software and hardware integration testing - documentation or something... just something which indicates what the individual package is there for. - So ./plainbox/vendor/funcsigs/ is not actually used? Can't it be removed from the upstream source then? - No worries about help2man and doc-base - lintian reported the issues, so I thought I'd bring them up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254831 Title: plainbox needs packaging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1254831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254831] Re: plainbox needs packaging
- You could fix the header file of ./plainbox/impl/signal.py to be GPL (v3 or later). Ah, we'll correct that by beta-2 upstream release then. I'll fix the copyright file now - You could have the short description of the packages say something like toolkit for software and hardware integration testing - documentation or something... just something which indicates what the individual package is there for. Corrected (not uploaded yet) - So ./plainbox/vendor/funcsigs/ is not actually used? Can't it be removed from the upstream source then? It is only used on python3.2 so that we don't need to depend on a pypi package (bundling was far easier). For Debian and Ubuntu 14.04 it is actually removed and it is not used at all. Similar with mock.py - No worries about help2man and doc-base - lintian reported the issues, so I thought I'd bring them up. OK, I'd leave that as a known issue, we'll be working on proper man pages for the next release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254831 Title: plainbox needs packaging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1254831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254831] Re: plainbox needs packaging
Hum... for me the files are still there on 14.04, but maybe I misunderstood? daniel@daydream:~/plainbox-0.4~b1$ find . -name '*funcsigs*' ./plainbox/vendor/funcsigs ./plainbox/vendor/funcsigs.py ./.pc/03-unvendorize/plainbox/vendor/funcsigs.py daniel@daydream:~/plainbox-0.4~b1$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254831 Title: plainbox needs packaging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1254831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254831] Re: plainbox needs packaging
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode. To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1254831/+editstatus and add the package name in the text box next to the word Package. [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: bot-comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254831 Title: plainbox needs packaging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1254831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254831] Re: plainbox needs packaging
** Description changed: Hi. The python package plainbox [1] needs to be packaged for Ubuntu. I have prepared the initial set of packaging [2] and built it inside my test PPA [3] [1] https://pypi.python.org/pypi/plainbox - [2] https://github.com/zyga/debian.plainbox + [2] https://github.com/zyga/debian.plainbox (specifically the trusty branch) [3] https://launchpad.net/~zkrynicki/+archive/plainbox-motu + + PlainBox may also be packaged for Debian soon, if that happens (before + this MOTU process is complete) then this package can be synchronized + instead. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254831 Title: plainbox needs packaging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1254831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254831] Re: plainbox needs packaging
** Description changed: Hi. The python package plainbox [1] needs to be packaged for Ubuntu. I have prepared the initial set of packaging [2] and built it inside my test PPA [3] [1] https://pypi.python.org/pypi/plainbox [2] https://github.com/zyga/debian.plainbox (specifically the trusty branch) [3] https://launchpad.net/~zkrynicki/+archive/plainbox-motu PlainBox may also be packaged for Debian soon, if that happens (before this MOTU process is complete) then this package can be synchronized instead. + + UPDATE: the ppa has been removed, I am unable to upload my .orig.tar.gz + with dput, I'll try again tomorrow, hoping the ppa name to become + released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254831 Title: plainbox needs packaging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1254831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254831] Re: plainbox needs packaging
** Description changed: Hi. The python package plainbox [1] needs to be packaged for Ubuntu. I have prepared the initial set of packaging [2] and built it inside my test PPA [3] [1] https://pypi.python.org/pypi/plainbox [2] https://github.com/zyga/debian.plainbox (specifically the trusty branch) [3] https://launchpad.net/~zkrynicki/+archive/plainbox-motu PlainBox may also be packaged for Debian soon, if that happens (before this MOTU process is complete) then this package can be synchronized instead. - - UPDATE: the ppa has been removed, I am unable to upload my .orig.tar.gz - with dput, I'll try again tomorrow, hoping the ppa name to become - released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254831 Title: plainbox needs packaging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1254831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
