Re: Package EOL checklist

[Andrey Rahmatullin]

On Mon, Feb 26, 2018 at 10:34:00PM -0800, Joseph Herlant wrote:
> Hi guys,
> 
> 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.
> 
> I can't find it in the documentation. Is it somewhere I missed?
A project stopping development is not a reason to delete the package from
the distro. Hence no docs.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Package EOL checklist

[Joseph Herlant]

Hi guys,

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.

I can't find it in the documentation. Is it somewhere I missed?

Here is what I had in mind:
1. Confirm with upstream that they dropped the dev and maintenance.
2. Confirm that there's no fork with people actively working on taking over
the maintenance.
3. Open bugs on all depending packaged (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, 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. Maybe put a note in debian/NEWS when you start this whole
process so that people can identify the repository more easily?

Did I miss a step? Is the process correct?

Thanks for your help,
Joseph

Bug#887403: Acknowledgement (RFS: budgie-extras/0.4.0-1)

[foss.freedom]

Hi Herbert,

  no I wasn't aware of that lintian - I ran lintian -i -I --pedantic
on my latest unstable but it didn't highlight that.  Odd.

However I have now corrected that in debian/rules.  I have taken also
the opportunity to refresh the source & build with the very latest
fixes made by the team made in the last month.

https://mentors.debian.net/debian/pool/main/b/budgie-extras/budgie-extras_0.4.2-1.dsc

The changelog has been adjusted slightly to reflect this
DEB_BUILD_OPTIONS addition:

  * New upstream release
  * Packaging Changes:
- debian/control and debian/compat: update to v11
- debian/control: Bump Standards-Version - no changes required
- debian/control: new binary packages budgie-rotation-lock-applet,
  budgie-clockworks-applet,
  budgie-dropby-applet
- debian/copyright: 2018 year updates
- debian/rules remove ninja make rules since debhelper can deal
  with meson builds
- debian/rules check DEB_BUILD_OPTIONS for autotest
- remove not needed debian/files
- signing key; move and rename to debian/upstream


thanks

David

On 25 February 2018 at 14:46, Herbert Fortes  wrote:
> Em 27-01-2018 14:06, foss.freedom escreveu:
>> The team has completed a minor release with lots of useful bug-fixes.
>>
>> These are summarised in the source ChangeLog file
>>
>> dget -x 
>> https://mentors.debian.net/debian/pool/main/b/budgie-extras/budgie-extras_0.4.1-1.dsc
>>
>> The debian/changelog I have just changed the package version info -
>> everything else is the same as originally detailed.
>>
>>
>
> Are you aware about this lintian?
>
>
> I: override_dh_auto_test-does-not-check-DEB_BUILD_OPTIONS
> N:
> N:   The debian/rules file for this package has an override_dh_auto_test
> N:   target that does not appear to check DEB_BUILD_OPTIONS against
> N:   nocheck.
> N:
> N:   As this check is not automatically performed by debhelper(1), the
> N:   specified testsuite is run regardless of another maintainer using the
> N:   nocheck build profile.
> N:
> N:   Please add a check such as:
> N:
> N:override_dh_auto_test:
> N:ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
> N:./run-upstream-testsuite
> N:endif
>
> It is a:
>
> N:   Severity: wishlist, Certainty: wild-guess
>
> Let me know so I can do the upload.
>
>
>
> Regards,
> Herbert

Bug#891430: marked as done (RFS: proxmoxer/1.0.2-1 [ITP])

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2018 22:21:08 +
with message-id 
and subject line closing RFS: proxmoxer/1.0.2-1 [ITP]
has caused the Debian Bug report #891430,
regarding RFS: proxmoxer/1.0.2-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.)


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

* Package name: proxmoxer
  Version : 1.0.2-1
  Upstream Author : Oleg Butovich 
* URL : https://github.com/swayf/proxmoxer
* License : MIT
  Section : python

t builds those binary packages:

  python-proxmoxer - Python Wrapper for the Proxmox 2.x API (HTTP and SSH) 
(Python 2)
ython3-proxmoxer - Python Wrapper for the Proxmox 2.x API (HTTP and SSH) 
(Python 3)

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

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


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

  dget -x 
https://mentors.debian.net/debian/pool/main/p/proxmoxer/proxmoxer_1.0.2-1.dsc

And the git repository is on 
https://salsa.debian.org/python-team/modules/proxmoxer :

  gbp clone g...@salsa.debian.org:python-team/modules/proxmoxer.git

This is a new package for debian, with ITP at http://bugs.debian.org/883103

As I wrote on the ITP, I'm also packaging the python2 version of this module as
it is used by ansible (until ansible itself will move on to python3)

I intend to maintain this package under the Debian Python Modules Team (DPMT)
and I'm a DM.

Regards,
 Elena Grandi
--- End Message ---
--- Begin Message ---
Package proxmoxer version 1.0.2-1 is in NEW now,
and the package at mentors is not newer (2018-02-25) than the package in NEW 
(2018-02-26),
so there is currently no package to sponsor.

https://ftp-master.debian.org/new/proxmoxer_1.0.2-1.html
https://mentors.debian.net/package/proxmoxer

If for some reason you need to replace the package in NEW,
then you can upload an updated package to mentors
and feel free to reopen this RFS 891430 or open a new RFS.--- End Message ---

Bug#891182: RFS: ssh-tools/1.4-1

[Sven Wick]

Ah well, after some fiddling lintian stopped complaining...


On 02/26/2018 08:20 PM, Andrey Rahmatullin wrote:

On Mon, Feb 26, 2018 at 07:23:35PM +0100, Sven Wick wrote:

Yeah, I did. But when I tried to get rid of the warnings
it complained about the whole control file.

Didn't find this "empty paragraph"

Description: collection of various tools using ssh
  .


and how to get rid of the "unindented list" warning

Have you read the tag description? You aldo need to read
https://www.debian.org/doc/debian-policy/#s-f-description

Bug#890878: RFS: company-irony

[Sean Whitton]

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


signature.asc
Description: PGP signature

Bug#890878: RFS: company-irony

[Nicholas D Steeves]

Hi Alberto,

On Mon, Feb 26, 2018 at 04:30:02PM +0100, Alberto Luaces wrote:
> Sean Whitton writes:
> 
> > Hello,
> >
> > On Wed, Feb 21 2018, Alberto Luaces wrote:
> >
> >> Thanks, Sean.  It is now located at
> >>
> >> https://salsa.debian.org/aluaces-guest/company-irony
> >>
> >> I guess someone else has to clone it under the team project folders,
> >> so I created that personal repository first.
> >
> > You should be able to do it yourself... are you saying that you were
> > unable to create a repo under emacsen-team?  I just bumped your
> > permission level.
> >
> 
> Thanks for that.  Yes, I think salsa's default permissions for non-DDs
> are much more stricter than Alioth were.  Nevertheless, I have been able
> to create and populate the repository under the Team's group.
> 
> >
> > I don't want to upload the package with the wrong Vcs-* headers, so
> > let's get this fixed first.
> 
> I have refreshed those fields.  I have not still refreshed the changelog
> date in order to wait for more potential changes.
> 

Thank you for packaging company-irony!  I'd be happy to review your
packaging too; although, I can't sponsor the upload.  Please ping me
if you haven't received an update in the next 48h. ;-)

Cheers,
Nicholas


signature.asc
Description: PGP signature

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

[Jeremy Bicha]

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.)

Thanks,
Jeremy Bicha

Bug#891182: RFS: ssh-tools/1.4-1

[Andrey Rahmatullin]

On Mon, Feb 26, 2018 at 07:23:35PM +0100, Sven Wick wrote:
> Yeah, I did. But when I tried to get rid of the warnings
> it complained about the whole control file.
> 
> Didn't find this "empty paragraph" 
Description: collection of various tools using ssh
 .

> and how to get rid of the "unindented list" warning
Have you read the tag description? You aldo need to read
https://www.debian.org/doc/debian-policy/#s-f-description

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#891182: RFS: ssh-tools/1.4-1

[Sven Wick]

Yeah, I did. But when I tried to get rid of the warnings
it complained about the whole control file.

Didn't find this "empty paragraph" and how to get rid
of the "unindented list" warning


On 02/26/2018 06:25 PM, Andrey Rahmatullin wrote:

On Mon, Feb 26, 2018 at 12:01:18AM +0100, Sven Wick wrote:

OK. It's done and uploaded to mentors

Have you run lintian on it? Or at least looked at the mentors page?

Bug#877331: sponsorship-requests: nix/1.1.15 (ITP 877019) -- Purely functional package manager

[Andrey Rahmatullin]

On Sun, Feb 25, 2018 at 11:14:37PM +0100, Kai Harries wrote:
> > The source package you've uploaded is broken, as .dsc mentions
> > nix_1.11.15-2~a1.debian.tar.xz.
> 
> My fault, GitHub doesn't like '~' in file names so I have uploaded
> the files with an '.' instead of '~'. I have uploaded a new version [1]
> that does not use the '~' in the version.
Thank you.
Please use verbose build output.
Please switch to the current debhelper compat level.
The Vcs-* tags don't point to the packaging repo.
You hardcode "perl5/site_perl/5.26.1/x86_64-linux-gnu-thread-multi" in
d/rules.
Does the package really need to include development files?
The source ships embedded code copies of at least bsdiff and parts of
boost. It even builds and installs bsdiff and bspatch binaries. And the
copyrights and licenses of this source are not listed in d/copyright.
Putting the whole LGPL in d/copyright is wrong. And it says "LGPL-2.1"
while the manual says "LGPL-2.1+".
src/libexpr/parser-tab.* and doc/manual/style.css licenses are not
mentioned in d.copyright. 

> > The version, 1.11.15-2~a1, is wrong for an initial Debian upload.
> 
> I have used 1.11.16-1 now. But I am not 100% sure that this is an
> correct version number for the initial upload!?
It is, why not?

> > Also, the version in the RFS subject is not the package version.
> 
> My fault I missed a number in my RFS. What should I do to fix
> this. Create a new RFS? (BTW I have now taken a newer upstream version).
You should retitle this one.

> > You need to run lintian from unstable on your package and fix main issues
> > before asking for sponsorship.
> 
> Only two warnings left:
> 
>   W: nix: manpage-has-errors-from-man usr/share/man/man1/nix-store.1.gz 1235: 
> warning [p 13, 9.7i]: can't break line
>   W: nix: binary-without-manpage usr/bin/nix-generate-patches
That's definitely not true.

E: nix changes: unreleased-changes
W: nix source: debhelper-tools-from-autotools-dev-are-deprecated dh ... --with 
autotools_dev (line 18)
P: nix source: package-uses-old-debhelper-compat-version 9
W: nix source: build-depends-on-obsolete-package build-depends: dh-systemd => 
use debhelper (>= 9.20160709)
I: nix source: out-of-date-standards-version 3.9.8 (released 2016-04-06) 
(current is 4.1.3)
I: nix source: testsuite-autopkgtest-missing
X: nix source: upstream-metadata-file-is-missing
P: nix source: debian-watch-does-not-check-gpg-signature
I: nix: hardening-no-fortify-functions usr/bin/nix-daemon
I: nix: hardening-no-fortify-functions usr/bin/nix-instantiate
I: nix: hardening-no-fortify-functions usr/bin/nix-store
I: nix: hardening-no-fortify-functions ... use --no-tag-display-limit to see 
all (or pipe to a file/program)
I: nix: spelling-error-in-binary usr/bin/nix-collect-garbage refered referred
I: nix: hardening-no-bindnow usr/bin/nix-collect-garbage
I: nix: spelling-error-in-binary usr/bin/nix-daemon refered referred
I: nix: hardening-no-bindnow usr/bin/nix-daemon
I: nix: spelling-error-in-binary usr/bin/nix-env refered referred
I: nix: hardening-no-bindnow usr/bin/nix-env
I: nix: spelling-error-in-binary ... use --no-tag-display-limit to see all (or 
pipe to a file/program)
I: nix: hardening-no-bindnow ... use --no-tag-display-limit to see all (or pipe 
to a file/program)
P: nix: no-upstream-changelog
I: nix: spelling-error-in-copyright GNU Library Public License GNU Library 
General Public License
W: nix: package-installs-deprecated-upstart-configuration 
etc/init/nix-daemon.conf
W: nix: pkg-config-unavailable-for-cross-compilation 
usr/lib/pkgconfig/nix-expr.pc
W: nix: pkg-config-unavailable-for-cross-compilation 
usr/lib/pkgconfig/nix-main.pc
W: nix: pkg-config-unavailable-for-cross-compilation 
usr/lib/pkgconfig/nix-store.pc
W: nix: manpage-has-errors-from-man usr/share/man/man1/nix-store.1.gz 1235: 
warning [p 13, 9.7i]: can't break line
W: nix: binary-without-manpage usr/bin/nix-generate-patches
I: nix: possible-documentation-but-no-doc-base-registration
X: nix: shlib-calls-exit usr/lib/nix/libnixexpr.so
X: nix: shlib-calls-exit usr/lib/nix/libnixmain.so
X: nix: shlib-calls-exit usr/lib/nix/libnixstore.so
I: nix: systemd-service-file-missing-documentation-key 
lib/systemd/system/nix-daemon.service
I: nix: systemd-service-file-missing-install-key 
lib/systemd/system/nix-daemon.service


-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#891182: RFS: ssh-tools/1.4-1

[Andrey Rahmatullin]

On Mon, Feb 26, 2018 at 12:01:18AM +0100, Sven Wick wrote:
> OK. It's done and uploaded to mentors
Have you run lintian on it? Or at least looked at the mentors page?

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#891005: RFS: gdbm/1.14.1-5

[Gianfranco Costamagna]

Hello 



>With all my respect, I am very relucant to solve problems of Ubuntu at
>expense of Debian output. What exactly is wrong, Debian-wise, in package
>we are discussing, apart the need to specify long list of architectures,
>so I could fix it?


this is not an "Ubuntu" problem, but something that even Debian
had (remember, 4 bugs opened in less than a week).
So I would say, I'm reluctant in re-enabling something that did cause a lot
of troubles to Debian folks :)

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


>Short answer: >  because you need it to link program, using gdbm, with diet 
>libc,
>  resulting small static executable.
>Full answer: 
>  because I believe Debian should provide not only libraries for
>  build-dependencies of something in /bin, but also libraries for
>  developers to develop with.
>
>  I did some search, and seems this is already happening. We have a lot
>  of leaf libraries (mostly perl and java), for example: 
>- libxmlenc-java 
>- libwx-scintilla-perl

>

I can understand the reasons for having it, but the question is:
does it work?
How can I run some simple make commands to see if everything works?
because people on the bug reports tried and they said it wasn't working.

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

>Or maybe we just need Guix/Nix?


I don't get this :)



cheers!

G.

Bug#890878: RFS: company-irony

[Alberto Luaces]

Sean Whitton writes:

> Hello,
>
> On Wed, Feb 21 2018, Alberto Luaces wrote:
>
>> Thanks, Sean.  It is now located at
>>
>> https://salsa.debian.org/aluaces-guest/company-irony
>>
>> I guess someone else has to clone it under the team project folders,
>> so I created that personal repository first.
>
> You should be able to do it yourself... are you saying that you were
> unable to create a repo under emacsen-team?  I just bumped your
> permission level.
>

Thanks for that.  Yes, I think salsa's default permissions for non-DDs
are much more stricter than Alioth were.  Nevertheless, I have been able
to create and populate the repository under the Team's group.

>
> I don't want to upload the package with the wrong Vcs-* headers, so
> let's get this fixed first.

I have refreshed those fields.  I have not still refreshed the changelog
date in order to wait for more potential changes.

Bug#891429: marked as done (RFS: urlwatch/2.8-1)

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2018 10:20:24 +
with message-id 
and subject line closing RFS: urlwatch/2.8-1
has caused the Debian Bug report #891429,
regarding RFS: urlwatch/2.8-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.)


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

 * Package name: urlwatch
   Version : 2.8-1
   Upstream Author : Thomas Perl
 * URL : https://thp.io/2008/urlwatch/
 * License : BSD-3-clause
   Section : web

It builds those binary packages:
  urlwatch   - tool for monitoring webpages for updates

To access further information about this package, please visit the
following URL:
  https://mentors.debian.net/package/urlwatch

Alternatively, one can download the package with dget using this command:
  dget -x 
https://mentors.debian.net/debian/pool/main/u/urlwatch/urlwatch_2.8-1.dsc

More information about urlwatch can be obtained from
https://github.com/thp/urlwatch.

Changes since the last upload:

urlwatch (2.8-1) unstable; urgency=medium

  * New upstream release
  * Changed copyright year
  * Switch upstream site and mail to tph.io instead of tphinfo.com
  * Wrapped debian/watch
  * Removed patch included in upstream
  * Patched to fallback on editor (Closes: #890835)

Regards,

Maxime Werlen
--- End Message ---
--- Begin Message ---
Package urlwatch version 2.8-1 is in unstable now.
https://packages.qa.debian.org/urlwatch--- End Message ---

Bug#891428: marked as done (RFS: minidb/2.0.2-2)

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2018 10:20:25 +
with message-id 
and subject line closing RFS: minidb/2.0.2-2
has caused the Debian Bug report #891428,
regarding RFS: minidb/2.0.2-2
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.)


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

* Package name: minidb
  Version : 2.0.2-2
  Upstream Author : Thomas Perl 
* URL : https://thp.io/2010/minidb/
* License : ISC
  Section : libs

It builds those binary packages:
  python3-minidb - simple SQLite3-based store for Python objects

To access further information about this package, please visit the
following URL:
  https://mentors.debian.net/package/minidb

Alternatively, one can download the package with dget using this command:
  dget -x 
https://mentors.debian.net/debian/pool/main/m/minidb/minidb_2.0.2-2.dsc

More information about minidb can be obtained from
https://github.com/thp/minidb.

Changes since the last upload:

minidb (2.0.2-2) unstable; urgency=low

  * Updated extended description from thp.io site
  * Adding missing blank line in ISC license
  * Wrapped d/watch file
  * Update debhelper version in control file to match d/compat

Regards,
Maxime Werlen
--- End Message ---
--- Begin Message ---
Package minidb version 2.0.2-2 is in unstable now.
https://packages.qa.debian.org/minidb--- End Message ---