Re: [Pkg-javascript-devel] Problems to recreate minimized JS in r-cran-jsonld
Hi, On Thu, May 10, 2018 at 01:31:56PM +0500, Pirate Praveen wrote: > > You'll need to update webpack.config.js with system path for it to find apt > installed modules. I naively tried diff --git a/webpack.config.js b/webpack.config.js index 7ce5c6e..87f7559 100644 --- a/webpack.config.js +++ b/webpack.config.js @@ -20,11 +20,11 @@ const outputs = [ entry: [ // 'babel-polyfill' is very large, list features explicitly 'regenerator-runtime/runtime', - 'core-js/fn/array/includes', - 'core-js/fn/object/assign', - 'core-js/fn/promise', - 'core-js/fn/string/starts-with', - 'core-js/fn/symbol', + '/usr/lib/nodejs/core-js/fn/array/includes', + '/usr/lib/nodejs/core-js/fn/object/assign', + '/usr/lib/nodejs/core-js/fn/promise', + '/usr/lib/nodejs/core-js/fn/string/starts-with', + '/usr/lib/nodejs/core-js/fn/symbol', // main lib './lib/index.js' ], which did not help. > > jsonld.js does not work. The file size of this uncompressed file is way > > smaller than the minimazion result and doese not work together with the > > R code. Thus I really need to undergo the process to create the > > minimized JS. > > https://wiki.debian.org/Javascript/#Using_build_tools_like_grunt has > examples. Is there any actual package example? The anchor does not exist (any more) on that wiki page (which should be updated to Salsa anyway ;-) ). Kind regards Andreas. -- http://fam-tille.de
Re: [Pkg-javascript-devel] Problems to recreate minimized JS in r-cran-jsonld
On Wed, May 9, 2018 at 3:05 PM, Andreas Tillewrote: Hi, I was stumbling upon an issue with some minimized JS in the package r-cran-jsonld (ITPed in #898224). I tried to recreate jsonld.min.js and have written a script[1] which calls webpack in a clone of the Github reporsitory. Unfortunately the webpack call ends in: webpack-merge@4.1.2 node_modules/webpack-merge └── lodash@4.17.10 Hash: eaf5c95c94821ab4944c9f696b4a89040915c26b Version: webpack 3.5.6 Child Hash: eaf5c95c94821ab4944c Time: 140ms Asset Size Chunks Chunk Names jsonld.js 3.61 kB 0 [emitted] jsonld [0] multi regenerator-runtime/runtime core-js/fn/array/includes core-js/fn/object/assign core-js/fn/promise core-js/fn/string/starts-with core-js/fn/symbol ./lib/index.js 100 bytes {0} [built] ERROR in multi regenerator-runtime/runtime core-js/fn/array/includes core-js/fn/object/assign core-js/fn/promise core-js/fn/string/starts-with core-js/fn/symbol ./lib/index.js Module not found: Error: Can't resolve 'babel-loader' in '/home/andreas/debian-maintain/salsa/r-pkg-team/0_prospective/r-cran-jsonld/debian/JS/jsonld.js' @ multi regenerator-runtime/runtime core-js/fn/array/includes core-js/fn/object/assign core-js/fn/promise core-js/fn/string/starts-with core-js/fn/symbol ./lib/index.js You'll need to update webpack.config.js with system path for it to find apt installed modules. jsonld.js does not work. The file size of this uncompressed file is way smaller than the minimazion result and doese not work together with the R code. Thus I really need to undergo the process to create the minimized JS. Any idea how to approach this? https://wiki.debian.org/Javascript/#Using_build_tools_like_grunt has examples.
Bug#898278: marked as done (RFS: arptables/0.0.4-2 - ARP table administration)
Your message dated Thu, 10 May 2018 13:06:37 +0200 with message-idand subject line RFS: arptables/0.0.4-2 - ARP table administration has caused the Debian Bug report #898278, regarding RFS: arptables/0.0.4-2 - ARP table administration 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.) -- 898278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898278 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 "arptables" * Package name: arptables Version : 0.0.4-2 Upstream Author : Bart De Schuymer * URL : http://www.netfilter.org * License : GPL-2 Section : net It builds those binary packages: arptables - ARP table administration To access further information about this package, please visit the following URL: https://mentors.debian.net/package/arptables Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/a/arptables/arptables_0.0.4-2.dsc Changes since the last upload: * [1a26c32] d/patch: Add dpkg-buildflags * [5869fd6] d/patches: cleanup sysvinit script (Closes: #897976) Regards, Alberto Molina Coballes --- End Message --- --- Begin Message --- build, signed and uploaded. Thanks for your contribution to Debian :-)--- End Message ---
r-cran-dbi changed from arch=any to arch=all which makes it "unvisible" in unstable (Was: New version of r-bioc-genomicranges breaks autopkgtests of r-bioc-summarizedexperiment in testing)
Hi, a lot of r-* packages received mails about test suite errors like this: On Wed, May 09, 2018 at 02:16:29PM +0100, Paul Gevers wrote: > ... > [2] > https://ci.debian.net/packages/r/r-bioc-summarizedexperiment/testing/amd64/ I think the problem is that the packages depend directly or indirectly from r-cran-dbi version 1.0.0 which is according to tracker[1] available for architecture all but an older version is available for all architectures. This ends up in something like $ apt-cache policy r-cran-dbi r-cran-dbi: Installed: 0.8-1 Candidate: 0.8-1 Version table: *** 0.8-1 501 501 http://httpredir.debian.org/debian testing/main amd64 Packages 50 http://httpredir.debian.org/debian unstable/main amd64 Packages 50 http://ftp.debian.org/debian unstable/main amd64 Packages 100 /var/lib/dpkg/status May be this will "heal" somehow automatically but I wanted to give some hint about this in case some manual action might be needed. Kind regards Andreas. [1] https://packages.debian.org/unstable/r-cran-dbi -- http://fam-tille.de
Bug#898308: marked as done (RFS: streamlink/0.12.1+dfsg-1)
Your message dated Thu, 10 May 2018 10:20:13 + with message-idand subject line closing RFS: streamlink/0.12.1+dfsg-1 has caused the Debian Bug report #898308, regarding RFS: streamlink/0.12.1+dfsg-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.) -- 898308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898308 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "streamlink" for a new upstream version 0.12.1. * Package name: streamlink Version : 0.12.1+dfsg-1 Upstream Author : Streamlink Team * URL : https://streamlink.github.io/ * License : BSD-2-clause, Apache-2.0, MIT/Expat, SIL-OFL-1.1 Section : python It builds those binary packages: livestreamer - transitional package - streamlink python3-streamlink - Python module for extracting video streams from various websites python3-streamlink-doc - CLI for extracting video streams from various websites (documentation) streamlink - CLI for extracting video streams from various websites to a video player To access further information about this package, please visit the following URL: https://mentors.debian.net/package/streamlink Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/streamlink/streamlink_0.12.1+dfsg-1.dsc More information about streamlink can be obtained from https://streamlink.github.io/ Changes since the last upload: streamlink (0.12.1+dfsg-1) unstable; urgency=low * Recommends vlc as default player * Test manpage and docs installation * New upstream version 0.12.1+dfsg * Bump standard version to 4.1.4, no change required * Remove X-Python3-Version not needed anymore -- Alexis Murzeau Thu, 10 May 2018 00:45:54 +0200 Regards, -- Alexis Murzeau PGP: B7E6 0EBB 9293 7B06 BDBC 2787 E7BD 1904 F480 937F signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Package streamlink version 0.12.1+dfsg-1 is in unstable now. https://packages.qa.debian.org/streamlink--- End Message ---
Bug#898308: RFS: streamlink/0.12.1+dfsg-1
Le 10/05/2018 à 04:01, Paul Wise a écrit : > On Thu, May 10, 2018 at 7:40 AM, Alexis Murzeau wrote: > >> I am looking for a sponsor for my package "streamlink" for a new >> upstream version 0.12.1. > > Uploaded. > > Some things you might want to do if you have spare time: > >> * Remove X-Python3-Version not needed anymore > > This is incorrect, removing this changed the Depends from python3 (>= > 3.4~) to 3.3.2-2~, which is clearly incorrect since upstream says they > only support Python 3.4. Yes but oldstable has python >= 3.4 and lintian warning ancient-python-version-field suggest to remove the X-Python3-Version field. (As a side note, the 3.3.2-2~ version is used as a default one as it is needed for dh-python3 compile/clean scripts.) I agree with you that this package should require python 3.4, independently from available versions in any Debian distribution or any derivative. I guess the lintian tag is there to avoid things like "Depends: python2:any (>> 2.1)", that is using versioned dependency with a very old one or try to avoid X- control fields when not really needed. I will ask them. -- Alexis Murzeau PGP: B7E6 0EBB 9293 7B06 BDBC 2787 E7BD 1904 F480 937F
Bug#898308: Upstream minimum supported python version 3.4 and lintian tag ancient-python-version-field
Hi, I maintain the "streamlink" package were upstream supports only python >= 3.4, so I have added X-Python3-Version >= 3.4 in control file. But the new lintian tag ancient-python-version-field want it to be removed as oldstable has python3 >= 3.4. Removing X-Python3-Version changes the binary package dependency on python from >= 3.4~ to >= 3.3.2-2~. What's the way to handle the minimum supported python3 version in respect to ancient-python-version-field lintian tag ? Thanks for your help, -- Alexis Murzeau PGP: B7E6 0EBB 9293 7B06 BDBC 2787 E7BD 1904 F480 937F signature.asc Description: OpenPGP digital signature
Re: r-cran-dbi changed from arch=any to arch=all which makes it "unvisible" in unstable (Was: New version of r-bioc-genomicranges breaks autopkgtests of r-bioc-summarizedexperiment in testing)
On 10 May 2018 at 11:54, Andreas Tille wrote: | Hi, | | a lot of r-* packages received mails about test suite errors like this: | | On Wed, May 09, 2018 at 02:16:29PM +0100, Paul Gevers wrote: | > ... | > [2] https://ci.debian.net/packages/r/r-bioc-summarizedexperiment/testing/amd64/ | | I think the problem is that the packages depend directly or indirectly | from r-cran-dbi version 1.0.0 which is according to tracker[1] available | for architecture all but an older version is available for all | architectures. This ends up in something like | | $ apt-cache policy r-cran-dbi | r-cran-dbi: | Installed: 0.8-1 | Candidate: 0.8-1 | Version table: | *** 0.8-1 501 | 501 http://httpredir.debian.org/debian testing/main amd64 Packages | 50 http://httpredir.debian.org/debian unstable/main amd64 Packages | 50 http://ftp.debian.org/debian unstable/main amd64 Packages | 100 /var/lib/dpkg/status | | | May be this will "heal" somehow automatically but I wanted to give some | hint about this in case some manual action might be needed. Sorry about that. It must have been an old packaging oversight that only came to light now -- DBI never had a src/ directory and should have been 'all' all along. Any idea how we can correct that at the repo? Shall we file a bug with release.d.o? Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Re: [Pkg-javascript-devel] Problems to recreate minimized JS in r-cran-jsonld
On Thu, May 10, 2018 at 2:31 PM, Andreas Tillewrote: > jsonld.js does not work. The file size of this uncompressed file is way > smaller than the minimazion result and doese not work together with the > R code. Thus I really need to undergo the process to create the > minimized JS. https://wiki.debian.org/Javascript/#Using_build_tools_like_grunt has examples. Is there any actual package example? The anchor does not exist (any more) on that wiki page (which should be updated to Salsa anyway ;-) ). https://wiki.debian.org/Javascript/Nodejs#Using_build_tools_like_grunt last link seems a mistake in copy-paste, this is the correct link.
Re: r-cran-dbi changed from arch=any to arch=all which makes it "unvisible" in unstable (Was: New version of r-bioc-genomicranges breaks autopkgtests of r-bioc-summarizedexperiment in testing)
Hi Dir, On 10-05-18 14:04, Dirk Eddelbuettel wrote: > Sorry about that. It must have been an old packaging oversight that only came > to light now -- DBI never had a src/ directory and should have been 'all' all > along. > > Any idea how we can correct that at the repo? Shall we file a bug with > release.d.o? ftp.debian.org is the right pseudo-package for removal (of the 0.8-1 packages) from unstable. Paul signature.asc Description: OpenPGP digital signature
Re: r-cran-dbi changed from arch=any to arch=all which makes it "unvisible" in unstable (Was: New version of r-bioc-genomicranges breaks autopkgtests of r-bioc-summarizedexperiment in testing)
On 10 May 2018 at 19:47, Paul Gevers wrote: | Hi Dir, | | On 10-05-18 14:04, Dirk Eddelbuettel wrote: | > Sorry about that. It must have been an old packaging oversight that only came | > to light now -- DBI never had a src/ directory and should have been 'all' all | > along. | > | > Any idea how we can correct that at the repo? Shall we file a bug with release.d.o? | | ftp.debian.org is the right pseudo-package for removal (of the 0.8-1 | packages) from unstable. Ok, thanks, filed as #898354. Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Re: r-cran-dbi changed from arch=any to arch=all which makes it "unvisible" in unstable (Was: New version of r-bioc-genomicranges breaks autopkgtests of r-bioc-summarizedexperiment in testing)
Hi, On 10-05-18 19:57, Dirk Eddelbuettel wrote: > On 10 May 2018 at 19:47, Paul Gevers wrote: > | On 10-05-18 14:04, Dirk Eddelbuettel wrote: > | > Sorry about that. It must have been an old packaging oversight that only > came > | > to light now -- DBI never had a src/ directory and should have been 'all' > all > | > along. > | > > | > Any idea how we can correct that at the repo? Shall we file a bug with > release.d.o? > | > | ftp.debian.org is the right pseudo-package for removal (of the 0.8-1 > | packages) from unstable. > > Ok, thanks, filed as #898354. Thanks. @Andreas/team, once that bug gets fixed, I'll reschedule all the regressing r-* packages. Good catch. Excellent cooperation. Paul signature.asc Description: OpenPGP digital signature
Bug#897238: Bits about Intel MKL packaging -- Higher Priority than OpenBLAS
On Sun, May 06, 2018 at 08:29:29AM +, Lumin wrote: > > He put forward a simpler solution: Just don't provide libblas.so.3, such > > that MKL will never be used to satisfy the dependency of libblas.so.3 . > > Based on his idea, my new solution is the follows: > > > > libmkl-rt -- > > Depends: libblas3 | libblas.so.3 > > Provides: NOTHING ... (4) > > > > So it's totally safe now. If there is MKL, there must be a free > > libblas.so.3 implementation with a priority definitely larger than 1, > > overriding MKL in terms of auto-mode alternatives. On the other hand, > > if that alternative is manually set, then there is nothing to worry > > about. This solution is also able to resolve problems found in (1) and (3). > > Now libmkl-rt doesn't provide libblas.so.3 and liblapack.so.3, and it > pre-depends on libblas3 | libblas.so.3 and liblapack3 | liblapack.so.3 . > Similar change was applied to libmkl-dev. Using a Pre-Depends here is IMO wrong. Quoting Policy §7.2: Pre-Depends should be used sparingly, preferably only by packages whose premature upgrade or installation would hamper the ability of the system to continue with any upgrade that might be in progress. You should not specify a Pre-Depends entry for a package before this has been discussed on the debian-devel mailing list and a consensus about doing that has been reached. See Dependencies. I also think that removing the Provides is not a good idea. The alternative is provided by the package, and that should be made clear in the dependency relationships. I'm sorry but I don't have an ideal solution to the problems we previously discussed. But IMO it's acceptable to not perfectly deal with the corner case where only MKL is installed, as long as some warning is displayed. > Previously Sébastien expressed his interest on benchmarking. I'm > interested in that too. So apart from the debconf part, I wrote a simple > benchmarker[4] in Julia[5] for comparing several BLAS implementations. > Thanks to Julia's convenient FFI functionality, I can test all > implementations within a single run, without any modification to environment > variable or alternatives. > > Test result on my laptop (CPU=i5-7440HQ) matches expectation: > > dnrm2 Julia > 0.33 seconds > dnrm2 /usr/lib/x86_64-linux-gnu/blas/libblas.so.3.8.0 > 0.74 seconds (3 allocations: 48 bytes) > dnrm2 Error :1.1368683772161603e-13 > dnrm2 /usr/lib/x86_64-linux-gnu/atlas/libblas.so.3.10.3 > 0.38 seconds (3 allocations: 48 bytes) > dnrm2 Error :0.0 > dnrm2 /usr/lib/x86_64-linux-gnu/libopenblas_haswellp-r0.2.20.so > 0.31 seconds (3 allocations: 48 bytes) > dnrm2 Error :0.0 > dnrm2 /usr/lib/x86_64-linux-gnu/libmkl_rt.so > 0.029561 seconds (3 allocations: 48 bytes) > dnrm2 Error :0.0 > dgemm Julia > 4.362279 seconds (2 allocations: 128.000 MiB, 0.20% gc time) > dgemm /usr/lib/x86_64-linux-gnu/blas/libblas.so.3.8.0 > 47.893710 seconds (10 allocations: 160 bytes) > dgemm Error :2.0735139719127268e-10 > dgemm /usr/lib/x86_64-linux-gnu/atlas/libblas.so.3.10.3 > 10.412422 seconds (10 allocations: 160 bytes) > dgemm Error :2.4175670445887973e-11 > dgemm /usr/lib/x86_64-linux-gnu/libopenblas_haswellp-r0.2.20.so > 1.211220 seconds (10 allocations: 160 bytes) > dgemm Error :2.770610675980814e-11 > dgemm /usr/lib/x86_64-linux-gnu/libmkl_rt.so > 1.103356 seconds (10 allocations: 160 bytes) > dgemm Error :2.7982744719588258e-11 > > Netlib is always the slowest one. For small matrices OpenBLAS is > very competitive. For large matrices MKL is the fastest. Thanks, this is an interesting data point. -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name ⠈⠳⣄ http://www.debian.org signature.asc Description: PGP signature
Re: Problems to recreate minimized JS in r-cran-jsonld
On Wed, May 9, 2018 at 5:35 AM, Andreas Tillewrote: > I was stumbling upon an issue with some minimized JS in the package > r-cran-jsonld (ITPed in #898224). I tried to recreate jsonld.min.js and > have written a script[1] which calls webpack in a clone of the Github > reporsitory. Unfortunately the webpack call ends in: > > webpack-merge@4.1.2 node_modules/webpack-merge > └── lodash@4.17.10 > ... > ERROR in multi regenerator-runtime/runtime core-js/fn/array/includes > core-js/fn/object/assign core-js/fn/promise core-js/fn/string/starts-with > core-js/fn/symbol ./lib/index.js > Module not found: Error: Can't resolve 'babel-loader' in > '/home/andreas/debian-maintain/salsa/r-pkg-team/0_prospective/r-cran-jsonld/debian/JS/jsonld.js' > @ multi regenerator-runtime/runtime core-js/fn/array/includes > core-js/fn/object/assign core-js/fn/promise core-js/fn/string/starts-with > core-js/fn/symbol ./lib/index.js > ... > Any idea how to get the minimized JS? Simply taking the non-minimized > jsonld.js does not work. The file size of this uncompressed file is way > smaller than the minimazion result and doese not work together with the > R code. Thus I really need to undergo the process to create the > minimized JS. > > Any idea how to approach this? > ... > [1] > https://salsa.debian.org/r-pkg-team/r-cran-jsonld/blob/master/debian/JS/get-jsonld.min > Hi, I'm an upstream developer for jsonld.js and the one to blame for the webpack config. ;-) I'm getting 404 on that salsa repo so I'm not sure what your script is doing. In npm world you can build jsonld.min.js with "npm install && npm run build-webpack". That's how it's published to npm. I've never tried building with apt installed modules. If upstream changes would help make this all easier, let me know. -dave
Bug#898389: RFS: proxychains-ng/4.12-2
Package: sponsorship-requests Severity: normal X-Debbugs-CC: proxycha...@packages.debian.org Dear mentors and proxychains maintainers, I am looking for a sponsor for my package "proxychains-ng". I am also looking for a DD to help migrate the packaging git repository onto Debian group on Salsa platform and grant Master role of that repo to me (hosiet-guest). * Package name: proxychains-ng Version : 4.12-2 Upstream Author : rofl0r* URL : https://github.com/rofl0r/proxychains-ng * License : GPL-2+ Section : net It builds those binary packages: libproxychains4 - runtime shared library for proxychains-ng proxychains4 - redirect connections through socks/http proxies To access further information about this package, please visit the following URL: https://mentors.debian.net/package/proxychains-ng Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/proxychains-ng/proxychains-ng_4.12-2.dsc Proposed git packaging repository: https://salsa.debian.org/debian/proxychains-ng (not available yet) Temporary git packaging repository: https://salsa.debian.org/hosiet-guest/proxychains-ng (should be removed after upload) Changes since the last upload: proxychains-ng (4.12-2) unstable; urgency=medium . * Backport more patches from upstream trunk. * Bump Standards-Version to 4.1.4 (no changes needed). * Bump debhelper compat to v11. * d/rules: Use "dh_missing --fail-missing". * d/control: Use Salsa repo in Vcs fields. * Use Alternatives system to provide /usr/bin/proxychains. It is worthwhile to note that I propose to use the alternatives system (as documented in Section 6 of Debian Policy) to handle the selection between original proxychains project and the new proxychains-ng project. An upload for proxychains project has been prepared [1] too and everyone are welcome to help review it, especially the review from maintainers of the original proxychains package. I have made it possible for those two packages to be uploaded independently (by specifying Breaks: relationship) but it would definitely be better if those two uploads could be made jointly. [1] https://salsa.debian.org/hosiet-guest/proxychains Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part.
RFS: pygithub/1.40a3-1 [ITP]
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "pygithub" * Package name: pygithub Version : 1.40a3-1 Upstream Author : Author : Adam DangoorVincent Jacques < vinc...@vincent-jacques.net> Jeremy Phelps < jphe...@linuxfoundation.org> * URL : https://pypi.python.org/pypi/PyGithub * License : LGPL-3+ Section : python It builds those binary packages: python-github - Access to full Github API v3 from Python2 python3-github - Access the full Github API v3 from Python3 To access further information about this package, please visit the following URL: https://mentors.debian.net/package/pygithub or https://salsa.debian.org/python-team/modules/pygithub Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/pygithub/pygithub_1.40a3-1.dsc or git clone g...@salsa.debian.org:python-team/modules/pygithub.git More information about pygithub can be obtained from http://pygithub.readthedocs.io/ Changes since the last upload: * New upstream release * Update Standards-Version from 4.1.3 to 4.1.4 version Regards, Emmanuel Arias -- Arias Emmanuel https://www.linkedin.com/in/emmanuel-arias-437a6a8a http://eamanu.com
Bug#898363: RFS: wrapperfactory.app/0.1.0-5
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "wrapperfactory.app". * Package name: wrapperfactory.app Version : 0.1.0-5 Upstream Author : Raffael Herzog* URL : N/A * License : GPL-2 Section : gnustep It builds this binary package: wrapperfactory.app - Application wrappers configuration tool for GNUstep To access further information about this package, please visit the following URL: https://mentors.debian.net/package/wrapperfactory.app Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/w/wrapperfactory.app/wrapperfactory.app_0.1.0-5.dsc Or clone the Git repository: https://salsa.debian.org/gnustep-team/wrapperfactory.app Changes since the last upload: * debian/compat: Bump to 11. * debian/rules: Rewrite for modern dh. Don't include dpatch.make. Don't generate/install the .xpm icon. Enable all hardening. Move the .gorm files to /usr/share as well. * debian/control: Run wrap-and-sort -ast. (Build-Depends): Remove dpatch and imagemagick. Bump debhelper to >= 11. Require gnustep-make >= 2.7.0-3 for noopt support. (Depends): Remove ${gnustep:Depends}; obsolete. (Vcs-Arch): Replace with Vcs-Git. (Vcs-Browser): New field. (Standards-Version): Claim compliance with 4.1.4 as of this release. * debian/source/format: Set to 3.0 (quilt). * debian/patches/00list: Rename as... * debian/patches/series: ...and update. * debian/patches/05_objdir.dpatch: Delete, no longer necessary. * debian/patches/10_libGSWrapper_libobjc.dpatch: Rename as... * debian/patches/link-libs.patch: ...and quiltify. * debian/patches/make-v2-strict.patch: New; fix FTBFS with gnustep-make in strict v2 mode, adapt code to a v2 environment (Closes: #897620). * debian/patches/gcc-warnings.patch: New; fix some GCC warnings. * debian/README.source: Delete; useless. * debian/menu: Delete as per policy requirement. * debian/manpages: New file. * debian/WrapperFactory.desktop: Set Icon to the actual file in /usr/share. Add Keywords key. * debian/watch: Replace with a dummy one as upstream's site is gone. * debian/maintscript: New; handle the move from dir to symlink. * debian/copyright: Rewrite in format 1.0.
Re: r-cran-dbi changed from arch=any to arch=all which makes it "unvisible" in unstable (Was: New version of r-bioc-genomicranges breaks autopkgtests of r-bioc-summarizedexperiment in testing)
On Thu, May 10, 2018 at 12:57:54PM -0500, Dirk Eddelbuettel wrote: > | > | ftp.debian.org is the right pseudo-package for removal (of the 0.8-1 > | packages) from unstable. > > Ok, thanks, filed as #898354. Seems that bug is somehow needed for this specific issue. However, I think I had other packages moved from Arch=any to Arch=all without any trouble. So my question is: Did something changed in the software dealing with those uploads recently or is that package in some other aspect different which might cause the observed issue? Kind regards Andreas. -- http://fam-tille.de
Re: r-cran-dbi changed from arch=any to arch=all which makes it "unvisible" in unstable (Was: New version of r-bioc-genomicranges breaks autopkgtests of r-bioc-summarizedexperiment in testing)
Hi Andreas On 10-05-18 22:08, Andreas Tille wrote: > On Thu, May 10, 2018 at 12:57:54PM -0500, Dirk Eddelbuettel wrote: >> | >> | ftp.debian.org is the right pseudo-package for removal (of the 0.8-1 >> | packages) from unstable. >> >> Ok, thanks, filed as #898354. > > Seems that bug is somehow needed for this specific issue. However, I > think I had other packages moved from Arch=any to Arch=all without any > trouble. So my question is: Did something changed in the software > dealing with those uploads recently or is that package in some other > aspect different which might cause the observed issue? You may be right, or maybe somebody behind the scene took action. I now looked up the cruft report, and r-cran-dbi is mentioned. https://ftp-master.debian.org/cruft-report-daily.txt Paul signature.asc Description: OpenPGP digital signature