Hi,
Quoting Sean Whitton (2016-08-20 19:58:49)
> On Sat, Aug 20, 2016 at 06:56:59PM +0200, Johannes Schauer wrote:
> > You might want to open another bug against propellor to ask it not to
> > generate
> > the key anymore if the propellor maintainers agree that that they don't
> > want to
> > su
Hello,
On Sat, Aug 20, 2016 at 06:56:59PM +0200, Johannes Schauer wrote:
> another way would be to change propellor not to run $(sbuild-update --keygen)
> anymore at all. Doing this is only required if you want to use sbuild for
> chroots containing Debian squeeze or older. If you only build for n
Hi Frederic,
On Sat, 20 Aug 2016 14:51:11 +0200 picca wrote:
> when I run propellor_cronjob, I get this error now
>
> mordor replace /var/cache/ccache-sbuild/sbuild-setup ... ok
> mordor /var/cache/ccache-sbuild/sbuild-setup mode 365 ... ok
> [2016-08-20 14:46:57 CEST] read: apt-cache ["policy",
control: reassign -1 sbuild
control: severity -1 normal
control: tag -1 + patch pending
control: merge -1 833547
Hello Fred,
On Sat, Aug 20, 2016 at 02:51:11PM +0200, picca wrote:
> when I run propellor_cronjob, I get this error now
>
> mordor replace /var/cache/ccache-sbuild/sbuild-setup ... ok
Package: propellor
Version: 3.1.0-1+b2
Severity: important
Dear Maintainer,
when I run propellor_cronjob, I get this error now
mordor replace /var/cache/ccache-sbuild/sbuild-setup ... ok
mordor /var/cache/ccache-sbuild/sbuild-setup mode 365 ... ok
[2016-08-20 14:46:57 CEST] read: apt-cache ["pol
5 matches
Mail list logo
