[Bug 409862] [NEW] using get-orig-source for creating _current_ tarball is not compliant with debian policy

[Alexander Sack]

Public bug reported:

Binary package hint: bzr-builddeb

As discussed, by debian policy [1] get-orig-source always gets the
latest upstream tarball and not the one matching the current topmost
changelog version.

In consequence, bzr builddeb shouldnt use that in the long run. As a
bunch of branches might still use it, the suggested approach is to add a
--policy-compliant=yes|no to bzr-builddeb and use "no" for one or two
cycles, while spitting out a warning; then after one or two cycles we
switch to "yes" by default, which doesnt use the get-orig-source
anymore.

In the same run, I suggest to  start discussing with debian how to
specify a "get current source" feature.

[1] - http://www.debian.org/doc/debian-policy/ch-source.html - Section
4.9

** Affects: bzr-builddeb (Ubuntu)
     Importance: High
         Status: Triaged

** Description changed:

  Binary package hint: bzr-builddeb
  
- As discussed, by debian policy get-orig-source always gets the latest
- upstream tarball and not the one matching the current topmost changelog
- version.
+ As discussed, by debian policy [1] get-orig-source always gets the
+ latest upstream tarball and not the one matching the current topmost
+ changelog version.
  
  In consequence, bzr builddeb shouldnt use that in the long run. As a
  bunch of branches might still use it, the suggested approach is to add a
  --policy-compliant=yes|no to bzr-builddeb and use "no" for one or two
  cycles, while spitting out a warning; then after one or two cycles we
  switch to "yes" by default, which doesnt use the get-orig-source
  anymore.
  
  In the same run, I suggest to  start discussing with debian how to
  specify a "get current source" feature.
+ 
+ [1] - http://www.debian.org/doc/debian-policy/ch-source.html - Section
+ 4.9

-- 
using get-orig-source for creating _current_ tarball is not compliant with debian policy
https://bugs.launchpad.net/bugs/409862
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs