'Legacy banner' issue

Bug #1859602 reported by Ovidiu Suciu
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Software Center Agent
Fix Released
Undecided
Hasan Ammar

Bug Description

We have this issue https://github.com/canonical-web-and-design/snapcraft.io/issues/2423 an there is an error message coming from the api.
The name match on "banner.[png|jpeg]" is too aggressive and should only be matched against if the file is of type "screenshot".
Currently is seems to be matching against type "banner".

Revision history for this message
Jonathan Hartley (tartley) wrote :

Suspect code:

```
dashboard:/src/devportal/forms.py:2004
# XXX cprov 2019-03-14: quick-and-dirty support for the
# GnomeSoftware (legacy) banner & banner-icon as specially
# named screenshots. Once clients get proper support for
# banner, this 'if' and the helper method can be
# removed along with the corresponding tests.
if not self._is_legacy_banner(uploaded_file.name, image):
```

_is_legacy_banner tests for LEGACY_BANNER_NAMES = ('banner.png', 'banner.jpg')

Hasan Ammar (hasanammar)
Changed in software-center-agent:
assignee: nobody → Hasan Ammar (hasanammar)
status: New → In Progress
Revision history for this message
Hasan Ammar (hasanammar) wrote :

The fix for this bug has been deployed in production. Legacy/gnome-software banners are not supported for new uploads anymore.

Changed in software-center-agent:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.