Re: more recent version with python3 support

[Herbert Fortes]

Hi Gianfranco,

> TLTR, Tiago seems to be *completely* correct here, you didn't state the 
> package name,
> so you might want to try to grasp a solution before reading this email.
> 
> But *please* read it eventually, because the Python3 package is probably 
> broken
> 
> 
> > I have packaged a Python library which has support for both Python 2
> > and 3 and didn't needed "debian/*.install" files[1]. It has two binary
> > packages, "python-*" and "python3-*", under "debian/control"[2] and
> > "PYBUILD_NAME" environment variable defined in "debian/rules"[3]
> > (which is required[4] by Pybuild).
> > 
> > Regards,
> > Tiago.
> 
> 
> I did check the package for pybuild, and it seems working/building correctly 
> with it.
> I don't want to share a patch with you, but the changes are
> 
> -Build-Depends: debhelper (>= 9), dh-python, python-all, python-setuptools
> 
> +Build-Depends: debhelper (>= 9), dh-python, python-all, python-setuptools, 
> python3-all, python3-setuptools
> 
> new package
> +Package: python3-django-notification
> +Architecture: all
> +Depends: ${misc:Depends}, ${python3:Depends}
> 
> 
> 
> (note the python3:Depends)
> 
> and changes on rules:
> -%:
> -   dh $@ --with python2
> +export PYBUILD_NAME=django-notification
> 
> -override_dh_clean:
> -   rm -f django_notification.egg-info/SOURCES.txt
> -   rm -f django_notification.egg-info/PKG-INFO
> -   dh_clean 
> +%:
> +   dh $@ --with python2,python3 --buildsystem=pybuild
> 
> 
> 
> and now lets see the build:
> Copying django_notification.egg-info to 
> /build/django-notification-0.1.5/debian/python3-django-notification/usr/lib/python3.5/dist-packages/django_notification-0.1.5.egg-info
> Skipping SOURCES.txt
> running install_scripts
> File "/usr/lib/python3.5/dist-packages/notification/models.py", line 193
> print "Updated %s NoticeType" % label
> ^
> SyntaxError: Missing parentheses in call to 'print'
> 
> 
> oops, the package isn't really Python3 ready, so I suggest you
> to try 2to3, or carefully patch it to be Python3 compatible.
> 
> Hope this helps,
> 
> and sorry if I gave you an unwanted solution :)
> 

Hey, thanks for spent some time with the package!

But I am working on 1.2.0. I belive you got the last
version from git repository, 0.1.5.



regards,
-- 
Herbert Parentes Fortes Neto (hpfn)

signature.asc
Description: This is a digitally signed message part

Re: more recent version with python3 support

[Herbert Fortes]

Hi people,

I am doing a QA (do not need a sponsor) and
packaging a more recent version of the app.

This new version has support for python3, as
said in setup.py, so I created debian/*.install
files and edited debian/control and debian/rules.

cat debian/rules:

#!/usr/bin/make -f

%:
dh $@ --with python2,python3 --buildsystem=pybuild

override_dh_auto_test:

override_dh_clean:
rm -f django_notification.egg-info/SOURCES.txt
#rm -f django_notification.egg-info/PKG-INFO
rm -f django_notification.egg-info/requires.txt
dh_clean

Two packages are been created:

 - Package: python-django-notification
 - Package: python3-django-notification

cowbuilder is ok.

I do not see errors during the build and there
is no differences between the .deb packages. Am 
I missing something ? First time doing this.



regards,
--
Herbert Parentes Fortes Neto (hpfn)

signature.asc
Description: This is a digitally signed message part

Re: more recent version with python3 support

[Herbert Fortes]

> 
> I have some nitpicks :)
> "usign" <-- typo
> 
> "python" "python3" should be used with upper case "P"
> 
> I did a debdiff between unstable and mentors, and I see many print that 
> aren't Python3 ready
> 
> (not really sure if and when are used in the code)
> -... print 'somefile', 'is locked already.'
> +... print "somefile", "is locked already."
> 
> 
> $ python -c 'print "somefile", "is locked already."'
> somefile is locked already.
> 
> $ python3 -c 'print "somefile", "is locked already."'
> File "", line 1
> print "somefile", "is locked already."
> ^
> SyntaxError: Missing parentheses in call to 'print'
> 
> 
> so, even in case that this is just documentation, I think it would be nice to 
> ask upstream
> to convert it in a common syntax between Python2 and Python3
> 
> thanks for the nice work!
> (and sorry for nitpicking on a fellow DD)

Yes, is between """.  And the upstream did not edit it to Python3:

$ less notification/lockfile.py

 """
lockfile.py - Platform-independent advisory file locks.

Requires Python 2.5 unless you apply 2.4.diff
Locking is done on a per-thread basis instead of a per-process basis.

Usage:

>>> lock = FileLock("somefile")
>>> try:
... lock.acquire()
... except AlreadyLocked:
... print "somefile", "is locked already."
[...]
"""

I did a 'dcut cancel' and will do a closer look
as you did.



regards,
-- Herbert Parentes Fortes Neto (hpfn)

signature.asc
Description: This is a digitally signed message part

Re: more recent version with python3 support

[Herbert Fortes]

Hi,

> BTW I see it in deferred/1, but you didn't push on git... :)
> if you want to do it, I can see the changes (not that I'm a powerful
> Python man, but I like to learn from other folks ;) )
> 

Good. I just did the upload to mentors:

https://mentors.debian.net/package/django-notification
https://mentors.debian.net/debian/pool/main/d/django-notification/django-notification_1.2.0-1.dsc



regards,
-- 
Herbert Parentes Fortes Neto (hpfn)

signature.asc
Description: This is a digitally signed message part

same upstream version but different orig.tar.gz

[Herbert Fortes]

Hi,

I am packaging a new version of webcamoid.
This new version has some files with Ms-LPL
license(nonfree).

First I removed libAvKys/Plugins/VirtualCamera/
directory. Generated a new .symbols file and
uploaded to experimental. Then I tested the
software. It did not run. An email to the upstream
was sent.

Only libAvKys/Plugins/VirtualCamera/src/dshow has
to be removed. So I did a new Debian revision after
the +dfsg.orig.tar.gz file be replaced.

I just did a 'debdiff' to check the differences
between the Debian revisions, and of course, the
output is:

dpkg-source: error: file webcamoid/webcamoid_7.2.0+dfsg.orig.tar.gz has 
size 3160998 instead of expected 3148208
Use of uninitialized value $from in stat at 
/usr/share/perl/5.22/File/Copy.pm line 211.
Use of uninitialized value $from in string eq at 
/usr/share/perl/5.22/File/Copy.pm line 64.
Use of uninitialized value $from in -d at 
/usr/share/perl/5.22/File/Copy.pm line 96.
Use of uninitialized value $_[0] in substitution (s///) at 
/usr/share/perl/5.22/File/Basename.pm line 180.
fileparse(): need a valid pathname at /usr/share/perl/5.22/File/Copy.pm 
line 51.


Is this a big problem ? (replace a +dfsg.orig.tar.gz file
with the same upstream version)



regards,
--
Herbert Parentes Fortes Neto (hpfn)


signature.asc
Description: PGP signature

Re: same upstream version but different orig.tar.gz

[Herbert Fortes]

Hi,

> 
> You can work around this locally by rewriting your .changes files; the
> changestool utility in the reprepro packages can help with that.  But
> you won't be able to upload different files with the same name.  The
> usual solution is adding a numeric part to the version after +dfsg, like
> +dfsg1, and incrementing that on each change to the tarball.

The version in experimental[0] now is 7.2.0+dfsg-2.

https://buildd.debian.org/status/package.php?p=webcamoid=experimental

The next upload will be 7.2.0+dfsg1-1 ?



regards,
-- 
Herbert Parentes Fortes Neto (hpfn)

signature.asc
Description: This is a digitally signed message part

Re: same upstream version but different orig.tar.gz

[Herbert Fortes]

Hi Ferenc Wágner,


> > > You can work around this locally by rewriting your .changes files; the
> > > changestool utility in the reprepro packages can help with that.  But
> > > you won't be able to upload different files with the same name.  The
> > > usual solution is adding a numeric part to the version after +dfsg, like
> > > +dfsg1, and incrementing that on each change to the tarball.
> > 
> > The version in experimental[0] now is 7.2.0+dfsg-2.
> > 
> > https://buildd.debian.org/status/package.php?p=webcamoid=experimental
> > 
> > The next upload will be 7.2.0+dfsg1-1 ?
> 
> $ dpkg --compare-versions 7.2.0+dfsg-2 \< 7.2.0+dfsg1-1 && echo yes
> yes
> 
> , that would be a valid choice.

Thanks!



regards,
-- 
Herbert Parentes Fortes Neto (hpfn)

signature.asc
Description: This is a digitally signed message part

Re: reproducible-builds

[Herbert Fortes]

Em Seg, 2016-07-18 às 20:28 +0800, Paul Wise escreveu:
> On Mon, Jul 18, 2016 at 8:18 PM, Herbert Fortes wrote:
> 
> > I did a QA and reproducible-builds says that
> > it FTBFS with armhf on 2016-07-09. The
> > build was not tried again.
> 
> Which package ?


dvbackup
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/armhf/dvbackup.html

At the end has:

[...]
I: Current time: Fri Jul  8 18:38:51 GMT+12 2016
I: pbuilder-time-stamp: 1468046331
Sat Jul  9 06:41:09 UTC 2016 - the second build failed, even though the first 
build was successful.

https://tests.reproducible-builds.org/debian/unstable/armhf/dvbackup : 
reproducible ➤ FTBFS
Sat Jul  9 06:41:11 UTC 2016 - total duration: 0h 6m 25s.



regards,
--
Herbert Parentes Fortes Neto (hpfn)


signature.asc
Description: This is a digitally signed message part

reproducible-builds

[Herbert Fortes]

Hi,

I did a QA and reproducible-builds says that
it FTBFS with armhf on 2016-07-09. The
build was not tried again.

I did a build with harris (ssh) and the build
ran fine.

I can do something about the status of the 
package on reproducible-builds ? Or just
wait for a new try by them ?



regards,
-- Herbert Parentes Fortes Neto (hpfn)

signature.asc
Description: This is a digitally signed message part

Re: reproducible-builds

[Herbert Fortes]

Hi,

> Something failed somewhere in the second build, not in the package build
> itself but rather in the building script and was not properly detected
> as an infrastructure error (but rather as a FTBFS).
> I triggered another build of the package and not it has built
> successfully.

Thanks for all replies.

I do not have a special interest in the package. Just
a QA to do. I also did a repository (collab-maint) for
it.



regards,
-- Herbert Parentes Fortes Neto (hpfn)

signature.asc
Description: This is a digitally signed message part

Re: reproducible-builds

[Herbert Fortes]

Em Ter, 2016-07-19 às 12:42 +, Mattia Rizzolo escreveu:
> On Tue, Jul 19, 2016 at 09:38:44AM -0300, Herbert Fortes wrote:
> > I do not have a special interest in the package. Just
> > a QA to do. I also did a repository (collab-maint) for
> > it.
> 
> You could/shoud have set Vcs-* in d/control for that.

I did the repository yesterday. After the upload. I
will do that today. The same for libdv and libextractor-python.



regards,
-- Herbert Parentes Fortes Neto (hpfn)

signature.asc
Description: This is a digitally signed message part

Re: /usr/share/pyshared dir

[Herbert Fortes]

Em Sáb, 2016-07-16 às 21:24 +0500, Andrey Rahmatullin escreveu:
> On Sat, Jul 16, 2016 at 01:05:47PM -0300, Herbert Fortes wrote:
> > The package in Sid[0] has a /usr/share/pyshared
> > directory that will not be present if
> > you build (withour changes) the package today, 
> /usr/share/pyshared was used when we supported python 2.6. You can see
> that the sid package supports 2.6.

Ok. The package now is:

Depends: libextractor3 (>= 1:1.1), python:any (<< 2.8), python:any (>= 2.7.5-5~)

Thanks for the help.

> 
> > But it is reproducible[1].
> I guess the reproducible tools don't look at the sid binary packages.
> 

Yes, it does. testing and unstable for amd64, i386 and armhf

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libextractor-python.html



regards,
-- Herbert Parentes Fortes Neto (hpfn)

signature.asc
Description: This is a digitally signed message part

/usr/share/pyshared dir

[Herbert Fortes]

Hi,

I am doing a QA for python-extractor.

The package in Sid[0] has a /usr/share/pyshared
directory that will not be present if
you build (withour changes) the package today, 
my sid chroot env at least. But it is reproducible[1].

[0] - https://packages.debian.org/sid/all/python-extractor/filelist
[1] - 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libextractor-python.html

Others packages also have this directory[2].

[2] - 
https://packages.debian.org/search?suite=sid=all=any=contents=extractor.py

The source package name is libextractor-python and extractor.py
file is going to /usr/lib. Why /usr/share/pyshared/extractor.py ?

my debian/changelog until now:

  * QA upload.
  * debian/clean created:
  - rm egg-info files.
  * debian/compat:
  - 9
  * debian/control:
  - bump Standarsd-Version from 3.9.2 to 3.9.8
  - debhelper >= 9 and dh-python added to Depends field
  - using X-Python-Version
  - Recommends libextractor-plugins removed. (Closes:  #722200)
It was merged into libextractor3 1:1.1.
Thanks Micah Gersten.
  * debian/rules:
  - using PYBUILD.
  * debian/watch created.



regards,
-- Herbert Parentes Fortes Neto (hpfn)

signature.asc
Description: This is a digitally signed message part

Re: more recent version with python3 support

[Herbert Fortes]

Hi Tiago,


> On 12 July 2016 at 16:46, Herbert Fortes <h...@ig.com.br> wrote:
> > This new version has support for python3, as
> > said in setup.py, so I created debian/*.install
> > files and edited debian/control and debian/rules.
> 
> What are the contents of "debian/*.install" files?
> 
> I have packaged a Python library which has support for both Python 2
> and 3 and didn't needed "debian/*.install" files[1]. It has two binary
> packages, "python-*" and "python3-*", under "debian/control"[2] and
> "PYBUILD_NAME" environment variable defined in "debian/rules"[3]
> (which is required[4] by Pybuild).
> 
> Regards,
> Tiago.
> 
> [1]: 
> https://anonscm.debian.org/git/collab-maint/python-path-and-address.git/tree/debian?id=0a933ff
> [2]: 
> https://anonscm.debian.org/git/collab-maint/python-path-and-address.git/tree/debian/control?id=0a933ff
> [3]: 
> https://anonscm.debian.org/git/collab-maint/python-path-and-address.git/tree/debian/rules?id=0a933ff
> [4]: https://wiki.debian.org/Python/Pybuild#debian.2Frules
> 

Thanks, debian/*.install files are not necessary now. :)

I also tried dh_auto_test again, but:

E   ImproperlyConfigured: Requested setting AUTH_USER_MODEL, 
but settings are not configured. You must either define the 
environment variable DJANGO_SETTINGS_MODULE or call settings.configure() 
before accessing settings.

Skipping tests.



regards,
-- Herbert Parentes Fortes Neto (hpfn)

signature.asc
Description: This is a digitally signed message part

QA for dvbackup

[Herbert Fortes]

Hi,

I do not think this a practice, but telling
that I will do a QA for dvbackup[0].

[0] - https://packages.qa.debian.org/d/dvbackup.html



regards,
-- Herbert Parentes Fortes Neto (hpfn)

signature.asc
Description: This is a digitally signed message part

wrong version number ?

[Herbert Fortes]

Hi,

I am doing a QA for dvbackup package. I do not need
a Sponsor.

debian/changelog:
dvbackup (1:0.0.4-8) unstable; urgency=low ( I am doing )
dvbackup (1:0.0.4-7) unstable; urgency=low ( current version )

After 'debuild':

dvbackup_0.0.4-8_amd64.deb ( no epoch )

$ apt-get download dvbackup
dvbackup_1%3a0.0.4-7_amd64.deb ( epoch )

Why ?



regards,
-- 
Herbert Parentes Fortes Neto (hpfn)

signature.asc
Description: This is a digitally signed message part

Re: wrong version number ?

[Herbert Fortes]

Em Qui, 2016-07-07 às 18:38 +, Gianfranco Costamagna escreveu:
> Hi
> > debian/changelog:
> 
> > dvbackup (1:0.0.4-8) unstable; urgency=low ( I am doing )
> > dvbackup (1:0.0.4-7) unstable; urgency=low ( current version )
> > 
> > After 'debuild':
> > 
> 
> 
> sure, it has an epoch since a lot of time
> 
> https://packages.qa.debian.org/d/dvbackup/news/20120512T030239Z.html
> 
> 
> I don't know debuild, but
> pull-debian-source dvbackup
> cd dvbackup-*
> dpkg-buildpackage
> should work.
> 

It did not.

piuparts is ok:
[...]
11m31.7s DEBUG: Command ok: ['chroot', '/tmp/tmpa_k5UW', 'eatmydata', 'dpkg', 
'-i', 'tmp/dvbackup_0.0.4-8_amd64.deb']
[...]
11m39.7s DEBUG: Recording chroot state
11m41.2s INFO: PASS: Installation, upgrade and purging tests.
11m41.5s DEBUG: Starting command: ['umount', '/tmp/tmpa_k5UW/dev/shm']
11m41.6s DEBUG: Command ok: ['umount', '/tmp/tmpa_k5UW/dev/shm']
11m41.6s DEBUG: Starting command: ['umount', '/tmp/tmpa_k5UW/dev/pts']
11m41.6s DEBUG: Command ok: ['umount', '/tmp/tmpa_k5UW/dev/pts']
11m41.6s DEBUG: Starting command: ['umount', '/tmp/tmpa_k5UW/proc']
11m41.6s DEBUG: Command ok: ['umount', '/tmp/tmpa_k5UW/proc']
11m41.6s DEBUG: Starting command: ['rm', '-rf', '--one-file-system', 
'/tmp/tmpa_k5UW']
11m41.9s DEBUG: Command ok: ['rm', '-rf', '--one-file-system', '/tmp/tmpa_k5UW']
11m41.9s DEBUG: Removed directory tree at /tmp/tmpa_k5UW
11m41.9s INFO: PASS: All tests.
11m41.9s INFO: piuparts run ends.



regards,
-- Herbert Parentes Fortes Neto (hpfn)

signature.asc
Description: This is a digitally signed message part

Re: wrong version number ?

[Herbert Fortes]

Em Qui, 2016-07-07 às 18:38 +, Gianfranco Costamagna escreveu:
> Hi
> > debian/changelog:
> 
> > dvbackup (1:0.0.4-8) unstable; urgency=low ( I am doing )
> > dvbackup (1:0.0.4-7) unstable; urgency=low ( current version )
> > 
> > After 'debuild':
> > 
> 
> 
> sure, it has an epoch since a lot of time
> 
> https://packages.qa.debian.org/d/dvbackup/news/20120512T030239Z.html
> 
> 
> I don't know debuild, but
> pull-debian-source dvbackup
> cd dvbackup-*
> dpkg-buildpackage
> should work.
> 
> (I didn't try)
> G.
> 

I checked the .changes file.
Format: 1.8
Date: Thu, 07 Jul 2016 15:10:48 -0300
Source: dvbackup
Binary: dvbackup
Architecture: source amd64
Version: 1:0.0.4-8           <- (Here)

epoch is there.

I checked another package (gthumb) and is the
same situation. I guess is all right.



regards,
-- 
Herbert Parentes Fortes Neto (hpfn)

signature.asc
Description: This is a digitally signed message part

Re: wrong version number ?

[Herbert Fortes]

Em Qui, 2016-07-07 às 17:05 -0300, Herbert Fortes escreveu:
> Em Qui, 2016-07-07 às 20:01 +, Gianfranco Costamagna escreveu:
> > Hi,
> > 
> > > I'm not entirely sure, but it's been like this since forever.
> > 
> > I guess a filename containing ":" character might be problematic in linux
> > (not techically problematic, but better to avoid escapes)
> > 
> > so, even if the filename is 
> > "dvbackup_0.0.4-7_amd64.changes", the content is:
> > dvbackup (1:0.0.4-7) unstable; urgency=low
> > 
> 

Thank you guys!



regards,
-- Herbert Parentes Fortes Neto (hpfn)

signature.asc
Description: This is a digitally signed message part

update .preinst file

[Herbert Fortes]

Hi,


I have to update 4 debian/*.preinst files.


Right now the files are like here[0]:


|

if dpkg --compare-versions "$2" lt "1.2.4+dfsg1-7" ; then
   rm -rf /usr/share/doc/bogofilter || true
fi [0] -
https://anonscm.debian.org/git/collab-maint/bogofilter.git/tree/debian/bogofilter.preinst
This approach has problems on an upgrade from Jessie to Stretch[1].The
recommendation today is to use 'dpkg-maintscript-helper', so I should
change to ("a real directory is switched to a symlink"): [1] -
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832291 if
dpkg-maintscript-helper supports dir_to_symlink 2>/dev/null; then
dpkg-maintscript-helper dir_to_symlink \ /usr/share/doc/bogofilter
bogofilter 1.2.4+dfsg1-8 bogofilter -- "$@" fi From the manpage:
"pathname(/usr/share/doc/bogofilter here) is the absolute name of the
old directory (the path will be a symlink at the end of the
installation) and new-target (bogofilter here) is the target of the new
symlink at pathname. It can either be absolute or relative to the
directory containing pathname." But the symlink is created by
dh_installdocs[1] already. I just want to remove the directory. [1] -
'dh_installdocs --link-doc=bogofilter-common' The manpage again:
COMMANDS AND PARAMETERS supports command rm_conffile conffile
[prior-version [package]] mv_conffile old-conffile new-conffile
[prior-version [package]] symlink_to_dir pathname old-target
[prior-version [package]] dir_to_symlink pathname new-target
[prior-version [package]] What should I do ? Regards, Herbert

|

Re: update .preinst file

[Herbert Fortes]

Hi,

> Due to the way dpkg-maintscript-helper is implemented, the symlink
> created with dh_installdocs is ignored, so dpkg-maintscript-helper will
> create it for you. The manpage for dpkg-maintscript-helper also contains
> an explanation of why 'just removing the directory in preinst' can cause
> problems.
> 
> I think putting this into 'bogofilter-bdb.maintscript' and something
> similar in other maintscript files should work:
> 
> dir_to_symlink /usr/share/doc/bogofilter-bdb
> /usr/share/doc/bogofilter-common 1.2.4+dfsg1-8~
> 

Thanks James Cowgill.

Upload done.



Regards,
Herbert

remove a git repository

[Herbert Fortes]

Hi,

I did a mess on gthumb repository and I tried to
fix it. What I want to do is a kind  of roll back 
because I jumped one Debian revision.

Right now the 'Tag' section is ok and if you
click on 'Branch' links everything seems ok too. 
But the process to fix the mess was not 100% 
correct as can be seen on 'Age' section. I would 
like to start again.

Before start the fix process I did a backup. :)
BACKUP_gthumb.git[0] and gthumb.git[1] but I can 
not use it. I do not have the rights to re-write
the gthumb.git.

[0] - https://anonscm.debian.org/cgit/collab-maint/BACKUP_gthumb.git
[1] - https://anonscm.debian.org/cgit/collab-maint/gthumb.git

What do I do ? If I should leave the way it is now,
how to remove the backup ?



Regards,
Herbert

Re: remove a git repository

[Herbert Fortes]

On 14-11-2016 11:26, Sean Whitton wrote:
> Hello Herbert,
> 
> On Mon, Nov 14, 2016 at 10:32:28AM -0200, Herbert Fortes wrote:
>> I did a mess on gthumb repository and I tried to
>> fix it. What I want to do is a kind  of roll back 
>> because I jumped one Debian revision.
> 
> You should never rewrite published branch history.  What if someone else
> cloned it?  Rewriting tags is much less harmful, though.
> 
>> Before start the fix process I did a backup. :)
>> BACKUP_gthumb.git[0] and gthumb.git[1] but I can 
>> not use it. I do not have the rights to re-write
>> the gthumb.git.
> 
> You can SSH to alioth and edit .git/config to allow you to force-push,
> if you're really sure you want to do that.
> 

I can not edit .git/config that's the problem. I tried. I think
because I am using a guest account.

I will see how to upgrade the status.

Thanks Sean and Adam Borowski.



Regards,
Herbert

Re: remove a git repository

[Herbert Fortes]

On 14-11-2016 17:45, Sean Whitton wrote:

Hello Herbert,

On Mon, Nov 14, 2016 at 04:05:42PM -0200, Herbert Fortes wrote:

I can not edit .git/config that's the problem. I tried. I think
because I am using a guest account.


I doubt it is this.  Who owns the repo?  You could just ask them to do
it.



I am the maintainer of the package. The repo
is on collab-maint.



Regards,
Herbert

gthumb fails to build on all architectures

[Herbert Fortes]

Hi,

I uploaded version 3:3.5.1-3 of gThumb Debian package
an something went wrong.

The main problem seems to be[0] (amd64 - Mon, 31 Jul 2017):

Found cached translation database
Merging translations into gthumb-import.desktop.
Traceback (most recent call last):
  File "/usr/bin/glib-mkenums", line 669, in 
process_file(fname)
  File "/usr/bin/glib-mkenums", line 406, in process_file
line = curfile.readline()
  File "/usr/lib/python3.5/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc2 in position 108: 
ordinal not in range(128)

[0] - 
https://buildd.debian.org/status/fetch.php?pkg=gthumb=amd64=3%3A3.5.1-3=1501514571=0

I do not have this error on my machine and was waiting for
a second try on x86-grnet-01.debian.org.

About glib-mkenums:

glib2.0 (2.53.4-2) unstable; urgency=medium

  * Upload to unstable

 -- Matthias Klumpp   Sun, 30 Jul 2017 12:54:22 +0200

glib2.0 (2.53.4-1) experimental; urgency=medium

  * New upstream release 2.53.4
+ Unicode support has been updated to Unicode 10.0.0
+ glib-genmarshal and glib-mkenums have been rewritten in python
+ GLib can now be built with meson. autotools are still supported

 -- Iain Lane   Wed, 19 Jul 2017 17:32:31 +0100


Any comment?



Regards,
Herbert

Re: gthumb fails to build on all architectures

[Herbert Fortes]

On 02-08-2017 04:22, Andrey Rahmatullin wrote:
> On Tue, Aug 01, 2017 at 09:03:05PM -0300, Herbert Fortes wrote:
>> The main problem seems to be[0] (amd64 - Mon, 31 Jul 2017):
>>
>> Found cached translation database
>> Merging translations into gthumb-import.desktop.
>> Traceback (most recent call last):
>>   File "/usr/bin/glib-mkenums", line 669, in 
>> process_file(fname)
>>   File "/usr/bin/glib-mkenums", line 406, in process_file
>> line = curfile.readline()
>>   File "/usr/lib/python3.5/encodings/ascii.py", line 26, in decode
>> return codecs.ascii_decode(input, self.errors)[0]
>> UnicodeDecodeError: 'ascii' codec can't decode byte 0xc2 in position 108: 
>> ordinal not in range(128)
> From /topic of #debian-devel:
> glib-mkenums breakage: #870310 #870212 
> 

Thanks!


Regards,
Herbert

Bug#875693: RFS: python-meshio/1.8.16-1

[Herbert Fortes]

Hi Ghislain Vaillant,

> Package: sponsorship-requests
> Severity: normal
> 
> Dear mentors,
> 
> I am looking for a sponsor for the following package:
> 
> * Package name    : python-meshio
>   Version : 1.8.16-1
>   Upstream Author : Nico Schlömer
> * URL : https://github.com/nschloe/meshio
> * License : Expat
>   Section : python
> 
> Please check out the package by visiting the following URL:
> 
>   https://anonscm.debian.org/git/debian-science/packages/python-meshio.git
> 
> Changes since last upload:
> 
>   * New upstream version 1.8.16
>   * Filter egg-info directory with extend-diff-ignore
>   * Add recommended get-orig-source target
>   * Fixup whitespacing in rules file
>   * Add Nico Schlömer to Uploaders
>   * Bump the standards version to 4.1.0
> 
> Regards,
> Ghis
> 

Uploaded. Thanks!



Regards,
Herbert

obs: people do not like to refresh License file.

Re: Bug#875876: RFS: python-dtcwt/0.12.0-1

[Herbert Fortes]

Hi Ghislain Vaillant,

> Package: sponsorship-requests
> Severity: normal
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "python-dtcwt"
> 
> * Package name    : python-dtcwt
>   Version : 0.12.0-1
>   Upstream Author : Rich Wareham 
> * URL : https://github.com/rjw57/dtcwt
> * License : BSD
>   Section : science
>

Cc: debian-legal


python-dtcwt is in Debian since 2015, but ORIGINAL_README.txt[0]
file is a bit problematic. I need someone to do a second check on
copyright.

[0] - 
https://anonscm.debian.org/git/debian-science/packages/python-dtcwt.git/tree/ORIGINAL_README.txt

It is said:

"This code is copyright and is supplied free of charge for research
purposes only. In return for supplying the code, all I ask is that, if
you use the algorithms, you give due reference to this work in any
papers that you write and that you let me know if you find any good
applications for the DT CWT. If the applications are good, I would be
very interested in collaboration. I accept no liability arising from use
of these algorithms."

 - ... free of charge for research only ...
 - ... all I ask is ... let me know if you find any good ...

The package is BSD, but COPYING.txt file says:

"This licence applies to any parts of this library which are novel in comparison
to the original DTCWT MATLAB toolbox written by Nick Kingsbury and Cian
Shaffrey. See the ORIGINAL_README.txt file for details on any further
restrictions of use."

It does not look to be in "main" to me.



Regards,
Herbert

Re: Bug#875764: RFS: pybind11/2.2.1-1 [experimental]

[Herbert Fortes]

Hi Ghislain Vaillant,

> Package: sponsorship-requests
> Severity: normal
> 
> Dear mentors,
> 
> I am looking for a sponsor for the following package:
> 
> * Package name    : pybind11
>   Version : 2.2.1-1
>   Upstream Author : Wenzel Jakob 
> * URL : https://github.com/pybind/pybind11
> * License : BSD
>   Section : libs
> 
> Please check out the package by visiting the following URL:
> 
>   https://anonscm.debian.org/git/debian-science/packages/pybind11.git
> 
> Changes since last upload:
> 
>   * New upstream version 2.2.1
>   * Drop the patch queue, no longer required
>   * Prevent multiple install of headers
>   * Add new test dependency on Boost
>   * Test query of includes via pybind11
>   * Add recommended get-orig-source target
>   * Fixup the nocheck and nodoc guards
>     - Replace occurrences of findstring with filter
>     - Use DEB_BUILD_OPTIONS instead of DEB_BUILD_PROFILES
>   * Fixup whitespacing in rules file
>   * Drop superfluous dependency on python-pytest
>   * Filter egg-info directory with extend-diff-ignore
>   * Fixup the Vcs-Browser URI
>   * Bump the standards version to 4.1.0
> 

There are some files that have headers with - Copyright (c) 2017.
But debian/copyright file was not refreshed.

Please update debian/copyright file.



Regards,
Herbert

Re: Bug#875693: RFS: python-meshio/1.8.16-1

[Herbert Fortes]

Hi Ghislain Vaillant,

> Package: sponsorship-requests
> Severity: normal
> 
> Dear mentors,
> 
> I am looking for a sponsor for the following package:
> 
> * Package name    : python-meshio
>   Version : 1.8.16-1
>   Upstream Author : Nico Schlömer
> * URL : https://github.com/nschloe/meshio
> * License : Expat
>   Section : python
> 
> Please check out the package by visiting the following URL:
> 
>   https://anonscm.debian.org/git/debian-science/packages/python-meshio.git
> 
> Changes since last upload:
> 
>   * New upstream version 1.8.16
>   * Filter egg-info directory with extend-diff-ignore
>   * Add recommended get-orig-source target
>   * Fixup whitespacing in rules file
>   * Add Nico Schlömer to Uploaders
>   * Bump the standards version to 4.1.0
> 
> Regards,
> Ghis
> 

I check this one tomorrow morning.



Regards,
Herbert

Bug#858155: RFS: stenc/1.0.7-1 [ITP]

[Herbert Fortes]

Em 10-10-2017 16:31, Andrey Rahmatullin escreveu:
> On Tue, Oct 10, 2017 at 04:06:59PM -0300, Herbert Fortes wrote:
>> It seems that the package is ready. Andrey Rahmatullin
>> did the review.
>>
>> The last activity was on 01 Oct 2017;  I can take one last
>> look in the package and upload it if the is no problem with
>> that.
> Yes please. The package seemed in good shape.
> 

Ok.



Regards,
Herbert

Bug#858155: RFS: stenc/1.0.7-1 [ITP]

[Herbert Fortes]

Hi Denys Berkovskyy and Andrey Rahmatullin,

>On Tue, 26 Sep 2017 15:34:35 +0100 Denys Berkovskyy  
>wrote:
>
> > On 8 Aug 2017, at 19:22, Andrey Rahmatullin  wrote:
> >
> > On Mon, Aug 07, 2017 at 11:52:33AM +0100, Denys Berkovskyy wrote:
> >> Thank you for your comments, I have made the changes you mentioned and 
> >> uploaded updated version to https://mentors.debian.net/package/stenc
> > debian/compat is still 9.
> > Also, please change priority to optional (and you should have done that
> > while updating to the Standards-Version 4.0.1, as you don't just bump the
> > version, you read
> > https://www.debian.org/doc/debian-policy/upgrading-checklist.html).
> >
> > --
> > WBR, wRAR
>
> I fixed the issues and uploaded new version to mentors: 
> https://mentors.debian.net/package/stenc 
> 
> Standards-Version is 4.1.0 now. Hopefully I haven't missed anything.
>

It seems that the package is ready. Andrey Rahmatullin
did the review.

The last activity was on 01 Oct 2017;  I can take one last
look in the package and upload it if the is no problem with
that.

Standards-Version is 4.1.1 now.



Regards,
Herbert

Bug#858155: RFS: stenc/1.0.7-1 [ITP]

[Herbert Fortes]

Em 10-10-2017 16:31, Andrey Rahmatullin escreveu:
> On Tue, Oct 10, 2017 at 04:06:59PM -0300, Herbert Fortes wrote:
>> It seems that the package is ready. Andrey Rahmatullin
>> did the review.
>>
>> The last activity was on 01 Oct 2017;  I can take one last
>> look in the package and upload it if the is no problem with
>> that.
> Yes please. The package seemed in good shape.
> 

Upload done. But in a next revision take a look at:


X: stenc source: deprecated-configure-filename (Severity: wishlist)
I: stenc: spelling-error-in-manpage usr/share/man/man1/stenc.1.gz preceed 
precede



Regards,
Herbert

Re: Bug#873630: RFS: python-qtpy/1.3.1-1

[Herbert Fortes]

Hi Ghislain Vaillant,

> Package: sponsorship-requests
> Severity: normal
> 
> Dear mentors,
> 
> I am looking for a sponsor for the following package:
> 
> * Package name: python-qtpy
>   Version : 1.3.1-1
>   Upstream Author : The Spyder Development Team
> * URL : https://github.com/spyder-ide/qtpy
> * License : Expat
>   Section : python
> 
> Please check out the package by visiting the following URL:
> 
>   https://anonscm.debian.org/git/python-modules/packages/python-qtpy.git
> 
> Changes since last upload:
> 
>   * Switch from git-dpm to gbp
>   * Source new releases from PyPI
>   * New upstream version 1.3.1
>   * Add new install dependency on pyqt5.qtopengl
>   * Bump standards version to 4.1.0
> 

It seems simple changes. And it will be my first task
tomorrow morning.



Regards,
Herbert

Bug#873630: RFS: python-qtpy/1.3.1-1

[Herbert Fortes]

Hi Ghislain Vaillant,

> Package: sponsorship-requests
> Severity: normal
> 
> Dear mentors,
> 
> I am looking for a sponsor for the following package:
> 
> * Package name: python-qtpy
>   Version : 1.3.1-1
>   Upstream Author : The Spyder Development Team
> * URL : https://github.com/spyder-ide/qtpy
> * License : Expat
>   Section : python
> 
> Please check out the package by visiting the following URL:
> 
>   https://anonscm.debian.org/git/python-modules/packages/python-qtpy.git
> 
> Changes since last upload:
> 
>   * Switch from git-dpm to gbp
>   * Source new releases from PyPI
>   * New upstream version 1.3.1
>   * Add new install dependency on pyqt5.qtopengl
>   * Bump standards version to 4.1.0
> 
> Regards,
> Ghis
> 

I am checking the package by repo.

Please update debian/copyright file.

Re: Bug#873631: RFS: pytest-qt/2.1.2-3 [RC]

[Herbert Fortes]

Hi Ghislain Vaillant,

> Package: sponsorship-requests
> Severity: normal
> 
> Dear mentors,
> 
> I am looking for a sponsor for the following package:
> 
> * Package name: pytest-qt
>   Version : 2.1.2-3
>   Upstream Author : Bruno Oliveira
> * URL : https://github.com/pytest-dev/pytest-qt
> * License : Expat
>   Section : python
> 
> Please check out the package by visiting the following URL:
> 
>   https://anonscm.debian.org/git/python-modules/packages/pytest-qt.git
> 
> Changes since the last upload:
> 
>   * Fix FTBFS due to logging changes in Qt.
> Thanks to Dmitry Shachnev for the patch (Closes: #872992)
>   * Use DEB_BUILD_OPTIONS for nocheck and nodoc guards
>   * Fixup the Vcs-Browser URI
>   * Bump standards version to 4.1.0
> 

I will see this one too. Tomorrow morning.



Regards,
Herbert
 

Re: Bug#874703: RFS: rednotebook/2.2-1.1 [ITP] [NMU] -- A cross-platform journal

[Herbert Fortes]

Em 09-09-2017 13:16, Phil Wyett escreveu:
>> I have emailed the person concerned and asked that I get the package back
>> into
>> debian and they learn from this, how to work with upstream and debian alike.

I never saw something like this 'debian/changelog'. But this
is not a problem. There is always new approach to learn.

But:

 - one name asking for an upload
 - one name in debian/changelog
 - one name in debian/control
 - one name as the responsable for the package

All different names. Is that not confuse ?



Regards,
Herbert

Re: Bug#874703: RFS: rednotebook/2.2-1.1 [ITP] [NMU] -- A cross-platform journal

[Herbert Fortes]

Hi Phil Wyert,

> On Fri, 2017-09-08 at 22:21 +0100, Phil Wyett wrote:
>> Package: sponsorship-requests
>> Severity: wishlist
>> Owner: Phil Wyett 
>>
>> I am looking for a sponsor for my package "rednotebook":
>>
>> * Package name: rednotebook
>>   Version : 2.2
>>   Upstream Author : Jendrik Seipp 
>> * URL : https://github.com/jendrikseipp/rednotebook
>> * License : GPL-2+
>>   Programming Lang: Python
>>   Description: A modern desktop journal. It lets you format, tag and
>>search your entries. You can also add pictures, links
>>and customizable templates, spell check your notes,
>>and export to plain text, HTML, Latex or PDF.
>>
>> To access further information about this package, please visit the following
>> URL:
>>
>> https://mentors.debian.net/package/rednotebook
>>
>> Alternatively, one can download the package with dget using this command:
>> https://mentors.debian.net/debian/pool/main/r/rednotebook/rednotebook_2.2-1.1.
>> ds
>> c
>>
>> More information about rednotebook can be obtained from:
>>
>> http://rednotebook.sourceforge.net
>> https://github.com/jendrikseipp/rednotebook
>>
>> This package was removed from debian due to webkit issues. This is hopefully
>> the
>> beginning of having it back in debian.
>>
>> I am working with the upstream author and will continue to do so.
>>
>> Regards
>>
>> Phil
>>
> 
> Hi,
> 
> New upload.
> 
> To access further information about this package, please visit the following
> URL:
> 
> https://mentors.debian.net/package/rednotebook
> 
> Alternatively, one can download the package with dget using this command:
> https://mentors.debian.net/debian/pool/main/r/rednotebook/rednotebook_2.2-1.2.ds
> c
> 
> Changes:
> 
> rednotebook (2.2-1.2) unstable; urgency=medium
> 
>   * Non-maintainer upload.
>   * Fix lintian pedantic warning - wiki-copyright-format-uri.
>   * Fix license block issues created from above fix.
> 
>  -- Phil Wyett   Fri, 08 Sep 2017 22:35:07 +0100
> 

The *.dsc link above does not work, so I visited the rednotebook's 
page on mentors and used this link (the last upload):

https://mentors.debian.net/debian/pool/main/r/rednotebook/rednotebook_2.2-2.dsc

The 'debian/changelog' file is a little bit difficult to 
understand. There is a lot of entries like that:

rednotebook (X.X-X) UNRELEASED; urgency=low

On dates that it was not part of Debian. The package has been 
removed on [Date: Sat, 01 Jul 2017 16:31:39 +]

The last entry in 'debian/changelog' file is:

rednotebook (2.2-2) UNRELEASED; urgency=medium

  * Team upload.
  * Packaged for Debian Mentors.
  * Non maintainer upload

 -- Omar Jair Purata Funes   Sat, 09 Sep 2017 00:07:42 
-0500


The maintainer is Jonathan Wiltshire (last upload 1.8.1-1). Not 
Jendrik Seipp (as is written on 'debian/control')

'debian/changelog', 'debian/control' and 'debian/rules' files 
needs adjusts. 

There is a lot of work to do to put this package back.



Regards,
Herbert

Bug#868086: RFS: beautify-bash/1.1-1 [ITP]

[Herbert Fortes]

Em 25-09-2017 17:16, Andrey Rahmatullin escreveu:
> On Mon, Sep 25, 2017 at 05:07:29PM -0300, Herbert Fortes wrote:
>> The debian/watch file is not working.
> It is working here.
> 

Ok. It is working on Sid.

I am sorry.



Regards,
Herbert

Bug#877047: RFS: sane-backends-extras/1.0.22.5 [QA]

[Herbert Fortes]

Hi Hugh McMaster,

> Package: sponsorship-requests
> Severity: normal
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "sane-backends-extras".
> 
> * Package name: sane-backends-extras
>Version: 1.0.22.5
>Upstream Author: SANE
> * URL: http://www.sane-project.org/
> * License: GPL v2
>Section: graphics
> 
> It builds the following binary packages:
>   * libsane-extras - API library for scanners -- extra backends
>   * libsane-extras-common - API library for scanners -- documentation and 
> support files
>   * 
> lihttp://deb.debian.org/debian/pool/main/b/bogofilter/bogofilter_1.2.4+dfsg1-10.dscbsane-extras-dev
>  - API development library for scanners [development files]
> 
> To access further information about this package, please visit the following 
> URL:
>   https://mentors.debian.net/package/sane-backends-extras
> 
> Alternatively, you may download the package with dget using this command:
> 
> dget -x 
> https://mentors.debian.net/debian/pool/main/s/sane-backends-extras/sane-backends-extras_1.0.22.5.dsc
> 
> Changes since the last upload:
>   * QA upload.
>   * debhelper update:
> - Update package compatibility to level 10
>   * debian/control:
> - Bump debhelper build-dep to >= 10~.
> - Remove autotools-dev from the Build-Depends list, as debhelper
>   enables the 'autoreconf' sequence by default.
> - Bump Standards-Version from 3.9.8 to 4.1.0 (no changes needed).
> - Convert libsane-extras-common to Architecture: all.
> - Mark libsane-extras-dev Multi-Arch: same (Closes: #862263).
>   * debian/extras-backends/geniusvp2:
> - Fix a spelling error in the BUGS file (lintian).
>   * debian/rules:
> - Remove '--with=autotools_dev' (now handled by debhelper level 10).
>   * doc/sane-geniusvp2.man:
> - Fix spelling errors (lintian).
>   * Rename configure.in to configure.ac (lintian).
> 
> Regards,
> 
> Hugh McMaster
> 

Uploaded. Thanks for you time.



Regards,
Herbert

Re: Bug#877047: RFS: sane-backends-extras/1.0.22.5 [QA]

[Herbert Fortes]

Hi Hugh McMaster,

> Package: sponsorship-requests
> Severity: normal
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "sane-backends-extras".

I can review this RFS. I did the last QA upload.



Regards,
Herbert

> 
> * Package name: sane-backends-extras
>Version: 1.0.22.5
>Upstream Author: SANE
> * URL: http://www.sane-project.org/
> * License: GPL v2
>Section: graphics
> 
> It builds the following binary packages:
>   * libsane-extras - API library for scanners -- extra backends
>   * libsane-extras-common - API library for scanners -- documentation and 
> support files
>   * libsane-extras-dev - API development library for scanners [development 
> files]
> 
> To access further information about this package, please visit the following 
> URL:
>   https://mentors.debian.net/package/sane-backends-extras
> 
> Alternatively, you may download the package with dget using this command:
> 
> dget -x 
> https://mentors.debian.net/debian/pool/main/s/sane-backends-extras/sane-backends-extras_1.0.22.5.dsc
> 
> Changes since the last upload:
>   * QA upload.
>   * debhelper update:
> - Update package compatibility to level 10
>   * debian/control:
> - Bump debhelper build-dep to >= 10~.
> - Remove autotools-dev from the Build-Depends list, as debhelper
>   enables the 'autoreconf' sequence by default.
> - Bump Standards-Version from 3.9.8 to 4.1.0 (no changes needed).
> - Convert libsane-extras-common to Architecture: all.
> - Mark libsane-extras-dev Multi-Arch: same (Closes: #862263).
>   * debian/extras-backends/geniusvp2:
> - Fix a spelling error in the BUGS file (lintian).
>   * debian/rules:
> - Remove '--with=autotools_dev' (now handled by debhelper level 10).
>   * doc/sane-geniusvp2.man:
> - Fix spelling errors (lintian).
>   * Rename configure.in to configure.ac (lintian).
> 
> Regards,
> 
> Hugh McMaster
> 

Bug#868086: RFS: beautify-bash/1.1-1 [ITP]

[Herbert Fortes]

Em 25-09-2017 17:16, Andrey Rahmatullin escreveu:
> On Mon, Sep 25, 2017 at 05:07:29PM -0300, Herbert Fortes wrote:
>> The debian/watch file is not working.
> It is working here.
> 

Again, debian/watch is working.

Here are my comments about:

debian/changelog:

 - ITP bug number is correct
 - please run 'dch -r' to update the timestamp

debian/compat:

 - Please use 10 instead of 9

debian/control:

 I test the script on python3 with 5 .sh scripts
and it ran without erros. But the first line is

   #!/usr/bin/env python

 So, I put on Build-Depends only:
 
   Build-Depends: debhelper (>= 10), dh-python, python-all

 Standards-Version: 4.1.0
 
 And after 'Package' entry:

   Architecture: all
   Depends: ${misc:Depends}, ${python:Depends}

debian/rules (only these lines):
 
 #!/usr/bin/make -f

 #export DH_VERBOSE = 1

 %:
 dh $@ --with python2


 override_dh_installchangelogs:
 dh_installchangelogs CHANGES

Please note that CHANGES file is been installed as
a changelog file so beautify-bash.docs file can be
removed.


debian/copyright:

 The github page says GPL version 2. As the LICENSE file and
the header in beautify_bash.py script too. But debian/copyright 
only has GPL-3.0+. please fix that.

 The file is pretty detailed, thanks for that. But the first 'Files'
entry only has:

 Files: *
 Copyright: 2017 Mike Mestnik <cheako+apt_r...@mikemestnik.net>
 License: GPL-3.0+

 I do not know if you really saying that your are the owner of
the project now or if you  misundertood with the 'debian/*' part.
The ITP says the upstreams are  Paul Lutus and Shriram V (they
are in the file). If you are the owner now the homepage should 
point to github, I think. Instead of the previous upstream page.
Or remove this entry.

Some tests in t_todo/ are failing.

These are my considerations.



Regards,
Herbert

Bug#868086: RFS: beautify-bash/1.1-1 [ITP]

[Herbert Fortes]

Em 26-09-2017 06:26, gregor herrmann escreveu:
> On Tue, 26 Sep 2017 06:12:54 -0300, Herbert Fortes wrote:
> 
>>  override_dh_installchangelogs:
>>   dh_installchangelogs CHANGES
> 
> This can be removed from debian/rules, dh_installchangelogs finds
> CHANGES and some other common names all by itself.
>  
> 

OK. Thanks for that.



Regards,
Herbert

Bug#868086: RFS: beautify-bash/1.1-1 [ITP]

[Herbert Fortes]

Hi Mike Mestnik,

> Package: sponsorship-requests
> Severity: wishlist
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Dear mentors,
>
> I am looking for a sponsor for my package "beautify-bash"

The debian/watch file is not working. And I assume that
you know where to look for information because the file
has an 'opts' line.

Can you please fix it ?



Regards,
Herbert


>
> * Package name : beautify-bash
> Version : 1.1-1
> Upstream Author : Paul Lutus, Shriram V 
> * URL : https://arachnoid.com/python/beautify_bash_program.html
> * License : GPL+
> Section : utils
>
> It builds those binary packages:
>
> beautify-bash - Beautifier for Bash shell scripts written in Python
>
> To access further information about this package, please visit the following 
> URL:
>
> https://mentors.debian.net/package/beautify-bash
>
>
> Alternatively, one can download the package with dget using this command:
>
> dget -x 
> https://mentors.debian.net/debian/pool/main/b/beautify-bash/beautify-bash_1.1-1.dsc
>
> Changes since the last upload:
>
> beautify-bash (1.1-1) unstable; urgency=medium
>
> * Initial release (Closes: #867869)
>
> -- Mike Mestnik  Tue, 11 Jul 2017 13:21:00 
> -0500
>
> Regards,
> Mike Mestnik
>
> - --
> Debian Release: 9.0
> APT prefers stable
> APT policy: (500, 'stable'), (480, 'unstable'), (470, 'experimental')
> Architecture: i386 (x86_64)
>
> Kernel: Linux 4.11.0-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)
>
> -BEGIN PGP SIGNATURE-
>
> iQJLBAEBCAA1FiEE50YYYn+e/FujuFBs49GprY7cq4oFAlllSBIXHGNoZWFrb0Bt
> aWtlbWVzdG5pay5uZXQACgkQ49GprY7cq4qpnBAAgGmQqwcmjqfCsm65YXvKGexO
> O/3AntGsC68Mi1NMBxYWZVkTIdkGFgNkq+VnoXqXxepGrdoAi9HZtBjhcxHZ+KN9
> bOGCOjhZj+coOSOiJXkCvVqMfGdUBn9Qfw2EyaXQcq/o/Dym64u+Vihq4ElvwdJq
> LpzdPZp8nEPpayAX+n7U5BvKnr0B4rUwdMtOfDTeDtCA6+86bzNKJO0eUnAOKKP6
> c4fCVODHc58WwF8NcW7GPywznvU4WoR5QJ8repLSYfXrLBeFGcv1sWugbbo2+hhe

Re: Bug#876624: RFS: qr-tools/1.4~bzr23-1 [QA]

[Herbert Fortes]

Hi Boyuan Yang,

Uploaded.

Thanks for your work!



Regards,
Herbert

> Package: sponsorship-requests
> Severity: normal
> X-Debbugs-CC: david4...@gmail.com algoz...@gmail.com
> 
> Dear mentors,
> 
> This is a QA upload for package "qr-tools", which might went a little bit too 
> far from simply a QA. Anyway here is the information:
> 
>  * Package name: qr-tools
>Version : 1.4~bzr23-1
>Upstream Author : David Green 
>  * URL : https://launchpad.net/qr-tools
>  * License : GPL-3+
>Section : python
> 
>   It builds those binary packages:
> 
> python-qrtools - high level library for reading and generating QR codes
>  qtqr  - Qt frontend for QR code generator and decoder
> 
>   To access further information about this package, please visit the 
> following 
> URL:
> 
>   https://mentors.debian.net/package/qr-tools
> 
> 
>   Alternatively, one can download the package with dget using this command:
> 
> dget -x 
> https://mentors.debian.net/debian/pool/main/q/qr-tools/qr-tools_1.4~bzr23-1.dsc
> 
> 
>   Git packaging repository:
> 
> https://anonscm.debian.org/git/collab-maint/qr-tools.git
> 
> 
> Changes since the last upload:
>  qr-tools (1.4~bzr23-1) unstable; urgency=high
>  .
>* QA upload.
>  + Set package maintainer to Debian QA Group.
>* New upstream snapshot.
>  + Fix incompatibility with new PIL library.
>(Closes: #812556; Closes: #847150)
>  + Add option to select whether to show WiFi password when writing it.
>* Replace python-imaging dep with python-pil. (Closes: #866475)
>* Apply wrap-and-sort -abst.
>* Bump debhelper compat to v10.
>* Use Standards-Version 4.1.0.
>* Add patch to migrate to Qt5. (Closes: #875142)
>* Add patch to prevent crashing when given file is not an image.
>* Add patch to provide zh_CN translation.
>* Add patch to fix crashing with malformed URL.
>* Update qtqr.desktop in debian/ dir.
>  + Add zh_CN translation.
>  + Edit Exec key to comply with Desktop Entry Specification.
>* Update qtqr.1 man page accordingly.
>* Set package qtqr in section "utils".
>* Document all known bugs in debian/BUGS file.
> 
> ...as you can see, it's more than just a QA upload. The biggest part is the 
> migration from PyQt4 to PyQt5 (since Qt4 is to be removed soon). AFAIK the 
> program is working well after the migration (tested locally).
> 
> I am CC-ing upstream authors here in hope that we could get contributions 
> merged back later.
> 
> Regards,
> Boyuan Yang
> 

package pynmea2

[Herbert Fortes]

Hi,

There was a ITP-RFS for pynmea2. But python-nmea2 already
exists.

https://packages.qa.debian.org/p/python-nmea2.html

I asked the contributor (2017-11-12) to close the bugs with 
an n-d...@bugs.debian.org but he sent -cl...@bugs.debian.org 
to ITP only. RFS still open.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871468

Today I received an email saying that pynmea2 was accepted. It
already has a page:

https://packages.qa.debian.org/p/pynmea2.html


What to do ? Ask FTP-Master to remove the package ?



Regards,
Herbert

Re: package pynmea2

[Herbert Fortes]

Em 21-11-2017 15:51, Joachim Langenbach escreveu:
> Good evening,
> 
> I've seen all the messages today. Is there something I need to do now?
> 

A RC bug was opened (blocks the package in unstable) and a request
to remove the package was done. So, I believe there is nothing 
else to do.

Thanks for replying.

>>> Yeah, although it's good to contact the maintainer first.  I've done so by
>>> a RC bug: #881763 (duplicate package, undeclared file conflict).  This
>>> way we won't need to dig potential rdeps someone may upload tomorrow out
>>> of testing.
>>>
>>> Have you talked to the ftpmasters already?
>>
>> I opened a bug against ftp.debian.org
>>
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881907
> 



Regards,
Herbert

Re: package pynmea2

[Herbert Fortes]

Em 14-11-2017 20:22, Adam Borowski escreveu:
> On Tue, Nov 14, 2017 at 12:13:55PM -0200, Herbert Fortes wrote:
>> There was a ITP-RFS for pynmea2. But python-nmea2 already
>> exists.
>>
>> https://packages.qa.debian.org/p/python-nmea2.html
>>
>> I asked the contributor (2017-11-12) to close the bugs with 
>> an n-d...@bugs.debian.org but he sent -cl...@bugs.debian.org 
>> to ITP only. RFS still open.
> 
>> Today I received an email saying that pynmea2 was accepted. It
>> already has a page:
>>
>> https://packages.qa.debian.org/p/pynmea2.html
>>
>>
>> What to do ? Ask FTP-Master to remove the package ?
> 
> Yeah, although it's good to contact the maintainer first.  I've done so by a
> RC bug: #881763 (duplicate package, undeclared file conflict).  This way we
> won't need to dig potential rdeps someone may upload tomorrow out of
> testing.
> 
> Have you talked to the ftpmasters already?
> 
> 

I opened a bug against ftp.debian.org

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881907

Re: package pynmea2

[Herbert Fortes]

Em 14-11-2017 20:22, Adam Borowski escreveu:
> On Tue, Nov 14, 2017 at 12:13:55PM -0200, Herbert Fortes wrote:
>> There was a ITP-RFS for pynmea2. But python-nmea2 already
>> exists.
>>
>> https://packages.qa.debian.org/p/python-nmea2.html
>>
>> I asked the contributor (2017-11-12) to close the bugs with 
>> an n-d...@bugs.debian.org but he sent -cl...@bugs.debian.org 
>> to ITP only. RFS still open.
> 
>> Today I received an email saying that pynmea2 was accepted. It
>> already has a page:
>>
>> https://packages.qa.debian.org/p/pynmea2.html
>>
>>
>> What to do ? Ask FTP-Master to remove the package ?
> 
> Yeah, although it's good to contact the maintainer first.  I've done so by a
> RC bug: #881763 (duplicate package, undeclared file conflict).  This way we
> won't need to dig potential rdeps someone may upload tomorrow out of
> testing.
> 
> Have you talked to the ftpmasters already?

No, not yet.

But, I was not clear, I guess.

It is the same program, the same upstream.

pynmea2 (python3-pynema2 Debian package) should be removed.



Regards,
Herbert
 

Re: package pynmea2

[Herbert Fortes]

Hi Geert Stappers,

> On Tue, Nov 14, 2017 at 12:13:55PM -0200, Herbert Fortes wrote:
>> Hi,
>>
>> There was a ITP-RFS for pynmea2.
>> But python-nmea2 already exists.
>>
>> https://packages.qa.debian.org/p/python-nmea2.html
>>
>> I asked the contributor (2017-11-12) to close the bugs with 
>> an n-d...@bugs.debian.org but he sent -cl...@bugs.debian.org 
>> to ITP only.
> 
> Bug Tracking System URL is  
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870906#64
> 
> 
>> RFS still open.
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871468
> 
> Meanwhile closed.
> 
> 
>> Today I received an email saying that pynmea2 was accepted. It
>> already has a page:
>>
>> https://packages.qa.debian.org/p/pynmea2.html
>>
>>
>> What to do ? Ask FTP-Master to remove the package ?
>>
> 
> Provide more information.
> 
> Make this table complete, fill in the dots
> 

upstream |  debian_source   | builds binary
-+--+
 .   |  ... |   python-pynmea2
Tom Flanagan | https://packages.qa.debian.org/p/pynmea2.html | python3-pynmea2

Only Python 3 was builded



Regards,
Herbert


























 

Bug#880491: RFS: budgie-desktop/10.4+git20171031.10.g9f71bb8-1

[Herbert Fortes]

Em 01-11-2017 06:06, foss.freedom escreveu:
> Package: sponsorship-requests
> Severity: normal
>   Dear mentors,
> 
>   I am looking for a sponsor for my package "budgie-desktop"
> 
>  * Package name: budgie-desktop
>Version : 10.4+git20171031.10.g9f71bb8-1
>Upstream Author : i...@solus-project.com
>  * URL : https://github.com/budgie-desktop/budgie-desktop
>  * License : LGPL-2.1/GPL2.0
>Section : x11
> 
>   It builds those binary packages:
> 
> budgie-core - Core package for Budgie-Desktop
>  budgie-core-dev - Development package for budgie-desktop
>  budgie-desktop - Desktop package for budgie-desktop
>  budgie-desktop-doc - documentation files for the budgie-desktop
>  gir1.2-budgie-1.0 - GNOME introspection library for budgie-desktop
>  libbudgie-plugin0 - Plugin library for budgie-desktop
>  libbudgietheme0 - Theme library for budgie-desktop
>  libraven0  - Raven library for budgie-desktop
> 
>   To access further information about this package, please visit the
> following URL:
> 
>   https://mentors.debian.net/package/budgie-desktop
> 
> 
>   Alternatively, one can download the package with dget using this command:
> 
> dget -x 
> https://mentors.debian.net/debian/pool/main/b/budgie-desktop/budgie-desktop_10.4+git20171031.10.g9f71bb8-1.dsc
> 
> Notes:
> The primary reason for this upload is due to meson v0.43 that has been
> uploaded to unstable.  With this version, budgie desktop no longer
> will build succcessfully.
> Thus this is a preemptive upload just in-case in the near future a
> rebuild of budgie-desktop is requested.
> 
> check-all-the-things run an copyright updates made due to the slight
> source restructuring in the upstream tarball
> 
>   Changes since the last upload:
> 
> * Bug-fix release
> - fix FTBFS due to meson v0.43; budgie desktop (upstream) have
>   released a signed tarball to resolve since it is not possible
>   to cherry-pick the appropriate git commit
>   https://github.com/budgie-desktop/budgie-desktop/issues/1228
>   * Packaging Changes
> - debian/rules: support separate ubuntu and debian gsettings
>   overrides
> - debian/rules: add bindnow hardening
> - debian/rules: install Budgie gi-typelib to a multiarch location
> - debian/control: Update standards version - add an autopkgtest
> - debian/copyright: gvc file-location changed from src to subprojects
> - debian/copyright: add Jeremy Bicha to packaging copyright
> 
> 
>   Regards,
>David Mohammed
> 

Re: Bug#880491: RFS: budgie-desktop/10.4+git20171031.10.g9f71bb8-1

[Herbert Fortes]

Hi,

Em 01-11-2017 06:06, foss.freedom escreveu:
> Package: sponsorship-requests
> Severity: normal
>   Dear mentors,
> 
>   I am looking for a sponsor for my package "budgie-desktop"
> 
>  * Package name: budgie-desktop
>Version : 10.4+git20171031.10.g9f71bb8-1
>Upstream Author : i...@solus-project.com
>  * URL : https://github.com/budgie-desktop/budgie-desktop
>  * License : LGPL-2.1/GPL2.0
>Section : x11
> 
>   It builds those binary packages:
> 
> budgie-core - Core package for Budgie-Desktop
>  budgie-core-dev - Development package for budgie-desktop
>  budgie-desktop - Desktop package for budgie-desktop
>  budgie-desktop-doc - documentation files for the budgie-desktop
>  gir1.2-budgie-1.0 - GNOME introspection library for budgie-desktop
>  libbudgie-plugin0 - Plugin library for budgie-desktop
>  libbudgietheme0 - Theme library for budgie-desktop
>  libraven0  - Raven library for budgie-desktop
> 

Can you please fix the typo:


I: budgie-core: spelling-error-in-binary usr/bin/budgie-panel overriden 
overridden


There are two 'wishlist' (just in case you had forgot).

I: budgie-core: desktop-entry-lacks-keywords-entry 
usr/share/applications/budgie-desktop-settings.desktop
I: budgie-core: desktop-entry-lacks-keywords-entry 
usr/share/xsessions/budgie-desktop.desktop



Regards,
Herbert

Bug#883305: RFS: sqldeveloper-package/0.5.0

[Herbert Fortes]

Hi Lazarus Long,

> Package: sponsorship-requests
> Severity: normal
>
> Dear mentors,
>
> I am looking for a sponsor for my package "sqldeveloper-package"
>

I did the upload.

Please close this RFS.



Regards,
Herbert


> * Package name : sqldeveloper-package
> Version : 0.5.0
> Upstream Author : Lazarus Long 
> * URL : 
> * License : GPL-3+
> Section : misc
>
> It builds this binary package:
>
> sqldeveloper-package - Oracle SQL Developer Debian package builder
>
> To access further information about this package, please visit the
> following URL:
>
> 
>
>
> Alternatively, one can download the package with dget using this command:
>
> dget -x 
> https://mentors.debian.net/debian/pool/contrib/s/sqldeveloper-package/sqldeveloper-package_0.5.0.dsc
>
> More information about sqldeveloper-package can be obtained from
> .
>
> Changes since the last upload:
>
> sqldeveloper-package (0.5.0) unstable; urgency=low
>
> * Since SQL Developer v4.1, Oracle has started to include i386 and amd64
> shared libraries in NetBeans Platform modules. Due to this, converted
> make-sqldeveloper-package to both generate multiple packages and to be
> Multi-Arch compatible:
> - Added Multi-Arch dependencies
> - Added cross-packaging functionality
> - Rewrote a large portion of make-sqldeveloper-package to deal with the
> additional logic
> - Rearranged the debian/* files to support multiple packages
> - Generated packages recommend each other (libraries and SQL Developer)
> - Added a new command line option "-s|--skip-libraries" to skip building
> the shared libraries package(s)
> * Multiple versions can now coexist, "sqldeveloper.[upstream version]" will
> invoke a specific version of Oracle SQL Developer while "sqldeveloper"
> takes advantage of Debian's alternatives system and, when left in auto
> mode, will always invoke the highest version installed
> * Exposed Oracle CLI for SQL Developer, a non-gui interface for
> scripting or
> headless control of Oracle SQL Developer. Following the multiple versions
> coexistence concept, "sdcli.[upstream version]" and "sdcli"
> will behave as
> described above
> * Since SQL Developer v4.2, Oracle started to bundle Oracle SQL Developer
> Command-Line (SQLcl) with Oracle SQL Developer. When available, and as an
> alternative to the standalone package (see "sqlcl-package"),

Bug#898231: RFS: budgie-extras/0.5.0-1

[Herbert Fortes]

Hi,

Em 08-05-2018 20:25, foss.freedom escreveu:

Package: sponsorship-requests
Severity: normal

   Dear mentors,

   I am looking for a sponsor for my package "budgie-extras"

  * Package name: budgie-extras
Version : 0.5.0-1
Upstream Author : Ubuntu Budgie Developers
  * URL : https://github.com/ubuntubudgie/budgie-extras
  * License : GPL-3+
Section : misc

   It builds those binary packages:



I did the upload.

[...]  

   May I request that this package be added to my debian maintainers
list of packages I'm allowed to look after (dak
fossfree...@ubuntu.com) ?


I can see that.

I will learn on how to give you a DM permission to budgie-extras.

Thanks for the package.



Regards,
Herbert

Re: Help to clarify an issue

[Herbert Fortes]

Em 31-12-2017 15:38, Mattia Rizzolo escreveu:
> Hello,
> 
> On Sun, Dec 31, 2017 at 01:23:51PM -0200, Herbert Fortes wrote:
>> Can someone read the bug report[0] an give
>> an second opinion?
>>
>> [0] - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885404
>>
>> We disagree when an NMU is necessary and how
>> important the request is.
> 
> wow - wtf.
> 
> I'll keep my comments here structured:
> 
> 1) I believe Jonathan is very very hasty on making NMUs
>  a) whilst true that NMUs today are seen very much with a nicer eye than
> in the past, it's still considered not something to do lightly, not
> even when somebody is on the LowNMU list or the package is in
> collab-maint
>  b) also, upload an NMU the day after saying he has a patch and 3 days
> after the original bug report is totally hasty, no matter the delay
>  c) and usually as soon as the maintainer replies to a bug all the
> intentions to NMU drops in favour of a team upload (unless the
> maintainer asks for a NMU, as it often happens)
> 2) I totally don't understand what's Herbert's problem with the
>proposal, providing /usr/bin/duc from both the regular and -nox
>package sounds a very nice idea to me
> 
> 

The problem is: Why think about this if an alias, an alias,
gives what he wants. Why spend more than a minute with this.

> Summary: please just stop meta-discussing whether or not a NMU was the
> appropriate action to take, and start discussing the actual bug, with
> neither party being so stubborn as it looks from my side.

I sent an email to mentors because the way things are going
he will make another upload. No delay, not nothing. Just upload.

I am stopping.

Help to clarify an issue

[Herbert Fortes]

Hi,

I am having difficult to end a situation
with duc Debian package.

Can someone read the bug report[0] an give
an second opinion?

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

We disagree when an NMU is necessary and how
important the request is.



Regards,
Herbert

Re: Help to clarify an issue

[Herbert Fortes]

Em 01-01-2018 12:06, Mattia Rizzolo escreveu:
> On Mon, Jan 01, 2018 at 11:01:59AM -0200, Herbert Fortes wrote:
>> It is impossible that someone has both - duc and duc-nox - installed ?
> 
> Using the alternatives system you can have both installed, and the the
> system administrator decides what provides /usr/bin/duc (but by default
> keep it the -x variant).
> You can also have bin:duc install /usr/bin/duc-x and keep bin:duc-nox
> installing /usr/bin/duc-nox, so really the dowside for people relying on
> /usr/bin/duc-nox are nil.
> 
> I'm sorry, but IMHO you have provided no argument in favour of rejecting
> Jonathan request.
> 

Ok. I am really do not understand.

The package is orphan now and what it is seems as best
can be done by who wants to do the job. 

I honestly not angry with anyone. I mean it.

Let's start the new year with good thoughts.



Sincerely,
Herbert

Re: Help to clarify an issue

[Herbert Fortes]

Em 01-01-2018 14:02, Mattia Rizzolo escreveu:
> On Mon, Jan 01, 2018 at 10:47:26AM -0500, The Wanderer wrote:
>> On 2018-01-01 at 10:39, Mattia Rizzolo wrote:
>>> On Mon, Jan 01, 2018 at 01:30:16PM -0200, Herbert Fortes wrote:
>>>> The package is orphan now and what it is seems as best can be done
>>>> by who wants to do the job.
>>>
>>> So your argument is "the package is not developed anymore (?) and
>>> was always like that, so let's not touch it too much"?
>>
>> I parsed his statement as meaning "Okay, since my opinion as maintainer
>> of this package isn't being accepted, I'm declaring the package
>> orphaned; now anyone who wants to work on it can do so".
>>
>> I mean, I hope I'm wrong, because orphaning would be a drastic and
>> unfortunate outcome from this - but that's how I interpret it.
> 
> Hell, no, that was definitely not what I meant.
> 
> It probably is my fault in misunderstanding its usage of the "orphan"
> word above, see "The package is orphan now".  I didn't want to read "I
> orphaned the package" in that, and definitely I wasn't even thinking of
> that outcome.
> 
> - https://bugs.debian.org/886013
> 
> Herbert: In no way I was even thinking of you giving up the package!
> (Also, I believe the only person interested in the package is Jonhatan)
> 

Please be calm everybody.

I really liked to do the package. It has an not common
debian/rules. But I am not in love with the package.

I am a domestic user who wants to be a programmer. I do
not know complex situations where different scenarios
come up. My usage (computer) is simple.

I do not have a camera yet, but I am more closed to 
libgphoto2, gphoto2, gthumb. And some python packages.

Packages come and go.

Re: Help to clarify an issue

[Herbert Fortes]

Em 01-01-2018 10:56, The Wanderer escreveu:
> On 2018-01-01 at 05:48, Herbert Fortes wrote:
> 
>>
>>> Well said, I agree 100%.
>>>
>>> I consider both parties to be wrong here:
>>> * Jonathan went very hasty on the NMU
>>> * Herbert refuses a patch for a quite annoying thing, fixing which requires
>>>   no effort on his side (as the submitter did all the work), without
>>>   providing any rationale
>>>
>>> It's a clear bug to me: the package behaves in a different way based on
>>> whether an unrelated doodad (some X stuff) is installed or not.  That breaks
>>> people's muscle memory, requiring user's effort for every single machine the
>>> package is installed on -- or, on every invocation, thinking "is this shell
>>> on a GUI machine?".  And I for one ssh to my home desktop a lot.
>>>
>>> "because one does not want to press tab" is a ridiculous explanation.
>>>
>>> Thus, Herbert: could you please tell us if you have any reason to reject the
>>> fix, other than being annoyed with a NMU done in a wrong way?
>>
>> It seems more ridiculous to me do not want to use an alias.
> 
> Adding an alias locally only fixes the problem locally, for one machine,
> or even one person on one machine. (And - as mentioned in the bug
> comments - if you're trying to share the same bashrc across multiple
> machines, some of which have only duc and some of which have duc-nox, a
> simple alias definition will not suffice; you'd need to write
> conditional logic to determine which alias to define.)
> 
> Diverting the installed binary to a non-conflicting name and defining an
> alternative locally would avoid the latter problem, but it seems
> fragile, and again only fixes the problem for one machine.
> 
> Defining an alternative in the package, or (less optimally) having both
> packages provide the same binary name with appropriate Conflicts:, fixes
> the problem for everyone who uses the package - with relatively minimal
> effort, and as far as I can see, zero undesirable side effects.
> 

It is impossible that someone has both - duc and duc-nox - installed ?

Re: Help to clarify an issue

[Herbert Fortes]

> Well said, I agree 100%.
> 
> I consider both parties to be wrong here:
> * Jonathan went very hasty on the NMU
> * Herbert refuses a patch for a quite annoying thing, fixing which requires
>   no effort on his side (as the submitter did all the work), without
>   providing any rationale
> 
> It's a clear bug to me: the package behaves in a different way based on
> whether an unrelated doodad (some X stuff) is installed or not.  That breaks
> people's muscle memory, requiring user's effort for every single machine the
> package is installed on -- or, on every invocation, thinking "is this shell
> on a GUI machine?".  And I for one ssh to my home desktop a lot.
> 
> "because one does not want to press tab" is a ridiculous explanation.
> 
> Thus, Herbert: could you please tell us if you have any reason to reject the
> fix, other than being annoyed with a NMU done in a wrong way?
>

It seems more ridiculous to me do not want to use an alias.


 

Re: Help to clarify an issue

[Herbert Fortes]

Em 01-01-2018 13:39, Mattia Rizzolo escreveu:
> On Mon, Jan 01, 2018 at 01:30:16PM -0200, Herbert Fortes wrote:
>> The package is orphan now and what it is seems as best
>> can be done by who wants to do the job.
> 
> So your argument is "the package is not developed anymore (?) and was
> always like that, so let's not touch it too much"?

No. Jonathan Dowland spent some time doing what he thinks
is good. And some folks agree that is a good improve.
I believe it was more than a day working on the solution. 
So he uses/has-more-interesting-in the software than me.

> 
>> I honestly not angry with anyone. I mean it.
>>
>> Let's start the new year with good thoughts.
> 
> Be assured nobody is angry at anybody, nor is thinking ill of you :)

Thanks!

Bug#905375: RFS: bitz-server/2.0.1-1

[Herbert Fortes]

Hi,

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> retitle 905375 RFS: bitz-server/2.0.1-1
> thanks
>

I ran 'blhc --all ../*.build and there are some

CXXFLAGS missing (-fPIE)
LDFLAGS missing (-fPIE -pie)

I saw debian/rules has 'hardening=+all' but can
you please add:

export DEB_CXXFLAGS_MAINT_APPEND  = -fPIE
export DEB_LDFLAGS_MAINT_APPEND = -fPIE -pie



Regards,
Herbert

Bug#905375: RFS: bitz-server/2.0.1-1

[Herbert Fortes]

Em 04-08-2018 19:21, Jörg Frings-Fürst escreveu:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi Herbert,


Am Samstag, den 04.08.2018, 09:05 -0300 schrieb Herbert Fortes:

Hi,

  > -BEGIN PGP SIGNED MESSAGE-
  > Hash: SHA512
  >
  > retitle 905375 RFS: bitz-server/2.0.1-1
  > thanks
  >

I ran 'blhc --all ../*.build and there are some

CXXFLAGS missing (-fPIE)
LDFLAGS missing (-fPIE -pie)

I saw debian/rules has 'hardening=+all' but can
you please add:

export DEB_CXXFLAGS_MAINT_APPEND  = -fPIE
export DEB_LDFLAGS_MAINT_APPEND = -fPIE -pie



Many thanks!!

Changed, tested and uploaded to mentors again.




Uploaded. Thanks.



Regards,
Herbert

Bug#905455: RFS: dmidecode/3.1-2

[Herbert Fortes]

Hi,


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

Package name: dmidecode
Version : 3.1-2
Upstream Author : dmidecode-de...@nongnu.org
URL : https://nongnu.org/dmidecode/
License : GPL-2+
Section : utils

   It builds those binary packages:

  dmidecode  - SMBIOS/DMI table decoder
  dmidecode-udeb - SMBIOS/DMI table decoder (udeb) (udeb)



Sorry, but can you please add to debian/rules:

export DEB_LDFLAGS_MAINT_APPEND = -fPIE -pie
export DEB_CFLAGS_MAINT_APPEND = -fPIE

It is just a copy and paste :)



Regards,
Herbert

Bug#905455: RFS: dmidecode/3.1-2

[Herbert Fortes]

Em 05-08-2018 15:10, Andrey Rahmatullin escreveu:

On Sun, Aug 05, 2018 at 03:02:39PM -0300, Herbert Fortes wrote:

Sorry, but can you please add to debian/rules:

export DEB_LDFLAGS_MAINT_APPEND = -fPIE -pie
export DEB_CFLAGS_MAINT_APPEND = -fPIE

Why?



Becauso of 'blhc --all'

Bug#905455: RFS: dmidecode/3.1-2

[Herbert Fortes]

Em 05-08-2018 15:47, Andrey Rahmatullin escreveu:

On Sun, Aug 05, 2018 at 03:23:33PM -0300, Herbert Fortes wrote:

Sorry, but can you please add to debian/rules:

export DEB_LDFLAGS_MAINT_APPEND = -fPIE -pie
export DEB_CFLAGS_MAINT_APPEND = -fPIE

Why?



Becauso of 'blhc --all'

I'm sorry but that's not a valid reason.



Can you tell me why not?

What I know is just 'blhc' is enough. But why not
use '--all'?

I do not know much about that and I can learn new
if you say a bit more.

Bug#905455: RFS: dmidecode/3.1-2

[Herbert Fortes]

Em 05-08-2018 15:27, Jörg Frings-Fürst escreveu:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello Herbert,

thanks for your review.

Am Sonntag, den 05.08.2018, 15:02 -0300 schrieb Herbert Fortes:

Hi,


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 Package name: dmidecode
 Version : 3.1-2
 Upstream Author : dmidecode-de...@nongnu.org
 URL : https://nongnu.org/dmidecode/
 License : GPL-2+
 Section : utils

It builds those binary packages:

   dmidecode  - SMBIOS/DMI table decoder
   dmidecode-udeb - SMBIOS/DMI table decoder (udeb) (udeb)



Sorry, but can you please add to debian/rules:

export DEB_LDFLAGS_MAINT_APPEND = -fPIE -pie
export DEB_CFLAGS_MAINT_APPEND = -fPIE

It is just a copy and paste :)



Blame on me :-(

Added, tested and uploaded again.



thanks for your patience Jörg

Uploaded.



Regards,
Herbert

Bug#905455: RFS: dmidecode/3.1-2

[Herbert Fortes]

Em 05-08-2018 16:14, Andrey Rahmatullin escreveu:

On Sun, Aug 05, 2018 at 03:54:23PM -0300, Herbert Fortes wrote:

Sorry, but can you please add to debian/rules:

export DEB_LDFLAGS_MAINT_APPEND = -fPIE -pie
export DEB_CFLAGS_MAINT_APPEND = -fPIE

Why?

Becauso of 'blhc --all'

I'm sorry but that's not a valid reason.

Can you tell me why not?

Sure.
First of all, you should never do some change because some static analyzer
told you. You need to understand what did it tell you, why, and why it
thinks you should do that change.
blhc just analyzes build logs to make sure all expected flags are passed.
"--all   Force check for all +all (+pie, +bindnow) hardening flags. By default it's 
auto detected."
So if you use --all you either know that the package should pass the flags
for both pie and bindnow or must ignore the respective blhc warnings.
dpkg-buildflags(1) says that the pie hardening option has no effect on
most architectures, as it's enabled in gcc, so no flags are passed.
In such situations you need to check the result, in this case check
whether the binary has PIE enabled, not just blindly follow an
incorrectly used static analyzer (and even then you need to find out the
problem and not just pass some compiler/linker flags).



Ok. Thanks.

Bug#907664: RFS: budgie-desktop/10.4+git20180830.01.f2dbc215fdb-1

[Herbert Fortes]

Hi David Mohammed,

I am giving you budgie-desktop upload permission.



Regards,
Herver

Bug#907664: RFS: budgie-desktop/10.4+git20180830.01.f2dbc215fdb-1

[Herbert Fortes]

 

Thanks Herver - due to the new binary with this upload (libbudgie-private0) 
FTP-Master has rejected the package with this message

"ACL dm: NEW uploads are not allowed

binary:libbudgie-private0 is NEW."

Can this be sponsored this time around please?



Uploaded to experimental.

But please update debian/copyright before the upload to SID.



Regards,
Herbert

Bug#894307: RFS: pgn2web/0.4-2 [ITA]

[Herbert Fortes]

Em 01-04-2018 05:25, Jose G. López escreveu:
> On Sat, 31 Mar 2018 09:29:02 -0300
> Herbert Fortes <terb...@gmail.com> wrote:
> 
>> Hi Jose G. López,
>>
>> I ran 'blhc --all' and there are some CFLAGS, CXXFLAGS and LDFLAGS
>> missing '-fPIE' '-fPIE -pie'.
>>
>> Can you please fix them?
>>
> 
> Hi Herbert,
> 
> Fix it. Reuploaded to mentors and pushed to salsa.
> 

Uploaded.

Thank you for your work.



Regards,
Herbert

Bug#894307: RFS: pgn2web/0.4-2 [ITA]

[Herbert Fortes]

Hi Jose G. López,

> Package: sponsorship-requests
> Severity: wishlist
>
> Dear mentors,
>
> I am looking for a sponsor for my package "pgn2web":
>
> * Package name : pgn2web
> Version : 0.4-2
> Upstream Author : William Hoggarth 
> * URL : http://pgn2web.sourceforge.net/
> * License : GPL-3+
> Section : web
>
> It builds those binary packages:
>
> pgn2web - convert PGN chess game files into webpages
>
> To access further information about this package, please visit the
> following URL:
>
> https://mentors.debian.net/package/pgn2web
>
> Alternatively, one can download the package with dget using this
> command:
>
> dget -x 
> https://mentors.debian.net/debian/pool/main/p/pgn2web/pgn2web_0.4-2.dsc
>

I ran 'blhc --all' and there are some CFLAGS, CXXFLAGS and LDFLAGS
missing '-fPIE' '-fPIE -pie'.

Can you please fix them?



Regards,
Herbert

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

[Herbert Fortes]

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#910913: RFS: ghostwriter/1.7.3-1 [ITP]

[Herbert Fortes]

On 10/13/18 7:56 PM, ghost wrote:

Thanks for reviewing!

I am neither the upstream nor the person who originally uploaded to mentors.d.n,
though I am doing the most fixing part for the package for it to get into 
Debian...


OK. I am reading files from 1.7.3-4 and there is only Sebastien
name in it.





- debian/copyright seems to need an update.

Ouch, there are new assets not included in COPYING. I guess it's now blocked on
upstream.


 Different author from the project.

Do we need to list everyone?



If there is a file with something like:

Copyright  foo
License 

It must be in debian/copyright. In the 1.7.3 upstream tarball:

$ /tmp/ghostwriter-1.7.3$ egrep -sriA25 "(copyright|public dom)" ./  | less
[...]
./src/spell_checker.h: * Copyright (C) 2009, 2010, 2012 Graeme Gott 

./src/spell_checker.h: * Copyright (C) 2014 attercop
./src/spell_checker.h- *
./src/spell_checker.h- * This program is free software: you can redistribute it 
and/or modify
./src/spell_checker.h- * it under the terms of the GNU General Public License 
as published by
./src/spell_checker.h- * the Free Software Foundation, either version 3 of the 
License, or
./src/spell_checker.h- * (at your option) any later version.
[...]
./src/find_dialog.h: * Copyright (C) 2008, 2009, 2010, 2012 Graeme Gott 

./src/find_dialog.h: * Copyright (C) 2014, 2015 wereturtle
./src/find_dialog.h- *
./src/find_dialog.h- * This program is free software: you can redistribute it 
and/or modify
./src/find_dialog.h- * it under the terms of the GNU General Public License as 
published by
./src/find_dialog.h- * the Free Software Foundation, either version 3 of the 
License, or
./src/find_dialog.h- * (at your option) any later version.
[...]
./src/sundown/autolink.h: * Copyright (c) 2011, Vicent Marti
./src/sundown/autolink.h- *
./src/sundown/autolink.h- * Permission to use, copy, modify, and distribute 
this software for any
./src/sundown/autolink.h- * purpose with or without fee is hereby granted, 
provided that the above
./src/sundown/autolink.h: * copyright notice and this permission notice appear 
in all copies.
./src/sundown/autolink.h- *

And more. They must go to debian/copyright.

The entry about 'Files: debian/*': the maintainer of the Debian package
here. debian/control says Sebastien CHAVAUX

As noone is the upstream the patch files also need - no must - a header.
See debian/patches/clean-deps.patch

dpkg-shlibdeps says it's a useless dependency  # Looks like a description
--- a/ghostwriter.pro
+++ b/ghostwriter.pro
@@ -28,7 +28,7 @@
 
 TEMPLATE = app
 
-QT += printsupport webkitwidgets widgets concurrent svg

+QT += printsupport webkitwidgets widgets concurrent
 
 CONFIG -= debug

 CONFIG += warn_on


The header:

Description: (above)
Author: foo
Last-Update: a date


https://dep-team.pages.debian.net/deps/dep3/  # Sample DEP-3 compliant headers



Regards,
Herbert

Bug#910966: RFS: 4pane

[Herbert Fortes]

Hi,

On 10/13/18 6:23 PM, David Hart wrote:

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for an update of my package "4pane"


I can not build the package right now.  I did a download of
the debian dir.

debian/changelog

 - is "UNRELEASED".
 - a comment: I never saw a changelog going to 'testing'. Like
   version 5.0-1. It is in Sid anyway. But there are less 4 lines
   in that part of the file

debian/copyright

 -  does not have a 'Files: debian/*". I never saw that either.

I can not check control and rules.



Regards,
Herbert




   * Package name: 4pane
 Version : 5.0-2
 Upstream Author : David Hart 
   * URL : https://4Pane.co.uk
   * License : GPL3
 Section : x11

It builds these binary packages:

   4pane - four-pane detailed-list file manager

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

   https://mentors.debian.net/package/4pane


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

dget -x https://mentors.debian.net/debian/pool/main/4/4pane/4pane_5.0-2.dsc

There is also a git repo:
  https://github.com/dghart/4pane-debian-dir

The upload mostly changes to the latest debhelper and policy versions, with
consequent lintian fixes. However it also switches 4pane to use the GTK3 flavour
of wxwidgets3.0: see #894663.

This is a request for a review and upload of the update. The amended package
builds and works, and is lintian-clean.

Changes since the last upload:

4pane (5.0-2) unstable; urgency=medium

   * Depend on the gtk+3 version of wxWidgets: see #894663
   * Override testsuite-autopkgtest-missing
   * Add an upstream/metadata file
   * Move the appdata.xml file from appdata/ to metadata/
   * Change some links from http: to https:
   * Update to the latest debhelper and policy versions


Regards,

David Hart

Bug#910966: RFS: 4pane/5.0-2

[Herbert Fortes]

On 10/14/18 11:24 AM, David Hart wrote:

Hi Herbert,


debian/changelog
- is "UNRELEASED".
- a comment: I never saw a changelog going to 'testing'. Like
   version 5.0-1. It is in Sid anyway. But there are less 4 lines
   in that part of the file


I wasn't sure what was right for that field. I've now changed it to 'unstable'.


debian/copyright
-  does not have a 'Files: debian/*". I never saw that either.


I don't think it's needed. As I'm both the packager and upstream, IIUC the
contents of a 'Files: debian/*' entry would just duplicate the overriding
'Files: *'. Please correct me if I'm mistaken.




I understand. I thought the same thing in a first time. And nobody
said anything before. Can not be wrong.

But then I thought the debian dir as a separated part. Not related
to other files.

If no sponsor does the upload the package before me, I will see it.



Regards,
Herbert

Bug#910913: RFS: ghostwriter/1.7.3-1 [ITP]

[Herbert Fortes]

On 10/14/18 8:38 AM, ghost wrote:

Hi,

I've uploaded my version to mentors.d.n. I thought it would cause conflict 
since Sebastien already uploaded the same version, but never mind.



Thank you very much!

I did the upload. Let's see what FTP-Master thinks.



Regards,
Herbert
 

Bug#910913: RFS: ghostwriter/1.7.3-1 [ITP]

[Herbert Fortes]

Hi,

On 10/13/18 7:52 AM, ghost wrote:

Package: sponsorship-requests
Severity: wishlist


 Forwarded Message  
Subject:RFS: ghostwriter/1.7.3-1 [ITP]
Date:   Mon, 08 Oct 2018 05:49:14 +1300
From:   Sebastien CHAVAUX 
To: 894...@bugs.debian.org, ghost 


 Dear mentors,

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


You sent a link to 1.7.3-1.dsc. But mentors also has others
revision number. The last one is 1.7.3-4.

The package is new in Debian. It must be 1.7.3-1. A few questions:

 - debian/changelog must has only one entry. About Debian. With an ITP number.
 - debian/compat is 10. Is there a reason to not use 11? I tried with 11
   and seems fine.
 - The package really does not have a git? Vcs-*.
 - patch files does not have info about description, author, last-update
   but as you are the upstream I think they will be removed in a next
   release.
 - debian/copyright seems to need an update. There are code with different
   license from the project. Different author from the project.

Please, fix the package.



Regards,
Herbert




* Package name: ghostwriter
  Version : 1.7.3-1
  Upstream Author :wereturtle 

* URL :http://wereturtle.github.io/ghostwriter/
* License : GPLv3
  Section : editors

 It builds those binary packages:

   ghostwriter - Distraction-free, themeable Markdown editor

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

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


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

   dget 
-xhttps://mentors.debian.net/debian/pool/main/g/ghostwriter/ghostwriter_1.7.3-1.dsc

 More information about ghostwriter
can be obtained fromhttp://wereturtle.github.io/ghostwriter/.

 Changes since the last upload:

 - Update to version 1.7.3:
 * Fixed segfault that occurred when changing the theme or interface style 
after opening the Preview Options dialog


 Regards,
  Sebastien CHAVAUX

Bug#910966: RFS: 4pane/5.0-2

[Herbert Fortes]

Hi,

My final comments so I can upload the package:

The history of debian/changelog is been changed. Please,
keep the history.

https://tracker.debian.org/media/packages/4/4pane/changelog-5.0-1

diff -Nru 4pane-5.0/debian/changelog 4pane-5.0/debian/changelog
--- 4pane-5.0/debian/changelog  2017-07-20 11:18:45.0 -0300
+++ 4pane-5.0/debian/changelog  2018-10-08 13:15:58.0 -0300
@@ -1,12 +1,19 @@
-4pane (5.0-1) unstable; urgency=medium
+4pane (5.0-2) unstable; urgency=medium
+
+  * Depend on the gtk+3 version of wxWidgets: see #894663
+  * Override testsuite-autopkgtest-missing
+  * Add an upstream/metadata file
+  * Move the appdata.xml file from appdata/ to metadata/
+  * Change some links from http: to https:
+  * Update to the latest debhelper and policy versions
+
+ -- David Hart   Mon, 08 Oct 2018 17:15:58 +0100
+
+4pane (5.0-1) testing; urgency=medium
 
   * New upstream version.

 All the previous patches are now redundant and a dfsg tarball is
 no longer needed.
-  * Bump std-version to 4.0.0, no changes needed
-  * Update copyright file.
-  * Add dependency on gettext, msgfmt is used by upstream build system
-  * Update watch file
 
  -- David Hart   Thu, 20 Jul 2017 15:18:45 +0100




 - debian/rules does not need these two lines:

diff -Nru 4pane-5.0/debian/rules 4pane-5.0/debian/rules
--- 4pane-5.0/debian/rules  2017-07-20 11:18:45.0 -0300
+++ 4pane-5.0/debian/rules  2018-10-08 13:15:58.0 -0300
@@ -3,8 +3,6 @@
 DH_VERBOSE = 1
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all

-DPKG_EXPORT_BUILDFLAGS = 1
-include /usr/share/dpkg/buildflags.mk



Regards,
Herbert

Bug#911867: RFS: frr/6.0.1-1 [ITP]

[Herbert Fortes]

Hi,

On 10/25/18 3:17 PM, David Lamparter wrote:


Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

  * Package name: frr
Version : 6.0.1-1
Upstream Author : FRRouting-dev 
  * URL : https://frrouting.org/
  * License : GPLv2 and LGPLv2.1
Section : net

This replaces the "quagga" package, which FRRouting is a fork of.

It builds those binary packages:

   frr   - BGP/OSPF/RIP/RIPng/ISIS/PIM/LDP routing daemon forked from Quagga
   frr-dbg- BGP/OSPF/RIP/RIPng/ISIS/PIM/LDP routing daemon (debug symbols)
   frr-doc- BGP/OSPF/RIP/RIPng/ISIS/PIM/LDP routing daemon (documentation)
   frr-pythontools - BGP/OSPF/RIP/RIPng/ISIS/PIM/LDP routing daemon (Python 
Tools)
   frr-rpki-rtrlib - FRRouting RTRlib RPKI support
   frr-snmp   - FRRouting SNMP support

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

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


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

   dget -x https://mentors.debian.net/debian/pool/main/f/frr/frr_6.0.1-1.dsc

More information about frr can be obtained from https://frrouting.org

Changes since the last upload is not applicable since this is the first
upload.

I expect there still is feedback that I need to address in regards to
the Debian packaging on this and I will likely be uploading further
revisions in the coming days.



I did not build the package. My comment:

There are many lintian info warnings that can be fixed easily:


I no-symbols-control-file
usr/lib/x86_64-linux-gnu/libfrrospfapiclient.so.0.0.0
usr/lib/x86_64-linux-gnu/libfrr.so.0.0.0

https://wiki.debian.org/UsingSymbolsFiles


I possible-documentation-but-no-doc-base-registration
I spelling-error-in-binary  # a lot
I spelling-error-in-manpage  # a lot

I systemd-service-file-missing-documentation-key
lib/systemd/system/frr.service
O package-name-doesnt-match-sonames
libfrr0 libfrrospfapiclient0 (override comment: libfrr* are for 
internal use only and do not provide a stable API or ABI. soname / library 
versioning is irrelevant and they must always be shipped exact-matching to the 
daemons compiled against it)

  It is a package name. That's all.
  The lib can not be trusted?


O systemd-service-file-refers-to-unusual-wantedby-target
lib/systemd/system/frr.service network-online.target (override comment: 
we're a bit special since we provide network connectivity by starting up 
routing protocols.)
X duplicate-files
usr/share/doc/frr/examples/pbrd.conf.sample 
usr/share/doc/frr/examples/staticd.conf.sample

frr-rpki-rtrlib

I extended-description-is-probably-too-short
I hardening-no-fortify-functions
usr/lib/x86_64-linux-gnu/frr/modules/bgpd_rpki.so

frr source

I debian-control-has-obsolete-dbg-package
frr-dbg
I duplicate-long-description
frr-doc frr-pythontools
I ored-build-depends-on-obsolete-package
build-depends: dh-systemd  => use debhelper (>= 
9.20160709)
P debian-watch-does-not-check-gpg-signature
P package-uses-old-debhelper-compat-version
9

There is a problem with version 11?
 
O alternatively-build-depends-on-python-sphinx-and-python3-sphinx

(override comment: these are for build-compatibility on older distros 
(e.g. Ubuntu 14.04))

It is a new package. It is preferable to not upload Python 2
X upstream-metadata-file-is-missing

Bug#911867: RFS: frr/6.0.1-1 [ITP]

[Herbert Fortes]

Hi,

On 10/25/18 3:17 PM, David Lamparter wrote:


Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

  * Package name: frr
Version : 6.0.1-1
Upstream Author : FRRouting-dev 
  * URL : https://frrouting.org/
  * License : GPLv2 and LGPLv2.1
Section : net

This replaces the "quagga" package, which FRRouting is a fork of.

It builds those binary packages:

   frr   - BGP/OSPF/RIP/RIPng/ISIS/PIM/LDP routing daemon forked from Quagga
   frr-dbg- BGP/OSPF/RIP/RIPng/ISIS/PIM/LDP routing daemon (debug symbols)
   frr-doc- BGP/OSPF/RIP/RIPng/ISIS/PIM/LDP routing daemon (documentation)
   frr-pythontools - BGP/OSPF/RIP/RIPng/ISIS/PIM/LDP routing daemon (Python 
Tools)
   frr-rpki-rtrlib - FRRouting RTRlib RPKI support
   frr-snmp   - FRRouting SNMP support

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

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


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

   dget -x https://mentors.debian.net/debian/pool/main/f/frr/frr_6.0.1-1.dsc

More information about frr can be obtained from https://frrouting.org

Changes since the last upload is not applicable since this is the first
upload.

I expect there still is feedback that I need to address in regards to
the Debian packaging on this and I will likely be uploading further
revisions in the coming days.



I did not build the package. My comment:

There are many lintian info warnings that can be fixed easily:


I no-symbols-control-file
usr/lib/x86_64-linux-gnu/libfrrospfapiclient.so.0.0.0
usr/lib/x86_64-linux-gnu/libfrr.so.0.0.0

https://wiki.debian.org/UsingSymbolsFiles


I possible-documentation-but-no-doc-base-registration
I spelling-error-in-binary  # a lot
I spelling-error-in-manpage  # a lot

I systemd-service-file-missing-documentation-key
lib/systemd/system/frr.service
O package-name-doesnt-match-sonames
libfrr0 libfrrospfapiclient0 (override comment: libfrr* are for 
internal use only and do not provide a stable API or ABI. soname / library 
versioning is irrelevant and they must always be shipped exact-matching to the 
daemons compiled against it)

  It is a package name. That's all.
  The lib can not be trusted?


O systemd-service-file-refers-to-unusual-wantedby-target
lib/systemd/system/frr.service network-online.target (override comment: 
we're a bit special since we provide network connectivity by starting up 
routing protocols.)
X duplicate-files
usr/share/doc/frr/examples/pbrd.conf.sample 
usr/share/doc/frr/examples/staticd.conf.sample

frr-rpki-rtrlib

I extended-description-is-probably-too-short
I hardening-no-fortify-functions
usr/lib/x86_64-linux-gnu/frr/modules/bgpd_rpki.so

frr source

I debian-control-has-obsolete-dbg-package
frr-dbg
I duplicate-long-description
frr-doc frr-pythontools
I ored-build-depends-on-obsolete-package
build-depends: dh-systemd  => use debhelper (>= 
9.20160709)
P debian-watch-does-not-check-gpg-signature
P package-uses-old-debhelper-compat-version
9

There is a problem with version 11?
 
O alternatively-build-depends-on-python-sphinx-and-python3-sphinx

(override comment: these are for build-compatibility on older distros 
(e.g. Ubuntu 14.04))

It is a new package. It is preferable to not upload Python 2
X upstream-metadata-file-is-missing



Regards,
Herbert

Bug#908629: RFS: biometric-authentication/0.9.55-1 [ITP]

[Herbert Fortes]

Hi,

On Wed, 12 Sep 2018 10:54:44 +0800 handsome_feng  
wrote:

> Package: sponsorship-requests
> Severity: wishlist
>
> Dear mentors,
>
> I am looking for a sponsor for my package "biometric-authentication"

About these lintians:

I: libbiometric0: hardening-no-bindnow 
usr/lib/x86_64-linux-gnu/libbiometric.so.0.0.0
I: libbiometric0: symbols-file-missing-build-depends-package-field
I: biometric-auth: hardening-no-bindnow 
usr/lib/biometric-authentication/biometric-authenticationd

Please, in debian/rules:

-# See debhelper(7) (uncomment to enable)
-# output every command that modifies files on the build system.
-#DH_VERBOSE = 1

DH_VERBOSE = 1


-# see EXAMPLES in dpkg-buildflags(1) and read /usr/share/dpkg/*
-DPKG_EXPORT_BUILDFLAGS = 1
-include /usr/share/dpkg/default.mk

-# see FEATURE AREAS in dpkg-buildflags(1)
-#export DEB_BUILD_MAINT_OPTIONS = hardening=+all

export DEB_BUILD_MAINT_OPTIONS = hardening=+all

-# see ENVIRONMENT in dpkg-buildflags(1)
-# package maintainers to append CFLAGS
-#export DEB_CFLAGS_MAINT_APPEND  = -Wall -pedantic
-# package maintainers to append LDFLAGS
-#export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed

export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed


Another lintian:

I: libbiometric0: symbols-file-missing-build-depends-package-field


It is a whislist and I do not know how to fix it. But

the version in it is not 0.9.56. The version that will

be in Debian. Please redo the file.


debian/copyright fiel does not seems right. The way it

is everything belongs to:

- Copyright: 2018, jianglinxuan 


But your name is in debian changelog and control(as uploader)

files.


The copyright headers says:

* Copyright (C) 2018 Tianjin KYLIN Information Technology Co., Ltd.

* Author: Droiing 


At least two entries in debian/copyright:

Files: *

Copyright: Tianjin etc

Comment: author Doiing email

License:


Files: debian/*

Copyright: 2018 you email

License:




Regards,

Herbert


> * Package name : biometric-authentication
> Version : 0.9.55-1
> Upstream Author : jianglinxuan 
> * URL : https://salsa.debian.org/kylin-team/biometric-
> authentication
> * License : LGPL-3+
> Section : admin
>
> It builds those binary packages:
>
> biometric-auth - Biometric Authentication Service
> biometric-driver-community-multidevice - Biometric Authentication Driver
> (community multidevice)
> biometric-utils - Biometric authentication utils
> libbiometric-dev - Biometric Identification DRIVER API - development files
> libbiometric0 - Biometric Identification library
>
> To access further information about this package, please visit the following
> URL:
>
> https://mentors.debian.net/package/biometric-authentication
>
>
> Alternatively, one can download the package with dget using this command:
>
> dget -x https://mentors.debian.net/debian/pool/main/b/biometric-
> authentication/biometric-authentication_0.9.55-1.dsc
>
> More information about this can be obtained from https://github.com/ukui.
>
>
> Regards,
> handsome_feng
>
>
>
> -- System Information:
> Debian Release: buster/sid
> APT prefers unstable
> APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.17.0-3-amd64 (SMP w/2 CPU cores)
> Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), 
LANGUAGE=zh_CN:zh (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
>

Bug#908629: RFS: biometric-authentication/0.9.55-1 [ITP]

[Herbert Fortes]

>
> Another lintian:
>
> I: libbiometric0: symbols-file-missing-build-depends-package-field
>
>
> It is a whislist and I do not know how to fix it. But
>
> the version in it is not 0.9.56. The version that will
>
> be in Debian. Please redo the file.
>
>


As an information, lintian stops with:

libbiometric.so.0 libbiometric0 #MINVER#
* Build-Depends-Package: libbiometric-dev
 bio_base64_decode@Base 0.9.56
 bio_base64_encode@Base 0.9.56
 bio_check_app_api_version@Base 0.9.56
[...]


But I am not 100% sure. I do not have

this knowledge.


To do a symbols file: https://wiki.debian.org/UsingSymbolsFiles




Regards,

Herbert

Bug#913261: RFS: chkboot/1.2-1 [ITP]

[Herbert Fortes]

Hi,
On 08/11/2018 17:30, Baptiste BEAUPLAT wrote:

Package: sponsorship-requests
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

   Dear mentors,

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


The package does not build twice in a row:

dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building chkboot using existing ./chkboot_1.2.orig.tar.gz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: local changes detected, the modified files are:
 chkboot-1.2/man/chkboot-check.8
 chkboot-1.2/man/chkboot-desktopalert.8
 chkboot-1.2/man/chkboot.8
dpkg-source: error: aborting due to unexpected upstream changes, see 
/tmp/chkboot_1.2-1.diff.PNYbwP

Please clean these files.



Regards,
Herbert





  * Package name: chkboot
Version : 1.2-1
Upstream Author : Giancarlo Razzolini 
  * URL : https://github.com/grazzolini/chkboot
  * License : GPL-2.0+
Section : utils

   It builds those binary packages:

 chkboot- detection of malicious changes for boot files

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

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

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

 dget -x 
https://mentors.debian.net/debian/pool/main/c/chkboot/chkboot_1.2-1.dsc

   This is the first release of the package.

   Debian source is hosted on salsa, at:

 https://salsa.debian.org/debian/chkboot

   Regards,
 Baptiste BEAUPLAT - lyknode

-BEGIN PGP SIGNATURE-

iIcEARYIAC8WIQQt4kiVMTxdp/CJ4U4XSUsQeV3XMwUCW+SOxhEcbHlrbm9kZUBj
aWxnLm9yZwAKCRAXSUsQeV3XM9WlAP93vo64ZSAwvMJ0cnxLBPMTUFGmgipjC6uJ
9rdGnmkKagD9GSoBOM674HGZ2kRlmEncJ6mLS0FKUdqXnc2hShdPRw4=
=nA8y
-END PGP SIGNATURE-

Bug#906721: RFS: plowshare/2.1.7-2

[Herbert Fortes]

Hi Carl Suster,


> Package: sponsorship-requests
> Severity: normal
>
> Dear mentors,
>
> I am looking for a sponsor for my package "plowshare" and the related
> package "plowshare-modules". The main reason this is worth an upload is
> that I'm shifting the way the two packages are related in order to
> follow upstream recommendations. Specifically plowshare-modules should
> be kept out of Debian releases (but I intend to keep it in unstable
> hence the placeholder RC bug to prevent migration), and this requires a
> slight adjustment in the dependencies of plowshare itself.
>
> Package name : plowshare
> Version : 2.1.7-2
> URL : https://salsa.debian.org/arcresu-guest/plowshare
> Section : web
>
> It builds these binary packages:
>
> plowshare - download and upload files from file sharing websites
> plowshare4 - transitional dummy package
>
> AND
>
> Package name : plowshare-modules
> Version : 0~git20180325.e4bd365-1
> URL : https://salsa.debian.org/arcresu-guest/plowshare-modules
> Section : web
>
> It builds these binary packages:
>
> plowshare-modules - plowshare drivers for various file sharing websites
>
> Getting the packages:
>
> https://mentors.debian.net/package/plowshare
> https://mentors.debian.net/package/plowshare-modules
>
> dget -x
> https://mentors.debian.net/debian/pool/main/p/plowshare/plowshare_2.1.7-2.dsc
> dget -x
> 
https://mentors.debian.net/debian/pool/main/p/plowshare-modules/plowshare-modules_0~git20180325.e4bd365-1.dsc
>
> Changes since the last upload:
>
> plowshare (2.1.7-2) unstable; urgency=medium
>
> * Update VCS to point to Salsa.
> * Correct typo in patch description.
> * Update debhelper compat to 11 (no changes).
> * Update to standards version 4.2.0:
> - use HTTPS URL in changelog.
> * Set Rules-Requires-Root to no.
> * De-emphasise plowshare-modules in favour of plowmod:
> - drop from Recommends to Suggests and
> - promote git from Suggests to Recommends since the plowmod script
> that replaces the modules package requires git.
>
> -- Carl Suster  Tue, 14 Aug 2018 10:54:27 +1000


I do not understand why the change in  the

debian/changelog file related to the current

version in Debian SID:


-  * Update to Standards-Version 4.1.1: no changes.
+  * Update to Standards-Version 4.0.0: no changes.

In the repository '4.1.1' seems to be the correct number:

https://salsa.debian.org/arcresu-guest/plowshare-modules/blob/debian/0_git20171112.e94a905-1/debian/control#L7


Please update debian/copyright file.




Regards,

Herbert

Bug#910245: RFS: engauge-digitizer/10.10+ds.1-1

[Herbert Fortes]

On 10/8/18 3:55 PM, Tobias Winchen wrote:

Dear Herbert,

I executed cowbuilder 2x in a fresh virtual machine and could not reproduce
this problem. Please let me know if I can do anything else.



Something was wrong with cowbuilder here. I reinstall it.
Then the package was compiled.

Uploading. Thanks!



Regards,
Herbert

Bug#906721: RFS: plowshare/2.1.7-2

[Herbert Fortes]

On 9/30/18 2:43 AM, Carl Suster wrote:

Hi Herbert,

Thanks for looking at my packages. I'm not really sure how the old changelog 
diff happened other than that the commit responsible must have been lost 
somewhere in the migration of the repository from GitHub to GitLab to salsa. I 
fixed the changelog in a new commit.

What did you want me to update about the copyright? Whenever I do a new 
snapshot I go through the upstream diff to check for copyright statement 
changes and I didn't notice anything. I've now updated the year range for the 
packaging copyright in case that's what you meant.



Some people update the upstream part by release. Not
only by copyright statement changes. The release has
2018 so I asked about it. Instead of '2010-2015',
'2010-2018'. This is not a problem.

I did ask because maybe it was forgotten to be updated,
as the year range for the packaging.

Package uploaded. Thanks for your work!



Regards,
Herbert

Bug#910134: RFS: dmidecode/3.2-1

[Herbert Fortes]

Hi,

On 10/3/18 3:58 AM, Jörg Frings-Fürst wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package: sponsorship-requests
Severity: normal

Dear mentors,

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


There are two changes made by Jean Delvare that is not
in debian/copyright:

+++ dmidecode-3.2/dmidecode.c   2018-09-14 10:52:12.0 -0300
@@ -2,7 +2,7 @@
  * DMI Decode
  *
  *   Copyright (C) 2000-2002 Alan Cox 
- *   Copyright (C) 2002-2017 Jean Delvare 
+ *   Copyright (C) 2002-2018 Jean Delvare 
--
+++ dmidecode-3.2/util.c2018-09-14 10:52:12.0 -0300
@@ -2,7 +2,7 @@
  * Common "util" functions
  * This file is part of the dmidecode project.
  *
- *   Copyright (C) 2002-2017 Jean Delvare 
+ *   Copyright (C) 2002-2018 Jean Delvare 


debian/copyright:

Files: *
Copyright: 2002-2017 Jean Delvare 


Can you please update it?



Regards,
Herbert





Package name: dmidecode
Version : 3.2-1
Upstream Author : dmidecode-de...@nongnu.org
URL : https://nongnu.org/dmidecode/
License : GPL-2+
Section : utils

   It builds those binary packages:

  dmidecode  - SMBIOS/DMI table decoder
  dmidecode-udeb - SMBIOS/DMI table decoder (udeb) (udeb)

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

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


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

   dget -x 
https://mentors.debian.net/debian/pool/main/d/dmidecode/dmidecode_3.2-1.dsc

or

   git https://jff.email/cgit/dmidecode.git/?h=release%2Fdebian%2F3.2-1
   



   Changes since the last upload:

   * New upstream release:
 - Refresh patches.
   * Declare compliance with Debian Policy 4.2.1 (No changes needed).
   * debian/dmidecode.docs:
 - Add README.


   Regards,
Jörg Frings-Fürst
- -- 
New:

GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema:  SYR8SJXB
Wire: @joergfringsfuerst
Skype:joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list:
  - Please send me a picture from the nature at your home.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAlu0aJAACgkQCfifPIyh
0l3QTRAAxgVCTNtbAQVGR1cjiMKaTUsw95jOxvuIDdsuqjxSwIG5LRt6BODCsbrH
3noioF6dzKo2NrSg3YDDNrqGI44CKmoJMH6h5HRz3Hg3HU7NMxWCP6z8ZflY6w1n
po/xY3TNo50xyY7Pq7g0G0458oy1FIiFHMJOgsRo/pe9WD++99cnpHX4gSM8vrgu
pXAMpeo7KpDn7cYQFUbX8F1/aiLVlnwX0wk2lTXU5lWIjnzuCiGLeXDurj1itum1
wzSkSH9jQ9Gvr2OLPc5opXzSu6WRWR7v0xFh60oj97rsqk0GTRzOe8mEJP1PpQA6
NQmrXqjkWtJ+DmAY2XjU93xpTQzczeD8Fxbsh28kBJSSr9IapkPDLH9GO9P/k03s
Qbc+ZcwBl+AOyCGnbY3AZK88hor2LpgGtiZN9wgY4UbRpoMOF0jY3e0siqrpzN+N
lQYA2K8rH4v6laCPjzdjw/AqZFXn7wEx2tIkqSoflxt9Qlp74b398SlqiUYKbUM1
jpQFSPUN73TN50VgLK7kv4o69T480LeIivRWbvhzY6CTFfzZyhx4Gz+7q230U/1O
Km3fBZXVd2SbHXn+9idKA1KUDARMnS0pMcqNJuBYH5m3LdAkxLVADV2QqoYkGcsd
bUHW6j6Tn4KzIrbtoL5JfES2o1jNxxAY/rKUwq17qeApcw/HYoE=
=g7Ry
-END PGP SIGNATURE-

Bug#910245: RFS: engauge-digitizer/10.10+ds.1-1

[Herbert Fortes]

Hi,

On 10/3/18 4:16 PM, Tobias Winchen wrote:

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "engauge-digitizer"


I ran 'cowbuilder' 2x and got this error:
# cowbuilder --build engauge-digitizer_10.10+ds.1-1.dsc

cklistWizardPoints.o src/.objs/moc_TutorialStateColorFilter.o 
src/.objs/moc_TutorialStateContext.o 
src/.objs/moc_TutorialStateCurveSelection.o 
src/.objs/moc_TutorialStateCurveType.o 
src/.objs/moc_TutorialStateIntroduction.o 
src/.objs/moc_TutorialStatePointMatch.o 
src/.objs/moc_TutorialStateSegmentFill.o src/.objs/moc_ViewPreview.o 
src/.objs/moc_ViewProfileDivider.o src/.objs/moc_WindowAbstractBase.o 
src/.objs/moc_WindowTable.o src/.objs/moc_LoadImageFromUrl.o 
src/.objs/moc_NetworkClient.o src/.objs/moc_DlgImportCroppingPdf.o   -L//lib 
-L/lib -lfftw3 -llog4cpp -lopenjp2 -lpoppler-qt5 -lQt5PrintSupport -lQt5Help 
-lQt5Widgets -lQt5Gui -lQt5Xml -lQt5Sql -lQt5Network -lQt5Core -lpthread -lGL
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:1707: bin/engauge] Error 1
make[2]: Leaving directory '/build/engauge-digitizer-10.10+ds.1'
dh_auto_build: make -j1 returned exit code 2
make[1]: *** [debian/rules:22: override_dh_auto_build] Error 25
make[1]: Leaving directory '/build/engauge-digitizer-10.10+ds.1'
make: *** [debian/rules:11: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
I: copying local configuration
E: Failed autobuilding of package
I: unmounting dev/ptmx filesystem
I: unmounting dev/pts filesystem
I: unmounting dev/shm filesystem
I: unmounting proc filesystem
I: unmounting sys filesystem
I: Cleaning COW directory
I: forking: rm -rf /var/cache/pbuilder/build/cow.17395


Can you please check it?



Regards,
Herbert


















  * Package name: engauge-digitizer
Version : 10.10+ds.1-1
   Upstream Author : Mark Mitchell 
  * URL : https://github.com/markummitchell/engauge6
  * License : GPL-2+
Section : science

  It builds those binary packages:

 engauge-digitizer - interactively extracts numbers from bitmap graphs or
maps
  engauge-digitizer-doc - engauge-digitizer user manual and tutorial

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

   https://mentors.debian.net/package/engauge-digitizer

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

 dget -x https://mentors.debian.net/debian/pool/main/e/engauge-digitizer/
engauge-digitizer_10.10+ds.1-1.dsc

   Changes since the last upload:

   * New upstream release
   * Updated to standards version 4.2.1


Bests,
Tobias Winchen

Bug#909134: RFS: budgie-extras/0.6.1-1

[Herbert Fortes]

Hi David Mohammed,


Package: sponsorship-requests
Severity: normal

   Dear mentors,

   I am looking for a sponsor for my package "budgie-extras"


I did a review and have two questions:

 The budgie-quicknote/QuickNoteApplet.vala file is GPL-2+. It
does not have an entry in debian/copyright. All project is GPL-3+
only.

 Did you mixed debian/changelog (Debian and Ubuntu) being aware
of that? I do not think it is good. It tends to confuse the projects.



Regards,
Herbert






  * Package name: budgie-extras
Version : 0.6.1-1
Upstream Author : Ubuntu Budgie Developers
  * URL : https://github.com/ubuntubudgie/budgie-extras
  * License : GPL-3+
Section : misc

   It builds those binary packages:

 budgie-app-launcher-applet - Applet to provide an alternative
means to launch applications
  budgie-clockworks-applet - Applet to display clock across multiple time zones
  budgie-countdown-applet - Applet providing a countdown capability on
the Budgie Desktop
  budgie-dropby-applet - Applet to popup when a USB device is connected
  budgie-hotcorners-applet - Applet providing hotcorners capabilities
for the Budgie Desktop
  budgie-kangaroo-applet - Applet to allow quick file-browsing
  budgie-keyboard-autoswitch-applet - Applet adding the ability to set
a different keyboard layout per
  budgie-previews-applet - Applet providing window previews
capabilities for the Budgie Desk
  budgie-quicknote-applet - Applet providing simple notes capability
for the Budgie Desktop
  budgie-recentlyused-applet - Applet displays files recently accessed
for the Budgie Desktop
  budgie-rotation-lock-applet - Applet to lock or unlock the screen rotation
  budgie-showtime-applet - Applet displaying date and time on the Budgie Desktop
  budgie-trash-applet - Applet allows access to trash capabilities for
the Budgie Desktop
  budgie-weathershow-applet - Applet to display the weather and forecast
  budgie-window-mover-applet - Applet allows moving windows between
workspaces for the Budgie De
  budgie-workspace-overview-applet - Applet providing quick access to
workspaces for the Budgie Deskto
  budgie-workspace-wallpaper-applet - Applet providing per workspace wallpaper

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

   https://mentors.debian.net/package/budgie-extras


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

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

Notes:
linitan -i -I --pedantic run on the built source and is lintian free
check-all-the-things run on the source and corrections made to the source
pbuilder-dist run to ensure builds correctly for unstable

This upload introduces new built binaries to be authorised by
archive-admins via the NEW queue:
- budgie-trash-applet
- budgie-recentlyused-applet
- budgie-app-launcher-applet
- budgie-weathershow-applet
- budgie-hotcorners-applet
- budgie-quicknote-applet

   May I request that this package be added to my debian maintainers
list of packages I'm allowed to look after (dak
fossfree...@ubuntu.com) ?

   Changes since the last upload:

(Most recent changelog)

 * New upstream release
 - see ChangeLog for details
 - Consolidated release to resync Debian and Ubuntu versions
   * Packaging Changes:
 - Bump Standards-Version - no changes required

   Regards,
David Mohammed

Bug#909134: Info received (Bug#909134: RFS: budgie-extras/0.6.1-1)

[Herbert Fortes]

Uploaded. And also sent the dak-comands to FTP-Master too.
Enjoy!



Regards,
Herbert

Bug#920218: RFS: webcamoid/8.5.0+dfsg-1

[Herbert Fortes]

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

Re: Bug#920218: RFS: webcamoid/8.5.0+dfsg-1

[Herbert Fortes]

On 1/23/19 4:14 AM, Sune Vuorela wrote:
> On 2019-01-22, Herbert Fortes  wrote:
>> akqml - full featured webcam capture application - qml module
> 
> shouldn't this be called qml-module-something instead ?

It is for Webcamoid only. I used the lib name.

/usr/lib/x86_64-linux-gnu/qt5/qml/AkQml/libAkQml.so
/usr/lib/x86_64-linux-gnu/qt5/qml/AkQml/qmldir

https://packages.debian.org/buster/amd64/akqml/filelist

> 
>> libavkys-dev - full featured webcam capture application - dev
> 
> Who are the consumers/users of this ?
> 
>> webcamoid-plugins - full featured webcam capture application - plugins
> 
> And this?
> 

I understood you are asking about other packages.
'apt-cache rdepends' says Webcamoid only.

Thanks for replying! But my new key was accepted
and I can take care of it by myself.



Regards,
Herbert
 

Bug#913363: RFS: desktopfolder/1.0.10-1 [ITP]

[Herbert Fortes]

On 07/12/2018 08:10, foss.freedom wrote:

It has been about a month since the initial package was uploaded to
mentors.  Still hoping for some feedback please.

Yesterday I've tweaked the package to remove an unnecessary
build-dependency after discussing with upstream.

I note one new "Information" lintian issue now occurs since the
initial upload.  Probably due to a slight tweak to the current debian
policy?

public-upstream-key-not-minimal
upstream/signing-key.asc has 1 extra signature(s) for keyid 92DED901DA15CC0D

Is this something I can deal with (if so how?) - or should I ask
upstream to create a signing-key.asc  for me using "gpg --armor
--export --export-options export-minimal,export-clean keyid"



The lintian tag is severity wishlist. But it is
good to save space in the archive.

"The package contains a public upstream signing key..."

The uscan man page says:

[...]
The armored keyring file debian/upstream/signing-key.asc can
be created by using the gpg (or gpg2) command as follows.
[...]

Did up try to run the command and see if there is any problem?

These would be my steps.

Bug#913261: RFS: chkboot/1.2-1 [ITP]

[Herbert Fortes]

On 21/11/2018 13:31, Baptiste BEAUPLAT wrote:

Hello Herbert,

I hope you are well.

I was wondering if you had time to take a second look at this package?



No.

I had to improve the Debian CI tests for some
of the packages I take care.

Anyone can take of that package if necessary.
I can not do it right now.



Regards,
Herbert

Bug#918580: RFS: libgphoto2/2.5.22-1

[Herbert Fortes]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package "libgphoto2" as I
  am without my key and no access to Salsa

 * Package name: libgphoto2
   Version : 2.5.22-1
   Upstream Author : Marcus Meissner and others
 * URL : https://github.com/gphoto/libgphoto2/
 * License : LGPL-2+
   Section : libs

  It builds those binary packages:

libgphoto2-6 - gphoto2 digital camera library
libgphoto2-dev - gphoto2 digital camera library (development files)
libgphoto2-dev-doc - gphoto2 digital camera library (development 
documentation)
libgphoto2-l10n - gphoto2 digital camera library - localized messages
libgphoto2-port12 - gphoto2 digital camera port library

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

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


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

dget -x 
https://mentors.debian.net/debian/pool/main/libg/libgphoto2/libgphoto2_2.5.22-1.dsc

  
  Changes since the last upload:


   * New upstream version 2.5.22
   * debian/control:
   - Bump Standards-Version from 4.2.1 to 4.3.0
   * debian/copyright:
  - Update year for myself
   * debian/watch:
  - sf.net only

It is a bugfix release.



Regards,
Herbert

Bug#918571: RFS: python-gphoto2/1.9.0-1

[Herbert Fortes]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package "python-gphoto2" as
  I am without my key and access to Salsa

 * Package name: python-gphoto2
   Version : 1.9.0-1
   Upstream Author : Jim Easterbrook 
 * URL : https://github.com/jim-easterbrook/python-gphoto2
 * License : GPL-3+
   Section : python

  It builds those binary packages:

python-gphoto2-doc - Python interface to libgphoto2 (common documentation)
python3-gphoto2 - Python interface to libgphoto2 (Python 3)

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

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


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

dget -x 
https://mentors.debian.net/debian/pool/main/p/python-gphoto2/python-gphoto2_1.9.0-1.dsc

  More information about python-gphoto2 can be obtained from 
https://www.example.com.

  Changes since the last upload:

  * New upstream version 1.9.0
  * debian/control:
  - Bump Standards-Version from 4.2.1 to .4.3.0
  * debian/copyright:
  - Update year for myself



Regards,
Herbert

Bug#906877: RFS: yuma123/2.11-1

[Herbert Fortes]

Em 15-09-2018 14:36, Vladimir Vassilev escreveu:

Hi Herbert,


I fixed this issue and updated the package now uploaded on mentors.debian.net

Removed the netconf/src/yangdiff/Makefile target from configure.ac with new 
patch 0004-Removed-unused-autoconf-targets.patch

Updated debian/changelog.

Tested a second build in pbuild environment which now works.

Will do second build as part of my release routine from now on.



Cool!

Upload done. As there are new packages. Let's wait FTP-Master.

Thank you for the working done.



Regards,
Herbert

Bug#906877: RFS: yuma123/2.11-1

[Herbert Fortes]

Hi Vladimir Vassilev,

> Package: sponsorship-requests
> Severity: normal
>
> Dear mentors,
>
> I am looking for a sponsor for my package "yuma123"

The package does not build twice because the generated
netconf/src/yangdiff/Makefile file.

Please add the file to dh_clean's routine. A debian/clean
file with 'netconf/src/yangdiff/Makefile' solves the
issue.



Regards,
Herbert

>
> * Package name    : yuma123
>   Version : 2.11-1
>   Upstream Author : Vladimir Vassilev 
> * URL :https://sourceforge.net/projects/yuma123
> * License : BSD
>   Section : net
>
> It builds those binary packages:
>
> libyangrpc-dev - NETCONF/YANG development files
> libyangrpc2 - NETCONF/YANG library for simple manager clients
> libyuma-base - Configuration script, YANG models and documentation
> libyuma-dev - NETCONF/YANG development files
> libyuma2 - NETCONF/YANG library
> netconfd - NETCONF (RFC-6241) agent
> netconfd-module-ietf-interfaces - SIL module for netconfd implementing
> ietf-interfaces.yang
> netconfd-module-ietf-system - SIL module for netconfd implementing
> ietf-system.yang
> yangcli - NETCONF/YANG command line client application
> yangdump - Validate YANG modules and convert them to different formats
>
>
> To access further information about this package, please visit the
> following URL:
>
> https://mentors.debian.net/package/yuma123
>
> Alternatively, one can download the package with dget using this command:
>
>     dget -x
> https://mentors.debian.net/debian/pool/main/y/yuma123/yuma123_2.11-1.dsc
>
> More information about yuma123 can be obtained
> fromhttp://yuma123.org/wiki   .
>
> Changes since the last upload:
>
> * New upstream release
>
> Regards,
> Vladimir Vassilev
>
>
>

Re: Lintian - pkg-config-references-unknown-shared-library

[Herbert Fortes]

On 2/15/19 10:34 AM, Andreas Metzler wrote:
> On 2019-02-15 Herbert Fortes  wrote:
>> I working on a Debian revison for libgphoto2 and
>> have this Lintian about pkg-config.
> 
>> pkg-config-references-unknown-shared-library
> 
>> The libgphoto2_port/libgphoto2_port.pc.in file has:
> 
>> Libs: -L${libdir} -lgphoto2 -lm
> [...]
> 
> Hello,
> Looks like a false positive, lintian warns about -lm, the full error is:
> W: libgphoto2-dev: pkg-config-references-unknown-shared-library 
> usr/lib/x86_64-linux-gnu/pkgconfig/libgphoto2.pc -lm (line 14)
> W: libgphoto2-dev: pkg-config-references-unknown-shared-library 
> usr/lib/x86_64-linux-gnu/pkgconfig/libgphoto2_port.pc -lm (line 12)
> 
> libm.so is shipped in libc6-dev. How about a bugreport?
> 

Yeah, I did not read right.

Thanks Andreas!



Regards,
Herbert