[MIR] gwibber-service-sohu
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gwibber-service-sohu (Ubuntu) |
Fix Released
|
Undecided
|
Didier Roche-Tolomelli |
Bug Description
Availability: http://
Rationale:
This package is useful for our growing user base in China.
The package helps meet a specific Blueprint goal, https:/
Security:
* CVE entries: none
* Secunia entries: none
* Executables which have the suid or sgid bit set: none
* Executables in /sbin, /usr/sbin: none
* Packages which install daemons (/etc/init.d/*): none
* Packages which open privileged ports (ports < 1024): none
* Add-ons and plugins to security-sensitive software (filters, scanners, UI skins, etc): none
Quality assurance:
* No open bugs.
* Good upstream maintenance.
* The package is maintained well in Ubuntu
* UI standards: good UI integration as a gwibber plugin.
* internationaliz
* End-user applications must ship a standard conformant desktop file: N/A it's a plugin
Dependencies:
* All build and binary dependencies (including Recommends:) must be satisfyable in main: yes
Standards compliance:
* The package should meet the FHS and Debian Policy standards: yes
Maintenance:
* The package must have an acceptable level of maintenance corresponding to its complexity: yes, very limited maintenance required.
Background information:
* general purpose and context of the package is clear from the package's debian/control file
Changed in gwibber-service-sohu (Ubuntu): | |
assignee: | nobody → Didier Roche (didrocks) |
summary: |
- gwibber-service-sohu main inclusion report + [MIR] gwibber-service-sohu |
All looks good, but few modification in the package is needed:
Some comments on the package: wiki.debian. org/Python/ TransitionToDHP ython2 dep.debian. net/deps/ dep5/
- we try to have in main all python package using dh_python2. It's basically for this one add the build-dep and --with python2 in debian/rules I guess. See http://
- debian/copyright sould follow the DEP5 format http://
Small and stupid question: any reason the credential is in the packaging?
Please, reset the bug as triaged once those modifications are done.