On 14.1.2019 20.30, Scott Kitterman wrote: > On Monday, January 14, 2019 08:07:13 PM Timo Aaltonen wrote: >> On 14.1.2019 19.54, Debian FTP Masters wrote: >>> We believe that the bug you reported is now fixed; the following >>> package(s) have been removed from unstable: >>> >>> 389-ds-base | 1.3.4.9-1 | source >>> 389-ds-base | 1.3.4.9-1+b1 | kfreebsd-amd64, kfreebsd-i386 >>> 389-ds-base | 1.4.0.18-1 | source >>> 389-ds-base | 1.4.0.19-3 | source >>> 389-ds-base-dbg | 1.3.4.9-1+b1 | kfreebsd-amd64, kfreebsd-i386 >>> 389-ds-base-dev | 1.3.4.9-1+b1 | kfreebsd-amd64, kfreebsd-i386 >>> 389-ds-base-libs | 1.3.4.9-1+b1 | kfreebsd-amd64, kfreebsd-i386 >>> 389-ds-base-libs-dbg | 1.3.4.9-1+b1 | kfreebsd-amd64, kfreebsd-i386 >>> >>> ------------------- Reason ------------------- >>> ROM; obsolete, provided by 389-ds-base-libs now >>> ---------------------------------------------- >> >> I don't understand how you ended up removing the wrong package.. The bug >> was filed to remove src:svrcore not 389-ds-base which is what now >> provides svrcore... >> >> I'll upload it back in a minute. > > Sorry about that. I was trying to clean up kfreebsd cruft and clearly messed > up. > > Ping me (mail or IRC) when it hits New and I'll push it through.
Well, luckily a version had just entered experimental (uploaded there because it added a new deb) so I just uploaded -2 to sid and things should be fine now. the closed bugs need to be reopened though, including this one until svrcore is removed ;) -- t