[Bug 1222128] Re: [needs-packaging] kqoauth

[Howard Chan]

** Description changed:

  Please package kqoauth 0.98
  
   Reported by kubotu for IRC user smartboyhw
+ 
+ FFe request + NEW request:
+ 
+ Why not put it into Debian first?
+ 
+ * It will be too late. It takes at least 3 days to get a sponsor in
+ Debian (maybe even longer), 7 days to go through Debian NEW, 1 day to
+ sync the package from Debian unstable to Ubuntu Saucy, 2-3 days for the
+ package to stay in Ubuntu NEW, and 1 more for uploading Digikam 3.4.0
+ and building it in the archive. That's a whopping 15 days, and by then I
+ want Digikam 3.4.0 uploaded so that it makes Beta 2.
+ 
+ Why I want this package to come in after Feature Freeze?
+ 
+ * It has support for the package "kipi-plugins" from source package
+ "digikam" for authentication. It will be good if we can enable all
+ features for DigiKam.
+ 
+ Why are the patches needed?
+ 
+ * The first patch (which is forwarded to upstream and committed into
+ master) corrects the incorrect multiarch path specifically for AMD64.
+ The second patch is for specific Debian/Ubuntu Multiarch Support.
+ 
+ Why didn't upstream put 0.98 in the NEWS and CHANGELOG file?
+ 
+ * 0.98 is an upstream release for deleting the debian/ folder. Upstream
+ has said that there are not much specific active plans for developing
+ further yet, so he's willing to release 0.98 for the removal.
+ 
+ Why does upstream have the patch in the 0.98 release?
+ 
+ * After the patch has been pulled in, upstream adjusted the tag to
+ include the commit. However it was after I did most of my work of the
+ package, and I decided it would be fine if I upload the package as long
+ as the patch is included.

** Description changed:

  Please package kqoauth 0.98
  
   Reported by kubotu for IRC user smartboyhw
+ 
+ Please review the package at https://launchpad.net/~smartboyhw/+archive
+ /packaging-staging-1/+files/kqoauth_0.98-0ubuntu1.dsc
  
  FFe request + NEW request:
  
  Why not put it into Debian first?
  
  * It will be too late. It takes at least 3 days to get a sponsor in
  Debian (maybe even longer), 7 days to go through Debian NEW, 1 day to
  sync the package from Debian unstable to Ubuntu Saucy, 2-3 days for the
  package to stay in Ubuntu NEW, and 1 more for uploading Digikam 3.4.0
  and building it in the archive. That's a whopping 15 days, and by then I
  want Digikam 3.4.0 uploaded so that it makes Beta 2.
  
  Why I want this package to come in after Feature Freeze?
  
  * It has support for the package "kipi-plugins" from source package
  "digikam" for authentication. It will be good if we can enable all
  features for DigiKam.
  
  Why are the patches needed?
  
  * The first patch (which is forwarded to upstream and committed into
  master) corrects the incorrect multiarch path specifically for AMD64.
  The second patch is for specific Debian/Ubuntu Multiarch Support.
  
  Why didn't upstream put 0.98 in the NEWS and CHANGELOG file?
  
  * 0.98 is an upstream release for deleting the debian/ folder. Upstream
  has said that there are not much specific active plans for developing
  further yet, so he's willing to release 0.98 for the removal.
  
  Why does upstream have the patch in the 0.98 release?
  
  * After the patch has been pulled in, upstream adjusted the tag to
  include the commit. However it was after I did most of my work of the
  package, and I decided it would be fine if I upload the package as long
  as the patch is included.

** Summary changed:

- [needs-packaging] kqoauth
+ [FFe] [needs-packaging] kqoauth

** Description changed:

  Please package kqoauth 0.98
  
   Reported by kubotu for IRC user smartboyhw
  
  Please review the package at https://launchpad.net/~smartboyhw/+archive
  /packaging-staging-1/+files/kqoauth_0.98-0ubuntu1.dsc
  
  FFe request + NEW request:
  
  Why not put it into Debian first?
  
  * It will be too late. It takes at least 3 days to get a sponsor in
  Debian (maybe even longer), 7 days to go through Debian NEW, 1 day to
  sync the package from Debian unstable to Ubuntu Saucy, 2-3 days for the
  package to stay in Ubuntu NEW, and 1 more for uploading Digikam 3.4.0
  and building it in the archive. That's a whopping 15 days, and by then I
- want Digikam 3.4.0 uploaded so that it makes Beta 2.
+ want Digikam 3.4.0 uploaded so that it makes Beta 2. I will submit the
+ package into Debian after the Ubuntu package is uploaded to the archive.
  
  Why I want this package to come in after Feature Freeze?
  
  * It has support for the package "kipi-plugins" from source package
  "digikam" for authentication. It will be good if we can enable all
  features for DigiKam.
  
  Why are the patches needed?
  
  * The first patch (which is forwarded to upstream and committed into
  master) corrects the incorrect multiarch path specifically for AMD64.
  The second patch is for specific Debian/Ubuntu Multiarch Support.
  
  Why didn't upstream put 0.98 in the NEWS and CHANGELOG file?
  
  * 0.98 is an upstream release for deleting the debian/ folder. Upstream
  has said that there are not much specific active plans for developing
  further yet, so he's willing to release 0.98 for the removal.
  
  Why does upstream have the patch in the 0.98 release?
  
  * After the patch has been pulled in, upstream adjusted the tag to
  include the commit. However it was after I did most of my work of the
  package, and I decided it would be fine if I upload the package as long
  as the patch is included.

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1222128

Title:
  [FFe] [needs-packaging] kqoauth

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1222128/+subscriptions