Please sync tuxpaint 1:0.9.22-1 from debian testing

Bug #1403664 reported by Mattia Rizzolo
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tuxpaint (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

tuxpaint (1:0.9.22-1) unstable; urgency=low

  * New upstream release. (Closes: #722933)
  * Switch to dpkg-source 3.0 (quilt) format.
  * Dependencies fixed.
    (Closes: #619724, #648787, #726580, #731728, #738252, #741671, #741691)

 -- Ben Armstrong <email address hidden> Sun, 26 Oct 2014 09:20:50 -0300

Revision history for this message
Mattia Rizzolo (mapreri) wrote :
Revision history for this message
Martin Pitt (pitti) wrote :

I'm fairly sure that debian/patches/fix-build-dep.patch is obsolete, as we don't change the build deps any more (that change was dropped a long time ago).

debian/patches/fix-gettext-domain.patch is also obsolete as tuxpaint isn't covered by language packs any more.

+ - debian/control: tuxpaint-data recommends (not depends) on
+ tuxpaint-stamps-default | tuxpaint-stamps.

The dependency changes also don't seem to be necessary any more. This was bug 82510, but in current Debian tuxpaint-stamps-default only recommends tuxpaint, so there is no cyclic dependency which would break apt.

Thus I think we can just sync this. Do you agree?

Revision history for this message
Mattia Rizzolo (mapreri) wrote : Re: [Bug 1403664] Re: Please merge tuxpaint 1:0.9.22-1 from debian testing

On Thu, Dec 18, 2014 at 8:38 AM, Martin Pitt <email address hidden> wrote:
> I'm fairly sure that debian/patches/fix-build-dep.patch is obsolete, as
> we don't change the build deps any more (that change was dropped a long
> time ago).

indeed... a test build shows it build fine without.

> debian/patches/fix-gettext-domain.patch is also obsolete as tuxpaint
> isn't covered by language packs any more.

umh... what's the canonical way to be aware of this?
In the past I keep every change about this, being unsure of how to check it.

> + - debian/control: tuxpaint-data recommends (not depends) on
> + tuxpaint-stamps-default | tuxpaint-stamps.
>
> The dependency changes also don't seem to be necessary any more. This
> was bug 82510, but in current Debian tuxpaint-stamps-default only
> recommends tuxpaint, so there is no cyclic dependency which would break
> apt.

right.

> Thus I think we can just sync this. Do you agree?

yes, please do (and if can tell me how to check the translation stuff would be great)

 summary "Please sync tuxpaint 1:0.9.22-1 from debian testing"

--
regards,
Mattia Rizzolo

GPG Key: 4096R/B9444540 http://goo.gl/I8TMB
more about me: http://mapreri.org
Launchpad User: https://launchpad.net/~mapreri
Ubuntu Wiki page: https://wiki.ubuntu.com/MattiaRizzolo

summary: - Please merge tuxpaint 1:0.9.22-1 from debian testing
+ Please sync tuxpaint 1:0.9.22-1 from debian testing
Revision history for this message
Martin Pitt (pitti) wrote :

> umh... what's the canonical way to be aware of this?

Good question -- The Ubuntu desktop team should generally know, but it's that sort of knowledge which almost always exists only in the heads of maintainers :/

I'll sync the package, thanks!

Changed in tuxpaint (Ubuntu):
status: New → Fix Released
Revision history for this message
Martin Pitt (pitti) wrote :

This bug was fixed in the package tuxpaint - 1:0.9.22-1
Sponsored for Mattia Rizzolo (mapreri)

---------------
tuxpaint (1:0.9.22-1) unstable; urgency=low

  * New upstream release. (Closes: #722933)
  * Switch to dpkg-source 3.0 (quilt) format.
  * Dependencies fixed.
    (Closes: #619724, #648787, #726580, #731728, #738252, #741671, #741691)

 -- Ben Armstrong <email address hidden> Sun, 26 Oct 2014 09:20:50 -0300

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.