Bug#1004260: pybuild-plugin-pyproject: Uninstallable

[David Steele]

Package: pybuild-plugin-pyproject
Version: 5.20220119
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: ste...@debian.org


Dear Maintainer,

The dh-python-pep517 meta package, required for poetry builds, and 
satisfied solely by this package, fails to install.


$ sudo apt-get install dh-python dh-python-pep517
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
dh-python is already the newest version (5.20220119).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 dh-python-pep517 : Depends: dh-python (= 5.20211225) but 5.20220119 is 
to be installed

E: Unable to correct problems, you have held broken packages.

Corroborated by the current debcheck report - 
https://qa.debian.org/debcheck.php?dist=unstable=dh-python


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (700, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.14.0-2-amd64 (SMP w/6 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: 
LC_ALL set to en_US.UTF-8), LANGUAGE not set

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pybuild-plugin-pyproject depends on:
ii  dh-python  5.20220119
ii  python3-build  0.7.0-2
ii  python3-installer  0.4.0+dfsg1-2
ii  python3-tomli  1.2.2-2

pybuild-plugin-pyproject recommends no packages.

pybuild-plugin-pyproject suggests no packages.

-- no debconf information



OpenPGP_signature
Description: OpenPGP digital signature

Bug#981145: todo.txt-gtd: missing Breaks+Replaces: turnin-ng

[David Steele]

control: severity -1 normal


On Tue, Jan 26, 2021 at 5:51 PM Andreas Beckmann  wrote:

> Package: todo.txt-gtd
> Version: 0.5
> 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 other packages files without declaring a
> Breaks+Replaces relation.
>

This text is not correct.

What section is this? That should be part of the report.


> See policy 7.6 at
>
> https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces


I'd accept this as an RC rationale if both packages existed in the same
distribution. You should tune your severity logic.

I'm willing to address it, but not as an RC bug.

joy.

Dave

Bug#976111: topydo 0.13-3 upload seems to hang ci.debian.net workers while testing todo.txt-base

[David Steele]

On Sun, Nov 29, 2020 at 3:51 PM Paul Gevers  wrote:

> Source: topydo
> Version: 0.13-3
> Severity: serious
> X-Debbugs-CC: debian...@lists.debian.org
> User: debian...@lists.debian.org
> Usertags: issue
>
> Dear David,
>
> I have no idea what's happening, but currently we have multiple workers
> (on different architectures) off-line on the ci.debian.net
> infrastructure. In the current (short) list of pending tests,
> todo.txt-base sticks out as being triggered (by topydo) some time ago
> and waiting on all architectures. armhf finished (tmpfail) while I was
> writing this message so I noticed it already ran multiple times but the
> test on armhf times out after 2:55 hours (previous tests were under 1
> minute) with an error in autopkgtest so is treated as tmpfail (and
> retried).
>
> Can you help us investigate what's going on? What is topydo doing?


Topydo is a package implementing a todo.txt client.

Todo.txt-base is a helper program adding features to todo.txt clients.

Both are new, and I am new to the alternatives environment. I started by
having todo.txt-base serve as the application installed as the todo/todo.txt
application. Packages using this model were accepted, but turned out
to be unworkable as I attempted to expand the ecosystem.

So there are new versions of topydo and todo.txt-base in sid which use
the todo.txt provider (topydo) as the home for the "todo" and "todo.txt"
applications. It calls todo.txt-base features as necessary for the added
features. Autopkgtests pass in sid.

All works well, until you test the new version of one package along with
the old version of the other. In one scenario there is a recursion, where
topydo ends up calling itself via the alternatives hook.

I didn't worry too much about this when I submitted the new packages,
because the issue was transient, and the common popcon is like 5. I
failed to consider that ci would evaluate the packages independently,
and would choke.

I'm reworking the packages so that they can manage this upgrade
without complaint. That process will take at least days. I'd be willing to
consider more drastic means to resolve this, either by overriding the
failures this one time, or by deleting the packages from the distribution
and starting fresh.

-- 
AE0D BF5A 92A5 ADE4 9481  BA6F 8A31 71EF 3661 50CE

Bug#935731: comitup: port to python 3

[David Steele]

 Severity: normal
thanks

There is an erroneous "Suggests" control file listing for the Python 2
package. This has no effect on the usability of the package. The issue
doesn't rate autoremoval 18 months before the next stable release.

The fix is in git, and will be released in due course.

https://github.com/davesteele/comitup/commit/43459f9

Bug#934484: python-pytest-asyncio: "Cannot import name 'transfer_markers'" with current pytest

[David Steele]

Source: python-pytest-asyncio
Version: 0.9.0-1
Severity: serious
Tags: upstream

Dear Maintainer,

Since the recent upgrade of pytest, tests involving pytest-asyncio[1]
are failing with:

ImportError: cannot import name 'transfer_markers' from
'_pytest.python' (/usr/lib/python3/dist-packages/_pytest/python.py)

A quick search suggests the problem is a compatibility issue with
pytest-asyncio[2], which
has been resolved upstream[3].

The package needs to be upgraded to 0.10.0.

[1] 
https://ci.debian.net/data/autopkgtest/unstable/amd64/a/aiofiles/2707314/log.gz
[2] https://github.com/pytest-dev/pytest-asyncio/issues/104
[3] https://github.com/pytest-dev/pytest-asyncio/pull/105


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (700, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/6 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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

-- 
AE0D BF5A 92A5 ADE4 9481  BA6F 8A31 71EF 3661 50CE

Bug#926487: GNOME Gmail incompatibilty with Gmail

[David Steele]

Package: gnome-gmail
Version: 2.5.6-1
Severity: Serious

If GNOME Gmail is used to "Send To..." on a file via Nautilus, the
resulting uploaded message is not rendered properly - not showing the
Subject or attached file. It is not possible to send the message that
is opened.

This happens because the service does not properly handle mime message
with no body. The fix would be to always add a body to the message.

As a result of this issue, a core capability of the package is broken.
Setting to Serious.

--
AE0D BF5A 92A5 ADE4 9481  BA6F 8A31 71EF 3661 50CE

Bug#902383: reproducible-builds.org: test host-specific FTBFS failures on i386

[David Steele]

Package: jenkins.debian.org
Severity: Serious

For some jobs, it appears that profitbricks-build2-i386.debian.net
repeatedly returns FTBFS, while profitbricks-build6-i386.debian.net always
succeeds. This situation has been in place for 2 months.

There is a FTBFS failure currently reported for Sirikali in Buster and Sid.
The failure is persistent across re-runs.

I can't reproduce the failure locally. The formal build succeeded.

Looking closer, success and failure is tied to the worker hardware. build2
always fails, whether running the first run or the second. build6 always
passes, when used for the first run.

I'm not able to see what the difference may be.

Note that i386 has the highest current FTBFS count across architectures.


-- 
AE0D BF5A 92A5 ADE4 9481  BA6F 8A31 71EF 3661 50CE

Bug#863671: Commit fix?

[David Steele]

Note that the CVE references 1ebc60b, which removes a "/bin/sh"
call, addressing the vulnerability.

Your patch incorporates the relevant code added by that commit
(though it replaces a system() call, instead).


https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9059

https://github.com/npat-efault/picocom/commit/1ebc60b

-- 
AE0D BF5A 92A5 ADE4 9481  BA6F 8A31 71EF 3661 50CE

Bug#855920: Can't reproduce either

[David Steele]

On Tue, Apr 11, 2017 at 12:31 PM, Ivo De Decker <iv...@debian.org> wrote:
> Hi,
>
> On Mon, Mar 27, 2017 at 10:32:20PM -0400, David Steele wrote:
>> I've built 0.9.6-1 amd64 sid and stretch, desktop and pdebuild, with
>> and without networking, and have not seen the failure. Stretch build
>> attached.
>
> Same here. I tried in a sid pbuilder chroot on a jessie machine, and the build
> succeeds.
>

Note this failure in the original fail log:

==
FAIL: testGetTime (fail2ban.tests.datedetectortestcase.DateDetectorTest)
--
Traceback (most recent call last):
  File 
"/<>/.pybuild/pythonX.Y_3.5/build/fail2ban/tests/datedetectortestcase.py",
line 75, in testGetTime
self.assertEqual(datelog, dateUnix)
AssertionError: 1106517599.0 != 1106513999.0



They differ by 3600 seconds.

-- 
AE0D BF5A 92A5 ADE4 9481  BA6F 8A31 71EF 3661 50CE

Bug#853916: encfs '-S' vulnerability

[David Steele]

Package: encfs
Version: 1.9.1-3
Severity: serious
thanks


Recently, a change in Encfs was found to have broken cryptkeeper, causing it
to use the password 'p' for all operations, regardless of user input 
(#852751)[3].
The bug was closed by removing cryptkeeper from Debian.

The issue, however, remains. Sirikali, which manages multiple userspace
filesystems including Encfs, suffers from the same failure (#853874).
An upstream Encfs representative has indicated that the problem will be fixed
there [1], though no change has been pushed to date [2].

The overall issue should be RC critical for Stretch. I've marked this as 
'serious',
indicating that the problem will be fixed in Encfs for the Stretch release. If 
this
is not the case, close or demote, and I'll elevate in Sirikali.

[1] https://github.com/tomm/cryptkeeper/issues/23#issuecomment-276304206
[2] https://github.com/vgough/encfs
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852751

-- 
AE0D BF5A 92A5 ADE4 9481  BA6F 8A31 71EF 3661 50CE


signature.asc
Description: GooPG digital signature

Bug#715064: Broken library symlink detected in firebird-dev

[David Steele]

Package: firebird-dev
Version: 2.5.2.26540.ds4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/x86_64-linux-gnu/libfbembed.so
- libfbembed.so.2.5.2


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 22:13:13 EST

Package: firebird-dev
Source: firebird2.5
Version: 2.5.2.26540.ds4-1
Installed-Size: 345
Maintainer: Debian Firebird Group pkg-firebird-gene...@lists.alioth.debian.org
Architecture: amd64
Replaces: firebird2.0-dev, firebird2.1-dev ( 2.1.4.18393-0.ds2-4~), 
firebird2.5-dev ( 2.5.1.26349-0~rc1.ds4-3~)
Provides: firebird2.1-dev, firebird2.5-dev
Depends: libfbclient2 (= 2.5.2.26540.ds4-1), libib-util, firebird2.5-common-doc 
(= 2.5.2.26540.ds4-1)
Suggests: libfbembed2.5, firebird2.5-examples
Breaks: firebird2.0-dev, firebird2.1-dev ( 2.1.4.18393-0.ds2-4~), 
firebird2.5-dev ( 2.5.1.26349-0~rc1.ds4-3~)
Description: Development files for Firebird - an RDBMS based on InterBase 6.0 
code
Homepage: http://firebirdsql.org/
Description-md5: b979fd7ee09f3a6d095da05eba782056
Tag: devel::lang:c, devel::lang:c++, devel::library, role::devel-lib
Section: libdevel
Priority: optional
Filename: pool/main/f/firebird2.5/firebird-dev_2.5.2.26540.ds4-1_amd64.deb
Size: 30666
MD5sum: 20792e20c1663376ca00fff065c6791b
SHA1: 917e6fd904d311e5c6b4942092b7e3722398d282
SHA256: e5d10cc88ff7d8fb2a95d08e48f5a3a6886b4bd8321afaa19bf1eba8cb77118b

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
firebird-dev=2.5.2.26540.ds4-1
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'firebird-dev=2.5.2.26540.ds4-1'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpHzZNgK
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpHzZNgK
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpHzZNgK', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.2s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpHzZNgK', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.2s DEBUG: Starting command: ['chroot', '/var/tmp/tmpHzZNgK', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.2s DEBUG: Command ok: ['chroot', '/var/tmp/tmpHzZNgK', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.2s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.2s DEBUG: Created policy-rc.d and chmodded it.
0m1.2s DEBUG: Starting command: ['chroot', '/var/tmp/tmpHzZNgK', 'eatmydata', 
'apt-get', 'update']
0m5.3s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib 

Bug#715075: Broken library symlink detected in libcwnn-dev

[David Steele]

Package: libcwnn-dev
Version: 1.1.1~a021+cvs20100325-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libcwnn.so
- libcwnn.so.0.0.0


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:43:10 EST

Package: libcwnn-dev
Source: freewnn
Version: 1.1.1~a021+cvs20100325-6
Installed-Size: 404
Maintainer: Keita Maehara maeh...@debian.org
Architecture: amd64
Replaces: cwnn-dev, freewnn-cserver-dev
Conflicts: cwnn-dev, freewnn-cserver-dev
Description: Header files and static library for cWnn (FreeWnn cserver)
Homepage: http://sourceforge.jp/projects/freewnn/
Description-md5: fff703ab6545601ccb55cebb5204054b
Tag: accessibility::input, culture::chinese, culture::taiwanese,
 devel::library, role::devel-lib
Section: libdevel
Priority: optional
Filename: pool/main/f/freewnn/libcwnn-dev_1.1.1~a021+cvs20100325-6_amd64.deb
Size: 124586
MD5sum: a1b130266c6f295663159fa179992e77
SHA1: 3592fe7da674f861f437bd8a82aaaeb7ef2fa758
SHA256: f7d358c6b57aa5d8bb62c36e8930bb187cc2185f05ca7f037e54c65bdfcc6118

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libcwnn-dev=1.1.1~a021+cvs20100325-6
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libcwnn-dev=1.1.1~a021+cvs20100325-6'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpa6IQe8
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpa6IQe8
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpa6IQe8', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.5s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpa6IQe8', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.5s DEBUG: Starting command: ['chroot', '/var/tmp/tmpa6IQe8', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.5s DEBUG: Command ok: ['chroot', '/var/tmp/tmpa6IQe8', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.5s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.5s DEBUG: Created policy-rc.d and chmodded it.
0m1.5s DEBUG: Starting command: ['chroot', '/var/tmp/tmpa6IQe8', 'eatmydata', 
'apt-get', 'update']
0m7.0s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 4s (2761 kB/s)
  Reading package lists...

Bug#715074: Broken library symlink detected in libboost-graph-parallel1.53-dev

[David Steele]

Package: libboost-graph-parallel1.53-dev
Version: 1.53.0-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libboost_graph_parallel.so
- libboost_graph_parallel.so.1.53.0


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:26:16 EST

Package: libboost-graph-parallel1.53-dev
Source: boost1.53
Version: 1.53.0-5
Installed-Size: 756
Maintainer: Debian Boost Team pkg-boost-de...@lists.alioth.debian.org
Architecture: amd64
Depends: libboost1.53-dev (= 1.53.0-5), libboost-serialization1.53-dev (= 
1.53.0-5), libboost-test1.53-dev (= 1.53.0-5)
Recommends: libboost-graph-parallel1.53.0 (= 1.53.0-5)
Conflicts: libboost-graph-parallel1.42-dev, libboost-graph-parallel1.46-dev, 
libboost-graph-parallel1.48-dev, libboost-graph-parallel1.49-dev, 
libboost-graph-parallel1.50-dev, libboost-graph-parallel1.52-dev
Description: generic graph components and algorithms in C++
Homepage: http://www.boost.org/libs/graph_parallel/
Description-md5: 4f57c2a6e2a339b83d9c59b83812e4c6
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: optional
Filename: 
pool/main/b/boost1.53/libboost-graph-parallel1.53-dev_1.53.0-5_amd64.deb
Size: 140052
MD5sum: 45ec40b735b342517b6a1d6675cb28c5
SHA1: 8b9480f4bf6362c88f1e9e04d618b6599296f0f3
SHA256: 5eb363cd5d2b8eceea39653afa24530290ca77f785c8fe3b25b280013e24d4ae

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libboost-graph-parallel1.53-dev=1.53.0-5
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libboost-graph-parallel1.53-dev=1.53.0-5'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpJBr27B
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpJBr27B
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpJBr27B', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpJBr27B', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpJBr27B', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: Command ok: ['chroot', '/var/tmp/tmpJBr27B', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.3s DEBUG: Created policy-rc.d and chmodded it.
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpJBr27B', 'eatmydata', 
'apt-get', 'update']
0m6.7s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages 

Bug#715070: Broken library symlink detected in libapron-dev

[David Steele]

Package: libapron-dev
Version: 0.9.10-5.2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libpolkaMPQ.so
- libpolkaMPQ.so.0
  /usr/lib/libboxMPQ.so
- libboxMPQ.so.0
  /usr/lib/libapron.so
- libapron.so.0
  /usr/lib/libboxD.so
- libboxD.so.0
  /usr/lib/liboctMPQ.so
- liboctMPQ.so.0
  /usr/lib/libpolkaRll.so
- libpolkaRll.so.0
  /usr/lib/libboxMPFR.so
- libboxMPFR.so.0
  /usr/lib/liboctD.so
- liboctD.so.0


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:21:48 EST

Package: libapron-dev
Source: apron
Version: 0.9.10-5.2
Installed-Size: 1636
Maintainer: Debian OCaml Maintainers debian-ocaml-ma...@lists.debian.org
Architecture: all
Depends: libgmp3-dev, libmpfr-dev, libppl-dev
Description: an abstract interpretation library
Homepage: http://apron.cri.ensmp.fr/library/
Description-md5: 16f96b6087ed491a2c7708d5d8fef746
Tag: devel::lang:c, devel::library, devel::testing-qa, implemented-in::c,
 role::devel-lib, use::analysing, use::checking
Section: libdevel
Priority: optional
Filename: pool/main/a/apron/libapron-dev_0.9.10-5.2_all.deb
Size: 197276
MD5sum: 69593e88e4b4970a2fcd67c0e575d221
SHA1: 99567f0270f91fdbd3af944986f73e3fa491f039
SHA256: a90655c195bce8c9d99ba0157323ced36e7c915faf0d8ba3507aa41cd4e216b1

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libapron-dev=0.9.10-5.2
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libapron-dev=0.9.10-5.2'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpq72xEy
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpq72xEy
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpq72xEy', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpq72xEy', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpq72xEy', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: Command ok: ['chroot', '/var/tmp/tmpq72xEy', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.4s DEBUG: Created policy-rc.d and chmodded it.
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmpq72xEy', 'eatmydata', 
'apt-get', 'update']
0m6.8s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 

Bug#715076: Broken library symlink detected in libdime-dev

[David Steele]

Package: libdime-dev
Version: 0.20030921-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libdime.so
- libdime.so.1.0.0


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:54:30 EST

Package: libdime-dev
Source: dime
Version: 0.20030921-2
Installed-Size: 288
Maintainer: A. Maitland Bottoms bott...@debian.org
Architecture: all
Description: DXF Import, Manipulation, and Export library - devel
Description-md5: 0cee8bf75f89bc011e901901c2606299
Tag: devel::lang:c++, devel::library, implemented-in::c++, role::devel-lib,
 works-with::3dmodel
Section: libdevel
Priority: optional
Filename: pool/main/d/dime/libdime-dev_0.20030921-2_all.deb
Size: 28840
MD5sum: 6579aeb2114360946110d66063872b5d
SHA1: 012c8aa0a42204114c01958ca5b07aed7507cb8a
SHA256: 8bc0ce2c0167486146cfaacff886e9e8b7fdd7bcebe0c891e1f0dad12fe6a4f1

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libdime-dev=0.20030921-2
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libdime-dev=0.20030921-2'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmp1YSgoW
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmp1YSgoW
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmp1YSgoW', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmp1YSgoW', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmp1YSgoW', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: Command ok: ['chroot', '/var/tmp/tmp1YSgoW', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.4s DEBUG: Created policy-rc.d and chmodded it.
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmp1YSgoW', 'eatmydata', 
'apt-get', 'update']
0m6.6s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (2889 kB/s)
  Reading package lists...
0m6.6s DEBUG: Command ok: ['chroot', '/var/tmp/tmp1YSgoW', 'eatmydata', 
'apt-get', 'update']
0m6.6s DEBUG: Starting command: ['chroot', '/var/tmp/tmp1YSgoW', 'eatmydata', 
'apt-get', '-yf', 

Bug#715068: Broken library symlink detected in gromacs-dev

[David Steele]

Package: gromacs-dev
Version: 4.5.5-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libgmx_mpi.mpich.so
- libgmx_mpi.mpich.so.6
  /usr/lib/libgmx_mpi_d.mpich.so
- libgmx_mpi_d.mpich.so.6
  /usr/lib/libgmxpreprocess_mpi.mpich.so
- libgmxpreprocess_mpi.mpich.so.6
  /usr/lib/libgmxpreprocess_mpi_d.mpich.so
- libgmxpreprocess_mpi_d.mpich.so.6
  /usr/lib/libmd_mpi.mpich.so
- libmd_mpi.mpich.so.6
  /usr/lib/libmd_mpi_d.mpich.so
- libmd_mpi_d.mpich.so.6
  /usr/lib/libgmx_mpi.openmpi.so
- libgmx_mpi.openmpi.so.6
  /usr/lib/libgmx_mpi_d.openmpi.so
- libgmx_mpi_d.openmpi.so.6
  /usr/lib/libgmxpreprocess_mpi.openmpi.so
- libgmxpreprocess_mpi.openmpi.so.6
  /usr/lib/libgmxpreprocess_mpi_d.openmpi.so
- libgmxpreprocess_mpi_d.openmpi.so.6
  /usr/lib/libmd_mpi.openmpi.so
- libmd_mpi.openmpi.so.6
  /usr/lib/libmd_mpi_d.openmpi.so
- libmd_mpi_d.openmpi.so.6


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:44:14 EST

Package: gromacs-dev
Source: gromacs
Version: 4.5.5-2
Installed-Size: 1380
Maintainer: Debichem Team debichem-de...@lists.alioth.debian.org
Architecture: amd64
Depends: gromacs (= 4.5.5-2), fftw3-dev
Recommends: gromacs-data
Suggests: gromacs-mpich (= 4.5.5-2) | gromacs-openmpi (= 4.5.5-2), 
libmpich2-dev, lesstif2-dev, libx11-dev, zlib1g-dev
Description: GROMACS molecular dynamics sim, development kit
Homepage: http://www.gromacs.org/
Description-md5: aab3304779c4ebcd0dbb20ae1eb40866
Tag: devel::lang:c, devel::library, field::biology, field::chemistry,
 implemented-in::c, role::devel-lib
Section: devel
Priority: extra
Filename: pool/main/g/gromacs/gromacs-dev_4.5.5-2_amd64.deb
Size: 291724
MD5sum: 52fa07d86a1b8a6a80c8ec284c819f5f
SHA1: 23e84010e9267229c421fae777d156eb2668c471
SHA256: 901a17e2ba8fa358f10befaf77f5ad6d0cb32cb4f2ce072aef10b3f046d390e7

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
gromacs-dev=4.5.5-2
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'gromacs-dev=4.5.5-2'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpTYza_H
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpTYza_H
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpTYza_H', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpTYza_H', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmpTYza_H', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: Command ok: ['chroot', '/var/tmp/tmpTYza_H', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']

Bug#715071: Broken library symlink detected in libboost-graph1.49-dev

[David Steele]

Package: libboost-graph1.49-dev
Version: 1.49.0-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libboost_graph-mt.so
- libboost_graph.so.1.49.0
  /usr/lib/libboost_graph.so
- libboost_graph.so.1.49.0


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:25:13 EST

Package: libboost-graph1.49-dev
Source: boost1.49
Version: 1.49.0-4
Installed-Size: 981
Maintainer: Debian Boost Team pkg-boost-de...@lists.alioth.debian.org
Architecture: amd64
Depends: libboost1.49-dev (= 1.49.0-4), libboost-serialization1.49-dev (= 
1.49.0-4), libboost-test1.49-dev (= 1.49.0-4)
Recommends: libboost-graph1.49.0 (= 1.49.0-4)
Conflicts: libboost-graph1.42-dev, libboost-graph1.46-dev, 
libboost-graph1.48-dev
Description: generic graph components and algorithms in C++
Homepage: http://www.boost.org/libs/graph/
Description-md5: 6dc872164cdff9808536697108f9eecd
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: optional
Filename: pool/main/b/boost1.49/libboost-graph1.49-dev_1.49.0-4_amd64.deb
Size: 191750
MD5sum: 9ad681c43171755e9b2d554085b12a7f
SHA1: ef3198c3d544df96c31a26d4d0c582bc5e17e246
SHA256: d89c93e5e10648a62aefc0bd24b9bb8819fb54ce795359b1049ace97b64a0f42

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libboost-graph1.49-dev=1.49.0-4
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libboost-graph1.49-dev=1.49.0-4'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpFZFhAs
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpFZFhAs
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpFZFhAs', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.5s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpFZFhAs', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.5s DEBUG: Starting command: ['chroot', '/var/tmp/tmpFZFhAs', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.6s DEBUG: Command ok: ['chroot', '/var/tmp/tmpFZFhAs', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.6s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.6s DEBUG: Created policy-rc.d and chmodded it.
0m1.6s DEBUG: Starting command: ['chroot', '/var/tmp/tmpFZFhAs', 'eatmydata', 
'apt-get', 'update']
0m6.6s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 

Bug#715069: Broken library symlink detected in heimdal-multidev

[David Steele]

Package: heimdal-multidev
Version: 1.6~git20120403+dfsg1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/x86_64-linux-gnu/heimdal/libotp.so
- ../libotp.so.0.1.5
  /usr/lib/x86_64-linux-gnu/heimdal/windc.so
- ../windc.so.0.0.0
  /usr/lib/x86_64-linux-gnu/heimdal/libsl.so
- ../libsl.so.0.2.1


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:22:09 EST

Package: heimdal-multidev
Source: heimdal
Version: 1.6~git20120403+dfsg1-3
Installed-Size: 5935
Maintainer: Brian May b...@debian.org
Architecture: amd64
Replaces: heimdal-clients ( 0.4e-7)
Depends: comerr-dev, libasn1-8-heimdal (= 1.6~git20120403+dfsg1-3), 
libgssapi3-heimdal (= 1.6~git20120403+dfsg1-3), libhcrypto4-heimdal (= 
1.6~git20120403+dfsg1-3), libhdb9-heimdal (= 1.6~git20120403+dfsg1-3), 
libheimbase1-heimdal (= 1.6~git20120403+dfsg1-3), libhx509-5-heimdal (= 
1.6~git20120403+dfsg1-3), libkadm5clnt7-heimdal (= 1.6~git20120403+dfsg1-3), 
libkadm5srv8-heimdal (= 1.6~git20120403+dfsg1-3), libkafs0-heimdal (= 
1.6~git20120403+dfsg1-3), libkdc2-heimdal (= 1.6~git20120403+dfsg1-3), 
libkrb5-26-heimdal (= 1.6~git20120403+dfsg1-3), libwind0-heimdal (= 
1.6~git20120403+dfsg1-3)
Suggests: heimdal-docs
Conflicts: heimdal-clients ( 0.4e-7), kerberos4kth-dev
Description: Heimdal Kerberos - Multi-implementation Development
Homepage: http://www.h5l.org/
Description-md5: 2c68ae41ae2a5a78791f623671e565b3
Tag: devel::lang:c, devel::library, implemented-in::c, protocol::kerberos,
 role::devel-lib
Section: devel
Priority: extra
Filename: pool/main/h/heimdal/heimdal-multidev_1.6~git20120403+dfsg1-3_amd64.deb
Size: 1511340
MD5sum: 94998ade460f037f3e56df2adff76ca2
SHA1: 5635f0f3bcd5592ed2d13d15277907b5b712ac3d
SHA256: b346920c70c7718f4906a2c3c3a5087b1cd051eb7785cd52e4f370f57d5991b3

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
heimdal-multidev=1.6~git20120403+dfsg1-3
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'heimdal-multidev=1.6~git20120403+dfsg1-3'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpIaS8Il
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpIaS8Il
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpIaS8Il', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpIaS8Il', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmpIaS8Il', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: Command ok: ['chroot', '/var/tmp/tmpIaS8Il', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: 

Bug#715067: Broken library symlink detected in gnash-dev

[David Steele]

Package: gnash-dev
Version: 0.8.11~git20120629-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/gnash/libgnashamf.so
- libgnashamf-0.8.11.so
  /usr/lib/gnash/libgnashnet.so
- libgnashnet-0.8.11.so


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:55:46 EST

Package: gnash-dev
Source: gnash
Version: 0.8.11~git20120629-1
Installed-Size: 1048
Maintainer: Debian Flash Team pkg-flash-de...@lists.alioth.debian.org
Architecture: amd64
Depends: gnash-common (= 0.8.11~git20120629-1)
Description: GNU Shockwave Flash (SWF) player - Development files
Homepage: http://www.gnu.org/software/gnash/
Description-md5: dbf2d8e5bd8cab1260d79b520eeb8918
Tag: devel::lang:c++, devel::library, implemented-in::c++, role::devel-lib,
 suite::gnu, works-with::audio, works-with::video
Section: libdevel
Priority: optional
Filename: pool/main/g/gnash/gnash-dev_0.8.11~git20120629-1_amd64.deb
Size: 261882
MD5sum: f5ac26b0e094405192a4572aadb7442b
SHA1: fcab0dd4faa7f2564fade04fd125e778abffc290
SHA256: 5b35e62af90d3fab5fd7d60388835700b853a6c7f52c074669711e9c5b5e30e9

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
gnash-dev=0.8.11~git20120629-1
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'gnash-dev=0.8.11~git20120629-1'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpLB7TMG
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpLB7TMG
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpLB7TMG', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpLB7TMG', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpLB7TMG', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: Command ok: ['chroot', '/var/tmp/tmpLB7TMG', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.3s DEBUG: Created policy-rc.d and chmodded it.
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpLB7TMG', 'eatmydata', 
'apt-get', 'update']
0m6.8s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 

Bug#715072: Broken library symlink detected in libboost-graph1.53-dev

[David Steele]

Package: libboost-graph1.53-dev
Version: 1.53.0-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libboost_graph.so
- libboost_graph.so.1.53.0


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:33:40 EST

Package: libboost-graph1.53-dev
Source: boost1.53
Version: 1.53.0-5
Installed-Size: 959
Maintainer: Debian Boost Team pkg-boost-de...@lists.alioth.debian.org
Architecture: amd64
Depends: libboost1.53-dev (= 1.53.0-5), libboost-serialization1.53-dev (= 
1.53.0-5), libboost-test1.53-dev (= 1.53.0-5)
Recommends: libboost-graph1.53.0 (= 1.53.0-5)
Conflicts: libboost-graph1.42-dev, libboost-graph1.46-dev, 
libboost-graph1.48-dev, libboost-graph1.49-dev, libboost-graph1.50-dev, 
libboost-graph1.52-dev
Description: generic graph components and algorithms in C++
Homepage: http://www.boost.org/libs/graph/
Description-md5: 6dc872164cdff9808536697108f9eecd
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: optional
Filename: pool/main/b/boost1.53/libboost-graph1.53-dev_1.53.0-5_amd64.deb
Size: 187452
MD5sum: d220cd1b58def73b4920937bcf3c1f28
SHA1: fb3f1269f3f5a01eb679eef1e548c51da7c58d8e
SHA256: 14fdeb1f63dd259a9a3928beb9064334c3f09f70a0ee77dd848636d68c0573cf

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libboost-graph1.53-dev=1.53.0-5
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libboost-graph1.53-dev=1.53.0-5'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpVQPuGB
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpVQPuGB
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpVQPuGB', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpVQPuGB', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmpVQPuGB', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.5s DEBUG: Command ok: ['chroot', '/var/tmp/tmpVQPuGB', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.5s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.5s DEBUG: Created policy-rc.d and chmodded it.
0m1.5s DEBUG: Starting command: ['chroot', '/var/tmp/tmpVQPuGB', 'eatmydata', 
'apt-get', 'update']
0m6.9s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  

Bug#715073: Broken library symlink detected in libboost-graph-parallel1.49-dev

[David Steele]

Package: libboost-graph-parallel1.49-dev
Version: 1.49.0-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libboost_graph_parallel.so
- libboost_graph_parallel.so.1.49.0
  /usr/lib/libboost_graph_parallel-mt.so
- libboost_graph_parallel.so.1.49.0


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:24:45 EST

Package: libboost-graph-parallel1.49-dev
Source: boost1.49
Version: 1.49.0-4
Installed-Size: 754
Maintainer: Debian Boost Team pkg-boost-de...@lists.alioth.debian.org
Architecture: amd64
Depends: libboost1.49-dev (= 1.49.0-4), libboost-serialization1.49-dev (= 
1.49.0-4), libboost-test1.49-dev (= 1.49.0-4)
Recommends: libboost-graph-parallel1.49.0 (= 1.49.0-4)
Conflicts: libboost-graph-parallel1.42-dev, libboost-graph-parallel1.46-dev, 
libboost-graph-parallel1.48-dev
Description: generic graph components and algorithms in C++
Homepage: http://www.boost.org/libs/graph_parallel/
Description-md5: 4f57c2a6e2a339b83d9c59b83812e4c6
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: optional
Filename: 
pool/main/b/boost1.49/libboost-graph-parallel1.49-dev_1.49.0-4_amd64.deb
Size: 142712
MD5sum: c30270d555a5bc7071194f98454bdc1e
SHA1: ba9609ed5e7e64dee7687abf2d1a01ceccbff692
SHA256: 7aca730fdf8338e91916c4aec922a64eab5588d8611cb2a4b2e1acb9be4592f8

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libboost-graph-parallel1.49-dev=1.49.0-4
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libboost-graph-parallel1.49-dev=1.49.0-4'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpwfFAKT
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpwfFAKT
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpwfFAKT', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpwfFAKT', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmpwfFAKT', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: Command ok: ['chroot', '/var/tmp/tmpwfFAKT', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.5s DEBUG: Created policy-rc.d and chmodded it.
0m1.5s DEBUG: Starting command: ['chroot', '/var/tmp/tmpwfFAKT', 'eatmydata', 
'apt-get', 'update']
0m6.9s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 

Bug#715078: Broken library symlink detected in libelk0-dev

[David Steele]

Package: libelk0-dev
Version: 3.99.8-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libelk.so
- libelk.so.0.0.0
  /usr/lib/libelk-xlib.so
- libelk-xlib.so.0.0.0
  /usr/lib/libelk-xt.so
- libelk-xt.so.0.0.0


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:55:06 EST

Package: libelk0-dev
Source: elk
Version: 3.99.8-2
Installed-Size: 1008
Maintainer: Sam Hocevar s...@debian.org
Architecture: amd64
Replaces: elk ( 3.99-1)
Depends: libelfg0-dev, libx11-dev, libxext-dev, libxmu-dev, libxt-dev, 
libice-dev, libsm-dev
Conflicts: elk ( 3.99-1)
Description: development files for libelk0
Description-md5: a4e9540c790fbcd5e6ef5ac76925c2af
Tag: devel::lang:scheme, devel::library, role::devel-lib
Section: libdevel
Priority: optional
Filename: pool/main/e/elk/libelk0-dev_3.99.8-2_amd64.deb
Size: 263816
MD5sum: 39d8f2fcf48907693b3232bc588a2d5c
SHA1: 4a04575699bca297249a4a437f837b44579a00ec
SHA256: 1da3a5e2a85471e9c0dd8b809b6470b6b6a5dd16b83215e8fe2328fa352d2634

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libelk0-dev=3.99.8-2
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libelk0-dev=3.99.8-2'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpWJMfID
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpWJMfID
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpWJMfID', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpWJMfID', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmpWJMfID', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: Command ok: ['chroot', '/var/tmp/tmpWJMfID', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.4s DEBUG: Created policy-rc.d and chmodded it.
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmpWJMfID', 'eatmydata', 
'apt-get', 'update']
0m6.6s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (2816 kB/s)
  Reading package lists...
0m6.6s DEBUG: Command ok: ['chroot', 

Bug#715079: Broken library symlink detected in libfence-dev

[David Steele]

Package: libfence-dev
Version: 3.1.8-1.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libfence.so
- libfence.so.3


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:57:25 EST

Package: libfence-dev
Source: redhat-cluster
Version: 3.1.8-1.1
Installed-Size: 78
Maintainer: Debian HA Maintainers 
debian-ha-maintain...@lists.alioth.debian.org
Architecture: amd64
Depends: libfence4 (= 3.1.8-1.1)
Description: Red Hat cluster suite - fence server development files
Description-md5: 6421f91d24808d375cadc1fb997a9ba9
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: optional
Filename: pool/main/r/redhat-cluster/libfence-dev_3.1.8-1.1_amd64.deb
Size: 26602
MD5sum: c327685b26074484fbe41001317ec22b
SHA1: f5f6012cc67a414c025852c8166023495220d578
SHA256: 6d474097c0a3a30ca7580d6b99b2b4733e442a4f1100d6a429f0e194b09ed762

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libfence-dev=3.1.8-1.1
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libfence-dev=3.1.8-1.1'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmp84G997
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmp84G997
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmp84G997', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmp84G997', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmp84G997', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: Command ok: ['chroot', '/var/tmp/tmp84G997', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.3s DEBUG: Created policy-rc.d and chmodded it.
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmp84G997', 'eatmydata', 
'apt-get', 'update']
0m6.5s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (2895 kB/s)
  Reading package lists...
0m6.5s DEBUG: Command ok: ['chroot', '/var/tmp/tmp84G997', 'eatmydata', 
'apt-get', 'update']
0m6.5s DEBUG: Starting command: ['chroot', '/var/tmp/tmp84G997', 'eatmydata', 
'apt-get', 

Bug#715086: Broken library symlink detected in libiodbc2-dev

[David Steele]

Package: libiodbc2-dev
Version: 3.52.7-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libdrvproxy.so
- libdrvproxy.so.2.1.19
  /usr/lib/libiodbcadm.so
- libiodbcadm.so.2.1.19


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:42:36 EST

Package: libiodbc2-dev
Source: libiodbc2
Version: 3.52.7-3
Installed-Size: 1944
Maintainer: Debian QA Group packa...@qa.debian.org
Architecture: amd64
Depends: libiodbc2 (= 3.52.7-3)
Conflicts: iodbc (= 3.52.6-1), libiodbc2 (= 3.52.6-1)
Description: iODBC Driver Manager (development files)
Homepage: http://www.iodbc.org/
Description-md5: d130ba790976d31df335175ab1a2c1f8
Tag: devel::library, role::devel-lib, works-with::db
Section: libdevel
Priority: optional
Filename: pool/main/libi/libiodbc2/libiodbc2-dev_3.52.7-3_amd64.deb
Size: 479144
MD5sum: 90189da1fd3459115c9699018f3d4982
SHA1: bd4540600db9fdf3d2c62fe7a14ffddc5dc5875a
SHA256: eca4d94b75edefea9d82fe1c715ff24e56366ce542e5e12f4e067dc8f970dbeb

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libiodbc2-dev=3.52.7-3
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libiodbc2-dev=3.52.7-3'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpjh89Fx
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpjh89Fx
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpjh89Fx', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.5s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpjh89Fx', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.5s DEBUG: Starting command: ['chroot', '/var/tmp/tmpjh89Fx', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.5s DEBUG: Command ok: ['chroot', '/var/tmp/tmpjh89Fx', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.5s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.5s DEBUG: Created policy-rc.d and chmodded it.
0m1.5s DEBUG: Starting command: ['chroot', '/var/tmp/tmpjh89Fx', 'eatmydata', 
'apt-get', 'update']
0m6.9s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 4s (2768 kB/s)
  Reading package lists...
0m6.9s DEBUG: Command ok: ['chroot', '/var/tmp/tmpjh89Fx', 

Bug#715077: Broken library symlink detected in libdmraid-dev

[David Steele]

Package: libdmraid-dev
Version: 1.0.0.rc16-4.2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libdmraid.so
- /lib/libdmraid.so.1.0.0.rc15


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 22:03:43 EST

Package: libdmraid-dev
Source: dmraid
Version: 1.0.0.rc16-4.2
Installed-Size: 501
Maintainer: Giuseppe Iuculano iucul...@debian.org
Architecture: amd64
Depends: libdmraid1.0.0.rc16 (= 1.0.0.rc16-4.2)
Description: Device-Mapper Software RAID support tool - header files
Homepage: http://people.redhat.com/~heinzm/sw/dmraid/
Description-md5: e5a3901320dc2ca7963a3c9dcf456f14
Tag: admin::hardware, devel::lang:c, devel::library, hardware::storage,
 implemented-in::c, role::devel-lib, use::driver
Section: libdevel
Priority: optional
Filename: pool/main/d/dmraid/libdmraid-dev_1.0.0.rc16-4.2_amd64.deb
Size: 154132
MD5sum: 2a824e34497d18ca1cee2656d4616d05
SHA1: 27478683d01ef3c1ad63da4ae9678f62e272a198
SHA256: e0c08269320324aafac84aaceeb58e4015f611f503764251b6bf8aa9fe79023d

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libdmraid-dev=1.0.0.rc16-4.2
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libdmraid-dev=1.0.0.rc16-4.2'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpUD9Bkq
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpUD9Bkq
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpUD9Bkq', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpUD9Bkq', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmpUD9Bkq', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: Command ok: ['chroot', '/var/tmp/tmpUD9Bkq', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.4s DEBUG: Created policy-rc.d and chmodded it.
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmpUD9Bkq', 'eatmydata', 
'apt-get', 'update']
0m6.0s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (3196 kB/s)
  Reading package lists...
0m6.0s DEBUG: Command ok: 

Bug#715085: Broken library symlink detected in libibdm-dev

[David Steele]

Package: libibdm-dev
Version: 1.2-OFED-1.4.2-1.3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libibdmcom.so
- libibdmcom.so.1.1.1
  /usr/lib/libibdm.so
- libibdm.so.1.1.1


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:46:27 EST

Package: libibdm-dev
Source: ibutils
Version: 1.2-OFED-1.4.2-1.3
Installed-Size: 2338
Maintainer: OFED and Debian Developement and Discussion 
pkg-ofed-de...@lists.alioth.debian.org
Architecture: amd64
Description: Development files for the libibdm library
Homepage: http://www.openfabrics.org
Description-md5: 0bcaf72869e0e5462c367affa959eca2
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: extra
Filename: pool/main/i/ibutils/libibdm-dev_1.2-OFED-1.4.2-1.3_amd64.deb
Size: 588422
MD5sum: b31ccd2d44976afcda10e68b12b88f13
SHA1: 49a1dced930dd3479de7ba83b1cd3acebb5ce018
SHA256: 61f189e33347ac770840f3cfb27c51e421b0688505b8bf52048d83f1c99883a9

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libibdm-dev=1.2-OFED-1.4.2-1.3
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libibdm-dev=1.2-OFED-1.4.2-1.3'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpcCng5r
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpcCng5r
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpcCng5r', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpcCng5r', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpcCng5r', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: Command ok: ['chroot', '/var/tmp/tmpcCng5r', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.3s DEBUG: Created policy-rc.d and chmodded it.
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpcCng5r', 'eatmydata', 
'apt-get', 'update']
0m6.6s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (2848 kB/s)
  Reading package lists...
0m6.6s DEBUG: Command ok: ['chroot', '/var/tmp/tmpcCng5r', 'eatmydata', 
'apt-get', 'update']
0m6.6s 

Bug#715082: Broken library symlink detected in libgeomview-dev

[David Steele]

Package: libgeomview-dev
Version: 1.9.4-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libgeomview.so
- libgeomview-1.9.4.so


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:58:37 EST

Package: libgeomview-dev
Source: geomview
Version: 1.9.4-4
Installed-Size: 2896
Maintainer: Debian Science Team 
debian-science-maintain...@lists.alioth.debian.org
Architecture: amd64
Description: geomview library development package
Homepage: http://www.geomview.org/
Description-md5: c427e7ebbc656c19e6432a4304c16c22
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: optional
Filename: pool/main/g/geomview/libgeomview-dev_1.9.4-4_amd64.deb
Size: 891016
MD5sum: 7cc2f8959db4abbf3c26e2beac7b52e5
SHA1: bb41de0422bd173e928caa9ae69515f184e2217f
SHA256: 4db47c041a718c6c38f30075e134d4ad05680302f1fd01fb2b7f9d8ea2a2cee0

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libgeomview-dev=1.9.4-4
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libgeomview-dev=1.9.4-4'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpXtaGzQ
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpXtaGzQ
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpXtaGzQ', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpXtaGzQ', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpXtaGzQ', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: Command ok: ['chroot', '/var/tmp/tmpXtaGzQ', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.4s DEBUG: Created policy-rc.d and chmodded it.
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmpXtaGzQ', 'eatmydata', 
'apt-get', 'update']
0m6.3s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (2887 kB/s)
  Reading package lists...
0m6.3s DEBUG: Command ok: ['chroot', '/var/tmp/tmpXtaGzQ', 'eatmydata', 
'apt-get', 'update']
0m6.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpXtaGzQ', 'eatmydata', 
'apt-get', '-yf', 

Bug#715083: Broken library symlink detected in libgrok-dev

[David Steele]

Package: libgrok-dev
Version: 1.20110708.1-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/x86_64-linux-gnu/libgrok.so
- libgrok.so.1


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 22:01:39 EST

Package: libgrok-dev
Source: grok
Version: 1.20110708.1-4
Installed-Size: 52
Maintainer: Stig Sandbeck Mathisen s...@debian.org
Architecture: amd64
Provides: libgrok-dev
Conflicts: libgrok-dev
Description: development files for grok
Homepage: http://code.google.com/p/semicomplete/wiki/Grok
Description-md5: b97d0850d5837eb0fc62d2f4748a756f
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: extra
Filename: pool/main/g/grok/libgrok-dev_1.20110708.1-4_amd64.deb
Size: 9252
MD5sum: 84cd23be0d8b791e294930e108bc7b28
SHA1: 8ca250bc9a0080972b41e177e554d16fbeb889c3
SHA256: 5a12eb65ea070955dbab2a94fcdf820010c397ab2b17c770f36987227e246aaf

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libgrok-dev=1.20110708.1-4
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libgrok-dev=1.20110708.1-4'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpTZhafQ
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpTZhafQ
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpTZhafQ', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpTZhafQ', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpTZhafQ', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: Command ok: ['chroot', '/var/tmp/tmpTZhafQ', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.3s DEBUG: Created policy-rc.d and chmodded it.
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpTZhafQ', 'eatmydata', 
'apt-get', 'update']
0m5.7s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (3309 kB/s)
  Reading package lists...
0m5.7s DEBUG: Command ok: ['chroot', '/var/tmp/tmpTZhafQ', 'eatmydata', 
'apt-get', 'update']
0m5.7s DEBUG: Starting command: ['chroot', '/var/tmp/tmpTZhafQ', 

Bug#715084: Broken library symlink detected in libhamlib++-dev

[David Steele]

Package: libhamlib++-dev
Version: 1.2.15.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libhamlib++.so
- libhamlib++.so.2.0.16


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:41:07 EST

Package: libhamlib++-dev
Source: hamlib
Version: 1.2.15.3-1
Installed-Size: 112
Maintainer: Debian Hamradio Maintainers debian-h...@lists.debian.org
Architecture: amd64
Provides: hamlib++-dev
Depends: libhamlib2 (= 1.2.15.3-1), libhamlib-dev (= 1.2.15.3-1), libc6-dev
Conflicts: hamlib++-dev
Description: Development library to control radio transceivers and receivers
Homepage: http://www.hamlib.org/
Description-md5: 6e05f44f729ecf59d7c9be3c217be78b
Tag: devel::lang:c++, devel::library, hardware::hamradio, role::devel-lib
Section: libdevel
Priority: optional
Filename: pool/main/h/hamlib/libhamlib++-dev_1.2.15.3-1_amd64.deb
Size: 23494
MD5sum: 2f66a0091c4bb3726a8dacbf30850478
SHA1: 324c20e90999e0178efc636621227c4989b5ecc0
SHA256: 7a9df72a92c1be5490cadf74a47d85226278a9da7e5f9b70210a562e116a0b5c

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libhamlib++-dev=1.2.15.3-1
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libhamlib++-dev=1.2.15.3-1'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmp4dM4a7
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmp4dM4a7
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmp4dM4a7', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmp4dM4a7', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmp4dM4a7', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: Command ok: ['chroot', '/var/tmp/tmp4dM4a7', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.3s DEBUG: Created policy-rc.d and chmodded it.
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmp4dM4a7', 'eatmydata', 
'apt-get', 'update']
0m6.5s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (2928 kB/s)
  Reading package lists...
0m6.5s DEBUG: 

Bug#715092: Broken library symlink detected in libmp3splt-dev

[David Steele]

Package: libmp3splt-dev
Version: 0.7.2-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libmp3splt/libsplt_ogg.so
- libsplt_ogg.so.0.0.0
  /usr/lib/libmp3splt/libsplt_mp3.so
- libsplt_mp3.so.0.0.0


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 22:09:07 EST

Package: libmp3splt-dev
Source: libmp3splt
Version: 0.7.2-2
Installed-Size: 485
Maintainer: Ryan Niebur r...@debian.org
Architecture: amd64
Replaces: libmp3splt, libmp3splt-mp3, libmp3splt-ogg
Depends: libmp3splt0 (= 0.7.2-2), libogg-dev, libvorbis-dev, libmad0-dev, 
libltdl3-dev, libid3tag0-dev
Conflicts: libmp3splt, libmp3splt-mp3, libmp3splt-ogg
Description: development files for libmp3splt0
Homepage: http://mp3splt.sourceforge.net/
Description-md5: 372360427e8b7badcc9cc88426d3fd90
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: optional
Filename: pool/main/libm/libmp3splt/libmp3splt-dev_0.7.2-2_amd64.deb
Size: 138946
MD5sum: 08eba4452a733fef1f4df970870e9d7c
SHA1: 17e33b5365276166d828ec92197ebb4e20c304ba
SHA256: a860bfe9676a94637bd53e70f4b626661a4db62af3a4b0093fa7a93ba148d1f9

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libmp3splt-dev=0.7.2-2
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libmp3splt-dev=0.7.2-2'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmp1WSMNB
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmp1WSMNB
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmp1WSMNB', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.2s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmp1WSMNB', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.2s DEBUG: Starting command: ['chroot', '/var/tmp/tmp1WSMNB', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: Command ok: ['chroot', '/var/tmp/tmp1WSMNB', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.3s DEBUG: Created policy-rc.d and chmodded it.
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmp1WSMNB', 'eatmydata', 
'apt-get', 'update']
0m5.7s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 

Bug#715087: Broken library symlink detected in libjack-dev

[David Steele]

Package: libjack-dev
Version: 1:0.121.3+20120418git75e3e20b-2.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/x86_64-linux-gnu/libjackserver.so
- libjackserver.so.0.0.28


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:19:47 EST

Package: libjack-dev
Source: jack-audio-connection-kit
Version: 1:0.121.3+20120418git75e3e20b-2.1
Installed-Size: 1803
Maintainer: Debian Multimedia Maintainers 
pkg-multimedia-maintain...@lists.alioth.debian.org
Architecture: amd64
Provides: libjack-dev-session, libjack0.100.0-dev
Depends: libjack0 (= 1:0.121.3+20120418git75e3e20b-2.1), pkg-config
Description: JACK Audio Connection Kit (development files)
Homepage: http://jackaudio.org/
Description-md5: 5769772c9db90298e719eeef115bed03
Tag: devel::lang:c, devel::library, implemented-in::c, role::devel-lib,
 works-with::audio
Section: libdevel
Priority: optional
Filename: 
pool/main/j/jack-audio-connection-kit/libjack-dev_0.121.3+20120418git75e3e20b-2.1_amd64.deb
Size: 364094
MD5sum: de023fec94fbf052def144e930c85879
SHA1: 6083cf722ff7b025863efd7accac8547c8c3c6cf
SHA256: 361a48d2795d334980c35abfd747eb29343477e8158c4c5c86f3930ddf462a61

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libjack-dev=1:0.121.3+20120418git75e3e20b-2.1
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 
'libjack-dev=1:0.121.3+20120418git75e3e20b-2.1'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpdQW0_X
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpdQW0_X
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpdQW0_X', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpdQW0_X', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpdQW0_X', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: Command ok: ['chroot', '/var/tmp/tmpdQW0_X', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.3s DEBUG: Created policy-rc.d and chmodded it.
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpdQW0_X', 'eatmydata', 
'apt-get', 'update']
0m6.4s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 

Bug#715097: Broken library symlink detected in libopenmpi1.6-dev

[David Steele]

Package: libopenmpi1.6-dev
Version: 1.6.4-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libmpi_f90.so
- libmpi_f90.so.3


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:59:25 EST

Package: libopenmpi1.6-dev
Source: openmpi1.6
Version: 1.6.4-2
Installed-Size: 3137
Maintainer: Debian Open MPI Maintainers 
pkg-openmpi-maintain...@lists.alioth.debian.org
Architecture: amd64
Depends: libc6 (= 2.3.4), libhwloc5, libltdl7 (= 2.4.2), libopenmpi1.6 (= 
1.6.4-2), openmpi1.6-common (= 1.6.4-2), libibverbs-dev, libhwloc-dev
Conflicts: libopenmpi-dev, openmpi-bin (= 1.2.4-0), openmpi-dev
Description: high performance message passing library -- header files
Homepage: http://www.open-mpi.org/
Description-md5: 8e5ff602ff3f7813a4a4cf41dfc27331
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: extra
Filename: pool/main/o/openmpi1.6/libopenmpi1.6-dev_1.6.4-2_amd64.deb
Size: 567384
MD5sum: 4a34a1c7ccaf2ad093232eab184c90bd
SHA1: 7cae88ce45a6da3d861bf3688713fe48990eca47
SHA256: f240cd9d28e7e22899e94d4b1f01434a0ab376cfe3073676f666d7a9200d2208

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libopenmpi1.6-dev=1.6.4-2
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libopenmpi1.6-dev=1.6.4-2'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpFLZ5ym
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpFLZ5ym
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpFLZ5ym', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpFLZ5ym', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpFLZ5ym', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: Command ok: ['chroot', '/var/tmp/tmpFLZ5ym', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.3s DEBUG: Created policy-rc.d and chmodded it.
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpFLZ5ym', 'eatmydata', 
'apt-get', 'update']
0m6.4s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB 

Bug#715094: Broken library symlink detected in libmudflap0-4.8-dev

[David Steele]

Package: libmudflap0-4.8-dev
Version: 4.8.1-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/gcc/x86_64-linux-gnu/4.8/x32/libmudflap.so
- ../../../../../libx32/libmudflap.so.0
  /usr/lib/gcc/x86_64-linux-gnu/4.8/x32/libmudflapth.so
- ../../../../../libx32/libmudflapth.so.0
  /usr/lib/gcc/x86_64-linux-gnu/4.8/32/libmudflap.so
- ../../../../../lib32/libmudflap.so.0
  /usr/lib/gcc/x86_64-linux-gnu/4.8/32/libmudflapth.so
- ../../../../../lib32/libmudflapth.so.0


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:43:41 EST

Package: libmudflap0-4.8-dev
Source: gcc-4.8
Version: 4.8.1-5
Installed-Size: 1160
Maintainer: Debian GCC Maintainers debian-...@lists.debian.org
Architecture: amd64
Depends: gcc-4.8-base (= 4.8.1-5), libmudflap0 (= 4.8.1-5), libc6-dev (= 
2.13-5)
Conflicts: libmudflap0-dev
Description: GCC mudflap support libraries (development files)
Homepage: http://gcc.gnu.org/
Description-md5: e62da3ba32a84c6821dd18f8a08e1b7f
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: optional
Filename: pool/main/g/gcc-4.8/libmudflap0-4.8-dev_4.8.1-5_amd64.deb
Size: 319104
MD5sum: 91d2529aacb6b4025dc163472ebfd572
SHA1: 3909029185b5fcb1fad1a7f50505c9e9381cb8b8
SHA256: e4015067dd20a887783417904a12a7262d106277e077924017451bddbcb15a85

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libmudflap0-4.8-dev=4.8.1-5
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libmudflap0-4.8-dev=4.8.1-5'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpPRshvW
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpPRshvW
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpPRshvW', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpPRshvW', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmpPRshvW', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.5s DEBUG: Command ok: ['chroot', '/var/tmp/tmpPRshvW', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.5s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.5s DEBUG: Created policy-rc.d and chmodded it.
0m1.5s DEBUG: Starting command: ['chroot', '/var/tmp/tmpPRshvW', 'eatmydata', 
'apt-get', 'update']
0m7.0s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 

Bug#715095: Broken library symlink detected in libncurses-gst

[David Steele]

Package: libncurses-gst
Version: 3.2.4-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/gnu-smalltalk/libncurses.so
- /lib/i386-linux-gnu/libncurses.so.5


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:40:10 EST

Package: libncurses-gst
Source: gnu-smalltalk
Version: 3.2.4-2
Installed-Size: 216
Maintainer: Debian GNU Smalltalk maintainers 
pkg-gnu-smalltalk-de...@lists.alioth.debian.org
Architecture: all
Depends: gnu-smalltalk (= 2.95h), libncurses5 (= 5.7+20100313)
Description: Ncurses bindings for GNU Smalltalk
Homepage: http://smalltalk.gnu.org
Description-md5: 4798ba848611cceaaf4e523011894a46
Tag: role::shared-lib, uitoolkit::ncurses
Section: interpreters
Priority: extra
Filename: pool/main/g/gnu-smalltalk/libncurses-gst_3.2.4-2_all.deb
Size: 91316
MD5sum: de63caea50abeacce18267d6321fe9f7
SHA1: fc32bd13db74dd9d230650dfe9abe9d84391ad49
SHA256: cfe4c8f19c4f54997020d0aa22d42e939304db7a15fa25051d44984f2cd8dc90

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libncurses-gst=3.2.4-2
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libncurses-gst=3.2.4-2'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpv9ZTjV
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpv9ZTjV
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpv9ZTjV', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpv9ZTjV', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmpv9ZTjV', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.5s DEBUG: Command ok: ['chroot', '/var/tmp/tmpv9ZTjV', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.5s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.5s DEBUG: Created policy-rc.d and chmodded it.
0m1.5s DEBUG: Starting command: ['chroot', '/var/tmp/tmpv9ZTjV', 'eatmydata', 
'apt-get', 'update']
0m6.8s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 4s (2730 kB/s)
  Reading package lists...
0m6.8s DEBUG: Command ok: ['chroot', '/var/tmp/tmpv9ZTjV', 'eatmydata', 
'apt-get', 

Bug#715090: Broken library symlink detected in liblz-dev

[David Steele]

Package: liblz-dev
Version: 1.3-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/x86_64-linux-gnu/liblz.so
- liblz.so.1.1


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:17:59 EST

Package: liblz-dev
Source: lzlib
Version: 1.3-4
Installed-Size: 83
Maintainer: Daniel Baumann m...@daniel-baumann.ch
Architecture: amd64
Depends: liblz1 (= 1.3-4)
Description: data compressor based on the LZMA algorithm (development)
Homepage: http://www.nongnu.org/lzip/lzlib.html
Description-md5: a084d46963a96b29cebe664999d6a5f6
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: optional
Filename: pool/main/l/lzlib/liblz-dev_1.3-4_amd64.deb
Size: 43666
MD5sum: 27608259a186e7d6e50b4c9662c012a4
SHA1: d0a6fd38e955dfa9fcb563b56ea0fb86057728ed
SHA256: 5b98d7377662b9c19ca003afe5c262c16a8753e06743534b007f93e060e4fbcf

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
liblz-dev=1.3-4
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'liblz-dev=1.3-4'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpao4Q_R
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpao4Q_R
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpao4Q_R', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpao4Q_R', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmpao4Q_R', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: Command ok: ['chroot', '/var/tmp/tmpao4Q_R', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.4s DEBUG: Created policy-rc.d and chmodded it.
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmpao4Q_R', 'eatmydata', 
'apt-get', 'update']
0m6.7s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 4s (2752 kB/s)
  Reading package lists...
0m6.7s DEBUG: Command ok: ['chroot', '/var/tmp/tmpao4Q_R', 'eatmydata', 
'apt-get', 'update']
0m6.7s DEBUG: Starting command: ['chroot', '/var/tmp/tmpao4Q_R', 'eatmydata', 
'apt-get', '-yf', 'dist-upgrade']
0m8.2s 

Bug#715091: Broken library symlink detected in libm17n-im-config-dev

[David Steele]

Package: libm17n-im-config-dev
Version: 0.9.0-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libm17n-im-config.so
- libm17n-im-config.so.0.0.0


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:58:38 EST

Package: libm17n-im-config-dev
Source: m17n-im-config
Version: 0.9.0-3
Installed-Size: 98
Maintainer: Daiki Ueno u...@unixuser.org
Architecture: amd64
Depends: libm17n-dev
Description: input method configuration library for m17n-lib - development
Homepage: http://www.m17n.org/
Description-md5: de55e2ad08c5a0b42fb7b7a5374675b5
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: optional
Filename: pool/main/m/m17n-im-config/libm17n-im-config-dev_0.9.0-3_amd64.deb
Size: 20800
MD5sum: ccd794d27d898da2e81801f37d76d93f
SHA1: 4d83c5dc61d0880ed3c2323a55b1a2fbb78faf17
SHA256: 26eb0cf9fad146c2c83409a1a23fb421b6abdef48d36dd026fd403c7f11b2141

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libm17n-im-config-dev=0.9.0-3
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libm17n-im-config-dev=0.9.0-3'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpHz5Svt
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpHz5Svt
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpHz5Svt', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpHz5Svt', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpHz5Svt', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: Command ok: ['chroot', '/var/tmp/tmpHz5Svt', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.3s DEBUG: Created policy-rc.d and chmodded it.
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmpHz5Svt', 'eatmydata', 
'apt-get', 'update']
0m6.4s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (2896 kB/s)
  Reading package lists...
0m6.4s DEBUG: Command ok: ['chroot', '/var/tmp/tmpHz5Svt', 'eatmydata', 
'apt-get', 'update']
0m6.4s DEBUG: Starting command: ['chroot', 

Bug#715088: Broken library symlink detected in libjack-jackd2-dev

[David Steele]

Package: libjack-jackd2-dev
Version: 1.9.9.5+20130622git7de15e7a-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/x86_64-linux-gnu/libjackserver.so
- libjackserver.so.0.1.0


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:48:19 EST

Package: libjack-jackd2-dev
Source: jackd2
Version: 1.9.9.5+20130622git7de15e7a-1
Installed-Size: 285
Maintainer: Debian Multimedia Maintainers 
pkg-multimedia-maintain...@lists.alioth.debian.org
Architecture: amd64
Replaces: libjack0.71.2-0 ( 0.75.0-1)
Provides: libjack-dev, libjack-dev-session, libjack0.100.0-dev
Depends: libjack-jackd2-0 (= 1.9.9.5+20130622git7de15e7a-1), pkg-config, 
libdbus-1-dev
Conflicts: libjack-dev, libjack0.100.0-dev ( 0.102.20-2)
Description: JACK Audio Connection Kit (development files)
Multi-Arch: same
Homepage: http://jackaudio.org/
Description-md5: 5769772c9db90298e719eeef115bed03
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: optional
Filename: 
pool/main/j/jackd2/libjack-jackd2-dev_1.9.9.5+20130622git7de15e7a-1_amd64.deb
Size: 95910
MD5sum: eaa44e40f8fea8f65e49ee63bc1794d8
SHA1: 9db552fb1617a9285e7ab9a278d03f759d19b043
SHA256: 8570947d60d1f0a183332ed2201173f81e666d5b8f1e0fddaa2ab7f6f86fe4d0

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libjack-jackd2-dev=1.9.9.5+20130622git7de15e7a-1
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 
'libjack-jackd2-dev=1.9.9.5+20130622git7de15e7a-1'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmp46yoDY
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmp46yoDY
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmp46yoDY', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmp46yoDY', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmp46yoDY', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: Command ok: ['chroot', '/var/tmp/tmp46yoDY', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.3s DEBUG: Created policy-rc.d and chmodded it.
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmp46yoDY', 'eatmydata', 
'apt-get', 'update']
0m6.3s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 

Bug#715096: Broken library symlink detected in libns3-dev

[David Steele]

Package: libns3-dev
Version: 3.17+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libns3.17-antenna-test.so
- libns3.17-antenna-test.so.0.0.0
  /usr/lib/libns3.17-antenna.so
- libns3.17-antenna.so.0.0.0
  /usr/lib/libns3.17-aodv-test.so
- libns3.17-aodv-test.so.0.0.0
  /usr/lib/libns3.17-aodv.so
- libns3.17-aodv.so.0.0.0
  /usr/lib/libns3.17-applications-test.so
- libns3.17-applications-test.so.0.0.0
  /usr/lib/libns3.17-applications.so
- libns3.17-applications.so.0.0.0
  /usr/lib/libns3.17-bridge.so
- libns3.17-bridge.so.0.0.0
  /usr/lib/libns3.17-buildings-test.so
- libns3.17-buildings-test.so.0.0.0
  /usr/lib/libns3.17-buildings.so
- libns3.17-buildings.so.0.0.0
  /usr/lib/libns3.17-config-store.so
- libns3.17-config-store.so.0.0.0
  /usr/lib/libns3.17-core-test.so
- libns3.17-core-test.so.0.0.0
  /usr/lib/libns3.17-core.so
- libns3.17-core.so.0.0.0
  /usr/lib/libns3.17-csma-layout.so
- libns3.17-csma-layout.so.0.0.0
  /usr/lib/libns3.17-csma.so
- libns3.17-csma.so.0.0.0
  /usr/lib/libns3.17-dsdv-test.so
- libns3.17-dsdv-test.so.0.0.0
  /usr/lib/libns3.17-dsdv.so
- libns3.17-dsdv.so.0.0.0
  /usr/lib/libns3.17-dsr-test.so
- libns3.17-dsr-test.so.0.0.0
  /usr/lib/libns3.17-dsr.so
- libns3.17-dsr.so.0.0.0
  /usr/lib/libns3.17-emu.so
- libns3.17-emu.so.0.0.0
  /usr/lib/libns3.17-energy-test.so
- libns3.17-energy-test.so.0.0.0
  /usr/lib/libns3.17-energy.so
- libns3.17-energy.so.0.0.0
  /usr/lib/libns3.17-fd-net-device.so
- libns3.17-fd-net-device.so.0.0.0
  /usr/lib/libns3.17-flow-monitor-test.so
- libns3.17-flow-monitor-test.so.0.0.0
  /usr/lib/libns3.17-flow-monitor.so
- libns3.17-flow-monitor.so.0.0.0
  /usr/lib/libns3.17-internet-test.so
- libns3.17-internet-test.so.0.0.0
  /usr/lib/libns3.17-internet.so
- libns3.17-internet.so.0.0.0
  /usr/lib/libns3.17-lte-test.so
- libns3.17-lte-test.so.0.0.0
  /usr/lib/libns3.17-lte.so
- libns3.17-lte.so.0.0.0
  /usr/lib/libns3.17-mesh-test.so
- libns3.17-mesh-test.so.0.0.0
  /usr/lib/libns3.17-mesh.so
- libns3.17-mesh.so.0.0.0
  /usr/lib/libns3.17-mobility-test.so
- libns3.17-mobility-test.so.0.0.0
  /usr/lib/libns3.17-mobility.so
- libns3.17-mobility.so.0.0.0
  /usr/lib/libns3.17-mpi.so
- libns3.17-mpi.so.0.0.0
  /usr/lib/libns3.17-netanim-test.so
- libns3.17-netanim-test.so.0.0.0
  /usr/lib/libns3.17-netanim.so
- libns3.17-netanim.so.0.0.0
  /usr/lib/libns3.17-network-test.so
- libns3.17-network-test.so.0.0.0
  /usr/lib/libns3.17-network.so
- libns3.17-network.so.0.0.0
  /usr/lib/libns3.17-nix-vector-routing.so
- libns3.17-nix-vector-routing.so.0.0.0
  /usr/lib/libns3.17-olsr-test.so
- libns3.17-olsr-test.so.0.0.0
  /usr/lib/libns3.17-olsr.so
- libns3.17-olsr.so.0.0.0
  /usr/lib/libns3.17-point-to-point-layout.so
- libns3.17-point-to-point-layout.so.0.0.0
  /usr/lib/libns3.17-point-to-point-test.so
- libns3.17-point-to-point-test.so.0.0.0
  /usr/lib/libns3.17-point-to-point.so
- libns3.17-point-to-point.so.0.0.0
  /usr/lib/libns3.17-propagation-test.so
- libns3.17-propagation-test.so.0.0.0
  /usr/lib/libns3.17-propagation.so
- libns3.17-propagation.so.0.0.0
  /usr/lib/libns3.17-spectrum-test.so
- libns3.17-spectrum-test.so.0.0.0
  /usr/lib/libns3.17-spectrum.so
- libns3.17-spectrum.so.0.0.0
  /usr/lib/libns3.17-stats-test.so
- libns3.17-stats-test.so.0.0.0
  /usr/lib/libns3.17-stats.so
- libns3.17-stats.so.0.0.0
  /usr/lib/libns3.17-tap-bridge.so
- libns3.17-tap-bridge.so.0.0.0
  /usr/lib/libns3.17-test-test.so
- libns3.17-test-test.so.0.0.0
  /usr/lib/libns3.17-test.so
- libns3.17-test.so.0.0.0
  /usr/lib/libns3.17-tools-test.so
- 

Bug#715093: Broken library symlink detected in libmpich-shmem1.0-dev

[David Steele]

Package: libmpich-shmem1.0-dev
Version: 1.2.7-10
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/mpich-shmem/lib/shared/libpmpich++-shmem.so
- libpmpich++-shmem.so.1.0


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:37:52 EST

Package: libmpich-shmem1.0-dev
Source: mpich
Version: 1.2.7-10
Installed-Size: 14416
Maintainer: Debian Science Team 
debian-science-maintain...@lists.alioth.debian.org
Architecture: amd64
Replaces: libmpich-p4shmem1.0 (= 1.2.4-8), mpich-common
Provides: libmpich-dev
Depends: libmpich-shmem1.0gf (= 1.2.7-10)
Suggests: mpi-doc
Conflicts: lam (= 6.1), mpich-common, mpich-shmem ( 1.2.5.3-2)
Description: mpich static libraries and development files
Homepage: http://www-unix.mcs.anl.gov/mpi/mpich1/
Description-md5: 0586a8c3f6c4cbd8e7a77eaf04422c5d
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: extra
Filename: pool/main/m/mpich/libmpich-shmem1.0-dev_1.2.7-10_amd64.deb
Size: 1498160
MD5sum: d6de31b82593683e8a3d2d10febe5f21
SHA1: 23fd6af2b9eba1d2418892f5f02c6e0b246854d6
SHA256: 0568fc0fd9568af5dd8f6387255b114fcb0eee8990913d0dc004bd31dae38b69

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libmpich-shmem1.0-dev=1.2.7-10
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libmpich-shmem1.0-dev=1.2.7-10'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmp0SB7Xo
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmp0SB7Xo
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmp0SB7Xo', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmp0SB7Xo', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmp0SB7Xo', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.5s DEBUG: Command ok: ['chroot', '/var/tmp/tmp0SB7Xo', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.5s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.5s DEBUG: Created policy-rc.d and chmodded it.
0m1.5s DEBUG: Starting command: ['chroot', '/var/tmp/tmp0SB7Xo', 'eatmydata', 
'apt-get', 'update']
0m7.1s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 

Bug#715089: Broken library symlink detected in libkwnn-dev

[David Steele]

Package: libkwnn-dev
Version: 1.1.1~a021+cvs20100325-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libkwnn.so
- libkwnn.so.0.0.0


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:52:59 EST

Package: libkwnn-dev
Source: freewnn
Version: 1.1.1~a021+cvs20100325-6
Installed-Size: 408
Maintainer: Keita Maehara maeh...@debian.org
Architecture: amd64
Replaces: freewnn-kserver-dev, kwnn-dev
Conflicts: freewnn-kserver-dev, kwnn-dev
Description: Header files and static library for kWnn (FreeWnn kserver)
Homepage: http://sourceforge.jp/projects/freewnn/
Description-md5: 29dd6ad96dffb2405a68de3fdca2fc75
Tag: accessibility::input, culture::korean, devel::library, role::devel-lib
Section: libdevel
Priority: optional
Filename: pool/main/f/freewnn/libkwnn-dev_1.1.1~a021+cvs20100325-6_amd64.deb
Size: 124410
MD5sum: a47de2e81ecc59c29d4d53c8ff653be4
SHA1: 96df0ef5e82a582cf32d5791b68322e3b204b64d
SHA256: 1af923b6fe504d17bd5b7d9eb5195d889d4e4f99d0dda87f4da5de2d55d6a354

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libkwnn-dev=1.1.1~a021+cvs20100325-6
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libkwnn-dev=1.1.1~a021+cvs20100325-6'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmp5mdXfC
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmp5mdXfC
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmp5mdXfC', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.5s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmp5mdXfC', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.5s DEBUG: Starting command: ['chroot', '/var/tmp/tmp5mdXfC', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.5s DEBUG: Command ok: ['chroot', '/var/tmp/tmp5mdXfC', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.5s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.5s DEBUG: Created policy-rc.d and chmodded it.
0m1.5s DEBUG: Starting command: ['chroot', '/var/tmp/tmp5mdXfC', 'eatmydata', 
'apt-get', 'update']
0m6.9s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (2780 kB/s)
  Reading package lists...
0m6.9s DEBUG: Command 

Bug#715107: Broken library symlink detected in libptscotch-dev

[David Steele]

Package: libptscotch-dev
Version: 5.1.12b.dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/scotch-int32/libptscotchparmetis.so
- libptscotchparmetis-5.1.so
  /usr/lib/scotch-int32/libptscotch.so
- libptscotch-5.1.so
  /usr/lib/scotch-int32/libptesmumps.so
- libptesmumps-5.1.so
  /usr/lib/scotch-int32/libptscotcherr.so
- libptscotcherr-5.1.so
  /usr/lib/scotch-int32/libptscotcherrexit.so
- libptscotcherrexit-5.1.so
  /usr/lib/scotch-int64/libptscotchparmetis.so
- libptscotchparmetis-5.1.so
  /usr/lib/scotch-int64/libptscotch.so
- libptscotch-5.1.so
  /usr/lib/scotch-int64/libptesmumps.so
- libptesmumps-5.1.so
  /usr/lib/scotch-int64/libptscotcherr.so
- libptscotcherr-5.1.so
  /usr/lib/scotch-int64/libptscotcherrexit.so
- libptscotcherrexit-5.1.so
  /usr/lib/scotch-long/libptscotchparmetis.so
- libptscotchparmetis-5.1.so
  /usr/lib/scotch-long/libptscotch.so
- libptscotch-5.1.so
  /usr/lib/scotch-long/libptesmumps.so
- libptesmumps-5.1.so
  /usr/lib/scotch-long/libptscotcherr.so
- libptscotcherr-5.1.so
  /usr/lib/scotch-long/libptscotcherrexit.so
- libptscotcherrexit-5.1.so


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:22:18 EST

Package: libptscotch-dev
Source: scotch
Version: 5.1.12b.dfsg-2
Installed-Size: 25001
Maintainer: Debian Science Maintainers 
debian-science-maintain...@lists.alioth.debian.org
Architecture: amd64
Depends: libptscotch-5.1 (= 5.1.12b.dfsg-2), libscotch-dev (= 5.1.12b.dfsg-2), 
mpi-default-dev, zlib1g-dev
Description: MPI programs and libraries for graph, mesh and hypergraph 
partitioning
Homepage: http://www.labri.fr/perso/pelegrin/scotch/
Description-md5: 0eafb053278f9be78b326b70f40b1fd4
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: extra
Filename: pool/main/s/scotch/libptscotch-dev_5.1.12b.dfsg-2_amd64.deb
Size: 6607682
MD5sum: 9174d368f4f5cfb40057aeb4253abd99
SHA1: 5075917300f70e1b8fab2bb1d0b6e5ffaca61443
SHA256: ab92fe817268c0a9e0816ee012e8b0ebf41297223a7ab6c37189b365b7a0858d

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libptscotch-dev=5.1.12b.dfsg-2
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libptscotch-dev=5.1.12b.dfsg-2'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmprqEfdN
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmprqEfdN
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmprqEfdN', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmprqEfdN', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s 

Bug#715100: Broken library symlink detected in libpcp-gui2-dev

[David Steele]

Package: libpcp-gui2-dev
Version: 3.8.0
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/share/man/man3/pmtime.3.gz
- pmTimeConnect.3.gz
  /usr/share/man/man3/pmafm.3.gz
- pmRecordAddHost.3.gz
  /usr/lib/libpcp_gui.so
- libpcp_gui.so.2


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:51:28 EST

Package: libpcp-gui2-dev
Source: pcp
Version: 3.8.0
Installed-Size: 85
Maintainer: PCP Development Team p...@oss.sgi.com
Architecture: amd64
Depends: libpcp3 (= 3.8.0)
Conflicts: libpcp-gui1-dev
Description: Performance Co-Pilot graphical client tools library and headers
Homepage: http://oss.sgi.com/projects/pcp
Description-md5: 532161d48a74ce75e2f12a2215f53ff9
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: extra
Filename: pool/main/p/pcp/libpcp-gui2-dev_3.8.0_amd64.deb
Size: 17036
MD5sum: ec077a020616571d6b4eea9585ec8c11
SHA1: 7c246063120c4f2a18c264c4c890fbaedcdcf5bb
SHA256: b738742075cb0e6b199c3808e607ca9aff11480bbef72c997141cc46dc728d35

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libpcp-gui2-dev=3.8.0
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libpcp-gui2-dev=3.8.0'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpt3E0f8
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpt3E0f8
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpt3E0f8', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.2s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpt3E0f8', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.2s DEBUG: Starting command: ['chroot', '/var/tmp/tmpt3E0f8', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: Command ok: ['chroot', '/var/tmp/tmpt3E0f8', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.3s DEBUG: Created policy-rc.d and chmodded it.
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpt3E0f8', 'eatmydata', 
'apt-get', 'update']
0m6.3s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (2938 kB/s)
  Reading package lists...
0m6.3s DEBUG: Command ok: ['chroot', 

Bug#715104: Broken library symlink detected in libpcp-trace2-dev

[David Steele]

Package: libpcp-trace2-dev
Version: 3.8.0
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libpcp_trace.so
- libpcp_trace.so.2


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:35:01 EST

Package: libpcp-trace2-dev
Source: pcp
Version: 3.8.0
Installed-Size: 115
Maintainer: PCP Development Team p...@oss.sgi.com
Architecture: amd64
Depends: libpcp3 (= 3.8.0)
Breaks: pcp ( 2.8.0)
Description: Performance Co-Pilot application tracing library and headers
Homepage: http://oss.sgi.com/projects/pcp
Description-md5: 56a0da729bb476482adb7efa62f09f84
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: extra
Filename: pool/main/p/pcp/libpcp-trace2-dev_3.8.0_amd64.deb
Size: 29356
MD5sum: 66549aca6bc9bdac7554c573c71c4d3f
SHA1: 321b59f87af17cfc919d6e8968108c44807c17b4
SHA256: e5292a7533ff2e85ee7283c5ce4cfb7f7cd9a1c8daf7423742f7ecf64a32d163

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libpcp-trace2-dev=3.8.0
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libpcp-trace2-dev=3.8.0'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpX4GihF
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpX4GihF
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpX4GihF', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.5s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpX4GihF', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.5s DEBUG: Starting command: ['chroot', '/var/tmp/tmpX4GihF', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.5s DEBUG: Command ok: ['chroot', '/var/tmp/tmpX4GihF', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.5s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.5s DEBUG: Created policy-rc.d and chmodded it.
0m1.5s DEBUG: Starting command: ['chroot', '/var/tmp/tmpX4GihF', 'eatmydata', 
'apt-get', 'update']
0m6.7s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (2826 kB/s)
  Reading package lists...
0m6.7s DEBUG: Command ok: ['chroot', '/var/tmp/tmpX4GihF', 'eatmydata', 
'apt-get', 'update']
0m6.7s DEBUG: Starting command: ['chroot', '/var/tmp/tmpX4GihF', 

Bug#715103: Broken library symlink detected in libpcp-pmda3-dev

[David Steele]

Package: libpcp-pmda3-dev
Version: 3.8.0
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libpcp_pmda.so
- libpcp_pmda.so.3


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:57:45 EST

Package: libpcp-pmda3-dev
Source: pcp
Version: 3.8.0
Installed-Size: 217
Maintainer: PCP Development Team p...@oss.sgi.com
Architecture: amd64
Depends: libpcp3 (= 3.8.0)
Breaks: pcp ( 2.8.0)
Description: Performance Co-Pilot Domain Agent library and headers
Homepage: http://oss.sgi.com/projects/pcp
Description-md5: 73b2bb904a6d0aa9d0ee405af2364cda
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: extra
Filename: pool/main/p/pcp/libpcp-pmda3-dev_3.8.0_amd64.deb
Size: 91990
MD5sum: 6f5a3ea5a5e819e215d78c7c3af695c5
SHA1: 90a00634463e873dc4605fb401603cb0dcb683d3
SHA256: 4992845d69b194eaff038637bdb0b063131e757b73600c4e3175299b65889ed7

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libpcp-pmda3-dev=3.8.0
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libpcp-pmda3-dev=3.8.0'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpKsgmn7
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpKsgmn7
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpKsgmn7', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpKsgmn7', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpKsgmn7', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: Command ok: ['chroot', '/var/tmp/tmpKsgmn7', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.3s DEBUG: Created policy-rc.d and chmodded it.
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpKsgmn7', 'eatmydata', 
'apt-get', 'update']
0m6.7s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (2815 kB/s)
  Reading package lists...
0m6.7s DEBUG: Command ok: ['chroot', '/var/tmp/tmpKsgmn7', 'eatmydata', 
'apt-get', 'update']
0m6.7s DEBUG: Starting command: ['chroot', '/var/tmp/tmpKsgmn7', 'eatmydata', 

Bug#715106: Broken library symlink detected in libpoco-dev

[David Steele]

Package: libpoco-dev
Version: 1.3.6p1-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libPocoUtild.so
- libPocoUtild.so.9
  /usr/lib/libPocoDatad.so
- libPocoDatad.so.9
  /usr/lib/libPocoMySQLd.so
- libPocoMySQLd.so.9
  /usr/lib/libPocoODBCd.so
- libPocoODBCd.so.9
  /usr/lib/libPocoFoundationd.so
- libPocoFoundationd.so.9
  /usr/lib/libPocoXMLd.so
- libPocoXMLd.so.9
  /usr/lib/libPocoNetSSLd.so
- libPocoNetSSLd.so.9
  /usr/lib/libPocoSQLited.so
- libPocoSQLited.so.9
  /usr/lib/libPocoZipd.so
- libPocoZipd.so.9
  /usr/lib/libPocoCryptod.so
- libPocoCryptod.so.9
  /usr/lib/libPocoNetd.so
- libPocoNetd.so.9


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:40:51 EST

Package: libpoco-dev
Source: poco
Version: 1.3.6p1-4
Installed-Size: 3317
Maintainer: Cristian Greco crist...@debian.org
Architecture: amd64
Replaces: libpoco5-dev
Provides: libpoco5-dev
Depends: libpococrypto9 (= 1.3.6p1-4), libpocodata9 (= 1.3.6p1-4), 
libpocofoundation9 (= 1.3.6p1-4), libpocomysql9 (= 1.3.6p1-4), libpoconet9 (= 
1.3.6p1-4), libpoconetssl9 (= 1.3.6p1-4), libpocoodbc9 (= 1.3.6p1-4), 
libpocosqlite9 (= 1.3.6p1-4), libpocoutil9 (= 1.3.6p1-4), libpocoxml9 (= 
1.3.6p1-4), libpocozip9 (= 1.3.6p1-4)
Suggests: libpoco-doc, libpococrypto9-dbg (= 1.3.6p1-4), libpocodata9-dbg (= 
1.3.6p1-4), libpocofoundation9-dbg (= 1.3.6p1-4), libpocomysql9-dbg (= 
1.3.6p1-4), libpoconet9-dbg (= 1.3.6p1-4), libpoconetssl9-dbg (= 1.3.6p1-4), 
libpocoodbc9-dbg (= 1.3.6p1-4), libpocosqlite9-dbg (= 1.3.6p1-4), 
libpocoutil9-dbg (= 1.3.6p1-4), libpocoxml9-dbg (= 1.3.6p1-4), libpocozip9-dbg 
(= 1.3.6p1-4)
Conflicts: libpoco5-dev
Description: C++ Portable Components (POCO) Development files
Homepage: http://poco.sourceforge.net/
Description-md5: 001356e1ebbed92df725fe478f69534f
Tag: devel::lang:c++, devel::library, implemented-in::c++, role::devel-lib
Section: libdevel
Priority: optional
Filename: pool/main/p/poco/libpoco-dev_1.3.6p1-4_amd64.deb
Size: 549030
MD5sum: ef65ae522015a3a36c933f56a2be9a26
SHA1: 4f5b5c26f28e4faf08ba3d595f97fbf9ac7c64df
SHA256: 179d2ed2be49a78a6b43a49154af5755ec7f8130e48a8862b2698c2d734ef8ca

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libpoco-dev=1.3.6p1-4
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libpoco-dev=1.3.6p1-4'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpj8EpXY
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpj8EpXY
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpj8EpXY', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: 

Bug#715102: Broken library symlink detected in libpcp-mmv1-dev

[David Steele]

Package: libpcp-mmv1-dev
Version: 3.8.0
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libpcp_mmv.so
- libpcp_mmv.so.1


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:51:52 EST

Package: libpcp-mmv1-dev
Source: pcp
Version: 3.8.0
Installed-Size: 77
Maintainer: PCP Development Team p...@oss.sgi.com
Architecture: amd64
Depends: libpcp3 (= 3.8.0)
Description: Performance Co-Pilot Memory Mapped Value library and headers
Homepage: http://oss.sgi.com/projects/pcp
Description-md5: 378b0f85ca464cbd51f1ffb46b8308dc
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: extra
Filename: pool/main/p/pcp/libpcp-mmv1-dev_3.8.0_amd64.deb
Size: 18088
MD5sum: a7be0eda011a34ec1131243c9d17d0b5
SHA1: 8d9ad2a7499fc36c14816ca463d21d742eca5892
SHA256: 7a83238c21afdb53f901a4c125148fd0505a3242e94fd9ecbe22ee1d7281ac5c

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libpcp-mmv1-dev=3.8.0
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libpcp-mmv1-dev=3.8.0'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpU0VfKO
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpU0VfKO
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpU0VfKO', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpU0VfKO', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmpU0VfKO', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: Command ok: ['chroot', '/var/tmp/tmpU0VfKO', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.4s DEBUG: Created policy-rc.d and chmodded it.
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmpU0VfKO', 'eatmydata', 
'apt-get', 'update']
0m7.0s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 4s (2720 kB/s)
  Reading package lists...
0m7.0s DEBUG: Command ok: ['chroot', '/var/tmp/tmpU0VfKO', 'eatmydata', 
'apt-get', 'update']
0m7.0s DEBUG: Starting command: ['chroot', '/var/tmp/tmpU0VfKO', 'eatmydata', 
'apt-get', '-yf', 

Bug#715105: Broken library symlink detected in libplplot-dev

[David Steele]

Package: libplplot-dev
Version: 5.9.9-5+b1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libplplotqtd.so
- libplplotqtd.so.0
  /usr/lib/libplplotwxwidgetsd.so
- libplplotwxwidgetsd.so.0


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:34:44 EST

Package: libplplot-dev
Source: plplot (5.9.9-5)
Version: 5.9.9-5+b1
Installed-Size: 3182
Maintainer: Andrew Ross andrewr...@users.sourceforge.net
Architecture: amd64
Depends: libplplot11 (= 5.9.9-5+b1), libqhull-dev, libfreetype6-dev, 
libltdl3-dev, libqsastime-dev, libplplot-c++10 (= 5.9.9-5+b1), 
libplplot-fortran9 (= 5.9.9-5+b1)
Recommends: pkg-config, cmake, libplplot-ocaml, libplplot-lua, libplplot-d
Suggests: plplot-doc
Breaks: libplplot-fortran9 ( 5.9.8-1)
Description: Scientific plotting library (development files)
Homepage: http://www.plplot.org
Description-md5: adea2f422876f569bb776360fe2045fb
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: optional
Filename: pool/main/p/plplot/libplplot-dev_5.9.9-5+b1_amd64.deb
Size: 915284
MD5sum: 4b85083378e48379b9d7ed14f06a4e44
SHA1: b6855b00f446041c78dd25e3995df52bcd44ccf6
SHA256: 33342f73f4f8a07e7b88648f8afa102ca42b5e76fb5a4938fc2df3658b4715b8

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libplplot-dev=5.9.9-5+b1
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libplplot-dev=5.9.9-5+b1'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmp3ViDWC
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmp3ViDWC
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmp3ViDWC', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.5s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmp3ViDWC', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.5s DEBUG: Starting command: ['chroot', '/var/tmp/tmp3ViDWC', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.5s DEBUG: Command ok: ['chroot', '/var/tmp/tmp3ViDWC', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.5s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.5s DEBUG: Created policy-rc.d and chmodded it.
0m1.5s DEBUG: Starting command: ['chroot', '/var/tmp/tmp3ViDWC', 'eatmydata', 
'apt-get', 'update']
0m6.7s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 

Bug#715101: Broken library symlink detected in libpcp-import1-dev

[David Steele]

Package: libpcp-import1-dev
Version: 3.8.0
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libpcp_import.so
- libpcp_import.so.1


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:40:26 EST

Package: libpcp-import1-dev
Source: pcp
Version: 3.8.0
Installed-Size: 72
Maintainer: PCP Development Team p...@oss.sgi.com
Architecture: amd64
Depends: libpcp3-dev
Description: Performance Co-Pilot data import library and headers
Homepage: http://oss.sgi.com/projects/pcp
Description-md5: 0a8b074356c9afa6d5ed44d808b4ace6
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: extra
Filename: pool/main/p/pcp/libpcp-import1-dev_3.8.0_amd64.deb
Size: 15980
MD5sum: a020f3535cbc95318d255dd6b32c8b9d
SHA1: c066388a89434593c3a25cdb28dfc1a7c8fcf4d6
SHA256: 3774b368b920ec818f1ea772ba5818fc9dcc7cc20364a2b6bc929fcc2d34cf47

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libpcp-import1-dev=3.8.0
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libpcp-import1-dev=3.8.0'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmp6Y_vvW
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmp6Y_vvW
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmp6Y_vvW', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmp6Y_vvW', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmp6Y_vvW', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: Command ok: ['chroot', '/var/tmp/tmp6Y_vvW', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.4s DEBUG: Created policy-rc.d and chmodded it.
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmp6Y_vvW', 'eatmydata', 
'apt-get', 'update']
0m6.6s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 4s (2766 kB/s)
  Reading package lists...
0m6.6s DEBUG: Command ok: ['chroot', '/var/tmp/tmp6Y_vvW', 'eatmydata', 
'apt-get', 'update']
0m6.6s DEBUG: Starting command: ['chroot', '/var/tmp/tmp6Y_vvW', 'eatmydata', 
'apt-get', '-yf', 

Bug#715099: Broken library symlink detected in libpacparser-dev

[David Steele]

Package: libpacparser-dev
Version: 1.3.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libpacparser.so
- libpacparser.so.1


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:40:37 EST

Package: libpacparser-dev
Source: pacparser
Version: 1.3.0-2
Installed-Size: 88
Maintainer: Manu Garg manug...@gmail.com
Architecture: amd64
Provides: libpacparser1-dev
Conflicts: libpacparser1-dev
Description: library to parse proxy auto-config files (development files)
Description-md5: fc4041d246a7a90ca4c53b8610275047
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: extra
Filename: pool/main/p/pacparser/libpacparser-dev_1.3.0-2_amd64.deb
Size: 14882
MD5sum: 6605fe475c0c7f6b1c55594392dfe66f
SHA1: 4815d11397672e2130c7015ea7525b44078adfa7
SHA256: cdb4264d0fb5d9fb986cf6dde35ec48521733a3e1da4e2110281ac05565906fd

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libpacparser-dev=1.3.0-2
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libpacparser-dev=1.3.0-2'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpMBlSh6
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpMBlSh6
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpMBlSh6', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpMBlSh6', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmpMBlSh6', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: Command ok: ['chroot', '/var/tmp/tmpMBlSh6', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.4s DEBUG: Created policy-rc.d and chmodded it.
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmpMBlSh6', 'eatmydata', 
'apt-get', 'update']
0m6.7s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (2825 kB/s)
  Reading package lists...
0m6.7s DEBUG: Command ok: ['chroot', '/var/tmp/tmpMBlSh6', 'eatmydata', 
'apt-get', 'update']
0m6.7s DEBUG: Starting command: ['chroot', '/var/tmp/tmpMBlSh6', 'eatmydata', 
'apt-get', '-yf', 

Bug#715098: Broken library symlink detected in libostyle-dev

[David Steele]

Package: libostyle-dev
Version: 1.4devel1-20.1+b1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libostyle.so
- libostyle.so.1.0.0
  /usr/lib/libospgrove.so
- libospgrove.so.1.0.0
  /usr/lib/libogrove.so
- libogrove.so.1.0.0


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:40:47 EST

Package: libostyle-dev
Source: openjade (1.4devel1-20.1)
Version: 1.4devel1-20.1+b1
Installed-Size: 6820
Maintainer: Neil Roeth n...@debian.org
Architecture: amd64
Conflicts: openjade ( 1.4devel1-14)
Description: OpenJade libraries, developer support
Homepage: http://openjade.sourceforge.net/
Description-md5: 916e65c0872facd3207bfd335df5203a
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: optional
Filename: pool/main/o/openjade/libostyle-dev_1.4devel1-20.1+b1_amd64.deb
Size: 1078116
MD5sum: 5f4becf8acacaff0d3cdda696dfe9529
SHA1: b9f17f659269937e5e5676c75a169c774aa9aaeb
SHA256: ffab627cda77b603e064f0ecf51f6e8ddfe1240079baab3f9541b806af9b1d83

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libostyle-dev=1.4devel1-20.1+b1
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libostyle-dev=1.4devel1-20.1+b1'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmphpRfJa
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmphpRfJa
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmphpRfJa', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmphpRfJa', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmphpRfJa', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: Command ok: ['chroot', '/var/tmp/tmphpRfJa', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.4s DEBUG: Created policy-rc.d and chmodded it.
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmphpRfJa', 'eatmydata', 
'apt-get', 'update']
0m6.9s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (2831 kB/s)
  Reading package lists...
0m6.9s DEBUG: Command ok: ['chroot', 

Bug#715108: Broken library symlink detected in libpythonqt2-dev

[David Steele]

Package: libpythonqt2-dev
Version: 2.0.1-1.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libPythonQt.so
- libPythonQt.so.2.0


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:56:41 EST

Package: libpythonqt2-dev
Source: pythonqt
Version: 2.0.1-1.1
Installed-Size: 162
Maintainer: Debian Med Packaging Team 
debian-med-packag...@lists.alioth.debian.org
Architecture: amd64
Description: Dynamic Python binding for the Qt framework - development
Homepage: http://pythonqt.sourceforge.net
Description-md5: bd150ad3a8faf1c1e1973a8ec167f478
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: optional
Filename: pool/main/p/pythonqt/libpythonqt2-dev_2.0.1-1.1_amd64.deb
Size: 33464
MD5sum: 9949fea8a14d46315e2e8bb7889af06b
SHA1: f9a528b1c5241c30c9b0471e260eb13e40263234
SHA256: e92e50d53de43e12e8859dadc053d37e18d0ca7bb48c0aec95b9cc6a191b565d

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libpythonqt2-dev=2.0.1-1.1
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libpythonqt2-dev=2.0.1-1.1'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmp49VJ3m
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmp49VJ3m
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmp49VJ3m', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmp49VJ3m', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmp49VJ3m', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: Command ok: ['chroot', '/var/tmp/tmp49VJ3m', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.3s DEBUG: Created policy-rc.d and chmodded it.
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmp49VJ3m', 'eatmydata', 
'apt-get', 'update']
0m6.5s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (2957 kB/s)
  Reading package lists...
0m6.5s DEBUG: Command ok: ['chroot', '/var/tmp/tmp49VJ3m', 'eatmydata', 
'apt-get', 'update']
0m6.5s DEBUG: Starting command: ['chroot', 

Bug#715112: Broken library symlink detected in libscotchmetis-dev

[David Steele]

Package: libscotchmetis-dev
Version: 5.1.12b.dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/metis-int64/libmetis.a
- libscotchmetis.a
  /usr/lib/metis-int64/libmetis.so
- libscotchmetis.so
  /usr/lib/metis-int32/libmetis.a
- libscotchmetis.a
  /usr/lib/metis-int32/libmetis.so
- libscotchmetis.so
  /usr/lib/metis-long/libmetis.a
- libscotchmetis.a
  /usr/lib/metis-long/libmetis.so
- libscotchmetis.so


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:53:45 EST

Package: libscotchmetis-dev
Source: scotch
Version: 5.1.12b.dfsg-2
Installed-Size: 123
Maintainer: Debian Science Maintainers 
debian-science-maintain...@lists.alioth.debian.org
Architecture: amd64
Replaces: libmetis-dev
Depends: libscotch-dev (= 5.1.12b.dfsg-2)
Conflicts: libmetis-dev, libparmetis-dev
Description: programs and libraries for graph, mesh and hypergraph partitioning
Homepage: http://www.labri.fr/perso/pelegrin/scotch/
Description-md5: a391c720b80b18263009a2efcd3d5429
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: extra
Filename: pool/main/s/scotch/libscotchmetis-dev_5.1.12b.dfsg-2_amd64.deb
Size: 30840
MD5sum: 8c5b4b42cc6fdf68950a7a4b4a0ee0c4
SHA1: fe78872ce19e8b274db1bda147cf02d4c499d71d
SHA256: ae5e7ff3a12dc983023de8a79f6d1ec5e07de9adcc54a526aa494dec8a7ee8ed

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libscotchmetis-dev=5.1.12b.dfsg-2
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libscotchmetis-dev=5.1.12b.dfsg-2'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpvsnc8h
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpvsnc8h
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpvsnc8h', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpvsnc8h', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmpvsnc8h', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: Command ok: ['chroot', '/var/tmp/tmpvsnc8h', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.4s DEBUG: Created policy-rc.d and chmodded it.
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmpvsnc8h', 'eatmydata', 
'apt-get', 'update']
0m7.0s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 

Bug#715114: Broken library symlink detected in libsdl-mixer-gst

[David Steele]

Package: libsdl-mixer-gst
Version: 3.2.4-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/gnu-smalltalk/libSDL_mixer-1.2.so
- ../libSDL_mixer-1.2.so.0


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 22:00:05 EST

Package: libsdl-mixer-gst
Source: gnu-smalltalk
Version: 3.2.4-2
Installed-Size: 132
Maintainer: Debian GNU Smalltalk maintainers 
pkg-gnu-smalltalk-de...@lists.alioth.debian.org
Architecture: all
Depends: gnu-smalltalk (= 3.2.4), libsdl-mixer1.2
Description: SDL_mixer bindings for GNU Smalltalk
Homepage: http://smalltalk.gnu.org
Description-md5: cb1fbb45f2bd545f088afe55a65bb202
Section: interpreters
Priority: extra
Filename: pool/main/g/gnu-smalltalk/libsdl-mixer-gst_3.2.4-2_all.deb
Size: 79098
MD5sum: ad0ab79d01288bbb4596b3dd3f6bd11e
SHA1: 354936d47e7b9feccece171764a5cb21ad6e4604
SHA256: 2f4534f592becad46c1a24be82c9ea6d957a55053c25f1ab634d34e8b9725050

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libsdl-mixer-gst=3.2.4-2
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libsdl-mixer-gst=3.2.4-2'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpTLVaEe
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpTLVaEe
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpTLVaEe', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.5s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpTLVaEe', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.5s DEBUG: Starting command: ['chroot', '/var/tmp/tmpTLVaEe', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.5s DEBUG: Command ok: ['chroot', '/var/tmp/tmpTLVaEe', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.5s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.5s DEBUG: Created policy-rc.d and chmodded it.
0m1.5s DEBUG: Starting command: ['chroot', '/var/tmp/tmpTLVaEe', 'eatmydata', 
'apt-get', 'update']
0m6.9s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 4s (2750 kB/s)
  Reading package lists...
0m6.9s DEBUG: Command ok: ['chroot', '/var/tmp/tmpTLVaEe', 'eatmydata', 
'apt-get', 'update']
0m6.9s DEBUG: Starting command: ['chroot', 

Bug#715116: Broken library symlink detected in libsdl-ttf-gst

[David Steele]

Package: libsdl-ttf-gst
Version: 3.2.4-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/gnu-smalltalk/libSDL_ttf-2.0.so
- ../libSDL_ttf-2.0.so.0


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 22:00:16 EST

Package: libsdl-ttf-gst
Source: gnu-smalltalk
Version: 3.2.4-2
Installed-Size: 124
Maintainer: Debian GNU Smalltalk maintainers 
pkg-gnu-smalltalk-de...@lists.alioth.debian.org
Architecture: all
Depends: gnu-smalltalk (= 3.2.4), libsdl-ttf2.0-0
Description: SDL_ttf bindings for GNU Smalltalk
Homepage: http://smalltalk.gnu.org
Description-md5: 0fd891545455ad6980e7c80975a73d88
Section: interpreters
Priority: extra
Filename: pool/main/g/gnu-smalltalk/libsdl-ttf-gst_3.2.4-2_all.deb
Size: 77218
MD5sum: 1a43badd2e3cc4b833d8a7cb1e1c2c13
SHA1: d1e9f369a690b86436a25c21141ef5981723f491
SHA256: 4a449f2aec809b9507b2ccbceb1be3bb67f9c066913d156bc531c3633fa93ff1

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libsdl-ttf-gst=3.2.4-2
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libsdl-ttf-gst=3.2.4-2'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpOO_X7m
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpOO_X7m
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpOO_X7m', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpOO_X7m', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpOO_X7m', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: Command ok: ['chroot', '/var/tmp/tmpOO_X7m', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.4s DEBUG: Created policy-rc.d and chmodded it.
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmpOO_X7m', 'eatmydata', 
'apt-get', 'update']
0m6.5s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (2867 kB/s)
  Reading package lists...
0m6.5s DEBUG: Command ok: ['chroot', '/var/tmp/tmpOO_X7m', 'eatmydata', 
'apt-get', 'update']
0m6.5s DEBUG: Starting command: ['chroot', 

Bug#715117: Broken library symlink detected in libsocksd0-dev

[David Steele]

Package: libsocksd0-dev
Version: 1.1.19.dfsg-3+b4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libsocksd.so
- libsocksd0.so.0


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:49:43 EST

Package: libsocksd0-dev
Source: dante (1.1.19.dfsg-3)
Version: 1.1.19.dfsg-3+b4
Installed-Size: 441
Maintainer: Peter Pentchev r...@ringlet.net
Architecture: amd64
Depends: libsocksd0 (= 1.1.19.dfsg-3+b4)
Description: Development files for compiling programs with SOCKS support
Homepage: http://www.inet.no/dante/
Description-md5: e3665f1fe22527f31227f98afb542c9a
Tag: devel::lang:c, devel::library, implemented-in::c, network::client,
 role::devel-lib, use::proxying, works-with::network-traffic
Section: libdevel
Priority: optional
Filename: pool/main/d/dante/libsocksd0-dev_1.1.19.dfsg-3+b4_amd64.deb
Size: 124632
MD5sum: 93246f234ccda65872c9430437838c55
SHA1: d50fea4d22b457894afe837c73a15b355371b5f9
SHA256: e41e4f08fe49199c071cbdd2b300cd5c11f00ab114c325119e4a189c0df1abd0

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libsocksd0-dev=1.1.19.dfsg-3+b4
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libsocksd0-dev=1.1.19.dfsg-3+b4'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpbpjHGF
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpbpjHGF
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpbpjHGF', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpbpjHGF', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpbpjHGF', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: Command ok: ['chroot', '/var/tmp/tmpbpjHGF', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.3s DEBUG: Created policy-rc.d and chmodded it.
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpbpjHGF', 'eatmydata', 
'apt-get', 'update']
0m6.6s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (2867 kB/s)
  Reading package lists...
0m6.6s DEBUG: Command ok: 

Bug#715113: Broken library symlink detected in libsdl-image-gst

[David Steele]

Package: libsdl-image-gst
Version: 3.2.4-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/gnu-smalltalk/libSDL_image-1.2.so
- ../libSDL_image-1.2.so.0


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:49:49 EST

Package: libsdl-image-gst
Source: gnu-smalltalk
Version: 3.2.4-2
Installed-Size: 122
Maintainer: Debian GNU Smalltalk maintainers 
pkg-gnu-smalltalk-de...@lists.alioth.debian.org
Architecture: all
Depends: gnu-smalltalk (= 3.2.4), libsdl-image1.2 (= 1.2.10)
Description: SDL_image bindings for GNU Smalltalk
Homepage: http://smalltalk.gnu.org
Description-md5: ff1d9e8b4f839fe51c0518cef0a47eff
Section: interpreters
Priority: extra
Filename: pool/main/g/gnu-smalltalk/libsdl-image-gst_3.2.4-2_all.deb
Size: 76722
MD5sum: 7957c80af5b8aa1386f821c179acb58e
SHA1: 6663f91ffa6f3d70ed7c307fcadbf06a458f3b80
SHA256: 6c6270bfac83279e7309824552f347968a588fd023b0aaef0503481e299d7190

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libsdl-image-gst=3.2.4-2
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libsdl-image-gst=3.2.4-2'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpNjjYC2
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpNjjYC2
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpNjjYC2', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.5s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpNjjYC2', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.5s DEBUG: Starting command: ['chroot', '/var/tmp/tmpNjjYC2', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.5s DEBUG: Command ok: ['chroot', '/var/tmp/tmpNjjYC2', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.5s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.5s DEBUG: Created policy-rc.d and chmodded it.
0m1.5s DEBUG: Starting command: ['chroot', '/var/tmp/tmpNjjYC2', 'eatmydata', 
'apt-get', 'update']
0m6.9s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (2847 kB/s)
  Reading package lists...
0m6.9s DEBUG: Command ok: ['chroot', '/var/tmp/tmpNjjYC2', 'eatmydata', 
'apt-get', 'update']
0m6.9s DEBUG: Starting command: 

Bug#715111: Broken library symlink detected in libsbml5-cil

[David Steele]

Package: libsbml5-cil
Version: 5.6.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/mono/libsbmlcsP/libsbml.so
- ../../libsbml.so


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:59:45 EST

Package: libsbml5-cil
Source: libsbml
Version: 5.6.0-1
Installed-Size: 5436
Maintainer: Debian Med Packaging Team 
debian-med-packag...@lists.alioth.debian.org
Architecture: amd64
Provides: libsbml-cil
Depends: libbz2-1.0, libc6 (= 2.4), libgcc1 (= 1:4.1.1), libsbml5, libstdc++6 
(= 4.6), libxml2 (= 2.7.4), zlib1g (= 1:1.1.4)
Description: System Biology Markup Language library - CLR binding
Homepage: http://www.sbml.org/
Description-md5: 526645fd5ac0eed729bf48bc3ad25c45
Section: cli-mono
Priority: optional
Filename: pool/main/libs/libsbml/libsbml5-cil_5.6.0-1_amd64.deb
Size: 1614602
MD5sum: 7b086c53b9896beb09ad6457efca64a7
SHA1: e1002cbed66f49ac05506518315e503f69914da0
SHA256: b43dda51337962d8c1824c0504ad7557c5b0c3fd77db79c05759d1ac2ef57fa8

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libsbml5-cil=5.6.0-1
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libsbml5-cil=5.6.0-1'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpcVRSl_
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpcVRSl_
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpcVRSl_', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpcVRSl_', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmpcVRSl_', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: Command ok: ['chroot', '/var/tmp/tmpcVRSl_', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.4s DEBUG: Created policy-rc.d and chmodded it.
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmpcVRSl_', 'eatmydata', 
'apt-get', 'update']
0m6.5s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (2959 kB/s)
  Reading package lists...
0m6.5s DEBUG: Command ok: ['chroot', '/var/tmp/tmpcVRSl_', 'eatmydata', 

Bug#715110: Broken library symlink detected in libsamba-util-dev

[David Steele]

Package: libsamba-util-dev
Version: 4.0.0~beta2+dfsg1-3.2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/x86_64-linux-gnu/libsamba-util.so
- libsamba-util.so.0.0.1
  /usr/lib/x86_64-linux-gnu/libtevent-util.so
- libtevent-util.so.0.0.1


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:36:51 EST

Package: libsamba-util-dev
Source: samba4
Version: 4.0.0~beta2+dfsg1-3.2
Installed-Size: 138
Maintainer: Samba Debian Maintainers pkg-samba-ma...@lists.alioth.debian.org
Architecture: amd64
Replaces: samba4-dev ( 4.0.0~alpha18)
Depends: pkg-config
Description: Samba utility function library - development files
Homepage: http://www.samba.org/
Description-md5: eb09eec6ee1200dddc5de024cb78ecb6
Tag: devel::lang:c, devel::library, implemented-in::c, role::devel-lib,
 suite::samba
Section: libdevel
Priority: optional
Filename: pool/main/s/samba4/libsamba-util-dev_4.0.0~beta2+dfsg1-3.2_amd64.deb
Size: 35254
MD5sum: df4cdeb7d517dee72f213ab15b6fcdad
SHA1: 23262dfae993ef1f48e786b3454f147d54969486
SHA256: a16db6ce5ae601c644d1f802937d2caff9803d633de3e93aaa917139821a5dee

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libsamba-util-dev=4.0.0~beta2+dfsg1-3.2
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libsamba-util-dev=4.0.0~beta2+dfsg1-3.2'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmp9WwVJ0
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmp9WwVJ0
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmp9WwVJ0', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.5s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmp9WwVJ0', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.5s DEBUG: Starting command: ['chroot', '/var/tmp/tmp9WwVJ0', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.5s DEBUG: Command ok: ['chroot', '/var/tmp/tmp9WwVJ0', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.5s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.5s DEBUG: Created policy-rc.d and chmodded it.
0m1.5s DEBUG: Starting command: ['chroot', '/var/tmp/tmp9WwVJ0', 'eatmydata', 
'apt-get', 'update']
0m6.7s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free 

Bug#715109: Broken library symlink detected in libsaga-dev

[David Steele]

Package: libsaga-dev
Version: 2.0.8+dfsg-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libsaga_api.so
- libsaga_api-2.0.8.so
  /usr/lib/libsaga_gdi.so
- libsaga_gdi-2.0.8.so


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 22:06:54 EST

Package: libsaga-dev
Source: saga
Version: 2.0.8+dfsg-3
Installed-Size: 487
Maintainer: Debian GIS Project pkg-grass-de...@lists.alioth.debian.org
Architecture: amd64
Replaces: libsaga ( 2.0.4+dfsg-3~)
Suggests: saga (= 2.0.8+dfsg-3)
Breaks: libsaga ( 2.0.4+dfsg-3~)
Description: SAGA GIS development files
Homepage: http://www.saga-gis.org/
Description-md5: 69520bc61abdf28171f5f6cba9362535
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: optional
Filename: pool/main/s/saga/libsaga-dev_2.0.8+dfsg-3_amd64.deb
Size: 137464
MD5sum: ca7c29fa330cdaab69b6c89d97fd8bf6
SHA1: e47bed6123b1d177323222a94b0b0577ed8b6500
SHA256: 85a671a99109a980a1b430fbe4c5d729fad9ad1279a754d5ab800079472a80eb

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libsaga-dev=2.0.8+dfsg-3
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libsaga-dev=2.0.8+dfsg-3'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpmEDJyG
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpmEDJyG
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpmEDJyG', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.2s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpmEDJyG', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.2s DEBUG: Starting command: ['chroot', '/var/tmp/tmpmEDJyG', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.2s DEBUG: Command ok: ['chroot', '/var/tmp/tmpmEDJyG', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.2s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.2s DEBUG: Created policy-rc.d and chmodded it.
0m1.2s DEBUG: Starting command: ['chroot', '/var/tmp/tmpmEDJyG', 'eatmydata', 
'apt-get', 'update']
0m5.6s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (3348 kB/s)
  Reading package lists...
0m5.6s DEBUG: Command ok: ['chroot', '/var/tmp/tmpmEDJyG', 

Bug#715118: Broken library symlink detected in libsoupcutter-dev

[David Steele]

Package: libsoupcutter-dev
Version: 1.1.7-1.2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libsoupcutter.so
- libsoupcutter.so.0.1.0


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:17:17 EST

Package: libsoupcutter-dev
Source: cutter-testing-framework
Version: 1.1.7-1.2
Installed-Size: 134
Maintainer: NIIBE Yutaka gni...@fsij.org
Architecture: amd64
Depends: libsoup2.4-dev, cutter-glib-support (= 1.1.7-1.2), 
cutter-testing-framework-bin (= 1.1.7-1.2)
Description: Cutter libsoup support (Development files)
Homepage: http://cutter.sourceforge.net/
Description-md5: c1d34233355f036908aa9d8cd8bbd009
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: extra
Filename: 
pool/main/c/cutter-testing-framework/libsoupcutter-dev_1.1.7-1.2_amd64.deb
Size: 68948
MD5sum: b3a785dd26fd6dd5ef1d2fd5a99baa8c
SHA1: db61f4a44e57f8a133b4fa971a3ef3257d255b23
SHA256: 7839ebe323a97cfe7d147f0d0d905c2f4fc5465426a6a5af61e77906eb02aaf7

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libsoupcutter-dev=1.1.7-1.2
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libsoupcutter-dev=1.1.7-1.2'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmps65b9g
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmps65b9g
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmps65b9g', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmps65b9g', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmps65b9g', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: Command ok: ['chroot', '/var/tmp/tmps65b9g', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.4s DEBUG: Created policy-rc.d and chmodded it.
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmps65b9g', 'eatmydata', 
'apt-get', 'update']
0m6.7s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (2839 kB/s)
  Reading package lists...
0m6.7s DEBUG: Command ok: ['chroot', '/var/tmp/tmps65b9g', 

Bug#715115: Broken library symlink detected in libsdl-sound-gst

[David Steele]

Package: libsdl-sound-gst
Version: 3.2.4-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/gnu-smalltalk/libSDL_sound-1.0.so
- ../libSDL_sound-1.0.so.1


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:59:56 EST

Package: libsdl-sound-gst
Source: gnu-smalltalk
Version: 3.2.4-2
Installed-Size: 133
Maintainer: Debian GNU Smalltalk maintainers 
pkg-gnu-smalltalk-de...@lists.alioth.debian.org
Architecture: all
Depends: gnu-smalltalk (= 3.2.4), libsdl-sound1.2
Description: SDL_sound bindings for GNU Smalltalk
Homepage: http://smalltalk.gnu.org
Description-md5: d9e145d50739a7d8d633010e314cb623
Section: interpreters
Priority: extra
Filename: pool/main/g/gnu-smalltalk/libsdl-sound-gst_3.2.4-2_all.deb
Size: 79226
MD5sum: 3ebe0dd76866d975fe78ee38acd6e61c
SHA1: ec6dea186738852f2733b28c65b961f812ac9bfb
SHA256: 5bf238b597536a86f94546357f2ec0226a7c854cd31e44b81981d787d95faa88

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libsdl-sound-gst=3.2.4-2
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libsdl-sound-gst=3.2.4-2'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmp5EzvyG
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmp5EzvyG
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmp5EzvyG', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmp5EzvyG', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmp5EzvyG', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: Command ok: ['chroot', '/var/tmp/tmp5EzvyG', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.3s DEBUG: Created policy-rc.d and chmodded it.
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmp5EzvyG', 'eatmydata', 
'apt-get', 'update']
0m6.6s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (2787 kB/s)
  Reading package lists...
0m6.6s DEBUG: Command ok: ['chroot', '/var/tmp/tmp5EzvyG', 'eatmydata', 
'apt-get', 'update']
0m6.6s DEBUG: Starting command: ['chroot', 

Bug#715126: Broken library symlink detected in libwnn-dev

[David Steele]

Package: libwnn-dev
Version: 1.1.1~a021+cvs20100325-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libwnn.so
- libwnn.so.0.0.0
  /usr/lib/libjd.so
- libjd.so.0.0.0


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:46:09 EST

Package: libwnn-dev
Source: freewnn
Version: 1.1.1~a021+cvs20100325-6
Installed-Size: 1392
Maintainer: Keita Maehara maeh...@debian.org
Architecture: amd64
Replaces: freewnn-jserver-dev, wnn-dev
Conflicts: freewnn-jserver-dev, wnn-dev, wnn6-dev
Description: Header files and static libraries for Wnn (FreeWnn jserver)
Homepage: http://sourceforge.jp/projects/freewnn/
Description-md5: 27fbc4d254aaa2dae0d544300e61e585
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: optional
Filename: pool/main/f/freewnn/libwnn-dev_1.1.1~a021+cvs20100325-6_amd64.deb
Size: 429144
MD5sum: 3503786389cfff6655d796f0560bbb79
SHA1: 07c4029196aef84c3bd5dcdc17e4a1373a913e79
SHA256: 42ee359837a0f2ae0307ea306c1af4691afe2f63cf97268446b916866d97458c

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libwnn-dev=1.1.1~a021+cvs20100325-6
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libwnn-dev=1.1.1~a021+cvs20100325-6'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpxokSHM
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpxokSHM
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpxokSHM', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpxokSHM', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpxokSHM', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: Command ok: ['chroot', '/var/tmp/tmpxokSHM', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.3s DEBUG: Created policy-rc.d and chmodded it.
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpxokSHM', 'eatmydata', 
'apt-get', 'update']
0m6.6s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (2883 kB/s)
  Reading package lists...
0m6.6s DEBUG: 

Bug#715123: Broken library symlink detected in libuim-dev

[David Steele]

Package: libuim-dev
Version: 1:1.8.6-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/x86_64-linux-gnu/libuim-custom.so
- libuim-custom.so.2.1.0


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 22:15:17 EST

Package: libuim-dev
Source: uim
Version: 1:1.8.6-1
Installed-Size: 517
Maintainer: HIGUCHI Daisuke (VDR dai) d...@debian.org
Architecture: amd64
Depends: libuim8 (= 1:1.8.6-1), uim-common (= 1:1.8.6-1), libgcroots-dev
Description: Universal Input Method - development files
Multi-Arch: same
Homepage: http://code.google.com/p/uim/
Description-md5: fc9a2c0f3032e584a502ed7d4f4034e5
Tag: devel::lang:c, devel::library, implemented-in::c, role::devel-lib
Section: libdevel
Priority: optional
Filename: pool/main/u/uim/libuim-dev_1.8.6-1_amd64.deb
Size: 138210
MD5sum: 152a29fe4a0613b5a803796d05c4278b
SHA1: 1cd430f6fec9a9b45e22cc2301e6843360f5a404
SHA256: e8a5babc672683031a2878e6431a8124b1dcc1af8b87b9ed4b0f41a6d87a56ae

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libuim-dev=1:1.8.6-1
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libuim-dev=1:1.8.6-1'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpU2dN4p
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpU2dN4p
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpU2dN4p', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.2s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpU2dN4p', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.2s DEBUG: Starting command: ['chroot', '/var/tmp/tmpU2dN4p', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.2s DEBUG: Command ok: ['chroot', '/var/tmp/tmpU2dN4p', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.2s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.2s DEBUG: Created policy-rc.d and chmodded it.
0m1.2s DEBUG: Starting command: ['chroot', '/var/tmp/tmpU2dN4p', 'eatmydata', 
'apt-get', 'update']
0m5.3s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (3562 kB/s)
  Reading package lists...
0m5.3s DEBUG: Command ok: ['chroot', '/var/tmp/tmpU2dN4p', 'eatmydata', 
'apt-get', 'update']

Bug#715125: Broken library symlink detected in libwcat1-dev

[David Steele]

Package: libwcat1-dev
Version: 1.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libwcat.so
- libwcat.so.1.1.1


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:42:03 EST

Package: libwcat1-dev
Source: libwcat1
Version: 1.1-1
Installed-Size: 34
Maintainer: Cyril Bouthors cy...@bouthors.org
Architecture: amd64
Description: Process monitoring library
Homepage: http://oss.digirati.com.br/watchcatd/
Description-md5: 277b29345a5007de740ce9bcc8528fa9
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: optional
Filename: pool/main/libw/libwcat1/libwcat1-dev_1.1-1_amd64.deb
Size: 2076
MD5sum: 6e65eb9190cd3a279f96914bd705d919
SHA1: 55eeb3d114c1a90b92a8ba86de45ed35d4672597
SHA256: 27eea6a6f23f988599b1fd0e8f61e0889f0404f5cfcea67ba916f55fcb08dc1c

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libwcat1-dev=1.1-1
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libwcat1-dev=1.1-1'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpp0S9m8
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpp0S9m8
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpp0S9m8', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.5s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpp0S9m8', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.5s DEBUG: Starting command: ['chroot', '/var/tmp/tmpp0S9m8', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.6s DEBUG: Command ok: ['chroot', '/var/tmp/tmpp0S9m8', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.6s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.6s DEBUG: Created policy-rc.d and chmodded it.
0m1.6s DEBUG: Starting command: ['chroot', '/var/tmp/tmpp0S9m8', 'eatmydata', 
'apt-get', 'update']
0m7.0s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 4s (2730 kB/s)
  Reading package lists...
0m7.0s DEBUG: Command ok: ['chroot', '/var/tmp/tmpp0S9m8', 'eatmydata', 
'apt-get', 'update']
0m7.0s DEBUG: Starting command: ['chroot', '/var/tmp/tmpp0S9m8', 'eatmydata', 
'apt-get', '-yf', 'dist-upgrade']
0m8.5s DUMP: 
  Reading package lists...
  Building 

Bug#715124: Broken library symlink detected in libwaei-dev

[David Steele]

Package: libwaei-dev
Version: 3.6.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libwaei.so
- libwaei.so.2.0.0


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:54:07 EST

Package: libwaei-dev
Source: gwaei
Version: 3.6.2-1
Installed-Size: 344
Maintainer: Norbert Preining prein...@debian.org
Architecture: amd64
Description: Japanese-English Dictionary for GNOME
Homepage: http://www.zacharydovel.com/software/gwaei
Description-md5: cfb56b0f7a295120d5039d3c35bee69c
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: optional
Filename: pool/main/g/gwaei/libwaei-dev_3.6.2-1_amd64.deb
Size: 72972
MD5sum: bfaa38196ec266feb188c6d875c8d68b
SHA1: b8de52e179daa0ae5c0231008b6bffa682935e47
SHA256: f9b23cee73695ec7249bb2629a67a9d513591e6d2dad885488de5734ba44e20b

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libwaei-dev=3.6.2-1
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libwaei-dev=3.6.2-1'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpq9sClh
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpq9sClh
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpq9sClh', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpq9sClh', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpq9sClh', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: Command ok: ['chroot', '/var/tmp/tmpq9sClh', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.3s DEBUG: Created policy-rc.d and chmodded it.
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpq9sClh', 'eatmydata', 
'apt-get', 'update']
0m6.9s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (2774 kB/s)
  Reading package lists...
0m6.9s DEBUG: Command ok: ['chroot', '/var/tmp/tmpq9sClh', 'eatmydata', 
'apt-get', 'update']
0m6.9s DEBUG: Starting command: ['chroot', '/var/tmp/tmpq9sClh', 'eatmydata', 
'apt-get', '-yf', 'dist-upgrade']
0m8.4s DUMP: 
  Reading package lists...

Bug#715120: Broken library symlink detected in libsquizz-dev

[David Steele]

Package: libsquizz-dev
Version: 0.99b+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libbioseq.so
- libbioseq.so.0.0.0
  /usr/lib/libbioali.so
- libbioali.so.0.0.0


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:52:58 EST

Package: libsquizz-dev
Source: squizz
Version: 0.99b+dfsg-1
Installed-Size: 1491
Maintainer: Debian Med Packaging Team 
debian-med-packag...@lists.alioth.debian.org
Architecture: amd64
Breaks: squizz (= 0.99a)
Description: development tools for squizz genetic sequence converter
Homepage: ftp://ftp.pasteur.fr/pub/gensoft/projects/squizz/
Description-md5: 589915a772125bf4a896737d450265e0
Tag: devel::lang:c, devel::library, field::biology:bioinformatics,
 implemented-in::c, role::devel-lib, use::converting
Section: libdevel
Priority: optional
Filename: pool/main/s/squizz/libsquizz-dev_0.99b+dfsg-1_amd64.deb
Size: 521574
MD5sum: dc94ce5b03bd426cfa2e344d0b2284ac
SHA1: da11788dcd5b34e6e63d594884b7592bff80c594
SHA256: 70a2a1d83b3cf69b332fbe2fe63529bf6dda92d50278125a3f46421a0d636b00

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libsquizz-dev=0.99b+dfsg-1
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libsquizz-dev=0.99b+dfsg-1'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpLFCsx0
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpLFCsx0
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpLFCsx0', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpLFCsx0', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmpLFCsx0', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: Command ok: ['chroot', '/var/tmp/tmpLFCsx0', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.4s DEBUG: Created policy-rc.d and chmodded it.
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmpLFCsx0', 'eatmydata', 
'apt-get', 'update']
0m6.6s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (2899 kB/s)
  Reading 

Bug#715129: Broken library symlink detected in lldb-3.3

[David Steele]

Package: lldb-3.3
Version: 1:3.3-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/python2.7/dist-packages/lldb/libLLVM-3.3.so.1
- ../../../libLLVM-3.3.so


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 22:14:57 EST

Package: lldb-3.3
Source: llvm-toolchain-3.3
Version: 1:3.3-3
Installed-Size: 22448
Maintainer: LLVM Packaging Team pkg-llvm-t...@lists.alioth.debian.org
Architecture: amd64
Replaces: lldb-3.2
Depends: libc6 (= 2.15), libedit2 (= 2.11-20080614-1), libffi6 (= 3.0.4), 
libgcc1 (= 1:4.1.1), libllvm3.3 (= 1:3.3-3), libpython2.7 (= 2.7), libstdc++6 
(= 4.8), python
Pre-Depends: multiarch-support
Breaks: lldb-3.2
Description: Next generation, high-performance debugger
Homepage: http://www.llvm.org/
Description-md5: 45d52d0209cd7953d2f2bc4d1a99170f
Section: devel
Priority: optional
Filename: pool/main/l/llvm-toolchain-3.3/lldb-3.3_3.3-3_amd64.deb
Size: 8230516
MD5sum: 91e3591c3b9a888add1c624348839369
SHA1: 0604448204cdd015fa532cf109e9d2a290b0faac
SHA256: 73b90048fcd56dfc2eed815873d4a60aa9a5640fac2cc61ccfe9f592a5e78b61

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
lldb-3.3=1:3.3-3
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'lldb-3.3=1:3.3-3'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpgAmnuo
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpgAmnuo
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpgAmnuo', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.2s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpgAmnuo', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.2s DEBUG: Starting command: ['chroot', '/var/tmp/tmpgAmnuo', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.2s DEBUG: Command ok: ['chroot', '/var/tmp/tmpgAmnuo', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.2s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.2s DEBUG: Created policy-rc.d and chmodded it.
0m1.2s DEBUG: Starting command: ['chroot', '/var/tmp/tmpgAmnuo', 'eatmydata', 
'apt-get', 'update']
0m5.3s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (3587 kB/s)
  Reading package 

Bug#715127: Broken library symlink detected in libwtdbomysql-dev

[David Steele]

Package: libwtdbomysql-dev
Version: 3.3.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libwtdbomysql.so
- libwtdbomysql.so.35


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:50:30 EST

Package: libwtdbomysql-dev
Source: witty
Version: 3.3.0-1
Installed-Size: 254
Maintainer: Pau Garcia i Quiles pgqui...@elpauer.org
Architecture: amd64
Provides: witty-dev
Depends: libwtdbofirebird35 (= 3.3.0-1), libwtdbo-dev (= 3.3.0-1)
Recommends: libwthttp-dev (= 3.3.0-1) | libwtfcgi-dev (= 3.3.0-1) | 
libwttest-dev (= 3.3.0-1)
Conflicts: witty-dev ( 3.1.0a-1~)
Description: MySQL/MariaDB backend for Wt::Dbo [development]
Homepage: http://www.webtoolkit.eu/
Description-md5: 6b06b433d240c6163b72b6862924d1b1
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: extra
Filename: pool/main/w/witty/libwtdbomysql-dev_3.3.0-1_amd64.deb
Size: 84002
MD5sum: a231fa22f2d693a1ce1878608f27a75c
SHA1: 6b749f51f0b8d4d66c179acf6ae7630453d6fd09
SHA256: bb0de47937f16c9d95ffbe4e38e95c51252e3991208a8d447175e5f21bb13eb4

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libwtdbomysql-dev=3.3.0-1
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libwtdbomysql-dev=3.3.0-1'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpFf2cAM
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpFf2cAM
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpFf2cAM', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.5s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpFf2cAM', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.5s DEBUG: Starting command: ['chroot', '/var/tmp/tmpFf2cAM', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.5s DEBUG: Command ok: ['chroot', '/var/tmp/tmpFf2cAM', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.5s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.5s DEBUG: Created policy-rc.d and chmodded it.
0m1.5s DEBUG: Starting command: ['chroot', '/var/tmp/tmpFf2cAM', 'eatmydata', 
'apt-get', 'update']
0m7.1s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 4s (2710 kB/s)
  Reading package lists...

Bug#715119: Broken library symlink detected in libspeechd-dev

[David Steele]

Package: libspeechd-dev
Version: 0.7.1-6.2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/speech-dispatcher/libsdaudio.so
- libsdaudio.so.2.0.4


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:54:50 EST

Package: libspeechd-dev
Source: speech-dispatcher
Version: 0.7.1-6.2
Installed-Size: 185
Maintainer: Boris Dušek du...@brailcom.org
Architecture: amd64
Replaces: speech-dispatcher ( 0.7.1-6)
Depends: libspeechd2 (= 0.7.1-6.2)
Suggests: speech-dispatcher
Breaks: speech-dispatcher ( 0.7.1-6)
Description: Speech Dispatcher: Development libraries and header files
Homepage: http://devel.freebsoft.org/speechd
Description-md5: b0cbd061ec5ff46814f8d8ed60212ce0
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: extra
Filename: pool/main/s/speech-dispatcher/libspeechd-dev_0.7.1-6.2_amd64.deb
Size: 43492
MD5sum: 669f6d5d35d53256fdc7416dea1cf60b
SHA1: 4e6b5a13b24dda8e3cb42f39c2ce3791abe62559
SHA256: cc31b942e7e2ddc861b760f2dee8b335562b43ff10ead97d465afd7e51beddbb

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libspeechd-dev=0.7.1-6.2
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libspeechd-dev=0.7.1-6.2'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpDcShmZ
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpDcShmZ
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpDcShmZ', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpDcShmZ', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpDcShmZ', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: Command ok: ['chroot', '/var/tmp/tmpDcShmZ', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.4s DEBUG: Created policy-rc.d and chmodded it.
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmpDcShmZ', 'eatmydata', 
'apt-get', 'update']
0m6.4s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (2917 kB/s)
  Reading package lists...
0m6.4s DEBUG: Command ok: 

Bug#715121: Broken library symlink detected in libstarpu-dev

[David Steele]

Package: libstarpu-dev
Version: 1.0.1-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libstarpufft-1.0.so
- libstarpufft-1.0.so.1.0.1
  /usr/lib/libstarpumpi-1.0.so
- libstarpumpi-1.0.so.1.0.1


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-06 03:13:01 EST

Package: libstarpu-dev
Source: starpu
Version: 1.0.1-4
Installed-Size: 1957
Maintainer: Samuel Thibault sthiba...@debian.org
Architecture: amd64
Depends: libstarpu-1.0 (= 1.0.1-4), libc6 (= 2.14), gcc-4.6 (= 4.6.4-4), 
gcc-4.6 ( 4.6.4A), install-info, libhwloc-dev
Conflicts: libstarpu-contrib-dev
Description: Task scheduler for heterogeneous multicore machines - dev
Homepage: http://starpu.gforge.inria.fr/
Description-md5: 967c103c8b3cf3662ee291f422fa5be6
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: extra
Filename: pool/main/s/starpu/libstarpu-dev_1.0.1-4_amd64.deb
Size: 395440
MD5sum: dcd3973b69ccce2c1bc940e1844ba12c
SHA1: f26be09fe07b7e25cd725dd861d3d08ab3096e5c
SHA256: 64ef87260e79c396812e9d22c80b095eda15e17215218fbb6fa2a80668ef9027

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libstarpu-dev=1.0.1-4
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libstarpu-dev=1.0.1-4'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpxuZxcn
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpxuZxcn
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpxuZxcn', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpxuZxcn', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpxuZxcn', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: Command ok: ['chroot', '/var/tmp/tmpxuZxcn', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.3s DEBUG: Created policy-rc.d and chmodded it.
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpxuZxcn', 'eatmydata', 
'apt-get', 'update']
0m6.0s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [204 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6396 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.4 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.7 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.8 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4256 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (3132 kB/s)
  Reading package 

Bug#715122: Broken library symlink detected in libtorture-dev

[David Steele]

Package: libtorture-dev
Version: 4.0.0~beta2+dfsg1-3.2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/x86_64-linux-gnu/libtorture.so
- libtorture.so.0.0.1


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 22:14:24 EST

Package: libtorture-dev
Source: samba4
Version: 4.0.0~beta2+dfsg1-3.2
Installed-Size: 79
Maintainer: Samba Debian Maintainers pkg-samba-ma...@lists.alioth.debian.org
Architecture: amd64
Depends: pkg-config
Description: Library for running unit tests - development files
Homepage: http://www.samba.org/
Description-md5: 1643da32df4d561e2470b3c500cde8d3
Tag: devel::lang:c, devel::library, implemented-in::c, role::devel-lib,
 suite::samba
Section: libdevel
Priority: optional
Filename: pool/main/s/samba4/libtorture-dev_4.0.0~beta2+dfsg1-3.2_amd64.deb
Size: 18104
MD5sum: 2c834ad0fe1bd66158dac0df8d7a1d0f
SHA1: 4df9e481c6c0af675145750999c9aa98995691a9
SHA256: d9edf52d0f87c00293c69620646fc30fddbf08f18ac3a1ba4e78839ede9821e4

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libtorture-dev=4.0.0~beta2+dfsg1-3.2
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libtorture-dev=4.0.0~beta2+dfsg1-3.2'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpgXu9dn
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpgXu9dn
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpgXu9dn', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.2s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpgXu9dn', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.2s DEBUG: Starting command: ['chroot', '/var/tmp/tmpgXu9dn', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.2s DEBUG: Command ok: ['chroot', '/var/tmp/tmpgXu9dn', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.2s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.2s DEBUG: Created policy-rc.d and chmodded it.
0m1.2s DEBUG: Starting command: ['chroot', '/var/tmp/tmpgXu9dn', 'eatmydata', 
'apt-get', 'update']
0m5.3s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (3580 kB/s)
  Reading package lists...
0m5.3s DEBUG: Command ok: ['chroot', 

Bug#715128: Broken library symlink detected in libxs-compat-libzmq-dev

[David Steele]

Package: libxs-compat-libzmq-dev
Version: 1.2.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libzmq.so
- libzmq.so.1.0.0


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 22:15:49 EST

Package: libxs-compat-libzmq-dev
Source: libxs
Version: 1.2.0-1
Installed-Size: 65
Maintainer: Robert S. Edmonds edmo...@debian.org
Architecture: amd64
Replaces: libzmq-dev
Provides: libzmq-dev
Depends: libxs2 (= 1.2.0-1)
Conflicts: libzmq-dev
Description: Crossroads I/O 'libzmq' compatibility library (header files)
Homepage: http://www.crossroads.io/
Description-md5: 5bb228920c96ce05a499dd108c40bc0c
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: optional
Filename: pool/main/libx/libxs/libxs-compat-libzmq-dev_1.2.0-1_amd64.deb
Size: 10194
MD5sum: 9270501f7727db661686e7ff2c99a876
SHA1: 0b47e1b3289dd9c948d34d19857fdbd3b42a97dc
SHA256: 8299819138fa67b208cc8057667b91e9c4c46e60150071a0e72bc3d72b0df6f4

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
libxs-compat-libzmq-dev=1.2.0-1
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'libxs-compat-libzmq-dev=1.2.0-1'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpl12Okf
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpl12Okf
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpl12Okf', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.2s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpl12Okf', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.2s DEBUG: Starting command: ['chroot', '/var/tmp/tmpl12Okf', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.2s DEBUG: Command ok: ['chroot', '/var/tmp/tmpl12Okf', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.2s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.2s DEBUG: Created policy-rc.d and chmodded it.
0m1.2s DEBUG: Starting command: ['chroot', '/var/tmp/tmpl12Okf', 'eatmydata', 
'apt-get', 'update']
0m5.3s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (3551 kB/s)
  Reading package lists...
0m5.3s DEBUG: Command ok: ['chroot', '/var/tmp/tmpl12Okf', 'eatmydata', 
'apt-get', 

Bug#715130: Broken library symlink detected in lldb-3.4

[David Steele]

Package: lldb-3.4
Version: 1:3.4~svn183914-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/python2.7/dist-packages/lldb/libLLVM-3.4.so.1
- ../../../libLLVM-3.4.so


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:57:45 EST

Package: lldb-3.4
Source: llvm-toolchain-snapshot
Version: 1:3.4~svn183914-1
Installed-Size: 22608
Maintainer: LLVM Packaging Team pkg-llvm-t...@lists.alioth.debian.org
Architecture: amd64
Replaces: lldb-3.2, lldb-3.3
Depends: libc6 (= 2.15), libedit2 (= 2.11-20080614-1), libffi6 (= 3.0.4), 
libgcc1 (= 1:4.1.1), libllvm3.4 (= 1:3.4~svn183914-1), libpython2.7 (= 2.7), 
libstdc++6 (= 4.8), python
Pre-Depends: multiarch-support
Breaks: lldb-3.2, lldb-3.3
Description: Next generation, high-performance debugger
Homepage: http://www.llvm.org/
Description-md5: 45d52d0209cd7953d2f2bc4d1a99170f
Section: devel
Priority: optional
Filename: pool/main/l/llvm-toolchain-snapshot/lldb-3.4_3.4~svn183914-1_amd64.deb
Size: 8286586
MD5sum: 18672b34f8bf98a4b36d09cd38b0b8fd
SHA1: a51d3ef2ac5b3bbeab154e1f38e165bc46106423
SHA256: 437c85e07f3d8721bd436114af9fcffe6246a96c05e33d1739d8ff4e1b6462bc

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
lldb-3.4=1:3.4~svn183914-1
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'lldb-3.4=1:3.4~svn183914-1'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpO8GPBT
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpO8GPBT
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpO8GPBT', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpO8GPBT', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpO8GPBT', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: Command ok: ['chroot', '/var/tmp/tmpO8GPBT', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.3s DEBUG: Created policy-rc.d and chmodded it.
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpO8GPBT', 'eatmydata', 
'apt-get', 'update']
0m6.6s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 

Bug#715135: Broken library symlink detected in yate-dev

[David Steele]

Package: yate-dev
Version: 4.3.0-1~dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/x86_64-linux-gnu/libyateqt4.so
- libyateqt4.so.4.3.0


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:46:47 EST

Package: yate-dev
Source: yate
Version: 4.3.0-1~dfsg-2
Installed-Size: 642
Maintainer: Debian VoIP Team pkg-voip-maintain...@lists.alioth.debian.org
Architecture: amd64
Depends: libyate4.3.0 (= 4.3.0-1~dfsg-2)
Description: Development files for YATE
Homepage: http://yate.null.ro/
Description-md5: fe0716c2de5366bf60c66aa083c9bac2
Tag: devel::library, implemented-in::c++, protocol::voip, role::devel-lib
Section: libdevel
Priority: optional
Filename: pool/main/y/yate/yate-dev_4.3.0-1~dfsg-2_amd64.deb
Size: 123076
MD5sum: 5bd84950ac1a3dc5640188c8ea4a422c
SHA1: fca97a4f27c199ecdd66de0b86389c0b7a1c8f06
SHA256: 47010de4929866cd22d91077d2b5b2d60dc60a89c2553e6c422b62865c4a8560

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
yate-dev=4.3.0-1~dfsg-2
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'yate-dev=4.3.0-1~dfsg-2'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpMYf6mX
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpMYf6mX
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpMYf6mX', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpMYf6mX', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmpMYf6mX', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: Command ok: ['chroot', '/var/tmp/tmpMYf6mX', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.4s DEBUG: Created policy-rc.d and chmodded it.
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmpMYf6mX', 'eatmydata', 
'apt-get', 'update']
0m7.2s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 4s (2648 kB/s)
  Reading package lists...
0m7.2s DEBUG: Command ok: ['chroot', '/var/tmp/tmpMYf6mX', 'eatmydata', 
'apt-get', 'update']
0m7.2s DEBUG: Starting command: 

Bug#715133: Broken library symlink detected in sra-toolkit-libs-dev

[David Steele]

Package: sra-toolkit-libs-dev
Version: 2.1.7a-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libsrareader.so
- libsrareader.so.1
  /usr/lib/libvdb.so
- libvdb.so.2
  /usr/lib/libkq.so
- libkq.so.1
  /usr/lib/libwvdb.so
- libwvdb.so.2
  /usr/lib/libkxfs.so
- libkxfs.so.1
  /usr/lib/libalign-access.so
- libalign-access.so.1
  /usr/lib/libwsradb.so
- libwsradb.so.3
  /usr/lib/libwsra-schema.so
- libwsra-schema.so.1
  /usr/lib/libwkdb.so
- libwkdb.so.1
  /usr/lib/libkproc.so
- libkproc.so.1
  /usr/lib/libsradb.so
- libsradb.so.3
  /usr/lib/libkfs.so
- libkfs.so.1
  /usr/lib/libkfg.so
- libkfg.so.1
  /usr/lib/libksrch.so
- libksrch.so.1
  /usr/lib/libkxml.so
- libkxml.so.1
  /usr/lib/libksproc.so
- libksproc.so.1
  /usr/lib/libalign-reader.so
- libalign-reader.so.1
  /usr/lib/libklib.so
- libklib.so.1
  /usr/lib/libkdb.so
- libkdb.so.1


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 22:14:40 EST

Package: sra-toolkit-libs-dev
Source: sra-sdk
Version: 2.1.7a-1
Installed-Size: 40
Maintainer: Debian Med Packaging Team 
debian-med-packag...@lists.alioth.debian.org
Architecture: amd64
Description: Development files for the NCBI SRA Toolkit's libraries
Homepage: http://trace.ncbi.nlm.nih.gov/Traces/sra/sra.cgi?view=software
Description-md5: db6c561e7efde962727ce64ca7bc482d
Section: science
Priority: optional
Filename: pool/main/s/sra-sdk/sra-toolkit-libs-dev_2.1.7a-1_amd64.deb
Size: 6320
MD5sum: c553ab8849494dc77d2b6e1120c8a7cd
SHA1: aa8af248cef9a38dccf26bee24edd47a612c2ab4
SHA256: 3bc66fddaee7a4413a8c1ebe50e345195ea53cdb1bf4f392311d328cb8458f95

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
sra-toolkit-libs-dev=2.1.7a-1
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'sra-toolkit-libs-dev=2.1.7a-1'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpc5FTmP
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpc5FTmP
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpc5FTmP', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.2s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpc5FTmP', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.2s DEBUG: Starting command: ['chroot', '/var/tmp/tmpc5FTmP', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.2s DEBUG: Command ok: ['chroot', '/var/tmp/tmpc5FTmP', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.2s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.2s DEBUG: 

Bug#715132: Broken library symlink detected in rygel-2.0-dev

[David Steele]

Package: rygel-2.0-dev
Version: 0.18.2-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/librygel-renderer-gst-2.0.so
- librygel-renderer-gst-2.0.so.1.0.0


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:51:25 EST

Package: rygel-2.0-dev
Source: rygel
Version: 0.18.2-2
Installed-Size: 2398
Maintainer: Debian Rygel Maintainers ah-ry...@debian.org
Architecture: amd64
Replaces: rygel-1.0-dev
Depends: libgupnp-1.0-dev, libgstreamer1.0-dev, librygel-core-2.0-1 (= 
0.18.2-2), librygel-server-2.0-1 (= 0.18.2-2), librygel-renderer-2.0-1 (= 
0.18.2-2)
Conflicts: rygel-1.0-dev
Description: GNOME UPnP/DLNA services - plugin development files
Homepage: http://live.gnome.org/Rygel
Description-md5: cab3db3aadb0364325951e091d25bb95
Section: devel
Priority: extra
Filename: pool/main/r/rygel/rygel-2.0-dev_0.18.2-2_amd64.deb
Size: 620822
MD5sum: 73ec35983219ddfddcd7d38119f09bcb
SHA1: 7cff05ac7f0fa1a96aa537c9cf1438c6eb777d6e
SHA256: 08f18365bd1af4d0d211faf2b319dd325d735e77d26efcca71586f752b8c8ecf

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
rygel-2.0-dev=0.18.2-2
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'rygel-2.0-dev=0.18.2-2'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmp8YXCXO
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmp8YXCXO
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmp8YXCXO', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmp8YXCXO', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmp8YXCXO', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: Command ok: ['chroot', '/var/tmp/tmp8YXCXO', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.3s DEBUG: Created policy-rc.d and chmodded it.
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmp8YXCXO', 'eatmydata', 
'apt-get', 'update']
0m6.4s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (2925 kB/s)
  Reading package lists...
0m6.4s DEBUG: Command 

Bug#715131: Broken library symlink detected in nordugrid-arc-dev

[David Steele]

Package: nordugrid-arc-dev
Version: 3.0.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/libarcglobusutils.so
- libarcglobusutils.so.2.0.0


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 22:01:56 EST

Package: nordugrid-arc-dev
Source: nordugrid-arc
Version: 3.0.2-1
Installed-Size: 1272
Maintainer: Mattias Ellert mattias.ell...@fysast.uu.se
Architecture: amd64
Replaces: nordugrid-arc-libs-devel ( 1.0.0~), nordugrid-arc-nox-dev ( 
1.3.0~), nordugrid-arc1-dev ( 1.0.0~)
Provides: nordugrid-arc-libs-devel, nordugrid-arc-nox-dev, nordugrid-arc1-dev
Depends: libarccommon2 (= 3.0.2-1), libc6 (= 2.14), libgcc1 (= 1:4.1.1), 
libglib2.0-0 (= 2.12.0), libglibmm-2.4-1c2a (= 2.36.2), libsigc++-2.0-0c2a 
(= 2.0.2), libstdc++6 (= 4.6), libuuid1 (= 2.16), libxml2 (= 2.6.27), 
zlib1g (= 1:1.1.4), libxml2-dev (= 2.4.0), libssl-dev, libglibmm-2.4-dev
Conflicts: nordugrid-arc-libs-devel ( 1.0.0~), nordugrid-arc-nox-dev ( 
1.3.0~), nordugrid-arc1-dev ( 1.0.0~)
Description: ARC development files
Homepage: http://www.nordugrid.org
Description-md5: f4e555e911b90cf4f3766f4ef2cf9418
Section: net
Priority: optional
Filename: pool/main/n/nordugrid-arc/nordugrid-arc-dev_3.0.2-1_amd64.deb
Size: 298394
MD5sum: 4ca50cb00462bfbd3416829e2e04ffac
SHA1: b3f74f04d0c004538dd8d2dbb78a41a27f1e241d
SHA256: 1548dec48f7b840aad56b94fce2cc963db8d6cb7e4e1ba26dce89adc064e041e

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
nordugrid-arc-dev=3.0.2-1
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'nordugrid-arc-dev=3.0.2-1'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpTBg4b2
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpTBg4b2
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpTBg4b2', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpTBg4b2', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpTBg4b2', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: Command ok: ['chroot', '/var/tmp/tmpTBg4b2', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.4s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.4s DEBUG: Created policy-rc.d and chmodded it.
0m1.4s DEBUG: Starting command: ['chroot', '/var/tmp/tmpTBg4b2', 'eatmydata', 
'apt-get', 'update']
0m5.6s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 

Bug#715134: Broken library symlink detected in trafficserver-dev

[David Steele]

Package: trafficserver-dev
Version: 3.2.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts, broken-symlink, broken-symlink-shared-library

Hi,

During a test with piuparts, I noticed your package is
responsible for the presence of broken symlinks involving
a shared library. Such failures may indicate a significant
problem with the package.

Usually this is caused by a missing Depends. It may also be
triggered if a Recommended or reverse dependency package
owning the symlink target file is not yet installed. This type
of failure mode needs to be eliminated so that other symlink
problems become more visible. In this case, the problem can be
resolved by creating a trigger for the target file. See the
dpkg triggers documentation[1] and an example on the net[2] for
implementation details.

This is being filed as Serious because it represents a violation
of Policy. Section 8 states Packages containing shared
libraries must be constructed with a little care to make sure
that the shared library is always available.

A link to the log containing the indicated broken symlinks can
be found on piuparts.debian.org[3]. Search for Warn: Broken
Symlinks to see the failure point. A log showing the broken
symlink as an error is appended.

The log contains the following broken symlinks:

  /usr/lib/trafficserver/libtsmgmt.so
- libtsmgmt.so.3.2.4
  /usr/lib/trafficserver/libtsutil.so
- libtsutil.so.3.2.4
  /usr/lib/trafficserver/libtsconfig.so
- libtsconfig.so.3.2.4


[1] - file:///usr/share/doc/dpkg-dev/triggers.txt.gz
[2] - http://www.seanius.net/blog/2009/09/dpkg-triggers-howto/
[3] - http://piuparts.debian.org/sid/broken_symlinks_issue.html


--

Start: 2013-07-05 21:46:22 EST

Package: trafficserver-dev
Source: trafficserver
Version: 3.2.4-1
Installed-Size: 1495
Maintainer: Arno Töll a...@debian.org
Architecture: amd64
Suggests: trafficserver (= 3.2.4-1)
Description: Apache Traffic Server Software Developers Kit (SDK)
Homepage: http://trafficserver.apache.org/
Description-md5: c48226f93323179e0f673718c6484a3b
Tag: devel::library, role::devel-lib, suite::apache
Section: web
Priority: extra
Filename: pool/main/t/trafficserver/trafficserver-dev_3.2.4-1_amd64.deb
Size: 434638
MD5sum: feff4871e6b9300fec128bd4d0074b5d
SHA1: 9ffb285a0adad321deca4c0d074a145627898f32
SHA256: 239f1bf63d878358b21dc70a3d183e315f39b499dba7302ddd512aac3b5f6e90

Executing: sudo piuparts --scriptsdir /etc/piuparts/scripts 
--skip-logrotatefiles-test --warn-on-others --fail-on-broken-symlinks --mirror 
http://127.0.0.1/debian --tmpdir /var/tmp --arch amd64 -b 
/var/cache/piuparts/basetgz/sid.tar.gz -d sid --no-upgrade-test --apt 
trafficserver-dev=3.2.4-1
0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 0.54~201306172307~0.53-14-ge8900a0 starting up.
0m0.0s INFO: Command line arguments: '/usr/sbin/piuparts' '--scriptsdir' 
'/etc/piuparts/scripts' '--skip-logrotatefiles-test' '--warn-on-others' 
'--fail-on-broken-symlinks' '--mirror' 'http://127.0.0.1/debian' '--tmpdir' 
'/var/tmp' '--arch' 'amd64' '-b' '/var/cache/piuparts/basetgz/sid.tar.gz' '-d' 
'sid' '--no-upgrade-test' '--apt' 'trafficserver-dev=3.2.4-1'
0m0.0s INFO: Running on: Linux debian-testing 3.9-1-amd64 #1 SMP Debian 3.9.8-1 
x86_64
0m0.0s DEBUG: Created temporary directory /var/tmp/tmpzQvG1Z
0m0.0s DEBUG: Unpacking /var/cache/piuparts/basetgz/sid.tar.gz into 
/var/tmp/tmpzQvG1Z
0m0.0s DEBUG: Starting command: ['tar', '-C', '/var/tmp/tmpzQvG1Z', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Command ok: ['tar', '-C', '/var/tmp/tmpzQvG1Z', '-zxf', 
'/var/cache/piuparts/basetgz/sid.tar.gz']
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpzQvG1Z', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: Command ok: ['chroot', '/var/tmp/tmpzQvG1Z', 'eatmydata', 
'mount', '-t', 'proc', 'proc', '/proc']
0m1.3s DEBUG: sources.list:
  deb http://127.0.0.1/debian sid main
  deb http://127.0.0.1/debian sid contrib
  deb http://127.0.0.1/debian sid non-free
0m1.3s DEBUG: Created policy-rc.d and chmodded it.
0m1.3s DEBUG: Starting command: ['chroot', '/var/tmp/tmpzQvG1Z', 'eatmydata', 
'apt-get', 'update']
0m6.5s DUMP: 
  Get:1 http://127.0.0.1 sid InRelease [205 kB]
  Get:2 http://127.0.0.1 sid/main amd64 Packages [6398 kB]
  Get:3 http://127.0.0.1 sid/contrib amd64 Packages [48.5 kB]
  Get:4 http://127.0.0.1 sid/non-free amd64 Packages [84.6 kB]
  Get:5 http://127.0.0.1 sid/contrib Translation-en [39.9 kB]
  Get:6 http://127.0.0.1 sid/main Translation-en [4246 kB]
  Get:7 http://127.0.0.1 sid/non-free Translation-en [72.7 kB]
  Fetched 11.1 MB in 3s (2913 kB/s)
  Reading package lists...
0m6.5s DEBUG: