Bug#831061: RFS: newlisp/10.7.0-3

[Sergio Durigan Junior]

Package: sponsorship-requests
Severity: normal

Hi,

I'd like to get new changes to the newLISP package uploaded.  The
changes are:

  * Silence a warning when compiling on GNU/kFreeBSD.
When enabling builds on GNU/kFreeBSD, I forgot to forward-declare the
prototype for strptime, which generated a warning when compiling the
code.
  * Fix FTBFS on PowerPC 32-bit.
The fourth argument to semctl must be a 'union semun', but the
original code passes 0 instead.  This makes the build fail on PowerPC
32-bit, because of the calling convention for this architecture.
(Closes: #828807)

You can get the package here:

  dget -x 
https://mentors.debian.net/debian/pool/main/n/newlisp/newlisp_10.7.0-3.dsc

The mentors page for it is:

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

I am taking the liberty to Cc Gianfranco because he's uploaded my latest
changes to this package.

Additionally, I'd like to request DM rights for newLISP, if Gianfranco
is comfortable with it.  There is at least one major task (porting
newLISP to GNU/Hurd, which is almost complete) that will go in soon, and
it would be nice to be more independent to upload my changes.

Thank you,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


signature.asc
Description: PGP signature

Bug#829151: RFS: setcolortemperature/1.1-1 ITP

[Jacob Adams]

> On Jul 12, 2016, at 8:08 AM, Gianfranco Costamagna  
> wrote:
> 
> sponsoring soon!
> 
> thanks for your contribution to Debian!

Thank you for sponsoring my package Gianfranco! 

Cómo Exportar en la Venezuela de Hoy, Es Posible ?

[Luis Arriaga]

[1] web

[2] nuestros servicios

 forum

[3] contacto

servicios ofrecidos
transmaquina
transporte de carga y alquiler de maquinaria

estimados srs.


quedamos a sus ordenes como proveedores serios y motivados a prestarles un 
excelente servicio en toda venezuela.

en caso de necesitar servicios de:

transporte de carga
alquiler de maquinaria de construcción
alquiler de grúas telescopicas
tansporte de carga extradimensionada
transporte de cemento a granel

reciban un cordial saludo,

luis arriaga
gerente comercial
[4] ven...@transmaquina.com.ve
0424-1362899

[5] www.transmaquina.com.ve

[6] visitar página web

información adicional

cobertura geográfica
prestamos servicios en toda venezuela , ya que trabajamos como aliados en las 
principales ciudades del país.

venta de equipos
prestamos el servicio de venta de equipos. nos encargamos de publicidad de 
venta de camiones, gandolas, maquinaria, grúas y montacargas.
este mensaje fue enviado a t...@test.com por gerencia comercial - luis arriaga
caracas, miranda, venezuela, caracas, miranda  1070, venezuela

cancelar suscripción| administre su suscripción| remitir email| reportar abuso


 References:

1. u=5f04de7
2. u=5f04de7
3. u=5f04de9
4. mailto:ven...@transmaquina.com.ve
5. u=5f04dea
6. u=5f04deb

This message was sent to debian-mentors@lists.debian.org by 
ventadeequip...@transmaquina.com.ve

You can modify/update your subscription via the link below.

Unsubscribe from all mailings
http://benchemail.bmetrack.com/c/su?e=9B58DF=717D3=F60F9B9=5OxzrBLumxPynvuzaF1bp7%2FeNWSbTFLphENb71UYrR8%3D=D897DD9A


Manage Subscription
http://benchemail.bmetrack.com/c/s?e=9B58DF=717D3=F60F9B9=5OxzrBLumxPynvuzaF1bp7%2FeNWSbTFLphENb71UYrR8%3D=D897DD9A


Forward Email
http://benchemail.bmetrack.com/c/f?e=9B58DF=717D3=F60F9B9=5OxzrBLumxPynvuzaF1bp7%2FeNWSbTFLphENb71UYrR8%3D=D897DD9A


Report Abuse
http://benchemail.bmetrack.com/Abuse?e=9B58DF=717D3=F60F9B9=5OxzrBLumxPynvuzaF1bp7%2FeNWSbTFLphENb71UYrR8%3D=D897DD9A


Caracas, Miranda, Venezuela, Caracas, Miranda  1070, Venezuela

Email Marketing
BenchmarkEmail.com
 [http://benchemail.bmetrack.com]

Re: libgdbm transition

[Jakub Wilk]

* Tobias Frost , 2016-07-13, 21:17:
You will have to file all the bugs manually, but I expect all the bugs 
will follow a similar template.

You'll find mass-bug(1) from devscripts helpful on the filing part.


Unlikely. mass-bug(1) produces almost series of almost-identical mails 
that can vary only with package name and version. That's not enough to 
produce useful FTBFS bug reports.


Also, #556375 disqualifies mass-bug(1) as a serious tool for me.

--
Jakub Wilk

Re: libgdbm transition

[Sven Joachim]

On 2016-07-13 01:35 +0300, Dmitry Bogatov wrote:


> Some time ago I made gdbm_1.12-3 into experimental, and since it is 
> incompatible with
> gdbm-1.8 (new soname, separated compat library) I rebuilt all reverse 
> depedencies.
> Here is my report:
>
>   FAIL camldbm_1.0-2.dsc | PATCH
>   FAIL courier_0.73.1-1.6.dsc
>   FAIL freeradius_2.2.8+dfsg-0.1.dsc | PATCH
>   FAIL ifmail_2.14tx8.10-22.dsc | PATCH
>   FAIL nis_3.17-34.dsc | FTPFS pre-history debhelper
>   FAIL ntop_5.0.1+dfsg1-2.1.dsc | FTBFS issues with rrd
>   FAIL ocsigenserver_2.4.0-1.dsc | FTPFS issues with FindLib
>   FAIL perdition_2.1-2.dsc | PATCH
>   FAIL python3-stdlib-extensions_3.4.2-1.dsc | FTBFS purely virtual
>   FAIL qsf_1.2.7-1.dsc | PATCH
>   FAIL ruby2.3_2.3.1-5.dsc | FTBFS testsuite
>   FAIL sortmail_2.4-2.dsc | PATCH

Please recheck those, apparently several of these packages have newer
versions in unstable, and at least one of them (ntop) has been removed.
There is no point in test-building packages from stable.

Cheers,
   Sven

Re: libgdbm transition

[Tobias Frost]

Am Mittwoch, den 13.07.2016, 11:33 +0100 schrieb James Cowgill:

> You will have to file all the bugs manually, but I expect all the
> bugs will follow a similar template.

You'll find mass-bug(1) from devscripts helpful on the filing part.

> 
> James

-- 
tobi

Bug#830569: RFS: z3/4.4.1-0.1 [NMU] [4xRC]

[Fabian Wolff]

Control: reopen -1

I have

 - added Breaks + Replaces in debian/control
 - fixed the copyright information for hamiltonian.py
 - enabled most tests
 - enabled hardening flags

This should address the remaining issues the two of you found in the
previous package.

  https://mentors.debian.net/package/z3
  https://mentors.debian.net/debian/pool/main/z/z3/z3_4.4.1-0.1.dsc

Regards,
 Fabian

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

Bug#830569: marked as done (RFS: z3/4.4.1-0.1 [NMU] [4xRC])

[Gianfranco Costamagna]

control: reopen -1

reopening.
G.





Il Mercoledì 13 Luglio 2016 18:45, Debian Bug Tracking System 
 ha scritto:
Your message dated Wed, 13 Jul 2016 16:40:55 +
with message-id 
and subject line closing RFS: z3/4.4.1-0.1 [NMU] [4xRC]
has caused the Debian Bug report #830569,
regarding RFS: z3/4.4.1-0.1 [NMU] [4xRC]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
830569: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830569
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problemsPackage: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for a NMU of the z3 package.

The update attempts to fix four RC bugs currently reported for z3.

Changes since the last upload:

   * New upstream release.
   * Remove patches that were fixed upstream:
  - signed_char01
  - signed_char02
  - signed_char03
  - signed_char04
  - disable_test
  - disable_test2
  - disable_test3
  - disable_test4 (upstream issue has been closed:
https://github.com/Z3Prover/z3/issues/210)
  - fix_conflict
   * Migrate remaining patches to DEP-3 format.
   * Rewrite typos.patch to apply to new version of z3.
   * Add patch fix-dotnet-version.patch (Closes: #808695).
   * Upgrade to Standards version 3.9.8 (no changes).
   * Install shared libraries into new libz3-4 package (Closes: #819884).
   * Install python files directly into /usr/lib/python2.7/dist-packages/
 (Closes: #802272).
   * Clean up debian/rules.
   * Remove unnecessary version restriction of build dependency
 cli-common-dev.
   * Format debian/control with cme.
   * Fix debian/copyright: Change MIT to Expat and move Expat license text
 into separate license block so that it covers both file blocks.
   * Move libz3-ocaml-dev into section ocaml.
   * Add preinst scripts to remove directories from older versions to allow
 debhelper to install symlinks (Closes: #823573).
   * Disable tests as they fail eventually.

As for the Lintian warnings: I've tried building z3 with hardening
flags turned on, but the build failed. I don't know what the problem
with the -dev package is; contrary to what Lintian claims, it *does*
contain a symlink to the respective shared library.

There are a few other issues that I was not able to fix, but I think
closing the four RC bugs has a higher priority right now.

The package is available on Mentors:

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

  dget -x https://mentors.debian.net/debian/pool/main/z/z3/z3_4.4.1-0.1.dsc

Regards,
Fabian Wolff

Package z3 has been removed from mentors.

Bug#830569: marked as done (RFS: z3/4.4.1-0.1 [NMU] [4xRC])

[Debian Bug Tracking System]

Your message dated Wed, 13 Jul 2016 16:40:55 +
with message-id 
and subject line closing RFS: z3/4.4.1-0.1 [NMU] [4xRC]
has caused the Debian Bug report #830569,
regarding RFS: z3/4.4.1-0.1 [NMU] [4xRC]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
830569: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830569
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for a NMU of the z3 package.

The update attempts to fix four RC bugs currently reported for z3.

Changes since the last upload:

   * New upstream release.
   * Remove patches that were fixed upstream:
  - signed_char01
  - signed_char02
  - signed_char03
  - signed_char04
  - disable_test
  - disable_test2
  - disable_test3
  - disable_test4 (upstream issue has been closed:
 https://github.com/Z3Prover/z3/issues/210)
  - fix_conflict
   * Migrate remaining patches to DEP-3 format.
   * Rewrite typos.patch to apply to new version of z3.
   * Add patch fix-dotnet-version.patch (Closes: #808695).
   * Upgrade to Standards version 3.9.8 (no changes).
   * Install shared libraries into new libz3-4 package (Closes: #819884).
   * Install python files directly into /usr/lib/python2.7/dist-packages/
 (Closes: #802272).
   * Clean up debian/rules.
   * Remove unnecessary version restriction of build dependency
 cli-common-dev.
   * Format debian/control with cme.
   * Fix debian/copyright: Change MIT to Expat and move Expat license text
 into separate license block so that it covers both file blocks.
   * Move libz3-ocaml-dev into section ocaml.
   * Add preinst scripts to remove directories from older versions to allow
 debhelper to install symlinks (Closes: #823573).
   * Disable tests as they fail eventually.

As for the Lintian warnings: I've tried building z3 with hardening
flags turned on, but the build failed. I don't know what the problem
with the -dev package is; contrary to what Lintian claims, it *does*
contain a symlink to the respective shared library.

There are a few other issues that I was not able to fix, but I think
closing the four RC bugs has a higher priority right now.

The package is available on Mentors:

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

  dget -x https://mentors.debian.net/debian/pool/main/z/z3/z3_4.4.1-0.1.dsc

Regards,
 Fabian Wolff
--- End Message ---
--- Begin Message ---
Package z3 has been removed from mentors.--- End Message ---

Re: more recent version with python3 support

[Herbert Fortes]

Hi Tiago,


> On 12 July 2016 at 16:46, Herbert Fortes  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

Re: more recent version with python3 support

[Gianfranco Costamagna]

Hi!


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

Gianfranco

Re: Packaging new upstream version of scid

[Gianfranco Costamagna]

Hi,

>I have been working on packaging a new version of scid (4.6.2); the version in 
>Debian is outdated (from 2014).
>I tried to contact Oliver, the actual mantainer, a month ago and haven't 
>received response yet. I tried it twice.


The maintainer has an ongoing MIA process, and he didn't answer to them since a 
month or so
(if I understand correctly the query of course)
>I did a NMU and the work can be reviewed on [0].


please user mentors.debian.org too :)

>What should I do? Wait a little bit more or should I fill a RFS bug?


I did *two* NMU of stockfish for this maintainer, both were new upstream 
release, and upstream was making pressure
about updating it.

So, even if the maintainer is not officially MIA, I guess you can already open 
an RFS bug, that I can sponsor if
the following conditions are met:
1) you bump severity of 802196 to important and explain why the new version is 
important to go in unstable

2) you fix also 772432 (just apply the patch or check if the new upstream 
release fixes that bug)
3) you try to see how and which bugs are fixed in the new release
4) you open an RFS bug


if the review is good, I'll upload in deferred/15 or somewhere in that deferred 
queue.

(and I think MIA team might orphan the package in the following days, so I'll 
probably ask you
to convert in a Team upload, or Qa upload, or to add yourself as maintainer of 
the package)


I should admit some changes are useless/out of an NMU scope, so maybe if you 
want to wait for him
to step in, or MIA team to orphan the package, I can sponsor even more easily 
the package.

cheers,
and thanks in advance for your work :)

G.

Packaging new upstream version of scid

[Jose G. López]

Hello!

I have been working on packaging a new version of scid (4.6.2); the version in 
Debian is outdated (from 2014).
I tried to contact Oliver, the actual mantainer, a month ago and haven't 
received response yet. I tried it twice.

I did a NMU and the work can be reviewed on [0].

What should I do? Wait a little bit more or should I fill a RFS bug?

Thanks in advance!

Regards,

[0] https://gitlab.com/deb-pkg/scid.git


pgp_CB4kBfgtM.pgp
Description: PGP signature

Re: libgdbm transition

[James Cowgill]

On Wed, 2016-07-13 at 07:35 +0100, Rebecca N. Palmer wrote:
> > We do not have automation
> > to rebuild packages and file FTBFS bugs, do we?
> 
> Automated whole-archive rebuilds have been done (see e.g. 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768691 ), but I
> don't know whether they are done regularly.

I think Dmitry is referring to the rebuilding of libgdbm reverse
dependencies which will be needed for this transition.

This is automated by the release team (see the transitions policy) once
a transition starts. For the transition to start, either all the FTBFS
bugs you found need to be fixed in unstable, or the packages in
question need removing from testing. You will have to file all the bugs
manually, but I expect all the bugs will follow a similar template.

James

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

Re: libgdbm transition

[Rebecca N. Palmer]

It looks as MBF, but I would like someone more experienced to give advice.


The transitions policy is here:
https://wiki.debian.org/Teams/ReleaseTeam/Transitions


We do not have automation
to rebuild packages and file FTBFS bugs, do we?


Automated whole-archive rebuilds have been done (see e.g. 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768691 ), but I don't 
know whether they are done regularly.