Package: gyoto,gyoto-doc
Version: 1.3.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.
>From the attached log (scroll to the bottom...):
Select
Followup-For: Bug #919651
Control: found -1 0.101-3
Hi,
you added B+R against non-existing libmoops instead of libmoops-perl.
Andreas
Package: python3-sbml5-doc
Version: 5.17.2+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It installed fine in 'stable', then the upgrade to 'sid' fails
because it tries to overwri
Followup-For: Bug #855958
Control: retitle -1 xserver-xorg-video-nv: FTBFS with current Xorg:
nv_driver.c:1181:6: error: too many arguments to function
'pScreen->BlockHandler'
Control: tags -1 ftbfs
Hi,
CC nv_driver.lo
In file included from ../../src/nv_include.h:19,
fr
On 2019-01-19 21:55, Kienan Stewart wrote:
> I tested a proposed patch from the upstream github repository which allows
> the package to build and run : https://github.com/snare/voltron/pull/243
>
> I'm not sure if there are other side-effects to the patch, since the async
> (now asynchronous) v
Followup-For: Bug #905415
Control: reopen -1
Control: reassign -1 libnode-dev 10.15.0~dfsg-8
Control: retitle -1 libnode-dev: broken symlinks:
/usr/include/nodejs/deps/uv/include/{uv,uv.h} -> ../../../../{uv,uv.h}
Hi,
the package reorganisation changed th eissue but did not completely
resolve it
Package: jupyter-sphinx-theme-common
Version: 0.0.6+ds1-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m30.4s ERROR: FAIL: Brok
Package: sqwebmail
Version: 6.0.0+1.0.5-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m54.4s ERROR: FAIL: Broken symlinks:
/
Package: node-istanbul
Version: 0.4.5+ds-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
1m33.0s ERROR: FAIL: Broken symlinks:
Package: lirc-doc
Version: 0.10.1-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m24.4s ERROR: FAIL: Broken symlinks:
/usr/sh
Package: ruby-rails-assets-highlightjs
Version: 9.12.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m30.0s ERROR: FAIL: Broke
Package: ruby-rails-assets-markdown-it
Version: 8.4.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m28.5s ERROR: FAIL: Broken
Package: tclxml-dev
Version: 1:3.2.7-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m28.5s ERROR: FAIL: Broken symlinks:
/usr
Package: python3-link-grammar
Version: 5.5.1-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
1m41.0s ERROR: FAIL: Broken symlinks
Package: prelude-lml
Version: 4.1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package removes files that
were installed by another package.
The removed files were already present before the package was installed,
they ma
Followup-For: Bug #863675
Control: reopen -1
Control: found -1 1:10.3.12-1
So, which package is shipping /usr/bin/mysql_config ?
libmariadb-dev (which got the B+R added) or libmariadb-dev-compat ?
Unpacking libmariadb-dev-compat:amd64 (1:10.3.12-1) ...
dpkg: error processing archive
/var/cac
On 2019-01-20 13:17, Andreas Beckmann wrote:
> So, which package is shipping /usr/bin/mysql_config ?
How weird is that?
-rwxr-xr-x 1 root root 14840 Jan 8 21:52 /usr/bin/mariadb_config
lrwxrwxrwx 1 root root14 Jan 8 21:52 /usr/bin/mysql_config ->
mariadb_config
lrwxrwxrwx 1 roo
On 2019-01-20 13:39, Andreas Beckmann wrote:
> Could we please have the symlinks in one direction only?
There is also this Lintian warning:
W: mariadb-10.3 source: binaries-have-file-conflict libmariadb-dev
libmariadb-dev-compat usr/include/mysql
Both libmariadb-dev and libmariadb-dev-compat
Package: ceph-common
Version: 12.2.10+dfsg1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + ceph-osd
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' f
Package: libppl-c4,libppl-swi
Version: 1:1.2-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old
Package: swi-prolog-odbc
Version: 8.0.0+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrit
Package: corosync-qnetd
Version: 3.0.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' fails.
>From the attached log (scrol
Package: exim4-config
Version: 4.92~RC4-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + exim4-daemon-light
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'bus
Package: libconfig-model-backend-yaml-perl
Version: 2.133-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + libconfig-model-perl
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then
Package: grub2-common
Version: 2.02+dfsg1-10
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + grub-cloud-amd64
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'bu
Package: yui-compressor
Version: 2.4.7-2
Severity: serious
Tags: jessie
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + libjs-protoaculous
Control: found -1 libjs-protoaculous/5
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition o
Package: netdata
Version: 1.12.0~rc3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
>From th
Package: ibus-keyman
Version: 11.0.103-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
>From
Package: python-greenlet-dev
Version: 0.4.15-1
Severity: serious
Hi,
your package ships the header file(s):
/usr/include/python3.7/greenlet/greenlet.h
but /usr/include/python3.7 is a symlink to python3.7m in
libpython3.7-dev. This may result in silent file overwrites or depending
on the unpac
Package: python3-persistent
Version: 4.2.2-1
Severity: serious
Hi,
your package ships the header file(s):
/usr/include/python3.7/persistent/cPersistence.h
/usr/include/python3.7/persistent/ring.h
but /usr/include/python3.7 is a symlink to python3.7m in
libpython3.7-dev. This may result in sil
Package: python3-bsddb3
Version: 6.2.6-2
Severity: serious
Hi,
your package ships the header file(s):
/usr/include/python3.7/bsddb3/bsddb.h
but /usr/include/python3.7 is a symlink to python3.7m in
libpython3.7-dev. This may result in silent file overwrites or depending
on the unpacking order
Package: python3-pygame
Version: 1.9.4.post1+dfsg-2
Severity: serious
Hi,
your package ships the header file(s):
/usr/include/python3.7/pygame/_camera.h
/usr/include/python3.7/pygame/_pygame.h
/usr/include/python3.7/pygame/_surface.h
/usr/include/python3.7/pygame/bitmask.h
/usr/include/pyth
Package: python3-zope.proxy
Version: 4.2.0-1
Severity: serious
Hi,
your package ships the header file(s):
/usr/include/python3.7/zope.proxy/proxy.h
but /usr/include/python3.7 is a symlink to python3.7m in
libpython3.7-dev. This may result in silent file overwrites or depending
on the unpackin
Package: python3-igraph
Version: 0.7.1.post6-6
Severity: serious
Hi,
your package ships the header file(s):
/usr/include/python3.7/python-igraph/igraphmodule_api.h
but /usr/include/python3.7 is a symlink to python3.7m in
libpython3.7-dev. This may result in silent file overwrites or depending
Package: obitools
Version: 1.2.12+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
See policy 7.6
Source: mariadb-10.1
Version: 1:10.1.37-3
Severity: serious
Tags: sid buster
buster should only ship one mariadb version, and as it looks, that will
be 10.3
Andreas
Control: reopen -1
Control: tags -1 =
On 2019-01-25 08:51, Debian Bug Tracking System wrote:
> This seems to be a temporary problem, since piuparts log seems fine now:
> https://piuparts.debian.org/sid/pass/dicoweb_2.7-1.log
That logfile predates the bug report.
I can still reproduce it in my pi
Package: i2p
Version: 0.9.38-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package modifies conffiles.
This is forbidden by the policy, see
https://www.debian.org/doc/debian-policy/ch-files.html#configuration-files
10.7.3:
Source: openhft-chronicle-wire
Version: 1.16.18-1
Severity: serious
Justification: fails to build from source
Hi,
openhft-chronicle-wire/experimental recently started to FTBFS with these
errors:
C[1;31mERRORESC[m] Failed to execute goal
ESC[32morg.apache.maven.plugins:maven-compiler-plugin:3.8.
Source: syslog-ng
Version: 3.19.1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Hi,
syslog-ng/experimental FTBFS during the binary-indep-only build, i.e. if
built with dpkg-buildpackage -A:
debian/rules build-indep
make: 'build-indep' is up t
Source: node-evp-bytestokey
Version: 1.0.3-4
Severity: serious
Justification: fails to build from source
Hi,
the old transitional package nodejs-dev is no longer built, please
update your build-depends to libnode-dev.
Andreas
Source: node-xmpp
Version: 0.3.2-3
Severity: serious
Hi,
the old transitional package nodejs-dev is no longer built, please
update your build-depends to libnode-dev.
Andreas
Source: node-nodedbi
Version: 1.0.12-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Hi,
the old transitional package nodejs-dev is no longer built, please
update your build-depends to libnode-dev.
Andreas
Package: node-gyp
Version: 3.8.0-2
Severity: serious
Hi,
nodejs-dev is no longer built. Please check whether you can use
libnode-dev as a replacement.
Andreas
On 2019-01-26 17:25, Rene Engelhard wrote:
> the package changed any (well, arch-specific) to all (transitional package),
> maybe
> that confuses dpkg-maintscript-helper? Any suggestion to get out of this?
dpkg-maintscript-helper does not work properly on any->all (or vice
versa) changes. #813455
On 2019-01-26 17:51, Rene Engelhard wrote:
> Except the "obvious" solution of keeping the transitional package
> arch-dep and changing the -common to -core in maintscript... Needs to be
> tested.
should work with an appropriate version in the .maintscript file
> Would like to avoid that, though;
Followup-For: Bug #849574
Hi,
nowadays it also fails during the binary-arch build:
debian/rules override_dh_install
On 2018-12-17 04:48, أحمد المحمودي wrote:
> On Wed, Dec 05, 2018 at 03:15:59AM +0100, Andreas Beckmann wrote:
>> Setting up python3 (3.7.1-2) ...
>> [Errno 2] No such file or directory: '/usr/share/dicoweb/settings.py'
> ---end quoted text---
>
> '/usr/
Followup-For: Bug #918858
Looking at the maintainer scripts, they all seem to have been copied
from the python-meep package without updating the referenced package
name from "python-meep" to "python-meep-?"
Instead of hardcoding the package name, you could also use
"$DPKG_MAINTSCRIPT_PACKAGE"
Control: severity -1 normal
On Tue, 15 Jan 2019 12:22:30 +0200 Graham Inggs wrote:
> Recent rebuilds of deal.ii on s390x have been failing with the following
> errors:
deal.ii has been removed from s390x, downgrading the severity.
Andreas
Package: ocsinventory-server
Version: 2.6~RC+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package is not
installable in experimental:
The following packages have unmet dependencies:
ocsinventory-reports : Depends: li
Source: gstreamer-vaapi
Version: 1.15.1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Hi,
gstreamer-vaapi/experimental FTBFS on the 32-bit architectures:
https://buildd.debian.org/status/package.php?p=gstreamer-vaapi&suite=experimental
from t
Package: orthanc-mysql
Version: 1.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Package: rainloop
Version: 1.11.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
a test with piuparts revealed that your package uses files from
/usr/share/doc in its maintainer scripts which is a violation of
Policy 12.3: "Packages must not require the existence of a
Source: knot-resolver
Version: 2.3.0-3~bpo9+1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
User: debian...@lists.debian.org
Package: python3-adios
Version: 1.13.1-14
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails.
>From the attached log (scroll
Package: python-jupyter-sphinx-theme
Version: 0.0.6+ds1-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually me
Control: tag -1 - experimental
Control: close -1
There is no longer an outdated version in experimental.
Andreas
Package: distcc
Version: 3.3.2-7
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails.
>From the attached log (scroll to the bo
Followup-For: Bug #911616
Control: tag -1 pending
Control: tag 875430 pending
Control: tag 910925 pending
Control: tag 690771 pending
Control: tag 918646 pending
Hi Rob,
this issue is cuasing a lot of upgrade failures in piuparts.
I've prepared a NMU of the emacs package fixing this and some more
Hi Guillem,
do you have any recommendations for this trigger loop?
I think at this point it is already dpkg 1.19.4 that is running
(dpkg is being upgraded during the same run).
On 2019-01-28 14:32, Christian Marillat wrote:
> On 28 janv. 2019 14:17, Andreas Beckmann wrote:
>
>
Source: lombok
Version: 1.16.22-6
Severity: serious
Control: block 920037 with -1
Hi,
your package still Build-Depends on openjdk-8-jdk which will not be part
of buster.
Andreas
Package: pki-base-java
Version: 10.6.8-2
Severity: serious
Control: block 920037 with -1
Hi,
buster will ship with openjdk-11 only.
Andreas
Package: openrocket
Version: 15.03.4
Severity: serious
Control: block 920037 with -1
Hi,
buster will ship with openjdk-11 only.
Andreas
Package: elpa-projectile
Version: 2.0.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' fails.
>From the attached log (scro
Package: freedink
Version: 109.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other pack
Package: libpam-modules
Version: 1.1.8-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
On 2019-01-28 20:45, b...@debian.org wrote:
> Hi,
>
> Would you mind detailing how you invoke piuparts so it gives that error?
input comes from some script using dose to find potential candidates for
file overwrites problems across distros
> I've been running it for an hour and I only get succes
Package: elpa-lsp-ui
Version: 6.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
>From the a
Package: libsbml5-dev
Version: 5.17.2+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m27.4s ERROR: FAIL: Broken symlinks:
Package: zfs-dkms
Version: 0.7.12-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Package: golang-golang-x-tools
Version: 1:0.0~git20190125.d66bd3c+ds-3
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Hi,
automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detecte
Package: docker.io
Version: 18.09.1+dfsg1-4
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Hi,
automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:
On 2019-01-30 20:12, Petter Reinholdtsen wrote:
>
> [Andreas Beckmann]
>> zfs-dkms does not build a kernel module for e.g. the 4.19.0-2-686 i386
>> kernel. This happened in a i386 chroot on a amd64 host, but this should
>> not really be a problem, since this setup works fi
Package: sysbench
Version: 0.4.12-1.2
Severity: serious
Tags: sid buster
Control: close -1 1.0.15+ds-1
Hi,
sysbench needs to be rebuilt against libmariadb3, this has happened in
unstable, but that version does not migrate to testing due to the FTBFS
on armhf and the missing availability of the ne
Source: qt4-x11
Version: 4:4.8.7+dfsg-17
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Hi,
qt4-x11 did FTBFS against mariadb-10.3 on a few architectures:
https://buildd.debian.org/status/package.php?p=qt4-x11&suite=unstable
but given that you p
Source: spatialite
Version: 5.0.0~beta0-1~exp1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Hi,
during a test rebuild of spatialite/experimental I noticed that it hangs
during the virtualknn test. After killing that process the build
continued a
Followup-For: Bug #863968
Control: severity -1 wishlist
Control: retitle -1 mariadb-client-10.3: move /usr/bin/mytop to a separate
package
Looks like we have Conflicts+Replaces since debian/1%10.3.11-1_exp1~135
Andreas
On 2019-02-02 11:28, Sebastian Andrzej Siewior wrote:
> I suggest to simply drop that, the symbol based dependecy is enough.
> ckermit was removed from unstable. We should fix this in stretch. Is someone
> working on that or should I prepare a NMU? A am against a binNMU: It will fix
I'm not going
Package: python3-surfer
Version: 0.9.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite othe
Package: open-infrastructure-ceph-tools
Version: 20180915-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it trie
Source: pluto-find-orb
Version: 0.0~git20180227-2
Severity: serious
Justification: fails to build from source
Hi,
pluto-find-orb/experimental recently started to FTBFS, probably due to
an updated build-dependency:
[...]
cc -g -O2 -fdebug-prefix-map=/build/pluto-find-orb-0.0~git20180227=.
-fstac
Package: icmake,icmake-doc
Version: 9.02.08-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Source: kicad
Version: 5.1~20190127.4fc692f+dfsg1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Hi,
kicad/experimental recently started to FTBFS with the new GLM:
-- Found GLM: /usr/include (found suitable version "0.9.9.3", minimum required
Source: gnunet-gtk
Version: 0.11.0~pre66-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Hi,
gnunet-gtk/experimental recently started to FTBFS, this is probably
related to the upload of gnutls28 3.6.x to unstable. The previous
successful experime
Package: openhft-chronicle-bytes
Version: 1.16.25-1
Severity: serious
Justification: fails to build from source
Hi,
openhft-chronicle-bytes FTBFS in a i386 pbuilder chroot, while it builds
successfully in an amd64 pbuilder chroot.
Andreas
openhft-chronicle-bytes_1.16.25-1.log.gz
Description:
Package: zfs-dkms
Version: 0.7.12-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' fails.
The problem is the order chosen by
On 2019-02-04 11:13, Adrian Bunk wrote:
>> openhft-chronicle-bytes FTBFS in a i386 pbuilder chroot, while it builds
>> successfully in an amd64 pbuilder chroot.
>
> Why is FTBFS on a binary-all package on !amd64 itself an RC bug?
I haven looked in detail in the FTBFS. It just smells fishy ...
Fee
Source: frr
Version: 6.0.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi
Hi David,
On 2019-02-04 22:01, David Lamparter wrote:
> I've added Conflicts: lines, as that seemed to be the most conservative
> option to me. ("Replaces: quagga" is a 'layer 9' discussion that I
> think it's a bit early to have at this point.)
>
> If you have any comments/opinions/input, I'd a
Control: retitle -1 starpu: FTBFS while building documentation
Hi Paolo,
On Mon, 4 Feb 2019 01:17:19 +0100 Paolo Greppi
wrote:
> Source: starpu
> Severity: serious
> I tested your package against a draft package for doxygen 1.8.15:
> https://bugs.debian.org/919413
>
> and it FTBFS with this er
Package: mtail
Version: 3.0.0~rc19-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.
From the attached log (scroll to the bottom...):
Selecting pr
Control: found -1 0.9.0-2
On 2019-02-04 14:54, Debian Bug Tracking System wrote:
>* Breaks / Replaces: python-surfer (<= 0.7-1)
buster has 0.7-2.1 with the file in the old location.
Andreas
Package: python3-spf-engine
Version: 2.9.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite
Control: found -1 1:2.24.5-3
On 2019-02-05 01:24, Debian Bug Tracking System wrote:
>* Fix "both ship usr/share/doc/libgtkmm-2.4-dev/examples/*":
> Install all demos into the -dev package, and only there;
> and also install Makefile*.
libgtkmm-2.4-dev now needs Breaks+Replaces: libg
Package: lxqt-branding-debian
Version: 0.14.0
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It installed fine in 'stable', then the upgrade to 'sid' fails
because it tries to overwrite o
Control: severity -1 important
Control: tag -1 moreinfo
We currently have no ppc64el binaries for cuneiform, so this is not a
regressions and therefore not RC.
On Wed, 6 Feb 2019 14:50:47 +0100 "Thierry fa...@linux.ibm.com"
wrote:
> --- images/phototest.tif.txt 2011-04-19 12:49:57.0 +00
Followup-For: Bug #919442
Control: affects -1 + python3-dmidecode-dbg
Control: found -1 3.12.2-7
Hi,
your .maintscript files are wrong. Obviously you wanted symlink_to_dir,
but you used dir_to_symlink.
This messes up the package on reinstallation.
Please also use the (optional) 'prior-version' a
Package: netdata-core-no-sse
Version: 1.11.1+dfsg-7
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severi
Package: openstack-dashboard
Version: 3:14.0.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails.
>From the attached log (
601 - 700 of 8196 matches
Mail list logo
