Bug#935485: RFS: kcollectd/0.10-1 ITA -- simple collectd graphing front-end for KDE
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for the very recently removed kcollectd package. It was removed because it required Qt4. I ported this to Qt5 several months ago, and mentioned this in the bug report [1]. I suppose that original bug report should have been accompanied by an ITA WNPP bug. I've also fixed some longstanding bugs [2]. The new upstream (which I maintain) is only a few extra commits on top of the old release, and is available at gitlab [3]. The Debian packaging is on salsa [4], and the source packages have been uploaded to mentors [5] [6]. Thank you, Antonio Russo [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927455 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814935 [3] https://gitlab.com/aerusso/kcollectd [4] https://salsa.debian.org/aerusso-guest/kcollectd [5] https://mentors.debian.net/package/kcollectd [6] dget -x https://mentors.debian.net/debian/pool/main/k/kcollectd/kcollectd_0.10.0-1.dsc
Bug#935390: RFS: vnstat/2.4-1 [NMU] [ITA]
Hi Sven, Teemu (vnstat dev) was kind enough to write me a lengthy and helpful commentary today on the situation relative vnstat. He pointed out various inconsistencies in the way I have presented the package (and also confusion from me sending two initial two emails, Teemu mentioned that policy says a new RFS should only come after the 21 days -- my apologies for being too quick on that without clear grasp of all the Debian policies). So I have removed the package from mentors and will work on gaining a fuller understanding of the correct way to package vnstat for Debian over the coming weeks. With the quite detailed analysis given me by Teemu, relative patches, possible closing of bugs (if a version v2.x moves into the Debian repositories) and tips about correct ways to make the package, there is much for me to learn! In any case, thank you again for your response and attention to my (unintended) slightly incorrect approach relative the intention of getting a newer vnstat into Debian repos. -Rob On 08/22/2019 03:10 AM, Rob Savoury wrote: > Hi Sven, > > Thanks for the reply. Spent the whole day (and evening!) doing my best > to go through all the necessary steps to learn how to create a reliable > first Debian package, but guess I'm not totally surprised it is not > quite correct somehow! > > In any case, along with the RFS another email sent was an "ITS: vnstat" > [1] due this package qualifying for salvaging. So my intent is actually > to move towards being maintainer of vnstat (starting out with sponsored > maintainership, of course). That was actually Teemu (the developer's) > suggestive prompt to me in an email yesterday (after I alerted him to a > minor cosmetic bug in vnstat and he alerted me to the situation of the > vnstat package in Debian apparently having a "MIA" maintainer). > > The very problem appears to be a one year lack of any sign of activity > from Christian relative this package, so that's why the ITS and RFS from > me today. My understanding is that a three week window is given for the > maintainer to respond to an ITS so we will see if Christian returns into > some communication about vnstat during that time. Until then, I'll keep > brushing up on my new learning with the whole complexity of the Debian > packaging process! > > Thanks, > Rob > > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935391 > > > On 08/22/2019 02:45 AM, Sven Hoexter wrote: >> On Thu, Aug 22, 2019 at 01:26:35AM -0700, Rob Savoury wrote: >> >> Hey Rob, >> >>> Changes since the last upload: >>> >>>* New upstream version 2.4 >>> . >>>* debian/patches/ >>>+ drop patch applied upstream (timeout for restart) >>>+ modify pidfile and systemd patches for new source files >>>* d/control: bump to std version 4.4.0 and add libsqlite3-dev BD (vnstat >>> 2.x) >> >> While I value the work, this is not properly packaged as an NMU. >> I uploaded the last NMU by Teemu because it made perfectly sense to upload >> those changes which were already implemented by Christian Göttsche. But >> Christian >> is still the maintainer of the package as far as I can tell. >> >> So would be nice to have an ACK from him if such kind of informal team >> uploads >> are ok. And beside of that NMUs which implement major version changes are >> mostly >> an exception. I would prefer either some team upload or some notice by >> Christian >> how he intents to handle this package. >> >> Sven >> >>
Bug#934053: RFS: fwlogwatch/1.4-2
On Tue, Aug 06, 2019 at 10:12:08AM -0300, William Grzybowski wrote: > Package: sponsorship-requests > Severity: normal > > fwlogwatch (1.4-2) unstable; urgency=medium Hi William, Thank you for helping with fwlogwatch. I've taken a look at your updated package and things look really good. I noticed a couple minor issues in the manpage I wanted to suggest you address before we upload. - The configuration file is found in /etc/fwlogwatch/fwlogwatch.config, not in /etc/fwlogwatch.config. - The pid file is now in /run/fwlogwatch.pid, not /var/run/fwlogwatch.pid Cheers, tony signature.asc Description: PGP signature
Bug#935462: RFS: xca/2.1.2-1 [ITS] -- x509 Certification Authority management tool based on QT
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "xca"
* Package name : xca
Version : 2.1.2-1
Upstream Author : Christian Hohnstaedt
* URL : https://hohnstaedt.de/xca/
* License : BSD-3-clause
* Vcs : https://salsa.debian.org/debian/xca
Section : x11
It builds those binary packages:
xca - x509 Certification Authority management tool based on QT
To access further information about this package, please visit the
following URL:
https://mentors.debian.net/package/xca
Alternatively, one can download the package with dget using this command:
dget -x https://mentors.debian.net/debian/pool/main/x/xca/xca_2.1.2-1.dsc
Changes since the last upload:
* New upstream version. (Closes: #927233)
* d/watch: Update watch file to track upstream xca repository on Github.
* d/compat: Update Debhelper compatibility to latest (12)
* d/control:
- New maintainer (Closes #931806)
- Update Standards-Version to 4.4.0
- Update Homepage to proper Upstream URL
- Update Vcs-Git to point at Debian Salsa. Package now uses a
git-buildpackage (gbp) workflow.
- Add Vcs-Browser field.
- Reorganize Build-Depends to be more readable.
- Remove dh-autoreconf build depends.
- Update debhelper build depends (compat is 12, so use debhelper >= 12)
- Make requisite changes to adjust xca built by the packages to enable
Remote DB support in xca: (Closes: #928678)
- Add libqt5sql5 Build-Depends for Remote DB support.
- Add Recommends on libqt5sql5-{mysql,postgresql} to xca package.
* d/patches/0001-Remove-misc-Info.plist-in-clean-target.patch: Refresh
patch to remove fuzz.
* d/copyright: Update copyright file to be Machine-readable per
https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Regards,
Thomas
Bug#935390: RFS: vnstat/2.4-1 [NMU] [ITA]
Hi Sven, Thanks for the reply. Spent the whole day (and evening!) doing my best to go through all the necessary steps to learn how to create a reliable first Debian package, but guess I'm not totally surprised it is not quite correct somehow! In any case, along with the RFS another email sent was an "ITS: vnstat" [1] due this package qualifying for salvaging. So my intent is actually to move towards being maintainer of vnstat (starting out with sponsored maintainership, of course). That was actually Teemu (the developer's) suggestive prompt to me in an email yesterday (after I alerted him to a minor cosmetic bug in vnstat and he alerted me to the situation of the vnstat package in Debian apparently having a "MIA" maintainer). The very problem appears to be a one year lack of any sign of activity from Christian relative this package, so that's why the ITS and RFS from me today. My understanding is that a three week window is given for the maintainer to respond to an ITS so we will see if Christian returns into some communication about vnstat during that time. Until then, I'll keep brushing up on my new learning with the whole complexity of the Debian packaging process! Thanks, Rob [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935391 On 08/22/2019 02:45 AM, Sven Hoexter wrote: > On Thu, Aug 22, 2019 at 01:26:35AM -0700, Rob Savoury wrote: > > Hey Rob, > >> Changes since the last upload: >> >>* New upstream version 2.4 >> . >>* debian/patches/ >>+ drop patch applied upstream (timeout for restart) >>+ modify pidfile and systemd patches for new source files >>* d/control: bump to std version 4.4.0 and add libsqlite3-dev BD (vnstat >> 2.x) > > While I value the work, this is not properly packaged as an NMU. > I uploaded the last NMU by Teemu because it made perfectly sense to upload > those changes which were already implemented by Christian Göttsche. But > Christian > is still the maintainer of the package as far as I can tell. > > So would be nice to have an ACK from him if such kind of informal team uploads > are ok. And beside of that NMUs which implement major version changes are > mostly > an exception. I would prefer either some team upload or some notice by > Christian > how he intents to handle this package. > > Sven > >
Bug#935390: RFS: vnstat/2.4-1 [NMU] [ITA]
On Thu, Aug 22, 2019 at 01:26:35AM -0700, Rob Savoury wrote: Hey Rob, > Changes since the last upload: > >* New upstream version 2.4 > . >* debian/patches/ >+ drop patch applied upstream (timeout for restart) >+ modify pidfile and systemd patches for new source files >* d/control: bump to std version 4.4.0 and add libsqlite3-dev BD (vnstat > 2.x) While I value the work, this is not properly packaged as an NMU. I uploaded the last NMU by Teemu because it made perfectly sense to upload those changes which were already implemented by Christian Göttsche. But Christian is still the maintainer of the package as far as I can tell. So would be nice to have an ACK from him if such kind of informal team uploads are ok. And beside of that NMUs which implement major version changes are mostly an exception. I would prefer either some team upload or some notice by Christian how he intents to handle this package. Sven
Bug#935390: RFS: vnstat/2.4-1 [NMU] [ITA]
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "vnstat" * Package name: vnstat Version : 2.4-1 Upstream Author : Teemu Toivola * URL : https://humdi.net/vnstat/ * License : GPL-2 * Vcs : https://salsa.debian.org/cgzones-guest/vnstat Section : net It builds those binary packages: vnstat - console-based network traffic monitor vnstati - image output support for vnStat To access further information about this package, please visit the following URL: https://mentors.debian.net/package/vnstat Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/v/vnstat/vnstat_2.4-1.dsc Changes since the last upload: * New upstream version 2.4 . * debian/patches/ + drop patch applied upstream (timeout for restart) + modify pidfile and systemd patches for new source files * d/control: bump to std version 4.4.0 and add libsqlite3-dev BD (vnstat 2.x) Regards, Rob Savoury
Re: Bug#927455 closed by Debian FTP Masters (Bug#935223: Removed package(s) from unstable)
"Paul Wise" – August 21, 2019 8:50 PM > On Thu, Aug 22, 2019 at 11:45 AM Antonio Russo wrote: > > > How exactly can I find a sponsor to help me maintain an orphaned Debian > package? > > Upload the new package to mentors and file a request for sponsor: > > mentors.debian.net/intro-maintainers > mentors.debian.net/sponsors/rfs-howto > > > Bug#935223: Removed package(s) from unstable > > Please note the extra steps required when reintroducing packages: > > www.debian.org/doc/manuals/developers-reference/ch05.html > > -- > bye, > pabs > > wiki.debian.org/PaulWise
