Bug#873094: RFS: granite/0.4.1-1 [ITP]

[Tobias Frost]

Am 28. Februar 2018 05:53:31 MEZ schrieb Yangfl :
>2018-02-28 2:30 GMT+08:00 Tobias Frost :
>> Homework:
>> - please manually remove the package from mentors. (as it has to pass
>NEW)
>
>IIRC the package will be auto-removed, isn't it?

After being accepted, yes. But until then it will show up on the list of 
packages needing sponsoring. To avoid that someone looks at it and waste time 
on it, simply manually delete it.

>> Future uploads:
>> - please add a dep3 header to the patch.
>> - there are tons of depereciation warnings in the upstream code..
>please ask upstream or work towards fixing them...
>
>I can't see anything like 'deprecate' from cmake log. Did I miss
>something?

Not cmake.
Iirc gtk depreciation messages in the build log.

Bug#873094: RFS: granite/0.4.1-1 [ITP]

[Yangfl]

2018-02-28 2:30 GMT+08:00 Tobias Frost :
> Homework:
> - please manually remove the package from mentors. (as it has to pass NEW)

IIRC the package will be auto-removed, isn't it?

> Future uploads:
> - please add a dep3 header to the patch.
> - there are tons of depereciation warnings in the upstream code.. please ask 
> upstream or work towards fixing them...

I can't see anything like 'deprecate' from cmake log. Did I miss something?

Bug#889515: Review of persepolis

[Moein Alinaghian]

Dear Julien,

Thanks for reviewing my package. It was really helpful.
I fixed some of the mentioned issues and uploaded a new package to
mentors.debian.net.

There are still the following issues which I cannot fix:
no-upstream-changelog - Because there isn't any upstream changelog.
debian-watch-may-check-gpg-signature - Because the upstream files are
not signed.
testsuite-autopkgtest-missing - Because there isn't a suitable test in
the upstream at the moment.

--
Sincerely yours,
Moein Alinaghian


On Sat, 24 Feb 2018 09:29:04 +0100 Julien Puydt
 wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Control: tags -1 moreinfo
>
> Hi,
>
> I had a look at your packaging, and found the following:
>
> (-) debhelper 10 -- some advise 11
> (-) standard-version 4.1.2 -- we're now at 4.1.3
> (-) in d/copyright, you could share the license chunks:
> Files: foo
> Copyright: whatever
> License: GPL-3+
>
> Files: bar
> Copyright: whatever
> License: GPL-3+
>
> License: GPL-3+
>  Here comes the text, once!
>
>
> Then I tried to compile it, and saw what lintian had to say:
>
> $ lintian -I persepolis_3.0.1-1_amd64.changes --pedantic
> P: persepolis source: package-uses-old-debhelper-compat-version 10
> (see above: should fix)
> W: persepolis source: dep5-copyright-license-name-not-unique
> (paragraph at line 26)
> (see above: must fix)
> I: persepolis source: out-of-date-standards-version 4.1.2 (released
> 2017-11-30) (current is 4.1.3)
> (see above: should fix)
> I: persepolis source: testsuite-autopkgtest-missing
> (ok, it's not always possible)
> P: persepolis source: debian-watch-does-not-check-gpg-signature
> (ok, it's not always possible)
> P: persepolis: no-upstream-changelog
> (ok, it's not always possible)
> I: persepolis: extended-description-is-probably-too-short
> (should fix)
>
> I hope that helps,
>
> Snark on #debian-mentors
> -BEGIN PGP SIGNATURE-
>
> iQIzBAEBCgAdFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAlqRIkkACgkQBMU71/4D
> BVGnNBAAmVMhKSXnaJGGE/EdRecoVJ+Jj2hufZHlXA9hW9jY3DlDxQLv9rANl2Pg
> lH+SPv4XDMOz92A698kfAE7tQkWpnOnirvvn+En6wT971WhL93IuFtjk4qWzo/8Y
> H4DdsrCBV777VGFpflX0aq2E0FBM9hk1BeUjrNiFrMTdUmwZPglDU7Mws3swVH7R
> jSh5ZDACh0NT20mYzr8VsLkDT4m184pRTOfn0ez0ND8HtfTun3g83KYMezXmhPye
> u7cFvCcjxOkhqLQv2OoPZrHd/c0WpZzJ5zFPw3chvCMiteaEzdspoZ1coOdF1CKE
> Jh+/mD1Kjdo00D4OsHD9ReOO+olKYPTz8mKlpezZJqA7yDmSWbMMsFEPJ322q5dG
> fD/GLDbsLBjqUXoCDU185ZfSz7dol58U00fqOwMmlXzP16q4iCxTf2wisMTLlJCx
> zxsDOokRshCmqT6T4mClfA1eblSxJAqQeqTBenfroa2N0HxDAvq8jRAw9GJy6RZF
> AmYY2/D+L+zhe3dD4xs2QgKlBkMlH2kR/8/ymRoDcfCk7bZpWdvL5yBSxjVNrIFu
> 1yhXjrqMUEO72xXDVTM+JvOZ/XBifWFgEq71GvQ27k/riAsWGNP1sLQgDkzRtlj6

Bug#890878: RFS: company-irony

[Nicholas D Steeves]

On Mon, Feb 26, 2018 at 02:43:51PM -0700, Sean Whitton wrote:
> Hello,
> 
> On Mon, Feb 26 2018, Alberto Luaces wrote:
> 
> > I have refreshed those fields.  I have not still refreshed the
> > changelog date in order to wait for more potential changes.
> 
> Thanks for fixing this.
> 
> I'm not in a position to properly review this package, unfortunately.
> Sorry for suggesting in a previous mail that I was planning on doing
> that.  Just wanted to get the Vcs-* fields fixed.
> 
> -- 
> Sean Whitton

Hi Alberto,

Welcome to the team, and thank you for packaging company-irony!  I
consider it a valuable addition to the archive :-)  The following
might be something you already know, but if not, here's a neat trick:

Make your changes, and then while in emacs, M-x magit-status, then d u
(diff unstaged).  Stage the changes that are part of one logical
operation with C-, select region, then s (or just s on a hunk to
stage the whole hunk).  Finally c c (commit staged), write your commit
message, and finally C-c C-c.  Later you can use gbp dch -a [-N
$upstream_version-$debian_revision, if necessary] to generate a nice changelog.

Hi Sean and David,

I'm willing to do reviews, and want to encourage best practises and our
team's high standards.  Please feel free to comment.

debian/copyright:
  Author's email is directly underneath Copyright in
  company-irony.el's header.  I would either Add it to the Copyright:
  for the 'Files: *' section, or add an Upstream-Contact field. (
  https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/#examples
  ) Sean, what's your best practices stance on this?  I'm guessing
  Upstream-Contact.

debian/gbp.conf:
  gbp:info: Tarballs 'company-irony_1.1.0.orig.tar.xz' not found
  gbp:warning: Pristine-tar branch "pristine-tar" not found
  gbp:info: Creating
  /home/sten/devel/build-area/company-irony_1.1.0.orig.tar.xz
  gbp:error: v1.1.0 is not a valid treeish

  Alberto, if you're using pristine-tar you need to push the branch;
  alternatively, if you got upstream source from git and are not using
  pristine-tar you need to push the upstream tag to our repo and also
  modify gbp.conf to indicate you're not using pristine-tar.  Also,
  for future reference, if you choose the git-only workflow you'll
  need to push each new upstream version tag as you update the
  package.

debian/watch:
  Missing, please add one.  Between the one for irony-mode (watch
  version 3, Guillaume is also the upstream for this one) and
  fountain-mode (version 4) you should be able to figure out how to
  produce a working v4 one ;-)  The only reason I mention
  fountain-mode is because it's the one I've checked most recently.

I'll do a more in depth review in the next round.

Cheers,
Nicholas


signature.asc
Description: PGP signature

Re: Package EOL checklist

[Joseph Herlant]

Thanks all for your help and advises. That's perfect!
I'll have a look into it. :)

Joseph

Bug#890681: marked as done (RFS: gexiv2/0.10.8-1 -- GObject-based wrapper around the Exiv2 library)

[Debian Bug Tracking System]

Your message dated Tue, 27 Feb 2018 18:02:10 -0500
with message-id 

Re: Package EOL checklist

[Paul Wise]

On Wed, Feb 28, 2018 at 1:36 AM, Andrey Rahmatullin wrote:

> Does it have revdeps or not? If it does, you can't just remove it. If it
> doesn't, I'd say don't maintain libs which no one needs.

There is one reverse dependency:

$ ssh mirror.ftp-master.debian.org dak rm -s unstable -Rn libmrss
...
Checking reverse dependencies...
# Broken Depends:
rsstail: rsstail

# Broken Build-Depends:
rsstail: libmrss0-dev

Dependency problem found.

I would suggest you talk to rsstail and libmrss upstreams about
transferring upstream maintainership of libmrss from the current
location to one where the rsstail upstream has write access (and the
original maintainer has access too, just in case). Once the move is
done, the original author can redirect the website/etc. Make sure
everything is transferred from the old location to the new one,
including the CVS repository, the tarballs and the documentation. If
moving to github where rsstail is, the CVS repository could be
converted to git, the tarballs could be attached to git tags and the
documentation is probably already in CVS but if not it could be added
to git or converted to a README.md and added to git.

The CVS to git conversion will work like this:

The CVS repo is currently offline. The libmrss upstream (or the
ippolita.net admins) should send a copy of the repository to the
person who is doing the conversion.

Prepare a cvs2git-authors file containing the CVS logins of committers
and how the corresponding git commit authors/committers should be
represented, for eg:

pabs=Paul Wise 

git cvsimport -A cvs2git-authors -akmRv -d libmrss-CVS -C libmrss-git
-o master libmrss &> log

If libmrss upstream cannot access the CVS repository any more then the
procedure is a bit more involved and you will have to download each of
the tarballs and import them in order, adding a git tag for each one.
If it comes to it, you can adapt the tar2git script I have attached
for this. I used the script to convert the whowatch tarball history to
git.

Once the git conversion is done and there are git tags corresponding
to each tarball, then the person doing the conversion should attach
each tarball to the corresponding git tag using the github interface.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


tar2git
Description: Binary data

Bug#890814: marked as done (RFS: anosql/0.2.0-1 [ITP])

[Debian Bug Tracking System]

Your message dated Tue, 27 Feb 2018 22:21:18 +
with message-id 
and subject line closing RFS: anosql/0.2.0-1 [ITP]
has caused the Debian Bug report #890814,
regarding RFS: anosql/0.2.0-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.)


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

* Package name: anosql
  Version : 0.2.0-1
  Upstream Author : Honza Pokorny
* URL : https://github.com/honza
* License : BSD-3-clause
  Section : python

It builds those binary packages:

  python-anosql - Python Library for using SQL
 python3-anosql - Python 3 library for using SQL

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

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

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

 dget -x https://mentors.debian.net/debian/pool/main/a/anosql/anosql_0.2.0-1.dsc

Changes since the last upload:

 * Initial release (closes: #890523)

Regards,
 Florian Grignon


-- System Information:
Debian Release: 9.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.13.0-0.bpo.1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Package anosql version 0.2.0-1 is in unstable now.
https://packages.qa.debian.org/anosql--- End Message ---

Re: Package EOL checklist

[gregor herrmann]

On Tue, 27 Feb 2018 11:20:49 -0800, Joseph Herlant wrote:

> 5. Once there is no more package depending on yours (probably after a
> few months), ask the ftp masters to remove the package from testing
> and unstable via a mail to their list.

"From unstable" (it will be removed automatically from testing later,
and testing is not ftp-master territory), and "by filing an RM
(removal) bug against (the pseudo-package) 'ftp.debian.org'."

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Lenny Kravitz: Fly Away


signature.asc
Description: Digital Signature

Bug#890681: RFS: gexiv2/0.10.8-1 -- GObject-based wrapper around the Exiv2 library

[Jason Crain]

On Tue, Feb 27, 2018 at 11:47:04AM -0500, Jeremy Bicha wrote:
> Please update the Vcs fields and I'll sponsor the update.
> 
> Also, it would be good for you to add a redirect at
> https://salsa.debian.org/salsa/AliothRewriter

I've updated the Vcs URLs, added a merge request for AliothRewriter, and
uploaded to mentors.

https://mentors.debian.net/debian/pool/main/g/gexiv2/gexiv2_0.10.8-1.dsc

Re: Package EOL checklist

[Andrey Rahmatullin]

On Tue, Feb 27, 2018 at 11:20:49AM -0800, Joseph Herlant wrote:
> > Yes, this needs to be done.
> 
> 
> Thanks for your answer.
> So is the list I was putting in my initial mail correct for this use case?
> 
> 3. Open bugs on all depending packages (including those who use it as
> build dependencies) to have them switch to something else.
> 4. Open a bug for your package explaining it's end of life so that
> people can see it easily.
> 5. Once there is no more package depending on yours (probably after a
> few months), ask the ftp masters to remove the package from testing
> and unstable via a mail to their list.
> 6. Wait that the package is out of old-stable to drop the git
> repository from Salsa.
Looks more or less fine to me but maybe someone else will advise something
better.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Re: Package EOL checklist

[Joseph Herlant]

> Yes, this needs to be done.


Thanks for your answer.
So is the list I was putting in my initial mail correct for this use case?

3. Open bugs on all depending packages (including those who use it as
build dependencies) to have them switch to something else.
4. Open a bug for your package explaining it's end of life so that
people can see it easily.
5. Once there is no more package depending on yours (probably after a
few months), ask the ftp masters to remove the package from testing
and unstable via a mail to their list.
6. Wait that the package is out of old-stable to drop the git
repository from Salsa.

Thanks
Joseph

Bug#873094: marked as done (RFS: granite/0.5+ds-1 [ITP])

[Debian Bug Tracking System]

Your message dated Tue, 27 Feb 2018 19:30:19 +0100
with message-id <20180227183018.gd29...@coldtobi.de>
and subject line Re: Bug#873094: RFS: granite/0.4.1-1 [ITP]
has caused the Debian Bug report #873094,
regarding RFS: granite/0.5+ds-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.)


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

* Package name: granite
  Version : 0.4.1-1
 Upstream Author : elementary OS
* URL : https://launchpad.net/granite
* License : LGPLv3+
  Section : libs

It builds those binary packages:

gir1.2-granite-1.0 - extension of GTK+ libraries (introspection files)
granite-demo - extension of GTK+ libraries (demo binary)
libgranite-common - extension of GTK+ libraries (common files)
libgranite-dev - extension of GTK+ libraries (development files)
libgranite3 - extension of GTK+ libraries
libgranite3-dbg - extension of GTK+ libraries (debugging symbols)

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

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


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

  dget -x 
https://mentors.debian.net/debian/pool/main/g/granite/granite_0.4.1-1.dsc

More information about hello can be obtained from
https://github.com/elementary/granite .

Changes since the last upload:

 granite (0.4.1-1) unstable; urgency=medium

   * Initial release (Closes: #872919)


Regards,
 Yangfl
--- End Message ---
--- Begin Message ---
On Thu, Feb 22, 2018 at 10:21:37PM +0800, Yangfl wrote:
> I (should have already) fixed them all. Will soon upload to mentors.d.o

Uploaded! Thanks for your contributions to Debian!

Homework:
- please manually remove the package from mentors. (as it has to pass NEW)

Future uploads:
- please add a dep3 header to the patch.
- there are tons of depereciation warnings in the upstream code.. please ask 
upstream or work towards fixing them...

-- 
tobi


signature.asc
Description: PGP signature
--- End Message ---

Bug#886399: RFS: opencascade/7.2.0-1 [ITP]

[Tobias Frost]

Hi, 

just to avoid a dead-lock: you're still working on the package, nothing to
review atm?
Just let us know (and remove the moreinfo tag as sign) when ready for
the next round of review. (I'd like to avoid reviewing when not everything
has been implemented)

--
tobi

On Thu, Feb 22, 2018 at 04:37:34PM -0600, Kurt Kremitzki wrote:
> I'm still addressing some of the feedback given by you and Tobias, but I
> thought I would post an update.
> 
> On 02/12/2018 05:44 AM, Anton Gladky wrote:
> > Hi Kurt,
> > 
> > Just a short review. I did not test the package. But some
> > stuff should be fixed before it will be uploaded.
> > 
> > As I understand you want to maintain the package under the
> > umbrella of debian science team? If so, please fix some
> > corresponding fields (maintaner etc) in d/control.
> > 
> > =
> > 1. source/include-binaries remove
> > 2. source/options - remove
> > 3. quilt debian/control : quilt - remove
> > 4. VCS - salsa under d/science
> > 5. all lib-packages should be numbered according to its API-version,
> > something like libopencascade-modeling-algorithms7.2
> > 6. Install files of lib-packages should have something like
> > usr/lib/*/libTKMath.so.*, not the particular version
> > 7. --parallel option is not needed with debhelper > 10
> 
> All of the above are done (but not pushed yet.)
> 
> > 8. Not sure about option -DCMAKE_BUILD_TYPE=Release.
> 
> Neither am I--normally when I run eg `ccmake` on the OpenCASCADE source this
> variable is already set to `Release`, but without this I get an error
> suggesting it's being set to `none`. I chalked it up to an idiosyncracy in
> OpenCASCADE.
> 
> > 9. Simplify d/rules. All cp-commands should be replaces by the lines
> > in d/install-files
> 
> Got it--the only one I had a question about was the
> opencascade-draw7.2.desktop file I have in the debian directory. Is it ok
> that I now have something like this in opencascade-draw7.2.install?:
> 
> ../opencascade-draw*.desktop usr/share/applications/
> 
> > 10. Check whether you need mkdir-commands in d/rules
> 
> They were superfluous.
> 
> > 11. override_dh_makeshlibs looks questionable
> 
> Removed.
> 
> > 12. Use dh_missing --fail-missing to be sure that all files are installed.
> 
> Good suggestion, there were about 300 files not being included, most of them
> part of opencascade-draw, which isn't used by FreeCAD and thus I hadn't
> noticed a problem from this.
> 
> However, with all the files included the package now FTBFS with a ton of
> errors like this:
> 
> dpkg-shlibdeps: error: cannot find library libTKBinTObj.so.7 needed by
> debian/opencascade-draw7.2/usr/lib/x86_64-linux-gnu/libTKTObjDRAW.so.7.2.0
> (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '')
> 
> All the libraries mentioned are files provided by the libopencascade-
> packages, so I tried adding them to opencascade-draw7.2's Depends: but that
> didn't resolve it, so I'm a little stuck.
> 
> > 13. Point the first upload into the experimental.
> 
> Updated.
> 
> > 14. Double-check __all__ the files and their licenses to save the time
> > for FTP-masters.
> 
> Will do once I clean up my current work and before I push.
> 

Bug#890803: marked as done (RFS: pokemmo-installer/1.4.6-1 -- Installer and Launcher for the PokeMMO emulator)

[Debian Bug Tracking System]

Your message dated Tue, 27 Feb 2018 18:46:37 +0100
with message-id <1519753597.5023.0.ca...@debian.org>
and subject line Re: RFS: pokemmo-installer/1.4.6-1 -- Installer and Launcher 
for the PokeMMO emulator
has caused the Debian Bug report #890803,
regarding RFS: pokemmo-installer/1.4.6-1 -- Installer and Launcher for the 
PokeMMO emulator
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.)


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

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

  It builds those binary packages:

  pokemmo-installer - Installer and Launcher for the PokeMMO emulator

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

  https://mentors.debian.net/package/pokemmo-installer

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

  dget -x 
https://mentors.debian.net/debian/pool/contrib/p/pokemmo-installer/pokemmo-installer_1.4.6-1.dsc

  More information about PokeMMO Installer can be obtained from 
https://github.com/coringao/pokemmo-installer/wiki.

  Changes since the last upload:

  **changelog version: 1.4.6**
   * Screenshots for the game client now point to ~/Pictures
   * Fixed zenity window width
   * Fixed dependency for wget / kdialog
   * Debug mode no longer requires jps
   * Fixed an issue where a corrupt updater could return as valid

  pokemmo-installer (1.4.6-1) unstable; urgency=medium

  * New upstream release
  * debian/control:
+ Added dependent files (kdialog, wget)
  * d/upstream/metadata: updated information

  Regards,
   Carlos Donizete Froes [a.k.a coringao]
--- End Message ---
--- Begin Message ---
Uploaded, thanks for your contributions!

--  
tobi--- End Message ---

Re: Package EOL checklist

[Andrey Rahmatullin]

On Tue, Feb 27, 2018 at 09:32:52AM -0800, Joseph Herlant wrote:
> * libmrss has received no upstream commit over the last 10 years and
> the author confirmed that he won't touch it anymore. I'm fine
> continuing to maintain the packaging part it's a very easy one! :) I
> was just wondering if after a while I should have it out of Debian as
> it already has a low popcon but Andrey already answered to that.
Does it have revdeps or not? If it does, you can't just remove it. If it
doesn't, I'd say don't maintain libs which no one needs.

> * asciidoc has made its last upstream official release. It only
> supports python2. They made a new repo to make a python3 version but
> as they pushed most of their contributors to move to asciidoctor over
> time, it has not really seen any movement over the year it has
> existed. There are some well maintained alternative like asciidoctor
> or pandoc (depending on the task) that upstream recommends using so I
> thought it might be wise to start to ask the packages that depend on
> asciidoc to move to them before it starts to be a problem with the end
> of python2 in the distro, hence looking for a proper checklist to
> manage that without forgetting something.
Yes, this needs to be done.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Re: Package EOL checklist

[Joseph Herlant]

Hi guys,

Thanks for your answers.

> A project stopping development is not a reason to delete the package from
> the distro. Hence no docs.

My bad, I thought it was a best practice after a few years without
maintenance to do that. Sorry :\

> The first step when asking questions should always be to include
> details so that we know what we are talking about.

> What to do when a package is no longer maintained is highly dependent
> on which software it is and the particular situation around it.

Sorry for that. I had 2 very different use case:

* libmrss has received no upstream commit over the last 10 years and
the author confirmed that he won't touch it anymore. I'm fine
continuing to maintain the packaging part it's a very easy one! :) I
was just wondering if after a while I should have it out of Debian as
it already has a low popcon but Andrey already answered to that.

* asciidoc has made its last upstream official release. It only
supports python2. They made a new repo to make a python3 version but
as they pushed most of their contributors to move to asciidoctor over
time, it has not really seen any movement over the year it has
existed. There are some well maintained alternative like asciidoctor
or pandoc (depending on the task) that upstream recommends using so I
thought it might be wise to start to ask the packages that depend on
asciidoc to move to them before it starts to be a problem with the end
of python2 in the distro, hence looking for a proper checklist to
manage that without forgetting something.

Thanks for your help,
Joseph

Bug#891005: RFS: gdbm/1.14.1-5

[Gianfranco Costamagna]

Hello Ansgar


>This means building the package will give different results depending
>on dietlibc-dev installed or not?  That shouldn't happen...
>
>Please check via some other means that a build using dietlibc has been
>requested; don't do different things just because a package happens to
>be installed.
mmm the result is not a different library, but an additional static library put
in a non-standard directory, built with another glibc.
I think there is nothing to worry about :)

this is the path:
/usr/lib/*/diet/*/libgdbm.a


G.

Bug#890681: RFS: gexiv2/0.10.8-1 -- GObject-based wrapper around the Exiv2 library

[Jeremy Bicha]

On Tue, Feb 27, 2018 at 11:41 AM, Jason Crain  wrote:
> On Tue, Feb 27, 2018 at 11:27:54AM -0500, Jeremy Bicha wrote:
>> Oops, It looks like I have to be an Owner.
>
> I don't have the option to set you to Owner. Looks like Master is the
> highest I can set the permission to.

Ok, instead of transferring, I just re-imported the repo to
https://salsa.debian.org/debian/gexiv2

Please update the Vcs fields and I'll sponsor the update.

Also, it would be good for you to add a redirect at
https://salsa.debian.org/salsa/AliothRewriter

Thanks,
Jeremy Bicha

Bug#890681: RFS: gexiv2/0.10.8-1 -- GObject-based wrapper around the Exiv2 library

[Jason Crain]

On Tue, Feb 27, 2018 at 11:27:54AM -0500, Jeremy Bicha wrote:
> Oops, It looks like I have to be an Owner.

I don't have the option to set you to Owner. Looks like Master is the
highest I can set the permission to.

Bug#890681: RFS: gexiv2/0.10.8-1 -- GObject-based wrapper around the Exiv2 library

[Jason Crain]

On Tue, Feb 27, 2018 at 11:20:19AM -0500, Jeremy Bicha wrote:
> On Tue, Feb 27, 2018 at 11:12 AM, Jason Crain  wrote:
> > I would like it to use the Debian namespace but I can't move it myself.
> > Is there a way to transfer it?
> 
> Sure. Could you make me (jbicha) a Master on the project and I can transfer 
> it?

OK, I've added you.

Bug#890681: RFS: gexiv2/0.10.8-1 -- GObject-based wrapper around the Exiv2 library

[Jeremy Bicha]

On Tue, Feb 27, 2018 at 11:20 AM, Jeremy Bicha  wrote:
> On Tue, Feb 27, 2018 at 11:12 AM, Jason Crain  wrote:
>> I would like it to use the Debian namespace but I can't move it myself.
>> Is there a way to transfer it?
>
> Sure. Could you make me (jbicha) a Master on the project and I can transfer 
> it?

Oops, It looks like I have to be an Owner.

Thanks,
Jeremy Bicha

Bug#891643: RFS: inkscape-open-symbols/1.2.1-1

[Félix Sipma]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for the latest version of my package 
"inkscape-open-symbols".

Download with dget:

dget -x 
https://mentors.debian.net/debian/pool/main/i/inkscape-open-symbols/inkscape-open-symbols_1.2.1-2.dsc

Or build it with gbp:

gbp clone --pristine-tar
https://salsa.debian.org/felix-guest/inkscape-open-symbols.git
cd inkscape-open-symbols
gbp buildpackage

I'd appreciate if you could also give me upload rights for this package.

Thanks!


signature.asc
Description: PGP signature

Bug#890681: RFS: gexiv2/0.10.8-1 -- GObject-based wrapper around the Exiv2 library

[Jeremy Bicha]

On Tue, Feb 27, 2018 at 11:12 AM, Jason Crain  wrote:
> I would like it to use the Debian namespace but I can't move it myself.
> Is there a way to transfer it?

Sure. Could you make me (jbicha) a Master on the project and I can transfer it?

Thanks,
Jeremy Bicha

Bug#890681: RFS: gexiv2/0.10.8-1 -- GObject-based wrapper around the Exiv2 library

[Jason Crain]

On Mon, Feb 26, 2018 at 03:07:05PM -0500, Jeremy Bicha wrote:
> I see you updated your VCS from
> https://anonscm.debian.org/git/collab-maint/gexiv2.git
> to
> https://salsa.debian.org/jcrain-guest/gexiv2
> 
> Do you want this project to use the Debian namespace instead?
> https://salsa.debian.org/debian/
> 
> That would allow commit access by all DD's.
> 
> (I believe it's ok to answer no.)

I would like it to use the Debian namespace but I can't move it myself.
Is there a way to transfer it?

Bug#891005: RFS: gdbm/1.14.1-5

[Ansgar Burchardt]

On Tue, 2018-02-27 at 13:58 +0300, kact...@gnu.org wrote:
> Anyhow, if you want to enable, you can do something like this, to
> make
> > me and you happy, and then easily revert when new bugs are opened
> 
>  
>   HAVE_DIETLIBC=no 
>   ifeq ($(shell dpkg -s dietlibc-dev | grep -o installed), installed)
>   DIET_LIBDIR := $(shell diet -L gcc)
>   HAVE_DIETLIBC=yes 
>   endif
>   
>   ifeq ($(shell dpkg-vendor --derives-from Ubuntu && echo yes),yes)
>   HAVE_DIETLIBC=no 
>   endif

This means building the package will give different results depending
on dietlibc-dev installed or not?  That shouldn't happen...

Please check via some other means that a build using dietlibc has been
requested; don't do different things just because a package happens to
be installed.

Ansgar

Bug#891005: RFS: gdbm/1.14.1-5

[KAction]

Hello.

> Anyhow, if you want to enable, you can do something like this, to make
> me and you happy, and then easily revert when new bugs are opened
 
HAVE_DIETLIBC=no 
ifeq ($(shell dpkg -s dietlibc-dev | grep -o installed), installed)
DIET_LIBDIR := $(shell diet -L gcc)
HAVE_DIETLIBC=yes 
endif

ifeq ($(shell dpkg-vendor --derives-from Ubuntu && echo yes),yes)
HAVE_DIETLIBC=no 
endif

Thanks, I will add this snippet.

> If you want to enable it, please make sure it works :)

Okay. I will add some autopkgtests.

Bug#891478: marked as done (RFS: gnustep-back/0.26.2-3)

[Debian Bug Tracking System]

Your message dated Tue, 27 Feb 2018 12:28:05 +0200
with message-id <20180227102805.GA27988@localhost>
and subject line Re: Bug#891478: RFS: gnustep-back/0.26.2-3
has caused the Debian Bug report #891478,
regarding RFS: gnustep-back/0.26.2-3
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.)


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

 * Package name: gnustep-back
   Version : 0.26.2-3
   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-3.dsc

Or clone the Git reposotory at

  https://salsa.debian.org/gnustep-team/gnustep-back

Changes since the last upload:

  * debian/patches/xlib-fontconfig.patch: New, cherry-picked from
upstream; replace xlib-specific font enumerator with the shared
fontconfig one.  Fixes major slowness with approx 1/3 of the apps.
  * debian/patches/threaded-x.patch: New, cherry-picked from upstream;
enables drawing in secondary threads which is needed by
lynkeos.app/2.10.
  * debian/patches/no-font_cacher.patch: New, cherry-picked from upstream;
don't build font_cacher with the Xft-enabled xlib backend.
  * debian/patches/fix-spelling-error.patch: Fix another spelling error.
  * debian/patches/tools.patch: Remove; not really needed.
  * debian/patches/series: Update.
  * debian/rules: Remove dh_make boilerplate comments.
(override_dh_auto_build, override_dh_auto_install): Simplify recipes
by passing SERIAL_SUBDIRECTORIES=Source for cairo and art.
  * debian/font_cacher.1: Delete.
  * debian/gnustep-back-common.manpages: Delete; the gpbs manpage is
installed by the upstream build system.
  * debian/templates/gnustep-back-common.install.in: Add usr/share/man.
  * debian/README.Debian: Update info about font handling.
  * debian/copyright: Remove font_cacher.1 snippet.
  * debian/tests/control (Depends): Add file.
--- End Message ---
--- Begin Message ---
On Mon, Feb 26, 2018 at 01:06:28AM +0200, Yavor Doganov wrote:
>...
> Changes since the last upload:
> 
>   * debian/patches/xlib-fontconfig.patch: New, cherry-picked from
> upstream; replace xlib-specific font enumerator with the shared
> fontconfig one.  Fixes major slowness with approx 1/3 of the apps.
>   * debian/patches/threaded-x.patch: New, cherry-picked from upstream;
> enables drawing in secondary threads which is needed by
> lynkeos.app/2.10.
>   * debian/patches/no-font_cacher.patch: New, cherry-picked from upstream;
> don't build font_cacher with the Xft-enabled xlib backend.
>   * debian/patches/fix-spelling-error.patch: Fix another spelling error.
>   * debian/patches/tools.patch: Remove; not really needed.
>   * debian/patches/series: Update.
>   * debian/rules: Remove dh_make boilerplate comments.
> (override_dh_auto_build, override_dh_auto_install): Simplify recipes
> by passing SERIAL_SUBDIRECTORIES=Source for cairo and art.
>   * debian/font_cacher.1: Delete.
>   * debian/gnustep-back-common.manpages: Delete; the gpbs manpage is
> installed by the upstream build system.
>   * debian/templates/gnustep-back-common.install.in: Add usr/share/man.
>   * debian/README.Debian: Update info about font handling.
>   * debian/copyright: Remove font_cacher.1 snippet.
>   * debian/tests/control (Depends): Add file.

Thanks, uploaded.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. 

Bug#891132: marked as done (RFS: python-meshio/1.11.7-1)

[Debian Bug Tracking System]

Your message dated Tue, 27 Feb 2018 10:45:27 +0100
with message-id <20180227094527.ad4qssrl2szho...@villemot.name>
and subject line Re: RFS: python-meshio/1.11.7-1
has caused the Debian Bug report #891132,
regarding RFS: python-meshio/1.11.7-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.)


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

* Package name: python-meshio
  Version : 1.11.7-1
  Upstream Author : Nico Schlömer
* URL : https://github.com/nschloe/meshio
* License : Expat
  Section : python

It builds those binary packages:

  meshio-tools - command-line tools for meshio
  python3-meshio - library for reading and writing mesh data (Python 3)

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

  https://mentors.debian.net/package/python-meshio

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

  dget -x 
https://mentors.debian.net/debian/pool/main/p/python-meshio/python-meshio_1.11.7-1.dsc

Changes since the last upload:

  * New upstream version 1.11.7
  * Refresh the patch queue
  * Update the copyright years
  * Remove obsolete dependency on lxml
  * Drop the get-orig-source target
  * Point the VCS URIs to salsa.debian.org
  * Bump the debhelper version to 11
  * Bump the standards version to 4.1.3

Regards,
Ghislain Vaillant
--- End Message ---
--- Begin Message ---
Dear Ghislain,

On Thu, Feb 22, 2018 at 02:34:26PM +, Ghislain Vaillant wrote:

> I am looking for a sponsor for my package "python-meshio"
> 
> * Package name: python-meshio
>   Version : 1.11.7-1
>   Upstream Author : Nico Schlömer
> * URL : https://github.com/nschloe/meshio
> * License : Expat
>   Section : python

Uploaded, thanks for your contribution.

P.S.: no need to open an RFS bug against sponsorship-requests when asking for a
Debian Science Team package. A mail to debian-science@ with
"RFS: package/version" in the subject is enough.

Cheers,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


signature.asc
Description: PGP signature
--- End Message ---

Re: Package EOL checklist

[Paul Wise]

On Tue, Feb 27, 2018 at 2:34 PM, Joseph Herlant wrote:

> Did I miss a step?

The first step when asking questions should always be to include
details so that we know what we are talking about.

> I have a package that is not maintained by upstream anymore and I was trying
> to find some sort of checklist on how to best manage its end of life.

What to do when a package is no longer maintained is highly dependent
on which software it is and the particular situation around it.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise