Bug#926715: marked as done (RFS: ddupdate/0.6.2-1 -- Tool updating DNS data for dynamic IP addresses)
Your message dated Sat, 13 Apr 2019 23:54:02 +0200 with message-id <20190413215402.gc3...@angband.pl> and subject line Re: Bug#926715: RFS: ddupdate/0.6.2-1 has caused the Debian Bug report #926715, regarding RFS: ddupdate/0.6.2-1 -- Tool updating DNS data for dynamic IP addresses 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.) -- 926715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926715 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "ddupdate" * Package name: ddupdate Version : 0.6.2-1 Upstream Author : Alec Leamas * URL : https://github.com/leamas/ddupdate * License : Expat Section : net It builds those binary packages: ddupdate - Tool updating DNS data for dynamic IP addresses For more information on this package see https://mentors.debian.net/package/ddupdate Alternatively, one can download the package with dget using: dget -x https://mentors.debian.net/debian/pool/main/d/ddupdate/ddupdate_0.6.2-1.dsc More information about ddupdate: https://github.com/leamas/ddupdate Changes since the last upload: * New upstream release. Regards, -- Alec Leamas --- End Message --- --- Begin Message --- On Tue, Apr 09, 2019 at 04:53:16PM +0200, Alec Leamas wrote: > * Package name: ddupdate >Version : 0.6.2-1 > Changes since the last upload: > > * New upstream release. The auto-update functionality is for some reason systemd only, despite not actually using any systemd features. This makes it broken on any other init/rc system for no gain. Could you please convert the .service/.timer to a init script and/or cron job? It's no regression from the previous version, though -- and small incremental updates are so much easier to review, thus I uploaded as-is. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Did ya know that typing "test -j8" instead of "ctest -j8" ⢿⡄⠘⠷⠚⠋⠀ will make your testsuite pass much faster, and fix bugs? ⠈⠳⣄--- End Message ---
Bug#926915: RFS: fossology/3.5.0-1 [ITP] -- OSS license compliance tool
On Fri, Apr 12, 2019 at 06:59:12AM +, Mishra, Gaurav wrote: > Package name: fossology > Version : 3.5.0-1 Alas, it fails to build: it build-depends on php5-cli which is gone for two releases already (was in jessie, your package can get to bullseye at the soonest). [I won't likely be reviewing this package any further, though -- web stuff is not my strength.] Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Did ya know that typing "test -j8" instead of "ctest -j8" ⢿⡄⠘⠷⠚⠋⠀ will make your testsuite pass much faster, and fix bugs? ⠈⠳⣄
Re: no response Fwd: Bug#905080: O: as31 - Intel 8031/8051 assembler
Please send this to the debian-mentors list instead of exclusively to me. I did not mean to imply that I personally would be offering mentorship or sponsorship, and in any case, my abilities are limited since I am not a DD. On 2019-04-11, Albert van der Horst wrote: > Jason Crain schreef op 2019-04-09 19:35: > > On Tue, Apr 09, 2019 at 07:05:29PM +0200, Albert van der Horst wrote: > > > I followed up on a "orphaned bug" by adding a message to the bug > > > 905080. > > > This got never a response. Did I make a mistake with respect to the > > > Debian protocols? > > > I seem to remember that I got a confirmation that in "due course" a > > > Debianist would > > > respond. > > > And no, the 8051 is not dead by a long stretch. So deleting from the > > > Debian distribution is not good. > > > > If you are intending to adopt the package, you should rename the O > > (Orphaned) bug to ITA (Intent To Adopt) and create an updated package > > fixing some of the issues and naming yourself as maintainer. Then, if > > you need a sponsor, upload the package to mentors.debian.net and create > > a RFS (Request For Sponsorship) bug to request that a Debian Developer > > review and upload the package for you. > > If there were issues, I would solve all of them. before uploading a package. > There are no technical issues, that I would tackle gladly, > only a very nasty formalistic one. > "Although it is known that it is licensed under BSD, there is only an > assumption that it is "3-clause" BSD." > I see that the maintainer commented on the issue, but did not classify > it. I think that the first thing to do for an issue is to classify it. > Now I've no idea how important it is to solve this issue. In addition to the license issue, I see a few minor things listed on the tracker page https://tracker.debian.org/pkg/as31, including a warning that the VCS repository is out of date, a lintian warning about a deprecated debhelper version, a build log warning about hardening flags, and a note that the standards version is out of date. I don't know how easy some of those will be to fix, but you should try to fix the ones that you can. The license is probably not that big of an issue, since I think any version of the BSD license would be free, but you could try to contact upstream to see if they will clarify the license. > I've just been through the painful process of getting a package in a > formally acceptable state, just to find out that there is no one willing > to sponsor. Can you or anyone give an idea of the chance this would happen > again? > I've no connections to speak of in the Debian community. > The orphaner got my message but didn't warn a newbee that renaming of the > bug > was necessary to get things rolling. Is that a bad sign or > is there a chance that the orphaner would for a limited time be willing to > sponsor? Yes, you can ask the orphaner if he is willing to sponsor your package, but he may decline or not respond for many reasons, including lack of available time. If he won't, you should file a sponsorship bug as described at https://mentors.debian.net/sponsors. Though note that since Debian is in a freeze, your package will probably not be uploaded to unstable until Debian Buster is released, possibly several months from now. I'm sorry that you were not able to find a sponsor for your previous package. I haven't had too much trouble finding sponsors before, so my only advice is to try again. > If I'd rid the package of some technical defect and it wouldn't be accepted, > that would not > mean a great deal to me, because the effort is not really wasted, as long as > I publish it somewhere. However if after a long e-mail exchange I finally > managed to fix a copyright message and it would not be accepted I > would be really depressed. Same if the only change was to list myself as > as maintainer. > > > Groetjes Albert > > -- > Suffering is the prerogative of the strong, the weak -- perish. > Albert van der Horst
Song Submission - "Lonely"
I wanted to submit my song "Lonely". The response I've gotten thus far has been so absolutely humbling. I can't even believe it. I've heard from several people who were ready to take their lives that somehow, this song came on, and gave them strength to keep moving forward. Absolutely blows my mind. Makes me feel like there's something larger at work. Also, me and my brother have a combined 110K instagram followers so we'll be able to send traffic your way. It be mutually beneficial. If not, I'll still continue to support you and your channel. Keep doing what you're doing. Be blessed, Nathan Wagner Youtube link: https://www.youtube.com/watch?v=5vzMmfQlBH4 Lonely Spotify: https://open.spotify.com/track/2V7JEBp1E45zWFvCIkUzp9?si=HSakzkP2ROav7UwRuOUgWQ Apple Music: https://itunes.apple.com/us/album/lonely-single/1447700192 Soundcloud (Downloadable): https://soundcloud.com/nathan-wagner/lonely Instagram: https://www.instagram.com/nathanwagner762/?hl=en
Bug#926306: RFS: socklog/2.1.0-9
On Fri, Apr 12, 2019 at 05:22:35PM +, Dmitry Bogatov wrote:
> [2019-04-10 23:48] Mathieu Mirmont
> >
> > part 1 text/plain 434
> > On Wed, Apr 10, 2019 at 08:20:30AM +, Dmitry Bogatov wrote:
> > > You can repack it as new upstream version. New version would be
> > > something like `2.1.0+repack-1'. Do not forget add clarification into
> > > Debian.source.
> >
> > I've updated the package and uploaded to mentors:
> >
> > https://mentors.debian.net/package/socklog
> > https://mentors.debian.net/debian/pool/main/s/socklog/socklog_2.1.0+repack-1.dsc
>
> Lintian (2.11.0) warnings:
>
> W: socklog: missing-versioned-depends-on-init-system-helpers
> postinst:152 "update-rc.d defaults-disabled" needs i
> nit-system-helpers >= 1.50
> W: socklog: missing-versioned-depends-on-init-system-helpers
> postinst:165 "update-rc.d defaults-disabled" needs i
> nit-system-helpers >= 1.50
> W: socklog: missing-versioned-depends-on-init-system-helpers
> postinst:178 "update-rc.d defaults-disabled" needs i
> nit-system-helpers >= 1.50
Embarassingly I don't know how to get rid of this one. I've added a
depencency on init-system-helpers (>= 1.50) naturally but the warning
remains.
Since ${misc:Pre-Depends} already includes init-system-helpers (>=
1.54~) I added lintian overrides. It's a bit dirty though, and the
line number makes it a moving target. I'll fix the line numbers in the
lintian overrides but if you know how to fix this in a better way I'm
all ears.
> Oh, and extremely minor notice: in `debian/control' you align fields
> with tabs. It does not look pretty, if tabstop is not 8. What about
> expand(1)?
Ah yeah sorry, I'll untabify this.
--
Mathieu Mirmont
signature.asc
Description: PGP signature
