Hi,
On Thu, 14 Jun 2018 10:15:51 -0700
Tianon Gravi wrote:
> > Instead of stretch simply defaulting to non-merged-usr, it's now
> > _blacklisted_ from merged-usr, even if I explicitly specify
> > "--merged-usr", right? Is that the intended implementation here?
Yes, since releases until
Hi,
Holger Wansing (2018-06-14):
> > I also changed some lines from svn to git (./daily-build-aggregator
> > and ./daily-build-manager and ./daily-build-overview)
>
> They fail, because on dillon, there is still a checkout of the svn
> repo. So dillon needs an git checkout there.
>
> Ok for
Hi,
Holger Wansing wrote:
> > > 2.
> > > Above you mention "re-enable cron entries". However, I cannot find any
> > > such
> > > disabled entries.
> > > I assume the l10n-sync process is currently enabled, or am I missing
> > > something?
> > > (I'm planning to test the modified script via
Hi,
Cyril Brulebois wrote:
> Hi,
>
> Holger Wansing (2018-06-12):
> > Cyril Brulebois wrote:
> > > I think it would make sense to have you in the d-i gid, so that you can
> > > access dillon, and re-enable crontab entries, maybe subscribing to cron
> > > mails? Of course I could re-enable
On Thu, 14 Jun 2018 at 10:00, Tianon Gravi wrote:
> Instead of stretch simply defaulting to non-merged-usr, it's now
> _blacklisted_ from merged-usr, even if I explicitly specify
> "--merged-usr", right? Is that the intended implementation here?
If the attached patch is an OK direction, I'd be
On Thu, 14 Jun 2018 at 07:43, Tianon Gravi wrote:
> Update is dput now -- should show up (and get re-tested) soonish. :)
It just dawned on me that this upload possibly won't actually fix the failure.
Instead of stretch simply defaulting to non-merged-usr, it's now
_blacklisted_ from merged-usr,
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package libgcrypt20, this is a upstream bugfix/security
release of the stable branch, fixing CVE-2018-0495.
On Thu, 14 Jun 2018 at 07:31, Tianon Gravi wrote:
> Ah, which is exactly what I did in [1], but the 0.7 release isn't
> uploaded to Debian yet -- I'll do that ASAP to fix this regression. :)
Update is dput now -- should show up (and get re-tested) soonish. :)
Thanks! (and thanks for your work
On Thu, 14 Jun 2018 at 02:23, Hideki Yamane wrote:
> > debootstrap should default to non-merged-usr for stretch, but it should
> > be possible to enable merged-usr via the command-line parameter to avoid
> > the regression in debuerreotype.
> ...
> We can use "--no-merged-usr" and
Hi,
> The patch for #839046 also disabled --merged-usr for stretch as stretch
> was added to the blacklist in first_stage_install().
>
> debootstrap should default to non-merged-usr for stretch, but it should
> be possible to enable merged-usr via the command-line parameter to avoid
> the
Hi,
Paul Gevers writes:
> I looked at the test¹ and it compares the result of the current run of
> debuerreotype with a stored hash. Luckily debuerreotype use diffoscope
> to investigate the delta. It seems that debuerreotype is hit by this
> change in debootstrap:
>
> * Enable merged-/usr by
Dear maintainers,
With a recent upload of debootstrap the autopkgtest of debuerreotype
version 0.6-1 started to fail. See:
https://ci.debian.net/packages/d/debuerreotype/
and
https://qa.debian.org/excuses.php?package=debootstrap
I looked at the test¹ and it compares the result of the current run
12 matches
Mail list logo
