| Summary: | [UPDATE REQUEST] clamtk 4.41 -> 4.44 | ||
|---|---|---|---|
| Product: | [ROSA-based products] ROSA Fresh | Reporter: | Giovanni Mariani <mc2374> |
| Component: | Packages from Main | Assignee: | ROSA Linux Bugs <bugs> |
| Status: | RESOLVED FIXED | QA Contact: | ROSA Linux Bugs <bugs> |
| Severity: | normal | ||
| Priority: | Normal | CC: | alex.burmashev, alexander.petryakov, denis.silakov, dmitry.romashkin, mc2374 |
| Version: | Fresh | Flags: | alexander.petryakov:
qa_verified+
dmitry.romashkin: secteam_verified+ alex.burmashev: published+ |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Platform: | --- | ROSA Vulnerability identifier: | |
| RPM Package: | clamtk | ISO-related: | |
| Bad POT generating: | Upstream: | ||
|
Description
Giovanni Mariani
2013-01-10 20:39:42 MSK
Advisory: update clamtk to ver. 4.44 and also cleanup the spec file. https://abf.rosalinux.ru/build_lists/872554 https://abf.rosalinux.ru/build_lists/872555 The correct workflow is to leave the bug in the "RESOLVED FIXED" state when requesting QA check. QA will set its status back to CONFIRMED in case of issues. (In reply to comment #2) > The correct workflow is to leave the bug in the "RESOLVED FIXED" state when > requesting QA check. QA will set its status back to CONFIRMED in case of > issues. Thanks for the clue... But I leaved the status in "confirmed" because I was not able to check the "Request For Update" checkbox, after changing the status to resolved-fixed (as abondrov told me to do on private email)... I guessed something was going wrong and so reinstated the original status. clamtk-4.44-1 ************** Advisory ************** update clamtk to ver. 4.44 and also cleanup the spec file. ************************************** QA Verified |