Bug#883750: RFS: dde-calendar/1.1.1-1 [ITP]
Package: sponsorship-requests Severity: wishlist X-Debbugs-CC: pkg-deepin-de...@lists.alioth.debian.org Dear mentors, I am looking for a sponsor for my package "dde-calendar" * Package name: dde-calendar Version : 1.1.1-1 Upstream Author : Deepin Technology Co., Ltd. * URL : https://github.com/linuxdeepin/dde-calendar * License : GPL-3+ Section : utils It builds those binary packages: dde-calendar - Deepin calendar To access further information about this package, please visit the following URL: https://mentors.debian.net/package/dde-calendar Git repo: https://anonscm.debian.org/git/pkg-deepin/dde-calendar.git Regards, Yangfl
Bug#883662: marked as done (RFS: agenda.app/0.44-1)
Your message dated Thu, 7 Dec 2017 08:13:59 +0100 with message-id <20171207071359.cdt4w7q7nzsba...@angband.pl> and subject line Re: Bug#883662: RFS: agenda.app/0.44-1 has caused the Debian Bug report #883662, regarding RFS: agenda.app/0.44-1 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.) -- 883662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883662 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 "agenda.app". * Package name: agenda.app Version : 0.44-1 Upstream Author : Philippe Roussel* URL : https://github.com/poroussel/simpleagenda * License : GPL-2+ Section : gnustep It builds this binary package: agenda.app - Calendar manager for GNUstep To access further information about this package, please visit the following URL: https://mentors.debian.net/package/agenda.app Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/a/agenda.app/agenda.app_0.44-1.dsc Or clone the Git repository: git clone https://anonscm.debian.org/git/pkg-gnustep/agenda.app.git Changes since the last upload: * New upstream release. * debian/compat: Set to 10. * debian/control (Build-Depends): Require debhelper >= 10 and gnustep-make >= 2.7.0-3 for recent config.mk. Add libdbuskit-dev for desktop notifications; drop dpkg-dev (obsolete) and imagemagick (not needed anymore as support for Debian menu is removed). (Depends): Remove ${gnustep:Depends}; obsolete. (Homepage): Replace with the new one at GitHub. (Vcs-Git, Vcs-Browser): Use canonical/secure URIs. (Standards-Version): Compliant with 4.1.2 as of this release. * debian/rules: Update for modern dh. * debian/install: * debian/docs: * debian/manpages: New files. * debian/menu: Delete. * debian/watch: Upgrade to version 4; use new upstream location. * debian/SimpleAgenda.desktop: Add Keywords field. * debian/patches/spelling-fix.patch: New, fix trivial spelling error. * debian/patches/series: New file. * debian/copyright: Switch to format 1.0; update Source field and copyright years. P.S. The package doesn't pass the piuparts test due to #832349. --- End Message --- --- Begin Message --- On Wed, Dec 06, 2017 at 11:53:02AM +0200, Yavor Doganov wrote: > * Package name: agenda.app >Version : 0.44-1 > Changes since the last upload: > > * New upstream release. > * debian/compat: Set to 10. > * debian/control (Build-Depends): Require debhelper >= 10 and > gnustep-make >= 2.7.0-3 for recent config.mk. Add libdbuskit-dev for > desktop notifications; drop dpkg-dev (obsolete) and imagemagick (not > needed anymore as support for Debian menu is removed). > (Depends): Remove ${gnustep:Depends}; obsolete. > (Homepage): Replace with the new one at GitHub. > (Vcs-Git, Vcs-Browser): Use canonical/secure URIs. > (Standards-Version): Compliant with 4.1.2 as of this release. > * debian/rules: Update for modern dh. > * debian/install: > * debian/docs: > * debian/manpages: New files. > * debian/menu: Delete. > * debian/watch: Upgrade to version 4; use new upstream location. > * debian/SimpleAgenda.desktop: Add Keywords field. > * debian/patches/spelling-fix.patch: New, fix trivial spelling error. > * debian/patches/series: New file. > * debian/copyright: Switch to format 1.0; update Source field and > copyright years. ✓ > P.S. The package doesn't pass the piuparts test due to #832349. Let's see if this will be a blocker. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ 14:13 < icenowy[m]> are they hot enough? ;-) ⣾⠁⢰⠒⠀⣿⡁ 14:17 < icenowy[m]> I think now in Europe it should be winter? Let ⢿⡄⠘⠷⠚⠋⠀ the BPi warm you ;-) ⠈⠳⣄ 14:17 <@KotCzarny> yeah, i have a pc to warm me ;)--- End Message ---
Re: Bug#880590: RFS: webmin/1.860-1 [ITP]
On Wed, Dec 06, 2017 at 07:01:04AM +, Chris Knadle wrote: > In order to make a new upload to Mentors, it's necessary to first log > into the Mentors website, visit the page for the uploaded package, and > *delete* it Why do you think so? -- WBR, wRAR signature.asc Description: PGP signature
Bug#883726: RFS: budgie-extras/0.3.0-1 [ITP]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "budgie-extras" * Package name: budgie-extras Version : 0.3.0-1 Upstream Author : Ubuntu Budgie Developers * URL : https://github.com/ubuntubudgie/budgie-extras * License : GPL-3+ Section : misc It builds those binary packages: budgie-countdown-applet - Applet providing a countdown capability on the Budgie Desktop budgie-hotcorners-applet - Applet providing hotcorners capabilities for the Budgie Desktop budgie-keyboard-autoswitch-applet - Applet adding the ability to set a different keyboard layout per budgie-previews-applet - Applet providing window previews capabilities for the Budgie Desk budgie-quicknote-applet - Applet providing simple notes capability for the Budgie Desktop budgie-showtime-applet - Applet displaying date and time on the Budgie Desktop budgie-window-mover-applet - Applet allows moving windows between workspaces for the Budgie De budgie-workspace-overview-applet - Applet providing quick access to workspaces for the Budgie Deskto budgie-workspace-wallpaper-applet - Applet providing per workspace wallpaper To access further information about this package, please visit the following URL: https://mentors.debian.net/package/budgie-extras Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/b/budgie-extras/budgie-extras_0.3.0-1.dsc Notes: Budgie Desktop is the flagship desktop system for Solus. Budgie Desktop can be extended through applets - LibPeas based applications that provide extra capabilities not available through the core product. For this sponsorship request, myself as the project lead of the GNU/Linux distro Ubuntu Budgie have been working with my team to develop a series of additional Budgie Desktop applets that we believe give the end user additional optional capabilities to enhance their user experience. These applets are distro agnostic and we believe would benefit Debian users of the Budgie Desktop. Viability: The Ubuntu Budgie team have a direct interest in developing and maintaining these applets. These are already available to Ubuntu Budgie users via its backports PPA. Maintainership: I maintain all budgie related packages for both Debian and Ubuntu. Packaging: We have made each applet available as individual binary packages - this allows users the flexibility to choose specific applets rather than having to install everything. For this release (and moving forward) I have signed with my 4K based key. The package was verfied through a `uscan -v --force-download` and unpacked & built & uploaded to mentors check-all-the-things has been run on the source and where appropriate we have tidied up both the source and debian packaging. lintian -i -I --pedantic on the built changes file has been run and is lintian free. We include a pep8 based autopkgtest that has been tested on an schroot for both unstable and also Ubuntu's bionic series. The test has passed successfully. The package itself runs with an autotest - the same pep8 test for autopkgtests (see tools/run_pep8) Testing: The minimal XFCE based Debian Buster was upgraded to unstable and budgie-desktop was installed. The package was built and each individual binary package was installed and tested to confirm that they work correctly - this importantly caught all the necessary runtime dependencies that have been captured in debian/control Changes since the last upload: * Initial Release (Closes: #883720) Regards, David Mohammed
Bug#883611:
Hi Juhani, Thanks for your feedback in your previous comment. I have now updated the package with the requested changes. I understand that you may not be able to sponsor this package however I would appreciate any additional advise you can offer. https://mentors.debian.net/package/auter dget -x https://mentors.debian.net/debian/pool/main/a/auter/auter_0.11-1.dsc Thanks Paolo
Bug#883702: RFS: lina/5.3.0-1 ( #859130 ITP: lina -- iso-compliant Forth interpreter and compiler )
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "lina" * Package name: lina Version : 5.3.0-1 Upstream Author : Albert van der Horst* URL : https://github.com/albertvanderhorst/ciforth * License : LGPL2 Section : devel It builds those binary packages: lina - close to ISO Forth interpreter and compiler To access further information about this package, please visit the following URL: https://mentors.debian.net/package/lina Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/l/lina/lina_5.3.0-1.dsc Changes since the last upload: * Initial release (Closes: #859130) * Added a Makefile * Administrative defects detected by lintian The relevance of this Forth in regard of the availability of other Forth's in Debian : * the connection with Forth's on microcontrollers, in partical http://home.hccnet.nl/willem.ouwerkerk/pr-bytef.htm (8051 AVR) http://home.hccnet.nl/anij/nof/noforth.html (MSP430) Tools in behalf of these (ide's, metacompiler, calibration programs) can then be built using a trusted compiler. * building real time control, portable accross Linux and MS-Windows's e.g. (requires a true parallel port:) http://home.hccnet.nl/a.w.m.van.der.horst/manx.html * ease of making elf executables and simplicity in general e.g. https://github.com/albertvanderhorst/primecounting/tree/master/sieve http://home.hccnet.nl/a.w.m.van.der.horst/ciasdis_1.0_all.deb Sponsoring efforts should be low, in view of one assembler source and basically a one line build. Regards, Albert van der Horst -- Suffering is the prerogative of the strong, the weak -- perish. Albert van der Horst
Bug#883611:
Hi Paul, Thanks for following up on this. To address your points: 1) The point raised in the ITP about stopping critical applications cleanly is an example scenario. The idea being that you have the ability to run any custom script at each of those phases. Other examples may include: - Backing up config files before applying updates - making an API call to a monitoring system to put the server in maintenance mode - adjust a status file which is used to keep the server in a loadbalance pool - possibly creating lvm snapshots before applying updates - capture current system statistics and states metrics which can then be compared post updates ie: listening ports before updates are applied and after the patching process has completed (Including post-reboot) The possibilities with these pre and post scripts are endless and have the potential to be extremely useful especially with tasks that you may not want or need to write a specific custom systemd file or init script. In addition tho this, the script hooks are not only for the reboot phase but also for the download and apply phases. 2) While it is possible to separate the download and install schedules in unattended-upgrades, it becomes a bit more of a task to work around an automatic version controlled setup. For example, you want a test environment to install updates in the first week of the month but the production environment should only be updated in the third week. With unattended upgrades, the latest packages will be downloaded and installed which may not have been the packages that were tested. With auter, you can set all environments to download patches at the same time and only install those specific downloaded packages at the required schedule. 3) While unattended-upgrades can also schedule automatic reboots, the huge advantage here is being able to run pre and post reboot scripts which are specific to the patching process as discussed in point 1 4) The separate patching profiles is one of the specific request we had when building this tool. 5) I am sure there are many use cases where system administrators are maintaining environments with multiple Linux distributions and having a tool which can be configured in the same way regardless of distribution is a huge advantage. Thanks Paolo On Wed, Dec 6, 2017 at 11:51 AM, Paul Wisewrote: > On Wed, Dec 6, 2017 at 6:12 PM, Paolo Gigante wrote: > > > As per the ITP (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880600 > ) > > there is a lot of additional functionality that auter provides which goes > > way beyond what is offered by cron-apt and unattended-upgrades: > > A comment on the ITP features: > > > This allows servers to be configured to stop any critical > > applications cleanly using custom scripts before any actions are taken. > > Critical applications should be cleanly integrated with the system so > that normal shutdown/reboot does the right thing. > > > - Auter has the functionality to separate download schedules from install > > schedules which is great for organisations wanting to version control > > updates across multiple servers and environments while staggering the > update > > process for the servers. > > This is also supported by unattended-upgrades under systemd. > > > - It also allows for customised scripts to be executed pre and post > > downloading updates, applying updates and rebooting the server > > This is also supported by apt, except reboot hooks but those should > probably be integrated into the init system instead. > > > - It has the option to automate reboots after the patching process has > been > > applied > > This is also supported by unattended-upgrades, including a set reboot time. > > > - There is an option of setting up multiple patching profiles eg: weekly > > application patches and monthly system/kernel patching (This is entirely > > customiseable) > > In theory this could be possible with unattended-upgrades but I think > it would be hard to setup. > > > - In cases where admins have multiple servers with different rehdat or > > debian based distributions, the same application and configuration files > can > > be deployed to servers regardless of the distribution. > > That seems like a plus for those stuck in that situation indeed. > > -- > bye, > pabs > > https://wiki.debian.org/PaulWise >
Bug#883611:
On Wed, Dec 6, 2017 at 6:12 PM, Paolo Gigante wrote: > As per the ITP (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880600) > there is a lot of additional functionality that auter provides which goes > way beyond what is offered by cron-apt and unattended-upgrades: A comment on the ITP features: > This allows servers to be configured to stop any critical > applications cleanly using custom scripts before any actions are taken. Critical applications should be cleanly integrated with the system so that normal shutdown/reboot does the right thing. > - Auter has the functionality to separate download schedules from install > schedules which is great for organisations wanting to version control > updates across multiple servers and environments while staggering the update > process for the servers. This is also supported by unattended-upgrades under systemd. > - It also allows for customised scripts to be executed pre and post > downloading updates, applying updates and rebooting the server This is also supported by apt, except reboot hooks but those should probably be integrated into the init system instead. > - It has the option to automate reboots after the patching process has been > applied This is also supported by unattended-upgrades, including a set reboot time. > - There is an option of setting up multiple patching profiles eg: weekly > application patches and monthly system/kernel patching (This is entirely > customiseable) In theory this could be possible with unattended-upgrades but I think it would be hard to setup. > - In cases where admins have multiple servers with different rehdat or > debian based distributions, the same application and configuration files can > be deployed to servers regardless of the distribution. That seems like a plus for those stuck in that situation indeed. -- bye, pabs https://wiki.debian.org/PaulWise
Bug#883611:
Hi Juhani, Thanks for the advise, I will start to work on that now but I am also trying to ensure that the same package will build for ubuntu based systems which is why I used compat 9 however I will try add an appropriate check in the Makefile for that. Hi Bart, I am not entirely sure about the correct process for creating a new package as the docs recommend creating an ITP so I raised that last month. With no response to that I raised a separate bug seeking sponsorship. I am not sure if both are a requirement. Hi Pabs, As per the ITP (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880600) there is a lot of additional functionality that auter provides which goes way beyond what is offered by cron-apt and unattended-upgrades: - Auter has the functionality to separate download schedules from install schedules which is great for organisations wanting to version control updates across multiple servers and environments while staggering the update process for the servers. - It also allows for customised scripts to be executed pre and post downloading updates, applying updates and rebooting the server - It has the option to automate reboots after the patching process has been applied - There is an option of setting up multiple patching profiles eg: weekly application patches and monthly system/kernel patching (This is entirely customiseable) - In cases where admins have multiple servers with different rehdat or debian based distributions, the same application and configuration files can be deployed to servers regardless of the distribution. Thanks for the responses.
Bug#883662: RFS: agenda.app/0.44-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "agenda.app". * Package name: agenda.app Version : 0.44-1 Upstream Author : Philippe Roussel* URL : https://github.com/poroussel/simpleagenda * License : GPL-2+ Section : gnustep It builds this binary package: agenda.app - Calendar manager for GNUstep To access further information about this package, please visit the following URL: https://mentors.debian.net/package/agenda.app Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/a/agenda.app/agenda.app_0.44-1.dsc Or clone the Git repository: git clone https://anonscm.debian.org/git/pkg-gnustep/agenda.app.git Changes since the last upload: * New upstream release. * debian/compat: Set to 10. * debian/control (Build-Depends): Require debhelper >= 10 and gnustep-make >= 2.7.0-3 for recent config.mk. Add libdbuskit-dev for desktop notifications; drop dpkg-dev (obsolete) and imagemagick (not needed anymore as support for Debian menu is removed). (Depends): Remove ${gnustep:Depends}; obsolete. (Homepage): Replace with the new one at GitHub. (Vcs-Git, Vcs-Browser): Use canonical/secure URIs. (Standards-Version): Compliant with 4.1.2 as of this release. * debian/rules: Update for modern dh. * debian/install: * debian/docs: * debian/manpages: New files. * debian/menu: Delete. * debian/watch: Upgrade to version 4; use new upstream location. * debian/SimpleAgenda.desktop: Add Keywords field. * debian/patches/spelling-fix.patch: New, fix trivial spelling error. * debian/patches/series: New file. * debian/copyright: Switch to format 1.0; update Source field and copyright years. P.S. The package doesn't pass the piuparts test due to #832349.