[Bug 697079] Re: package kdebase-runtime-data 4:4.3.5-0ubuntu1~karmic1 failed to install/upgrade: trying to overwrite '/usr/share/kde4/apps/khelpcenter/searchhandlers/docbook.desktop', which is also i
Thank you for reporting this to Ubuntu. Since this bug only affects a backported package, I have opened a bug task in the appropriate Ubuntu backport project for you. I am only marking the Ubuntu task Invalid. Please report any other issues you may find. ** Also affects: karmic-backports Importance: Undecided Status: New ** Changed in: kdebase-runtime (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Backporters, which is the registrant for Karmic Backports. https://bugs.launchpad.net/bugs/697079 Title: package kdebase-runtime-data 4:4.3.5-0ubuntu1~karmic1 failed to install/upgrade: trying to overwrite '/usr/share/kde4/apps/khelpcenter/searchhandlers/docbook.desktop', which is also in package khelpcenter4 4:4.3.5-0ubuntu1~karmic1 -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 695944] Re: update apache2 in lucid or backport some features?
Correction, I will leave the status at 'New' so somebody from ubuntu- backporters can have a look at it. -- You received this bug notification because you are a member of Ubuntu Backporters, which is subscribed to lucid-backports. https://bugs.launchpad.net/bugs/695944 Title: update apache2 in lucid or backport some features? -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 695944] Re: update apache2 in lucid or backport some features?
Hi Fernan, this is an excellent idea, thanks for taking the time to file the report and help us make Ubuntu better. There is a fairly well documented procedure for requesting backports to lucid, defined here: https://help.ubuntu.com/community/UbuntuBackports#How to request new packages Apache is recommended by quite a few packages, and probably depended on by a lot, so I don't know if it is entirely acceptable for backports. However, I'd support the effort if some core devs and / or MOTU's feel that its worth doing. Changing bug report to affect lucid-backports, marking Confirmed / Wishlist. ** Also affects: lucid-backports Importance: Undecided Status: New ** Changed in: apache2 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Backporters, which is subscribed to lucid-backports. https://bugs.launchpad.net/bugs/695944 Title: update apache2 in lucid or backport some features? -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 692636] Re: backport 2.8.3
** Changed in: cmake (Ubuntu Maverick) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Backporters, which is subscribed to maverick-backports. https://bugs.launchpad.net/bugs/692636 Title: backport 2.8.3 -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 696912] [NEW] Upgrade lucid tryton-server from 1.4.3 to 1.4.5
Public bug reported: Version 1.4.5-2 of tryton-server (which contains some bugfixes from the current 1.4.3) is available in Debian testing -- would it be possible to bump the version in 10.04, as well? Debian package archive for tryton-server 1.4.5-2: http://archive.debian-maintainers.org/tryton/packages/tryton- server/1.4.5-2/ ** Affects: lucid-backports Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Backporters, which is subscribed to lucid-backports. https://bugs.launchpad.net/bugs/696912 Title: Upgrade lucid tryton-server from 1.4.3 to 1.4.5 -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 694475] Re: Backport clementine 0.6-0ubuntu4 to maverick
Ack. Approved by ubuntu-backporters. -- You received this bug notification because you are a member of Ubuntu Backporters, which is a direct subscriber. https://bugs.launchpad.net/bugs/694475 Title: Backport clementine 0.6-0ubuntu4 to maverick -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 694475] Re: Backport clementine 0.6-0ubuntu4 to maverick
OK. In the future please document in the backport request that the package not only builds and installs, but also runs in the target release. ** Changed in: maverick-backports Importance: Undecided => Wishlist ** Changed in: maverick-backports Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Backporters, which is a direct subscriber. https://bugs.launchpad.net/bugs/694475 Title: Backport clementine 0.6-0ubuntu4 to maverick -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 694475] Re: Backport clementine 0.6-0ubuntu4 to maverick
Feedbacks there: https://bugs.launchpad.net/ubuntu/+source/clementine/+bug/694423/comments/9 https://bugs.launchpad.net/ubuntu/+source/clementine/+bug/694118/comments/7 -- You received this bug notification because you are a member of Ubuntu Backporters, which is a direct subscriber. https://bugs.launchpad.net/bugs/694475 Title: Backport clementine 0.6-0ubuntu4 to maverick -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 694475] Re: Backport clementine 0.6-0ubuntu4 to maverick
Did you test the package runs on Maverick? ** Changed in: maverick-backports Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Backporters, which is a direct subscriber. https://bugs.launchpad.net/bugs/694475 Title: Backport clementine 0.6-0ubuntu4 to maverick -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 694475] Re: Backport clementine 0.6-0ubuntu3 to maverick
** Description changed: Binary package hint: clementine + + Changelog + + clementine (0.6-0ubuntu4) natty; urgency=low + + * debian/patches/fix_two_instances.patch: + - Update DEP3 tags. + * debian/patches/show_full_filename_in_osd.patch: + - Don't strip off file extensions in the OSD. + * debian/patches/parsing_non-ascii_filenames.patch: + - Fix parsing non-ascii filenames passed on the commandline + (or through a file browser). (LP: #694423) + * debian/patches/disable_lyric_providers.patch: + - Make it possible to disable all lyric providers. (LP: #694491) clementine (0.6-0ubuntu3) natty; urgency=low - * debian/patches/fix_two_instances.patch: Fix a race condition - on startup that might lead to two instances of Clementine being - started. (LP: #694118) + * debian/patches/fix_two_instances.patch: Fix a race condition + on startup that might lead to two instances of Clementine being + started. (LP: #694118) ** Summary changed: - Backport clementine 0.6-0ubuntu3 to maverick + Backport clementine 0.6-0ubuntu4 to maverick -- You received this bug notification because you are a member of Ubuntu Backporters, which is a direct subscriber. https://bugs.launchpad.net/bugs/694475 Title: Backport clementine 0.6-0ubuntu4 to maverick -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 693157] Re: New bug fix releases: 8.4.6, 8.3.13, 8.1.23
The new postgresql-8.4 package needs a newer postgresql-common as well, I'll backport that too. -- You received this bug notification because you are a member of Ubuntu Backports Testing Team, which is subscribed to Hardy Backports. https://bugs.launchpad.net/bugs/693157 Title: New bug fix releases: 8.4.6, 8.3.13, 8.1.23 -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 693157] New bug fix releases: 8.4.6, 8.3.13, 8.1.23
I: Extracting postgresql-8.4_8.4.6-1.dsc ... done. I: Building backport of postgresql-8.4 as 8.4.6-1~hardy1 ... done. ** Changed in: hardy-backports Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Backports Testing Team, which is subscribed to Hardy Backports. https://bugs.launchpad.net/bugs/693157 Title: New bug fix releases: 8.4.6, 8.3.13, 8.1.23 -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 693157] Re: New bug fix releases: 8.4.6, 8.3.13, 8.1.23
This bug was fixed in the package postgresql-8.4 - 8.4.6-0ubuntu10.10 --- postgresql-8.4 (8.4.6-0ubuntu10.10) maverick-proposed; urgency=low * New upstream bug fix release: (LP: #693157) - Force the default wal_sync_method to be fdatasync on Linux. The default on Linux has actually been fdatasync for many years, but recent kernel changes caused PostgreSQL to choose open_datasync instead. This choice did not result in any performance improvement, and caused outright failures on certain filesystems, notably ext4 with the data=journal mount option. - Fix assorted bugs in WAL replay logic for GIN indexes. This could result in "bad buffer id: 0" failures or corruption of index contents during replication. - Fix recovery from base backup when the starting checkpoint WAL record is not in the same WAL segment as its redo point. - Fix persistent slowdown of autovacuum workers when multiple workers remain active for a long time. The effective vacuum_cost_limit for an autovacuum worker could drop to nearly zero if it processed enough tables, causing it to run extremely slowly. - Add support for detecting register-stack overrun on IA64. The IA64 architecture has two hardware stacks. Full prevention of stack-overrun failures requires checking both. - Add a check for stack overflow in copyObject(). Certain code paths could crash due to stack overflow given a sufficiently complex query. - Fix detection of page splits in temporary GiST indexes. It is possible to have a "concurrent" page split in a temporary index, if for example there is an open cursor scanning the index when an insertion is done. GiST failed to detect this case and hence could deliver wrong results when execution of the cursor continued. - Fix error checking during early connection processing. The check for too many child processes was skipped in some cases, possibly leading to postmaster crash when attempting to add the new child process to fixed-size arrays. - Improve efficiency of window functions. Certain cases where a large number of tuples needed to be read in advance, but work_mem was large enough to allow them all to be held in memory, were unexpectedly slow. percent_rank(), cume_dist() and ntile() in particular were subject to this problem. - Avoid memory leakage while "ANALYZE"'ing complex index expressions. - Ensure an index that uses a whole-row Var still depends on its table. An index declared like create index i on t (foo(t.-)) would not automatically get dropped when its table was dropped. - Do not "inline" a SQL function with multiple OUT parameters. This avoids a possible crash due to loss of information about the expected result rowtype. - Behave correctly if ORDER BY, LIMIT, FOR UPDATE, or WITH is attached to the VALUES part of INSERT ... VALUES. - Fix constant-folding of COALESCE() expressions. The planner would sometimes attempt to evaluate sub-expressions that in fact could never be reached, possibly leading to unexpected errors. - Fix postmaster crash when connection acceptance (accept() or one of the calls made immediately after it) fails, and the postmaster was compiled with GSSAPI support. - Fix missed unlink of temporary files when log_temp_files is active. If an error occurred while attempting to emit the log message, the unlink was not done, resulting in accumulation of temp files. - Add print functionality for InhRelation nodes. This avoids a failure when debug_print_parse is enabled and certain types of query are executed. - Fix incorrect calculation of distance from a point to a horizontal line segment. This bug affected several different geometric distance-measurement operators. - Fix incorrect calculation of transaction status in ecpg. - Fix PL/pgSQL's handling of "simple" expressions to not fail in recursion or error-recovery cases. - Fix PL/Python's handling of set-returning functions. Attempts to call SPI functions within the iterator generating a set result would fail. - Fix bug in "contrib/cube"'s GiST picksplit algorithm. This could result in considerable inefficiency, though not actually incorrect answers, in a GiST index on a cube column. If you have such an index, consider "REINDEX"ing it after installing this update. - Don't emit "identifier will be truncated" notices in "contrib/dblink" except when creating new connections. - Fix potential coredump on missing public key in "contrib/pgcrypto". - Fix memory leak in "contrib/xml2"'s XPath query functions. -- Martin PittTue, 21 Dec 2010 21:06:25 +0100 -- You received this bug notification because you are a member of Ubuntu Ba
[Bug 693157] Re: New bug fix releases: 8.4.6, 8.3.13, 8.1.23
This bug was fixed in the package postgresql-8.4 - 8.4.6-0ubuntu10.04 --- postgresql-8.4 (8.4.6-0ubuntu10.04) lucid-proposed; urgency=low * New upstream bug fix release: (LP: #693157) - Force the default wal_sync_method to be fdatasync on Linux. The default on Linux has actually been fdatasync for many years, but recent kernel changes caused PostgreSQL to choose open_datasync instead. This choice did not result in any performance improvement, and caused outright failures on certain filesystems, notably ext4 with the data=journal mount option. - Fix assorted bugs in WAL replay logic for GIN indexes. This could result in "bad buffer id: 0" failures or corruption of index contents during replication. - Fix recovery from base backup when the starting checkpoint WAL record is not in the same WAL segment as its redo point. - Fix persistent slowdown of autovacuum workers when multiple workers remain active for a long time. The effective vacuum_cost_limit for an autovacuum worker could drop to nearly zero if it processed enough tables, causing it to run extremely slowly. - Add support for detecting register-stack overrun on IA64. The IA64 architecture has two hardware stacks. Full prevention of stack-overrun failures requires checking both. - Add a check for stack overflow in copyObject(). Certain code paths could crash due to stack overflow given a sufficiently complex query. - Fix detection of page splits in temporary GiST indexes. It is possible to have a "concurrent" page split in a temporary index, if for example there is an open cursor scanning the index when an insertion is done. GiST failed to detect this case and hence could deliver wrong results when execution of the cursor continued. - Fix error checking during early connection processing. The check for too many child processes was skipped in some cases, possibly leading to postmaster crash when attempting to add the new child process to fixed-size arrays. - Improve efficiency of window functions. Certain cases where a large number of tuples needed to be read in advance, but work_mem was large enough to allow them all to be held in memory, were unexpectedly slow. percent_rank(), cume_dist() and ntile() in particular were subject to this problem. - Avoid memory leakage while "ANALYZE"'ing complex index expressions. - Ensure an index that uses a whole-row Var still depends on its table. An index declared like create index i on t (foo(t.-)) would not automatically get dropped when its table was dropped. - Do not "inline" a SQL function with multiple OUT parameters. This avoids a possible crash due to loss of information about the expected result rowtype. - Behave correctly if ORDER BY, LIMIT, FOR UPDATE, or WITH is attached to the VALUES part of INSERT ... VALUES. - Fix constant-folding of COALESCE() expressions. The planner would sometimes attempt to evaluate sub-expressions that in fact could never be reached, possibly leading to unexpected errors. - Fix postmaster crash when connection acceptance (accept() or one of the calls made immediately after it) fails, and the postmaster was compiled with GSSAPI support. - Fix missed unlink of temporary files when log_temp_files is active. If an error occurred while attempting to emit the log message, the unlink was not done, resulting in accumulation of temp files. - Add print functionality for InhRelation nodes. This avoids a failure when debug_print_parse is enabled and certain types of query are executed. - Fix incorrect calculation of distance from a point to a horizontal line segment. This bug affected several different geometric distance-measurement operators. - Fix incorrect calculation of transaction status in ecpg. - Fix PL/pgSQL's handling of "simple" expressions to not fail in recursion or error-recovery cases. - Fix PL/Python's handling of set-returning functions. Attempts to call SPI functions within the iterator generating a set result would fail. - Fix bug in "contrib/cube"'s GiST picksplit algorithm. This could result in considerable inefficiency, though not actually incorrect answers, in a GiST index on a cube column. If you have such an index, consider "REINDEX"ing it after installing this update. - Don't emit "identifier will be truncated" notices in "contrib/dblink" except when creating new connections. - Fix potential coredump on missing public key in "contrib/pgcrypto". - Fix memory leak in "contrib/xml2"'s XPath query functions. -- Martin PittTue, 21 Dec 2010 21:13:09 +0100 ** Changed in: postgresql-8.4 (Ubuntu Lucid) Status: Fix Committed => Fi
[Bug 693157] Re: New bug fix releases: 8.4.6, 8.3.13, 8.1.23
We also need to update the existing hardy backport. Shamefully we already forgot the 8.4.5 update (which had a security fix), sorry about that. ** Also affects: hardy-backports Importance: Undecided Status: New ** Changed in: hardy-backports Status: New => In Progress ** Changed in: hardy-backports Assignee: (unassigned) => Martin Pitt (pitti) -- You received this bug notification because you are a member of Ubuntu Backports Testing Team, which is subscribed to Hardy Backports. https://bugs.launchpad.net/bugs/693157 Title: New bug fix releases: 8.4.6, 8.3.13, 8.1.23 -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
