Sync request RSIBreak from Debian unstable

Bug #400909 reported by Tom Albers
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rsibreak (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: rsibreak

>Source package name
rsibreak

>Source package version number to sync
1:0.10~beta2-1
After the weekend 0.10 will be ready and uploaded in debian.

> Where to sync from (e.g. 'Debian sid main', 'Debian experimental non-free')
Unstable

I don't see any ubuntu changes that should be kept.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

MOTU ack.

Changed in rsibreak (Ubuntu):
status: New → Confirmed
Revision history for this message
James Westby (james-w) wrote :

Hi Jonathan,

We need an explicit declaration that the Ubuntu changes are applied in
Debian or should be dropped. In this bug it's not even clear that the Ubuntu
changes were noticed, so I'm not going to sync. Please comment and
re-confirm if the sync should go ahead.

Thanks,

James

Changed in rsibreak (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

It's basically different packaging, so everything is different but somewhat the same. (same build-deps, different order. Different package descriptions, etc) I see no Ubuntu differences that are really relevant any more. The cmake-find-plasma patch is no longer needed.

Changed in rsibreak (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

debian/changelog just shows a bunch of new upstream release/transition/rebuild uploads anyway. We just haven't synced in a while and Debian rewrote the packaging in the meanwhile.

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

This cannot be sync'd with the current epoch versioning:
  rsibreak | 4:0.9.0-0ubuntu5 | karmic/universe | source, amd64, i386
  rsibreak | 1:0.10-1 | unstable | source, alpha, amd64, armel, hppa, i386, ia64, mips, sparc

Marking as Won't Fix because a sync is not possible.

Changed in rsibreak (Ubuntu):
status: Confirmed → Won't Fix
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Yeah, not sure how a drastic epoch change such as that got past whomever sponsored that...
Anyway, we got Debian to bump their epoch up to match ours: http://packages.qa.debian.org/r/rsibreak/news/20090724T181719Z.html
So reconfirming the bug. (This has been quite an adventure!) ;-)

Changed in rsibreak (Ubuntu):
status: Won't Fix → Confirmed
Revision history for this message
James Westby (james-w) wrote :

[Updating] rsibreak (4:0.9.0-0ubuntu5 [Ubuntu] < 4:0.10-2 [Debian])
 * Trying to add rsibreak...
  - <rsibreak_0.10-2.dsc: downloading from http://ftp.debian.org/debian/>
  - <rsibreak_0.10.orig.tar.gz: downloading from http://ftp.debian.org/debian/>
  - <rsibreak_0.10-2.diff.gz: downloading from http://ftp.debian.org/debian/>
I: rsibreak [universe] -> rsibreak_4:0.9.0-0ubuntu5 [universe].

Changed in rsibreak (Ubuntu):
status: Confirmed → 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.