Re: Looking for help towards my first Debian package (ITP#962603)
On 6/11/20 12:52 AM, Paul Wise wrote: On Wed, Jun 10, 2020 at 8:25 PM Qianqian Fang wrote: dpkg-shlibdeps: warning: symbol deflateBound used by debian/libzmat1/usr/lib/x86_64-linux-gnu/libzmat.so.1 found in none of the libraries although, I've already added zlib1g-dev to Build-Depends and zlib1g to the Depends fields, I am wondering what else do I need to add. The libzmat1.so.1 library needs to link against libz.so too. Probably this needs to be fixed upstream. hi Paul, I listed *zlib1g* in the Depends section, isn't it the provider of libz.so? https://packages.debian.org/buster/amd64/zlib1g/filelist These precompiled binaries should be removed from the upstream source repository and tarballs and always built from source at build time. If upstream refuses to do that, you should remove them from the orig.tar.gz before uploading your package. Using the Files-Excluded feature of uscan is a reasonable way to achieve that. I am the upstream author of this toolbox. I included those precompiled mex files because most of my users do not have a dev environment to compile. I will remove them from the orig tarball then. The source package name should be the same as the upstream source repository name (so zmat) and the binary package name should be named after the SONAME of the library binary (so libzmat1). Boyuan in an earlier message suggested to use libzmat instead of libzmat1. I've changed my control files on salsa https://salsa.debian.org/fangq/libzmat moving forward, to make these suggested changes, do I need to reupload the package to mentors? thanks Qianqian
Bug#962640: RFS: zmat/0.9.8 [RFS] -- a portable C-library and Octave toolbox for data compression
On 6/10/20 11:28 PM, Boyuan Yang wrote: This is because the PGP key you used to sign the source package is not trusted by default in Debian (which is natural since you are not an official member of Debian). According to the manual page of dget (dget(1)), you may use -u/--allow-unauthenticated option when calling dget to circumvent this problem. thanks Boyang for chiming in. I did some search later on, and realized the same. Uploading to mentors.debian.net is recommended but not compulsory. If you can prepare a git packging repo following the DEP-14 layout ( https://dep-team.pages.debian.net/deps/dep14), the review can also take place there. great to know. I would be appreciated if you can point me to one of the accepted git repos, it is a lot easier to follow an example regarding the folder structure and branch names. also, by using a git, is there a preference using the ones on salsa or github/gitlab is ok too? I saw your submission at https://mentors.debian.net/package/zmat . Before we start the review, I'd suggest to take a look at those automatic lintian warnings and error messages. They often indicate important problems with your packaging. There are several questions listed on mentors.debian.net/package/zmat and I believe it might be better to send them together with your RFS email (this is more likely to be read by mentors). For now I will copy them here and I will answer some of them below: thanks for pointing out, will do next time (had created a worklist of 6-7 ITPs today, will work on them one after another) For 1: unfortunately I am not an expert in dealing with Octave. Maybe someone from the Debian Science Team or Octave Group ( https://wiki.debian.org/Teams/DebianOctaveGroup) can help you with it. For 2: This will need some more closer look into your code; I may do it later. For 3: If you are _sure_ that your source code will regenerate those binary files during the building process from source code, this warning can be treated as false-positives and can be overridden. those pre-compiled binaries were included in the source package solely for the purpose of easy installation for the end users. I don't need them for this package. In a similar package I maintained for Fedora, I had to remove those unwanted binaries in the "setup" phase in the packaging file https://src.fedoraproject.org/rpms/octave-iso2mesh/blob/master/f/octave-iso2mesh.spec#_68 for Debian, do I have to modify the orig package or there is a setting that I can exclude (or remove) these files? For 4: Either one is okay in this case. BTW: I'm unsure if you are indeed going to add SONAME into the -dev package name (using libzmat1- dev instead of libzmat-dev). If you are to use libzmat1-dev and encounter SONAME bump later, the package name for development package will have to change as well, which may affect other packages that build-depend on your library (if any). got it. I fixed the lib name in this commit https://salsa.debian.org/fangq/libzmat/-/commit/fee2578b9b17356d0dbf7e0ae11fab6848aa773f I took a very quick glimpse on the library source code and it seems that you are bundling some 3rd-party libraries, including lz4 and easylzma. Debian is largely against bundling 3rdparty libraries: if possible, please consider using libraries from Debian archive instead of bundled ones. In this case, at least we need a switch to enable/disable using bundled library copy in Makefile/CMakeLists.txt. the decision was made largely for portability - a pretty big portion of the users are windows/mac users, so, letting them compile these libraries on their systems is a nightmare if I don't provide. For lz4, you are almost surely required to adjust your code to use external library (https://tracker.debian.org/pkg/lz4); for easylzma it might be okay to use the bundled one for now since Debian hasn't packaged it separately; however I personally suggest moving away from such library since this one looks largely unmaintained and hasn't seen development activity for 10+ years (https://github.com/lloyd/easylzma). Stripping the bundled libraries is not required since they are still free software and have compatible licenses with your whole project. the bundled lz4 code is actually newer than the versions included in Debian because I took it from its git repo last year. While I prefer to keep those as is but I will be happy to read the policy regarding bundling, if you can point me to, and see what I can do. I will stop here for now. Thanks for your work and maybe we could fix the issues mentioned previously first to properly shape your package. appreciated for the commends!
Re: Looking for help towards my first Debian package (ITP#962603)
On Wed, Jun 10, 2020 at 8:25 PM Qianqian Fang wrote: > dpkg-shlibdeps: warning: symbol deflateBound used by > debian/libzmat1/usr/lib/x86_64-linux-gnu/libzmat.so.1 found in none of the > libraries > > although, I've already added zlib1g-dev to Build-Depends and zlib1g to the > Depends fields, I am wondering what else do I need to add. The libzmat1.so.1 library needs to link against libz.so too. Probably this needs to be fixed upstream. > these two folders (private/octave) are precompiled binary (mex) files using > the same source codes. These precompiled binaries should be removed from the upstream source repository and tarballs and always built from source at build time. If upstream refuses to do that, you should remove them from the orig.tar.gz before uploading your package. Using the Files-Excluded feature of uscan is a reasonable way to achieve that. > 4. naming convention: did I do this correctly? can I use libzmat or zmat as > the main package name? The source package name should be the same as the upstream source repository name (so zmat) and the binary package name should be named after the SONAME of the library binary (so libzmat1). -- bye, pabs https://wiki.debian.org/PaulWise
Bug#962640: RFS: zmat/0.9.8 [RFS] -- a portable C-library and Octave toolbox for data compression
Control: owner -1 ! Control: block 962603 by 962640 Hi Qianqian, Thanks for being the upstream as well as a new packager. I am assuming that you have have read https://mentors.debian.net/intro-maintainers and know the key info about becoming a new packager. 在 2020-06-10星期三的 22:35 -0400，Qianqian Fang写道： > Package: sponsorship-requests > Severity: wishlist > > Dear mentors, > > (new contributor here. the package has been uploaded to > mentors https://mentors.debian.net/package/zmat, but showed > several warnings/errors that I need help to fix.) > > I am looking for a sponsor for my package "zmat": > To access further information about this package, please visit the > following URL: > > https://salsa.debian.org/fangq/libzmat > > Alternatively, one can download the package with dget using this > command: > > dget -x > https://mentors.debian.net/debian/pool/main/z/zmat/zmat_0.9.8-1.dsc > > ** sorry, the above command failed on my machine due to the below > error: >gpg: Can't check signature: No public key This is because the PGP key you used to sign the source package is not trusted by default in Debian (which is natural since you are not an official member of Debian). According to the manual page of dget (dget(1)), you may use -u/--allow-unauthenticated option when calling dget to circumvent this problem. Uploading to mentors.debian.net is recommended but not compulsory. If you can prepare a git packging repo following the DEP-14 layout ( https://dep-team.pages.debian.net/deps/dep14), the review can also take place there. I saw your submission at https://mentors.debian.net/package/zmat . Before we start the review, I'd suggest to take a look at those automatic lintian warnings and error messages. They often indicate important problems with your packaging. There are several questions listed on mentors.debian.net/package/zmat and I believe it might be better to send them together with your RFS email (this is more likely to be read by mentors). For now I will copy them here and I will answer some of them below: == I'd like to have someone take a look, and help me figure out some of the remaining issues. Specifically, here are the things I want to fix 1. one of the 3 subpackages is an Octave toolbox (as a mex file). Although the binary was compiled during the packaging process, I wasn't able to find a template to assemble the octave package. can someone point to me if there is a template (for a similar mex-based toolbox) for octave? 2. when running debuild, I got the below warning dpkg-shlibdeps: warning: symbol deflateBound used by debian/libzmat1/usr/lib/x86_64-linux-gnu/libzmat.so.1 found in none of the libraries although, I've already added zlib1g-dev to Build-Depends and zlib1g to the Depends fields, I am wondering what else do I need to add. 3. I have two errors from lintian: E: zmat source: source-is-missing private/zipmat.mexa64 E: zmat source: source-is-missing octave/linux64/zipmat.mex these two folders (private/octave) are precompiled binary (mex) files using the same source codes. They are not installed anyways, I am wondering if I can set a flag to skip these files (or run a pre-build script to remove them?) 4. naming convention: did I do this correctly? can I use libzmat or zmat as the main package name? if you can provide additional feedback on this package, I am very much appreciated. == For 1: unfortunately I am not an expert in dealing with Octave. Maybe someone from the Debian Science Team or Octave Group ( https://wiki.debian.org/Teams/DebianOctaveGroup) can help you with it. For 2: This will need some more closer look into your code; I may do it later. For 3: If you are _sure_ that your source code will regenerate those binary files during the building process from source code, this warning can be treated as false-positives and can be overridden. For 4: Either one is okay in this case. BTW: I'm unsure if you are indeed going to add SONAME into the -dev package name (using libzmat1- dev instead of libzmat-dev). If you are to use libzmat1-dev and encounter SONAME bump later, the package name for development package will have to change as well, which may affect other packages that build-depend on your library (if any). I took a very quick glimpse on the library source code and it seems that you are bundling some 3rd-party libraries, including lz4 and easylzma. Debian is largely against bundling 3rdparty libraries: if possible, please consider using libraries from Debian archive instead of bundled ones. In this case, at least we need a switch to enable/disable using bundled library copy in Makefile/CMakeLists.txt. For lz4, you are almost surely required to adjust your code to use external library (https://tracker.debian.org/pkg/lz4); for easylzma it might be okay to use the bundled one for now since Debian hasn't packaged it separately; however I personally suggest moving
Bug#962640: RFS: zmat/0.9.8 [RFS] -- a portable C-library and Octave toolbox for data compression
Package: sponsorship-requests Severity: wishlist Dear mentors, (new contributor here. the package has been uploaded to mentors https://mentors.debian.net/package/zmat, but showed several warnings/errors that I need help to fix.) I am looking for a sponsor for my package "zmat": * Package name : zmat Version : 0.9.8 Upstream Author : Qianqian Fang (fangqq at gmail.com) * URL : https://github.com/fangq/zmat * License : GPLv3+ * Vcs : https://github.com/fangq/zmat Section : libs It builds those binary packages: libzmat1 - a portable C library for stream-level compression libzmat1-dev - the library header files and samples to use libzmat octave-zmat - an Octave toolbox for array compression To access further information about this package, please visit the following URL: https://salsa.debian.org/fangq/libzmat Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/z/zmat/zmat_0.9.8-1.dsc ** sorry, the above command failed on my machine due to the below error: gpg: Can't check signature: No public key need some help to go through a submission process once, first time contributor. Changes since the last upload: * Initial release. (Closes: #962603) -- Qianqian Fang Mon, 08 Jun 2020 10:30:07 -0400 Regards,
Bug#961179: RFS: inkscape-textext/1.0.1-1 [ITP] -- Re-editable LaTeX graphics for Inkscape
On 2020-06-10 08:53, Boyuan Yang wrote: > Signed tags/tarballs don't matter; they are totally optional. Your > debian/watch file is using mode=git, which is totally fine; however, > you may also opt to monitor the github releases page like other Debian > packages. Understood. I've left it untouched, in the hope that upstream will sign their git tags. > Just one last issue: you did not document the license information of > textext/texoutparse.py; this file is licensed under the MIT License > (seems to be the Expat variant), not BSD-3-Clause. Please update this > information accordingly. After that, I think I can help to upload this > package. Whoops. I've fixed that, and uploaded the changes to mentors and salsa. Thanks for your time, Antonio
Bug#962091: RFS: xine-ui/0.99.12-1 [QA] -- xine video player, user interface
Hi, and thanks for the review. lør. 6. jun. 2020 kl. 11:41 skrev Adrian Bunk : > > Control: tags -1 moreinfo > > On Wed, Jun 03, 2020 at 08:04:45AM +, Håvard Flaget Aasen wrote: > >... > > Changes since the last upload: > >... > >* d/rules > > - Change to dh-sequence > >... > >* d/control > >... > > - Remove unnecessary Depends field > >... > > This was necessary, it was just broken by your debian/rules rewrite. > This RC regression can easily be reproduced with aaxine. > > For the debian/rules change, please verify that the changed package > does not contain any unexpected changes from the original one. > This means first understanding what the old debian/rules did. > I can immediately find two things that were done in the old debian/rules > but are missing in the new one. > I re added the dependency fields in d/control, dh_xine, and dh_compress targets in d/rules, which shouldn't have been removed, thanks for spotting that. I also added back dh_installchangelog, I'm still not sure if anything is actually using this symlink, but it is consistent with the previous version. > >* Add fix_spelling_error.patch > >... I've updated the .pot file and .po files as well, I believe that should fix it. > > This is a translated string, such a change breaks all translations of > this string. > > > Regards, > > Håvard > > cu > Adrian Regards, Håvard
Looking for help towards my first Debian package (ITP#962603)
hi there, I am learning my way towards creating my first Debian package. The specific package I am working on right now is in this ITP bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962603 at this point, I've uploaded a set of packaging files to salsa https://salsa.debian.org/fangq/libzmat I'd like to have someone take a look, and help me figure out some of the remaining issues. Specifically, here are the things I want to fix 1. one of the 3 subpackages is an Octave toolbox (as a mex file). Although the binary was compiled during the packaging process, I wasn't able to find a template to assemble the octave package. can someone point to me if there is a template (for a similar mex-based toolbox) for octave? 2. when running debuild, I got the below warning *dpkg-shlibdeps: warning: symbol deflateBound used by debian/libzmat1/usr/lib/x86_64-linux-gnu/libzmat.so.1 found in none of the libraries* although, I've already added zlib1g-dev to Build-Depends and zlib1g to the Depends fields, I am wondering what else do I need to add. 3. I have two errors from lintian: *E: zmat source: source-is-missing private/zipmat.mexa64** **E: zmat source: source-is-missing octave/linux64/zipmat.mex* these two folders (private/octave) are precompiled binary (mex) files using the same source codes. They are not installed anyways, I am wondering if I can set a flag to skip these files (or run a pre-build script to remove them?) 4. naming convention: did I do this correctly? can I use libzmat or zmat as the main package name? if you can provide additional feedback on this package, I am very much appreciated. thanks Qianqian
Bug#962617: RFS: audiolink/0.05-4 [ITA] -- makes managing and searching for music easier
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "audiolink" * Package name: audiolink Version : 0.05-4 Upstream Author : Amit Shah * URL : http://audiolink.sourceforge.net/ * License : GPL-2 * Vcs : https://salsa.debian.org/debian/audiolink Section : sound It builds those binary packages: audiolink - makes managing and searching for music easier To access further information about this package, please visit the following URL: https://mentors.debian.net/package/audiolink Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/a/audiolink/audiolink_0.05-4.dsc Changes since the last upload: * New maintainer. (Closes: #831544) * Using new DH level format. Consequently: - debian/compat: removed. - debian/control: changed from 'debhelper' to 'debhelper-compat' in Build-Depends field and bumped level to 13. * debian/control: - Added 'Rules-Requires-Root: no' to source stanza. - Created VCS fields. - Bumped Standards-Version to 4.5.0. * debian/copyright: - Migrated to new format 1.0. - Updated all data. * debian/patches/01_debian-changes.patch: - Renamed the numeric prefix. - Updated header and data. * debian/patches/02_fix-spelling-error.patch: fix spelling error in manpage. * debian/patches/series: changed order application. * debian/README.Debian: drop. * debian/salsa-ci.yml: created to perform Salsa CI tests. * debian/tests/control: created to perform CI tests. * debian/upstream/metadata: created. * debian/watch: created. Regards, Gleisson Jesuino Joaquim Cardoso.
Bug#962600: RFS: etktab/3.2-11 [ITA] -- ASCII guitar tab editor
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "etktab": * Package name: etktab Version : 3.2-11 Upstream Author : Jason Sonnenschein * URL : https://sourceforge.net/projects/etktab/ * License : Artistic-1.0 * Vcs : https://salsa.debian.org/debian/etktab Section : sound It builds those binary packages: etktab - ASCII guitar tab editor To access further information about this package, please visit the following URL: https://mentors.debian.net/package/etktab Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/e/etktab/etktab_3.2-11.dsc Changes since the last upload: * New maintainer. (Closes: #812615) Regards, -- Fabio Augusto De Muzio Tobich
Bug#962598: RFS: mpack/1.6-15 [ITA] -- tools for encoding/decoding MIME messages
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "mpack": * Package name: mpack Version : 1.6-15 Upstream Author : Carnegie Mellon University * URL : ftp://ftp.andrew.cmu.edu/pub/mpack/ * License : MIT * Vcs : https://salsa.debian.org/debian/mpack Section : mail It builds those binary packages: mpack - tools for encoding/decoding MIME messages To access further information about this package, please visit the following URL: https://mentors.debian.net/package/mpack Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/m/mpack/mpack_1.6-15.dsc Changes since the last upload: * New maintainer. (Closes: #925069) Regards, -- Fabio Augusto De Muzio Tobich pgp6tuV5D6zJf.pgp Description: PGP signature
Bug#961179: RFS: inkscape-textext/1.0.1-1 [ITP] -- Re-editable LaTeX graphics for Inkscape
在 2020-06-09星期二的 21:58 -0600，Antonio Russo写道： > This essentially the same as [1] BTS 961741, and I've pushed the fix > to debian-mentors [2] and salsa [3]. I apologize for this, I did not > push these changes out earlier because I (apparently incorrectly) > assumed no one was going to look at my package. > > I still have not heard back from upstream regarding signed git tags > [4]. Signed tags/tarballs don't matter; they are totally optional. Your debian/watch file is using mode=git, which is totally fine; however, you may also opt to monitor the github releases page like other Debian packages. Just one last issue: you did not document the license information of textext/texoutparse.py; this file is licensed under the MIT License (seems to be the Expat variant), not BSD-3-Clause. Please update this information accordingly. After that, I think I can help to upload this package. -- Regards, Boyuan Yang
Bug#962552: marked as done (RFS: palettable/3.3.0-1 [ITP] -- library of color palettes for Python (Python 3))
Your message dated Wed, 10 Jun 2020 16:37:36 +0300 with message-id and subject line Re: Bug#962552: RFS: palettable/3.3.0-1 [ITP] -- library of color palettes for Python (Python 3) has caused the Debian Bug report #962552, regarding RFS: palettable/3.3.0-1 [ITP] -- library of color palettes for Python (Python 3) 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.) -- 962552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962552 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 "palettable" * Package name: palettable Version : 3.3.0-1 Upstream Author : Matt Davis * URL : https://github.com/jiffyclub/palettable * License : MIT * Vcs : https://salsa.debian.org/python-team/modules/palettable Section : python It builds those binary packages: python3-palettable - library of color palettes for Python (Python 3) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/palettable Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/palettable/palettable_3.3.0-1.dsc Changes since the last upload: * Initial release (Closes: #962340) Regards, -- Emmanuel Arias 0xFA9DEC5DE11C63F1.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- On 2020-06-10 16:03, Emmanuel Arias wrote: > Sorry my error. > > I've just make the change. Uploaded. Thanks for your contribution! Best, Andrius--- End Message ---
Bug#962552: RFS: palettable/3.3.0-1 [ITP] -- library of color palettes for Python (Python 3)
Hi Andrius, Sorry my error. I've just make the change. I look your change on the repo, thanks! Cheers, Emmanuel
Bug#962044: marked as done (RFS: xmlstarlet/1.6.1-2.1 [NMU] -- command line XML toolkit)
Your message dated Wed, 10 Jun 2020 12:10:51 +0200 with message-id <20200610101051.ga1963...@mapreri.org> and subject line Re: Bug#962044: RFS: xmlstarlet/1.6.1-2.1 [NMU] -- command line XML toolkit has caused the Debian Bug report #962044, regarding RFS: xmlstarlet/1.6.1-2.1 [NMU] -- command line XML toolkit 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.) -- 962044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962044 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 "xmlstarlet" * Package name: xmlstarlet Version : 1.6.1-2.1 Upstream Author : Mikhail Grushinskiy * URL : http://xmlstar.sourceforge.net/ * License : Expat * Vcs : https://anonscm.debian.org/cgit/collab-maint/xmlstarlet.git Section : text The source builds the following binary packages: xmlstarlet - command line XML toolkit To access further information about this package, please visit the following URL: https://mentors.debian.net/package/xmlstarlet Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/x/xmlstarlet/xmlstarlet_1.6.1-2.1.dsc Changes since the last upload: * Non-maintainer upload. * Use pkg-config to find the libxml2, libxslt and libexslt libraries (Closes: #948791, #949513). * debian/changelog: Remove trailing whitespace. * debian/control: - Sort Build-Depends list. - Drop build-dependencies on autotools-dev and dh-autoreconf. The autoreconf sequence is enabled by default in debhelper >= 10. - Build-Depend on pkg-config. - Use debhelper-compat v13 instead of legacy debian/compat. - Raise Standards-Version to 4.5.0 from 3.9.8 (no changes needed). - Add Rules-Requires-Root: no. * debian/copyright: Use secure HTTP protocol in the Format field. * debian/rules: - Drop '--with autoreconf' with change to debhelper >= 10. - Set 0644 permissions on xmlstarlet-pad.xml and xmlstarlet-xsa.xml. - Do not install upstream ChangeLog. The file is empty. While it can be argued that many of these changes are out of bounds for an NMU, the state of the existing package is a real concern. I believe a clean-up is warranted. Regards, -- Hugh McMaster --- End Message --- --- Begin Message --- On Tue, Jun 02, 2020 at 11:16:47PM +1000, Hugh McMaster wrote: > dget -x > https://mentors.debian.net/debian/pool/main/x/xmlstarlet/xmlstarlet_1.6.1-2.1.dsc uploaded! > While it can be argued that many of these changes are out of bounds > for an NMU, the state of the existing package is a real concern. I > believe a clean-up is warranted. The problem is that the maintainer is not MIA, so indeed some of those changes are somewhat out of scope. Nevertheless, I think they are fine enough, and I've uploaded them to DELAYED/15. Now, microsoft decided to ban the IP range my mail sever lives at, so I'm now unable to mail you directly… Just so you know… :\ -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature --- End Message ---
