Bug#816542: RFS: connman/1.31-0.1 [RC]
control: owner -1 ! control: tags -1 moreinfo Hi Mateusz! >I am looking for a sponsor for my package "connman" lets review: 1) > * New upstream release (1.31) (Closes: #813580, #813647) #813647 seems not fixed, according to the upstream commits referenced in RC bug. http://git.kernel.org/cgit/network/connman/connman.git/commit/?id=acea08a0e4234a4c1a87bedc087c73ff36de0c7b http://git.kernel.org/cgit/network/connman/connman.git/commit/?id=754cc1678f5c61501299bbde70a73c58d691609b 2) you seem to have changed a previous changelog entry connman (1.21-1) unstable; urgency=low - * New upstream release. (Closes: #688238) - * Add myself to the list of uploaders. - * Bump Standards Version to 3.9.5 (no changes required). - * Build from upstream git: -- Use dh-autoreconf. - * Use init-system-helpers/dh-systemd. - * Split off connman-vpn. - * Rework descriptions (From Patrik Flykt ). - * Also install manpage for connmanctl. - * Add patch to remove obsolete After=syslog.target -from systemd service file: -- debian/patches/0001-remove-After-syslog.target-obsolete.patch + * New upstream release. + * Bump Standards Version to 3.9.5 (no changes required) + * Build from upstream git +- Use dh-autoreconf + * Use init-system-helpers/dh-systemd + * Split off connman-vpn + * Rework descriptions (From Patrik Flykt ) -- Shawn Landden Mon, 10 Feb 2014 19:40:38 -0800 3) std-version is 3.9.7 now other stuff LGTM, even if it seems a little too much for an NMU, but since most work has been done by an uploader (Shawn), and the package gained 4 NMUs in 2 uploads, I can sponsor it if you fix the above. thanks a lot for the nice work! Gianfranco
RFS: Compiz making its comeback into debian
Hey fellow debian lovers. I think it's time to re-empower some users, who like fancyness in their desktop, with compiz! Compiz also addresses a matter of accessibility, with its integration of many visual adaptation features, so it would be a significant addition to our impaired users. A couple new a11y features have also been pushed to upstream, hoping they take it into consideration. BTW, I rather concentrate on the Mate desktop, and plan on releasing an accessibility enabling package lot, called mate-accessibility (see http://git.hypra.fr/hypra/mate-accessibility), to facilitate several configuration profiles for different impairments. The first step is getting compiz back in debian. It has been cleaned up, and polished with the last version of upstream. I have followed the previous advice of Adam Borowski, and set the jpeg and png deps strait. there is the question of the source format, should it be 3(native) or quilted? Another issue, that is pending resolve, is a couple lintian errors: compiz-dev: package-contains-cmake-private-file usr/share/cmake-3.0/FindCompiz.cmake compiz-dev: package-contains-cmake-private-file usr/share/cmake-3.0/FindOpenGLES2.cmake Are those critical? or is it ok till resolution? As for functionnal tests, compiz is used by ~20 people, and is ready from sid to jessie-backports. I await more instructions and pieces of sound advice, of which i know debian people have plenty. project is uploaded to alioth: https://alioth.debian.org/projects/compiz/ git clone git+ssh://$u...@git.debian.org/git/pkg-a11y/compiz.git To check out built packages, and the mate-accessibility pkgs: http://debian.hypra.fr/debian/import_key (i suggest sid) till then, happy hacking -- Ksamak pgpCmqZvqcWSe.pgp Description: PGP signature
Bug#816611: RFS: yamllint/1.0.3-1 [ITP] -- A linter for YAML files
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "yamllint" Package name: yamllint Version : 1.0.3-1 Upstream Author : Adrien Vergé URL : https://github.com/adrienverge/yamllint License : GPL-3+ Section : devel It builds this binary package: yamllint - A linter for YAML files To access further information about this package, please visit the following URL: http://mentors.debian.net/package/yamllint Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/y/yamllint/yamllint_1.0.3-1.dsc More information about yamllint can be obtained from http://yamllint.readthedocs.org/en/latest/ Regards, Adrien Vergé
Bug#807763: Looking for help to solve licence and third-party issues of the tomahawk-player package
control: tags -1 moreinfo
Hi sorry for the late answer, it took a while to have time to dig into the
issue.
>I'm confused, on a Ubuntu 16.04 clean environment everything works fine
>with multiarch support but on debian sid it does not work.
>(https://launchpadlibrarian.net/240678247/tomahawk-player_0.8.4+dfsg1-0ubuntu1~xenial1_amd64.build)
>Is there a different in multiarch support?
seems so.
the problem seems to come from "CMAKE_INSTALL_LIBDIR", set because of the
include of GNUInstallDirs.cmake
file.
Probably the root of the issue is that *you* have a custom embedded
GNUInstallDirs.cmake file, so it might be
outdated, or not working for a bunch of other reasons.
Also that file is different from the one you can find on an Ubuntu system
meld CMakeModules/GNUInstallDirs.cmake
/usr/share/cmake-3.2/Modules/GNUInstallDirs.cmake
I see something like:
if(EXISTS "/etc/debian_version")
include(${CMAKE_ROOT}/Modules/MultiArchCross.cmake OPTIONAL RESULT_VARIABLE
_INCLUDED_MULTIARCH_TOOLCHAIN_FILE)
endif()
probably the MultiArchCross.cmake is something Ubuntu specific [1], I'm not
sure why Debian is not using it.
cmake (3.3.2-1ubuntu1) xenial; urgency=medium
* Merge with Debian; remaining changes:
- debian/cmake-data.install
debian/MultiArchCross.cmake
debian/patches/ubuntu_cmake-crosscompile.patch
Add MultiArchCross.cmake to installed files.
(help cmake to find libraries in multiarch path)
xnox says this is not yet ready to go upstream but he will work on it
- debian/patches/ubuntu_boost-multiarch.patch
find boost and python in multiarch path
this is a candidate for removal but needs rdepend testing
* Search for Python 3.5.
you can override the issue probably by using the system Module (and drop the
embedded stuff)
and using LIB_SUFFIX if it doesn't work [2]
[1] https://launchpad.net/ubuntu/+source/cmake/3.3.2-1ubuntu1
[2]
https://codesearch.debian.net/results/LIB_SUFFIX%20path%3Adebian%2Frules/page_0
Re: RFS: Compiz making its comeback into debian
Hi, On Thu, 2016-03-03 at 14:09 +0100, Ksamak wrote: > Hey fellow debian lovers. > I think it's time to re-empower some users, who like fancyness in their > desktop, with compiz! [...] > The first step is getting compiz back in debian. It has been cleaned up, > and polished with the last version of upstream. I have followed the > previous advice of Adam Borowski, and set the jpeg and png deps strait. Sounds good, assuming it can easily be used with an existing DE in Debian (I used to use compiz but I think I've forgotten how it all worked). > there is the question of the source format, should it be 3(native) or > quilted? 3.0 (quilt) Native is intended for projects developed by Debian itself. These are usually infastructure type projects (like dpkg, debhelper, etc). Most packages should not be native. > Another issue, that is pending resolve, is a couple lintian errors: > compiz-dev: package-contains-cmake-private-file > usr/share/cmake-3.0/FindCompiz.cmake > compiz-dev: package-contains-cmake-private-file > usr/share/cmake-3.0/FindOpenGLES2.cmake > Are those critical? or is it ok till resolution? You're not allowed to ship files in /usr/share/cmake-* because that directory is internal to cmake. Things will also break when cmake gets upgraded - infact what you're doing is already broken in sid. You should try and use CMake config files if possible, although they can be a bit fiddly to setup. For now you could either drop those files, or move them to some other directory (which will not automatically be searched). See: https://lintian.debian.org/tags/package-contains-cmake-private-file.html > As for functionnal tests, compiz is used by ~20 people, and is ready > from sid to jessie-backports. > I await more instructions and pieces of sound advice, of which i know > debian people have plenty. > > project is uploaded to alioth: > https://alioth.debian.org/projects/compiz/ > git clone git+ssh://$u...@git.debian.org/git/pkg-a11y/compiz.git I've only had a brief look but there a few obvious issues: - Needs "de-ubuntifying" (changelogs, control, etc) - Maintainer field needs sorting out. Who exactly is working on this? - Also you don't own the ITP - are you working together? - The package cannot be built since these dependencies do not exist in Debian. How did you test this on Debian if it cannot be built? The following packages have unmet dependencies: sbuild-build-depends-compiz-dummy : Depends: dh-migrations but it is not installable Depends: dh-translations but it is not installable Depends: libxorg-gtest-dev but it is not installable E: Unable to correct problems, you have held broken packages. Thanks, James signature.asc Description: This is a digitally signed message part
Bug#816635: RFS: memtailor/1.0~git20160302-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "memtailor" * Package name: memtailor Version : 1.0~git20160302-1 Upstream Author : Bjarke Hammersholt Roune * URL : https://github.com/Macaulay2/memtailor * License : BSD-3-clause Section : libs It builds those binary packages: libmemtailor-dev - C++ library of special purpose memory allocators (developer tools libmemtailor0 - C++ library of special purpose memory allocators (shared library) To access further information about this package, please visit the following URL: http://mentors.debian.net/package/memtailor Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/m/memtailor/memtailor_1.0~git20160302-1.dsc Or, via git: https://anonscm.debian.org/git/debian-science/packages/memtailor.git Changes since the last upload: memtailor (1.0~git20160302-1) unstable; urgency=medium * New upstream release. - Now maintained by Macaulay2 developers. * debian/control - Bump Standards-Version to 3.9.7. - Update Homepage. - Use https protocol for Vcs-Browser. - Drop libmemtailor-dbg package in favor of automatically generated memtailor-dbgsym. * debian/copyright - Update Source. * debian/libmemtailor0.symbols - Add MEMTAILOR_VERSION_STRING. * debian/patches - Remove directory; patches applied upstream. * debian/rules - Remove override_dh_strip target; no longer needed. - Update get-orig-source target. - Update GTEST_PATH in override_dh_auto_configure target. - Add --enable-shared to override_dh_auto_configure target. - Enable all hardening flags. -- Doug Torrance Thu, 03 Mar 2016 09:11:23 -0500 Regards, Doug Torrance
Bug#816647: RFS: arrayfire/3.3.0+dfsg1-1~exp1 [experimental]
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "arrayfire" * Package name: arrayfire Version : 3.3.0+dfsg1-1~exp1 Upstream Author : ArrayFire Development Group * URL : http://arrayfire.com/ * License : BSD Section : science It builds those binary packages: libarrayfire-cpu-dev - Development files for ArrayFire (CPU backend) libarrayfire-cpu3 - High performance library for parallel computing (CPU backend) libarrayfire-cpu3-dbg - Debugging symbols for ArrayFire (CPU backend) libarrayfire-dev - Common development files for ArrayFire libarrayfire-doc - Common documentation and examples for ArrayFire libarrayfire-opencl-dev - Development files for ArrayFire (OpenCL backend) libarrayfire-opencl3 - High performance library for parallel computing (OpenCL backend) libarrayfire-opencl3-dbg - Debugging symbols for ArrayFire (OpenCL backend) libarrayfire-unified-dev - Development files for ArrayFire (unified backend) libarrayfire-unified3 - High performance library for parallel computing (unified backend) libarrayfire-unified3-dbg - Debugging symbols for ArrayFire (unified backend) To access further information about this package, please visit the following URL: http://mentors.debian.net/package/arrayfire Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/a/arrayfire/arrayfire_3.3.0+dfsg1-1~exp1.dsc Changes since the last upload: * New upstream release. * d/watch: add missing repacksuffix. * d/rules: build CPU backend without ASYNC support. * Update copyright information. * Bump standards version to 3.9.7, no changes required. * Add patch fixing LAPACKE detection. * d/t/control: add missing dependency on libarrayfire-unified-dev. Regards, Ghislain Vaillant
Bug#816647: marked as done (RFS: arrayfire/3.3.0+dfsg1-1~exp1 [experimental])
Your message dated Thu, 3 Mar 2016 17:08:40 + (UTC) with message-id <13429453.4582424.1457024921022.javamail.ya...@mail.yahoo.com> and subject line Re: Bug#816647: RFS: arrayfire/3.3.0+dfsg1-1~exp1 [experimental] has caused the Debian Bug report #816647, regarding RFS: arrayfire/3.3.0+dfsg1-1~exp1 [experimental] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 816647: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816647 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "arrayfire" * Package name: arrayfire Version : 3.3.0+dfsg1-1~exp1 Upstream Author : ArrayFire Development Group * URL : http://arrayfire.com/ * License : BSD Section : science It builds those binary packages: libarrayfire-cpu-dev - Development files for ArrayFire (CPU backend) libarrayfire-cpu3 - High performance library for parallel computing (CPU backend) libarrayfire-cpu3-dbg - Debugging symbols for ArrayFire (CPU backend) libarrayfire-dev - Common development files for ArrayFire libarrayfire-doc - Common documentation and examples for ArrayFire libarrayfire-opencl-dev - Development files for ArrayFire (OpenCL backend) libarrayfire-opencl3 - High performance library for parallel computing (OpenCL backend) libarrayfire-opencl3-dbg - Debugging symbols for ArrayFire (OpenCL backend) libarrayfire-unified-dev - Development files for ArrayFire (unified backend) libarrayfire-unified3 - High performance library for parallel computing (unified backend) libarrayfire-unified3-dbg - Debugging symbols for ArrayFire (unified backend) To access further information about this package, please visit the following URL: http://mentors.debian.net/package/arrayfire Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/a/arrayfire/arrayfire_3.3.0+dfsg1-1~exp1.dsc Changes since the last upload: * New upstream release. * d/watch: add missing repacksuffix. * d/rules: build CPU backend without ASYNC support. * Update copyright information. * Bump standards version to 3.9.7, no changes required. * Add patch fixing LAPACKE detection. * d/t/control: add missing dependency on libarrayfire-unified-dev. Regards, Ghislain Vaillant --- End Message --- --- Begin Message --- Hi, Signed&Uploading right now. cheers, G. Il Giovedì 3 Marzo 2016 18:03, Ghislain Vaillant ha scritto: Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "arrayfire" * Package name: arrayfire Version : 3.3.0+dfsg1-1~exp1 Upstream Author : ArrayFire Development Group * URL : http://arrayfire.com/ * License : BSD Section : science It builds those binary packages: libarrayfire-cpu-dev - Development files for ArrayFire (CPU backend) libarrayfire-cpu3 - High performance library for parallel computing (CPU backend) libarrayfire-cpu3-dbg - Debugging symbols for ArrayFire (CPU backend) libarrayfire-dev - Common development files for ArrayFire libarrayfire-doc - Common documentation and examples for ArrayFire libarrayfire-opencl-dev - Development files for ArrayFire (OpenCL backend) libarrayfire-opencl3 - High performance library for parallel computing (OpenCL backend) libarrayfire-opencl3-dbg - Debugging symbols for ArrayFire (OpenCL backend) libarrayfire-unified-dev - Development files for ArrayFire (unified backend) libarrayfire-unified3 - High performance library for parallel computing (unified backend) libarrayfire-unified3-dbg - Debugging symbols for ArrayFire (unified backend) To access further information about this package, please visit the following URL: http://mentors.debian.net/package/arrayfire Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/a/arrayfire/arrayfire_3.3.0+dfsg1-1~exp1.dsc Changes since the last upload: * New upstream release. * d/watch: add missing repacksuffix. * d/rules: build CPU backend without ASYNC support. * Update copyright information. * Bump standards version to 3.9.7, no changes required. * Add patch fixing LAPACKE detection. * d/t/control: add missing dependency on libarrayfire-unified-dev. Regards, Ghislain Vaillant--- End Message ---
Bug#816652: RFS: compiz/1:0.9.12.2 [ITP:722451]
Package: sponsorship-requests Severity: wishlist Dear mentors, fellow debian lovers, I think it's time to re-empower some users, who like fancyness in their desktop, with compiz! Compiz also addresses a matter of accessibility, with its integration of many visual adaptation features, so it would be a significant addition to our impaired users. BTW, a couple new a11y features have also been pushed to upstream, hoping they take it into consideration. I rather concentrate on the Mate desktop, and plan on releasing an accessibility enabling package lot, called mate-accessibility (see http://git.hypra.fr/hypra/mate-accessibility), to facilitate several configuration profiles for different impairments. The first step is getting compiz back in debian. It has been cleaned up, and polished with the last version of upstream. I have followed the previous advice of Adam Borowski (on ITP), and set the jpeg and png deps strait. As for functionnal tests, compiz is used by myself, and approx ~20 people, and is ready from sid to jessie(-backports). I await more instructions and pieces of sound advice, of which i know debian people have plenty. I am looking for a sponsor for my package "compiz" * Package name: compiz Version : 1:0.9.12.2 Upstream Author : multiple (see AUTHORS) * URL : https://launchpad.net/compiz * Licenses: GPL/LGPL/MIT Section : x11 It builds those binary packages: compiz - OpenGL window and compositing manager compiz-core - OpenGL window and compositing manager compiz-dev - OpenGL window and compositing manager - development files compiz-gnome - OpenGL window and compositing manager - GNOME window decorator compiz-mate - OpenGL window and compositing manager - MATE integration compiz-plugins - OpenGL window and compositing manager - plugins compiz-plugins-default - OpenGL window and compositing manager - default plugins compiz-plugins-extra - transitional dummy package compiz-plugins-main - transitional dummy package compiz-plugins-main-default - transitional dummy package compiz-plugins-main-dev - transitional dummy package compizconfig-settings-manager - Compiz configuration settings manager libcompizconfig0 - Settings library for plugins - OpenCompositing Project libcompizconfig0-dev - Development file for plugin settings - OpenCompositing Project libdecoration0 - Compiz window decoration library libdecoration0-dev - Compiz window decoration library - development files python-compizconfig - Compizconfig bindings for Python To access further information about this package, please visit the following URL: http://mentors.debian.net/package/compiz project is also uploaded to alioth in pkg-a11y section: https://alioth.debian.org/projects/compiz/ git clone git+ssh://$u...@git.debian.org/git/pkg-a11y/compiz.git To check out built packages, and the mate-accessibility pkgs: http://debian.hypra.fr/debian/import_key (use sid for last version) Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/c/compiz/compiz_0.9.12.2.dsc -- Ksamak hypra.fr Team pgpTEKSSP47sC.pgp Description: PGP signature
Re: Bug#816652: RFS: compiz/1:0.9.12.2 [ITP:722451]
On Thu, Mar 03, 2016 at 06:55:28PM +0100, Vincent Auboyneau wrote: > Package: sponsorship-requests > Severity: wishlist > > Dear mentors, fellow debian lovers, > > I think it's time to re-empower some users, who like fancyness in their > desktop, with compiz! > Compiz also addresses a matter of accessibility, with its integration of > many visual adaptation features, so it would be a significant addition > to our impaired users. > > BTW, a couple new a11y features have also been pushed to upstream, hoping > they > take it into consideration. > I rather concentrate on the Mate desktop, and plan on releasing an > accessibility enabling package lot, called mate-accessibility (see > http://git.hypra.fr/hypra/mate-accessibility), to facilitate several > configuration profiles for different impairments. > > The first step is getting compiz back in debian. It has been cleaned up, > and polished with the last version of upstream. I have followed the > previous advice of Adam Borowski (on ITP), and set the jpeg and png deps > strait. > > As for functionnal tests, compiz is used by myself, and approx ~20 people, > and > is ready from sid to jessie(-backports). > I await more instructions and pieces of sound advice, of which i know > debian people have plenty. > > I am looking for a sponsor for my package "compiz" > > * Package name: compiz >Version : 1:0.9.12.2 >Upstream Author : multiple (see AUTHORS) > * URL : https://launchpad.net/compiz > * Licenses: GPL/LGPL/MIT >Section : x11 > > It builds those binary packages: > > compiz - OpenGL window and compositing manager > compiz-core - OpenGL window and compositing manager > compiz-dev - OpenGL window and compositing manager - development files > compiz-gnome - OpenGL window and compositing manager - GNOME window decorator > compiz-mate - OpenGL window and compositing manager - MATE integration > compiz-plugins - OpenGL window and compositing manager - plugins > compiz-plugins-default - OpenGL window and compositing manager - default > plugins > compiz-plugins-extra - transitional dummy package > compiz-plugins-main - transitional dummy package > compiz-plugins-main-default - transitional dummy package > compiz-plugins-main-dev - transitional dummy package > compizconfig-settings-manager - Compiz configuration settings manager > libcompizconfig0 - Settings library for plugins - OpenCompositing Project > libcompizconfig0-dev - Development file for plugin settings - > OpenCompositing Project > libdecoration0 - Compiz window decoration library > libdecoration0-dev - Compiz window decoration library - development files > python-compizconfig - Compizconfig bindings for Python > > To access further information about this package, please visit the following > URL: > http://mentors.debian.net/package/compiz > > project is also uploaded to alioth in pkg-a11y section: > https://alioth.debian.org/projects/compiz/ > git clone git+ssh://$u...@git.debian.org/git/pkg-a11y/compiz.git > > To check out built packages, and the mate-accessibility pkgs: > http://debian.hypra.fr/debian/import_key (use sid for last version) > > Alternatively, one can download the package with dget using this command: > dget -x > http://mentors.debian.net/debian/pool/main/c/compiz/compiz_0.9.12.2.dsc Following replies: On Thu, Mar 03, 2016 at 03:03:11PM +, James Cowgill wrote: > Hi, > > > The first step is getting compiz back in debian. It has been cleaned up, > > and polished with the last version of upstream. I have followed the > > previous advice of Adam Borowski, and set the jpeg and png deps strait. > > Sounds good, assuming it can easily be used with an existing DE in > Debian (I used to use compiz but I think I've forgotten how it all > worked). The obvious prime target is the mate desktop, which is growing in users, and has become an official ubuntu flavour, so they recently added a plugin for better integration. This is also, according to several professional in this area, the most accessible desktop available for some impaired users, partly because it provides stability. > > > there is the question of the source format, should it be 3(native) or > > quilted? > > 3.0 (quilt) > > Native is intended for projects developed by Debian itself. These are > usually infastructure type projects (like dpkg, debhelper, etc). Most > packages should not be native. if using quilt, i need to generate a orig.tar.gz, so how'd you proceed with that? just tar the thing, rename it? > > > Another issue, that is pending resolve, is a couple lintian errors: > > compiz-dev: package-contains-cmake-private-file > > usr/share/cmake-3.0/FindCompiz.cmake > > compiz-dev: package-contains-cmake-private-file > > usr/share/cmake-3.0/FindOpenGLES2.cmake > > Are those critical? or is it ok till resolution? > > You're not allowed to ship files in /usr/share/cmake-* because that > directory is
Bug#816635: marked as done (RFS: memtailor/1.0~git20160302-1)
Your message dated Thu, 3 Mar 2016 21:25:44 +0100 with message-id and subject line Re: Bug#816635: RFS: memtailor/1.0~git20160302-1 has caused the Debian Bug report #816635, regarding RFS: memtailor/1.0~git20160302-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 816635: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816635 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "memtailor" * Package name: memtailor Version : 1.0~git20160302-1 Upstream Author : Bjarke Hammersholt Roune * URL : https://github.com/Macaulay2/memtailor * License : BSD-3-clause Section : libs It builds those binary packages: libmemtailor-dev - C++ library of special purpose memory allocators (developer tools libmemtailor0 - C++ library of special purpose memory allocators (shared library) To access further information about this package, please visit the following URL: http://mentors.debian.net/package/memtailor Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/m/memtailor/memtailor_1.0~git20160302-1.dsc Or, via git: https://anonscm.debian.org/git/debian-science/packages/memtailor.git Changes since the last upload: memtailor (1.0~git20160302-1) unstable; urgency=medium * New upstream release. - Now maintained by Macaulay2 developers. * debian/control - Bump Standards-Version to 3.9.7. - Update Homepage. - Use https protocol for Vcs-Browser. - Drop libmemtailor-dbg package in favor of automatically generated memtailor-dbgsym. * debian/copyright - Update Source. * debian/libmemtailor0.symbols - Add MEMTAILOR_VERSION_STRING. * debian/patches - Remove directory; patches applied upstream. * debian/rules - Remove override_dh_strip target; no longer needed. - Update get-orig-source target. - Update GTEST_PATH in override_dh_auto_configure target. - Add --enable-shared to override_dh_auto_configure target. - Enable all hardening flags. -- Doug Torrance Thu, 03 Mar 2016 09:11:23 -0500 Regards, Doug Torrance --- End Message --- --- Begin Message --- Uploaded. 2016-03-03 16:44 GMT+01:00 Doug Torrance : > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "memtailor" > > * Package name: memtailor >Version : 1.0~git20160302-1 >Upstream Author : Bjarke Hammersholt Roune > * URL : https://github.com/Macaulay2/memtailor > * License : BSD-3-clause >Section : libs > > It builds those binary packages: > > libmemtailor-dev - C++ library of special purpose memory allocators > (developer tools > libmemtailor0 - C++ library of special purpose memory allocators (shared > library) > > To access further information about this package, please visit the > following URL: > > http://mentors.debian.net/package/memtailor > > > Alternatively, one can download the package with dget using this command: > > dget -x > http://mentors.debian.net/debian/pool/main/m/memtailor/memtailor_1.0~git20160302-1.dsc > > Or, via git: > > https://anonscm.debian.org/git/debian-science/packages/memtailor.git > > Changes since the last upload: > > memtailor (1.0~git20160302-1) unstable; urgency=medium > > * New upstream release. > - Now maintained by Macaulay2 developers. > * debian/control > - Bump Standards-Version to 3.9.7. > - Update Homepage. > - Use https protocol for Vcs-Browser. > - Drop libmemtailor-dbg package in favor of automatically generated > memtailor-dbgsym. > * debian/copyright > - Update Source. > * debian/libmemtailor0.symbols > - Add MEMTAILOR_VERSION_STRING. > * debian/patches > - Remove directory; patches applied upstream. > * debian/rules > - Remove override_dh_strip target; no longer needed. > - Update get-orig-source target. > - Update GTEST_PATH in override_dh_auto_configure target. > - Add --enable-shared to override_dh_auto_configure target. > - Enable all hardening flags. > >-- Doug Torrance Thu, 03 Mar 2016 09:11:23 > -0500 > > Regards, >Doug Torrance > > --- End Message ---
Bug#816635: RFS: memtailor/1.0~git20160302-1
Uploaded. 2016-03-03 16:44 GMT+01:00 Doug Torrance : > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "memtailor" > > * Package name: memtailor >Version : 1.0~git20160302-1 >Upstream Author : Bjarke Hammersholt Roune > * URL : https://github.com/Macaulay2/memtailor > * License : BSD-3-clause >Section : libs > > It builds those binary packages: > > libmemtailor-dev - C++ library of special purpose memory allocators > (developer tools > libmemtailor0 - C++ library of special purpose memory allocators (shared > library) > > To access further information about this package, please visit the > following URL: > > http://mentors.debian.net/package/memtailor > > > Alternatively, one can download the package with dget using this command: > > dget -x > http://mentors.debian.net/debian/pool/main/m/memtailor/memtailor_1.0~git20160302-1.dsc > > Or, via git: > > https://anonscm.debian.org/git/debian-science/packages/memtailor.git > > Changes since the last upload: > > memtailor (1.0~git20160302-1) unstable; urgency=medium > > * New upstream release. > - Now maintained by Macaulay2 developers. > * debian/control > - Bump Standards-Version to 3.9.7. > - Update Homepage. > - Use https protocol for Vcs-Browser. > - Drop libmemtailor-dbg package in favor of automatically generated > memtailor-dbgsym. > * debian/copyright > - Update Source. > * debian/libmemtailor0.symbols > - Add MEMTAILOR_VERSION_STRING. > * debian/patches > - Remove directory; patches applied upstream. > * debian/rules > - Remove override_dh_strip target; no longer needed. > - Update get-orig-source target. > - Update GTEST_PATH in override_dh_auto_configure target. > - Add --enable-shared to override_dh_auto_configure target. > - Enable all hardening flags. > >-- Doug Torrance Thu, 03 Mar 2016 09:11:23 > -0500 > > Regards, >Doug Torrance > >
Bug#813933: RFS: sawfish/1:1.11-1 [ITA] -- window manager for X11
One more iteration. On 01/03/16 22:35, Mattia Rizzolo wrote: > On Tue, Mar 01, 2016 at 09:11:58PM +, Jose M Calhariz wrote: >> On 28/02/16 23:00, Mattia Rizzolo wrote: >>> On Wed, Feb 24, 2016 at 09:41:32PM +, Jose M Calhariz wrote: >>> * I just noticed sawfish.preinst removes /var/lib/sawfish that you are >>> creating in sawfish.dirs. ??? >> I believe the directory /var/lib/sawfish is necessary. So cleaning >> sawfish.preinst > ok. > >>> * in d/rules, is the ACLOCAL variable still needed? if not get rid of >>> it (test building without works) >> I tried to used automake instead of automake1.11 and worked for my >> machine (i386). > As a QA guy I like when I see old stuff being dropped from the archive, > so also avoiding hardcoding and fixing with automake1.11 will also help > remove automake1.11 when the time will come :) > >>> after this, back to what lintian knows: >>> >>> * spelling-error-in-changelog unusuable unusable >> This is a misspell on the bug report title, so preserving the error and >> add an lintian-override for it. > brr, how ugly! > > no, please revert that commit, retitle the bug report if you care and > fix the typo in the changelog. Also, there is no need at all that the > changelog entries for bug fix are the same of the bug reports... > Surely the most nice thing would be to retitle the bug report and fix > the changelog, adding a lintian override is just plain wrong here. I misread the title of the bug report, so you are right. >> I will work on the following tomorrow. > Thanks for showing the progress, appreciated as usual :) > >>> * non-empty-dependency_libs-in-la-file + incorrect-libdir-in-la-file >>> these are caused just because of a typo in the target name of >>> override_dh_auto_install; I'll let you discover the typo and fix it. Done. >>> * sawfish: maintainer-script-without-set-e (all the maintscripts) I don't get that error and my lintian is updated. >>> * sawfish-lisp-source: script-not-executable >>> usr/share/sawfish/lisp/sawfish/cfg/main.jl >>> there actually is an override, but the file is named wrongly and so >>> not picked up by dh_lintian. maybe you also want to add an override >>> for the sawfish-data one. Done > > signature.asc Description: OpenPGP digital signature
Bug#806572: RFS: multimail/0.50~20150922-1 [ITA]
Hi Mattia! On Wednesday, March 02, 2016 01:16:20 PM Mattia Rizzolo wrote: > On Sat, Jan 09, 2016 at 10:38:47AM -0500, Robert James Clay wrote: > > Hi Tobias! > > > > On Thursday, January 07, 2016 05:54:29 AM Tobias Frost wrote: > > > On Tue, 05 Jan 2016 18:08:55 -0500 Robert James Clay > > > > > > wrote: > > > > On Tuesday, January 05, 2016 04:27:48 AM Tobias Frost wrote: > [ anticipation of work that will be done... ] > > How's going with this? I'm afraid that I got rather heavily tied up in other things and so haven't been able to work on this as much as I'd like... Should I perhaps temporarily close the RFS bug and reopen it when I have an updated version of the package done and uploaded to mentors? (Note that the next package update will also include a new snapshot.) > Several weeks passed and we haven't heard back from you, this is just a > gentle ping :) And I appreciate that! RJ Clay j...@rocasa.us
Bug#816683: RFS: cloudabi-utils/0.8-1 [ITP]
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "cloudabi-utils" Package name: cloudabi-utils Version : 0.8-1 Upstream Author : Ed Schouten URL : https://nuxi.nl/ License : 2-clause BSD license Section : misc It builds those binary packages: cloudabi-utils - Utilities for spawning CloudABI processes libcloudabi-dev - Native ports of CloudABI functions (development files) libcloudabi0 - Native ports of CloudABI functions (shared library) To access further information about this package, please visit the following URL: http://mentors.debian.net/package/cloudabi-utils Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/c/cloudabi-utils/cloudabi-utils_0.8-1.dsc - End of boilerplate ;-) - To summarize, cloudabi-utils is a package that provides a utility called cloudabi-run that you can use to start CloudABI programs. CloudABI is a secure POSIX-like runtime built around the concept of capability-based security. In order to make the startup process secure, cloudabi-run cannot start the requested program directly. It first has to jump through a tiny 'proxy' program called cloudabi-reexec to ensure it has already entered CloudABI's sandbox. cloudabi-reexec itself is a CloudABI program. This tool has to be built with a cross compiler for CloudABI and linked against CloudABI's C library. All of these components are fully BSD and MIT licensed: - Toolchain: Clang, LLVM, LLD, Binutils - C runtime library: LLVM's compiler-rt - C library: https://github.com/NuxiNL/cloudlibc - cloudabi-reexec: https://github.com/NuxiNL/cloudabi-ports/blob/master/packages/cloudabi-reexec/cloudabi-reexec.c Now the problem is as follows: I don't think it's realistic that we'll be able to build cloudabi-reexec as part of this Debian package. I don't have any intent on including packages for CloudABI's C library in Debian, for example. For this reason I've including a precompiled binary. The README explicitly states where this binary came from. A package that I wrote for FreeBSD also uses these precompiled binaries: https://www.freshports.org/sysutils/cloudabi-utils My question is, is this all right according to Debian's project guidelines? If not, is there anything I can do to address this? Thanks, Ed Schouten
Bug#816652: RFS: compiz/1:0.9.12.2 [ITP:722451]
Hi, [I've added Jean-Philippe in case he wants to weigh in] On Thu, 2016-03-03 at 19:58 +0100, Vincent Auboyneau wrote: > On Thu, Mar 03, 2016 at 03:03:11PM +, James Cowgill wrote: > > > The first step is getting compiz back in debian. It has been cleaned up, > > > and polished with the last version of upstream. I have followed the > > > previous advice of Adam Borowski, and set the jpeg and png deps strait. > > Sounds good, assuming it can easily be used with an existing DE in > > Debian (I used to use compiz but I think I've forgotten how it all > > worked). > > The obvious prime target is the mate desktop, which is growing in users, > and has become an official ubuntu flavour, so they recently added a > plugin for better integration. > This is also, according to several professional in this area, the most > accessible desktop available for some impaired users, partly because it > provides stability. Ok I'm fine with compiz being reintroduced into Debian. > > > there is the question of the source format, should it be 3(native) or > > > quilted? > > 3.0 (quilt) > > > > Native is intended for projects developed by Debian itself. These are > > usually infastructure type projects (like dpkg, debhelper, etc). Most > > packages should not be native. > if using quilt, i need to generate a orig.tar.gz, so how'd you proceed > with that? just tar the thing, rename it? In a normal package, the orig.tar.gz should (if possible) be identical to the upstream release version. You probably want this file: https://launchpad.net/compiz/0.9.12/0.9.12.2/+download/compiz-0.9.12.2.tar.bz2 BUT, I have noticed that instead of using patches, Ubuntu has been creating "fake" upstream releases when fixing bugs. This isn't great since the latest bugfixes are now only found in Ubuntu and aren't easily split out for other distributions. The best solution is to try and get a new release of compiz with these fixes and then persuade Ubuntu developers to ship patches in debian/patches rather than manually patching the source. The ideal change flow should be Upstream -> Debian -> Ubuntu. The alternatives to that don't look nice. You could move the diff between ubuntu and upstream into debian/patches, but it looks massive. > > > Another issue, that is pending resolve, is a couple lintian errors: > > > compiz-dev: package-contains-cmake-private-file > > > usr/share/cmake-3.0/FindCompiz.cmake > > > compiz-dev: package-contains-cmake-private-file > > > usr/share/cmake-3.0/FindOpenGLES2.cmake > > > Are those critical? or is it ok till resolution? > > You're not allowed to ship files in /usr/share/cmake-* because that > > directory is internal to cmake. Things will also break when cmake gets > > upgraded - infact what you're doing is already broken in sid. > > > > You should try and use CMake config files if possible, although they > > can be a bit fiddly to setup. For now you could either drop those > > files, or move them to some other directory (which will not > > automatically be searched). > > > > See: > > https://lintian.debian.org/tags/package-contains-cmake-private-file.html > I've already sent a mail to this part's creator, as it is indeed fiddly. Ok, hopefully that can be sorted - it has to be removed for the moment though. > > > As for functionnal tests, compiz is used by ~20 people, and is ready > > > from sid to jessie-backports. > > > I await more instructions and pieces of sound advice, of which i know > > > debian people have plenty. > > > > > > project is uploaded to alioth: > > > https://alioth.debian.org/projects/compiz/ > > > git clone git+ssh://$u...@git.debian.org/git/pkg-a11y/compiz.git > > I've only had a brief look but there a few obvious issues: > > - Needs "de-ubuntifying" (changelogs, control, etc) > I have been told (by a DD) that changelog "mixing" was ok, since ubuntu > was already using it as a project changelog (not just deb changelog), > and debian's additions would only affect last entry. > What do you suggest? OK, in that case leaving those entries should be fine. I did notice the Debian version number is earlier than the Ubuntu version in the changelog which isn't going to work properly - maybe that can be fixed with a new upstream release :) > > - Maintainer field needs sorting out. Who exactly is working on this? > > - Also you don't own the ITP - are you working together? > I work with Jean-philippe yes. we could transfer ownership indeed. You don't need to transfor ownership if everyone involved is ok with what's going on. You should remove the XSBC-Original-Maintainer field, and replace the Uploaders field with the other people working on compiz. Looking over the ITP, two teams were mentioned: pkg-a11y and compiz. If the packaging is being done by a team then the Maintainer field should be set to a sutible mailing list. Has it been decided which team compiz will live under? Relevant policy info: https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Maintainer
