Andrey Smirnov
Andrey Smirnov
Looks like I was able to hit that, but with forced compaction and `aptly db cleanup`
but seems to be `aptly db recover` triggering all the tables to be on L0 which leads to this behavior.
Summary: * `too many open files` seem to be related to huge number of tables on L0 (level zero) * under regular operations, I can't trick DB to enter this...
#882 might help here as well
@chnyda I'll get a link added to your repo tomorrow. Thanks!
@aioue I agree that 'wildcard' should work, but right now "always true" condition is `Name` (which means Name is not empty)
No, you don't need `*` at all, just `Name`
Do you believe that aptly should use different architectures list for different components? Btw, you can fix that by passing list of architectures to `aptly mirror create` as `-architectures=i386`.
@eignhpants this sounds like a bug. Could you please provide more information: output of `aptly publish list` and contents of `InRelease` file?
There has already been some issue around that... this is for flat Debian repositories without Relese. Probably this should be fixed.