Bug#862875: marked as done (RFS: libzc/0.3.6-1 [ITP] -- fast zip cracking library)
Your message dated Tue, 31 Oct 2017 04:09:30 +0100 with message-id <20171031030930.gctevfilvbgmc...@angband.pl> and subject line Re: Bug#862875: RFS: libzc/0.3.1-1 [ITP] -- fast zip cracking library has caused the Debian Bug report #862875, regarding RFS: libzc/0.3.6-1 [ITP] -- fast zip cracking library to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 862875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862875 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "libzc". Package name: libzc Version : 0.3.1-1 Upstream Author : Marc Ferland URL : https://github.com/mferland/libzc License : GPL-3 Section : libs It builds those binary packages: libzc-dev - fast password cracking library and client for zip archives - development headers libzc3 - fast password cracking library and client for zip archives To access further information about this package, please visit the following URL: https://mentors.debian.net/package/libzc Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/libz/libzc/libzc_0.3.1-1.dsc More information about libzc can be obtained from https://github.com/mferland/libzc Regards, Marc Ferland --- End Message --- --- Begin Message --- On Thu, Oct 26, 2017 at 09:59:26PM -0400, Marc Ferland wrote: > > The package fails to build on most architectures, with a timeout in the > > testsuite: > > > ... > > Running suite(s): reduce > > 66%: Checks: 3, Failures: 0, Errors: 1 > > check_reduce.c:60:E:Core:test_can_generate_next_array_from_plaintext:0: > > (after this point) Test timeout expired > > FAIL reduce (exit status: 1) > > Some tests can take quite some time to finish. I've excluded those > from running when > doing an 'ordinary' make check. This fix and other small fixes are > available in the latest > version: > > https://mentors.debian.net/debian/pool/main/libz/libzc/libzc_0.3.6-1.dsc Uploaded, in NEW. I've chosen armhf as the sacrificial no-buildlog architecture. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ Laws we want back: Poland, Dz.U. 1921 nr.30 poz.177 (also Dz.U. ⣾⠁⢰⠒⠀⣿⡁ 1920 nr.11 poz.61): Art.2: An official, guilty of accepting a gift ⢿⡄⠘⠷⠚⠋⠀ or another material benefit, or a promise thereof, [in matters ⠈⠳⣄ relevant to duties], shall be punished by death by shooting.--- End Message ---
Bug#862115: marked as done (RFS: lr/1.1-1 [ITP] -- list files, recursively)
Your message dated Mon, 30 Oct 2017 22:20:09 + with message-id and subject line closing RFS: lr/1.1-1 [ITP] -- list files, recursively has caused the Debian Bug report #862115, regarding RFS: lr/1.1-1 [ITP] -- list files, recursively to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 862115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862115 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: wishlist Control: block 861792 by -1 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear mentors, I'm looking for a sponsor for my package `lr`: * Package name: lr Version : 0.4 Upstream Author : Leah Neukirchen * URL : https://github.com/chneukirchen/lr * License : MIT Programming Lang: C Description : list files, recursively lr is a new tool for generating file listings, which includes the best features of ls(1), find(1), stat(1) and du(1). It has a powerful and user-friendly filter syntax, sorting and formatting capabilities. Differences with find(1) and ls(1) are hilighted on the homepage: https://github.com/chneukirchen/lr#benefits I uploaded the (signed) source and binary packages, and build logs, at https://nicolas.braud-santoni.eu/tmp/deb/ Best, nicoo - -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (900, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- iQJNBAEBCgA3FiEEiWEbFKE2h/s1SpJPnU+IAQz+GeMFAlkQp8IZHG5pY29sYXNA YnJhdWQtc2FudG9uaS5ldQAKCRCdT4gBDP4Z48SdEADSMbuiusDBeyFDh5HhOJvT 2c1jZDDbxgERIacaQsEDIE5yB8nX4QedbB/wQqQvcYT0tdyv4hBA2fHJnoMDUUIA K4Clgz+kfKlKr4M55YLppiXz2XQJWpznmYvS/OO74meAcCYdoZ74D9ZzXBUhB0Vp KBgnSmHifQ/pmsxpiyRJ2KWAzGVyf4ktDUHUo4ksHMXXVI+imNVZsLGxD8TZt8w4 PKZSJ2ZM1Od5ydFEfytEy8nK/iFMst41HaFVj/JeplkI2HWL14ALMswExrhlAE3L 5izCAUx/jcmICp96psYPCZfRMuL4wZcOIaIVNUobJIGNO+r+Ex4Kq5Y5EagTpJrO 69HqLL7xRE7o1SOLmfp3lZ824rwZZhQjBDraZMhOQoKRFLwbRSAIPkSWO0vv94vY NySc9n4hTv7StJG48V9apmeznYpdkmYmyvi5YMHvxHVJ9eLHhBkS0amX4sphvRRd 1STmg/TQ2y8nCchfH5mQjcEElDjPlK/jrnvTiA1eOmb9a6/ojENHT7qESOHjkej+ zgpSoKatzhHp+dg8EWw+B7REN/a6cfi/zoEgsrqkHEiGX3/2xy/x41XBrRWflOIv E1ofJyIH5486f0+piIyLkQOMxvArLO5d6bC2nIwyAzIgUs7kX8QnYAd86JxCM1HP l7FIWQJQyidjX1evuYJVjw== =OUn3 -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Package lr version 1.1-1 is in NEW now, and the package at mentors is not newer (2017-10-30) than the package in NEW (2017-10-30), so there is currently no package to sponsor. https://ftp-master.debian.org/new/lr_1.1-1.html https://mentors.debian.net/package/lr Please remove the package from mentors or mark it "needs sponsor = no". If for some reason you need to replace the package in NEW, then you can upload an updated package to mentors and feel free to reopen this RFS 862115 or open a new RFS.--- End Message ---
Bug#880264: RFS: kconfig-frontends/4.11.0.1-1 [ITP] -- Standalone implementation of the Linux Kconfig parser and frontends
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "kconfig-frontends" * Package name : kconfig-frontends Version : 4.11.0.1-1 Upstream Author : Yann Morin * URL : http://ymorin.is-a-geek.org/projects/kconfig-frontends * License : GPL-2+ Programming Lang: C Section : devel Description : Standalone implementation of the Linux Kconfig parser and frontends It builds those binary packages: kconfig-greontds: Kconfig-frontends provides the kconfig parser, as well as all the frontends (dialog, ncurses, Qt and Gtk based) to configure and generate config files and config headers for various projects. To access further information about this package, please visit the following URL: https://mentors.debian.net/package/kconfig-frontends Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/k/kconfig-frontends/kconfig-frontends_4.11.0.1-1.dsc This project aims to give an out of Linux tree support for Kconfig files, in order to use the same syntax and mechanisms for emedded (or any other) project configuration. This permits to highly simplify the configuration part and to help in the integration of the configuration as much in the project's production system as in the project's code itself (through autoconf.h support). Regards, -- OPhilippe Thierry. /Y\/ Hardened embedded systems o#o GPG: F889 D7F7 85CA E380 DBDA D796 99C5 4C59 C22D 06D4 signature.asc Description: OpenPGP digital signature
Bug#879720: RFS: runescape/0.2-1 [QA] -- Multiplayer online game set in a fantasy world
> Uploaded! Many thanks for your contributions to Debian! Thank you very much for your instructions before loading the package. :D -- ⢀⣴⠾⠻⢶⣦⠀ Carlos Donizete Froes [a.k.a coringao] ⣾⠁⢠⠒⠀⣿⡁ - https://wiki.debian.org/coringao ⢿⡄⠘⠷⠚⠋⠀ GPG: 4096R/B638B780 ⠈⠳⣄⠀⠀⠀ 2157 630B D441 A775 BEFF D35F FA63 ADA6 B638 B780 signature.asc Description: This is a digitally signed message part
Bug#848327: marked as done (RFS: libu2f-host/1.1.4-1 [RC])
Your message dated Mon, 30 Oct 2017 16:22:31 + with message-id and subject line closing RFS: libu2f-host/1.1.4-1 [RC] has caused the Debian Bug report #848327, regarding RFS: libu2f-host/1.1.4-1 [RC] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 848327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848327 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal Control: block 824532 by -1 Control: block 846358 by -1 Control: block 846359 by -1 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear Mentors, I am looking for a sponsor for my package "libu2f-host": * Package name: libu2f-host Version : 1.1.3-1 Upstream Author : Yubico AG * URL : https://developers.yubico.com/libu2f-host/ * License : LGPLv2 * Section : libs This updates brings: - - a fix for #846358, so that rules for the right udev version are installed; - - as per #846359 and #824532, this creates a new binary package, libu2f-common, containing the udev rules; - - the new upstream version brings udev rules for additional devices. The source and binary (Architecture: all) packages are available here: https://nicolas.braud-santoni.eu/tmp/deb I also uploaded it to mentors.d.n, but it doesn't seem to be visible there yet. Best, nicoo - -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- iQJNBAEBCgA3FiEEiWEbFKE2h/s1SpJPnU+IAQz+GeMFAlhTyOgZHG5pY29sYXNA YnJhdWQtc2FudG9uaS5ldQAKCRCdT4gBDP4Z4yn3EACCh0Jxho0X6oOvR7+e9vRx LFnD92R2HEa+2dXqIr5wVMZQHzSHc814Hr9iSM7yEfeiNEa+OCy3tMYexQ3+wYIJ OHbkzkek9y4DEBpyY12GQIS/W/iWSQFOOch+yQUyf9KORo++7qf7BYWBx6CUI0/S Xr3IaF2kXV/vEQzuGlHcqlRE+9gInu8/Ov+BeygvzGoR2GQgz6Scmcv2t0KViDg+ tgmgsLhQ4iECxQrh9neMaeWmccgAH8ftYGt89kPvbgdBg3NyfcbVO3l3IJldCGUG KHn8lpO62skHqtnA5YTt8ao236QrlPNiqom5a9rqxU6dJ0k0YOIZBS6Im8RmG1Xf qtLgdAEbn0TRU18h1ljOvELSyovwyLoq0KBIVCsntJjXePtVG/x8wR0JrPYfYL0+ H4VA13PNYvkwWabLcVrs9hnXCp6feeDFSMnxK0ujfyU87yUCdrTl9OG0alHVDwki Dl+6PhLPgkbam2YjO3eOVLKSDL4Ui02CONlBGY01oyoP7yeNb+4ieIDOuYESdmtx OoAfojtlQAqse7zA7/ZpfCPlVo1RfNV9NqPBs0f0GdvOvNNpIwjU6sK4iiBCgeRv 34qlH8tLhBLpAIiBl26n4+LtuiMcBNUtEo2w2rGdsohyRtzdoiydM4JRQIb2Qp8v o1zMNcA6Di3m/Sg20loSbg== =bX10 -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Package libu2f-host version 1.1.4-1 is in NEW now, and the package at mentors is not newer (2017-10-30) than the package in NEW (2017-10-30), so there is currently no package to sponsor. https://ftp-master.debian.org/new/libu2f-host_1.1.4-1.html https://mentors.debian.net/package/libu2f-host Please remove the package from mentors or mark it "needs sponsor = no". If for some reason you need to replace the package in NEW, then you can upload an updated package to mentors and feel free to reopen this RFS 848327 or open a new RFS.--- End Message ---
Bug#880007: marked as done (RFS: brightnessctl/0.3-1 [ITP])
Your message dated Mon, 30 Oct 2017 16:22:29 + with message-id and subject line closing RFS: brightnessctl/0.3-1 [ITP] has caused the Debian Bug report #880007, regarding RFS: brightnessctl/0.3-1 [ITP] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 880007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880007 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "brightnessctl" * Package name: brightnessctl Version : 0.3-1 Upstream Author : Mykyta Holuakha * URL : https://github.com/Hummer12007/brightnessctl * License : Expat Section : misc It builds those binary packages: brightness-udev - Control backlight brightness - udev rules brightnessctl - Control backlight brightness The udev rules simply enable non-root users (in the video and input groups) to control the brightness of backlights and LEDs, and brightnessctl is a very simple tool that is more user-friendly than writing to /sys. To access further information about this package, please visit the following URL: https://mentors.debian.net/package/brightnessctl Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/b/brightnessctl/brightnessctl_0.3-1.dsc Best, nicoo signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Package brightnessctl version 0.3-1 is in NEW now, and the package at mentors is not newer (2017-10-28) than the package in NEW (2017-10-28), so there is currently no package to sponsor. https://ftp-master.debian.org/new/brightnessctl_0.3-1.html https://mentors.debian.net/package/brightnessctl Please remove the package from mentors or mark it "needs sponsor = no". If for some reason you need to replace the package in NEW, then you can upload an updated package to mentors and feel free to reopen this RFS 880007 or open a new RFS.--- End Message ---
Bug#862114: Bug#862115: RFS: xe/0.8-1 (ITP, #862114) & lr/0.4-1 (ITP, #862115)
On Mon, 2017-10-30 at 15:01 +0100, Nicolas Braud-Santoni wrote: > Oh, I didn't realise this wasn't a person :O Yeah, it probably should migrate to mentors and a more obvious sender address. > I guess the obvious solution is for me to become a DD and sponsor uploads :P That would definitely help, I wish you the best of luck towards that. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#862114: Bug#862115: RFS: xe/0.8-1 (ITP, #862114) & lr/0.4-1 (ITP, #862115)
On Mon, Oct 30, 2017 at 09:56:10PM +0800, Paul Wise wrote: > On Mon, Oct 30, 2017 at 9:45 PM, Nicolas Braud-Santoni wrote: > > I appreciate that Bart was likely trying to triage RFSes, but closing it > > rather than asking to reupload to mentors.d.n feels somewhat unfriendly, > > especially when the packaging repo is available, and up-to-date, on alioth. > > That is a cron job that syncs the state of RFSes with the archive and > mentors. The maintainer of the cron job is fairly MIA, so I'm not sure > it will change any time soon. Oh, I didn't realise this wasn't a person :O > Given the current general package sponsorship resources don't appear > to be increasing much year on year, I doubt it will ever be possible > for Debian to accept all proposed packages in a timely manner, sorry. I guess the obvious solution is for me to become a DD and sponsor uploads :P signature.asc Description: PGP signature
Re: Comment posted on sqldeveloper-package
Hi, Phil. It'll be a lot of work, but I have to change my email address, I've been having problems with BigFoot service, and only yesterday noticed it was failed. Probably it doesn't matter who's name appears on the page as long as the package gets sponsored which, from my experience, isn't that easy and the reason I gave up in 2012 of keeping uploading my newer versions. I develop all my packages in "testing", but I've tried to have them backward compatible, so I believe that all of them will work on previous releases counting from the time they were published. I've noticed the key issue and I believe you are right, it's the 1024 bit that might be issuing the warning, I'll look into it also. I didn't notice you had issued a package, just noticed the bug report, I haven't been using 0.2.4 since Nov 2012. The code base became quite different from 0.2.4 to 0.3.0, not sure how to add an out of order entry to changelog, if I put it in sequence with the version number the date is completely wrong, if I do it by date the version is out of order. In fact your package is more of a fork than an inline version. Since it's native, the changelog isn't just for the uploaded versions, it's for all the ones I've made, even those I haven't made public, like those prior to 0.2.3. Never used Alioth, just GitHub, and for a long time just my own machine. No issue was raised before about this, so I'm guessing it's not a requirement. I've revised your "stretch-pu" package and though the changelog isn't quite accurate (--no-tgz-check is used, not because sqldeveloper isn't free but, because this is a native package and doesn't need a ".orig" folder or archive), the patch to make-sqldeveloper-package is pristine, so I see no issue in it. Regards, -- Lazarus On Mon, Oct 30, 2017 at 9:55 AM, Phil Morrell wrote: > Hello Lazarus, pleased to meet you. > > I attempted to get in touch with you over the summer, but > unfortunately only got bounces from bigfoot.com. > > On 29 October 2017 at 22:57, mentors.debian.net > wrote: >> Lazarus Long made the following comment about the sqldeveloper-package >> package: >> >> Not sure what happened, but although I uploaded this package, it went under >> Phil's name. >> >> I'm guessing it's an interface bug, and not a problem. If I'm wrong please >> advise. > > I currently have an upload prepared for stretch-pu: > https://bugs.debian.org/879850 I'm also guessing from the URL > structure that there can be only one (first come, first served) > uploader on mentors.debian.net per package but since your version was > correctly signed, it was added to the existing page. If you like, I'm > happy to reverse that by deleting the package page and re-uploading > after you, just let me know. > > As for v0.4.2, thanks for fixing the outstanding bugs, I was only > interested in getting it working on stretch and unfortunately I'm not > at work today, so can't test the .deb. I did have to use dget > --allow-unauthenticated on your .dsc otherwise dscverify complained > about the signature, but gpg --verify did not. Hmm, dget-ing my own > upload had the same issue - do I need to explicitly specify the > keyring somehow, or is the 1024 bit key causing issues with gpg > modern? > > In the changelog, please include my nmu entry verbatim (as it has > reached unstable and instead of ack in 0.4.0), so bugs.debian.org > correctly shows the graph for #868673. I don't know if the deb9u1 > changelog entry also needs including, I've never done a stable update > before. I also thought the changelog should only contain versions > actually uploaded to unstable, rather than UNRELEASED ones, but that > might just be the behaviour of git-buildpackage. > > As the package is debian native, does the VCS need to point to alioth? > I know it's fine for there to be a mirror, accept contributions, or > for the upstream to be on a non-free service, but I thought all the > debian packaging needed to be DFSG hosted. > > Thanks, > -- > Phil Morrell (emorrp1)
Bug#862114: Bug#862115: RFS: xe/0.8-1 (ITP, #862114) & lr/0.4-1 (ITP, #862115)
On Mon, Oct 30, 2017 at 9:45 PM, Nicolas Braud-Santoni wrote: > This RFS is a pretty good example: there was no new upstream version, and > no review (or any sort of activity on the RFS) since June, while the timeout > on mentors.debian.net is only 20 days. The best you can do in that situation is bump the changelog date and reupload. > I appreciate that Bart was likely trying to triage RFSes, but closing it > rather than asking to reupload to mentors.d.n feels somewhat unfriendly, > especially when the packaging repo is available, and up-to-date, on alioth. That is a cron job that syncs the state of RFSes with the archive and mentors. The maintainer of the cron job is fairly MIA, so I'm not sure it will change any time soon. > Note that I'm not mentionning that to complain or vent, but to report a > problem that I'm encountering, as a non-DD contributor, in the hopes that > it might be possible to fix it rather than let it affect other people. Given the current general package sponsorship resources don't appear to be increasing much year on year, I doubt it will ever be possible for Debian to accept all proposed packages in a timely manner, sorry. -- bye, pabs https://wiki.debian.org/PaulWise
Bug#862114: Bug#862115: RFS: xe/0.8-1 (ITP, #862114) & lr/0.4-1 (ITP, #862115)
Hi pabs, On Sat, Oct 28, 2017 at 08:51:03PM +0800, Paul Wise wrote: > > Even if you haven't got a sponsor yet, RFS submitters should still be > maintaining the packages as they would if they were in the archive. > That means updating to new upstreams, fixing any review comments, > checking with new versions of lintian, running static analysis tools > and fixing issues etc. That's entirely fair. (And I've done that much, though I recently discovered my lintian setup was suboptimal, and didn't report some issues, which are since fixed.) > Those updates should prevent you from ever hitting the inactivity timeout > on mentors. This RFS is a pretty good example: there was no new upstream version, and no review (or any sort of activity on the RFS) since June, while the timeout on mentors.debian.net is only 20 days. I appreciate that Bart was likely trying to triage RFSes, but closing it rather than asking to reupload to mentors.d.n feels somewhat unfriendly, especially when the packaging repo is available, and up-to-date, on alioth. Note that I'm not mentionning that to complain or vent, but to report a problem that I'm encountering, as a non-DD contributor, in the hopes that it might be possible to fix it rather than let it affect other people. Best, nicoo signature.asc Description: PGP signature
Bug#880168: marked as done (RFS: libu2f-server/1.0.1-4 [RC])
Your message dated Mon, 30 Oct 2017 14:07:30 +0100 with message-id <20171030130730.7gpcv24xlkichoez@bogus> and subject line Re: RFS: libu2f-server/1.0.1-4 [RC] has caused the Debian Bug report #880168, regarding RFS: libu2f-server/1.0.1-4 [RC] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 880168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880168 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: important Control: blocks 876580 by -1 Control: tags 876580 fixed pending X-Debbugs-CC: si...@josefsson.org, pkg-auth-maintain...@lists.alioth.debian.org Dear mentors, I am looking for a sponsor for my package "libu2f-server" * Package name: libu2f-server Version : 1.0.1-4 * URL : https://developers.yubico.com/libu2f-server/ * License : Expat Section : utils This upload fixes a FTBFS bug (#876580), so please consider sponsoring it soon. The package can be found on mentors.d.n: https://mentors.debian.net/package/libu2f-server Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/libu/libu2f-server/libu2f-server_1.0.1-4.dsc The corresponding source has been pushed to the packaging repository on alioth. Best, nicoo signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Package uploaded by highvoltage. Thanks a lot <3 On Mon, Oct 30, 2017 at 10:24:50AM +0100, Nicolas Braud-Santoni wrote: > Package: sponsorship-requests > Severity: important > Control: blocks 876580 by -1 > Control: tags 876580 fixed pending > X-Debbugs-CC: si...@josefsson.org, > pkg-auth-maintain...@lists.alioth.debian.org > > Dear mentors, > > I am looking for a sponsor for my package "libu2f-server" > > * Package name: libu2f-server >Version : 1.0.1-4 > * URL : https://developers.yubico.com/libu2f-server/ > * License : Expat >Section : utils > > This upload fixes a FTBFS bug (#876580), > so please consider sponsoring it soon. > > > The package can be found on mentors.d.n: > > https://mentors.debian.net/package/libu2f-server > > Alternatively, one can download the package with dget using this command: > > dget -x > https://mentors.debian.net/debian/pool/main/libu/libu2f-server/libu2f-server_1.0.1-4.dsc > > > The corresponding source has been pushed to the packaging repository on > alioth. > > Best, > > nicoo signature.asc Description: PGP signature --- End Message ---
Bug#848327: RFS: libu2f-host/1.1.4-1 [RC]
Control: tags -1 + pending This has been uploaded to NEW by jcc@ Thanks <3 signature.asc Description: PGP signature
Bug#862115: Bug #862115: RFS: lr/0.4-1 [ITP] -- list files, recursively
Control: retitle -1 RFS: lr/1.1-1 [ITP] -- list files, recursively Upstream made a new release yesterday, so I updated the package. It is (again) on mentors.d.n and alioth. On Sat, Oct 28, 2017 at 12:17:00PM +0200, Nicolas Braud-Santoni wrote: > Control: retitle -1 Re: RFS: lr/1.0-1 [ITP] -- list files, recursively > > I updated the package to the latest upstream version > and uploaded it to alioth and mentors.d.n. > > On Sat, Oct 28, 2017 at 11:38:33AM +0200, Nicolas Braud-Santoni wrote: > > X-Debbugs-CC: ba...@quantz.debian.org > > > > Hi, > > > > I reopened those 2 RFSes, as Bart closed them over the > > packages not being on mentors.d.n anymore (due to a 20 > > days timeout). > > > > I will reupload them momentarily, but as mentionned > > in the previous emails they are available anyhow on > > > > https://nicolas.braud-santoni.eu/tmp/deb/ > > > > > > As an aside, I find it very weird to close a RFS due to > > the inactivity of would-be sponsors: from the packager's > > side, it feels like a double punishment (getting ignored, > > then getting your RFS closed because you got ignored)... > > > > > > Best, > > > > nicoo > > signature.asc Description: PGP signature
Re: Comment posted on sqldeveloper-package
Hello Lazarus, pleased to meet you. I attempted to get in touch with you over the summer, but unfortunately only got bounces from bigfoot.com. On 29 October 2017 at 22:57, mentors.debian.net wrote: > Lazarus Long made the following comment about the sqldeveloper-package > package: > > Not sure what happened, but although I uploaded this package, it went under > Phil's name. > > I'm guessing it's an interface bug, and not a problem. If I'm wrong please > advise. I currently have an upload prepared for stretch-pu: https://bugs.debian.org/879850 I'm also guessing from the URL structure that there can be only one (first come, first served) uploader on mentors.debian.net per package but since your version was correctly signed, it was added to the existing page. If you like, I'm happy to reverse that by deleting the package page and re-uploading after you, just let me know. As for v0.4.2, thanks for fixing the outstanding bugs, I was only interested in getting it working on stretch and unfortunately I'm not at work today, so can't test the .deb. I did have to use dget --allow-unauthenticated on your .dsc otherwise dscverify complained about the signature, but gpg --verify did not. Hmm, dget-ing my own upload had the same issue - do I need to explicitly specify the keyring somehow, or is the 1024 bit key causing issues with gpg modern? In the changelog, please include my nmu entry verbatim (as it has reached unstable and instead of ack in 0.4.0), so bugs.debian.org correctly shows the graph for #868673. I don't know if the deb9u1 changelog entry also needs including, I've never done a stable update before. I also thought the changelog should only contain versions actually uploaded to unstable, rather than UNRELEASED ones, but that might just be the behaviour of git-buildpackage. As the package is debian native, does the VCS need to point to alioth? I know it's fine for there to be a mirror, accept contributions, or for the upstream to be on a non-free service, but I thought all the debian packaging needed to be DFSG hosted. Thanks, -- Phil Morrell (emorrp1)
Bug#848327: RFS: libu2f-host/1.1.4-1 [RC]
X-Debbugs-CC: si...@josefsson.org, pkg-auth-maintain...@lists.alioth.debian.org Control: reopen -1 = Control: retitle -1 RFS: libu2f-host/1.1.4-1 [RC] Control: severity -1 important Control: block 846358 by -1 Control: tags 846358 fixed pending Control: block 846359 by -1 Control: tags 846359 fixed pending Control: block 824532 by -1 Control: tags 824532 fixed pending Control: block 876579 by -1 Control: tags 876579 fixed pending Hi, @Simon: you pushed a different package for the same version, this summer, that didn't include my fixes. I merged the work on alioth (now directly on branch `master`, to avoid a repeat of this confusion) and prepared a new upload that includes the new release (1.1.4) and a fix for #876579 (FTBFS). Please consider sponsoring this upload, as it closes a number of bugs, including a FTBFS. Best, nicoo signature.asc Description: PGP signature
Bug#880168: RFS: libu2f-server/1.0.1-4 [RC]
Package: sponsorship-requests Severity: important Control: blocks 876580 by -1 Control: tags 876580 fixed pending X-Debbugs-CC: si...@josefsson.org, pkg-auth-maintain...@lists.alioth.debian.org Dear mentors, I am looking for a sponsor for my package "libu2f-server" * Package name: libu2f-server Version : 1.0.1-4 * URL : https://developers.yubico.com/libu2f-server/ * License : Expat Section : utils This upload fixes a FTBFS bug (#876580), so please consider sponsoring it soon. The package can be found on mentors.d.n: https://mentors.debian.net/package/libu2f-server Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/libu/libu2f-server/libu2f-server_1.0.1-4.dsc The corresponding source has been pushed to the packaging repository on alioth. Best, nicoo signature.asc Description: PGP signature
Bug#879720: RFS: runescape/0.2-1 [QA] -- Multiplayer online game set in a fantasy world
On Sun, Oct 29, 2017 at 10:24:29PM -0200, Carlos Donizete Froes wrote: > Em dom, 2017-10-29 às 15:30 +0100, Tobias Frost escreveu: > > Good! > > > > Sorry for bringing up another issue, but I completly missed that > > before: The Debian changelog's purpose is not to document changes made > > to upstream code but only to document changes made to the Debian > > package. (It is in Debian Policy 4.4) > > > > So in your case those lines should not be d/changelog: > > > > * Changed icon format and fixed bug in desktop file (Closes: > > Bug#866227) > > * Replaced command line to create temporary directory (Closes: > > Bug#879784) > > > > Instead of those two lines you would write: > > * New upstream release. (Closes: #866227, #879784) > > > > Please fix this and I'll upload. > > Done changes as requested. Uploaded! Many thanks for your contributions to Debian! tobi > Thanks! > > -- > ⢀⣴⠾⠻⢶⣦⠀ Carlos Donizete Froes [a.k.a coringao] > ⣾⠁⢠⠒⠀⣿⡁ - https://wiki.debian.org/coringao > ⢿⡄⠘⠷⠚⠋⠀ GPG: 4096R/B638B780 > ⠈⠳⣄⠀⠀⠀ 2157 630B D441 A775 BEFF D35F FA63 ADA6 B638 B780
