Your message dated Sat, 9 Mar 2019 15:45:34 +0000
with message-id <[email protected]>
and subject line Re: Bug#922300: unblock: chef/13.8.7-3, ohai/13.8.0-1
has caused the Debian Bug report #922300,
regarding unblock: chef/13.8.7-3, ohai/13.8.0-1
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.)
--
922300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922300
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: unblock
Hello,
Please unblock package chef
Hi,
The ci.debian.net nodes are managed with chef, and during the weekend I
realized that it was not in testing. There was an RC bug against chef (FTBFS, 3
tests broken by an update to the test framework, package just worked
nevertheless) and ruby-cheffish (broken by openssl 1.1.1). I fixed both, and
they were ACCEPTED in unstable Sunday morning within less than one hour of each
other (ruby-cheffish at 11:53:21 +0000 and chef at 12:34:15 +0000)
https://tracker.debian.org/news/1029431/accepted-chef-1387-3-source-into-unstable/
https://tracker.debian.org/news/1029425/accepted-ruby-cheffish-1310-2-source-into-unstable/
ruby-cheffish migrated to testing before the freeze, but chef didn't
even though they have a pathological circular build dependency. So
ruby-cheffish can't be built in buster at the moment:
The following packages have unmet dependencies:
builddeps:ruby-cheffish : Depends: chef but it is not installable
E: Unable to correct problems, you have held broken packages.'
Maybe this a bug in britney; it should have migrated either both or none
of them, but not one without the other.
I would very much prefer to have this fixed by having chef migrate, since 1)
that would make my life maintaining ci.debian.net much easier and 2) it will
save a lot of Debian users the pain of not having chef in stable. OTOH I
realize chef that the fixes came in late, so if it's unacceptable to have it in
buster, ruby-cheffish needs to be removed.
So I would ask you to
unblock chef/13.8.7-3
unstable ohai/13.8.0-1
(ohai also has a circular dependency with chef and was removed from testing
because of chef)
OR
remove ruby-cheffish/13.1.0-2
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8),
LANGUAGE=pt_BR:pt:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Thu, Feb 14, 2019 at 09:42:42AM -0200, Antonio Terceiro wrote:
> Please unblock package chef
Unblocked (no precedence); thanks.
--
Jonathan Wiltshire [email protected]
Debian Developer http://people.debian.org/~jmw
4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
--- End Message ---
