Hi, also got bitten by this. One suggested workaround is to downgrade to 1.0.0~rc2+git20170201.133.9df8b30-3. However, I can't find this version (and so can't my aptitude). What am I missing?
- Bug#877146: update to runc (1.0.0~rc4) breaks d... Bastian Venthur
- Bug#877146: update to runc (1.0.0~rc4) bre... Chris Lamb
- Processed: Re: [pkg-go] Bug#877146: update... Debian Bug Tracking System
- Bug#877146: [pkg-go] Bug#877146: update to... Bálint Réczey
- Bug#877146: [pkg-go] Bug#877146: update to... Chris Lamb
- Bug#877146: [pkg-go] Bug#877146: update to... Bálint Réczey
- Bug#877146: [pkg-go] Bug#877146: update to... Chris Lamb
- Bug#877146: Where is 1.0.0~rc2+git20170201... Norbert Kiesel
- Bug#877146: Where is 1.0.0~rc2 git20170201... Norbert Kiesel
- Bug#877146: [pkg-go] Bug#877146: update to... Bálint Réczey
- Processed: Re: [pkg-go] Bug#877146: update... Debian Bug Tracking System
- Bug#877146: update to runc (1.0.0~rc4) bre... Shengjing Zhu
- Bug#877146: [pkg-go] Bug#877146: update to... Chris Lamb
- Bug#877146: update to runc (1.0.0~rc4) bre... Bálint Réczey
- Bug#877146: update to runc (1.0.0~rc4) bre... Bálint Réczey
- Processed: Re: Bug#877146: update to runc ... Debian Bug Tracking System
- Bug#877146: marked as done (update to runc... Debian Bug Tracking System
- Bug#877146: update to runc (1.0.0~rc4) bre... Tianon Gravi
