Bug#475722: semop(2) gives wrong information in its example section

Package: manpages-dev Version: 2.79-2 Severity: important Tags: patch Hi, sops[1].sem_op must be equal to 1 to increment value by 1. Being equal to 0 means no difference as waiting for value to equal 0. Therefore there is no difference from the previous setting on sops[0].sem_op. A NMUdiff is

Bug#475722: semop(2) gives wrong information in its example section

tags 475722 fixed-upstream thanks Thanks Gerome -- fixed in upstream 2.80. Cheers, Michael On Sat, Apr 12, 2008 at 4:18 PM, Aurélien GÉRÔME [EMAIL PROTECTED] wrote: Package: manpages-dev Version: 2.79-2 Severity: important Tags: patch Hi, sops[1].sem_op must be equal to 1 to increment