Bug#1050814: RFS: qbootctl/0.1.2-1 [ITP] -- utility to control Quacomm A/B boot slots
Thanks, Dmitry, for the prompt fix/update! On Sat, Sep 2, 2023 at 2:09 PM Dmitry Baryshkov wrote: > > On Sat, 2 Sept 2023 at 11:23, Roger Shimizu wrote: > > Thanks for your ITP & RFS! > > > > Some nitpicking: > > * debian/README.Debian: > > Please add more description, or remove this file. > > Ack. I've updated the package to drop this file (and also to include > the qbootctl.service file to mark the boot as successful > automatically). > > > * debian/include/scsi/scsi_bsg_ufs.h > > This header is not upstreamed yet? > > This header comes from the Linux kernel itself. It is a part of uABI. > > > Is it possible to use existing debian packaged header? > > Unfortunately, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050368 Above ticket is in pending status, so the next upload should fix the issue. So please update this package accordingly then. > > * Do you know whether this package works for QCOM LE / LU baseline systems? > > Most likely, the Linux kernel API and the bootloader are the same. But > I don't think anybody tested it with LE / LU. OK. We can test it easily when it hit Debian archive. I'll upload it later. But hope you can also fix the lintian in the future: W: qbootctl: no-manual-page [usr/bin/qbootctl] I: qbootctl: package-supports-alternative-init-but-no-init.d-script [lib/systemd/system/qbootctl.service] I: qbootctl: systemd-service-file-missing-documentation-key [lib/systemd/system/qbootctl.service] Thank you for your contribution to Debian! Cheers, Roger > > -- > With best wishes > Dmitry
Bug#1050814: RFS: qbootctl/0.1.2-1 [ITP] -- utility to control Quacomm A/B boot slots
control: owner -1 ! control: tags -1 +moreinfo Dear Dmitry, Thanks for your ITP & RFS! Some nitpicking: * debian/README.Debian: Please add more description, or remove this file. * debian/include/scsi/scsi_bsg_ufs.h This header is not upstreamed yet? Is it possible to use existing debian packaged header? * Do you know whether this package works for QCOM LE / LU baseline systems? Cheers, Roger
Bug#1001757: RFS: google-android-installers/1639148153 [NMU] -- Google's Android SDK
Dear Fab, Thanks for your work! I already merged your MR to debian/exp branch. Since there're 128 commits / patches for your one MR, it's actually not possible for me to review deeply. So I'd prefer to upload to experimental first. Your upload to mentors seems to have some more commits / patches than MR. So please make another MR to release all your patches to salsa. After that I can sponsor the upload to experimental. Cheers, Roger On Thu, May 19, 2022 at 6:59 PM Roger Shimizu wrote: > > Dear Bastian, > > Thanks for the ping! > I'll check this package later. > > Cheers, > Roger > > On Thu, May 19, 2022 at 2:09 AM Bastian Germann wrote: > > > > Hi Roger and List, > > > > Can you please comment on this and your plans on the > > google-android-installers package? > > This is from sponsorship-requests and nobody cared about it in months. > > I am not familiar with the Android build system. > > > > Hans-Christoph has commented on the Salsa MR to possibly make Fab Stz the > > new package maintainer. > > > > Thanks, > > Bastian > > > > On Wed, 15 Dec 2021 14:13:32 +0100 Fab Stz wrote: > > > I already sent an email on 21/Oct & 19/Nov to android-tools- > > > de...@lists.alioth.debian.org, Roger Shimizu > > concerning a > > > merge request for that package. I haven't seen an anwser yet. > > > > > > Message was: > > > Hello everybody, > > > > > > I updated the google-android-installers source package and created a > > merge > > > request available here: > > > > > > > > https://salsa.debian.org/android-tools-team/google-android-installers/-/merge_requests/3 > > > > > > It automatically builds packages for almost all SDK components described > > in > > > Google's https://dl.google.com/android/repository/repository2-1.xml > > > > > > Among the covered components there is: build-tools, platforms, > > platform-tools, > > > cmdline-tools, emulator, ndk, sources. > > > > > > Could you have a look and give any feedback please? > > > > > > Once merged & approved, this is ready to be reused with the other SDK > > > repositories of Google. It will permit to create source packages for > > these > > > components: sys-img, add-on, extras...
Bug#1001757: RFS: google-android-installers/1639148153 [NMU] -- Google's Android SDK
Dear Bastian, Thanks for the ping! I'll check this package later. Cheers, Roger On Thu, May 19, 2022 at 2:09 AM Bastian Germann wrote: > > Hi Roger and List, > > Can you please comment on this and your plans on the > google-android-installers package? > This is from sponsorship-requests and nobody cared about it in months. > I am not familiar with the Android build system. > > Hans-Christoph has commented on the Salsa MR to possibly make Fab Stz the new > package maintainer. > > Thanks, > Bastian > > On Wed, 15 Dec 2021 14:13:32 +0100 Fab Stz wrote: > > I already sent an email on 21/Oct & 19/Nov to android-tools- > > de...@lists.alioth.debian.org, Roger Shimizu concerning a > > merge request for that package. I haven't seen an anwser yet. > > > > Message was: > > Hello everybody, > > > > I updated the google-android-installers source package and created a merge > > request available here: > > > > > https://salsa.debian.org/android-tools-team/google-android-installers/-/merge_requests/3 > > > > It automatically builds packages for almost all SDK components described in > > Google's https://dl.google.com/android/repository/repository2-1.xml > > > > Among the covered components there is: build-tools, platforms, > platform-tools, > > cmdline-tools, emulator, ndk, sources. > > > > Could you have a look and give any feedback please? > > > > Once merged & approved, this is ready to be reused with the other SDK > > repositories of Google. It will permit to create source packages for these > > components: sys-img, add-on, extras...
Re: How to ignore some versions for watch file?
Dear Eriberto, and Sergio, Really thanks for your help! Yes, "downgrade" 2019 to 0.2019, is the perfect solution for my case. And searching for \. by force seems to be a more generic solution. I tried both, and both work as expected. And through this practise, I understand the syntax for watch file deeper than before. Very appreciated! > [1] https://wiki.debian.org/debian/watch > [2] > http://eriberto.pro.br/blog/2013/10/07/how-to-write-a-good-debianwatch-easily/ Eriberto maybe you can add this tip to your blog post [2]. And I'll try to add it to wiki [1] later. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
How to ignore some versions for watch file?
Dear mentors list, I maintain a package that previously used vMMDD as version, but now changed to v1.y.z - https://tracker.debian.org/pkg/shadowsocks-v2ray-plugin - https://github.com/shadowsocks/v2ray-plugin/tags So my question is how to ignore the old version vMMDD, and only detect v1.y.z as latest version for d/watch file? BTW. I already read a few posts regarding on d/watch file [1][2], but still didn't find a proper solution. [1] https://wiki.debian.org/debian/watch [2] http://eriberto.pro.br/blog/2013/10/07/how-to-write-a-good-debianwatch-easily/ Thank you! Cheers. -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#966415: RFS: pixz/1.0.7-1 -- parallel, indexing XZ compressor/decompressor
Dear Leon, Git repo created on salsa, with your account as maintainer: - https://salsa.debian.org/debian/pixz I also find one with some old gits, maybe you can create from that: - https://salsa.debian.org/bremner/pixz Usually I do such task by: gbp import-dscs --debsnap --author-is-committer --author-date-is-committer-date --create-missing-branches Good luck! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#966415: RFS: pixz/1.0.7-1 -- parallel, indexing XZ compressor/decompressor
Dear Leon, Thanks for your package update! On Tue, Jul 28, 2020 at 6:51 PM Leon Marz wrote: > https://mentors.debian.net/package/pixz/ > > Alternatively, one can download the package with dget using this command: > > dget -x https://mentors.debian.net/debian/pool/main/p/pixz/pixz_1.0.7-1.dsc > > Changes since the last upload: > > pixz (1.0.7-1) unstable; urgency=medium > . >* New upstream release >* Drop all patches since they are included in the upstream release As I stated in previous RFS: > But it's better if you can use git and push your packaging to > somewhere, such as salsa, or github. Could you kindly address above this time? If you need someone to create git repo on salsa, just let me know. Thank you! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Re: Understand Debian Keyring
On Mon, Jan 6, 2020 at 12:02 AM Tong Sun wrote: > > On Sat, Jan 4, 2020 at 7:56 PM Paul Wise wrote: > > > > How to delete my package from ftp.upload.debian.org? > > > > Usually that means using dcut (from devscripts), but in this case the > > package is no longer in the upload queue so you cannot remove it from > > there. > > . . . > > Thanks a lot for the explanation. > > Now, before I redo the upload (and get it stuck again), let me try to > understand the situation -- > > The reason it was stuck might be because my key was *considered* > expired. The problem is, I renewed it two or three weeks ago, and sent > it to pgp & > Ubuntu key servers. > > The mentors.debian.net accepted my (renewed) key, but ftp-master > didn't. Might that my key on ftp-master.debian.org is somehow not > refreshed? Anyway, I tried to fix the issue by refreshing my key to > keyring.debian.org. However, on reading https://keyring.debian.org/, I > stated to wonder that if it good enough *now*: Yes, mentors.debian.net may accept your key update in short time, but for debian keyring it's not the same case. > > We will include your changed key in our next keyring push (which happens > > approx. monthly). > > What does it really mean? Shall I need to wait a month before uploading again? Yes, and keyring updates "monthly" means it may take about two months for your key update in the worst case. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Re: Wrongly sent ITP
On Fri, Mar 22, 2019 at 1:26 AM Shreyas Bapat wrote: > > Hi > > I was issuing an ITP for einsteinpy, and by mistake, I pressed "Enter" and > the mail got sent partially, without much details in it. The bug number for > the same is Bug#925239. I have issued another ITP with full details in it. > I am sorry for my mistake. Can the Bug#925239 be closed in favor of newly > issued ITP(Bug#925241)? > I am really sorry for the inconvenience caused. Thanks for your interest in contribution to Debian! Don't worry. You can do it by yourself. Simply send a email to 925239-done@bugs dot debian dot org State your reason in the email body. For more information, you can visit: - https://www.debian.org/Bugs/Developer#closing Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#909949: RFS: android-platform-system-extras/8.1.0+r23-1 (experimental)
Dear Kai-Chung, On Wed, Oct 3, 2018 at 2:05 AM 殷啟聰 | Kai-Chung Yan wrote: > > Thanks for the sponsor again, Roger! > > I did push the changes already, check > <https://salsa.debian.org/android-tools-team/android-platform-system-extras/compare/debian%2F7.0.0+r33-1...master>. > > Or do you mean you want a dedicated merge request so you can leave comments > their so that in a more sophisticated way? That's probably not viable... I did a quick review. Since you removed a few stuff from upstream, such as unused test data, jar, etc, the upstream source need to be called "repack", or debian source [1]. And all removed stuff need to be listed in debian/copyright. (I see you already handled this.) In this way, the repack can be done automatically by uscan. (nice to do, but not must) [1] https://wiki.debian.org/BenFinney/software/repack The problem is you didn't mention +ds or +repack in version in d/changelog. I guess the version need to be changed to 8.1.0+r23+ds-1 or 8.1.0+r23+repack-1. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#909949: RFS: android-platform-system-extras/8.1.0+r23-1 (experimental)
On Sun, Sep 30, 2018 at 10:45 PM 殷啟聰 | Kai-Chung Yan wrote: > > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "android-platform-system-extras" Thanks for your work! Could you push your commits to salsa? It will make the review easier. You can push to a tentative branch if you're not quite sure. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#909305: RFS: android-platform-system-core/1:8.1.0+r23-1~stage1.1
On Sat, Sep 22, 2018 at 7:16 PM, 殷啟聰 | Kai-Chung Yan wrote: > Hello Roger, >> -1~stageX means preparing version -1. > > Well, it means preparing a version that is earlier than -1. >> Hope you can address some lintian on next upload: >> - >> http://debomatic-armel.debian.net/distribution#experimental/android-platform-system-core/8.1.0+r23-1~stage1.1/lintian > > Most of the Lintian warnings are too trivial and of low priority. Getting the > Oreo SDK ready as fast as possible is my current goal. But there are some > warnings that are actually false-positive, e.g. hardening and > ldcondif-trigger. We only override "E" tags and leave the rest as is so they > serve as a reminder of such bugs from the build-tools. Yes, but for case of ~stageX in version, you need to just change 1 byte or 2 to comfort lintian. Why not? >> Just uploaded to experimental. > > Thank you for the sponsor! > > Alas, MIPS still FTBFS... I finally fixed the bug and tested it on mips64el. > Could you please upload it once again? It should be on the same URL on > . Thanks! This time seems OK for mips* - http://debomatic-mips.debian.net/distribution#experimental/android-platform-system-core/8.1.0+r23-1~stage1.2/buildlog - http://debomatic-mipsel.debian.net/distribution#experimental/android-platform-system-core/8.1.0+r23-1~stage1.2/buildlog - http://debomatic-mips64el.debian.net/distribution#experimental/android-platform-system-core/8.1.0+r23-1~stage1.2/buildlog Uploaded. Thanks for your contribution! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#909305: RFS: android-platform-system-core/1:8.1.0+r23-1~stage1.1
On Fri, Sep 21, 2018 at 7:58 PM, 殷啟聰 | Kai-Chung Yan wrote: > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "android-platform-system-core" > > * Package name: android-platform-system-core > Version : 1:8.1.0+r23-1~stage1.1 Good to see this package! I just quickly checked the version on salsa, and find d/changelog is not uploaded yet. $ git diff --name-status 8b1e66f8 42202fb6 debian/ Mdebian/append2simg.mk Mdebian/control Mdebian/libadb.mk Mdebian/libcrypto_utils.mk Mdebian/rules Mdebian/simg2img.mk Mdebian/simg2simg.mk So could you change the version to 1:8.1.0+r23-1~stage2 ? Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#897642: RFS: gpgme1.0/1.11.1-1~bpo9+1
On Sun, Sep 9, 2018 at 3:21 PM, Carsten Schoenert wrote: > Hi, > > Am 09.09.18 um 07:55 schrieb Roger Shimizu: > ... >> Both gpgme1.0 and libgpg-error are already in backports NEW queue. >> So I'm closing this ticket. >> >>> Thank you>> Looking into why you did a gnupg2 backport I probably should use >>> that too, to support newer ECC keys.> >> Please do so. >> Thanks for your work! > > please talk before doing a backport to the release team if they would > accept in circumstances gnupgp2 within a point release, supporting > recent gpg key material is something which can also being seen as a > security fix, and that's the point releases are for, not backports. > Given that Stretch is quite young in a possible lifespan of four years I > bet gnupg2 will need at one for Stretch obviously. And I'm not the maintainer of src:gnupg2. I just want to help Bug#906545, and upstream maintainer says patching stable version may be hard and backport may be easier. backports should be no harm since it uses ~bpo in version. So it's still feasible if pkg maintainer and release team decide to include a new major version into point release. > It's already (to?) late for enigmail e.g., Thunderbird 60.0 has a Breaks > on Enigmail < 2 and enigmail will need gnupg2. Thunderbird 60.0 has > taken the NEW queue for s-s a few days ago. Time is passing by ... > > So people can use the recent Enigmail extension from > https://addons.thunderbird.net/ of course but don't get support for new > keys I guess as s-s don't get a recent enigmail package which is > requiring gnupg2. > > Note: I'm not that deep in the impact of an introduction of gnupg2, so I > might have not a realistic view on this all. I just see that we once > again have made our self a hard time with the release of a new ESR > version of Thunderbird like for 45 and 52 in the past. Did you report this situation to release team? I think if it's necessary and release team agree, gnupg2 maintainer can certainly help. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#897642: RFS: gpgme1.0/1.11.1-1~bpo9+1
[ Resend for the record with the lists below ] + debian-backports@l.d.o + pkg-gnupg-maint@l.alioth.d.o On Sat, Sep 1, 2018 at 11:15 PM, Jacob Adams wrote: > control: tag -1 -moreinfo > > On Sep 1, 2018, at 04:49, Roger Shimizu wrote: > > control: tag -1 +moreinfo > > Dear Jacob, > > On Fri, May 4, 2018 at 3:27 AM, Jacob Adams wrote: > > Package: sponsorship-requests > > Severity: normal > > > Dear mentors, > > > I am looking for a sponsor for my package "gpgme1.0" > > > Thanks for your interest in contribution to debian! > > Changes since the last upload: > > > gpgme1.0 (1.11.1-1~bpo9+1) stretch-backports; urgency=medium > > > * Rebuild for stretch-backports. > > > -- Jacob Adams Thu, 26 Apr 2018 13:13:54 -0400 > > > > This package will also require libgpgerror, which you can find here: > > > https://mentors.debian.net/package/libgpg-error > > > https://mentors.debian.net/debian/pool/main/libg/libgpg-error/libgpg-error_1.29-4~bpo9+1.dsc > > > It already has an RFS: #897045 > > > I would like to be able to use the latest version of GPGME in my GSoC > > 2018 project. In order to do that I would prefer to use a backport as > > the PGP Clean Room CD is based off of stretch. > > > I see the project seems already released as beta [1], so maybe there's > no need to do this backports upload? > > > My project does require a newer version of GPGME than is shipped in stretch. > However, I didn’t want to wait on the backport, so I’ve been including the > deb files directly in my build: > https://salsa.debian.org/tookmund-guest/make-pgp-clean-room/tree/master/resources/config/packages.chroot > > > And what's the benefit for this backports pkg? Any new feature or > bugfix you're particularly interested in? > > > There has been significant improvement in GPGME’s python binding since > stretch, and my project relies on these features, such as the new key > generation function. > > It would be nice to be able to pull these packages from backports instead of > including them directly. I compiled this pkg under stretch, and meet the following error. cJSON.c:45:20: fatal error: gpgrt.h: No such file or directory # include ^ I see you updated libgpg-error to 1.29, so I tried to compile with latest backported sid version, 1.32, and it succeeded. So I updated D-B on libgpg-error to >= 1.29. I uploaded this backported pkg to DELAYED/6. So If you don't like the backports upload, just kindly cancel it. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#897642: RFS: gpgme1.0/1.11.1-1~bpo9+1
On Sat, Sep 1, 2018 at 11:15 PM, Jacob Adams wrote: > control: tag -1 -moreinfo > > On Sep 1, 2018, at 04:49, Roger Shimizu wrote: > > control: tag -1 +moreinfo > > Dear Jacob, > > On Fri, May 4, 2018 at 3:27 AM, Jacob Adams wrote: > > Package: sponsorship-requests > > Severity: normal > > > Dear mentors, > > > I am looking for a sponsor for my package "gpgme1.0" > > > Thanks for your interest in contribution to debian! > > Changes since the last upload: > > > gpgme1.0 (1.11.1-1~bpo9+1) stretch-backports; urgency=medium > > > * Rebuild for stretch-backports. > > > -- Jacob Adams Thu, 26 Apr 2018 13:13:54 -0400 > > > > This package will also require libgpgerror, which you can find here: > > > https://mentors.debian.net/package/libgpg-error > > > https://mentors.debian.net/debian/pool/main/libg/libgpg-error/libgpg-error_1.29-4~bpo9+1.dsc > > > It already has an RFS: #897045 > > > I would like to be able to use the latest version of GPGME in my GSoC > > 2018 project. In order to do that I would prefer to use a backport as > > the PGP Clean Room CD is based off of stretch. > > > I see the project seems already released as beta [1], so maybe there's > no need to do this backports upload? > > > My project does require a newer version of GPGME than is shipped in stretch. > However, I didn’t want to wait on the backport, so I’ve been including the > deb files directly in my build: > https://salsa.debian.org/tookmund-guest/make-pgp-clean-room/tree/master/resources/config/packages.chroot > > > And what's the benefit for this backports pkg? Any new feature or > bugfix you're particularly interested in? > > > There has been significant improvement in GPGME’s python binding since > stretch, and my project relies on these features, such as the new key > generation function. > > It would be nice to be able to pull these packages from backports instead of > including them directly. I compiled this pkg under stretch, and meet the following error. cJSON.c:45:20: fatal error: gpgrt.h: No such file or directory # include ^ I see you updated libgpg-error to 1.29, so I tried to compile with latest backported sid version, 1.32, and it succeeded. So I updated D-B on libgpg-error to >= 1.29. I uploaded this backported pkg to DELAYED=6. So If you don't like the backports upload, just kindly cancel it. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#897642: RFS: gpgme1.0/1.11.1-1~bpo9+1
control: tag -1 +moreinfo Dear Jacob, On Fri, May 4, 2018 at 3:27 AM, Jacob Adams wrote: > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "gpgme1.0" Thanks for your interest in contribution to debian! > Changes since the last upload: > > gpgme1.0 (1.11.1-1~bpo9+1) stretch-backports; urgency=medium > > * Rebuild for stretch-backports. > > -- Jacob Adams Thu, 26 Apr 2018 13:13:54 -0400 > > > This package will also require libgpgerror, which you can find here: > > https://mentors.debian.net/package/libgpg-error > > https://mentors.debian.net/debian/pool/main/libg/libgpg-error/libgpg-error_1.29-4~bpo9+1.dsc > > It already has an RFS: #897045 > > I would like to be able to use the latest version of GPGME in my GSoC > 2018 project. In order to do that I would prefer to use a backport as > the PGP Clean Room CD is based off of stretch. I see the project seems already released as beta [1], so maybe there's no need to do this backports upload? And what's the benefit for this backports pkg? Any new feature or bugfix you're particularly interested in? BTW. I just uploaded gnupg 2.2 to stretch-backports, to fix #906545 [2]. And I see your RFS. [1] https://tookmund.com/2018/07/pgp-clean-room-beta [2] https://bugs.debian.org/906545 Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Re: How to get debian ci test passed for proxy application
Dear Antonio, Thanks for your informative email! With the upload last night, I confirm now the issue got solved [0]. [0] https://ci.debian.net/data/autopkgtest/unstable/amd64/s/shadowsocks-libev/20171212_175154/log.gz On Tue, Dec 5, 2017 at 3:14 AM, Antonio Terceiro <terce...@debian.org> wrote: > > You do not need anything Restrictions: to be able to start a daemon or > listen on a local TCP port. Thanks for your confirmation! Now I removed the Restrictions for isolation-*. > | $ ./tests/test.sh > | running test: python tests/test.py -c tests/aes.json > | 2017-12-04 16:07:02 INFO: UDP relay enabled > | 2017-12-04 16:07:02 INFO: initializing ciphers... aes-256-cfb > | 2017-12-04 16:07:02 ERROR: bind: Address already in use > | 2017-12-04 16:07:02 ERROR: bind() error > | 2017-12-04 16:07:02 INFO: initializing ciphers... aes-256-cfb > | 2017-12-04 16:07:02 INFO: listening at 127.0.0.1:1081 > | 2017-12-04 16:07:02 INFO: initializing ciphers... aes-256-cfb > | 2017-12-04 16:07:02 INFO: UDP relay enabled > | 2017-12-04 16:07:02 INFO: listening at 127.0.0.1:1082 > > > > | * Trying 127.0.0.1... > | * TCP_NODELAY set > | % Total% Received % Xferd Average Speed TimeTime Time > Current > | Dload Upload Total SpentLeft > Speed > | 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- > 0* SOCKS5 communication to www.google.com:80 > | 2017-12-04 16:07:04 INFO: connect to www.google.com:80 > | * SOCKS5 request granted. > | * Connected to 127.0.0.1 (127.0.0.1) port 1081 (#0) > > | > GET / HTTP/1.1 > | > Host: www.google.com > | > User-Agent: curl/7.57.0 > | > Accept: */* > | > > | 2017-12-04 16:07:04 ERROR: remote_recv_cb_recv: Connection reset by peer > | * Empty reply from server > | 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- > 0 > | * Connection #0 to host 127.0.0.1 left intact > | curl: (52) Empty reply from server > | 2017-12-04 16:07:04 INFO: closed gracefully > | test failed: python tests/test.py -c tests/aes.json > > Why this happens? Because on autopkgtest, you assume the package is already > *installed*. I assume the the daemon provided by the binary package is already > listening to port 1081, so the test server starts on 1082. Thanks for your hint! Yes, previous failure on debci was because of installation of the package, with the default config, so with the default port to open. However the test opens both 1081 and 1082, which is expected. The root cause is the application opens more than 1 port, and 8388 is both listed in default config [1] and test config. So here's the conflict. After I add a patch [2] to change the port for the test from 8388 to 8389, now the test can be passed on debci [0]. [1] https://anonscm.debian.org/cgit/collab-maint/shadowsocks-libev.git/tree/debian/config.json [2] https://anonscm.debian.org/cgit/collab-maint/shadowsocks-libev.git/tree/debian/patches/0001-Change-the-port-to-listen-from-8388-to-8389.patch I'm happy that one more package is starting to enjoy the benefit of continuous integration practice in debian. It's really appreciated there's debci framework in debian. Thanks for your work! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Re: How to get debian ci test passed for proxy application
Thanks all for your reply! On Mon, Nov 27, 2017 at 3:42 AM, James Cowgill <jcowg...@debian.org> wrote: > Hi, > > On 26/11/17 17:00, Roger Shimizu wrote: > >> The last test.sh script invokes the test, which creates local proxy >> listen to 127.0.0.1:1081, and then it calls curl command to get index >> page of google via local proxy, 127.0.0.1:1081. >> >> My local test shows all pass, while debian ci test [1] shows a >> connection timeout message. >> So I'm wondering whether debian ci support network activity, and how >> can I configure the test to get it passed. > > I think you might need a "Restrictions: isolation-container" to get > network access, but that's only a guess. Thanks for the hint! I find a supporting document [2], which state this flag is to allow open network TCP ports. [2] https://people.debian.org/~mpitt/autopkgtest/README.package-tests.html However, I tried "Restrictions: isolation-container", but it still failed [3] [3] https://ci.debian.net/data/autopkgtest/unstable/amd64/s/shadowsocks-libev/20171201_180744/log.gz So I'll try to use "Restrictions: isolation-machine" next. On Mon, Nov 27, 2017 at 5:36 AM, gregor herrmann <gre...@debian.org> wrote: > On Sun, 26 Nov 2017 18:42:22 +, James Cowgill wrote: > >> > My local test shows all pass, while debian ci test [1] shows a >> > connection timeout message. >> > So I'm wondering whether debian ci support network activity, and how >> > can I configure the test to get it passed. >> I think you might need a "Restrictions: isolation-container" to get >> network access, but that's only a guess. > > That's not my experience. We have quite a few perl packages where the > tests do something networky and haven't experienced problems on > ci.debian.net (modulo failing requests to external resources but > that's of course a different story). Maybe out bound network activity is OK, but not for open tcp port to listen, as James said. On Wed, Nov 29, 2017 at 5:45 PM, gustavo panizzo <g...@zumbi.com.ar> wrote: > > I'd suggest to install apache as part of the tests and connect to > localhost:80, that way it always works even if ci.debian.net moves to > China or google goes down > > to test python-openstackclient; MySQL, RabbitMQ, Apache and others are > installed, I haven't check its tests in a while but happy to help you Thanks for your idea! Maybe it'a a last resort, but I want to avoid currently. It's too big for just a simple test. And actually the package I'm try to make the test to work is helping people to fight with censorship in mid- or far- east area. So your example is not so proper IMHO. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
How to get debian ci test passed for proxy application
Dear mentors list, I maintain a proxy application, shadowsocks-libev. I want to let it pass debian ci test. And I already confirm the test all passed on my local environment, and debomatic [0]. However it failed on debian ci infrastructure [1]. [0] http://debomatic-amd64.debian.net/distribution#unstable/shadowsocks-libev/3.1.1+ds-1/autopkgtest [1] https://ci.debian.net/packages/s/shadowsocks-libev/unstable/amd64/ For local test, it just need the commands below: $ sudo apt install shadowsocks-libev curl dnsutils $ git clone https://anonscm.debian.org/git/collab-maint/shadowsocks-libev.git $ cd shadowsocks-libev $ ./tests/test.sh The last test.sh script invokes the test, which creates local proxy listen to 127.0.0.1:1081, and then it calls curl command to get index page of google via local proxy, 127.0.0.1:1081. My local test shows all pass, while debian ci test [1] shows a connection timeout message. So I'm wondering whether debian ci support network activity, and how can I configure the test to get it passed. Thank you! -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
experimental => unstable?
Dear mentors list, Stretch is just released [0], Yeah~! We're having a release party in Tokyo [1]. [0] https://www.debian.org/News/2017/20170617 [1] https://wiki.debian.org/ReleasePartyStretch/Japan/Tokyo So it should be fine to release various packages currently being held in experimental to unstable. Right? Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#861936: Subject: RFS: golang-github-seccomp-libseccomp-golang/0.0~git20150813.0.1b506fc-2 [RC]
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for package "golang-github-seccomp-libseccomp-golang" * Package name: golang-github-seccomp-libseccomp-golang Version : 0.0~git20150813.0.1b506fc-2 Section : devel It builds those binary packages: golang-github-seccomp-libseccomp-golang-dev - golang bindings for libseccomp To access further information about this package, please visit the following URL: https://mentors.debian.net/package/golang-github-seccomp-libseccomp-golang Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/golang-github-seccomp-libseccomp-golang/golang-github-seccomp-libseccomp-golang_0.0~git20150813.0.1b506fc-2.dsc tested to build on DoM: http://debomatic-i386.debian.net/distribution#unstable/golang-github-seccomp-libseccomp-golang/0.0~git20150813.0.1b506fc-2/buildlog http://debomatic-amd64.debian.net/distribution#unstable/golang-github-seccomp-libseccomp-golang/0.0~git20150813.0.1b506fc-2/buildlog Commits are pushed to mentors branch: https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-seccomp-libseccomp-golang.git -b mentors Changes since the last upload: golang-github-seccomp-libseccomp-golang (0.0~git20150813.0.1b506fc-2) unstable; urgency=medium * Team upload. [ Paul Tagliamonte ] * Use a secure transport for the Vcs-Git and Vcs-Browser URL [ Roger Shimizu ] * debian/patches: - Add a patch to fix FTBFS on 32-bit platforms. Thanks to upstream author Matthew Heon <matthew.h...@gmail.com> (Closes: #860618). Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1 pgp7Ym4ltvpcM.pgp Description: PGP signature
Bug#861543: RFS: golang-github-jacobsa-bazilfuse/0.0~git20150622-2 [RC] -- fork of bazil.org/fuse for gcsfuse
On Sun, 30 Apr 2017 16:27:18 + (UTC) Gianfranco Costamagna <locutusofb...@debian.org> wrote: > uploaded, please push the tag! > > (upstream removed that code, so probably you don't have to forward the patch) Thanks for the upload! Pushed to master with version tag. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1 pgpYSLP08vOrM.pgp Description: PGP signature
Bug#861543: RFS: golang-github-jacobsa-bazilfuse/0.0~git20150622-2 [RC] -- fork of bazil.org/fuse for gcsfuse
On Mon, 1 May 2017 00:35:34 +0900 Roger Shimizu <rogershim...@gmail.com> wrote: > I am looking for a sponsor for package "golang-github-jacobsa-bazilfuse" > This fixes an FTBFS RC bug #860623. Sorry that I forgot to mention the changes are pushed to: https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-jacobsa-bazilfuse.git -b mentors -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1 pgpApux5UUqC8.pgp Description: PGP signature
Bug#861543: RFS: golang-github-jacobsa-bazilfuse/0.0~git20150622-2 [RC] -- fork of bazil.org/fuse for gcsfuse
Package: sponsorship-requests Severity: important X-Debbugs-Cc: pkg-go-maintain...@lists.alioth.debian.org, rogershim...@gmail.com Dear mentors, I am looking for a sponsor for package "golang-github-jacobsa-bazilfuse" This fixes an FTBFS RC bug #860623. * Package name: golang-github-jacobsa-bazilfuse Version : 0.0~git20150622-2 * URL : https://github.com/jacobsa/bazilfuse * License : Go Section : devel It builds those binary packages: golang-github-jacobsa-bazilfuse-dev - fork of bazil.org/fuse for gcsfuse To access further information about this package, please visit the following URL: https://mentors.debian.net/package/golang-github-jacobsa-bazilfuse Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/golang-github-jacobsa-bazilfuse/golang-github-jacobsa-bazilfuse_0.0~git20150622-2.dsc Changes since the last upload: golang-github-jacobsa-bazilfuse (0.0~git20150622-2) unstable; urgency=medium * Team upload. [ Paul Tagliamonte ] * Use a secure transport for the Vcs-Git and Vcs-Browser URL [ Roger Shimizu ] * debian/patches: - Add a patch to fix FTBFS on i386 and other 32-bit systems. (Closes: #860623) * debian/control: - Use cgit URL for Vcs-Browser. Thank you and look forward to the upload! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1 pgpZQMSBCg42m.pgp Description: PGP signature
Re: I have some questions about alioth repository
On Fri, 21 Apr 2017 10:58:30 +0100 Ghislain Vaillant <ghisv...@gmail.com> wrote: > If the corresponding Vcs-* fields in d/control are missing for these > packages, then the packaging work is not stored in a VCS. You may > generate one by calling `gbp import-dscs $PACKAGE` which will download > all previous uploads and record them as successive Git commits. I guess the command should be: gbp import-dscs --debsnap $PACKAGE and I always add two more options: --author-date-is-committer-date --author-is-committer to make the git log looks better. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1 pgp8jmakAX0U3.pgp Description: PGP signature
Bug#860466: RFS: equivs/2.0.10 [QA] -- Circumvent Debian package dependencies
Control: tag -1 -moreinfo Dear Sean, On Thu, 20 Apr 2017 09:36:24 -0700 Sean Whitton <spwhit...@spwhitton.name> wrote: > I'd like to note that I'm planning to upload with dgit, so you shouldn't > rebase after the upload. It's okay to rebase before the upload. Understand. I always cut the final releasing commit and append with new commit, or amend the last commit, which you may call it rebase, and finally add a new releasing commit and push to a new branch, such as mentors2 or qa_upload2. Old branch is also kept, you you can easily "git show-branch" or "git diff" between branches. So you can know what has been changed. > The changelog still doesn't say that the Maintainer: field has been updated. > > If you're able to address the issues I've raised in this message, please > remove the moreinfo tag in this bug, and don't forget to re-run `dch -r` > to refresh the changelog timestamp. It's fixed and pushed to qa_upload4. _source package is also uploaded to mentors & DoM, for your reference. Thanks for your help! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1 pgpYlVqqIhtM7.pgp Description: PGP signature
Bug#860466: RFS: equivs/2.0.10 [QA] -- Circumvent Debian package dependencies
Control: tag -1 -moreinfo Dear Gianfranco, Thanks for your detailed explanation! On Wed, 19 Apr 2017 12:39:00 + (UTC) Gianfranco Costamagna <locutusofb...@debian.org> wrote: > Hello Roger, > > > >Targeting t-p-u need pre-approval from release team, while targeting > >unstable doesn't. > > > > true > >I didn't targeting t-p-u. What I meant was if: > >- my upload to unstable don't get unblock permission from release > >team > >- the original version of this package in stretch get a new RC need to > >fix > > > correct > >When both above two conditions meet, we have to use t-p-u to fix that > >new RC bug, which may be troublesome. But it still have way out. > >That's why I originally targeted unstable. > > > >Since it seems both you insist that experimental is the right place, > >I updated the package, uploaded to DoM & mentors, and pushed to > >branch qa_upload3. > > > the problem is not the theory, but it is more pratical. > Do you know in advance that an RC bug will be trivial to fix, and the fix will > be sane? > in case a bug is not so trivial, and you are not confident with the fix, > having a 10 days delay for migration, requesting help on lists, and having a > broader > testing is better than having a package in t-p-u tested only by a RT member. Yes, I only ever fixed 3-4 RC bugs, so not very experienced at this, and giving rough estimation how hard to solve a trivial or non-trivial issue. However, now I understand using t-p-u is not only requiring manual operation from release team, but also risky because we are unable to let mass unstable users to test the version for a few days and become confident to let it migrate to testing. > Having a new version in unstable, in case of a bad RC bug means the package > go out > of testing. Simple as that. > (and avoiding bothering of RT members during freeze times is always a sane > idea). > > So, to avoid troubles, better safe than sorry :) > > (I want to point out this because you are having your nm process, and this is > part > of the questions your AM will ask you). Reasonable. Now think this is the most difficult part because it's more about "feeling", than rules. Such as: - Feeling of confidence that fixing RC and not making new RC - Feeling of deserving the cost of brothering release team - Feeling of avoiding troubles and keep risk minimal etc. Seems I need more experience so I can have the right feeling. > Also, in case you upload a library foo2 in unstable > that has a foo1 in testing, you are preventing fixes of reverse-dependencies > from being uploaded > in unstable (because to migrate they should be built against the old version). > so, keeping unstable into a "releasable state" is always the preferred, safer > solution. Yes, speaking of library, it always need more attention. Your example is quite convincing. Thanks! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1 pgpbou7rULYxr.pgp Description: PGP signature
Bug#858454: RFS: simple-obfs/0.0.3-1~exp1 [ITP] -- simple obfusacting plugin for shadowsocks server
Dear Andrew, Thank you for reviewing my package! On Tue, 18 Apr 2017 22:46:19 -0400 Andrew Starr-Bochicchio <a...@debian.org> wrote: > On Wed, Mar 22, 2017 at 10:13 AM, Roger Shimizu <rogershim...@gmail.com> > wrote: > > I am looking for a sponsor for my package "simple-obfs", which is a new > > dependency of shadowsocks-libev since v3.0.3 > > Hi Roger, > > Great work! Though there are a few things to address before uploading. > The largest ones are around the watch file and upstream tarball: > > The watch file as provided seems to have an issue with the regex used > for filenamemangle and fails to download the upstream tarball. Running > uscan errors out with: > > uscan warn: stop mangling: > rule="s%(?:.*?)?v?(\d[\d.]*)\.tar\.gz%simple-obfs-$1.tar.gz%"" >rule doesn't match "(s|tr|y)%.*%.*%[a-z]*" (or similar). > uscan warn: In debian/watch, potentially unsafe or malformed > filenamemangle pattern: > 's%(?:.*?)?v?(\d[\d.]*)\.tar\.gz%simple-obfs-$1.tar.gz%"' found. > Skipping watchline > https://github.com/shadowsocks/simple-obfs/tags > (?:.*?/)?v?(\d[\d.]*)\.tar\.gz debian uupdate I find a '"' mark missing: https://github.com/rogers0/simple-obfs/commit/f94908a After this fix, uscan can sucessfully scan and download latest upstream tarball. > Additionally, the upstream tarball I found on the project's GitHub > page [0] does not match the one provided on mentors. > > $ md5sum simple-obfs-0.0.3.tar.gz > 7daebe04043402fa61616c958140c24e simple-obfs-0.0.3.tar.gz > > $ md5sum simple-obfs_0.0.3.orig.tar.xz > edf878d5cd84416bd9241862e0c58e0a simple-obfs_0.0.3.orig.tar.xz Original idea was to remove some autotools files by adding to Excluded-Files: in d/copyright, and repack the upstream tarball. But finally it seems not necessary, so yes, simply using upstream's tarball is fine. Fixed by force push pristine-tar branch. > A few minor points: > > - The package description could be expanded on a bit. Referring to the > README.md and manpages isn't all that useful as the user would likely > not have the package installed. The description should help a user > understand what purpose the package serves but does not need to get > into usage details. I picked a few words from manpage to add to description. > - The control file does not contain Vcs-* [1] fields. [1] Also, while > it is not a hard requirement, using Debian infrastructure (i.e. > git.debian.org) rather than GitHub would be prefered. Added collab-maint git repo to d/control. Though not created yet, I'll push to alioth after your upload. > - If desired, targeting unstable would be fine as this is a new > package and will not cause issues with getting changes into testing. Fixed. New commits are pushed to branch mentors2. And here're updated mentors & DoM url: https://mentors.debian.net/debian/pool/main/s/simple-obfs/simple-obfs_0.0.3-1.dsc http://debomatic-amd64.debian.net/distribution#unstable/simple-obfs/0.0.3-1/buildlog Thanks again! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1 pgpH3w20_mVyX.pgp Description: PGP signature
Bug#860466: RFS: equivs/2.0.10 [QA] -- Circumvent Debian package dependencies
On Wed, 19 Apr 2017 07:01:56 + (UTC) Gianfranco Costamagna <locutusofb...@debian.org> wrote: > Hello, > > >Secondly, testing-proposed-updates is highly inconvenient for the > >release team. It requires manual intervention and slows everything > >down. So we shouldn't upload to unstable unless we *expect* it to be > >unblocked. > > > also, TPU means that semi-automatic bug reports (e.g. piuparts, ftbfs and so > on) > won't be opened in case the package has problems. > Uploading to unstable an RC fix means higher probability of a fix being > tested. > > I don't even remember if t-p-u is available as external repo Targeting t-p-u need pre-approval from release team, while targeting unstable doesn't. I didn't targeting t-p-u. What I meant was if: - my upload to unstable don't get unblock permission from release team - the original version of this package in stretch get a new RC need to fix When both above two conditions meet, we have to use t-p-u to fix that new RC bug, which may be troublesome. But it still have way out. That's why I originally targeted unstable. Since it seems both you insist that experimental is the right place, I updated the package, uploaded to DoM & mentors, and pushed to branch qa_upload3. Thank you! -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1 pgpHcqF6RiyQ7.pgp Description: PGP signature
Bug#860466: RFS: equivs/2.0.10 [QA] -- Circumvent Debian package dependencies
Control: tag -1 -moreinfo Dear Sean, Thanks for your review! Very helpful. And I pushed my fixes to branch qa_upload2. (I removed the final releasing commit of branch qa_upload, and added update commit) Package also re-uploaded to DoM amd64 and mentors. On Tue, 18 Apr 2017 09:37:20 -0700 Sean Whitton <spwhit...@spwhitton.name> wrote: > control: tag -1 +moreinfo > > Dear Roger, > > On Mon, Apr 17, 2017 at 08:25:16PM +0900, Roger Shimizu wrote: > > I am looking for a sponsor for my package "equivs" > > Thanks for working on all these improvements and fixes. > > Here is a review of 9818bd99a15efbbbf37eace90480f69e682f2e8f: > > - Shouldn't this target experimental, not unstable, due to the freeze? I think these are all simple fix that suitable for stretch. The policy don't require pre-approval to upload to unstable [0]. If the unblock is rejected, and someone need to to fix another RC bug for this package, it's still possible since we have "testing-proposed-updates" [0]. [0] https://release.debian.org/stretch/freeze_policy.html > - In the old copyright file, there was a single list of copyright > holders, but you have generated two lists, for * and for debian/*. > How did you determine this? Based on d/changelog? I'm not sure that > is sufficiently reliable. To be safe, it might be best to just have a > "Files: *" stanza for everything -- I'm not sure. Indeed. The new d/copyright was generated by decopy. I think it's just have issue to support native package, or 1.0 source format, when I invoked decopy command. (I changed to 3.0 native afterwards) Now I merged two parts. New entries are catched by decopy, which find it in d/changelog, I think. > d/changelog: > > - You should include in the changelog that you updated the Maintainer: > field (not every QA upload does this). It's also good to write > something like (see #xx) where that's the number of the orphaning > bug. Fixed. > - You wrote "fix typos" in README.Debian, but the errors were not typos > (typos means "typographical errors"). They were just errors. So I > would suggest s/typos/minor errors/ or even s/typos/references/. Fixed. > - I think you should say that no changes were required when bumping the > std-ver in the template. > - You should say that you are bumping the debhelper compat level, not > the "debhelper version" Fixed. Hope you can sponsor this QA upload. Thank you! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1 pgpvhQlpqXOiM.pgp Description: PGP signature
Bug#860524: RFS: usbwall/0.4-1 [ITP] -- centralized USB devices filtering tool to associate locally allowed devices to LDAP user accounts
On Tue, 18 Apr 2017 20:13:55 +0900 Roger Shimizu <rogershim...@gmail.com> wrote: > Interesting package! > Actually it looks like usbguard (already in stretch) + LDAP + PAM. > > Could you kindly push your packaging code to some SCM, such as github? > This could make the review easier. Thank you! I cannot sponsor your package. But still wish you find my review helpful. Hope you can fix these and put your work in some SCM. Thank you! - d/copyright: MIT license has some variants, so it's better to specify as Expat license. - d/*-docs: Better to add README.md here - d/usbwalld.default should cleanup non-effective comments - d/usbwalld.service for document, you should use man page, not a URL. you can also take my package shadowsocks-libev as reference. - d/libpam-usbwall.install please replace x86_64-linux-gnu with *, or you will have FTBFS from all arch except amd64 - d/patches: please upstream your 2 patches - you have init script, so I guess you need to add Depends: lsb-base (>= 3.0-6) - d/rules: need cleanup. Some above are not required, but quite simple to fix. Thanks for your work! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1 pgpPM0lMnXh3f.pgp Description: PGP signature
Bug#860524: RFS: usbwall/0.4-1 [ITP] -- centralized USB devices filtering tool to associate locally allowed devices to LDAP user accounts
On Tue, 18 Apr 2017 09:23:54 +0200 p...@reseau-libre.net wrote: > Package: sponsorship-requests > Severity: wishlist > > Dear mentors, > > I am looking for a sponsor for my package "usbwall" > > * Package name: usbwall > Version : 0.4-1 > Upstream Author : Sylvain Leroy <sylv...@unmondelibre.fr> > * URL : https://github.com/Oline/usbwall > * License : MIT > Section : utils > > It builds those binary packages: > > devid-schema - LDAP schema file for devid device management schema > libpam-usbwall - usbwall PAM support allowing user-based device > filtering > usbwalld - Device filtering daemon, managing locally authorized > devices > > The goal of the usbwall project is to support dynamic USB device > filtering depending > on a per-user centralized authorized device list. When a user log in, a > custom PAM > module will alert a daemon, that will get back the list of the > authorized devices > from LDAP. Interesting package! Actually it looks like usbguard (already in stretch) + LDAP + PAM. Could you kindly push your packaging code to some SCM, such as github? This could make the review easier. Thank you! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1 pgpgsZqND2BZP.pgp Description: PGP signature
Bug#860466: RFS: equivs/2.0.10 [QA] -- Circumvent Debian package dependencies
Package: sponsorship-requests
Severity: normal
X-Debbugs-Cc: rogershim...@gmail.com
Dear mentors,
I am looking for a sponsor for my package "equivs"
* Package name: equivs
Version : 2.0.10
Upstream Author : Debian Native Package
* URL : https://tracker.debian.org/pkg/equivs
* License : GPL-2+
Section : admin
It builds those binary packages:
equivs - Circumvent Debian package dependencies
To access further information about this package, please visit the following
URL:
https://mentors.debian.net/package/equivs
Alternatively, one can download the package with dget using this command:
dget -x https://mentors.debian.net/debian/pool/main/e/equivs/equivs_2.0.10.dsc
or you can use git-buildpackage:
git clone https://github.com/rogers0/equivs
cd equivs
git checkout qa_upload
gbp buildpackage -uc -us --git-ignore-branch
Changes since the last upload:
equivs (2.0.10) unstable; urgency=medium
* QA upload.
* Strip subdirectories before installing file listed in "Files:".
Thanks to RjY <r...@users.sourceforge.net> and
Euan Thoms <e...@potensol.com>. (Closes: #662946)
* Fix that equivs-build doesn't work if & is part of PWD.
Thanks to Martin Mrazik and era eriksson <e...@iki.fi>.
(Closes: #679101) (LP: #881153, #1016402)
* debian/README.Debian:
- Fix typos. Thanks to Regid Ichira <regi...@nt1.in> (Closes: #724608)
* debian/rules:
- Thanks to Reiner Herrmann <rei...@reiner-h.de>, this package should be
reproducible now. (Closes: #786714)
* debian/copyright:
- Make DEP5 copyright
* debian/{control,compat}
- Bump debhelper to version 9.
* Bump versions in template:
- standard version to 3.9.8
- debhelper version to 9
- source version to 3.0 (quilt)
* debian/control:
- Bump stardard version to 3.9.8 (no change required)
* debian/source/format:
- Bump to 3.0 (native).
Cheers,
--
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1
pgpFA3zhqGeh7.pgp
Description: PGP signature
Bug#858083: RFS: libbloom/1.4-2
On Thu, Apr 13, 2017 at 2:09 AM, Boyuan Yang <073p...@gmail.com> wrote: > Everyone in collab-maint group can set up a repo (including yourself). Anyway > here it is: > > https://anonscm.debian.org/git/collab-maint/libbloom.git Thanks! I pushed all commits there. And latest release (-b mentors) starts to use alioth as official Vcs. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#858083: RFS: libbloom/1.4-1~exp1 [ITP] -- simple and small bloom filter implementation in C
On Wed, 12 Apr 2017 21:08:59 +0800 Aron Xu <a...@debian.org> wrote: > Hi, > > I've uploaded the package with several changes: > > 1. The package is new to the archive, targeting unstable is fine. > 2. Changed version number to 1.4-1 as per 1. > 3. Added MIT license text to d/copyright, it's not the same as the BSD one > 4. Dropped two Debian patches that do the shoot and catch game. > 5. Dropped your orig.tar.xz tarball because I can't find it anywhere > upstream, I replaced all the code using .tar.gz downloaded from > Github. Really appreciated for your kindness to upload! I pushed the release with your changes for version -1 to git repo. And I find there're a few arch with FTBFS issue in buildd. So I made a -2 attempt. I pushed my changes to branch mentors. Package is on mentors and debomatic with the following arch: http://debomatic-amd64.debian.net/distribution#unstable/libbloom/1.4-2/buildlog http://debomatic-armel.debian.net/distribution#unstable/libbloom/1.4-2/buildlog http://debomatic-arm64.debian.net/distribution#unstable/libbloom/1.4-2/buildlog So please kindly help to upload. Thank you! > Suggestions: > > Would you mind to move the git repository to git.debian.org? Also your > repo lacks the `upstream` branch which is usually used in > git-buildpackage style of packaging. If you create one repo in collab-maint, I'll mirror my repo there. Thanks for your advice! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1 pgpOQQAkDxRoe.pgp Description: PGP signature
Bug#849521: RFS: rutorrent/3.7-1 [ITP] -- A front-end for the rTorrent torrent client
Control: tag -1 +moreinfo On Tue, Jan 10, 2017 at 9:49 AM, JCF Ploemen <li...@jcf.pm> wrote: > your watch file issue is caused by the presence of a colon in the url, > at the start of every filename: > https://dl.bintray.com/novik65/generic/:ruTorrent-3.7.zip > > Once you account for that things start moving on the uscan front. Could you kindly fix the d/watch issue? You can try the following command when trying your new d/watch file: $ uscan --download-current-version Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1 pgpcBZRHXy8dC.pgp Description: PGP signature
Bug#847217: RFS: python-django-allauth/0.29.0-1 [ITP]
Control: tag -1 +moreinfo Dear Jan, > I forgot to mention that I upload the package to the Git repo of the > Python modules team as soon as my request to join the team is accepted. I guess you were going to push your changes to the git repo below: - https://anonscm.debian.org/git/python-modules/packages/python-django-allauth.git Before python-modules team react, could you please publish your work in other git repo such as github? This can make the review easier. Thanks! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1 pgpaJau4Fvalc.pgp Description: PGP signature
Bug#858557: golang-github-klauspost-reedsolomon_1.3-1~exp1_amd64.changes uploaded
On Wed, Mar 29, 2017 at 11:05 AM, Potter, Tim <timothy.pot...@hpe.com> wrote: > Hi Roger. Apologies for the delay - I meant to do this at the beginning of > the week. > > I've just uploaded the 1.3~exp1 version to Debian unstable. No problem, and really appreciate your kindness! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#854395: RFS: golang-go-xdg/0~bzr20140219-2 [RC] -- Go interface for XDG standards
Dear Gianfranco, Thanks for the upload! On Wed, Mar 29, 2017 at 3:50 AM, Gianfranco Costamagna <locutusofb...@debian.org> wrote: > > maybe sending an email to some dev would be nice! Sure. Will do later. > >> 2) why are you disabling tests? > > >my local gbp build (with or without pbuilder) is fine, however two > >test items fail on debomatic. > >I already paste the log from debomatic to the patch. > > it fails in pbuilder too > base_directory_test.go:45: > c.Check(h, Matches, s.home+".*"+s.val1) > ... value string = "/root/something" > ... regex string = "/home/locutus.*something" > > reason is, somewher xdg is returning my $HOME to be /root, > but echo $HOME returns /home/locutus > this is probably related to the fact I'm inside a chroot, > where /home/locutus points to nothing, while /root is my directory > > (I'm root but $HOME is not the root one) > > anyhow, > > HOME=/root dpkg-buildpackageworks here Thanks for digging it so deep! > lets go for unstable instead :) > please push the tag on git! Pushed with version tag (and removed the mentors branch). Thanks again! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#858557: [pkg-go] Bug#858557: RFS: golang-github-klauspost-reedsolomon/1.3-1~exp1 -- Reed-Solomon Erasure Coding in Go
Dear Timothy, I find it's better to add 2 entries in changelog. [Updated changelog] golang-github-klauspost-reedsolomon (1.3-1~exp1) experimental; urgency=medium * New upstream 1.3 (Closes: #857551) * debian/control: - Add myself as uploader. * Add debian/watch So I updated the package on mentors and debomatic. (version is the same, so URL also keeps the same, respectively) commits are pushed to git repo, branch mentors2: - https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-klauspost-reedsolomon.git/log/?h=mentors2 Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1 pgpgN5RGknh7V.pgp Description: PGP signature
Bug#858557: [pkg-go] Bug#858557: RFS: golang-github-klauspost-reedsolomon/1.3-1~exp1 -- Reed-Solomon Erasure Coding in Go
Dear Timothy, Thanks for your email! On Fri, 24 Mar 2017 06:59:45 + "Potter, Tim" <timothy.pot...@hpe.com> wrote: > Hi Roger. Did you find anyone to look at your package? If no-one has done > it already I > can sponsor it for you. No, you're the first one contacting me on this package. So it'd be appreciated if you can kindly take the owner of this RFS bug. -:D Thanks in advance! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1 pgpJmHMjx0mk4.pgp Description: PGP signature
Bug#858557: RFS: golang-github-klauspost-reedsolomon/1.3-1~exp1 -- Reed-Solomon Erasure Coding in Go
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: pkg-go-maintain...@lists.alioth.debian.org, fr...@debian.org, daniel820...@gmail.com, rogershim...@gmail.com Dear mentors, I am looking for a sponsor for my package "golang-github-klauspost-reedsolomon", which is a dependency of another my package "golang-github-xtaci-kcp". * Package name: golang-github-klauspost-reedsolomon Version : 1.3-1~exp1 Upstream Author : Klaus Post <klausp...@gmail.com> * URL : https://github.com/klauspost/reedsolomon * License : MIT Section : devel It builds those binary packages: golang-github-klauspost-reedsolomon-dev - Reed-Solomon Erasure Coding in Go To access further information about this package, please visit the following URL: https://mentors.debian.net/package/golang-github-klauspost-reedsolomon Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/golang-github-klauspost-reedsolomon/golang-github-klauspost-reedsolomon_1.3-1~exp1.dsc or you can use git-buildpackage to build: gbp clone --pristine-tar https://anonscm.debian.org/git/pkg-go/packages/golang-github-klauspost-reedsolomon.git cd golang-github-klauspost-reedsolomon git checkout mentors mk-build-deps --root-cmd sudo --install --tool "apt-get -o Debug::pkgProblemResolver=yes --no-install-recommends" gbp buildpackage -uc -us --git-ignore-branch --git-pristine-tar I also built this package on debomatic (amd64): http://debomatic-amd64.debian.net/distribution#experimental/golang-github-klauspost-reedsolomon/1.3-1~exp1/buildlog Changes since the last upload: golang-github-klauspost-reedsolomon (1.3-1~exp1) experimental; urgency=medium * New upstream 1.3 * debian/control: - Add myself as uploader. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#858454: RFS: simple-obfs/0.0.3-1~exp1 [ITP] -- simple obfusacting plugin for shadowsocks server
Package: sponsorship-requests Severity: wishlist X-Debbugs-Cc: max.c...@gmail.com, rogershim...@gmail.com Dear mentors, I am looking for a sponsor for my package "simple-obfs", which is a new dependency of shadowsocks-libev since v3.0.3 * Package name: simple-obfs Version : 0.0.3-1~exp1 Upstream Author : Max Lv <max.c...@gmail.com> * URL : https://github.com/shadowsocks/simple-obfs * License : GPL-3+ Section : net It builds those binary packages: simple-obfs - simple obfusacting plugin for shadowsocks server To access further information about this package, please visit the following URL: https://mentors.debian.net/package/simple-obfs Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/simple-obfs/simple-obfs_0.0.3-1~exp1.dsc or you can use git-buildpackage to build: gbp clone --pristine-tar https://github.com/rogers0/simple-obfs.git cd simple-obfs git checkout mentors mk-build-deps --root-cmd sudo --install --tool "apt-get -o Debug::pkgProblemResolver=yes --no-install-recommends" gbp buildpackage -uc -us --git-ignore-branch --git-pristine-tar I also built this package on debomatic (amd64): http://debomatic-amd64.debian.net/distribution#experimental/simple-obfs/0.0.3-1~exp1/buildlog [changelog] simple-obfs (0.0.3-1~exp1) experimental; urgency=low * Initial release. (Closes: #858370) Thanks advance for your review and upload! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1 pgpiEAXknd3MC.pgp Description: PGP signature
Bug#858083: RFS: libbloom/1.4-1~exp1 [ITP] -- simple and small bloom filter implementation in C
On Sat, 18 Mar 2017 12:46:50 +0900 Roger Shimizu <rogershim...@gmail.com> wrote: > I am looking for a sponsor for my package "libbloom" Upload an updated version to mentors, which handles FTBFS on armel/armhf/arm64 platform. (occured on debomoatic) Version is kept the same. Changes are push to git repo, branch mentors: - https://github.com/rogers0/libbloom/tree/mentors So you can use git-buildpackage to build: gbp clone --pristine-tar https://github.com/rogers0/libbloom.git cd libbloom git checkout mentors mk-build-deps --root-cmd sudo --install --tool "apt-get -o Debug::pkgProblemResolver=yes --no-install-recommends" gbp buildpackage -uc -us --git-ignore-branch --git-pristine-tar debomatic log on a few platform: - http://debomatic-arm64.debian.net/distribution#experimental/libbloom/1.4-1~exp1/buildlog - http://debomatic-armel.debian.net/distribution#experimental/libbloom/1.4-1~exp1/buildlog - http://debomatic-armhf.debian.net/distribution#experimental/libbloom/1.4-1~exp1/buildlog - http://debomatic-amd64.debian.net/distribution#experimental/libbloom/1.4-1~exp1/buildlog - http://debomatic-i386.debian.net/distribution#experimental/libbloom/1.4-1~exp1/buildlog Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1 pgp8ZFr8hEhmF.pgp Description: PGP signature
Bug#858083: RFS: libbloom/1.4-1~exp1 [ITP] -- simple and small bloom filter implementation in C
Package: sponsorship-requests Severity: wishlist X-Debbugs-Cc: j...@virkki.com, max.c...@gmail.com, rogershim...@gmail.com Dear mentors, I am looking for a sponsor for my package "libbloom" * Package name: libbloom Version : 1.4 Upstream Author : Jyri J. Virkki <j...@virkki.com> * URL : https://github.com/jvirkki/libbloom * License : BSD-2-Clause Programming Lang: C Description : simple and small bloom filter implementation in C It builds those binary packages: libbloom-dev - simple and small bloom filter implementation in C (development fi libbloom1 - simple and small bloom filter implementation in C To access further information about this package, please visit the following URL: https://mentors.debian.net/package/libbloom Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/libb/libbloom/libbloom_1.4-1~exp1.dsc or you can use git-buildpackage to build: gbp clone --pristine-tar https://github.com/rogers0/libbloom.git cd libbloom git checkout exp1 mk-build-deps --root-cmd sudo --install --tool "apt-get -o Debug::pkgProblemResolver=yes --no-install-recommends" gbp buildpackage -uc -us --git-ignore-branch --git-pristine-tar I also built this package on debomatic (amd64): http://debomatic-amd64.debian.net/distribution#experimental/libbloom/1.4-1~exp1/buildlog Thank you! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1 pgpWoy1mdGDGi.pgp Description: PGP signature
Bug#857053: RFS: kcptun/20170303+ds-1~exp1 [ITP] -- Simple UDP Tunnel Based On KCP
Package: sponsorship-requests Severity: wishlist X-Debbugs-Cc: pkg-go-maintain...@lists.alioth.debian.org, daniel820...@gmail.com, rogershim...@gmail.com Dear mentors, I am looking for a sponsor for my package "kcptun" * Package name: kcptun Version : 20170303+ds-1~exp1 Upstream Author : Daniel Fu <daniel820...@gmail.com> * URL : https://github.com/xtaci/kcptun * License : Expat Section : net It builds those binary packages: kcptun - Simple UDP Tunnel Based On KCP To access further information about this package, please visit the following URL: https://mentors.debian.net/package/kcptun Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/k/kcptun/kcptun_20170303+ds-1~exp1.dsc or you can use git-buildpackage to build: gbp clone --pristine-tar https://anonscm.debian.org/git/pkg-go/packages/kcptun.git cd kcptun git checkout mentors apt install -t experimental golang-github-xtaci-kcp-dev # also need to install golang-github-xtaci-smux-dev from RFS BTS#857033 mk-build-deps --root-cmd sudo --install --tool "apt-get -o Debug::pkgProblemResolver=yes --no-install-recommends" gbp buildpackage -uc -us --git-ignore-branch --git-pristine-tar Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1 pgpY9uaBIIEn3.pgp Description: PGP signature
Bug#857033: RFS: golang-github-xtaci-smux/1.0.4+git20170307+ds-1~exp1 [ITP] -- Simple Multiplexing for golang
Package: sponsorship-requests Severity: wishlist X-Debbugs-Cc: pkg-go-maintain...@lists.alioth.debian.org, daniel820...@gmail.com, rogershim...@gmail.com Dear mentors, I am looking for a sponsor for my package "golang-github-xtaci-smux". Previous upload was rejected by ftpmaster, with following comment: LICENSE says "xtaci" but d/copyright refers to Daniel Fu. Please fix or clarify in d/copyright. I have fixed the license issue with upstream: https://github.com/xtaci/smux/pull/14 So hopefully it can be accepted this time. Thank you! * Package name: golang-github-xtaci-smux Version : 1.0.4+git20170307+ds-1~exp1 Upstream Author : Daniel Fu <daniel820...@gmail.com> * URL : https://github.com/xtaci/smux * License : Expat Section : devel It builds those binary packages: golang-github-xtaci-smux-dev - Simple Multiplexing for golang To access further information about this package, please visit the following URL: https://mentors.debian.net/package/golang-github-xtaci-smux Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/golang-github-xtaci-smux/golang-github-xtaci-smux_1.0.4+git20170307+ds-1~exp1.dsc or you can use git-buildpackage to build: gbp clone --pristine-tar https://anonscm.debian.org/git/pkg-go/packages/golang-github-xtaci-smux.git cd golang-github-xtaci-smux git checkout mentors3 gbp buildpackage -uc -us --git-ignore-branch --git-pristine-tar I also made it available on debomatic (amd64): http://debomatic-amd64.debian.net/distribution#experimental/golang-github-xtaci-smux/1.0.4+git20170307+ds-1~exp1/buildlog Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1 pgpAk2CAHxQf0.pgp Description: PGP signature
Bug#854395: RFS: golang-go-xdg/0~bzr20140219-2 [RC] -- Go interface for XDG standards
Dear Gianfranco, Thanks for the review! On Tue, Feb 28, 2017 at 7:48 PM, Gianfranco Costamagna <costamagnagianfra...@yahoo.it> wrote: > > lets have a look: > 1) did you forward the patch upstream? sorry, no. upstream hosts in launchpad, which I don't have an account. > 2) why are you disabling tests? my local gbp build (with or without pbuilder) is fine, however two test items fail on debomatic. I already paste the log from debomatic to the patch. > 3) is the package still maintained? I'm not sure. Last upload was 3 years ago, though. I don't use the package myself, but it's a dependency of another package I'm interested in, so I'm just trying to help on this package. > Disabling tests seems bad to me, please investigate the reason for the > failures > and explain them in the patch in case Since I fixed another library dependency issue (Build-Depends on golang-check.v1-dev), how about upload first to experimental without the patch disabling two tests, to see how the test goes on buildd (instead of debomatic)? If the two tests fail also on buildd, we can investigate further. If you agree with things above, I can prepare another upload to mentors. Thanks! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#845710: removed Vcs fields
On Mon, Feb 27, 2017 at 5:07 AM, Tim Kuijsten <t...@netsend.nl> wrote: > > For the sake of simplicity I have added the debian directory to my main > repository. Hope this is good enough. Thanks for add back debian folder! I was wondering where's the git repository, and finally found it in your original RFS email. So you're also upstream. awesome! I cannot sponsor the upload, but here's my review and hope you find it helpful. - debian/copyright * according to https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ "There are many versions of the MIT license. Please use Expat instead, when it matches." So please avoid using "MIT" as license. * main.css is under a different license, which should be mentioned - lintian reports two hardening info level message * I guess you can add $(CPPFLAGS) to Makefile to fix it - debian/control * debhelper / compat recommend >=10 * better if line separated + sorted Build-Depends list (easy to maintain afterwrads) - debian/rules * why do you disable the test? Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#855202: RFS: binaryornot/0.4.0+dfsg-0.1 [RC][NMU] -- check if a file is binary or text
On Sat, Feb 18, 2017 at 1:04 AM, Sean Whitton <spwhit...@spwhitton.name> wrote: > > You need to submit the nmudiff to #854851. Followed your advice. Please kindly helpt to sponsor. Thank you! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#845710: removed Vcs fields
On Thu, Feb 9, 2017 at 10:59 PM, Tim Kuijsten <t...@netsend.nl> wrote: > The Vcs-* links are removed since the debian directory is not included in the > official repo. I guess you misunderstand Sean's words. There're two types of Vcs: - upstream Vcs, which should not contain debian/ folder. (but if it contains debian/, it should still have way to work out) - debian packaing Vcs, which Sean requested you to make BTW. Vcs-* in d/control file is the 2nd type listed above. So please create one with your packaging files, and add the Vcs info back to d/control. Thanks! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#840739: RFS: gudhi/1.3.1+ds-1 [ITP]
On Thu, Feb 9, 2017 at 4:47 AM, Gard Spreemann <gspreem...@gmail.com> wrote: > On Wednesday, 8 February 2017 18:46:46 CET Roger Shimizu wrote: >> Dear Gard, >> >> I cannot sponsor the upload. But here's my review that I hope it's helpful. > > Dear Roger, > > Thank you very much for your helpful feedback. I believe I have > rectified some of the below. > >> Here're the items need to be fixed: >> - missing in debian/copyright, not GPL-3+ license: >> cmake/modules/FindEigen3.cmake >> cmake/modules/FindTBB.cmake >> include/gudhi/Contraction/CGAL_queue/*.h >> data/points/COIL_database/images/* >> doc/*/*.png >> Better to ask upstream to confirm license of those image files. >> Usually license of image files is different from the code. If it's not >> sure simply remove it from "debian source" repack. > > Good catch! I'm sorry for overlooking this. I'll get to work > clarifying the licenses and/or stripping out these. I mean there're src files under other than GPL-3+, which is totally fine. But you need to sort them out, list all the licenses and their src files. Please take a look at my package as example: - https://anonscm.debian.org/git/collab-maint/shadowsocks-libev.git/tree/debian/copyright >> - lintian reports: >> I: libgudhi-dev: spelling-error-in-copyright unneccessary unnecessary > > Fixed. > >> Other comments, nice to have: >> - it's more convenient if you can export your work to some modern >> SCM, such as git >>the review will be easier if doing with such SCM >>you can omit the final releasing commit, so if there's something >> still need to work, you don't have to push forcefully. > > Done; https://git.nonempty.org/debian-gudhi/ > >> - add Vcs-* line to d/control (depends on the above item) > > Done. > >> - bump to debhelper 10 > > Done. > >> - wrap and sort Build-Depends & Depends list in d/control > > Done. Great! On Tue, Feb 14, 2017 at 7:13 PM, Gard Spreemann <gspreem...@gmail.com> wrote: > On Wednesday, 8 February 2017 20:47:07 CET Gard Spreemann wrote: >> On Wednesday, 8 February 2017 18:46:46 CET Roger Shimizu wrote: >> > >> > - have separated -doc package >> >> The documentation shipped with upstream's source is rather >> limited. They instead ship a dedicated tarball for documentation >> [1]. I intend to package it too, and have it provide the -doc >> package. >> >> Does this sound sensible to you? > > Scratch that. My package now generates the doxygen documentation and > builds a -doc package. Great! >> I'll upload a new version to mentors.debian.net when I hear back >> from upstream regarding the missing copyrights. > > Upstream say they will take into account my remarks regarding > licensing for the next release. I'll upload a new version to mentors > when that happens. I guess only image files need to confirm, right? We can wait for the version you're satisfied with. > The version on https://git.nonempty.org/debian-gudhi/ has diverged a > bit from the mentors one meanwhile. Most importantly, it now builds a > -doc and an -examples package. Any comments would be greatly > appreciated. No problem about the divergence, git repo is just easy to track what you've changed. Look forward to your updated upload next time. Thanks for your effort! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#855354: RFS: alot/0.5.1-1 [ITA]
On Fri, Feb 17, 2017 at 4:59 PM, Simon Chopin <chopin.si...@gmail.com> wrote: > > to review anyone's work. As far as uploading goes, I'm fairly sure my GPG > key has expired. FYI. if your key hasn't been compromised, it's easy to extend the expiration date [0]. [0] https://riseup.net/en/security/message-security/openpgp/best-practices#use-an-expiration-date-less-than-two-years Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#855193: RFS: slt/0.0.git20140301-2.1 [RC][NMU] -- TLS reverse-proxy with SNI multiplexing (TLS virtual hosts)
On Thu, Feb 16, 2017 at 1:36 AM, James Cowgill <jcowg...@debian.org> wrote: > > On 15/02/17 11:24, Roger Shimizu wrote: >> Dear James, >> >> On Wed, Feb 15, 2017 at 7:51 PM, James Cowgill <jcowg...@debian.org> wrote: >>> >>> So do you know why the tests only pass when using 2 CPUs? That seems >>> pretty fishy to me. Maybe there is an underlying bug here? >> >> I'm not sure the reason. >> I was just trying to help on the FTBFS RC bug during BSP Tokyo. > > I found the actual cause - there's a race condition in the testsuite > which will usually (100% in practice) cause it to deadlock on single > processor systems. You can look at the bug I filed upstream if you want. Thanks for catching the race condition bug! But can we do something to prevent the autoremove of the package soon? I guess the testcase issue can be lower to non-RC level then. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#855202: RFS: binaryornot/0.4.0+dfsg-0.1 [RC][NMU] -- check if a file is binary or text
Package: sponsorship-requests
Severity: important
Dear mentors,
I am looking for a sponsor for my package "binaryornot" as [RC][NMU].
* Package name: binaryornot
Version : 0.4.0+dfsg-0.1
Upstream Author : Audrey Roy <audr...@gmail.com>
* URL : https://github.com/audreyr/binaryornot
* License : BSD-3-clause
Section : python
It builds those binary packages:
python-binaryornot - check if a file is binary or text (Python 2 module)
python3-binaryornot - check if a file is binary or text (Python 3 module)
To access further information about this package, please visit the following
URL:
https://mentors.debian.net/package/binaryornot
Alternatively, one can download the package with dget using this command:
dget -x
https://mentors.debian.net/debian/pool/main/b/binaryornot/binaryornot_0.4.0+dfsg-0.1.dsc
or you can use git-buildpackage to build:
(since I don't have access to maintainer's Vcs, I pushed my changes to github)
gbp clone --pristine-tar https://github.com/rogers0/binaryornot
cd binaryornot
gbp buildpackage -uc -us --pristine-tar
I also made it available on debomatic (i386):
http://debomatic-i386.debian.net/distribution#unstable/binaryornot/0.4.0+dfsg-0.1/buildlog
Changes since the last upload:
binaryornot (0.4.0+dfsg-0.1) unstable; urgency=medium
* Non-maintainer upload.
[ Ondřej Nový ]
* Fixed VCS URL (https)
[ Roger Shimizu ]
* Remove non-free image files, and repack as +dfsg.
* Add patch to remove tests regarding to non-free image files.
(Closes: #854851)
I also enclosed the debdiff for NMU review.
Thank you!
Cheers,
--
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1
diff -Nru binaryornot-0.4.0/debian/changelog
binaryornot-0.4.0+dfsg/debian/changelog
--- binaryornot-0.4.0/debian/changelog 2015-11-16 07:05:20.0 +0900
+++ binaryornot-0.4.0+dfsg/debian/changelog 2017-02-15 21:07:15.0
+0900
@@ -1,3 +1,17 @@
+binaryornot (0.4.0+dfsg-0.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+
+ [ Ondřej Nový ]
+ * Fixed VCS URL (https)
+
+ [ Roger Shimizu ]
+ * Remove non-free image files, and repack as +dfsg.
+ * Add patch to remove tests regarding to non-free image files.
+(Closes: #854851)
+
+ -- Roger Shimizu <rogershim...@gmail.com> Wed, 15 Feb 2017 21:07:15 +0900
+
binaryornot (0.4.0-1) unstable; urgency=medium
* New upstream release.
diff -Nru binaryornot-0.4.0/debian/control binaryornot-0.4.0+dfsg/debian/control
--- binaryornot-0.4.0/debian/control2015-11-16 07:05:20.0 +0900
+++ binaryornot-0.4.0+dfsg/debian/control 2017-02-15 21:01:09.0
+0900
@@ -10,7 +10,7 @@
python-hypothesis, python3-hypothesis
Standards-Version: 3.9.6
Homepage: https://github.com/audreyr/binaryornot
-Vcs-Git: git://anonscm.debian.org/python-modules/packages/binaryornot.git
+Vcs-Git: https://anonscm.debian.org/git/python-modules/packages/binaryornot.git
Vcs-Browser:
https://anonscm.debian.org/cgit/python-modules/packages/binaryornot.git
Package: python-binaryornot
diff -Nru
binaryornot-0.4.0/debian/patches/0001-Remove-tests-regarding-to-non-free-image-lena.patch
binaryornot-0.4.0+dfsg/debian/patches/0001-Remove-tests-regarding-to-non-free-image-lena.patch
---
binaryornot-0.4.0/debian/patches/0001-Remove-tests-regarding-to-non-free-image-lena.patch
1970-01-01 09:00:00.0 +0900
+++
binaryornot-0.4.0+dfsg/debian/patches/0001-Remove-tests-regarding-to-non-free-image-lena.patch
2017-02-15 21:07:15.0 +0900
@@ -0,0 +1,26 @@
+From: Roger Shimizu <rogershim...@gmail.com>
+Date: Wed, 15 Feb 2017 21:14:30 +0900
+Subject: Remove tests regarding to non-free image lena
+
+See Bug #854851
+---
+ tests/test_check.py | 6 --
+ 1 file changed, 6 deletions(-)
+
+diff --git a/tests/test_check.py b/tests/test_check.py
+index 338119e..fbe32d1 100755
+--- a/tests/test_check.py
b/tests/test_check.py
+@@ -49,12 +49,6 @@ class TestIsBinary(unittest.TestCase):
+ def test_png(self):
+ self.assertTrue(is_binary('tests/files/logo.png'))
+
+-def test_gif(self):
+-self.assertTrue(is_binary('tests/files/lena.gif'))
+-
+-def test_jpg(self):
+-self.assertTrue(is_binary('tests/files/lena.jpg'))
+-
+ def test_tiff(self):
+ self.assertTrue(is_binary('tests/files/palette-1c-8b.tiff'))
+
diff -Nru binaryornot-0.4.0/debian/patches/series
binaryornot-0.4.0+dfsg/debian/patches/series
--- binaryornot-0.4.0/debian/patches/series 1970-01-01 09:00:00.0
+0900
+++ binaryornot-0.4.0+dfsg/debian/patches/series2017-02-15
21:07:15.0 +0900
@@ -0,0 +1 @@
+0001-Remove-tests-regarding-to-non-free-image-lena.patch
Binary files /tmp/carUuVTSnE/binaryornot-0.4.0/tests/files/lena.gif and
/tmp/lVa9B18e3R/binaryornot-0.4.0+dfsg/tests/files/lena.gif differ
Binary files /tmp/carUuVTSnE/binaryornot-0.4.0/tests/files/lena.jpg and
Bug#855193: RFS: slt/0.0.git20140301-2.1 [RC][NMU] -- TLS reverse-proxy with SNI multiplexing (TLS virtual hosts)
Dear James, On Wed, Feb 15, 2017 at 7:51 PM, James Cowgill <jcowg...@debian.org> wrote: > > So do you know why the tests only pass when using 2 CPUs? That seems > pretty fishy to me. Maybe there is an underlying bug here? I'm not sure the reason. I was just trying to help on the FTBFS RC bug during BSP Tokyo. What I know is this is not rare, like another one I fixed: https://bugs.debian.org/854500 Could you kindly help to upload? Buildd [0] shows it actually build fine for all ARCHs I should build, so I don't what to trigger the autoremove ... Thanks! [0] https://buildd.debian.org/status/package.php?p=slt Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#855193: RFS: slt/0.0.git20140301-2.1 [RC][NMU] -- TLS reverse-proxy with SNI multiplexing (TLS virtual hosts)
Package: sponsorship-requests
Severity: important
Dear mentors,
I am looking for a sponsor for my package "slt" as [RC][NMU].
I posted the patch to Bug#851876 for 4 days but no feedback.
And pkg maintainer is in LowThresholdNmu list.
* Package name: slt
Version : 0.0.git20140301-2.1
Upstream Author : Alan Shreve <a...@inconshreveable.com>
* URL : https://github.com/inconshreveable/slt
* License : Apache-2.0
Section : devel
It builds those binary packages:
slt - TLS reverse-proxy with SNI multiplexing (TLS virtual hosts)
To access further information about this package, please visit the following
URL:
https://mentors.debian.net/package/slt
Alternatively, one can download the package with dget using this command:
dget -x
https://mentors.debian.net/debian/pool/main/s/slt/slt_0.0.git20140301-2.1.dsc
or you can use git-buildpackage to build:
gbp clone --pristine-tar https://anonscm.debian.org/git/collab-maint/slt.git
cd slt
git checkout debian_nmu
gbp buildpackage -uc -us --git-ignore-branch
I also made it available on debomatic (i386):
http://debomatic-i386.debian.net/distribution#unstable/slt/0.0.git20140301-2.1/buildlog
Changes since the last upload:
slt (0.0.git20140301-2.1) unstable; urgency=medium
[ Roger Shimizu ]
* Non-maintainer upload.
* debian/rules:
- Run dh_auto_test only if CPUs >= 2 (Closes: #851876).
I also enclosed the debdiff for NMU review.
Thank you!
Cheers,
--
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1
diff -Nru slt-0.0.git20140301/debian/changelog
slt-0.0.git20140301/debian/changelog
--- slt-0.0.git20140301/debian/changelog2017-01-03 14:37:31.0
+0900
+++ slt-0.0.git20140301/debian/changelog2017-02-15 07:52:32.0
+0900
@@ -1,3 +1,12 @@
+slt (0.0.git20140301-2.1) unstable; urgency=medium
+
+ [ Roger Shimizu ]
+ * Non-maintainer upload.
+ * debian/rules:
+- Run dh_auto_test only if CPUs >= 2 (Closes: #851876).
+
+ -- Roger Shimizu <rogershim...@gmail.com> Wed, 15 Feb 2017 07:52:32 +0900
+
slt (0.0.git20140301-2) unstable; urgency=medium
* wrap-and-sort -ast
diff -Nru slt-0.0.git20140301/debian/rules slt-0.0.git20140301/debian/rules
--- slt-0.0.git20140301/debian/rules2017-01-03 14:36:32.0 +0900
+++ slt-0.0.git20140301/debian/rules2017-02-15 07:52:32.0 +0900
@@ -8,3 +8,11 @@
override_dh_installman:
ronn < man/slt.8.ronn >debian/slt.8
dh_installman
+
+# Run test only if CPUs >= 2. See Bug#851876
+override_dh_auto_test:
+ifneq ($(shell nproc), 1)
+ dh_auto_test
+else
+ @echo dh_auto_test skipped on 1-Core CPU platform
+endif
Bug#852981: RFS: golang-github-xtaci-kcp/2.14+git20170120+ds-1 [ITP] -- Full-Featured Reliable-UDP Library for golang
On Sun, Jan 29, 2017 at 2:11 AM, Roger Shimizu <rogershim...@gmail.com> wrote: > Package: sponsorship-requests > Severity: wishlist > X-Debbugs-Cc: pkg-go-maintain...@lists.alioth.debian.org, > daniel820...@gmail.com, rogershim...@gmail.com > > Dear mentors, > > I am looking for a sponsor for my package "golang-github-xtaci-kcp" > > * Package name: golang-github-xtaci-kcp >Version : 2.14+git20170120+ds-1 >Upstream Author : Daniel Fu <daniel820...@gmail.com> > * URL : https://github.com/xtaci/kcp-go > * License : Expat >Section : devel > > It builds those binary packages: > > golang-github-xtaci-kcp-dev - Full-Featured Reliable-UDP Library for > golang > > To access further information about this package, please visit the > following URL: > > https://mentors.debian.net/package/golang-github-xtaci-kcp Update version in mentors, upload to experimental instead of unstable, since it's frozen stage now. one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/golang-github-xtaci-kcp/golang-github-xtaci-kcp_2.14+git20170120+ds-1~exp1.dsc or you can use git-buildpackage to build: gbp clone --pristine-tar https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-xtaci-kcp.git cd golang-github-xtaci-kcp git checkout mentors2 gbp buildpackage -uc -us --git-ignore-branch --git-pristine-tar I also built on debomatic (i386): http://debomatic-i386.debian.net/distribution#experimental/golang-github-xtaci-kcp/2.14+git20170120+ds-1~exp1/buildlog Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#852978: RFS: golang-github-xtaci-smux/1.0.4+git20170112+ds-1 [ITP] -- Simple Multiplexing for golang
On Sun, Jan 29, 2017 at 1:42 AM, Roger Shimizu <rogershim...@gmail.com> wrote: > Package: sponsorship-requests > Severity: wishlist > X-Debbugs-Cc: pkg-go-maintain...@lists.alioth.debian.org, > daniel820...@gmail.com, rogershim...@gmail.com > > Dear mentors, > > I am looking for a sponsor for my package "golang-github-xtaci-smux" > > * Package name: golang-github-xtaci-smux >Version : 1.0.4+git20170112+ds-1 >Upstream Author : Daniel Fu <daniel820...@gmail.com> > * URL : https://github.com/xtaci/smux > * License : Expat >Section : devel > > It builds those binary packages: > > golang-github-xtaci-smux-dev - Simple Multiplexing for golang > > To access further information about this package, please visit the > following URL: > > https://mentors.debian.net/package/golang-github-xtaci-smux Update version in mentors, upload to experimental instead of unstable, since it's frozen stage now. one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/golang-github-xtaci-smux/golang-github-xtaci-smux_1.0.4+git20170112+ds-1~exp1.dsc or you can use git-buildpackage to build: gbp clone --pristine-tar https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-xtaci-smux.git cd golang-github-xtaci-smux git checkout mentors2 gbp buildpackage -uc -us --git-ignore-branch --git-pristine-tar I also built on debomatic (i386): http://debomatic-i386.debian.net/distribution#experimental/golang-github-xtaci-smux/1.0.4+git20170112+ds-1~exp1/buildlog Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#851606: RFS: rmlint/2.4.6-1 [ITP]
Control: tag -1 +moreinfo Dear Carlos, I cannot sponsor the upload. But here's my review that I hope it's helpful. On Tue, Jan 17, 2017 at 3:56 AM, Carlos Maddela <e7ap...@gmail.com> wrote: > > I am looking for a sponsor for my package "rmlint" > > * Package name: rmlint >Version : 2.4.6-1 >Upstream Author : Christopher Pahl <sa...@online.de> > * URL : https://rmlint.readthedocs.io/ > * License : GPL-3 >Section : utils Here're the items need to be fixed: - license/copyright There're many files not under GPL-3, which need to be mentioned in d/copyright - There's Vcs-* line set for collab-maint, but I cannot access it. Please push your work in collab-maint or other git repo, which make the review easier. - There's doc/ folder, but you didn't install them? Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#849313: RFS: mate-equake-applet/1.3.8-1 [ITP]
Control: tag -1 +moreinfo Dear Jeroen, Thanks for your packaging work! I cannot sponsor the upload, but here're a few comments after reviewing your package. On Sun, Dec 25, 2016 at 5:39 PM, Jeroen van Aart <andr...@e-quake.org> wrote: > > I am looking for a sponsor for my package "mate-equake-applet" > > * Package name: mate-equake-applet > Version : 1.3.8-1 > Upstream Author : Jeroen van Aart > * URL : http://www.e-quake.org > * License : GPL > Section : x11 Here're the items need to be fixed: - inconsistent on license: COPYING shows the project is under GPL-3+ however, source files under src/ folder and debian/copyright shows GPL-2+ - license of image file: icons/48x48/mate-equake-applet-icon.png Please confirm its license with upstream (you?), usually license of image files is different from the code. - license of install-sh is differrent, you need to sort it out - lintian reports: Former 2 should be easy, last one can be fixed later. W: mate-equake-applet source: ancient-standards-version 3.9.5 (current is 3.9.8) I: mate-equake-applet: spelling-error-in-binary usr/lib/x86_64-linux-gnu/mate-equake-applet Minimun Minimum I: mate-equake-applet: hardening-no-bindnow usr/lib/x86_64-linux-gnu/mate-equake-applet Other comments, nice to have: - it's more convenient if you can export your work to some modern SCM, such as git the review will be easier if doing with such SCM you can omit the final releasing commit, so if there's something still need to work, you don't have to push forcefully. - add Vcs-* line to d/control (depends on the above item) - bump to debhelper 10 - In favor of https URL over http in debian/copyright - there're a few warnings during build, better fix them if possible I don't use mate, so just a review from source side. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Re: [RFC] How to review RFS package
Dear Sean, Gianfranco, Thanks for your feedback! On Wed, Feb 8, 2017 at 11:18 PM, Sean Whitton <spwhit...@spwhitton.name> wrote: > > I've made some edits. > > Your page should probably discuss sbuild/pbuilder. On Wed, Feb 8, 2017 at 11:23 PM, Gianfranco Costamagna <costamagnagianfra...@yahoo.it> wrote: > > a low-level manual is something nice to have... > > I propose some additions for non-new packages: > "dget -u" unpacks the source in case you already trust the person (but you > didn't update the keyring) > > > debdiff between versions (in case of update) > filterdiff debdiff -i "*debian*" > debdiff.filtered > to see just debian changes I added your suggestion to the final "ideas" section in that wiki page. > apt build-dep (dsc-file) to build-dependencies I remember "apt build-dep " is only for package already exists in archive. It's not proper for ITP, or B-D updated package. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Re: [RFC] How to review RFS package
On Wed, Feb 8, 2017 at 11:03 PM, Paul Wise <p...@debian.org> wrote: > On Wed, Feb 8, 2017 at 9:50 PM, Roger Shimizu wrote: > >> During my attempt to review RFS package in mentors list, I find actually >> there's no good manual for this activity. > > Did you see the existing documentation? > > http://mentors.debian.net/intro-reviewers > https://wiki.debian.org/SponsorChecklist Thanks for your info! Yes, but those docs didn't provide info detailed enough for me to start. Probably I too much rely on the high level tools, and lack of ability to use plumbing level tools such as dpkg-*. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
[RFC] How to review RFS package
Dear mentors, During my attempt to review RFS package in mentors list, I find actually there's no good manual for this activity. At first I even don't know what to do with the downloaded .dsc and two tarballs, because my previous experience was all using high level packaging tool, such as git-buildpackage. So I start a new wiki entry [0], to describe how to review a RFS package. [0] https://wiki.debian.org/Mentors/Review I call it RFC, because I'm not sure whether there're enough steps there. Please kindly review and give me feedback. You're also welcome to change things directly on the wiki. Thank you! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1 pgpkiuDYwXqNk.pgp Description: PGP signature
Bug#849273: RFS: gemmlowp/0~20161216-gb56df4a-1 [ITP]
Control: tag -1 +moreinfo
Dear lumin,
On Sat, Dec 24, 2016 at 11:44 PM, lumin <cdlumin...@gmail.com> wrote:
>
> * Package name: gemmlowp
>Version : 0~20161216-gb56df4a-1
Thanks for your clean packaging!
I cannot sponsor the upload, just a few comments after reviewing your package.
I see some activities on your PR on github:
- https://github.com/google/gemmlowp/pull/63
So you're going to update the CMakeLists.txt based on upstream's feedback?
Others are all nitpicking (not required):
- In favor of https URL over http in debian/copyright
- no need to depends on ${shlibs:Depends}, since there's no real library?
dpkg-gencontrol: warning: Depends field of package gemmlowp-dev:
unknown substitution variable ${shlibs:Depends}
Cheers,
--
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#840739: RFS: gudhi/1.3.1+ds-1 [ITP]
Control: tag -1 +moreinfo Dear Gard, On Fri, Oct 14, 2016 at 7:32 PM, Gard Spreemann <gspreem...@gmail.com> wrote: > > I am looking for a sponsor for my package "gudhi" > > * Package name : gudhi >Version : 1.3.1+ds-1 >Upstream Author : Gudhi Project / INRIA > * URL : http://gudhi.gforge.inria.fr/ > * License : GPL3+ >Section : math > > GUDHI is a C++ header-only template library for computations in the > mathematical field of topological data analysis. I cannot sponsor the upload. But here's my review that I hope it's helpful. Here're the items need to be fixed: - missing in debian/copyright, not GPL-3+ license: cmake/modules/FindEigen3.cmake cmake/modules/FindTBB.cmake include/gudhi/Contraction/CGAL_queue/*.h data/points/COIL_database/images/* doc/*/*.png Better to ask upstream to confirm license of those image files. Usually license of image files is different from the code. If it's not sure simply remove it from "debian source" repack. - lintian reports: I: libgudhi-dev: spelling-error-in-copyright unneccessary unnecessary Other comments, nice to have: - it's more convenient if you can export your work to some modern SCM, such as git the review will be easier if doing with such SCM you can omit the final releasing commit, so if there's something still need to work, you don't have to push forcefully. - add Vcs-* line to d/control (depends on the above item) - bump to debhelper 10 - wrap and sort Build-Depends & Depends list in d/control - have separated -doc package - even upstream didn't provide script to install example, you can install those example files by adding d/docs file - In favor of https URL over http in debian/copyright So far it's enough for now. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#854395: RFS: golang-go-xdg/0~bzr20140219-2 [RC] -- Go interface for XDG standards
Control: severity -1 normal On Tue, Feb 7, 2017 at 1:12 AM, Andrey Rahmatullin <w...@debian.org> wrote: > On Tue, Feb 07, 2017 at 01:04:12AM +0900, Roger Shimizu wrote: >> This pkg is removed from testing on Jan. 14th [0]. >> So it means even after fixing the FTBFS, it cannot go back to testing again? > Yes, until the stretch release. Understand. Thanks for the explanation! So put into normal for the time being. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#854477: RFS: shadowsocks-libev/2.6.3+ds-1~bpo8+1 -- lightweight and secure socks5 proxy
package: sponsorship-requests severity: normal X-Debbugs-Cc: max.c...@gmail.com, 073p...@gmail.com, rogershim...@gmail.com Dear mentors, I am looking for a sponsor for my package "shadowsocks-libev" for jessie-backports. * Package name: shadowsocks-libev Version : 2.6.3+ds-1~bpo8+1 Upstream Author : Max Lv <max.c...@gmail.com> * URL : https://www.shadowsocks.org * License : GPL-3+ Section : net It builds those binary packages: libshadowsocks-dev - lightweight and secure socks5 proxy (development files) libshadowsocks1 - lightweight and secure socks5 proxy (shared library) shadowsocks-libev - lightweight and secure socks5 proxy To access further information about this package, please visit the following URL: https://mentors.debian.net/package/shadowsocks-libev Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/shadowsocks-libev/shadowsocks-libev_2.6.3+ds-1~bpo8+1.dsc or you can use git-buildpackage to build: gbp clone --pristine-tar https://anonscm.debian.org/git/collab-maint/shadowsocks-libev.git cd shadowsocks-libev git checkout jessie-backports_2.6.3+ds-1 DIST=jessie-backports git-pbuilder create # Skip this if you already have pbuilder environment gbp buildpackage --git-ignore-branch --git-pristine-tar --git-pbuilder --git-dist=jessie-backports I also built the package on debomatic amd64: http://debomatic-amd64.debian.net/distribution#jessie-backports/shadowsocks-libev/2.6.3+ds-1~bpo8+1/buildlog I pushed my changes to git repo: https://anonscm.debian.org/cgit/collab-maint/shadowsocks-libev.git/log/?h=jessie-backports_2.6.3+ds-1 Thank you! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1 pgpaBjdUMmHbQ.pgp Description: PGP signature
Bug#854395: RFS: golang-go-xdg/0~bzr20140219-2 [RC] -- Go interface for XDG standards
On Tue, Feb 7, 2017 at 12:48 AM, Andrey Rahmatullin <w...@debian.org> wrote: > On Tue, Feb 07, 2017 at 12:33:08AM +0900, Roger Shimizu wrote: >> Changes since the last upload: >> >> * Team upload. >> >> [ Paul Tagliamonte ] >> * Use a secure transport for the Vcs-Git and Vcs-Browser URL >> >> [ Roger Shimizu ] >> * debian/control: >> - Update Build-Depends on golang-check.v1-dev, in stead of >> golang-gocheck-dev which is already non-active upstream. >> - Use cgit URL for Vcs-Browser. >> * debian/patches: >> - Add a patch to use golang-check.v1-dev. >> - Add a patch to remove failure tests (Closes: #830446). > If you want this to go to stretch please read > https://release.debian.org/stretch/freeze_policy.html first. Thanks for your reply! This pkg is removed from testing on Jan. 14th [0]. So it means even after fixing the FTBFS, it cannot go back to testing again? I already tried to minimize the changes.. [0] https://tracker.debian.org/news/832624 Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#854395: RFS: golang-go-xdg/0~bzr20140219-2 [RC] -- Go interface for XDG standards
Package: sponsorship-requests Severity: important X-Debbugs-Cc: pkg-go-maintain...@lists.alioth.debian.org, sergio.schve...@canonical.com, t...@pault.ag, rogershim...@gmail.com Dear mentors, I am looking for a sponsor for my package "golang-go-xdg" * Package name: golang-go-xdg Version : 0~bzr20140219-2 Upstream Author : John R. Lenton. * URL : https://launchpad.net/go-xdg * License : BSD-2-Clause Section : devel It builds those binary packages: golang-go-xdg-dev - Go interface for XDG standards To access further information about this package, please visit the following URL: https://mentors.debian.net/package/golang-go-xdg Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/golang-go-xdg/golang-go-xdg_0~bzr20140219-2.dsc or you can use git-buildpackage to build: gbp clone --pristine-tar https://anonscm.debian.org/git/pkg-go/packages/golang-go-xdg.git cd golang-go-xdg git checkout mentors gbp buildpackage -uc -us --git-ignore-branch --git-pristine-tar I also made it available on debomatic (amd64): http://debomatic-amd64.debian.net/distribution#unstable/golang-go-xdg/0~bzr20140219-2/buildlog Changes since the last upload: * Team upload. [ Paul Tagliamonte ] * Use a secure transport for the Vcs-Git and Vcs-Browser URL [ Roger Shimizu ] * debian/control: - Update Build-Depends on golang-check.v1-dev, in stead of golang-gocheck-dev which is already non-active upstream. - Use cgit URL for Vcs-Browser. * debian/patches: - Add a patch to use golang-check.v1-dev. - Add a patch to remove failure tests (Closes: #830446). Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#852981: RFS: golang-github-xtaci-kcp/2.14+git20170120+ds-1 [ITP] -- Full-Featured Reliable-UDP Library for golang
Package: sponsorship-requests Severity: wishlist X-Debbugs-Cc: pkg-go-maintain...@lists.alioth.debian.org, daniel820...@gmail.com, rogershim...@gmail.com Dear mentors, I am looking for a sponsor for my package "golang-github-xtaci-kcp" * Package name: golang-github-xtaci-kcp Version : 2.14+git20170120+ds-1 Upstream Author : Daniel Fu <daniel820...@gmail.com> * URL : https://github.com/xtaci/kcp-go * License : Expat Section : devel It builds those binary packages: golang-github-xtaci-kcp-dev - Full-Featured Reliable-UDP Library for golang To access further information about this package, please visit the following URL: https://mentors.debian.net/package/golang-github-xtaci-kcp Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/golang-github-xtaci-kcp/golang-github-xtaci-kcp_2.14+git20170120+ds-1.dsc or you can use git-buildpackage to build: gbp clone --pristine-tar https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-xtaci-kcp.git cd golang-github-xtaci-kcp git checkout mentors gbp buildpackage -uc -us --git-ignore-branch --git-pristine-tar I also made it available on debomatic (amd64): http://debomatic-amd64.debian.net/distribution#unstable/golang-github-xtaci-kcp/2.14+git20170120+ds-1/buildlog Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#852978: RFS: golang-github-xtaci-smux/1.0.4+git20170112+ds-1 [ITP] -- Simple Multiplexing for golang
Package: sponsorship-requests Severity: wishlist X-Debbugs-Cc: pkg-go-maintain...@lists.alioth.debian.org, daniel820...@gmail.com, rogershim...@gmail.com Dear mentors, I am looking for a sponsor for my package "golang-github-xtaci-smux" * Package name: golang-github-xtaci-smux Version : 1.0.4+git20170112+ds-1 Upstream Author : Daniel Fu <daniel820...@gmail.com> * URL : https://github.com/xtaci/smux * License : Expat Section : devel It builds those binary packages: golang-github-xtaci-smux-dev - Simple Multiplexing for golang To access further information about this package, please visit the following URL: https://mentors.debian.net/package/golang-github-xtaci-smux Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/golang-github-xtaci-smux/golang-github-xtaci-smux_1.0.4+git20170112+ds-1.dsc or you can use git-buildpackage to build: gbp clone --pristine-tar https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-xtaci-smux.git cd golang-github-xtaci-smux git checkout mentors gbp buildpackage -uc -us --git-ignore-branch --git-pristine-tar I also made it available on debomatic (amd64): http://debomatic-amd64.debian.net/distribution#unstable/golang-github-xtaci-smux/1.0.4+git20170112+ds-1/buildlog Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#842166: renewed sponsorship-request
On Mon, Jan 9, 2017 at 10:53 PM, Andrey Rahmatullin <w...@debian.org> wrote: > > The package is already in NEW and I don't think uploading a fix is worth > it so no. upload can be stacked, which means it's able to upload a new version while it's in NEW queue. though it seems it missed Stretch ... (soft freeze passed already) -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Move from asciidoc to asciidoc-base as build dependency
[ CC mentors list ] Dear Joseph, I find this change affects many packages, so I CC mentors. On Fri, Jan 6, 2017 at 1:17 PM, Joseph Herlant <herla...@gmail.com> wrote: > Package: shadowsocks-libev > Severity: wishlist > > Dear Maintainer, > > Asciidoc has been split in different packages in #637006 and #729242. > This split has arrived in Testing. > > To lower the number of dependencies to install during the build, could > you evaluate the switch of the build-depends from asciidoc to > asciidoc-base instead of asciidoc please? > > asciidoc-base is enough to build manpages and html pages. I'm thinking how to make the Build-Depends fits both sid/stretch and jessie-backports. Whether the following is good enough? or appending the version is better? Build-Depends: asciidoc-base | asciidoc Thanks! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#846231: RFS: shadowsocks-libev/2.5.6+ds-1~bpo8+1 -- lightweight and secure socks5 proxy
package: sponsorship-requests severity: normal X-Debbugs-Cc: max.c...@gmail.com, 073p...@gmail.com, rogershim...@gmail.com Dear mentors, I am looking for a sponsor for my package "shadowsocks-libev" for jessie-backports. * Package name: shadowsocks-libev Version : 2.5.6+ds-1~bpo8+1 Upstream Author : Max Lv <max.c...@gmail.com> * URL : https://www.shadowsocks.org * License : GPL-3+ Section : net It builds those binary packages: libshadowsocks-dev - lightweight and secure socks5 proxy (development files) libshadowsocks1 - lightweight and secure socks5 proxy (shared library) shadowsocks-libev - lightweight and secure socks5 proxy To access further information about this package, please visit the following URL: https://mentors.debian.net/package/shadowsocks-libev Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/shadowsocks-libev/shadowsocks-libev_2.5.6+ds-1~bpo8+1.dsc or you can use git-buildpackage to build: gbp clone --pristine-tar https://anonscm.debian.org/git/collab-maint/shadowsocks-libev.git cd shadowsocks-libev git checkout jessie-backports_2.5.6+ds-1 DIST=jessie-backports git-pbuilder create # Skip this if you already have pbuilder environment gbp buildpackage --git-ignore-branch --git-pristine-tar --git-pbuilder --git-dist=jessie-backports I pushed my changes to git repo: https://anonscm.debian.org/cgit/collab-maint/shadowsocks-libev.git/log/?h=jessie-backports_2.5.6+ds-1 Thank you! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#845934: RFS: libcorkipset/1.1.1+20150311-6~bpo8+1 -- C library to store sets/maps of IP address
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: rogershim...@gmail.com Dear Mentors, I am looking for a sponsor for my package "libcorkipset" into jessie-backports. It's a clean rebuild bpo from testing/stretch. * Package name: libcorkipset Version : 1.1.1+20150311-6~bpo8+1 Upstream Author : Douglas Creager <dcrea...@dcreager.net> * URL : https://github.com/redjack/ipset * License : BSD-3-clause Section : libs It builds those binary packages: libcorkipset-dev - C library to store sets/maps of IP address (development files) libcorkipset-doc - C library to store sets/maps of IP address (documentation files) libcorkipset-utils - C library to store sets/maps of IP address (utility files) libcorkipset1 - C library to store sets/maps of IP address To access further information about this package, please visit the following URL: https://mentors.debian.net/package/libcorkipset Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/libc/libcorkipset/libcorkipset_1.1.1+20150311-6~bpo8+1.dsc or you can use git-buildpackage to build: gbp clone --pristine-tar https://github.com/rogers0/libcorkipset git checkout jessie-backports # DIST=jessie-backports git-pbuilder create gbp buildpackage --git-ignore-branch --git-pristine-tar --git-pbuilder --git-dist=jessie-backports I pushed my changes to git repo: https://github.com/rogers0/libcorkipset - branch jessie-backports Thank you! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#845933: RFS: libcork/0.15.0+ds-10~bpo8+1 -- simple, easily embeddable, cross-platform C library
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: rogershim...@gmail.com Dear Mentors, I am looking for a sponsor for my package "libcork" into jessie-backports. It's a clean rebuild bpo from testing/stretch. * Package name: libcork Version : 0.15.0+ds-10~bpo8+1 Upstream Author : Douglas Creager <dcrea...@dcreager.net> * URL : https://libcork.readthedocs.io * License : BSD-3-clause Section : libs It builds those binary packages: libcork-dev - simple, easily embeddable, cross-platform C library (development libcork-doc - simple, easily embeddable, cross-platform C library (documentatio libcork15 - simple, easily embeddable, cross-platform C library To access further information about this package, please visit the following URL: https://mentors.debian.net/package/libcork Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/libc/libcork/libcork_0.15.0+ds-10~bpo8+1.dsc or you can use git-buildpackage to build: gbp clone --pristine-tar https://github.com/rogers0/libcork cd libcork git checkout jessie-backports # DIST=jessie-backports git-pbuilder create gbp buildpackage --git-ignore-branch --git-pristine-tar --git-pbuilder --git-dist=jessie-backports I pushed my changes to git repo: https://github.com/rogers0/libcork - branch jessie-backports Thank you! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#844537: RFS: fxlinuxprint/1.1.0+ds-1 [ITP] -- printer driver for Fuji Xerox printers
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: debian-print...@lists.debian.org, rogershim...@gmail.com Dear mentors, I am looking for a sponsor for my package "fxlinuxprint" I already tried to contact with printing team [0][1], but nobody responded about sponsor, so I come to mentors again. [0] https://bugs.debian.org/841194 [1] https://lists.debian.org/debian-printing/2016/10/msg00181.html * Package name: fxlinuxprint Version : 1.1.0+ds-1 Upstream Author : Fuji Xerox Co.,Ltd. * URL : https://www.fujixerox.co.jp/download/apeosport/download/c4300series/linux_module.html * License : GPL-2+ Section : text It builds those binary packages: printer-driver-fujixerox - printer driver for Fuji Xerox printers To access further information about this package, please visit the following URL: https://mentors.debian.net/package/fxlinuxprint Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/f/fxlinuxprint/fxlinuxprint_1.1.0+ds-1.dsc or you can use git-buildpackage to build: gbp clone --pristine-tar https://github.com/rogers0/fxlinuxprint git checkout mentors gbp buildpackage -uc -us --git-ignore-branch --git-pristine-tar Thank you! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Re: Bug#842528: RFS: wide-dhcpv6/20080615-17 -- DHCPv6 server/client for automatic IPv6 hosts configuration
Dear Gianfranco, On Thu, Nov 3, 2016 at 11:47 AM, Roger Shimizu <rogershim...@gmail.com> wrote: > I'll look at it later, and let you know whether I can help on that package. I cloned the git repo and tried to do "gbp buildpackage", but failed with error message: dpkg-source: error: cannot read boinc/debian/control: No such file or directory I checked the debian's boinc wiki [0], but didn't find anything useful. So I'm asking the simple command how to compile this package. Thank you! [0] https://wiki.debian.org/BOINC/Development/GitUsage Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Re: Bug#842528: RFS: wide-dhcpv6/20080615-17 -- DHCPv6 server/client for automatic IPv6 hosts configuration
On Wed, Nov 2, 2016 at 8:34 PM, Gianfranco Costamagna <costamagnagianfra...@yahoo.it> wrote: > >>PS. The parallel building issue of my package is fixed and uploaded. > > I would appreciate if you could fix src:boinc to build in parallel :) > You seems to have an high autoconf knowledge, and all my attempts failed > so far... I'm not familiar with autotools, except having basic knowledge on makefile. I'll look at it later, and let you know whether I can help on that package. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Re: Bug#842528: RFS: wide-dhcpv6/20080615-17 -- DHCPv6 server/client for automatic IPv6 hosts configuration
On Tue, Nov 1, 2016 at 2:26 PM, Adam Borowski <kilob...@angband.pl> wrote: > > Why won't you put "export DEB_BUILD_OPTIONS=parallel=8" into your ~/.bashrc? > It's not like your number of cores changes, and even if it does, you can > export DEB_BUILD_OPTIONS=parallel=`nproc` > > (Please don't use `grep ^processor /proc/cpuinfo` nor `getconf > _NPROCESSORS_ONLN` as neither is portable enough.) When I read the debhelper 10 post [0], it says "defaults to building in parallel", so I thought no other option is needed. Thanks for letting me know it's better to put this into .bashrc, too. [0] https://nthykier.wordpress.com/2016/09/11/debhelper-10-is-now-available/ PS. The parallel building issue of my package is fixed and uploaded. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#842528: RFS: wide-dhcpv6/20080615-17 -- DHCPv6 server/client for automatic IPv6 hosts configuration
On Tue, Nov 1, 2016 at 8:36 AM, Gianfranco Costamagna <locutusofb...@debian.org> wrote: > > not outdated, just like mine, we don't use parallel in building > > DEB_BUILD_OPTIONS=parallel=8 can reproduce the issue (and bad me > I didn't check that) > probably some dependencies are not handled correctly in Makefile.in > and having parallel enabled by default in compat 10 can't work. Dear Gianfranco, Thanks for letting me know the options to specify parallel number. This helped me to get a build error reproducible environment so I can spend some time and fix it finally. The fixed build is uploaded. Let us see the result in buildd. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#842528: RFS: wide-dhcpv6/20080615-17 -- DHCPv6 server/client for automatic IPv6 hosts configuration
On Tue, Nov 1, 2016 at 1:45 AM, Gianfranco Costamagna <locutusofb...@debian.org> wrote: > Hi Roger, > >>I am looking for a sponsor for my package "wide-dhcpv6" > > done >>If it's convenient for you, please kindly setup DM upload permission >>of this package for me. > > oh well, I gave them to you before reading the whole email :) Dear Gianfranco, Thanks for your trust! However the buildd seems not like my upload this time. I guess it's caused by parallel support from debhelper 10. Maybe because my PC is outdated :-P I'll try to fix this in couple of days. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#842528: RFS: wide-dhcpv6/20080615-17 -- DHCPv6 server/client for automatic IPv6 hosts configuration
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "wide-dhcpv6" * Package name: wide-dhcpv6 Version : 20080615-17 Upstream Author : SUZUKI Shinsuke <s...@kame.net> * URL : http://wide-dhcpv6.sourceforge.net/ * License : BSD-3-clause Section : net It builds those binary packages: wide-dhcpv6-client - DHCPv6 client for automatic IPv6 hosts configuration wide-dhcpv6-client-udeb - DHCPv6 client for automatic IPv6 hosts configuration (udeb) wide-dhcpv6-relay - DHCPv6 relay for automatic IPv6 hosts configuration wide-dhcpv6-server - DHCPv6 server for automatic IPv6 hosts configuration To access further information about this package, please visit the following URL: https://mentors.debian.net/package/wide-dhcpv6 Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/w/wide-dhcpv6/wide-dhcpv6_20080615-17.dsc or you can use git-buildpackage to build: gbp clone --pristine-tar https://github.com/rogers0/packaging_wide-dhcpv6 wide-dhcpv6 cd wide-dhcpv6 git checkout mentors gbp buildpackage -uc -us --git-ignore-branch --git-pristine-tar Changes since the last upload: * debian/control: - Add lsb-base as dependency to all binary packages (except udeb), since the init script sources /lib/lsb/init-functions utility functions - Bump debhelper version to 10 - Upgrade VCS URL to secure one (https) - Bump policy version to 3.9.8 (no actual change required) * debian/rules: - Add a few comments - Add hardening support * debian/patches: - Add 0016 patch to fix typo in dhcp6c.8 manpage * debian/copyright: - Upgrade URL to secure one (https) - Update my copyright year I pushed my changes to git repo: https://github.com/rogers0/packaging_wide-dhcpv6 wide-dhcpv6 branch: mentors If it's convenient for you, please kindly setup DM upload permission of this package for me. I have maintained this package for a few releases. Thank you! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#841749: RFS: adjtimex/1.29-8 -- kernel time variables configuration utility
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "adjtimex" * Package name: adjtimex * Version : 1.29-8 * Upstream Author : Steven S. Dick <s...@nevets.oau.org>, James R. Van Zandt <j...@comcast.net> * URL : http://metalab.unc.edu/pub/Linux/system/admin/time * License : GPL-2 * Section : admin It builds those binary packages: adjtimex - kernel time variables configuration utility To access further information about this package, please visit the following URL: http://mentors.debian.net/package/adjtimex Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/a/adjtimex/adjtimex_1.29-8.dsc or you can use git-buildpackage to build: gbp clone --pristine-tar https://github.com/rogers0/adjtimex cd adjtimex git checkout mentors gbp buildpackage -uc -us --git-ignore-branch --git-pristine-tar Changes since the last upload: * debian/patches: - Improve precision. Thanks Christopher Alexander Tobias Schulze. (Closes: #633082). - Update patches to make compatible with "gbp pq" command. * Upgrade to support debhelper 10 * debian/copyright: - Update URL to make use of https instead of http, when possible * debian/control: - Add lsb-base as dependency to package shadowsocks-libev, since the init script sources /lib/lsb/init-functions utility functions - Bump policy version to 3.9.8 (no actual change required) * debian/adjtimex.service: - Add documentation line. Thanks to lintian. * debian/rules: - Add a few comments - Remove hardening setting already enabled by default since compat=9 I pushed my changes to git repo: https://github.com/rogers0/adjtimex branch: mentors If it's convenient for you, please kindly setup DM upload permission of this package for me. I have maintained this package for a few releases. Thank you! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Re: [ANOUNCE] Debtemplate
On Mon, Oct 17, 2016 at 11:27 PM, Sean Whitton <spwhit...@spwhitton.name> wrote: > Hello Dmitry, > > On Sun, Oct 16, 2016 at 07:53:53AM +0300, Dmitry Bogatov wrote: >> I anounce it to resolve following questions: >> >> - Is it useful for anyone but me? >> - Should it be packaged as native Debian package? > > Looking forward to this. I like ideas that can simplify the mentors/RFS process. Maybe it's not suitable for this thread, but I'd like to mention that there's another approach that implement this on web server side. - https://lists.debian.org/debian-mentors/2016/07/threads.html#00218 - https://lists.debian.org/debian-mentors/2016/08/msg00108.html It was posted to the mentors list (above thread links), and I'm expecting that it can be also merged to production system of mentors. (The author, Hayashi Kentaro, introduced his work in monthly Tokyo Debian meeting previously, so I got to know this.) Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#840672: RFS: libcork/0.15.0+ds-7~exp1 -- simple, easily embeddable, cross-platform C library
On Sat, Oct 15, 2016 at 4:11 PM, Gianfranco Costamagna <locutusofb...@debian.org> wrote: > Hi, > >>Actually it's an issue raised by James Clarke: >>- https://lists.debian.org/debian-sparc/2016/08/msg00035.html >> >>As he pointed out, it's a bug in cmake config in libcork source tree. >> >>It involves library transition, and I was not familiar with it, so I >>didn't try to fix it until recently I learned how to do transition so >>here's the upload and RFS report. >> >>Since all packages depends on libcork is maintained by me, and I can >>update those rdepends package accordingly, so there's no risk for this > >>transition. > > well, this isn't the real problem. > The real problem is that you have uploaded a version without the patch > https://lists.debian.org/debian-sparc/2016/08/msg00035.html > There is a patch here, you should apply it then. James provided a patch to fix "unaligned access" issue at above thread, and he also pointed out the SONAME version issue, which he didn't provide a patch, so I created the patch based on his suggestion. As the original issue of the "unaligned access" patch only occurs on the sparc64 platform, I need some time to fully test whether the patch applies well on other platform. Considering transition freeze is drawing near (3 weeks later), so I want to push the transition first, and after the transition finished I can handle this unaligned access patch James provided. Hope it make things clear to you. Thank you! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#840672: RFS: libcork/0.15.0+ds-7~exp1 -- simple, easily embeddable, cross-platform C library
On Sat, Oct 15, 2016 at 2:12 AM, Gianfranco Costamagna <locutusofb...@debian.org> wrote: > control: owner -1 ! > control: tags -1 moreinfo > >>I am looking for a sponsor for my package "libcork". > >>This is the first time I'm trying to raise a library transition. >>So if there's anything wrong, just let me know. Thank you! > > bumping soname with the same upstream tarball and no changes > > makes no real sense. > If you want to bump soname you need to have API/ABI changes in the packaging, > and then the need to do a transition. Dear Gianfranco, Actually it's an issue raised by James Clarke: - https://lists.debian.org/debian-sparc/2016/08/msg00035.html As he pointed out, it's a bug in cmake config in libcork source tree. It involves library transition, and I was not familiar with it, so I didn't try to fix it until recently I learned how to do transition so here's the upload and RFS report. Since all packages depends on libcork is maintained by me, and I can update those rdepends package accordingly, so there's no risk for this transition. Thanks! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#840672: RFS: libcork/0.15.0+ds-7~exp1 -- simple, easily embeddable, cross-platform C library
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: rogershim...@gmail.com Dear mentors, I am looking for a sponsor for my package "libcork". This is the first time I'm trying to raise a library transition. So if there's anything wrong, just let me know. Thank you! * Package name: libcork Version : 0.15.0+ds-7~exp1 Upstream Author : Douglas Creager <douglas.crea...@redjack.com> * URL : https://libcork.readthedocs.io * License : BSD-3-clause Section : libs It builds those binary packages: libcork-dev - simple, easily embeddable, cross-platform C library (development libcork-doc - simple, easily embeddable, cross-platform C library (documentatio libcork16 - simple, easily embeddable, cross-platform C library To access further information about this package, please visit the following URL: https://mentors.debian.net/package/libcork Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/libc/libcork/libcork_0.15.0+ds-7~exp1.dsc or you can use git-buildpackage to build: gbp clone --pristine-tar https://github.com/rogers0/libcork cd libcork git checkout transition gbp buildpackage -uc -us --git-ignore-branch --git-pristine-tar Changes since the last upload: * debian/control: - Bump up libcork SONAME to libcork16 * debian/patches: - Add 0011 patch, to make SONAME version the same as library version I pushed my changes to git repo: https://github.com/rogers0/libcork branch: transition Thank you! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#840502: RFS: shadowsocks-libev/2.4.8+ds-1~bpo8+1 -- lightweight and secure socks5 proxy
package: sponsorship-requests severity: normal X-Debbugs-Cc: rogershim...@gmail.com, max.c...@gmail.com, 073p...@gmail.com Dear mentors, I am looking for a sponsor for my package "shadowsocks-libev" for jessie-backports. * Package name: shadowsocks-libev Version : 2.4.8+ds-1~bpo8+1 Upstream Author : Max Lv <max.c...@gmail.com> * URL : https://www.shadowsocks.org * License : GPL-3+ Section : net It builds those binary packages: libshadowsocks-dev - lightweight and secure socks5 proxy (development files) libshadowsocks1 - lightweight and secure socks5 proxy (shared library) shadowsocks-libev - lightweight and secure socks5 proxy To access further information about this package, please visit the following URL: https://mentors.debian.net/package/shadowsocks-libev Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/shadowsocks-libev/shadowsocks-libev_2.4.8+ds-1~bpo8+1.dsc or you can use git-buildpackage to build: gbp clone --pristine-tar https://anonscm.debian.org/git/collab-maint/shadowsocks-libev.git git checkout jessie-backports_2.4.8+ds-1 DIST=jessie-backports git-pbuilder create # Skip this if you already have pbuilder environment gbp buildpackage --git-ignore-branch --git-pristine-tar --git-pbuilder --git-dist=jessie-backports I pushed my changes to git repo: https://anonscm.debian.org/cgit/collab-maint/shadowsocks-libev.git/log/?h=jessie-backports_2.4.8+ds-1 Thank you! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#839739: RFS: shadowsocks-libev/2.5.3+ds-1 -- lightweight and secure socks5 proxy
On Tue, Oct 4, 2016 at 9:20 PM, Gianfranco Costamagna <locutusofb...@debian.org> wrote: > Hi > >>I have DM upload access of package "shadowsocks-libev", but since >>there's a library soname version up, so I am looking for a sponsor for >>it. > > --- shadowsocks-libev-2.4.8+ds/m4/pcre.m4 1970-01-01 01:00:00.0 > +0100 > +++ shadowsocks-libev-2.5.3+ds/m4/pcre.m4 2016-09-25 18:42:43.0 > +0200 > @@ -0,0 +1,152 @@ > +dnl -*- autoconf -*- > +dnl Licensed to the Apache Software Foundation (ASF) under one or more > +dnl contributor license agreements. See the NOTICE file distributed with > > > > other stuff LGTM Dear Gianfranco, Thanks for your review! Added license for m4/ folder, and pushed to mentors2 branch. (previous mentors branch is removed) so you can use git-buildpackage to build: gbp clone --pristine-tar https://anonscm.debian.org/git/collab-maint/shadowsocks-libev.git git checkout mentors2 gbp buildpackage -uc -us --git-ignore-branch --git-pristine-tar Updated deb packages are uploaded to mentors already. Thanks! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#839739: RFS: shadowsocks-libev/2.5.3+ds-1 -- lightweight and secure socks5 proxy
package: sponsorship-requests severity: normal X-Debbugs-Cc: rogershim...@gmail.com, max.c...@gmail.com, 073p...@gmail.com Dear mentors, I have DM upload access of package "shadowsocks-libev", but since there's a library soname version up, so I am looking for a sponsor for it. There's no other package in the archive depends on this library, so I think there's no need to proceed the library transition. * Package name: shadowsocks-libev Version : 2.5.3+ds-1 Upstream Author : Max Lv <max.c...@gmail.com> * URL : https://www.shadowsocks.org * License : GPL-3+ Section : net It builds those binary packages: libshadowsocks-dev - lightweight and secure socks5 proxy (development files) libshadowsocks2 - lightweight and secure socks5 proxy (shared library) shadowsocks-libev - lightweight and secure socks5 proxy To access further information about this package, please visit the following URL: https://mentors.debian.net/package/shadowsocks-libev Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/shadowsocks-libev/shadowsocks-libev_2.5.3+ds-1.dsc or you can use git-buildpackage to build: gbp clone --pristine-tar https://anonscm.debian.org/git/collab-maint/shadowsocks-libev.git git checkout mentors gbp buildpackage -uc -us --git-ignore-branch --git-pristine-tar Changes since the last upload: * Update to upstream v2.5.3 - Remove patches merged by upstream: 0003 - Update patch 0001 0002: make it appliable to this version - Update debian/copyright: remove .github/, add newly appended files * debian/control: - Update based on upstream's change - Add Replaces and Breaks for lib version up * debian/maint-tools/: - Add two script to make life easier for new upstream release I pushed my changes to git repo: https://anonscm.debian.org/cgit/collab-maint/shadowsocks-libev.git/log/?h=mentors Thank you! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#832122: RFS: shadowsocks-libev/2.4.8+ds-1 -- lightweight and secure socks5 proxy
package: sponsorship-requests severity: normal X-Debbugs-Cc: rogershim...@gmail.com, max.c...@gmail.com, 073p...@gmail.com Dear mentors, I am looking for a sponsor for my package "shadowsocks-libev" * Package name: shadowsocks-libev Version : 2.4.8+ds-1 Upstream Author : Max Lv <max.c...@gmail.com> * URL : https://www.shadowsocks.org * License : GPL-3+ Section : net It builds those binary packages: libshadowsocks-dev - lightweight and secure socks5 proxy (development files) libshadowsocks1 - lightweight and secure socks5 proxy (shared library) shadowsocks-libev - lightweight and secure socks5 proxy To access further information about this package, please visit the following URL: https://mentors.debian.net/package/shadowsocks-libev Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/shadowsocks-libev/shadowsocks-libev_2.4.8+ds-1.dsc or you can use git-buildpackage to build: gbp clone --pristine-tar https://anonscm.debian.org/git/collab-maint/shadowsocks-libev.git git checkout new gbp buildpackage -uc -us --git-ignore-branch --git-pristine-tar Changes since the last upload: * Update to upstream v2.4.8 - Remove patches merged by upstream: 0003 0004 0005 - Update patch 0001: make it appliable to this version - Update debian/control to add newly appended build-dep - Update debian/rulesi to adjust param ordering as close as upstream - Update debian/copyright to remove man/, which merged into doc/ folder * debian/patches: - Cherry-Pick upstream patch 0003: add a few spaces to asciidoc to make lintian happy. Thanks to Max Lv for fixing this. I pushed my changes to git repo: https://anonscm.debian.org/cgit/collab-maint/shadowsocks-libev.git/log/?h=new If it's convenient for you, please kindly setup DM upload permission of this package for me. Thank you! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#832032: RFS: libcorkipset/1.1.1+20150311-2 -- C library to store sets/maps of IP address
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: rogershim...@gmail.com Dear mentors, I am looking for a sponsor for my package "libcorkipset" * Package name: libcorkipset Version : 1.1.1+20150311-2 Upstream Author : Douglas Creager <douglas.crea...@redjack.com> * URL : https://github.com/redjack/ipset * License : BSD-3-clause Section : libs It builds those binary packages: libcorkipset-dev - C library to store sets/maps of IP address (development files) libcorkipset-doc - C library to store sets/maps of IP address (documentation files) libcorkipset-utils - C library to store sets/maps of IP address (utility files) libcorkipset1 - C library to store sets/maps of IP address To access further information about this package, please visit the following URL: https://mentors.debian.net/package/libcorkipset Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/libr/libcorkipset/libcorkipset_1.1.1+20150311-2.dsc Changes since the last upload: * debian/rules: - Remove "--builddirectory=build" * debian/patches: - Update 0001: Include all debian version as library version. - Update 0004: Update test of python-cram according to libcork, although there's no cram unit test item now. - Add 0009: Support CMake Threads. - Add 0010: Fix typo in src/CMakeLists.txt * debian/libcorkipset-doc.docs: - Add example code as docs * debian/control, debian/rules & debian/libcorkipset-utils.install: - Add new "-utils" package, to include binary tools. manpages are created by help2man tool in debian/rules. I pushed my changes to git repo (branch "new"): https://github.com/rogers0/libcorkipset/tree/new If it's convenient for you, please kindly setup DM upload permission of this package for me. Thank you! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#831694: RFS: shadowsocks-libev/2.4.7+20160630+ds-3 -- lightweight and secure socks5 proxy
Dear Christian, Thanks for your review! On Tue, Jul 19, 2016 at 12:21 AM, Christian Seiler <christ...@iwakd.de> wrote: > I'm not a DD, so I can't sponsor, but: > > On 07/18/2016 04:53 PM, Roger Shimizu wrote: >> * debian/rules: >> - Add param "--disable-ssp" to dh_auto_configure command. >> Thanks to Aaron M. Ucko and Boyuan Yang. (Closes: #829498) > > Please don't disable the SSP unconditionally, because it's a useful > defense-in-depth strategy. Especially since you are packaging a > network service, I would really recommend not doing that. My bad on wording of changelog. Actually it means turn off the broken hardening by upstream, and only use hardening by Debian (from dpkg-buildflags) So this change won't lower the security check. >> - Cherry-Pick two patch from upstream as 0004 and 0005 > > Generally you should describe in the changelog what these patches > do. I would hence suggest an entry like: > >- Cherry-pick the following upstream patches: >* Fix typo in argument passed to manager command. >* Use SO_REUSEADDR for remote socket Indeed. This makes more clear. I'll update the changelog entry on next release. Thank you! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#831694: RFS: shadowsocks-libev/2.4.7+20160630+ds-3 -- lightweight and secure socks5 proxy
package: sponsorship-requests severity: normal X-Debbugs-Cc: rogershim...@gmail.com, max.c...@gmail.com, 073p...@gmail.com Dear mentors, I am looking for a sponsor for my package "shadowsocks-libev" * Package name: shadowsocks-libev Version : 2.4.7+20160630+ds-3 Upstream Author : Max Lv <max.c...@gmail.com> * URL : https://www.shadowsocks.org * License : GPL-3+ Section : net It builds those binary packages: libshadowsocks-dev - lightweight and secure socks5 proxy (development files) libshadowsocks1 - lightweight and secure socks5 proxy (shared library) shadowsocks-libev - lightweight and secure socks5 proxy To access further information about this package, please visit the following URL: https://mentors.debian.net/package/shadowsocks-libev Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/shadowsocks-libev/shadowsocks-libev_2.4.7+20160630+ds-3.dsc Changes since the last upload: * debian/rules: - Add param "--disable-ssp" to dh_auto_configure command. Thanks to Aaron M. Ucko and Boyuan Yang. (Closes: #829498) * debian/patches: - Add 0003 patch, to fix PATH_MAX for GNU/Hurd. - Cherry-Pick two patch from upstream as 0004 and 0005 I pushed my changes to git repo: https://anonscm.debian.org/cgit/collab-maint/shadowsocks-libev.git/log/?h=new If it's convenient for you, please kindly setup DM upload permission of this package for me. Thank you! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Re: blocked mentors queue?
On Sat, Jul 16, 2016 at 5:26 PM, foss.freedom <foss.free...@gmail.com> wrote: > Hi, > > I sent a package up to the mentors queue last night but it hasn't appeared > in "my packages" of the mentors website. > > I've checked ftp://mentors.debian.net/ and my package is there as are a few > other packages. > > I've tried to send a revised package today both via HTTP and FTP but am > getting a 403 / 553 error respectively. > > I've tried to delete an older version that was listed on "my packages" - my > packages now says I havent got any packages uploaded I had similar issue before. It need to contact <supp...@mentors.debian.net> to let the admin remove the broken uploaded package. After that, you'll be able to upload again. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#830236: RFS: libcork/0.15.0+ds-4 -- simple, easily embeddable, cross-platform C library
On Fri, Jul 15, 2016 at 12:15 PM, Gianfranco Costamagna <locutusofb...@debian.org> wrote: > Hi, > >> https://launchpad.net/ubuntu/+source/libcork/0.15.0+ds-5 > > > > some hours ago, I had to retry the build on amd64 and i386 archs if I remember > correctly. > > Retrying the build was fine > (I remember it failed for testsuite failures) > > bug closed, > thanks Greatly Thank you for helping this package! Yes, I know yesterday amd64/i386 failed to build, but I checked again moment ago and found it became fine. I was wondering why ubuntu is so smart to restart the build again. So now I know the answer :-D Thanks again! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
