On Sat, Jan 26, 2019 at 11:17:35PM +0100, Andreas Beckmann wrote:
> I think I now understood what is happening here.
> Both python3 and dicoweb are being installed in the same run.
> At the time python3 gets configured, dicoweb is already unpacked, but
> not yet configured and therefore /etc/dicowe
On Sat, Jan 26, 2019 at 11:17:35PM +0100, Andreas Beckmann wrote:
> I think I now understood what is happening here.
> Both python3 and dicoweb are being installed in the same run.
> At the time python3 gets configured, dicoweb is already unpacked, but
> not yet configured and therefore /etc/dicowe
On 2018-12-17 04:48, أحمد المحمودي wrote:
> On Wed, Dec 05, 2018 at 03:15:59AM +0100, Andreas Beckmann wrote:
>> Setting up python3 (3.7.1-2) ...
>> [Errno 2] No such file or directory: '/usr/share/dicoweb/settings.py'
> ---end quoted text---
>
> '/usr/share/dicoweb/settings.py' is a symlink t
On Fri, Jan 25, 2019 at 06:32:47PM +0100, Andreas Beckmann wrote:
> @Holger: please reschedule sid/pass/dicoweb_2.7-1.log
done.
--
tschüß,
Holger
---
holger@(debian|reproducible-builds|layer-acht
Control: reopen -1
Control: tags -1 =
On 2019-01-25 08:51, Debian Bug Tracking System wrote:
> This seems to be a temporary problem, since piuparts log seems fine now:
> https://piuparts.debian.org/sid/pass/dicoweb_2.7-1.log
That logfile predates the bug report.
I can still reproduce it in my pi
On Wed, Dec 05, 2018 at 03:15:59AM +0100, Andreas Beckmann wrote:
> Setting up python3 (3.7.1-2) ...
> [Errno 2] No such file or directory: '/usr/share/dicoweb/settings.py'
---end quoted text---
'/usr/share/dicoweb/settings.py' is a symlink to
/etc/dicoweb/settings.py , could this be the caus
Package: dicoweb
Version: 2.7-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
>From the attac
7 matches
Mail list logo
