Bug#887921: marked as done (RFS: bluefish/2.2.10-1 [ITA])

[Debian Bug Tracking System]

Your message dated Mon, 22 Jan 2018 04:48:45 +0100
with message-id <20180122034845.mdh6cw4vlx5sh...@angband.pl>
and subject line Re: Bug#887921: RFS: bluefish/2.2.10-1 [ITA]
has caused the Debian Bug report #887921,
regarding RFS: bluefish/2.2.10-1 [ITA]
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.)


-- 
887921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887921
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]

  Dear mentors,

  I am looking for a sponsor for my package "bluefish"

 * Package name: bluefish
   Version : 2.2.10-1
   Upstream Author : Olivier Sessink 
 * URL : http://bluefish.openoffice.nl
 * License : GPL-3+
   Section : web

  It builds those binary packages:

bluefish   - advanced Gtk+ text editor for web and software
development bluefish-data - advanced Gtk+ text editor (data)
 bluefish-plugins - advanced Gtk+ text editor (plugins)

  To access further information about this package, please visit the
  following URL:

  https://mentors.debian.net/package/bluefish


  Alternatively, one can download the package with dget using this
  command:

dget -x
https://mentors.debian.net/debian/pool/main/b/bluefish/bluefish_2.2.10-1.dsc


  Changes since the last upload:

  * New upstream release (Closes: #591965, #771394 ; LP:#1551298).
- Removed unnecessary 827747_fix_z-index_description.patch.
  * New maintainer (Closes: #887145).
  * Bumped to Standards-Version 4.1.3.
+ debian/compat: Raised to level 10.
+ Added Multi-Arch: same to bluefish-plugins.
- Removed dh-autoreconf Build-Depends. 
  * Changed the installation directory of the
bluefish.appdata.xml file (added changed-install-dir-appdata.patch).
+ Changed to usr/share/metainfo on bluefish.install.
  * Added hardering flags on debian/rules.
  * Changed desktop-data/bluefish.appdata.xml.in to legacyformat
(added patch file).


  Regards,
   Innocent De Marchi
--- End Message ---
--- Begin Message ---
On Sun, Jan 21, 2018 at 07:08:48PM +0100, Innocent De Marchi wrote:
>  * Package name: bluefish
>Version : 2.2.10-1

>   Changes since the last upload:
> 
>   * New upstream release (Closes: #591965, #771394 ; LP:#1551298).
> - Removed unnecessary 827747_fix_z-index_description.patch.
>   * New maintainer (Closes: #887145).
>   * Bumped to Standards-Version 4.1.3.
> + debian/compat: Raised to level 10.
> + Added Multi-Arch: same to bluefish-plugins.
> - Removed dh-autoreconf Build-Depends. 
>   * Changed the installation directory of the
> bluefish.appdata.xml file (added changed-install-dir-appdata.patch).
> + Changed to usr/share/metainfo on bluefish.install.
>   * Added hardering flags on debian/rules.
>   * Changed desktop-data/bluefish.appdata.xml.in to legacyformat
> (added patch file).

✓

-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢰⠒⠀⣿⡁ Imagine there are bandits in your house, your kid is bleeding out,
⢿⡄⠘⠷⠚⠋⠀ the house is on fire, and seven big-ass trumpets are playing in the
⠈⠳⣄ sky.  Your cat demands food.  The priority should be obvious...--- End Message ---

Bug#887954: marked as done (RFS: jag/0.3.4-1 -- arcade and puzzle 2D game)

[Debian Bug Tracking System]

Your message dated Mon, 22 Jan 2018 03:25:18 +0100
with message-id <20180122022518.tzvvu7hcylo3r...@angband.pl>
and subject line Re: Bug#887954: RFS: jag/0.3.4-1 -- arcade and puzzle 2D game
has caused the Debian Bug report #887954,
regarding RFS: jag/0.3.4-1 -- arcade and puzzle 2D game
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.)


-- 
887954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887954
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 "jag"

 * Package name: jag
   Version : 0.3.4-1
   Upstream Author : Carlos Donizete Froes 
 * URL : https://github.com/coringao/jag
 * License : GPL-3+
   Section : games

  It builds those binary packages:

  jag   - arcade and puzzle 2D game
  jag-data  - arcade and puzzle 2D game (data file)

  To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/jag

  Alternatively, one can download the package with dget using this command:

  dget -x https://mentors.debian.net/debian/pool/main/j/jag/jag_0.3.4-1.dsc

  More information about JAG can be obtained from 
https://github.com/coringao/jag/wiki.

  Changes since the last upload:

  **changelog version: 0.3.4**
* Fix unix install in 'game.pro' (Thanks for the contribution of yuryfdr)
* Fix editor build with Qt5 (Thanks for the contribution of yuryfdr)
* Added the GPLv3 license to the files in the 'editor' directory
* Files removed in 'data/help' directory indexed language: Russian and Dutch
* Added language in Portuguese (Thanks for the contribution of Ricky R. 
Froes)
* Updated language files

  **debian/changelog version: 0.3.4-1**
* New upstream release
* debian/control:
  + Changed Vcs-* URLs to salsa.d.o
  + Declare compliance with Debian Policy: 4.1.3
* Updated d/copyright years
* Added Debian Games Team in d/copyright
* Updated d/upstream/metadata years

  Regards,
   Carlos Donizete Froes
--- End Message ---
--- Begin Message ---
On Sun, Jan 21, 2018 at 11:46:18PM -0200, Carlos Donizete Froes wrote:
>  * Package name: jag
>Version : 0.3.4-1

>   Changes since the last upload:
> 
>   **changelog version: 0.3.4**
> * Fix unix install in 'game.pro' (Thanks for the contribution of yuryfdr)
> * Fix editor build with Qt5 (Thanks for the contribution of yuryfdr)
> * Added the GPLv3 license to the files in the 'editor' directory
> * Files removed in 'data/help' directory indexed language: Russian and 
> Dutch
> * Added language in Portuguese (Thanks for the contribution of Ricky R. 
> Froes)
> * Updated language files
> 
>   **debian/changelog version: 0.3.4-1**
> * New upstream release
> * debian/control:
>   + Changed Vcs-* URLs to salsa.d.o
>   + Declare compliance with Debian Policy: 4.1.3
> * Updated d/copyright years
> * Added Debian Games Team in d/copyright
> * Updated d/upstream/metadata years

✓

-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢰⠒⠀⣿⡁ Imagine there are bandits in your house, your kid is bleeding out,
⢿⡄⠘⠷⠚⠋⠀ the house is on fire, and seven big-ass trumpets are playing in the
⠈⠳⣄ sky.  Your cat demands food.  The priority should be obvious...--- End Message ---

Bug#887954: RFS: jag/0.3.4-1 -- arcade and puzzle 2D game

[Carlos Donizete Froes]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package "jag"

 * Package name: jag
   Version : 0.3.4-1
   Upstream Author : Carlos Donizete Froes 
 * URL : https://github.com/coringao/jag
 * License : GPL-3+
   Section : games

  It builds those binary packages:

  jag   - arcade and puzzle 2D game
  jag-data  - arcade and puzzle 2D game (data file)

  To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/jag

  Alternatively, one can download the package with dget using this command:

  dget -x https://mentors.debian.net/debian/pool/main/j/jag/jag_0.3.4-1.dsc

  More information about JAG can be obtained from 
https://github.com/coringao/jag/wiki.

  Changes since the last upload:

  **changelog version: 0.3.4**
* Fix unix install in 'game.pro' (Thanks for the contribution of yuryfdr)
* Fix editor build with Qt5 (Thanks for the contribution of yuryfdr)
* Added the GPLv3 license to the files in the 'editor' directory
* Files removed in 'data/help' directory indexed language: Russian and Dutch
* Added language in Portuguese (Thanks for the contribution of Ricky R. 
Froes)
* Updated language files

  **debian/changelog version: 0.3.4-1**
* New upstream release
* debian/control:
  + Changed Vcs-* URLs to salsa.d.o
  + Declare compliance with Debian Policy: 4.1.3
* Updated d/copyright years
* Added Debian Games Team in d/copyright
* Updated d/upstream/metadata years

  Regards,
   Carlos Donizete Froes

Bug#883627: RFS: network-manager-fortisslvpn/1.2.6-1 [ITP] -- NetworkManager Fortinet SSLVPN plugin

[Michael Biebl]

Hi!

On Wed, 17 Jan 2018 14:31:24 +0100 Lubomir Rintel  wrote:
> At 1.2.8 now.
> 
> https://mentors.debian.net/debian/pool/main/n/network-manager-fortisslvpn/network-manager-fortisslvpn_1.2.8-1.dsc

I think the package is already in a pretty good shape. Only a few minor
nits. The other day, I've uploaded gnome-shell 3.26.2-4 to unstable
where I pulled your patches for the libnm port.

I would thus prefer, if network-manager-fortisslvpn does not build the
libnm-glib compat support, as I'm actually in the process of getting all
affected packages updated to drop those dependencies.

Would be great if you apply the attached patch and re-upload 1.2.8-1.
I'm happy to sponsor the package then.

Regards,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
diff --git a/debian/control b/debian/control
index 0993a2e..eff1d16 100644
--- a/debian/control
+++ b/debian/control
@@ -4,15 +4,9 @@ Priority: optional
 Maintainer: Lubomir Rintel 
 Build-Depends: debhelper (>= 11),
intltool,
-   network-manager-dev (>= 1.2.0),
-   libnm-util-dev (>= 1.2.0),
-   libnm-glib-dev (>= 1.2.0),
-   libnm-glib-vpn-dev (>= 1.2.0),
-   libnm-gtk-dev (>= 1.2.0),
libnm-dev (>= 1.2.0),
libnma-dev (>= 1.2.0),
ppp-dev (>= 2.4.7-1+1),
-   libdbus-glib-1-dev (>= 0.74),
libsecret-1-dev (>= 0.18),
libgtk-3-dev (>= 3.4),
libglib2.0-dev (>= 2.32)
@@ -27,8 +21,6 @@ Depends: ${shlibs:Depends},
  ${misc:Depends},
  network-manager (>= 1.2.0),
  openfortivpn
-Breaks: network-manager-fortisslvpn-gnome (<< 1.2.4-2)
-Replaces: network-manager-fortisslvpn-gnome (<< 1.2.4-2)
 Description: network management framework (Fortinet SSLVPN plugin core)
  NetworkManager is a system network service that manages your network devices
  and connections, attempting to keep active network connectivity when
diff --git a/debian/network-manager-fortisslvpn-gnome.install b/debian/network-manager-fortisslvpn-gnome.install
index 8cbcbe5..c0c7cc6 100644
--- a/debian/network-manager-fortisslvpn-gnome.install
+++ b/debian/network-manager-fortisslvpn-gnome.install
@@ -1,4 +1,3 @@
-usr/lib/*/NetworkManager/libnm-fortisslvpn-properties.so
 usr/lib/*/NetworkManager/libnm-vpn-plugin-fortisslvpn-editor.so
 usr/lib/NetworkManager/nm-fortisslvpn-auth-dialog
 usr/share/appdata/network-manager-fortisslvpn.metainfo.xml
diff --git a/debian/rules b/debian/rules
index b04953f..91a1423 100755
--- a/debian/rules
+++ b/debian/rules
@@ -13,6 +13,7 @@ override_dh_auto_configure:
 	dh_auto_configure -- \
 		--libexecdir=/usr/lib/NetworkManager \
 		--disable-static \
+		--without-libnm-glib \
 		--with-pppd-plugin-dir=$(PPPD_PLUGIN_DIR)
 
 override_dh_makeshlibs:


signature.asc
Description: OpenPGP digital signature

Bug#849754: Review

[Michael Lustfield]

I reviewed this packaging and came up with some issues:

- The description does nothing to explain what makes this solution unique.
  + Why is this special?
  + How does it even work?
  + This should be easily gleaned from the package description.
- There is a lintian override for a legitimate mistake (unindented list).
- d/patches is scary...
  + Do not create lintian overrides using d/patches.
  + Keep patches to essential changes (not syntax and language changes).
  + Do not perform such a massive application rewrite using d/patches.
  + That change should be sent upstream... not held local.
- Absolutely DO NOT generate lintian-override files from d/patches.
- d/control should wrap long lines.
- d/rules could use some more whitespace.
- The py2 dependency is bad (very bad, especially at this point).
  + There are only two years left until py2 EoL.
- d/links suggests binaries are not being installed into standard locations.
- d/NEWS is not needed here and will be needlessly noisy for users.
- d/install should use wildcards to grab docs, instead of a file list
- d/install does not need the leading "./"
- d/compat should probably get a bump to 11
  + in d/control as well
- This is a python package, but raw source is being installed to /usr/lib.
  + The python scripts should be compiled.
  + There should be no "src/*" inclusion in d/install.
- Using d/install is not the correct way to include init script.
- The debhelper scripts have already been commented on.
- The interaction with the init system was also already commented on.
- This packaging doesn't follow any sort of standard.
  + There is no way to simply grab the source and build a package.
  + I would suggest creating a debian packaging repo (on alioth or salsa).
  + Using gbp will make it substantially easier for others to review.
  + Following a standard also means others can easily hop in and help.
- Tests are included, but nothing is done with them.
  + If you built them, use them!


Not Debian-centric:

- Why is there no Makefile?
  + What Install.txt provides should be available via make.
  + It's also where you would stick bits of code to generate documentation.
- The "release" version v0.0.0 suggests incomplete work.
  + There has been no release since v0.0.0 (in 2016), despite code changes.
- Why are man pages under debian/?
  + Make them a part of the software, not the package.
  + Generate the file man page during build (using make).


Personally, I don't understand what this backup solution offers over others.
Even after discussing this on IRC, I still really don't have any idea what it
offers over other solutions. I feel like a lot of buzz words are being
arbitrarily assigned to the description. This makes it hard to follow what is
fact and what is opinion.


Perhaps:
Guerilla Backup is a backup solution for small and unstable networks. It can
use your choice of transports (ssh, telnet, xmpp, etc.) to push backups to a
distributed cluster. Guerilla Backup ensures security by pre-encrypting data
before upload and only this key can be used to decrypt the data.

There's no real distinction between opinions, technical info, or general user
info. It makes it pretty much impossible to know what someone is getting with
this software.

Feel free to reach out via IRC if you need help!
-- 
Michael Lustfield

Bug#887758: closed by Adam Borowski <kilob...@angband.pl> (Re: Bug#887758: RFS: memleax/1.1.1-1)

[Nicholas D Steeves]

On Sun, Jan 21, 2018 at 02:51:07PM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the sponsorship-requests package:
> 
> #887758: RFS: memleax/1.1.1-1
> 
> It has been closed by Adam Borowski .
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Adam Borowski 
>  by
> replying to this email.

Thank you Adam! :-)


signature.asc
Description: PGP signature

Bug#887595: RFS: xft/2.3.2-1.1 [NMU]

[Julien Cristau]

Hi Hugh,

On Thu, Jan 18, 2018 at 10:43:01 +, Hugh McMaster wrote:

> Changes since the last upload:
>   * Non-maintainer upload.
>   * debian/control:
> - Mark libxft-dev Multi-Arch: same (Closes: #884176).
> 
IMO this is nothing that warrants a NMU, or an upload on its own.

Cheers,
Julien

Bug#887040: RFS: reptyr/0.6.2-1.1 [RC] [NMU]

[Nicolas Braud-Santoni]

On Sun, Jan 21, 2018 at 08:00:49PM +0100, Nicolas Braud-Santoni wrote:
> The version currently in mentors.d.n looks good to me.

Actually, I missed a minor wart: there is still no DEP3 metadata in the patches.
You can easily add that with `patchedit`.


signature.asc
Description: PGP signature

Bug#887040: RFS: reptyr/0.6.2-1.1 [RC] [NMU]

[Nicolas Braud-Santoni]

Hi Mateusz,

On Fri, Jan 19, 2018 at 10:36:40PM +0100, Mateusz Łukasik wrote:
> 
> Thanks for review. I pushed all suggested changes to mentors.

You are very welcome.

The version currently in mentors.d.n looks good to me.

Now we only need an actual DD to sponsor the upload; Jonathan
(in copy) might do it, but he is not very available since a few days.


Best,

  nicoo


signature.asc
Description: PGP signature

Bug#887921: RFS: bluefish/2.2.10-1 [ITA]

[Innocent De Marchi]

Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]

  Dear mentors,

  I am looking for a sponsor for my package "bluefish"

 * Package name: bluefish
   Version : 2.2.10-1
   Upstream Author : Olivier Sessink 
 * URL : http://bluefish.openoffice.nl
 * License : GPL-3+
   Section : web

  It builds those binary packages:

bluefish   - advanced Gtk+ text editor for web and software
development bluefish-data - advanced Gtk+ text editor (data)
 bluefish-plugins - advanced Gtk+ text editor (plugins)

  To access further information about this package, please visit the
  following URL:

  https://mentors.debian.net/package/bluefish


  Alternatively, one can download the package with dget using this
  command:

dget -x
https://mentors.debian.net/debian/pool/main/b/bluefish/bluefish_2.2.10-1.dsc


  Changes since the last upload:

  * New upstream release (Closes: #591965, #771394 ; LP:#1551298).
- Removed unnecessary 827747_fix_z-index_description.patch.
  * New maintainer (Closes: #887145).
  * Bumped to Standards-Version 4.1.3.
+ debian/compat: Raised to level 10.
+ Added Multi-Arch: same to bluefish-plugins.
- Removed dh-autoreconf Build-Depends. 
  * Changed the installation directory of the
bluefish.appdata.xml file (added changed-install-dir-appdata.patch).
+ Changed to usr/share/metainfo on bluefish.install.
  * Added hardering flags on debian/rules.
  * Changed desktop-data/bluefish.appdata.xml.in to legacyformat
(added patch file).


  Regards,
   Innocent De Marchi

Bug#887665: RFS: usbguard/0.7.1+ds-1

[Adam Borowski]

On Thu, Jan 18, 2018 at 10:34:37PM +0100, Muri Nicanor wrote:
> I am looking for a sponsor for my package "usbguard"
> 
> * Package name : usbguard
>   Version  : 0.7.1+ds-1

> Changes since last upload:
> 
>   * New upstream version 0.7.1 (Closes: #868160)

The bug you're closing is not "please package new upstream".  Thus,
this part should be:

  * New upstream version 0.7.1
+ Fix failure with read-only /etc (Closes: #868160)

>   * remove dh-systemd due to being part of debhelper (>= 9.20160709)
>   * bump standards version
>   * add correct section to libusbguard0
>   * remove parsing of dpkg-genchangelog
>   * updated the watch file for the new github url, modified the archive name
> so the correct version will be used and removed the signature line, as
> that version is not signed
>   * remove patches that have been upstreamed
>   * add asciidoctor to build depends

Please run lintian before requesting sponsoring; it automates checking for
most of likely problems, saving time for both you and me:

E: usbguard changes: unreleased-changes

The package is explicitely marked as "not for uploading" (ie, is meant for
testing, review and further work).  As you filed the RFS, I guess it's not
what you wanted...

W: usbguard source: maintainer-script-lacks-debhelper-token 
debian/usbguard.postinst

Debhelper wants to add further things to the postinst, but doesn't know
where.

W: usbguard source: debian-watch-could-verify-download 
debian/upstream/signing-key.asc

The new version is not signed; you should then delete (or rename away) this
key to mark the lack of signature as intentional.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢰⠒⠀⣿⡁ Imagine there are bandits in your house, your kid is bleeding out,
⢿⡄⠘⠷⠚⠋⠀ the house is on fire, and seven big-ass trumpets are playing in the
⠈⠳⣄ sky.  Your cat demands food.  The priority should be obvious...

Bug#887907: RFS: gnustep-back/0.26.2-1

[Yavor Doganov]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I'm looking for a sponsor for my package "gnustep-back".  This version
requires gnustep-gui/0.26.2-1 which is in the NEW queue.  I have
included an additional link to the .dsc for convenience.

 * Package name: gnustep-back
   Version : 0.26.2-1
   Upstream Author : Fred Kiefer ,
 Adam Fedor ,
 Alexander Malmberg ,
 Banlu Kemiyatorn  and many others
 * URL : http://gnustep.org
 * License : LGPL-2+ (bundles), GPL-3+ (tools)
   Section : gnustep

It builds these binary packages:

gnustep-back-common - GNUstep GUI Backend - common files
gnustep-back0.26 - GNUstep GUI Backend
gnustep-back0.26-art - GNUstep GUI Backend (art)
gnustep-back0.26-cairo - GNUstep GUI Backend (cairo)
gnustep-back0.26-xlib - GNUstep GUI Backend (xlib)

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/gnustep-back

Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/g/gnustep-back/gnustep-back_0.26.2-1.dsc
  dget -x 
https://mentors.debian.net/debian/pool/main/g/gnustep-gui/gnustep-gui_0.26.2-1.dsc

Changes since the last upload:

  [ Eric Heintzmann ]
  * debian/rules:
+ Remove -shared-libgcc LDFLAG, now useless.
+ Append --as-needed LDFLAG.
+ Hardening: remove -pie option.
+ Now build depends on latest gnustep-gui package.
  * debian/control:
+ Bump Standards Versions to 4.1.0.
+ As requested by Gürkan, change his name.
  * New fix-spelling-error.patch.
  * Add a testsuite.

  [ Yavor Doganov ]
  * New upstream release 0.26.2:
+ Rename packages following the SONAME change:
  - gnustep-back0.25 -> gnustep-back0.26
  - gnustep-back0.25-art -> gnustep-back0.26-art
  - gnustep-back0.25-cairo -> gnustep-back0.26-cairo
+ New package gnustep-back0.26-xlib: prepare for removal of the art
  backend due to removal of src:libart-lgpl (Addresses: #885786).
  * debian/watch: Switch to ftp.gnustep.org; much more reliable.
  * debian/compat: Bump compat level to 11.
  * debian/rules: Replace shell comments with makefile comments; M-x
wh-cl.  Use convenience variables where possible.
(DEB_LDFLAGS_MAINT_APPEND): Add -Wl,--no-undefined.
(override_dh_testdir): New target to regenerate debian/control.
(override_dh_auto_configure): Substitute GNUSTEP_SYSTEM_DOC as well
when generating gnustep-back-common.install.  Configure the xlib
backend in a separate builddir; handle the generation of maintainer
scripts and .install/.links files.
(override_dh_auto_build): Pass dpkg-buildflags explicitly as OBJCFLAGS
and CFLAGS are being reset by gnustep-make.  Build documentation.
Pass $(optim) for proper noopt support.  Pass tools=no and fonts=no to
the cairo build.  Remove unnecessary tools recipe; add one for xlib.
(override_dh_auto_install): Install documentation and the xlib
backend.
(override_dh_auto_clean): Clean documentation; ignoring errors.
Simplify the recipe.
(override_dh_strip): Remove in favor of automatic -dbgsym packages.
(override_dh_shlibdeps): Add override to fix circular dependencies;
regression introduced in 0.25.0-1 (Closes: #882078).  Thanks to Bill
Allombert for the report.
  * debian/templates/control.m4: Remove -dbg, add new package -xlib.
(Build-Depends): Require debhelper >= 11 and gnustep-make >= 2.7.0-3
for the optim variable definition.
(Section): Remove section "libs" for all packages as it is wrong
according to lintian (and to me).
(Depends): Relax dependencies on -common to ease transitions with the
ultimate goal to support partial upgrades.
(Breaks, Replaces): Remove; obsolete.
(Standards-Version): Declare compliance with 4.1.3.
  * debian/control: Regenerate.
  * debian/templates/gnustep-back-common.install.in: Add
@GNUSTEP_SYSTEM_DOC@/*.
  * debian/templates/gnustep-back-common.prerm.in: Also delete
/var/lib/GNUstep, another regession in 0.25.0-1 (Closes: #832349).
Thanks Andreas Beckmann.
  * debian/patches/autoreconf.patch: New; fix autoreconf failure.
  * debian/patches/no-freetype-config.patch: New; use PKG_CHECK_MODULES to
detect freetype as freetype-config is being removed (Closes: #887719).
  * debian/patches/link-libs.patch: New; fix FTBFS with ld --no-undefined.
  * debian/patches/fix-spelling-error.patch: Fix another spelling error.
  * debian/patches/series: Update.
  * debian/clean: Simplify; add Documentation/version.texi.
  * debian/font_cacher.1: New file.
  * debian/gnustep-back-common.manpages: Install it.
  * debian/changelog: Whitespace cleanup.
  * debian/copyright: Update copyright years, add debian packaging
copyright/license information, add configure 

Bug#849754: Update from IRC discussion

[halfdog]

In response to discussion, packaging was adjusted:

* Added lintian override to ignore non-standard directory perms
  explaining the read restrictions
* Ignore possible-unindented-list-in-extended-description (false
  positive)
* Added docstrings to systemd service files, reported when using
  lintian -EviIL +pedantic

Bug#887758: marked as done (RFS: memleax/1.1.1-1)

[Debian Bug Tracking System]

Your message dated Sun, 21 Jan 2018 15:49:06 +0100
with message-id <20180121144906.hb2lbtwi3diz4...@angband.pl>
and subject line Re: Bug#887758: RFS: memleax/1.1.1-1
has caused the Debian Bug report #887758,
regarding RFS: memleax/1.1.1-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.)


-- 
887758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887758
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 "memleax".

Hi Jonathan,

I've CCed you because you sponsored my last upload.  Please consider
granting DM privileges for this package if you're satisfied with the
quality of my work :-) -- P.S, I retagged debian/1.1.0-1 to
incorporate your fixes.  Btw, I take it the bits I copied from the
Valgrind package and then commented out will never be potentially
useful?

Package name: memleax
Version : 1.1.1-1
Upstream Author : WuBingzheng 
URL : https://github.com/WuBingzheng/memleax
License : GPL-2
Section : devel

It builds this binary package:

memleax- debug a running process for memory leaks

To access further information about this package, please visit the following 
URL:

https://mentors.debian.net/package/memleax

Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/m/memleax/memleax_1.1.1-1.dsc

Alternatively, one can clone its repository with this command:

git clone ssh://git.debian.org/git/collab-maint/memleax.git

More information about memleax can be obtained from 
https://github.com/WuBingzheng/memleax.


Changes since the last upload:

memleax (1.1.1-1) unstable; urgency=medium

  * New upstream version.
  * Only build for supported architectures: amd64, arm64, armel, armhf,
and i386. (Closes: #886971)
  * Switch to debhelper 11.
  * Declare compat level 11.
  * Fix Vcs-Git link.

 -- Nicholas D Steeves   Fri, 19 Jan 2018 12:14:10 -0500

memleax (1.1.0-1) unstable; urgency=medium
--- End Message ---
--- Begin Message ---
On Fri, Jan 19, 2018 at 12:38:34PM -0500, Nicholas D Steeves wrote:
> Version : 1.1.1-1
> Upstream Author : WuBingzheng 

> Changes since the last upload:
> 
> memleax (1.1.1-1) unstable; urgency=medium
> 
>   * New upstream version.
>   * Only build for supported architectures: amd64, arm64, armel, armhf,
> and i386. (Closes: #886971)
>   * Switch to debhelper 11.
>   * Declare compat level 11.
>   * Fix Vcs-Git link.

✓

-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢰⠒⠀⣿⡁ Imagine there are bandits in your house, your kid is bleeding out,
⢿⡄⠘⠷⠚⠋⠀ the house is on fire, and seven big-ass trumpets are playing in the
⠈⠳⣄ sky.  Your cat demands food.  The priority should be obvious...--- End Message ---

Bug#887870: RFS: pcc/1.2.0~DEVEL+20180120-1 [ITP]

[Yangfl]

2018-01-21 20:54 GMT+08:00 Mathieu Malaterre :
> On Sun, Jan 21, 2018 at 1:19 PM, Yangfl  wrote:
>> Hi,
>>
>> Sorry for including wrong deps. I've fixed them all and reuploaded the
>> package into mentors.d.o.
>>
>> I'd like to mention that pcc alone *won't* work without the pcc-libs
>> (which I've already packaged and tested). But I'd want pcc-libs to be
>> built with pcc, so pcc must be uploaded prior to pcc-libs.
>
> Are you saying that #638309 is still there then ?
>
> $ pcc --version
> Portable C Compiler 1.2.0.DEVEL 20171212 for x86_64-pc-linux-gnu
> $ echo 'main() {}' > junk.c
> $ pcc junk.c
> /usr/bin/x86_64-linux-gnu-ld: cannot find crtbegin.o: No such file or 
> directory
> /usr/bin/x86_64-linux-gnu-ld: cannot find -lpcc
> error: /usr/bin/x86_64-linux-gnu-ld terminated with status 1

You can install https://mentors.debian.net/package/pcc-libs (newer
version), hope it can work.

Bug#887870: RFS: pcc/1.2.0~DEVEL+20180120-1 [ITP]

[Mathieu Malaterre]

On Sun, Jan 21, 2018 at 1:19 PM, Yangfl  wrote:
> Hi,
>
> Sorry for including wrong deps. I've fixed them all and reuploaded the
> package into mentors.d.o.
>
> I'd like to mention that pcc alone *won't* work without the pcc-libs
> (which I've already packaged and tested). But I'd want pcc-libs to be
> built with pcc, so pcc must be uploaded prior to pcc-libs.

Are you saying that #638309 is still there then ?

$ pcc --version
Portable C Compiler 1.2.0.DEVEL 20171212 for x86_64-pc-linux-gnu
$ echo 'main() {}' > junk.c
$ pcc junk.c
/usr/bin/x86_64-linux-gnu-ld: cannot find crtbegin.o: No such file or directory
/usr/bin/x86_64-linux-gnu-ld: cannot find -lpcc
error: /usr/bin/x86_64-linux-gnu-ld terminated with status 1

Bug#887870: RFS: pcc/1.2.0~DEVEL+20180120-1 [ITP]

[Yangfl]

Hi,

Sorry for including wrong deps. I've fixed them all and reuploaded the
package into mentors.d.o.

I'd like to mention that pcc alone *won't* work without the pcc-libs
(which I've already packaged and tested). But I'd want pcc-libs to be
built with pcc, so pcc must be uploaded prior to pcc-libs.

Sincerely,

Bug#887870: RFS: pcc/1.2.0~DEVEL+20180120-1 [ITP]

[Mathieu Malaterre]

Are you using the package ? I cannot even install it.

$ dget -u 
https://mentors.debian.net/debian/pool/main/p/pcc/pcc_1.2.0~DEVEL+20180120-1.dsc
$ cd pcc-1.2.0\~DEVEL+20180120
$ debuild
$ sudo dpkg -i ../pcc_1.2.0~DEVEL+20180120-1_amd64.deb
Selecting previously unselected package pcc.
(Reading database ... 483634 files and directories currently installed.)
Preparing to unpack .../pcc_1.2.0~DEVEL+20180120-1_amd64.deb ...
Unpacking pcc (1.2.0~DEVEL+20180120-1) ...
dpkg: dependency problems prevent configuration of pcc:
 pcc depends on pcc-for-x86-64-linux-gnu; however:
  Package pcc-for-x86-64-linux-gnu is not installed.

dpkg: error processing package pcc (--install):
 dependency problems - leaving unconfigured
Processing triggers for man-db (2.7.6.1-2) ...
Errors were encountered while processing:
 pcc

Bug#887870: RFS: pcc/1.2.0~DEVEL+20180120-1 [ITP]

[Sven Joachim]

Disclaimer: I am not a DD and cannot sponsor your package.

On 2018-01-21 15:01 +0800, Yangfl wrote:

> Package: sponsorship-requests
> Severity: wishlist
>
> Dear mentors,
>
> I am looking for a sponsor for my package "pcc"
>
>  * Package name: pcc
>Version : 1.2.0~DEVEL+20180120-1
>Upstream Author : Anders Magnusson 
>  * URL : http://pcc.ludd.ltu.se/
>  * License : BSD
>Section : devel
>
> It builds those binary packages:
>
>   pcc   - Portable C Compiler
>
> To access further information about this package, please visit the
> following URL:
>
> https://mentors.debian.net/package/pcc
>
>
> Alternatively, one can download the package with dget using this command:
>
>   dget -x 
> https://mentors.debian.net/debian/pool/main/p/pcc/pcc_1.2.0~DEVEL+20180120-1.dsc

Haven't tried to build it yet, but I see the following rather serious
problem: pcc depends on unavailable packages on amd64 and i386,
apparently a remnant from the previous version which used to be in
experimental.  This makes me wonder how you have tested your package,
when it is not installable.  In particular, has bug #638309 been fixed?

The debian/links file should probably be removed, it only works on amd64
and seems to be redundant with the override_dh_link rule in debian/rules.

> More information about hello can be obtained from https://www.example.com.

Information about pcc, however, can be found at
http://pcc.ludd.ltu.se/. ;-) Sadly they don't do https. :-(

> Changes since the last upload:
>
> [your most recent changelog entry]

  * Initial release (Closes: #442913)

Which is not completely true, since version 1.1.0~DEVEL+20110422-1 used
to be in experimental: https://tracker.debian.org/pkg/pcc.  Whether it's
worth to keep the old changelog entry for that version is debatable.

Cheers,
   Sven