Your message dated Thu, 15 Jan 2015 13:32:26 +0000
with message-id <[email protected]>
and subject line Re: Bug#775352: unblock (pre-approval or jessie-p-u):
autopkgtest (was "Fixing autopkgtest RC bug #775076 via t-p-u")
has caused the Debian Bug report #775352,
regarding unblock (pre-approval or jessie-p-u): autopkgtest (was "Fixing
autopkgtest RC bug #775076 via t-p-u")
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
775352: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775352
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: unblock jessie-pu
Opening a bug report since that's way more likely to be handled in this
way.
On Sun, Jan 11, 2015 at 02:00:45PM +0100, Martin Pitt wrote:
> Hello release team,
>
> Christian Kastner discovered that when using vmdebootstrap with
> autopkgtest's "VM setup" script it erroneously enables dpkg's
> "force-unsafe-io" option on the host instead of the guest. This can
> lead to potential system damage and thus should qualify as RC:
>
> https://bugs.debian.org/775076
>
> This is fixed in version 3.9.3 in unstable now, including a postinst
> cleanup for cleaning up an erroneously created
> /etc/dpkg/dpkg.cfg.d/autopkgtest on the host.
>
> At the time when testing froze, testing had 3.6, and unstable's 3.7
> (with a lot of changes) was one day short of propagating to testing;
> so as these were already out of sync, I just kept on uploading to
> unstable as that's what most people use for development. So I prepared
> a debdiff for testing-proposed-updates at
>
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=34;filename=autopkgtest.775076.jessie.debdiff;att=1;bug=775076
>
> autopkgtest is mostly a Debian/Ubuntu developer, QA, and continuous
> integration tool, so honestly the testing version isn't that
> interesting any more. So if you prefer, I'd be perfectly okay (and
> in fact happier) with getting 3.9.3 into testing instead; it has a lot
> of new features, but also a lot of bug fixes:
>
> https://people.debian.org/~mpitt/tmp/autopkgtest_3.6_3.9.3.debdiff
>
> It's clearly waaaay outside the current freeze rules, but as it's not
> an end user tool but rather an internal QA one, I want to at least
> consider it. If we want to go that route, I'm happy to provide more
> details.
>
> Thank you and have a nice Sunday!
>
> Martin
>
> --
> Martin Pitt | http://www.piware.de
> Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
--
Antonio Terceiro <[email protected]>
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
On Wed, Jan 14, 2015 at 09:41:17PM +0100, Ivo De Decker wrote:
> Control: tags -1 confirmed moreinfo
>
> Hi,
>
> On Wed, Jan 14, 2015 at 01:57:33PM -0200, Antonio Terceiro wrote:
> > Opening a bug report since that's way more likely to be handled in this
> > way.
>
> Thanks for that.
>
> > On Sun, Jan 11, 2015 at 02:00:45PM +0100, Martin Pitt wrote:
> > > Hello release team,
> > >
> > > Christian Kastner discovered that when using vmdebootstrap with
> > > autopkgtest's "VM setup" script it erroneously enables dpkg's
> > > "force-unsafe-io" option on the host instead of the guest. This can
> > > lead to potential system damage and thus should qualify as RC:
> > >
> > > https://bugs.debian.org/775076
> > >
> > > This is fixed in version 3.9.3 in unstable now, including a postinst
> > > cleanup for cleaning up an erroneously created
> > > /etc/dpkg/dpkg.cfg.d/autopkgtest on the host.
> > >
> > > At the time when testing froze, testing had 3.6, and unstable's 3.7
> > > (with a lot of changes) was one day short of propagating to testing;
> > > so as these were already out of sync, I just kept on uploading to
> > > unstable as that's what most people use for development. So I prepared
> > > a debdiff for testing-proposed-updates at
>
> > >
> > > https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=34;filename=autopkgtest.775076.jessie.debdiff;att=1;bug=775076
>
> We prefer patches attached to the bug instead of links to somewhere else.
>
> Anyway, please go ahead with the upload to jessie (the distribution should
> also be set to 'jessie') and remove the moreinfo tag from this bug once the
> upload is accepted into t-p-u.
Saw the upload; marked for approval.
Thanks,
--
Jonathan Wiltshire [email protected]
Debian Developer http://people.debian.org/~jmw
4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
signature.asc
Description: Digital signature
--- End Message ---
