** Changed in: gnomescan (Ubuntu Karmic)
Status: Fix Committed = Won't Fix
--
link to gnomescan homepage broken
https://bugs.launchpad.net/bugs/482618
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This bug was fixed in the package gnomescan - 0.6.2-0ubuntu1+lucid1
---
gnomescan (0.6.2-0ubuntu1+lucid1) lucid-proposed; urgency=low
* fix link to project page. (LP: #482618)
-- Rolf Leggewie f...@rolf.leggewie.biz Mon, 13 Sep 2010 22:14:55 +0200
** Changed in: gnomescan
SRU verification for Lucid:
I have reproduced the problem with gnomescan 0.6.2-0ubuntu1 in lucid and have
verified that the version of gnomescan 0.6.2-0ubuntu1+lucid1 in -proposed fixes
the issue.
Marking as verification-done
** Tags added: verification-done
** Tags removed:
Accepted gnomescan into lucid-proposed, the package will build now and
be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
I don't think this is important enough to warrant a Karmic SRU really.
I'ts out for almost a year, so people learned to live with that. So why
risking a rebuild now and inflicting an update to every user in karmic?
--
link to gnomescan homepage broken
https://bugs.launchpad.net/bugs/482618
You
** Branch linked: lp:ubuntu/lucid-proposed/gnomescan
--
link to gnomescan homepage broken
https://bugs.launchpad.net/bugs/482618
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: gnome-scan
Status: Unknown = Fix Released
** Changed in: gnome-scan
Importance: Unknown = Low
--
link to gnomescan homepage broken
https://bugs.launchpad.net/bugs/482618
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Patch added: updated lucid patch
https://bugs.launchpad.net/ubuntu/+source/gnomescan/+bug/482618/+attachment/1577033/+files/lp482618-lucid.debdiff
--
link to gnomescan homepage broken
https://bugs.launchpad.net/bugs/482618
You received this bug notification because you are a member of
** Patch removed: updated lucid patch
https://bugs.launchpad.net/ubuntu/+source/gnomescan/+bug/482618/+attachment/1577033/+files/lp482618-lucid.debdiff
** Patch added: updated lucid patch
** Patch added: updated karmic patch
https://bugs.launchpad.net/ubuntu/+source/gnomescan/+bug/482618/+attachment/1577041/+files/lp482618-karmic.debdiff
--
link to gnomescan homepage broken
https://bugs.launchpad.net/bugs/482618
You received this bug notification because you are a member of
somebody please sponsor the last two patches. Thank you.
--
link to gnomescan homepage broken
https://bugs.launchpad.net/bugs/482618
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Uploaded to karmic-proposed and lucid-proposed. Pending SRU team
approval.
** Changed in: gnomescan (Ubuntu Karmic)
Status: Triaged = Fix Committed
** Changed in: gnomescan (Ubuntu Lucid)
Status: Triaged = Fix Committed
--
link to gnomescan homepage broken
Rolf: BTW I was still subscribed from the previous upload, but you need
to resubscribe ubuntu-sponsors if you want to find somebody.
--
link to gnomescan homepage broken
https://bugs.launchpad.net/bugs/482618
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thank you, Stefano.
--
link to gnomescan homepage broken
https://bugs.launchpad.net/bugs/482618
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Branch linked: lp:ubuntu/gnomescan
--
link to gnomescan homepage broken
https://bugs.launchpad.net/bugs/482618
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Please correct if that's incorrect.
That's incorrect. ubuntu-sponsors receives no bugmail.
I assigned you, as you'd taken on the packaging part of this bug, and it
needed more work. If you don't like being assigned to bugs, I can try to
remember that for the future. You obviously have no
On 16.08.2010 10:52, Stefano Rivera wrote:
seeing as you seemed interested, it made sense that you'd want to know
this bug needs work from you.
Feel free to continue to assign bugs to me.
But it seems you have an incorrect assumption about the incomplete
status. Again, it's NOT meant to poke
do you want to work on merging gnomescan from Debian? Because otherwise
I maintain that my original patch is and always was the most appropriate
way to deal with this. I think merging the Debian package is even
better, but I'll have to leave that to others (you?)
--
link to gnomescan homepage
Michael: Sorry you ended up in the middle of this, but at least your bug
is being worked on :)
Rolf (sorry I missed this message in the flurry):
If you insist on bloating the Ubuntu diff more than necessary I kindly
suggest you make the changes as you see fit.
I was working under the
This bug was fixed in the package gnomescan - 0.6.2-0ubuntu2
---
gnomescan (0.6.2-0ubuntu2) maverick; urgency=low
* fix link to project page. (LP: #482618)
* update to standard version 3.9.1
- fix obsolete-relation-form-in-source warning
-- Rolf Leggewie
** Changed in: gnomescan (Ubuntu)
Importance: Medium = Low
** Also affects: gnomescan (Ubuntu Lucid)
Importance: Undecided
Status: New
--
link to gnomescan homepage broken
https://bugs.launchpad.net/bugs/482618
You received this bug notification because you are a member of Ubuntu
This bug seems a bit unimportant for SRUing, but I've opened a Lucid
task, the SRU team can still weigh in.
Rolf: The lucid debdiff looks ok. For the maverick change: There are
currently no patches to the upstream source in the Ubuntu package,
please enable a patch system (I recommend source
I don't agree this is an unimportant bug, at all. That menu entry is
one of the first entries a user will be looking for help. It really
should work. Please reopen the karmic task.
--
link to gnomescan homepage broken
https://bugs.launchpad.net/bugs/482618
You received this bug notification
I also don't understand why you assign to me and then set to incomplete.
It's my understanding that incomplete is to request for more information
from people affected, not to bug developers. You set to incomplete but
I don't see what information you are looking for from Michael.
--
link to
** Also affects: gnomescan (Ubuntu Karmic)
Importance: Undecided
Status: New
** Changed in: gnomescan (Ubuntu Karmic)
Importance: Undecided = Low
** Changed in: gnomescan (Ubuntu Karmic)
Status: New = Triaged
--
link to gnomescan homepage broken
I think the Maverick debdiff is perfectly fine as is. If you insist on
bloating the Ubuntu diff more than necessary I kindly suggest you make
the changes as you see fit. But if you really want to do the right
thing then I suggest you merge the Debian package and work together with
the Debian
I also don't understand why you assign to me and then set to
incomplete.
Standard sponsor procedure. Unsubscribing sponsors doesn't show up in
e-mail, and I've never sponsored for you before.
Please reopen the karmic task.
Opened.
--
link to gnomescan homepage broken
BTW: I can't SRU both karmic and lucid with the same version numbers,
you'll need to differentiate them. See here:
https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update%20the%20packaging
--
link to gnomescan homepage broken
https://bugs.launchpad.net/bugs/482618
You received this bug
On 15.08.2010 22:25, Stefano Rivera wrote:
I also don't understand why you assign to me and then set to
incomplete.
Standard sponsor procedure. Unsubscribing sponsors doesn't show up in
e-mail, and I've never sponsored for you before.
I'm not sure I understand you correctly. FWIW, your
FWIW, let's not worry about the SRU before we have agreed how to fix
maverick. That's really the first step.
--
link to gnomescan homepage broken
https://bugs.launchpad.net/bugs/482618
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Patch added: this debdiff should fix the problem in maverick
https://bugs.launchpad.net/ubuntu/+source/gnomescan/+bug/482618/+attachment/1487987/+files/lp482618-maverick.debdiff
--
link to gnomescan homepage broken
https://bugs.launchpad.net/bugs/482618
You received this bug notification
** Patch added: this debdiff should fix the problem in lucid
https://bugs.launchpad.net/ubuntu/+source/gnomescan/+bug/482618/+attachment/1487988/+files/lp482618-lucid.debdiff
** Changed in: gnomescan (Ubuntu)
Importance: Undecided = Medium
** Changed in: gnomescan (Ubuntu)
Status:
** Patch added: this debdiff should fix the problem in karmic
https://bugs.launchpad.net/ubuntu/+source/gnomescan/+bug/482618/+attachment/1487997/+files/lp482618-karmic.debdiff
--
link to gnomescan homepage broken
https://bugs.launchpad.net/bugs/482618
You received this bug notification
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/35683809/Dependencies.txt
** Attachment added: ProcEnviron.txt
http://launchpadlibrarian.net/35683810/ProcEnviron.txt
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/35683811/XsessionErrors.txt
** Bug watch added: GNOME Bug Tracker #593960
https://bugzilla.gnome.org/show_bug.cgi?id=593960
** Also affects: gnome-scan via
https://bugzilla.gnome.org/show_bug.cgi?id=593960
Importance: Unknown
Status: Unknown
--
link to gnomescan homepage broken
35 matches
Mail list logo
