Bug#893522: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

  sagemath |   8.1-2+b1 | armel

--- Reason ---
ROM; FTB on buildds
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 893...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/893522

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#892125: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

   gazebo7 | 7.8.1+dfsg-4+b1 | arm64, armel, armhf, mips, mips64el, mipsel, 
s390x
gazebo7-plugin-base | 7.8.1+dfsg-4+b1 | arm64, armel, armhf, mips, mips64el, 
mipsel, s390x
libgazebo7 | 7.8.1+dfsg-4+b1 | arm64, armel, armhf, mips, mips64el, mipsel, 
s390x
libgazebo7-dev | 7.8.1+dfsg-4+b1 | arm64, armel, armhf, mips, mips64el, mipsel, 
s390x

--- Reason ---
NBS; gazebo is now only built on amd64 and i386
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 892...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/892125

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#890838: marked as done (duplicate "Example" in a docstring causes FTBFS due to sphinx in dependent package(s))

[Debian Bug Tracking System]

Your message dated Tue, 20 Feb 2018 01:23:43 +
with message-id <e1enwel-0008eh...@fasolo.debian.org>
and subject line Bug#890838: fixed in sympy 1.1.1-4
has caused the Debian Bug report #890838,
regarding duplicate "Example" in a docstring causes FTBFS due to sphinx in 
dependent package(s)
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.)


-- 
890838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890838
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-sympy
Version: 1.1.1-3
Severity: important
Tags: upstream

I am trying to update  python-nipy package and it FTBFS due to docs
failing to build, because sphinx parses imported interfaces as well and pukes 
due to
https://github.com/numpy/numpydoc/issues/115
since there is two Examples within a single docstring 

$> dpkg -L python-sympy | xargs grep -A30 'Returns the atoms that form the 
current' 2>/dev/null
/usr/lib/python2.7/dist-packages/sympy/core/basic.py:"""Returns the 
atoms that form the current object.
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-   By default, 
only objects that are truly atomic and can't
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-   be divided into 
smaller pieces are returned: symbols, numbers,
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-   and number 
symbols like I and pi. It is possible to request
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-   atoms of any 
type, however, as demonstrated below.
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-   Examples
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-   
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-   >>> from sympy 
import I, pi, sin
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-   >>> from 
sympy.abc import x, y
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-   >>> (1 + x + 
2*sin(y + I*pi)).atoms()
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-   {1, 2, I, pi, 
x, y}
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-   If one or more 
types are given, the results will contain only
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-   those types of 
atoms.
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-   Examples
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-   
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-   >>> from sympy 
import Number, NumberSymbol, Symbol
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-   >>> (1 + x + 
2*sin(y + I*pi)).atoms

It was fixed upstream (attaching the commit patch, adjusted for 1 line offset
against our version).  I will prepare team upload now to fix it, hopefully
there is no objections

Cheers,

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (600, 'unstable'), (300, 'experimental'), (100, 
'unstable-debug'), (100, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-3-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)
LSM: AppArmor: enabled

Versions of packages python-sympy depends on:
ii  python 2.7.14-4
ii  python-mpmath  1.0.0-1

Versions of packages python-sympy recommends:
ii  ipython 5.5.0-1
ii  python [python-ctypes]  2.7.14-4
ii  python-gmpy 1.17-3
ii  python-numpy1:1.13.3-2
ii  python-pil  5.0.0-1
ii  python-pyglet   1.3.0-1

Versions of packages python-sympy suggests:
ii  dvipng   1.15-1
ii  python-sympy-doc 1.1.1-2
ii  texlive-fonts-extra  2017.20180103-2

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: sympy
Source-Version: 1.1.1-4

We believe that the bug you reported is fixed in the latest version of
sympy, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be c

Bug#890838: duplicate "Example" in a docstring causes FTBFS due to sphinx in dependent package(s)

[Yaroslav Halchenko]

Package: python-sympy
Version: 1.1.1-3
Severity: important
Tags: upstream

I am trying to update  python-nipy package and it FTBFS due to docs
failing to build, because sphinx parses imported interfaces as well and pukes 
due to
https://github.com/numpy/numpydoc/issues/115
since there is two Examples within a single docstring 

$> dpkg -L python-sympy | xargs grep -A30 'Returns the atoms that form the 
current' 2>/dev/null
/usr/lib/python2.7/dist-packages/sympy/core/basic.py:"""Returns the 
atoms that form the current object.
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-   By default, 
only objects that are truly atomic and can't
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-   be divided into 
smaller pieces are returned: symbols, numbers,
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-   and number 
symbols like I and pi. It is possible to request
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-   atoms of any 
type, however, as demonstrated below.
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-   Examples
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-   
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-   >>> from sympy 
import I, pi, sin
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-   >>> from 
sympy.abc import x, y
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-   >>> (1 + x + 
2*sin(y + I*pi)).atoms()
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-   {1, 2, I, pi, 
x, y}
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-   If one or more 
types are given, the results will contain only
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-   those types of 
atoms.
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-   Examples
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-   
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-   >>> from sympy 
import Number, NumberSymbol, Symbol
/usr/lib/python2.7/dist-packages/sympy/core/basic.py-   >>> (1 + x + 
2*sin(y + I*pi)).atoms

It was fixed upstream (attaching the commit patch, adjusted for 1 line offset
against our version).  I will prepare team upload now to fix it, hopefully
there is no objections

Cheers,

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (600, 'unstable'), (300, 'experimental'), (100, 
'unstable-debug'), (100, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-3-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)
LSM: AppArmor: enabled

Versions of packages python-sympy depends on:
ii  python 2.7.14-4
ii  python-mpmath  1.0.0-1

Versions of packages python-sympy recommends:
ii  ipython 5.5.0-1
ii  python [python-ctypes]  2.7.14-4
ii  python-gmpy 1.17-3
ii  python-numpy1:1.13.3-2
ii  python-pil  5.0.0-1
ii  python-pyglet   1.3.0-1

Versions of packages python-sympy suggests:
ii  dvipng   1.15-1
ii  python-sympy-doc 1.1.1-2
ii  texlive-fonts-extra  2017.20180103-2

-- no debconf information

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#887891: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

apertium-es-it | 0.1.0~r51165-1 | source, all

--- Reason ---
Replaced by apertium-spa-ita
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 887...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/887891

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#887890: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

apertium-es-ca | 1.2.1+svn~57448-4 | source, all

--- Reason ---
Replaced by apertium-spa-cat
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 887...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/887890

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#886669: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

python-pyfai | 0.13.0+dfsg-1+b1 | powerpc
python-pyfai | 0.13.0+dfsg-1+b2 | armel, hurd-i386, mips, mips64el, mipsel, 
ppc64el, s390x
python-pyfai-dbg | 0.13.0+dfsg-1+b1 | powerpc
python-pyfai-dbg | 0.13.0+dfsg-1+b2 | armel, hurd-i386, mips, mips64el, mipsel, 
ppc64el, s390x
python3-pyfai | 0.13.0+dfsg-1+b1 | powerpc
python3-pyfai | 0.13.0+dfsg-1+b2 | armel, hurd-i386, mips, mips64el, mipsel, 
ppc64el, s390x
python3-pyfai-dbg | 0.13.0+dfsg-1+b1 | powerpc
python3-pyfai-dbg | 0.13.0+dfsg-1+b2 | armel, hurd-i386, mips, mips64el, 
mipsel, ppc64el, s390x

--- Reason ---
RoQA; new build dependency python-pyopencl not available on these architectures
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 886...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/886669

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#883445: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

cl-tf2-msgs |   0.5.13-5 | all
cl-tf2-srvs |   0.5.13-5 | all
python-tf2-geometry-msgs |   0.5.13-5 | all
python-tf2-kdl |   0.5.13-5 | all
python-tf2-msgs |   0.5.13-5 | all
python-tf2-ros |   0.5.13-5 | all
python-tf2-sensor-msgs |   0.5.13-5 | all
ros-geometry-experimental |   0.5.13-5 | source

--- Reason ---
ROM; source package renamed to ros-geometry2
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 883...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/883445

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#882774: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

   freemat | 4.2+dfsg1-1+b2 | hurd-i386

--- Reason ---
RoQA; B-D clang not available
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 882...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/882774

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#882401: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

r-cran-scatterplot3d |   0.3-40-1 | all
scatterplot3d |   0.3-40-1 | source

--- Reason ---
ROM; binary package taken over by src:r-cran-scatterplot3d
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 882...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/882401

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#880876: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

r-cran-afex | 0.16-1-1+b1 | armel

--- Reason ---
ROM; transitively build-depends on nodejs
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 880...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/880876

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#877837: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

r-cran-spam |2.1-1-2 | hurd-i386

--- Reason ---
RoQA; B-D: r-cran-dotcall64 not available
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 877...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/877837

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#877835: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

r-cran-randomfields |   3.1.50-2 | hurd-i386

--- Reason ---
RoQA; transitive B-D r-cran-dotcall64 not available
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 877...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/877835

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#881612: debian-science: s/libalberta2-dev/libalberta-dev/

[Ansgar Burchardt]

Package: src:debian-science
Version: 1.7
Severity: normal
Control: block 878199 by -1

Please depend on libalberta-dev instead of libalberta2-dev (which is a
transitional package).

Ansgar

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Processed: debian-science: s/libalberta2-dev/libalberta-dev/

[Debian Bug Tracking System]

Processing control commands:

> block 878199 by -1
Bug #878199 [libalberta2-dev] please drop transitional package libalberta2-dev
878199 was not blocked by any bugs.
878199 was not blocking any bugs.
Added blocking bug(s) of 878199: 881612

-- 
878199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878199
881612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881612
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#878062: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

r-cran-knitr | 1.15.1-2+b1 | armel, hurd-i386
r-cran-knitr |   1.15.1-3 | powerpc

--- Reason ---
ROM; node.js not available
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 878...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/878062

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#784505: marked as done ([paraview] Qt4's WebKit removal)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 07:04:41 +
with message-id <e1duz3p-0004by...@fasolo.debian.org>
and subject line Bug#784505: fixed in paraview 5.4.1+dfsg1-1
has caused the Debian Bug report #784505,
regarding [paraview] Qt4's WebKit removal
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.)


-- 
784505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784505
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: paraview
Version: 4.1.0+dfsg+1-2
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4webkit-removal

Dear Debian Science Team <debian-science-maintainers@lists.alioth.debian.org>,

As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit
as announced in [announce].

[announce] 
<https://lists.debian.org/debian-devel-announce/2015/05/msg1.html>

Basically we are about to get the latest Qt4 point release and upstream is
migrating from WebKit to Bing in the Qt5 series, so we won't have much upstream
support for maintaining Qt4's WebKit.

In order to make this move, all packages directly or indirectly depending on
the Qt4's WebKit library have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4. In
order to ease the transition time we have provided Wheezy backports for Qt5.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

Ana,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: paraview
Source-Version: 5.4.1+dfsg1-1

We believe that the bug you reported is fixed in the latest version of
paraview, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 784...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Anton Gladky <gl...@debian.org> (supplier of updated paraview package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 20 Sep 2017 08:51:19 +0200
Source: paraview
Binary: paraview paraview-dev paraview-doc paraview-python
Architecture: source
Version: 5.4.1+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 
<debian-science-maintainers@lists.alioth.debian.org>
Changed-By: Anton Gladky <gl...@debian.org>
Description:
 paraview   - Parallel Visualization Application
 paraview-dev - Parallel Visualization Application. Development header files
 paraview-doc - Parallel Visualization Application. Comprehensive documentation
 paraview-python - Parallel Visualization Application. python-support
Closes: 784505 835002
Changes:
 paraview (5.4.1+dfsg1-1) unstable; urgency=medium
 .
   * [663aeb8] New upstream version 5.4.1+dfsg1
   * [df8c7f2] Refresh patches
   * [6c0e2d3] Some minor changes in d/rules and install files
   * [2dd50c2] Remove libqtwebkit-dev from build-depends. (Closes: #784505)
   * [546b2fd] Remove Christophe from uploaders. (Closes: #835002)
   * [e3a8012] Update d/copyright
Checksums-Sha1:
 5f038f77f8f4ff6b55b8cd48958a26c5819811ca 2899 paraview_5.4.1+dfsg1-1.dsc
 d1882f7bd3daf55d5c385373a6d35c301bc05a61 23840212 
paraview_5.4.1+dfsg1.orig.tar.xz
 99440ea88758d01e0aba8fe11c2be7d0d5d929da 31252 

Bug#875564: Removed package(s) from unstable

[Debian FTP Masters]

Version: 3.2.1+dfsg-1+rm

Dear submitter,

as the package clapack has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/875564

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#875564: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

   clapack | 3.2.1+dfsg-1 | source
libcblas-dev | 3.2.1+dfsg-1 | amd64, arm64, armel, armhf, kfreebsd-amd64, mips, 
mips64el, mipsel, powerpc, ppc64el, s390x
 libcblas3 | 3.2.1+dfsg-1 | amd64, arm64, armel, armhf, kfreebsd-amd64, mips, 
mips64el, mipsel, powerpc, ppc64el, s390x
libclapack-dev | 3.2.1+dfsg-1 | amd64, arm64, armel, armhf, kfreebsd-amd64, 
mips, mips64el, mipsel, powerpc, ppc64el, s390x
libclapack3 | 3.2.1+dfsg-1 | amd64, arm64, armel, armhf, kfreebsd-amd64, mips, 
mips64el, mipsel, powerpc, ppc64el, s390x
libctmg-dev | 3.2.1+dfsg-1 | amd64, arm64, armel, armhf, kfreebsd-amd64, mips, 
mips64el, mipsel, powerpc, ppc64el, s390x
  libctmg3 | 3.2.1+dfsg-1 | amd64, arm64, armel, armhf, kfreebsd-amd64, mips, 
mips64el, mipsel, powerpc, ppc64el, s390x

--- Reason ---
ROM; duplicate functionality; dead upstream
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 875...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/875564

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#875544: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

 ovito | 2.3.3+dfsg1-2+b5 | hurd-i386, kfreebsd-amd64, kfreebsd-i386, 
powerpc

--- Reason ---
RoQA; Obsolete Qt4 based binaries interfere with Qt4 removal
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 875...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/875544

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#875442: Removed package(s) from experimental

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from experimental:

 elmer-doc | 2014.10.23-1 | source, all

--- Reason ---
ROM; useless without elmerfem
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 875...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/875442

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#875441: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

 elmer-doc | 2014.02.06-1 | source, all

--- Reason ---
ROM; useless without elmerfem
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 875...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/875441

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#875397: Removed package(s) from experimental

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from experimental:

libtorch-thnn | 0~20160908-g9d7b9ea+dfsg-1 | mips, mipsel
libtorch-thnn | 0~20170204-g3a1b725+dfsg-1 | hurd-i386, i386, kfreebsd-i386
libtorch-thnn-dev | 0~20160908-g9d7b9ea+dfsg-1 | mips, mipsel
libtorch-thnn-dev | 0~20170204-g3a1b725+dfsg-1 | hurd-i386, i386, kfreebsd-i386

--- Reason ---
ANAIS; restricted to fewer architectures
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 875...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/875397

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#875347: Removed package(s) from experimental

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from experimental:

 elmer | 7.0.svn.6034+dfsg-2 | amd64, armel, i386, kfreebsd-amd64, 
kfreebsd-i386, powerpc, s390x
elmer-common | 7.0.svn.6034+dfsg-2 | all
 elmer-dbg | 7.0.svn.6034+dfsg-2 | amd64, armel, i386, kfreebsd-amd64, 
kfreebsd-i386, powerpc, s390x
  elmerfem | 7.0.svn.6034+dfsg-2 | source
elmergui-samples | 7.0.svn.6034+dfsg-2 | all
libelmer-dev | 7.0.svn.6034+dfsg-2 | amd64, armel, i386, kfreebsd-amd64, 
kfreebsd-i386, powerpc, s390x
libelmersolver-7.0 | 7.0.svn.6034+dfsg-2 | amd64, armel, i386, kfreebsd-amd64, 
kfreebsd-i386, powerpc, s390x
libelmersolver-dbg | 7.0.svn.6034+dfsg-2 | amd64, armel, i386, kfreebsd-amd64, 
kfreebsd-i386, powerpc, s390x

--- Reason ---
RoQA; missed both jessie and stretch
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 875...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/875347

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#784475: marked as done ([kbibtex] Qt4's WebKit removal)

[Debian Bug Tracking System]

Your message dated Mon, 11 Sep 2017 07:00:21 +
with message-id <e1drihh-00039r...@fasolo.debian.org>
and subject line Bug#784475: fixed in kbibtex 0.8~20170819git31a77b27e8e83836e-1
has caused the Debian Bug report #784475,
regarding [kbibtex] Qt4's WebKit removal
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.)


-- 
784475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784475
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kbibtex
Version: 0.4-4
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4webkit-removal

Dear Debian Science Maintainers 
<debian-science-maintainers@lists.alioth.debian.org>,

As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit
as announced in [announce].

[announce] 
<https://lists.debian.org/debian-devel-announce/2015/05/msg1.html>

Basically we are about to get the latest Qt4 point release and upstream is
migrating from WebKit to Bing in the Qt5 series, so we won't have much upstream
support for maintaining Qt4's WebKit.

In order to make this move, all packages directly or indirectly depending on
the Qt4's WebKit library have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4. In
order to ease the transition time we have provided Wheezy backports for Qt5.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

Ana,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: kbibtex
Source-Version: 0.8~20170819git31a77b27e8e83836e-1

We believe that the bug you reported is fixed in the latest version of
kbibtex, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 784...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastien Roucariès <ro...@debian.org> (supplier of updated kbibtex package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 28 Aug 2017 16:12:42 +0200
Source: kbibtex
Binary: kbibtex kbibtex-data
Architecture: source all amd64
Version: 0.8~20170819git31a77b27e8e83836e-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 
<debian-science-maintainers@lists.alioth.debian.org>
Changed-By: Bastien Roucariès <ro...@debian.org>
Description:
 kbibtex- BibTeX editor for KDE
 kbibtex-data - BibTeX editor for KDE -- common data
Closes: 742974 784475
Changes:
 kbibtex (0.8~20170819git31a77b27e8e83836e-1) unstable; urgency=medium
 .
   * New upstream release
   * Bug fix: "new upstream release available", thanks to Gerrit Kruse
 (Closes: #742974).
   * Bug fix: "[kbibtex] Qt4s WebKit removal", thanks to Ana Guerrero
 Lopez (Closes: #784475).
Checksums-Sha1:
 8bc42442f139f88eb56049b1fc943b49ec15d7db 2739 
kbibtex_0.8~20170819git31a77b27e8e83836e-1.dsc
 666071a8351c653eea3440be355b213734345ace 7635908 
kbibtex_0.8~20170819git31a77b27e8e83836e.orig.tar.xz
 032d3ec37bdd9cfe0ad38a3c3d4013f25ee6e70c 16648 
kbibtex_0.8~20170819git31a77b27e8e83836e-1.debian.tar.xz
 a8a2135ca437690305aa40ef98bf58bf631d58b3 2579620 
kbibtex-data_0.8~20170819git31a77b27e8e83836e-1_all.deb
 32e368652e10c

Bug#874568: Removed package(s) from experimental

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from experimental:

libopencv3.1-java | 3.1.0+dfsg1-1~exp1 | all

--- Reason ---
RoQA; NBS; superseded by libopencv3.2-java
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 874...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/874568

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#870984: Removed package(s) from unstable

[Debian FTP Masters]

Version: 1.0.1-3+rm

Dear submitter,

as the package imview-doc has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/870984

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#870984: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

imview-doc |1.0.1-3 | source, all

--- Reason ---
RoQA; missed both jessie and stretch
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 870...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/870984

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#870922: Removed package(s) from unstable

[Debian FTP Masters]

Version: 6.1.0.svn.5396.dfsg2-4+rm

Dear submitter,

as the package elmerfem has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/870922

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#870922: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

 elmer | 6.1.0.svn.5396.dfsg2-3 | s390x
 elmer | 6.1.0.svn.5396.dfsg2-4+b1 | mips64el
 elmer | 6.1.0.svn.5396.dfsg2-4+b2 | amd64, hurd-i386, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel
 elmer | 6.1.0.svn.5396.dfsg2-4+b3 | armel, armhf
elmer-common | 6.1.0.svn.5396.dfsg2-3 | all
elmer-common | 6.1.0.svn.5396.dfsg2-4 | all
 elmer-dbg | 6.1.0.svn.5396.dfsg2-3 | s390x
 elmer-dbg | 6.1.0.svn.5396.dfsg2-4+b1 | mips64el
 elmer-dbg | 6.1.0.svn.5396.dfsg2-4+b2 | amd64, hurd-i386, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel
 elmer-dbg | 6.1.0.svn.5396.dfsg2-4+b3 | armel, armhf
  elmerfem | 6.1.0.svn.5396.dfsg2-3 | source
  elmerfem | 6.1.0.svn.5396.dfsg2-4 | source
libelmer-dev | 6.1.0.svn.5396.dfsg2-3 | s390x
libelmer-dev | 6.1.0.svn.5396.dfsg2-4+b1 | mips64el
libelmer-dev | 6.1.0.svn.5396.dfsg2-4+b2 | amd64, hurd-i386, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel
libelmer-dev | 6.1.0.svn.5396.dfsg2-4+b3 | armel, armhf
libelmersolver-6.1 | 6.1.0.svn.5396.dfsg2-3 | s390x
libelmersolver-6.1 | 6.1.0.svn.5396.dfsg2-4+b1 | mips64el
libelmersolver-6.1 | 6.1.0.svn.5396.dfsg2-4+b2 | amd64, hurd-i386, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel
libelmersolver-6.1 | 6.1.0.svn.5396.dfsg2-4+b3 | armel, armhf
libelmersolver-dbg | 6.1.0.svn.5396.dfsg2-3 | s390x
libelmersolver-dbg | 6.1.0.svn.5396.dfsg2-4+b1 | mips64el
libelmersolver-dbg | 6.1.0.svn.5396.dfsg2-4+b2 | amd64, hurd-i386, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel
libelmersolver-dbg | 6.1.0.svn.5396.dfsg2-4+b3 | armel, armhf

--- Reason ---
RoQA; missed both jessie and stretch
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 870...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/870922

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#784464: marked as done ([freecad] Qt4's WebKit removal)

[Debian Bug Tracking System]

Your message dated Fri, 08 Sep 2017 21:05:39 +
with message-id <e1dqqt5-0007ei...@fasolo.debian.org>
and subject line Bug#784464: fixed in freecad 0.16.6712+dfsg1-1
has caused the Debian Bug report #784464,
regarding [freecad] Qt4's WebKit removal
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.)


-- 
784464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784464
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freecad
Version: 0.14.3702+dfsg-3
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4webkit-removal

Dear Debian Science Maintainers 
<debian-science-maintainers@lists.alioth.debian.org>,

As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit
as announced in [announce].

[announce] 
<https://lists.debian.org/debian-devel-announce/2015/05/msg1.html>

Basically we are about to get the latest Qt4 point release and upstream is
migrating from WebKit to Bing in the Qt5 series, so we won't have much upstream
support for maintaining Qt4's WebKit.

In order to make this move, all packages directly or indirectly depending on
the Qt4's WebKit library have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4. In
order to ease the transition time we have provided Wheezy backports for Qt5.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

Ana,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: freecad
Source-Version: 0.16.6712+dfsg1-1

We believe that the bug you reported is fixed in the latest version of
freecad, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 784...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Anton Gladky <gl...@debian.org> (supplier of updated freecad package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 Sep 2017 22:55:20 +0200
Source: freecad
Binary: freecad
Architecture: source
Version: 0.16.6712+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 
<debian-science-maintainers@lists.alioth.debian.org>
Changed-By: Anton Gladky <gl...@debian.org>
Description:
 freecad- Extensible Open Source CAx program
Closes: 784464 868727
Changes:
 freecad (0.16.6712+dfsg1-1) unstable; urgency=medium
 .
   * [c631550] New upstream version 0.16.6712+dfsg1
   * [70d3ebc] Refresh patches
   * [c2f67a5] Remove dependency on Qt4 Webkit. (Closes: #784464)
   * [31d5630] Set Standards-Version: 4.1.0
   * [85cc9d9] Change priority to optional
   * [dc32b52] Set maximal hardening option
   * [c56abf6] Drop "alpha" from description. (Closes: #868727)
Checksums-Sha1:
 c6100ed4a905bf52a5074a91ab79e94d4115cedb 2922 freecad_0.16.6712+dfsg1-1.dsc
 55e54d6aeb562dd390e34de824ecf2ee4c12403d 16777580 
freecad_0.16.6712+dfsg1.orig.tar.xz
 68e140900cabb35da0acdb509868300df338a48b 23764 
freecad_0.16.6712+dfsg1-1.debian.tar.xz
 fcba8d9b7c7d491cbba23a110e5bf5989bb9b898 22551 
freecad_0.16.6712+dfsg1-1_source.buildinfo
Checksums-Sha256:
 884152f16eafa2a04cc2eb1f9fb06aa758eca15be6e4b0641b800f

Bug#874361: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

 einspline |0.9.2-2 | source
libeinspline-dbg | 0.9.2-2+b2 | amd64, arm64, armel, armhf, hurd-i386, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x
libeinspline-dev | 0.9.2-2+b2 | amd64, arm64, armel, armhf, hurd-i386, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x
libeinspline0 | 0.9.2-2+b2 | amd64, arm64, armel, armhf, hurd-i386, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x

--- Reason ---
ROM; dead upstream; FTBFS with GCC 7
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 874...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/874361

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#873477: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libceres-dev | 1.12.0+dfsg0-1+b3 | mips, mips64el, mipsel
 libceres1 | 1.12.0+dfsg0-1+b3 | mips, mips64el, mipsel

--- Reason ---
ROM; mips* currently not supported by upstream
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 873...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/873477

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#869688: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libdune-grid-dbg |2.5.0-1 | mips, powerpc
libdune-grid-dev |2.5.0-1 | mips, powerpc
libdune-grid-glue-dbg | 2.5.0~20161206g666200e-2+b1 | mips, powerpc
libdune-grid-glue-dev | 2.5.0~20161206g666200e-2+b1 | mips, powerpc
libdune-pdelab-dev | 2.5.0~20161204gdb53a76-3 | powerpc
libdune-pdelab-dev | 2.5.0~20170124g7cf9f47a-1 | mips

--- Reason ---
ROM; test hangs on mips and powerpc
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 869...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/869688

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#784455: marked as done ([cb2bib] Qt4's WebKit removal)

[Debian Bug Tracking System]

Your message dated Wed, 05 Jul 2017 16:57:55 +0200
with message-id <5770113.xkSkUPrO6Y@pendragon>
and subject line Fixed with cb2bib 1.9.2-1
has caused the Debian Bug report #784455,
regarding [cb2bib] Qt4's WebKit removal
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.)


-- 
784455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784455
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cb2bib
Version: 1.4.9-4
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4webkit-removal

Dear Debian Science Maintainers 
<debian-science-maintainers@lists.alioth.debian.org>,

As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit
as announced in [announce].

[announce] 
<https://lists.debian.org/debian-devel-announce/2015/05/msg1.html>

Basically we are about to get the latest Qt4 point release and upstream is
migrating from WebKit to Bing in the Qt5 series, so we won't have much upstream
support for maintaining Qt4's WebKit.

In order to make this move, all packages directly or indirectly depending on
the Qt4's WebKit library have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4. In
order to ease the transition time we have provided Wheezy backports for Qt5.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

Ana,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: cb2bib
Source-Version: 1.9.2-1

Hi,

it looks like cb2bib was ported to Qt5 already, and 1.9.2-1 is the
first version in Debian after the switch -- hence, closing.

Thanks,
-- 
Pino Toscano

signature.asc
Description: This is a digitally signed message part.
--- End Message ---
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#864949: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

 libug-dbg |   3.12.1-2 | amd64, arm64, armel, armhf, hurd-i386, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x
 libug-dev |   3.12.1-2 | amd64, arm64, armel, armhf, hurd-i386, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x
libug3.12.1 |   3.12.1-2 | amd64, arm64, armel, armhf, hurd-i386, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x
ug |   3.12.1-2 | source

--- Reason ---
ROM; superseded by dune-uggrid
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 864...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/864949

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#864265: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libdune-geometry-dbg |2.4.1-1 | hurd-i386
libdune-geometry-dev |2.4.1-1 | hurd-i386

--- Reason ---
RoM; Build-Depends on package not available on hurd-i386
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 864...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/864265

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#864004: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libdune-grid-2.3.1 |2.3.1-1 | hurd-i386
libdune-grid-dbg |2.3.1-1 | hurd-i386
libdune-grid-dev |2.3.1-1 | hurd-i386

--- Reason ---
RoM; FTBFS, MPI not working on hurd-i386
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 864...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/864004

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#864264: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libdune-pdelab-2.0.0 |2.0.0-1 | hurd-i386
libdune-pdelab-dev |2.0.0-1 | hurd-i386

--- Reason ---
RoM; Build-Depends on package not available on hurd-i386
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 864...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/864264

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#864263: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libdune-grid-glue-2.3.0 | 2.3.1-1+b1 | hurd-i386
libdune-grid-glue-dbg | 2.3.1-1+b1 | hurd-i386
libdune-grid-glue-dev | 2.3.1-1+b1 | hurd-i386

--- Reason ---
RoM; Build-Depends on package not available on hurd-i386
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 864...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/864263

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#843279: marked as done (libparmetis4.0: maintainer script(s) do not start on #!)

[Debian Bug Tracking System]

Your message dated Mon, 15 May 2017 18:49:37 +
with message-id <e1dal3p-0008zi...@fasolo.debian.org>
and subject line Bug#843279: fixed in parmetis 4.0.3-5
has caused the Debian Bug report #843279,
regarding libparmetis4.0: maintainer script(s) do not start on #!
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.)


-- 
843279: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843279
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libparmetis4.0
Version: 4.0.3-4+b2
Severity: important
User: trei...@debian.org
Usertags: colis-shparser

Dear maintainer,

at least one of the maintainer scripts (preinst, postinst, prerm,
postrm) of the package libparmetis4.0 does not start with #!. This is
a violation of policy 6.1, which states about maintainer scripts "if
they are scripts (which is recommended), they must start with the
usual #! convention."

This mass bug filing has been discussed and approved in thread [1].

-Ralf.

[1] https://lists.debian.org/debian-devel/2016/11/msg00168.html 
--- End Message ---
--- Begin Message ---
Source: parmetis
Source-Version: 4.0.3-5

We believe that the bug you reported is fixed in the latest version of
parmetis, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 843...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ansgar Burchardt <ans...@debian.org> (supplier of updated parmetis package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 15 May 2017 20:21:44 +0200
Source: parmetis
Binary: libparmetis-dev libparmetis4.0 parmetis-test parmetis-doc
Architecture: source
Version: 4.0.3-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 
<debian-science-maintainers@lists.alioth.debian.org>
Changed-By: Ansgar Burchardt <ans...@debian.org>
Description:
 libparmetis-dev - Parallel Graph Partitioning and Sparse Matrix Ordering Libs: 
Deve
 libparmetis4.0 - Parallel Graph Partitioning and Sparse Matrix Ordering Shared 
Lib
 parmetis-doc - Parallel Graph Partitioning and Sparse Matrix Ordering Lib - 
Docs
 parmetis-test - Parallel Graph Partitioning and Sparse Matrix Ordering Tests
Closes: 835020 843279 862659
Changes:
 parmetis (4.0.3-5) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Wolfgang Fütterer ]
   * [9bc9267] Removed Christophe from uploaders list (Closes: #835020)
 .
   [ Ansgar Burchardt ]
   * libparmetis4.0: remove `postinst` maintainer script: it only contained
 the "#DEBHELPER#" marker. Closes: #843279
   * libparmetis-dev: add dependency on libmetis-dev. Closes: #862659
Checksums-Sha1:
 cd402e8f711bf4a3df516f929062fe0ce9335ca5 2410 parmetis_4.0.3-5.dsc
 6c4d2c529889cc795e2ecbf9e437f7f3ddf5a47e 13980 parmetis_4.0.3-5.debian.tar.xz
Checksums-Sha256:
 a4d31c7fc766529d9dea43b742d47bbb11d7ada5f92582294d3511be16c8 2410 
parmetis_4.0.3-5.dsc
 396c47feba29bb5e64e03b2c23b1ebff5b9047f3a011b4f0aceadc3980f6523c 13980 
parmetis_4.0.3-5.debian.tar.xz
Files:
 a9833e1aec0618e63a7a7bcaaabb58f0 2410 non-free/math extra parmetis_4.0.3-5.dsc
 47e3321e633f05107469d4ca330ba8ac 13980 non-free/math extra 
parmetis_4.0.3-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEE6XYjQ9o8g2p4zSVKamMCj1p06JMFAlkZ8tMSHGFuc2dhckBk
ZWJpYW4ub3JnAAoJEGpjAo9adOiTEFMP/2iZ1VizC8oNjuvVXZ8DgB4FuiqNGCAG
sRpksGTLTdZ76oGUYNBCzMW5LKTnaXAi/77doIV8hloSSf99QgMRpoZpvp5w8FHY
wDFxAlfwEnJyKwaYu5CZ7G6F/UQRAr4X8vSYyg56RpeDjTf4KhYk1LCxZjUuSO7V
iwQq3QBDe1sw86oXKOBqetCMulp38lpAWQxMZ4r0JhSzEo64ArGxYhvagAEvt7o/
u5dJczAByHtUkuhNmsedXxmey92pF55Izkcj75uvgBag+813Q2H2RFNJZaFvbLtw
QrS6y0faZ2LzBnHUAWeuO1seAJdBUdV8AsCMdXzXhKLzsYKgxjTXRKBK9/V0cy9u
RSyyQ1yMAaY74vDUZlxv9zEkiZwz8gRrKazFyfHzb9Vs1ChexLy5ul0y451ql9MY
Rcc2A4nx+tBTmhQVk1vmPAe6Dw73iddk/cKxxZ5ZKwFcZ7n5xFVjDm56y/bxLccO
MXQYFRoeNE0DjnB4TbNldgEvFTTPfdMAo+TyMTLBuk2XTd0a0oH3B0sMjE3P9+lg
Hp5g0uoJMMi9lY408A1eQYlteJWBt+1Ox/1KMvTtOCViYXJihlfzQO5073G42uAf
Y7TVOFbS6umrSIml2tIA4xhflF2zj8G7ah0FAbQPp+wS4vVTyAnm63Gi9BCv5ooL
FKQwIpv6AIEi
=tYbZ
-END PGP SIGNATURE End Message ---
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://list

Bug#859406: Removed package(s) from unstable

[Debian FTP Masters]

Version: 11.5.0+dfsg2-4+rm

Dear submitter,

as the package aster has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/859406

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#859406: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

 aster | 11.5.0+dfsg2-4 | source
code-aster | 11.5.0+dfsg2-4+b3 | amd64, armel, armhf, i386, mips, mipsel, 
powerpc
code-aster-mpi-engine | 11.5.0+dfsg2-4+b3 | amd64, armel, armhf, i386, mips, 
mipsel, powerpc
code-aster-test | 11.5.0+dfsg2-4 | all

--- Reason ---
ROM; unmaintained, FTBFS
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 859...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/859406

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#816800: marked as done ([gazebo] Qt4's WebKit removal)

[Debian Bug Tracking System]

Your message dated Sun, 26 Feb 2017 20:21:49 +0100
with message-id 
<cafpsygrpofuqznmeq8xvfyn-hcwndwvuhqge3-ohf50fxsa...@mail.gmail.com>
and subject line Re: Delivery Status Notification (Failure)
has caused the Debian Bug report #816800,
regarding [gazebo] Qt4's WebKit removal
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.)


-- 
816800: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816800
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gazebo
Version: 7.0.0+dfsg-1
User: debian-qt-...@lists.debian.org
Usertags: qt4webkit-removal

Hi! As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit
as announced in [announce].

[announce] 
<https://lists.debian.org/debian-devel-announce/2015/05/msg1.html>

Basically we are about to get the last Qt4 point release and upstream is
migrating from WebKit to Blink in the Qt5 series, so we won't have much 
upstreams
support for maintaining Qt4's WebKit (Qt5's WebKit is expected to stay supported
until Qt6).

In order to make this move, all packages directly or indirectly depending on
the Qt4's WebKit library have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5 
port of your application
- if there are no activities regarding porting, investigate whether there are 
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian 
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4. In
order to ease the transition time we have provided Wheezy backports for Qt5.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

If you have any questions, please reply to this mail and CC me.

On behalf of the Qt4 maintainers,

--
Dmitry Shachnev

signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Gazebo upstream has removed the dependency on webkit qt and the latest
version in debian is already webkit free:
https://anonscm.debian.org/cgit/debian-science/packages/gazebo
.git/commit/?id=91b89c43f0e9860ea5bb05239f230b7f927dad96

On Sun, Feb 26, 2017 at 8:14 PM, Mail Delivery Subsystem <
mailer-dae...@googlemail.com> wrote:

> [image: Error Icon]
> Message not delivered
> There was a problem delivering your message to
> *816800+d...@bugs.debian.org*. See the technical details below, or try
> resending in a few minutes.
> The response from the remote server was:
>
> 550 Unknown or archived bug
>
> Final-Recipient: rfc822; 816800+d...@bugs.debian.org
> Action: failed
> Status: 5.0.0
> Remote-MTA: dns; buxtehude.debian.org. (2607:f8f0:614:1::1274:39, the
> server
>  for the domain bugs.debian.org.)
> Diagnostic-Code: smtp; 550 Unknown or archived bug
> Last-Attempt-Date: Sun, 26 Feb 2017 11:14:34 -0800 (PST)
>
>
> -- Forwarded message --
> From: Jose Luis Rivero <jriv...@osrfoundation.org>
> To: 816800+d...@bugs.debian.org
> Cc:
> Bcc:
> Date: Sun, 26 Feb 2017 20:14:24 +0100
> Subject: Re: Processed: Qt4's WebKit removal: rising severity to important
> Gazebo upstream has removed the dependency on webkit qt and the latest
> version in debian is already webkit free:
> https://anonscm.debian.org/cgit/debian-science/packages/
> gazebo.git/commit/?id=91b89c43f0e9860ea5bb05239f230b7f927dad96
>
>
> On Mon, Oct 3, 2016 at 4:28 PM, Debian Bug Tracking System <
> ow...@bugs.debian.org> wrote:
>
> > Processing control commands:
> >
> > > severity -1 important
> > Bug #816800 [src:gazebo] [gazebo] Qt4's WebKit removal
> > Severity set to 'important' from 'normal'
> >
> > --
> > 816800: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816800
> > Debian Bug Tracking System
> > Contact ow...@bugs.debian.org with problems
> >
> >
>
>
--- End Message ---
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

S

[Jennifer Weyker]

Can we talk
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

S

[Neil, Ryan William]

Can we talk
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

RSC Business Group, Inc.'s

[YOUR PRODUCTS CATALOG]

To Whom It May Concern


   I Have Buyer Interested In Your Product  and ONI B4 LIQUID OIL for CONTRACT 
Order In Large Quantity In Ghana West Africa,Can You Supply This Product From 
DUBAI? Contact Me For More Details with your product catalog.




Thanks



--
RSC Business Group, Inc.'s
23B Commercial Avenue,Off
Randle Road, Apapa,Lagos,
Nigeria.Advertising and marketing,
Marketing consulting services,
Corporate management activities.


-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

S

[Bonini, Diana Grace]

Can we talk
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

S

[Melissa Ann Bong]

Can we talk
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

S

[Jamison, Constance S]

Can we talk
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

S

[Boyne, Kim]

Can we talk
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Re: Bug#848859: Lowering the bug`s severity

[Jose Luis Rivero]

Hello Santiago:

On 27/12/16 10:26, Santiago Vila wrote:
> 
> Sorry if you don't like my communication style. Please try not to
> dismiss completely the build logs I sent and maybe you will see how my
> communication style improves greatly.
> 

The communication style is involve in the respect that everyone
deserves, and as such, please don't use it in a negotiation. No matter
what technical problem are you solving, no matter how obvious is the
problem you try to explain, no matter how you disagree with the
decisions taken. Nothing gives you the option of being disrespectful.

Point 1 in the code of conduct:
https://www.debian.org/code_of_conduct

Thanks and happy holidays.

-- 
Jose Luis Rivero 

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#849447: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libdune-uggrid-dbg | 2.5.0~rc2-1 | mips64el
libdune-uggrid-dev | 2.5.0~rc2-1 | mips64el

--- Reason ---
RoM; OpenMPI broken on mips64el (#848574) and others
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 849...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/849447

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#849446: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libdune-pdelab-dev |2.4.1-1 | kfreebsd-amd64, kfreebsd-i386
libdune-pdelab-dev | 2.5.0~20161204gdb53a76-3 | mips64el

--- Reason ---
RoM; OpenMPI broken on mips64el (#848574) and others
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 849...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/849446

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#849445: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libdune-grid-glue-dbg | 2.4.0-1+b1 | kfreebsd-amd64, kfreebsd-i386
libdune-grid-glue-dbg | 2.5.0~20161206g666200e-2 | mips64el
libdune-grid-glue-dev | 2.4.0-1+b1 | kfreebsd-amd64, kfreebsd-i386
libdune-grid-glue-dev | 2.5.0~20161206g666200e-2 | mips64el

--- Reason ---
RoM; OpenMPI broken on mips64el (#848574) and others
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 849...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/849445

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#849443: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libdune-geometry-dbg |2.4.1-1 | kfreebsd-amd64, kfreebsd-i386
libdune-geometry-dbg | 2.5.0~rc2-1 | mips64el
libdune-geometry-dev |2.4.1-1 | kfreebsd-amd64, kfreebsd-i386
libdune-geometry-dev | 2.5.0~rc2-1 | mips64el

--- Reason ---
RoM; OpenMPI broken on mips64el (#848574) and others
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 849...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/849443

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#849444: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libdune-grid-dbg |2.4.1-1 | kfreebsd-amd64, kfreebsd-i386
libdune-grid-dbg | 2.5.0~rc2-1 | mips64el
libdune-grid-dev |2.4.1-1 | kfreebsd-amd64, kfreebsd-i386
libdune-grid-dev | 2.5.0~rc2-1 | mips64el

--- Reason ---
RoM; OpenMPI broken on mips64el (#848574) and others
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 849...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/849444

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#849442: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libdune-common-dbg |2.4.1-1 | hurd-i386, kfreebsd-amd64, kfreebsd-i386
libdune-common-dbg | 2.5.0~rc2-2 | mips64el
libdune-common-dev |2.4.1-1 | hurd-i386, kfreebsd-amd64, kfreebsd-i386
libdune-common-dev | 2.5.0~rc2-2 | mips64el

--- Reason ---
RoM; OpenMPI broken on mips64el (#848574) and others
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 849...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/849442

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#849287: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libtrilinos-amesos-dev |  12.10.1-1 | mips64el
libtrilinos-amesos12 |  12.10.1-1 | mips64el
libtrilinos-amesos2-12 |  12.10.1-1 | mips64el
libtrilinos-amesos2-dev |  12.10.1-1 | mips64el
libtrilinos-anasazi-dev |  12.10.1-1 | mips64el
libtrilinos-anasazi12 |  12.10.1-1 | mips64el
libtrilinos-aztecoo-dev |  12.10.1-1 | mips64el
libtrilinos-aztecoo12 |  12.10.1-1 | mips64el
libtrilinos-belos-dev |  12.10.1-1 | mips64el
libtrilinos-belos12 |  12.10.1-1 | mips64el
libtrilinos-epetra-dev |  12.10.1-1 | mips64el
libtrilinos-epetra12 |  12.10.1-1 | mips64el
libtrilinos-epetraext-dev |  12.10.1-1 | mips64el
libtrilinos-epetraext12 |  12.10.1-1 | mips64el
libtrilinos-galeri-dev |  12.10.1-1 | mips64el
libtrilinos-galeri12 |  12.10.1-1 | mips64el
libtrilinos-globipack-dev |  12.10.1-1 | mips64el
libtrilinos-globipack12 |  12.10.1-1 | mips64el
libtrilinos-ifpack-dev |  12.10.1-1 | mips64el
libtrilinos-ifpack12 |  12.10.1-1 | mips64el
libtrilinos-ifpack2-12 |  12.10.1-1 | mips64el
libtrilinos-ifpack2-dev |  12.10.1-1 | mips64el
libtrilinos-intrepid-dev |  12.10.1-1 | mips64el
libtrilinos-intrepid12 |  12.10.1-1 | mips64el
libtrilinos-isorropia-dev |  12.10.1-1 | mips64el
libtrilinos-isorropia12 |  12.10.1-1 | mips64el
libtrilinos-kokkos-dev |  12.10.1-1 | mips64el
libtrilinos-kokkos12 |  12.10.1-1 | mips64el
libtrilinos-komplex-dev |  12.10.1-1 | mips64el
libtrilinos-komplex12 |  12.10.1-1 | mips64el
libtrilinos-ml-dev |  12.10.1-1 | mips64el
libtrilinos-ml12 |  12.10.1-1 | mips64el
libtrilinos-moertel-dev |  12.10.1-1 | mips64el
libtrilinos-moertel12 |  12.10.1-1 | mips64el
libtrilinos-muelu-dev |  12.10.1-1 | mips64el
libtrilinos-muelu12 |  12.10.1-1 | mips64el
libtrilinos-nox-dev |  12.10.1-1 | mips64el
libtrilinos-nox12 |  12.10.1-1 | mips64el
libtrilinos-optipack-dev |  12.10.1-1 | mips64el
libtrilinos-optipack12 |  12.10.1-1 | mips64el
libtrilinos-pamgen-dev |  12.10.1-1 | mips64el
libtrilinos-pamgen12 |  12.10.1-1 | mips64el
libtrilinos-phalanx-dev |  12.10.1-1 | mips64el
libtrilinos-phalanx12 |  12.10.1-1 | mips64el
libtrilinos-pike-dev |  12.10.1-1 | mips64el
libtrilinos-pike12 |  12.10.1-1 | mips64el
libtrilinos-piro-dev |  12.10.1-1 | mips64el
libtrilinos-piro12 |  12.10.1-1 | mips64el
libtrilinos-pliris-dev |  12.10.1-1 | mips64el
libtrilinos-pliris12 |  12.10.1-1 | mips64el
libtrilinos-rol-dev |  12.10.1-1 | mips64el
libtrilinos-rol12 |  12.10.1-1 | mips64el
libtrilinos-rtop-dev |  12.10.1-1 | mips64el
libtrilinos-rtop12 |  12.10.1-1 | mips64el
libtrilinos-rythmos-dev |  12.10.1-1 | mips64el
libtrilinos-rythmos12 |  12.10.1-1 | mips64el
libtrilinos-sacado-dev |  12.10.1-1 | mips64el
libtrilinos-sacado12 |  12.10.1-1 | mips64el
libtrilinos-shards-dev |  12.10.1-1 | mips64el
libtrilinos-shards12 |  12.10.1-1 | mips64el
libtrilinos-shylu-dev |  12.10.1-1 | mips64el
libtrilinos-shylu12 |  12.10.1-1 | mips64el
libtrilinos-stokhos-dev |  12.10.1-1 | mips64el
libtrilinos-stokhos12 |  12.10.1-1 | mips64el
libtrilinos-stratimikos-dev |  12.10.1-1 | mips64el
libtrilinos-stratimikos12 |  12.10.1-1 | mips64el
libtrilinos-teko-dev |  12.10.1-1 | mips64el
libtrilinos-teko12 |  12.10.1-1 | mips64el
libtrilinos-teuchos-dev |  12.10.1-1 | mips64el
libtrilinos-teuchos12 |  12.10.1-1 | mips64el
libtrilinos-thyra-dev |  12.10.1-1 | mips64el
libtrilinos-thyra12 |  12.10.1-1 | mips64el
libtrilinos-tpetra-dev |  12.10.1-1 | mips64el
libtrilinos-tpetra12 |  12.10.1-1 | mips64el
libtrilinos-trilinoscouplings-dev |  12.10.1-1 | mips64el
libtrilinos-trilinoscouplings12 |  12.10.1-1 | mips64el
libtrilinos-triutils-dev |  12.10.1-1 | mips64el
libtrilinos-triutils12 |  12.10.1-1 | mips64el
libtrilinos-xpetra-dev |  12.10.1-1 | mips64el
libtrilinos-xpetra12 |  12.10.1-1 | mips64el
libtrilinos-zoltan-dev |  12.10.1-1 | mips64el
libtrilinos-zoltan12 |  12.10.1-1 | mips64el
libtrilinos-zoltan2-12 |  12.10.1-1 | mips64el
libtrilinos-zoltan2-dev |  12.10.1-1 | mips64el
trilinos-all-dev |  12.10.1-1 | mips64el
trilinos-dev |  12.10.1-1 | mips64el

--- Reason ---
RoM; FTBFS
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been

Bug#848859: Lowering the bug`s severity

[Santiago Vila]

On Tue, Dec 27, 2016 at 10:11:56AM +0100, Anton Gladky wrote:
> 2016-12-27 9:50 GMT+01:00 Santiago Vila :
> > This means, if you are bad at math, that the error will happen once
> > every 20 tries. If you only built it 5 times, you did not really tried
> > to reproduce it.
> 
> I'm not going to build every package 20 times to catch a "possible" bug,

The build logs I sent prove that there is bug, so it's not a "possible" bug.

> The main source of information for this type of bugs is the
> buildds [1] for me. They are happy at the moment.

The main, maybe, but it should not be the only one.

In particular, if something happens 1 every 20 times on average, the
fact that it did not happen when you try 10 times does not mean in any
way that it may not happen.

This is basic math, and everybody here (debian-science) should be aware of that.

Sorry if you don't like my communication style. Please try not to
dismiss completely the build logs I sent and maybe you will see how my
communication style improves greatly.

Thanks.

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#848859: Lowering the bug`s severity

[Anton Gladky]

2016-12-27 9:50 GMT+01:00 Santiago Vila :
> This means, if you are bad at math, that the error will happen once
> every 20 tries. If you only built it 5 times, you did not really tried
> to reproduce it.

I'm not going to build every package 20 times to catch a "possible" bug,
sorry. The main source of information for this type of bugs is the
buildds [1] for me. They are happy at the moment.

And please change the style of communication with me.

Cheers

[1] https://buildd.debian.org/status/package.php?p=getfem%2B%2B

Anton

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#848859: Lowering the bug`s severity

[Santiago Vila]

On Tue, Dec 27, 2016 at 08:20:54AM +0100, Anton Gladky wrote:
> severity 848859 minor
> tags 848859 +unreproducible
> thanks
> 
> Hi  Santiago,
> 
> thanks for your bugreport! I tried to reproduce the failing
> test, building getfem on barriere.d,o 5 times but in all
> cases it did not failed. Also the last upload of getfem was
> successfully built on all supported platforms.
> 
> Nevertheless I am not closing the bug, but lowering its
> severity for the case if the bug will appear again.

The bug is probably still there, just that you didn't really bother to
reproduce it. I clearly said this in my bug report:

"The failure rate is around 5%, so if you try to reproduce this,
please try a *lot* of times."

This means, if you are bad at math, that the error will happen once
every 20 tries. If you only built it 5 times, you did not really tried
to reproduce it.

And then you didn't bother to Cc:me on this message, which I had to
read from debian-bugs-rc@l.d.o.

For this reason, I consider this downgrade of yours unacceptable and a
bad joke.

I'm going to repeat my tests in unstable, just for the case that some
already-fixed build-dependency was to blame for this, but if I still
reproduce this I will restore the original severity, as packages *must*
build from source *without* failure, this is not an invention of mine,
it's Release Policy.

Thanks.

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#848859: Lowering the bug`s severity

[Anton Gladky]

severity 848859 minor
tags 848859 +unreproducible
thanks

Hi  Santiago,

thanks for your bugreport! I tried to reproduce the failing
test, building getfem on barriere.d,o 5 times but in all
cases it did not failed. Also the last upload of getfem was
successfully built on all supported platforms.

Nevertheless I am not closing the bug, but lowering its
severity for the case if the bug will appear again.

Best regards

Anton

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#848925: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

apophenia-bin |   1.0+ds-3 | mips, mips64el, mipsel
libapophenia2 |   1.0+ds-3 | mips, mips64el, mipsel
libapophenia2-dev |   1.0+ds-3 | mips, mips64el, mipsel

--- Reason ---
ROM; weird GCC problem on mips* arch
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 848...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/848925

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#848548: Removed package(s) from experimental

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from experimental:

libopencv3.0-java | 3.0.0+dfsg-1~exp7 | all

--- Reason ---
RoQA; NBS; superseded by libopencv3.1-java
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 848...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/848548

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#847431: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libtrilinos-amesos-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-amesos12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-amesos2-12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-amesos2-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-anasazi-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-anasazi12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-aztecoo-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-aztecoo12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-belos-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-belos12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-epetra-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-epetra12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-epetraext-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-epetraext12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-galeri-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-galeri12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-globipack-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-globipack12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-ifpack-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-ifpack12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-ifpack2-12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-ifpack2-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-intrepid-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-intrepid12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-isorropia-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-isorropia12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-kokkos-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-kokkos12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-komplex-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-komplex12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-ml-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-ml12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-moertel-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-moertel12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-muelu-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-muelu12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-nox-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-nox12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-optipack-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-optipack12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-pamgen-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-pamgen12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-phalanx-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-phalanx12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-pike-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-pike12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-piro-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-piro12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-pliris-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-pliris12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-rol-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-rol12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-rtop-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-rtop12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-rythmos-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-rythmos12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-sacado-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-sacado12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-shards-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-shards12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-shylu-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-shylu12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-stokhos-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-stokhos12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-stratimikos-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-stratimikos12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-teko-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-teko12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-teuchos-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-teuchos12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-thyra-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-thyra12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-tpetra-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-tpetra12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-trilinoscouplings-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-trilinoscouplings12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-triutils-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-triutils12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-xpetra-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-xpetra12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-zoltan-dev | 12.6.4-1+b1 | armhf, i386
libtrilinos-zoltan12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-zoltan2-12 | 12.6.4-1+b1 | armhf, i386
libtrilinos-zoltan2-dev | 12.6.4-1+b1 | armhf, i386
  trilinos |   12.6.4-1 | source
  trilinos |  12.10.1-1 | source
trilinos-all-dev | 12.6.4-1+b1 | armhf, i386
trilinos-dev | 12.6.4-1+b1 | armhf, i386

--- Reason ---
ROM; Broken on 32 bit archs
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive

Bug#847430: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libdeal.ii-8.4.2 |8.4.2-2 | armhf, i386
libdeal.ii-dev |8.4.2-2 | armhf, i386

--- Reason ---
ROM; trilinos broken on 32-bit
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 847...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/847430

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#846194: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

r-cran-rprotobuf |0.4.7-1 | mips64el

--- Reason ---
ROM; Does not build on mips64el
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 846...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/846194

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#845936: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

   meshlab | 1.3.2+dfsg1-2+b2 | mips64el
   meshlab | 1.3.2+dfsg1-2+b4 | mips, mipsel

--- Reason ---
ROM; FTBFS on these architectures
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 845...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/845936

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#845267: Bug#741112 closed by Debian FTP Masters <ftpmas...@ftp-master.debian.org> (Bug#845053: Removed package(s) from unstable)

[Francesco Poli]

Control: retitle -1 libopenfoam: libscotchDecomp.so.0.1.0 is GPL-licensed but 
links with GPL-incompatible library


On Mon, 21 Nov 2016 23:12:14 +0100 Francesco Poli wrote:

> Control: clone -1 -2
> Control: reassign -2 libopenfoam 4.0+dfsg1-5
> Control: reopen -2
[...]

I forgot to retitle the bug report...


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpak529niKtd.pgp
Description: PGP signature
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Processed: Re: Bug#741112 closed by Debian FTP Masters <ftpmas...@ftp-master.debian.org> (Bug#845053: Removed package(s) from unstable)

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 libopenfoam: libscotchDecomp.so.0.1.0 is GPL-licensed but links 
> with GPL-incompatible library
Bug #845267 [libopenfoam] libfreefoam1: libscotchDecomp.so.0.1.0 is 
GPL-licensed but links with GPL-incompatible library
Changed Bug title to 'libopenfoam: libscotchDecomp.so.0.1.0 is GPL-licensed but 
links with GPL-incompatible library' from 'libfreefoam1: 
libscotchDecomp.so.0.1.0 is GPL-licensed but links with GPL-incompatible 
library'.

-- 
845267: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845267
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Processed: Re: Bug#741112 closed by Debian FTP Masters <ftpmas...@ftp-master.debian.org> (Bug#845053: Removed package(s) from unstable)

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #741112 {Done: Debian FTP Masters } 
[libfreefoam1] libfreefoam1: libscotchDecomp.so.0.1.0 is GPL-licensed but links 
with GPL-incompatible library
Bug 741112 cloned as bug 845267
> reassign -2 libopenfoam 4.0+dfsg1-5
Bug #845267 {Done: Debian FTP Masters } 
[libfreefoam1] libfreefoam1: libscotchDecomp.so.0.1.0 is GPL-licensed but links 
with GPL-incompatible library
Bug reassigned from package 'libfreefoam1' to 'libopenfoam'.
No longer marked as found in versions freefoam/0.1.0+dfsg-1.
No longer marked as fixed in versions 0.1.0+dfsg+1-4+rm.
Bug #845267 {Done: Debian FTP Masters } 
[libopenfoam] libfreefoam1: libscotchDecomp.so.0.1.0 is GPL-licensed but links 
with GPL-incompatible library
Marked as found in versions openfoam/4.0+dfsg1-5.
> reopen -2
Bug #845267 {Done: Debian FTP Masters } 
[libopenfoam] libfreefoam1: libscotchDecomp.so.0.1.0 is GPL-licensed but links 
with GPL-incompatible library
Bug reopened
Ignoring request to alter fixed versions of bug #845267 to the same values 
previously set

-- 
741112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741112
845267: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845267
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Re: Bug#741112 closed by Debian FTP Masters <ftpmas...@ftp-master.debian.org> (Bug#845053: Removed package(s) from unstable)

[Francesco Poli]

Control: clone -1 -2
Control: reassign -2 libopenfoam 4.0+dfsg1-5
Control: reopen -2


On Mon, 21 Nov 2016 06:18:09 + Debian Bug Tracking System wrote:

> Dear submitter,
> 
> as the package freefoam has just been removed from the Debian archive
> unstable we hereby close the associated bug reports.  We are sorry
> that we couldn't deal with your issue properly.
[...]

Package freefoam has been removed, but an identical issue is present in
package openfoam.
I am therefore cloning, reassigning, and reopening this bug report...

Bye.

-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgptHTxWFYDtR.pgp
Description: PGP signature
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#845053: Removed package(s) from unstable

[Debian FTP Masters]

Version: 0.1.0+dfsg+1-4+rm

Dear submitter,

as the package freefoam has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/845053

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#845053: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

  freefoam | 0.1.0+dfsg+1-4 | source, hurd-i386, kfreebsd-amd64, kfreebsd-i386
  freefoam | 0.1.0+dfsg+1-4+b2 | amd64, i386, mips64el
freefoam-dev-doc | 0.1.0+dfsg+1-4 | all
freefoam-user-doc | 0.1.0+dfsg+1-4 | all
libfreefoam-dev | 0.1.0+dfsg+1-4 | hurd-i386, kfreebsd-amd64, kfreebsd-i386
libfreefoam-dev | 0.1.0+dfsg+1-4+b2 | amd64, i386, mips64el
libfreefoam1 | 0.1.0+dfsg+1-4 | hurd-i386, kfreebsd-amd64, kfreebsd-i386
libfreefoam1 | 0.1.0+dfsg+1-4+b2 | amd64, i386, mips64el

--- Reason ---
ROM; the package is superseded by OpenFOAM
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 845...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/845053

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#844767: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libliggghts-dev | 3.4.0+repack1-2+b1 | mips, mipsel
libliggghts3 | 3.4.0+repack1-2+b1 | mips, mipsel
  liggghts | 3.4.0+repack1-2+b1 | mips, mipsel

--- Reason ---
ROM; FTBFS on mips and mipsel
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 844...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/844767

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#844586: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

lua-torch-sundown | 0~20160713-g8353f5a-1 | arm64, mips64el, ppc64el, s390x

--- Reason ---
ROM; ANAIS
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 844...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/844586

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#844209: Removed package(s) from unstable

[Debian FTP Masters]

Version: 0.5.3+svn287-2.1+rm

Dear submitter,

as the package sivp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/844209

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#844209: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

scilab-sivp |0.5.2-2 | powerpc
scilab-sivp | 0.5.3+svn287-2.1 | amd64, armel, armhf, i386, mips, mipsel
  sivp |0.5.2-2 | source
  sivp | 0.5.3+svn287-2.1 | source

--- Reason ---
ROM; Low popcon, dead upstream
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 844...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/844209

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#843103: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libpolybori-0.8-3 |  0.8.3-5.2 | armhf
libpolybori-0.8-3 | 0.8.3-5.2+b1 | amd64, arm64, armel, i386, kfreebsd-amd64, 
kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x
libpolybori-0.8-3-dbg |  0.8.3-5.2 | armhf
libpolybori-0.8-3-dbg | 0.8.3-5.2+b1 | amd64, arm64, armel, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x
libpolybori-dev |  0.8.3-5.2 | armhf
libpolybori-dev | 0.8.3-5.2+b1 | amd64, arm64, armel, i386, kfreebsd-amd64, 
kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x
libpolybori-groebner-0.8-3 |  0.8.3-5.2 | armhf
libpolybori-groebner-0.8-3 | 0.8.3-5.2+b1 | amd64, arm64, armel, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x
libpolybori-groebner-0.8-3-dbg |  0.8.3-5.2 | armhf
libpolybori-groebner-0.8-3-dbg | 0.8.3-5.2+b1 | amd64, arm64, armel, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x
libpolybori-groebner-dev |  0.8.3-5.2 | armhf
libpolybori-groebner-dev | 0.8.3-5.2+b1 | amd64, arm64, armel, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x
  polybori |  0.8.3-5.2 | source, armhf
  polybori | 0.8.3-5.2+b1 | amd64, arm64, armel, i386, kfreebsd-amd64, 
kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x
polybori-doc |  0.8.3-5.2 | all
polybori-gui |  0.8.3-5.2 | armhf
polybori-gui | 0.8.3-5.2+b1 | amd64, arm64, armel, i386, kfreebsd-amd64, 
kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x
python-polybori |  0.8.3-5.2 | armhf
python-polybori | 0.8.3-5.2+b1 | amd64, arm64, armel, i386, kfreebsd-amd64, 
kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x

--- Reason ---
ROM; NVIU
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 843...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/843103

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#842827: Removed package(s) from experimental

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from experimental:

libpcl-apps1.8 | 1.8.0+dfsg1-4 | amd64, arm64, i386, mips, mips64el, mipsel, 
powerpc, ppc64el, s390x
libpcl-common1.8 | 1.8.0+dfsg1-4 | amd64, arm64, i386, mips, mips64el, mipsel, 
powerpc, ppc64el, s390x
libpcl-dev | 1.8.0+dfsg1-4 | amd64, arm64, i386, mips, mips64el, mipsel, 
powerpc, ppc64el, s390x
libpcl-doc | 1.8.0+dfsg1-4 | all
libpcl-features1.8 | 1.8.0+dfsg1-4 | amd64, arm64, i386, mips, mips64el, 
mipsel, powerpc, ppc64el, s390x
libpcl-filters1.8 | 1.8.0+dfsg1-4 | amd64, arm64, i386, mips, mips64el, mipsel, 
powerpc, ppc64el, s390x
libpcl-io1.8 | 1.8.0+dfsg1-4 | amd64, arm64, i386, mips, mips64el, mipsel, 
powerpc, ppc64el, s390x
libpcl-kdtree1.8 | 1.8.0+dfsg1-4 | amd64, arm64, i386, mips, mips64el, mipsel, 
powerpc, ppc64el, s390x
libpcl-keypoints1.8 | 1.8.0+dfsg1-4 | amd64, arm64, i386, mips, mips64el, 
mipsel, powerpc, ppc64el, s390x
libpcl-ml1.8 | 1.8.0+dfsg1-4 | amd64, arm64, i386, mips, mips64el, mipsel, 
powerpc, ppc64el, s390x
libpcl-octree1.8 | 1.8.0+dfsg1-4 | amd64, arm64, i386, mips, mips64el, mipsel, 
powerpc, ppc64el, s390x
libpcl-outofcore1.8 | 1.8.0+dfsg1-4 | amd64, arm64, i386, mips, mips64el, 
mipsel, powerpc, ppc64el, s390x
libpcl-people1.8 | 1.8.0+dfsg1-4 | amd64, arm64, i386, mips, mips64el, mipsel, 
powerpc, ppc64el, s390x
libpcl-recognition1.8 | 1.8.0+dfsg1-4 | amd64, arm64, i386, mips, mips64el, 
mipsel, powerpc, ppc64el, s390x
libpcl-registration1.8 | 1.8.0+dfsg1-4 | amd64, arm64, i386, mips, mips64el, 
mipsel, powerpc, ppc64el, s390x
libpcl-sample-consensus1.8 | 1.8.0+dfsg1-4 | amd64, arm64, i386, mips, 
mips64el, mipsel, powerpc, ppc64el, s390x
libpcl-search1.8 | 1.8.0+dfsg1-4 | amd64, arm64, i386, mips, mips64el, mipsel, 
powerpc, ppc64el, s390x
libpcl-segmentation1.8 | 1.8.0+dfsg1-4 | amd64, arm64, i386, mips, mips64el, 
mipsel, powerpc, ppc64el, s390x
libpcl-stereo1.8 | 1.8.0+dfsg1-4 | amd64, arm64, i386, mips, mips64el, mipsel, 
powerpc, ppc64el, s390x
libpcl-surface1.8 | 1.8.0+dfsg1-4 | amd64, arm64, i386, mips, mips64el, mipsel, 
powerpc, ppc64el, s390x
libpcl-tracking1.8 | 1.8.0+dfsg1-4 | amd64, arm64, i386, mips, mips64el, 
mipsel, powerpc, ppc64el, s390x
libpcl-visualization1.8 | 1.8.0+dfsg1-4 | amd64, arm64, i386, mips, mips64el, 
mipsel, powerpc, ppc64el, s390x
   pcl | 1.8.0+dfsg1-4 | source
 pcl-tools | 1.8.0+dfsg1-4 | amd64, arm64, i386, mips, mips64el, mipsel, 
powerpc, ppc64el, s390x

--- Reason ---
ROM; changeset didn't worked
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 842...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/842827

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#842088: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

r-cran-knitr |   1.12.3-1 | armel

--- Reason ---
ROM; Build-Dependency nodejs not available on armel
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 842...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/842088

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#840987: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

   freemat | 4.2+dfsg1-1+b2 | armel

--- Reason ---
ROM: needs llvm-3.8
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 840...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/840987

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#840195: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

fflas-ffpack |1.6.0-1 | armel, mips, powerpc, s390x

--- Reason ---
ROM; FTBFS on some architectures and blocking migration to testing
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 840...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/840195

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#813371: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

   libyade |   1.20.0-2 | kfreebsd-i386
python-yade |   1.20.0-2 | kfreebsd-i386
  yade |   1.20.0-2 | kfreebsd-i386

--- Reason ---
ROM; FTBFS
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 813...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/813371

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Processed: Qt4's WebKit removal: rising severity to important

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #784505 [src:paraview] [paraview] Qt4's WebKit removal
Severity set to 'important' from 'normal'

-- 
784505: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784505
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#784455: Qt4's WebKit removal: rising severity to important

[Mattia Rizzolo]

Control: severity -1 important

Please consider this a reminder of the upcoming removal of Qt4's WebKit.
We are rising the severity of all bugs to important, but they will
become serious in a fairly short term, to be able to remove it before
the release of stretch.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Processed: Qt4's WebKit removal: rising severity to important

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #784464 [src:freecad] [freecad] Qt4's WebKit removal
Severity set to 'important' from 'normal'

-- 
784464: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784464
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Processed: Qt4's WebKit removal: rising severity to important

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #784455 [src:cb2bib] [cb2bib] Qt4's WebKit removal
Severity set to 'important' from 'normal'

-- 
784455: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784455
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#839229: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

pyfftw | 0.10.1+dfsg1-1 | source
pyfftw | 0.10.4+dfsg1-1 | source
python-pyfftw | 0.10.1+dfsg1-1+b1 | arm64, armel, armhf, hurd-i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x
python-pyfftw | 0.10.4+dfsg1-1 | amd64, i386
python-pyfftw-dbg | 0.10.1+dfsg1-1+b1 | arm64, armel, armhf, hurd-i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x
python3-pyfftw | 0.10.1+dfsg1-1+b1 | arm64, armel, armhf, hurd-i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x
python3-pyfftw | 0.10.4+dfsg1-1 | amd64, i386
python3-pyfftw-dbg | 0.10.1+dfsg1-1+b1 | arm64, armel, armhf, hurd-i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x

--- Reason ---
ROM; RC-buggy, FTBFS on x86
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 839...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/839229

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#839229: Removed package(s) from unstable

[Debian FTP Masters]

Version: 0.10.4+dfsg1-1+rm

Dear submitter,

as the package pyfftw has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/839229

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#838655: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libhypre-dev |   2.8.0b-3 | all

--- Reason ---
RoQA; obsolete arch:all package
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 838...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/838655

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#836740: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libshark-dev | 3.0.1+ds1-1 | mips, mipsel
 libshark0 | 3.0.1+ds1-1 | mips, mipsel
libshark0-dbg | 3.0.1+ds1-1 | mips, mipsel

--- Reason ---
ROM; ANAIS
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 836...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/836740

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#835427: s/XML_NO_ERROR/XML_SUCCESS/

[Peter Green]

On 03/09/16 06:05, Graham Inggs wrote:


This comes from protobuf 3.  I found it has already been fixed in git
[1], although the patch description is incorrect.

Regards
Graham


[1] 
https://anonscm.debian.org/cgit/debian-science/packages/gazebo.git/commit/?id=d033bbf3218580638e35b8df13565099a5c7c8db
   

Any eta on an upload? is something blocking one?

--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#836178: Removed package(s) from unstable

[Debian FTP Masters]

Version: 0.13.13-1+rm

Dear submitter,

as the package pyoperators has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/836178

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#836178: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

pyoperators |  0.13.11-1 | source
pyoperators |  0.13.13-1 | source
python-pyoperators |  0.13.11-1 | armel, armhf, hurd-i386, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x
python-pyoperators |  0.13.13-1 | amd64, arm64, mips64el
python3-pyoperators |  0.13.11-1 | armel, armhf, hurd-i386, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x
python3-pyoperators |  0.13.13-1 | amd64, arm64, mips64el

--- Reason ---
ROM; RC-buggy; obsoleted; low-popcorn
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 836...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/836178

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#836222: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libgetfem++-dev | 5.0+dfsg1-2 | armel
libgetfem5++ | 5.0+dfsg1-2 | armel
python-getfem++ | 5.0+dfsg1-2 | armel

--- Reason ---
ROM; FTBFS on armel
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 836...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/836222

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#835427: s/XML_NO_ERROR/XML_SUCCESS/

[Graham Inggs]

Hi Peter

On 2 September 2016 at 23:15, Peter Green  wrote:
> Unfortunately while that patch fixed the FTBFS in raspbian stretch at the
> time the package is now failing for us for a different reason. While I saw
> this in raspbian I have no reason to belive it is raspbian specific.
>
>
> In file included from /usr/include/spnav.h:33:0,
>  from
> /<>/gazebo-7.3.0+dfsg/gazebo/gui/SpaceNav.cc:27:
> /usr/include/google/protobuf/stubs/logging.h:66:7: error: expected
> identifier before 'int'
>  class Status;
>^
> /usr/include/google/protobuf/stubs/logging.h:66:7: error: multiple types in
> one declaration

This comes from protobuf 3.  I found it has already been fixed in git
[1], although the patch description is incorrect.

Regards
Graham


[1] 
https://anonscm.debian.org/cgit/debian-science/packages/gazebo.git/commit/?id=d033bbf3218580638e35b8df13565099a5c7c8db

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#835427: s/XML_NO_ERROR/XML_SUCCESS/

[Peter Green]

On 29/08/16 15:45, Peter Michael Green wrote:

tags 835427 +patch
thanks
Older versions of tinyxml defined both XML_NO_ERROR and XML_SUCCESS 
to 0. Never

versions define only XML_SUCCESS.


Attatched is a patch that replaces XML_NO_ERROR with XML_SUCCESS
Unfortunately while that patch fixed the FTBFS in raspbian stretch at 
the time the package is now failing for us for a different reason. While 
I saw this in raspbian I have no reason to belive it is raspbian specific.



In file included from /usr/include/spnav.h:33:0,
 from /<>/gazebo-7.3.0+dfsg/gazebo/gui/SpaceNav.cc:27:
/usr/include/google/protobuf/stubs/logging.h:66:7: error: expected identifier 
before 'int'
 class Status;
   ^
/usr/include/google/protobuf/stubs/logging.h:66:7: error: multiple types in one 
declaration
In file included from /usr/include/google/protobuf/stubs/common.h:45:0,
 from /usr/include/google/protobuf/stubs/atomicops.h:59,
 from 
/usr/include/google/protobuf/stubs/atomic_sequence_num.h:33,
 from /usr/include/google/protobuf/arena.h:52,
 from /usr/include/google/protobuf/message.h:118,
 from 
/<>/gazebo-7.3.0+dfsg/gazebo/transport/CallbackHelper.hh:20,
 from 
/<>/gazebo-7.3.0+dfsg/obj-arm-linux-gnueabihf/gazebo/transport/transport.hh:2,
 from 
/<>/gazebo-7.3.0+dfsg/gazebo/gui/SpaceNavPrivate.hh:23,
 from /<>/gazebo-7.3.0+dfsg/gazebo/gui/SpaceNav.cc:31:
/usr/include/google/protobuf/stubs/logging.h:90:32: error: expected ')' before 
'::' token
   LogMessage&  operator<<(const ::google::protobuf::util::Status&  status);
^~
/usr/include/google/protobuf/stubs/logging.h:90:32: error: 
'google::protobuf::internal::LogMessage&  
google::protobuf::internal::LogMessage::operator<<(...)' must not have variable 
number of arguments
/usr/include/google/protobuf/stubs/logging.h:90:26: error: expected ';' at end 
of member declaration
   LogMessage&  operator<<(const ::google::protobuf::util::Status&  status);
  ^
In file included from /usr/include/spnav.h:33:0,
 from /<>/gazebo-7.3.0+dfsg/gazebo/gui/SpaceNav.cc:27:
/usr/include/google/protobuf/stubs/logging.h:90:58: error: expected 
unqualified-id before 'int'
   LogMessage&  operator<<(const ::google::protobuf::util::Status&  status);
  ^
gazebo/gui/CMakeFiles/gazebo_gui.dir/build.make:1194: recipe for target 
'gazebo/gui/CMakeFiles/gazebo_gui.dir/SpaceNav.cc.o' failed

http://buildd.raspbian.org/status/fetch.php?pkg=gazebo=armhf=7.3.0%2Bdfsg-2%2Brpi1%2Bb1=1472782288

I'm guessing some sort of header conflict, I will try to take a look but not 
promising anything. Ideas welcome.

--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Processed: re: s/XML_NO_ERROR/XML_SUCCESS/

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 835427 +patch
Bug #835427 [src:gazebo] gazebo: FTBFS in unstable (error: 'XML_NO_ERROR' is 
not a member of 'tinyxml2')
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
835427: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835427
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers