[okular] [Bug 399031] Can't print 4 pages per sheet and then odd/even for double-sided printing

2018-09-24 Thread Luigi Toscano
https://bugs.kde.org/show_bug.cgi?id=399031

--- Comment #7 from Luigi Toscano  ---
I disagree with this guideline. The volume of exact duplicate bugs due to user
error is not so high to make developers waste their time. On the other side,
the connection between the two bugs is lost.
Maybe a new sub-state EXACT_DUPLICATE could solve the issue, but
notwithstanding, I think that DUPLICATE is the correct solution.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 399031] Can't print 4 pages per sheet and then odd/even for double-sided printing

2018-09-24 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=399031

Christoph Feck  changed:

   What|Removed |Added

 Resolution|DUPLICATE   |NOT A BUG

--- Comment #6 from Christoph Feck  ---
Nate is right. Someone looking at bug 399030 might check the duplicates to
gather more information, and we want to spare developers from reading the exact
same information again.

We used to have the INVALID resolution, but NOT A BUG is the best we have now.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 399031] Can't print 4 pages per sheet and then odd/even for double-sided printing

2018-09-24 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=399031

--- Comment #5 from Nate Graham  ---
It was in the bug itself, but it was so long ago I can't remember which one it
was, sorry. We don't have any guidelines one way or the other on
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging or
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging/Identifying_duplicates

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 399031] Can't print 4 pages per sheet and then odd/even for double-sided printing

2018-09-24 Thread Luigi Toscano
https://bugs.kde.org/show_bug.cgi?id=399031

--- Comment #4 from Luigi Toscano  ---
(In reply to Nate Graham from comment #3)
> At one point I was told not to mark duplicates when a single reporter opened
> two bugs, because it could artificially inflate the apparent severity of the
> bug, because the number of duplicates is useful information.

It may be project specific - I don't remember such rule. Do you have any
pointer or was it discussed in person/through messaging systems?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 399031] Can't print 4 pages per sheet and then odd/even for double-sided printing

2018-09-24 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=399031

--- Comment #3 from Nate Graham  ---
At one point I was told not to mark duplicates when a single reporter opened
two bugs, because it could artificially inflate the apparent severity of the
bug, because the number of duplicates is useful information.

If that's no longer the case, I'll happily mark these kinds of bugs as
duplicates from now on.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 399031] Can't print 4 pages per sheet and then odd/even for double-sided printing

2018-09-24 Thread Luigi Toscano
https://bugs.kde.org/show_bug.cgi?id=399031

Luigi Toscano  changed:

   What|Removed |Added

 Resolution|NOT A BUG   |DUPLICATE
 CC||luigi.tosc...@tiscali.it

--- Comment #2 from Luigi Toscano  ---
(In reply to Nate Graham from comment #1)
> Already submitted as Bug 399030. Let's track the issue there.

Right, so it's a duplicate.

*** This bug has been marked as a duplicate of bug 399030 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 399031] Can't print 4 pages per sheet and then odd/even for double-sided printing

2018-09-24 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=399031

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |NOT A BUG
 Status|REPORTED|RESOLVED
 CC||n...@kde.org

--- Comment #1 from Nate Graham  ---
Already submitted as Bug 399030. Let's track the issue there.

-- 
You are receiving this mail because:
You are the assignee for the bug.