Bug#920039: RFS: brightness-controller/2.2.3 [ITP]

[Archisman Panigrahi]

Hi,

Please note that the issues raised have been mostly dealt with. There is a
man page, the descriptions in the control file have been changed, the
copyright has been updated, and now usr/bin/brightness-controller calls an
interpreter.

Thanks,
Archisman

On Wed, Jan 23, 2019, 12:35 AM Archisman Panigrahi 
>
> -- Forwarded message -
> From: Archisman Panigrahi 
> Date: Tue, Jan 22, 2019 at 8:15 PM
> Subject: Re: Bug#920039: RFS: brightness-controller/2.2.3 [ITP]
> To: Adam Borowski 
>
>
> Hi,
>
> I have uploaded version 2.2.3-1.
> Now the /usr/bin calls the interpreter python to run
> /usr/share/brightness-controller/init.py.
>
> Thanks,
> Archisman
>
> On Tue, Jan 22, 2019 at 8:05 PM Adam Borowski  wrote:
>
>> On Tue, Jan 22, 2019 at 07:54:45PM +0530, Archisman Panigrahi wrote:
>> > On Tue, Jan 22, 2019 at 5:41 PM Adam Borowski 
>> wrote:
>> >
>> > > On Tue, Jan 22, 2019 at 04:57:20PM +0530, Archisman Panigrahi wrote:
>> > > > I am not sure about the native package issue. Has it got something
>> to
>> > > > do with /debian/source/format? I did not exactly understand what is
>> > > > the difference between native and quilt, so went for native. Any
>> > > > suggestion is welcome.
>> > >
>> > > The "native" format is adequate only when there's no separate
>> upstream (and
>> > > often not even then); in this case you are packaging Amit's software
>> that
>> > > has proper releases, tarballs, and all proper trappings.
>> > >
>> > > The packaging is supposed to be composed of two pieces:
>> > > * the upstream (.orig) tarball
>> > > * a packaging tarball, that includes the debian/ dir and a (possibly
>> empty)
>> > >   patch series
>> > >
>> > > This was somewhat different with the 1.0 format, but you don't want
>> it --
>> > > even if you (like me) despite quilt, the "3.0 (quilt)" format with a
>> single
>> > > patch is strictly better than 1.0.
>> >
>> > I am now using 3.0 (quilt). I have uploaded a new release (under the
>> same
>> > version number), please check.
>> > There is some lintian error
>> > "debian-changelog-version-requires-debian-revision". Is it due to the
>> fact
>> > that the debian/changelog in .orig.tar.gz
>>
>> Lintian has a nice set of explanations for its error messages, they get
>> enables by "-I".  These tend to be better than one-paragraph responses
>> reviewers like me reply with (even though an automated tool is not as good
>> at understanding the context).
>>
>> In this case, the version number should end in "-1".
>>
>> > init.py calls other python files in usr/share/brightness-controller/ui
>> and
>> > usr/share/brightness-controller/util, so I want init.py
>> > to be in usr/share/brightness-controller/ as well. Otherwise I will
>> need to
>> > import them across directories which I want to avoid.
>>
>> That's a Python specific question, I can't answer those.  I'm afraid that
>> I
>> need to pass you to other people on this mailing list.  If you happen to
>> have any Perl questions, though...
>>
>>
>> Meow!
>> --
>> ⢀⣴⠾⠻⢶⣦⠀
>> ⣾⠁⢠⠒⠀⣿⡁ Remember, the S in "IoT" stands for Security, while P stands
>> ⢿⡄⠘⠷⠚⠋⠀ for Privacy.
>> ⠈⠳⣄
>
>
>

Re: my first debian package

[Paul Wise]

On Sun, Feb 3, 2019 at 2:36 PM Robert Arkiletian wrote:

> The package used to be in debian before but has been orphaned.

When reintroducing packages, there are some extra steps to perform in
addition to the ones done when adding new packages:

https://www.debian.org/doc/manuals/developers-reference/ch05.html#reintroducing-pkgs

> The package is python-fltk

That is the binary package name, the source package name is pyfltk.
Removed packaging should be retrieved from the VCS for the package,
failing that, from the Debian snapshot archive. In this case the
repository was SVN on alioth, which is now archived, so you'll have to
get the python-modules tarball, unpack it and convert the pyfltk part
of the repository to git and continue from there. You can also skip
the conversion and just checkout the latest svn revision and continue
from there.

https://tracker.debian.org/pkg/pyfltk
https://alioth-archive.debian.org/svn/python-modules.tar.xz
https://snapshot.debian.org/package/pyfltk/

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

my first debian package

[Robert Arkiletian]

Hi I am trying to create a debian package and submit it before the
Buster Feb 12 soft freeze.

The package used to be in debian before but has been orphaned. The package is

 python-fltk

I am in the process of learning how to build the package. I found a
previous xenial ubuntu package here

https://packages.ubuntu.com/xenial/python-fltk

So I am basically copying the stuff in the debian directory and making
the required changes. However, the old package was a python 2 package.
The one I am building will be for python 3. So I have changed the name
to python3-fltk.

It's a python library that wraps the C++ fltk gui toolkit.  Am I too
late to submit this for Buster.  Any tips or advice is appreciated.

Bug#921204: RFS: austin/0.6.1-beta-1 [ITP]

[Gabriele]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

* Package name: austin
  Version : 0.6.1-beta-1
  Upstream Author : Gabriele N. Tornetta 
* URL : https://github.com/P403n1x87/austin
* License : GPLv3
  Section : devel

It builds those binary packages:

  austin - a frame stack sampler for CPython

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

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


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

  dget -x 
https://mentors.debian.net/debian/pool/main/a/austin/austin_0.6.1-beta-1.dsc

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

Changes since the last upload:

austin (0.6.1-beta-1) unstable; urgency=medium

  * Initial release (Closes: #918518)

 -- Gabriele N. Tornetta   Fri, 04 Jan 2019
23:13:40 +


  Regards,
   Gabriele N. Tornetta

Bug#920990: marked as done (RFS: rawdog/2.23-3)

[Debian Bug Tracking System]

Your message dated Sat, 2 Feb 2019 22:29:38 +0100
with message-id <20190202212938.bvlplqzeqdsng...@angband.pl>
and subject line Re: Bug#920990: RFS: rawdog/2.23-3
has caused the Debian Bug report #920990,
regarding RFS: rawdog/2.23-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.)


-- 
920990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920990
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 "rawdog". Vincent, CCed,
normally sponsors this package, but I think he's away at the moment and
I'm conscious that the freeze is approaching, so if someone else is able
to look at it then I'd very much appreciate it!

 * Package name: rawdog
   Version : 2.23-3 (or -2 -- see below)
   Upstream Author : Adam Sampson 
 * URL : http://offog.org/code/rawdog/
 * License : GPLv2+
   Section : web

It builds those binary packages:

  rawdog - RSS Aggregator Without Delusions Of Grandeur

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

Alternatively, one can download the package with dget using this
command:
  dget -x https://mentors.debian.net/debian/pool/main/r/rawdog/rawdog_2.23-3.dsc

Changes since the last upload:

rawdog (2.23-3) unstable; urgency=medium
  
  * Version bump to address missing .asc file in the archive.
 
 -- Adam Sampson   Thu, 31 Jan 2019 10:00:41 +

rawdog (2.23-2) unstable; urgency=medium

  * Include @ in autopkgtest dependencies. (Closes: #919580)

 -- Adam Sampson   Thu, 17 Jan 2019 16:18:03 +

The change in 2.23-2 is straightforward: it's a one-line fix to correct
a mistake I made when updating the autopkgtest dependencies that is
preventing migration to testing (see #919580).

Where it gets a bit more complicated: I tried to upload -2 to
mentors.debian.net, but this failed because the .asc file isn't in the
archive. From discussion with supp...@mentors.debian.net a few days ago:

> From: Mattia Rizzolo 
[...]
>> dpkg-source: error: cannot fstat file ./rawdog_2.23.orig.tar.gz.asc: No such 
>> file or directory
[...]
> 
> Your .dsc includes a reference to the .orig.tar.gz.asc file, but that
> one was not included in the upload 2.23-1 done in debian, therefore
> mentors can't access it.  It would usually be downloaded automatically
> if it was in the Debian archive, apparently your sponsor back then
> wasn't aware that he had to obtain the .asc as well.
> 
> You solutions here are two:
>  * build with -sa to force the inclusion of the full upstream sources
>(which means both the .orig.tar.gz and the .orig.tar.gz.asc) into the
>.changes
>  * remove the .asc from your working directory, that prevents
>dpkg-source from picking it up and referencing it in the .dsc.
> 
> I personally recommend the first, and then tell your sponsor to pick
> download the full sources again and re-upload with -sa so that he can
> add the .asc in the debian archive.

I've rebuilt -2 using -sa, but mentors doesn't see it as a new upload --
dput succeeds but I don't get any response back by email. So -3 is just
a version bump to get mentors to accept the package again; I'd be
equally happy with -2 being uploaded (the files for -2 are here:
https://stuff.offog.org/rawdog/ ).

Thanks very much,

-- 
Adam Sampson  
--- End Message ---
--- Begin Message ---
On Thu, Jan 31, 2019 at 10:45:04AM +, Adam Sampson wrote:
> I am looking for a sponsor for my package "rawdog". Vincent, CCed,
> normally sponsors this package, but I think he's away at the moment and
> I'm conscious that the freeze is approaching, so if someone else is able
> to look at it then I'd very much appreciate it!

The soft freeze affects only new packages -- but yeah, it's wise to not wait
till the last moment (someone whack me over the head about the last part,
please).

>  * Package name: rawdog
>Version : 2.23-3 (or -2 -- see below)

> Changes since the last upload:
> 
> rawdog (2.23-3) unstable; urgency=medium
>   
>   * Version bump to address missing .asc file in the archive.
>  
>  -- Adam Sampson   Thu, 31 Jan 2019 10:00:41 +
> 
> rawdog (2.23-2) unstable; urgency=medium
> 
>   * Include @ in autopkgtest dependencies. (Closes: #919580)
> 
>  -- Adam Sampson   Thu, 17 Jan 2019 16:18:03 +

Uploaded -2.

And it got accepted; I see .asc in incoming.  So this went well.

> The change in 2.23-2 is straightforward: it's a one-line fix 

Bug#921141: marked as done (RFS: dvdisaster/0.79.6-5)

[Debian Bug Tracking System]

Your message dated Sat, 2 Feb 2019 21:18:04 +0100
with message-id <20190202201804.xavp44c5ylvuf...@angband.pl>
and subject line Re: Bug#921141: RFS: dvdisaster/0.79.6-5
has caused the Debian Bug report #921141,
regarding RFS: dvdisaster/0.79.6-5
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.)


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

 * Package name: dvdisaster
   Version : 0.79.6-5
   Upstream Author : Carsten Gnörlich 
 * URL : 
https://web.archive.org/web/20180428070843/http://dvdisaster.net/
 * License : GPL-3+
   Section : otherosfs

  It builds these binary packages:

dvdisaster - data loss/scratch/aging protection for CD/DVD media
dvdisaster-doc - data loss/scratch/aging protection for CD/DVD media 
(documentation)

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

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


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

dget -ux 
https://mentors.debian.net/debian/pool/main/d/dvdisaster/dvdisaster_0.79.6-5.dsc

  Changes since the last upload:

dvdisaster (0.79.6-5) experimental; urgency=medium

  * Merge changes from 0.79.5-9.

 -- Carlos Maddela   Sat, 02 Feb 2019 16:05:29 +1100


  Regards,
   Carlos Maddela
--- End Message ---
--- Begin Message ---
On Sat, Feb 02, 2019 at 05:01:04PM +1100, Carlos Maddela wrote:
>  * Package name: dvdisaster
>Version : 0.79.6-5

>   Changes since the last upload:
> 
> dvdisaster (0.79.6-5) experimental; urgency=medium
> 
>   * Merge changes from 0.79.5-9.
> 
>  -- Carlos Maddela   Sat, 02 Feb 2019 16:05:29 +1100

✓

-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Remember, the S in "IoT" stands for Security, while P stands
⢿⡄⠘⠷⠚⠋⠀ for Privacy.
⠈⠳⣄--- End Message ---

Bug#921140: marked as done (RFS: dvdisaster/0.79.5-9)

[Debian Bug Tracking System]

Your message dated Sat, 2 Feb 2019 21:17:37 +0100
with message-id <20190202201737.z7fxjolztn26m...@angband.pl>
and subject line Re: Bug#921140: RFS: dvdisaster/0.79.5-9
has caused the Debian Bug report #921140,
regarding RFS: dvdisaster/0.79.5-9
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.)


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

 * Package name: dvdisaster
   Version : 0.79.5-9
   Upstream Author : Carsten Gnörlich 
 * URL : 
https://web.archive.org/web/20180428070843/http://dvdisaster.net/
 * License : GPL-3+
   Section : otherosfs

  It builds these binary packages:

dvdisaster - data loss/scratch/aging protection for CD/DVD media
dvdisaster-doc - data loss/scratch/aging protection for CD/DVD media 
(documentation)

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

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


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

dget -ux 
https://mentors.debian.net/debian/pool/main/d/dvdisaster/dvdisaster_0.79.5-9.dsc

  Changes since the last upload:

dvdisaster (0.79.5-9) unstable; urgency=medium

  * Make sure that the upstream changelog remains uncompressed so
that the application can display it.
  * Suggest to install dvdisaster-doc in error message, if the PDF manual
cannot be found.

 -- Carlos Maddela   Sat, 02 Feb 2019 15:20:23 +1100


  Regards,
   Carlos Maddela
--- End Message ---
--- Begin Message ---
On Sat, Feb 02, 2019 at 04:55:56PM +1100, Carlos Maddela wrote:
>  * Package name: dvdisaster
>Version : 0.79.5-9

>   Changes since the last upload:
> 
> dvdisaster (0.79.5-9) unstable; urgency=medium
> 
>   * Make sure that the upstream changelog remains uncompressed so
> that the application can display it.
>   * Suggest to install dvdisaster-doc in error message, if the PDF manual
> cannot be found.
> 
>  -- Carlos Maddela   Sat, 02 Feb 2019 15:20:23 +1100

✓

-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Remember, the S in "IoT" stands for Security, while P stands
⢿⡄⠘⠷⠚⠋⠀ for Privacy.
⠈⠳⣄--- End Message ---

Bug#921130: marked as done (RFS: php-elisp/1.21.0-1 [ITA])

[Debian Bug Tracking System]

Your message dated Sat, 02 Feb 2019 12:40:40 -0500
with message-id <87bm3u142v@curie.anarc.at>
and subject line Re: Bug#921130: RFS: php-elisp/1.21.0-1 [ITA]
has caused the Debian Bug report #921130,
regarding RFS: php-elisp/1.21.0-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.)


-- 
921130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal
Control: block 902633 by -1

Dear Mentors, Ola, and Moritz,

I am looking for a sponsor for my update/adoption of "php-elisp".

Package name: php-elisp
Version : 1.21.0-1
Upstream Author : USAMI Kenta  (current maintainer)
URL : https://github.com/emacs-php/php-mode
License : GPL-3+
Section : lisp

It builds these binary packages:

  elpa-php-mode - PHP Mode for GNU Emacs
  php-elisp - transitional package, php-elisp to elpa-php-mode

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

  https://mentors.debian.net/package/php-elisp

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

  dget -x 
https://mentors.debian.net/debian/pool/main/p/php-elisp/php-elisp_1.21.0-1.dsc

Alternatively, clone this git repo and use upstream git tag or uscan for the 
upstream source:

  git clone https://salsa.debian.org/emacsen-team/php-elisp.git

Changes since the last upload:

php-elisp (1.21.0-1) unstable; urgency=medium

  * Adopt package (Closes: #902633).
- Add Emacsen team VCs links.
- Set Maintainer to Debian Emacsen Team.
- Add Ola Lundqvist and myself to Uploaders.
  * New upstream release (Closes: #895743).
  * Elpafy php-elisp:
- Implicitly drops support for xemacs (Closes: #665314).
- Add dh-elpa to Build-Depends.
- Add new package: elpa-php-mode.
- Convert php-elisp to dummy transitional package.
- Rewrite debian/rules.
- Enable autopkgtests.
- Drop obsolete emacsen packaging directives: php-elisp.dirs,
  php-elisp.emacsen-install, php-elisp.emacsen-remove,
  php-elisp.emacsen-startup, php-elisp.emacsen-startup.new
  (Closes: #827827).
  * Declare compat level 11.
  * Switch to debhelper 11.
  * Declare Standards-Version: 4.3.0.
  * Update watchfile to v4, and update upstream project's location.
  * Suggest php and php-cli rather than php5 and php5-cli.
  * Add gbp.conf.
  * Add patch to disable php-project-root selftest.
  * Add upstream README.
  * Update Homepage, because php-mode has a new upstream maintainer.
The project's transfer of ownership is documented here:
https://github.com/emacs-php/php-mode/issues/387
  * Drop out-of-date php-elisp.README.Debian.  The upstream README contains
this information.
  * Add debian/NEWS to notify users of depreciated PHP 2 support, and show
how to restore the behaviour of past php-elisp releases.

 -- Nicholas D Steeves   Fri, 01 Feb 2019 14:43:45 -0700

php-elisp (1.13.5-3) unstable; urgency=medium

Regards,
Nicholas D Steeves
--- End Message ---
--- Begin Message ---
I uploaded the package, but I'll note some improvements that could be
done on it:

 1. newer versions of debhelper allow deduplicating information between
the control file and debian/compat. just remove the latter and
change the control dependency to "debhelper-compat (=11)" (or
12). see also:


https://nthykier.wordpress.com/2019/01/04/debhelper-compat-12-is-now-released/

 2. very minor, but i like to keep the "transitional package" phrase on
a separate line in package descriptions so it's more obvious to
someone looking at the description

 3. why was the php-root self-test disabled? what's the next step for
that patch? can it be sent upstream or will we have to carry this on
forever?

Thanks for your work! :)

A.

-- 
I'm no longer accepting the things I cannot change.
I'm changing the things I cannot accept.
- Angela Davis


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

Re: A problem with an upload

[Tong Sun]

On Sat, Feb 2, 2019 at 10:14 AM Mattia Rizzolo wrote:

> ffcvt is now in NEW: . . .

Thanks for your kind explanation Mattia, after which I found that
email in my trash bin, :-(

Thanks again everyone!

Re: A problem with an upload

[Mattia Rizzolo]

On Sat, Feb 02, 2019 at 10:04:57AM -0500, Tong Sun wrote:
> Would such such upload problem affected my ffcvt package as well? --
> as Pirate has done the upload for me, but so far I haven't received
> any response for it yet either.

ffcvt is now in NEW:
mattia@coccia ~ % xzgrep ffcvt /srv/ftp-master.debian.org/log/2019-01.xz
20190125163421|process-upload|dak|Processing changes 
file|ffcvt_1.3.1-1_amd64.changes
20190125163430|process-upload|dak|ACCEPT-TO-NEW|ffcvt_1.3.1-1_amd64.changes

~> https://ftp-master.debian.org/new/ffcvt_1.3.1-1.html

You should have received exactly one mail about it, and so did the ML:
https://alioth-lists.debian.net/pipermail/pkg-go-maintainers/Week-of-Mon-20190121/024742.html
https://alioth-lists.debian.net/pipermail/pkg-go-maintainers/Week-of-Mon-20190121/024743.html


If you did upload the package to mentors, indeed it most likely got
lost, but you shouldn't need to worry about it anymore, since you
already found a sponsor :)

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Re: A problem with an upload

[Andrey Rahmatullin]

On Sat, Feb 02, 2019 at 10:04:57AM -0500, Tong Sun wrote:
> > > I uploaded a new version 0.7.5-2 of package theme-d-gnome about five hours
> > > ago but so far I haven't received any response.
> >
> > I think the importer was stuck somewhere, at least the log stopped a
> > couple of days ago suddenly…
> >
> > That said, I could find no trace of your upload, so could you please try
> > uploading again?
> 
> Would such such upload problem affected my ffcvt package as well? --
> as Pirate has done the upload for me,
This thread discusses uploads to mentors.

> but so far I haven't received
> any response for it yet either.
> 
> Mattia would you take a look as well please, if you can find a trace
> of ffcvt upload -- ITP#902228, RFS#919745
ffcvt is in NEW. You should have received an email about that.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Re: A problem with an upload

[Tong Sun]

On Sat, Jan 26, 2019 at 10:24 AM Mattia Rizzolo wrote:
>
> On Sat, Jan 26, 2019 at 04:26:49PM +0200, Tommi Höynälänmaa wrote:
> > I uploaded a new version 0.7.5-2 of package theme-d-gnome about five hours
> > ago but so far I haven't received any response.
>
> I think the importer was stuck somewhere, at least the log stopped a
> couple of days ago suddenly…
>
> That said, I could find no trace of your upload, so could you please try
> uploading again?

Would such such upload problem affected my ffcvt package as well? --
as Pirate has done the upload for me, but so far I haven't received
any response for it yet either.

Mattia would you take a look as well please, if you can find a trace
of ffcvt upload -- ITP#902228, RFS#919745

Thanks!

Bug#920218: marked as done (RFS: webcamoid/8.5.0+dfsg-1)

[Debian Bug Tracking System]

Your message dated Sat, 2 Feb 2019 13:22:42 +
with message-id <20190202132242.f3lycaztye4yv...@master.debian.org>
and subject line no longer at mentors
has caused the Debian Bug report #920218,
regarding RFS: webcamoid/8.5.0+dfsg-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.)


-- 
920218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920218
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 "webcamoid".
  It is a upload to experimental. To test the new .symbols
  file, install via apt and run the software. My key is
  not in the archive yet.

  The new release closes two important bugs:

  https://github.com/webcamoid/webcamoid/issues/142
  https://github.com/webcamoid/webcamoid/issues/108



 * Package name: webcamoid
   Version : 8.5.0+dfsg-1
   Upstream Author : Gonzalo Exequiel Pedone 
 * URL : https://github.com/webcamoid/webcamoid
 * License : GNU General Public License v3.0
   Section : video

  It builds those binary packages:

akqml - full featured webcam capture application - qml module
libavkys-dev - full featured webcam capture application - dev
libavkys8  - full featured webcam capture application - library
webcamoid  - full featured webcam capture application
webcamoid-data - icons and locale files for webcamoid
webcamoid-plugins - full featured webcam capture application - plugins

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

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


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

dget -x 
https://mentors.debian.net/debian/pool/main/w/webcamoid/webcamoid_8.5.0+dfsg-1.dsc

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

  Changes since the last upload:

  * New upstream version 8.5.0+dfsg
  * debian/control:
  - Update Build-Depends and Webcamoid pkg Depends
  - Bump Standards-Version from 4.2.1 to 4.3.0
  * debian/copyright:
  - Update year for myself and upstream
  * debian/clean:
  - Remove libAkQml.so file
  * debian/gbp.conf:
  - Remove sign-tags
  * debian/watch:
  - Add repacksuffix,repack,compression to opts
  - dversionmangle: remove number 1 from +dfsg
  * debian/patches:
  - Remove upstream patches
  - Add patch for .desktop file
  * Add new .symbols file
  * debian/webcamoid-data.install:
  - StandAlone does not have .json and effects.xml files



Regards,
Herbert
--- End Message ---
--- Begin Message ---
--- End Message ---

Bug#910004: RFS: apache-opennlp/1.9.0-1 [ITP] -- machine learning based toolkit for the processing of natural language text

[Andrius Merkys]

Hi Mo Zhou,

thanks a lot for the interest in my RFS. At first glance the FTBFS issue
seems to be related to #920020. I will investigate it further.

Best wishes,
Andrius

[#920020] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920020

On Sat, 2 Feb 2019, 10:30 Mo Zhou  control: tags -1 +moreinfo
>
> Hi Andrius,
>
> Thank you for the effort on apache-opennlp packaging. However it failed
> to build (I cannot help you diagnose the failure because I know nothing
> about Java):
>
>
> http://debomatic-amd64.debian.net/distribution#unstable/apache-opennlp/1.9.0-1/buildlog
>
> BTW, 1.9.1 release is available.
>
>

Bug#910004: RFS: apache-opennlp/1.9.0-1 [ITP] -- machine learning based toolkit for the processing of natural language text

[Mo Zhou]

control: tags -1 +moreinfo

Hi Andrius,

Thank you for the effort on apache-opennlp packaging. However it failed
to build (I cannot help you diagnose the failure because I know nothing
about Java):

http://debomatic-amd64.debian.net/distribution#unstable/apache-opennlp/1.9.0-1/buildlog

BTW, 1.9.1 release is available.

Bug#919590: RFS: openliberty/18.0.0.4 [ITP]

[Mo Zhou]

control: tags -1 +moreinfo

Hi Michael,

As much as I'd appreciate your effort trying to create a package for
Debian, but I have to say the packaging is unacceptable.

> https://mentors.debian.net/debian/pool/main/o/openliberty/openliberty_18.0.0.4.dsc

The present packaging might be fine to third party deb package
repositories, but it doesn't meet Debian's requirements and there are
too many policy[1] violations. 

For example, I caught many unacceptable lines in d/rules:

```
 25 mkdir -p 
/home/travis/build/was-lighthouse/openliberty-rpmdeb/debuild/openliberty/debian/openliberty/opt/openliberty
 26 tar -zxf ../openliberty-*.tar.gz -C 
/home/travis/build/was-lighthouse/openliberty-rpmdeb/debuild/openliberty/debian/openliberty/opt/openliberty
```

Long description is missing. Short description far exceeds 80 chars.
source/format being "3.0 (native)" is also questionable.

Please refer the documentations https://www.debian.org/doc/ for
guidance on creating packages in good shape. Thanks.

[1] https://www.debian.org/doc/devel-manuals#policy