[Bug 1554843] Re: Remove lava-dispatcher from ubuntu universe
** Also affects: lava (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Remove lava-dispatcher from ubuntu universe + Remove lava (lava-dispatcher & lava-server) from ubuntu universe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554843 Title: Remove lava (lava-dispatcher & lava-server) from ubuntu universe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lava/+bug/1554843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1554843] Re: Remove lava-dispatcher from ubuntu universe
Yes. There is no support for Ubuntu at this time (same for lava-server). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554843 Title: Remove lava-dispatcher from ubuntu universe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lava-dispatcher/+bug/1554843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1554843] Re: Remove lava-dispatcher from ubuntu universe
That was my understanding of the block - to keep what has been released but prevent new releases in Debian from arriving in Ubuntu until someone offers to maintain a LAVA instance in/for Ubuntu. Why was 2016.8-1 allowed to bypass the block? There should be no releases of lava-server in Ubuntu after 2014.9.post1 but I'll leave it up to Ubuntu developers to decide whether to apply this to wily as that's been released. yakity should not have lava-server nor should any further uploads to Debian migrate into Ubuntu until further notice. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554843 Title: Remove lava-dispatcher from ubuntu universe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lava-dispatcher/+bug/1554843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1554843] Re: Remove lava-dispatcher from ubuntu universe
That was my understanding of the block - to keep what has been released but prevent new releases in Debian from arriving in Ubuntu until someone offers to maintain a LAVA instance in/for Ubuntu. Why was 2016.8-1 allowed to bypass the block? There should be no releases of lava-dispatcher in Ubuntu after 2014.9.post1 but I'll leave it up to Ubuntu developers to decide whether to apply this to wily as that's been released. yakity should not have lava-dispatcher nor should any further uploads to Debian migrate into Ubuntu until further notice. ** Summary changed: - Remove lava-server from ubuntu universe + Remove lava-dispatcher from ubuntu universe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554843 Title: Remove lava-dispatcher from ubuntu universe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lava-dispatcher/+bug/1554843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1554843] Re: Remove lava-dispatcher
** Summary changed: - Please do not release with Xenial + Remove lava-dispatcher ** Summary changed: - Remove lava-dispatcher + Remove lava-dispatcher from ubuntu universe ** Summary changed: - Remove lava-dispatcher from ubuntu universe + Remove lava-server from ubuntu universe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554843 Title: Remove lava-dispatcher from ubuntu universe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lava-dispatcher/+bug/1554843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1554843] Re: Please do not release with Xenial
Yes, the block should remain in place until there are upstream resources to maintain and test on Ubuntu and likely until the current migration has completed in the upstream codebase (which will be in 2017). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554843 Title: Please do not release with Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lava-dispatcher/+bug/1554843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1554844] [NEW] Please do not release with Xenial
*** This bug is a duplicate of bug 1554843 *** https://bugs.launchpad.net/bugs/1554843 Public bug reported: The LAVA Software Team at Linaro has discussed the complications of having lava-server and lava-dispatcher in Ubuntu Xenial 16.04LTS and, despite having fixed packages available for sync in Debian unstable, it will be better if lava-server and lava-dispatcher are removed from Ubuntu universe before Xenial is released as the LAVA software team do not have the resources to properly support these packages through the lifetime of Xenial LTS at the versions currently available. Please also block migration of these packages back into Ubuntu. See also https://bugs.launchpad.net/ubuntu/+source/lava- dispatcher/+bug/1554843 lava-tool is completely unaffected by this step and will be fully supportable in Xenial, so please keep that. ** Affects: lava-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554844 Title: Please do not release with Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lava-server/+bug/1554844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1554843] [NEW] Please do not release with Xenial
Public bug reported: The LAVA Software Team at Linaro has discussed the complications of having lava-server and lava-dispatcher in Ubuntu Xenial 16.04LTS and, despite having fixed packages available for sync in Debian unstable, it will be better if lava-server and lava-dispatcher are removed from Ubuntu universe before Xenial is released as the LAVA software team do not have the resources to properly support these packages through the lifetime of Xenial LTS at the versions currently available. Please also block migration of these packages back into Ubuntu. This bug is filed against lava-dispatcher and will be referenced in a similar bug against lava-server. lava-tool is completely unaffected by this step and will be fully supportable in Xenial, so please keep that. ** Affects: lava-dispatcher (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554843 Title: Please do not release with Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lava-dispatcher/+bug/1554843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177122] Re: dummy_deploy: don't boot master image
** Changed in: lava-dispatcher (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177122 Title: dummy_deploy: don't boot master image To manage notifications about this bug go to: https://bugs.launchpad.net/lava-dispatcher/+bug/1177122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 126979] Re: gpe-julia and xaos fractal generators in different sections
Invalid. Just because two applications use the same methods, does not mean the applications are of the same type. gpe-julia is an embedded curiosity, it is not a graphics program. ** Changed in: gpe-julia (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/126979 Title: gpe-julia and xaos fractal generators in different sections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpe-julia/+bug/126979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 739151] Re: [PATCH] dpkg-cross: handle multi-arch packages too
On Wed, 23 Mar 2011 15:37:34 +0100 Marcin Juszkiewicz marcin.juszkiew...@linaro.org wrote: Ubuntu 'natty' switched to multiarch recently and my cross toolchain packages started to fail to build. Most of problems were fixed but then dpkg-cross hit us. Today I looked at dpkg-cross and made attached patch to handle problem. What patch does is converting multiarch packages into old style ones. Are you sure you want to convert Multi-Arch paths to the old paths? The idea is to get the packages concerned to use Multi-Arch paths which the toolchain should just find without needing dpkg-cross at all. The toolchain should be looking in the Multi-Arch paths first, then the old cross paths. The expected role for dpkg-cross once Multi-Arch started to be deployed was only in putting non-Multi-Arch packages into old paths, letting the toolchain find the other packages in their normal Multi-Arch paths. There is no extra switch like --force-even-when-multiarch and --convert-anyway -A is used instead. This is change against latest CVS code (dpkg-cross r1.83). From my tests it looks like it does proper job. It sounds like the wrong job to me. Why are the libraries IN the correct Multi-Arch paths not being found by a Multi-Arch aware toolchain? You need a Multi-Arch-Cross toolchain to work with Multi-Arch and not changes to dpkg-cross. Old toolchains need to be upgraded. If correctly Multi-Arch'd packages are not being found by a Multi-Arch aware toolchain, that's not something dpkg-cross should be expected to solve. -- Neil Williams = http://www.linux.codehelp.co.uk/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/739151 Title: dpkg-cross does not do sensible things with multi-arch: same packages -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 739151] Re: [PATCH] dpkg-cross: handle multi-arch packages too
On Wed, 23 Mar 2011 09:39:04 -0700 Steve Langasek steve.langa...@linaro.org wrote: Hi Neil, On Wed, Mar 23, 2011 at 02:55:07PM -, Neil Williams wrote: On Wed, 23 Mar 2011 15:37:34 +0100 Marcin Juszkiewicz marcin.juszkiew...@linaro.org wrote: Ubuntu 'natty' switched to multiarch recently and my cross toolchain packages started to fail to build. Most of problems were fixed but then dpkg-cross hit us. Today I looked at dpkg-cross and made attached patch to handle problem. What patch does is converting multiarch packages into old style ones. Are you sure you want to convert Multi-Arch paths to the old paths? In a word: yes. As long as we need dpkg-cross to do anything with Multi-Arch: same packages, the thing we need them to do is to convert them over to the old paths. It wasn't initially clear that this was a temporary hack to get through the transition. I'd hate to see this kind of support being used once Multi-Arch-Cross is working and the toolchain is all done etc. As well as removing dpkg-cross from the archive, there may need to be a package which Conflicts: with it or certain cross-builds could Build-Conflict with it. Yet it's the -cross packages that are the problem, if such a problem actually exists. There never was a good way of removing all -cross packages in one go - I wrote emprunecross but it's reliant on detailed knowledge of the toolchain. We do have the dpkg-cross compatibility variable: Provides: libgtk2.0-dev-armel-dcv1 Can't see that this would really help in this case, until we decide that the transition is over but that would then need another upload of the Multi-Arch package to conflict with the -dcv1 version but that means adding one conflict for each arch. Looks like this is just something else for each cross-building developer to have to handle themselves. Current tools (like synaptic and aptitude) do list all these cross packages in the local or obsolete but there's other stuff in that list too. So since a developer might want to have both libc6-armel-cross and libc6:armel installed at the same time during the transition, the files still need to be moved around. The expected role for dpkg-cross once Multi-Arch started to be deployed was only in putting non-Multi-Arch packages into old paths, letting the toolchain find the other packages in their normal Multi-Arch paths. This was also what I expected when viewing the matter from 10,000 feet. Now that we're closer to the ground, I see that more involvement is still needed from dpkg-cross during the transition. :-) Glad to know I hadn't misunderstood the final objective It's not that the toolchain can't find the packages, it's that for bootstrapping toolchains into the archive we need to generate an installable libc6-armel-cross and libc6-dev-armel-cross package - and these packages should not use the multiarch paths, because the *real multiarch packages* want to use those. :) I'll sort this out in dpkg-cross 2.6.3 this weekend. -- Neil Williams = http://www.linux.codehelp.co.uk/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/739151 Title: dpkg-cross does not do sensible things with multi-arch: same packages -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 126979] Re: gpe-julia and xaos fractal generators in different sections
** Changed in: gpe-julia (Ubuntu) Status: Confirmed = Opinion ** Changed in: gpe-julia (Ubuntu) Status: Opinion = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/126979 Title: gpe-julia and xaos fractal generators in different sections -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 650493] Re: Drivel crashed on logging in a blogger account
Already fixed in drivel 3.0.2 available in Maverick. ** Changed in: drivel (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/650493 Title: Drivel crashed on logging in a blogger account -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 634920] Re: Drivel exits with floating point exception
Fixed in version in Maverick ** Changed in: drivel (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/634920 Title: Drivel exits with floating point exception -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 615252] Re: drivel segfaults immediately
Unless this can be reproduced with the current Debian version, it's invalid. ** Changed in: drivel (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/615252 Title: drivel segfaults immediately -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 681505] Re: xapt config and mirrors various related breakages
Fixed in the Debian package in experimental ** Changed in: emdebian-crush (Ubuntu) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/681505 Title: xapt config and mirrors various related breakages -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 625059] Re: multistrap incorrectly identifies some repositories as 'flat URLs'
** Changed in: emdebian-crush (Ubuntu) Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/625059 Title: multistrap incorrectly identifies some repositories as 'flat URLs' -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 115874] Re: svn-buildpackage depends on svn_load_dirs script, which is missing because of a DFSG repack of subversion package
No action on this for three years, the relevant fix is about to go into Debian oldstable. Invalid bug. ** Changed in: svn-buildpackage (Ubuntu) Status: Confirmed = Invalid -- svn-buildpackage depends on svn_load_dirs script, which is missing because of a DFSG repack of subversion package https://bugs.launchpad.net/bugs/115874 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 646901] Re: multistrap needs to be updated for new apt and cross-tools in main
On Fri, 01 Oct 2010 18:41:03 - Steve Langasek steve.langa...@canonical.com wrote: Ah. But in that case, because the unpack ordering is not guaranteed, you would need to reinstall *both* binutils and binutils-multiarch, The unpack ordering *could* be guaranteed as multistrap handles each package individually. It is conceivable that a method can be implemented to specify such a sequence - probably as a config option. e.g. the *order* of packages listed in reinstall=... could be rendered significant. because the unpacked files could be from either package. You don't want to end up with /usr/bin/objdump.single identical to /usr/bin/objdump! That isn't that much of an issue specifically for binutils - nothing actually calls the .single variants - for binutils* itself, diverts could mostly be replaced by Replaces: without problems. The issue of preinst scripts and foreign chroots is wider than just binutils though. Long-term, I think multistrap shouldn't be ignoring the distinctions between essential/required packages and other packages. Sorry, that forces multistrap backwards into the debootstrap model and that just isn't useful. Multistrap needs to work principally for foreign chroots - it's use with pdebuild-cross for cross-building chroots and other native chroots is secondary to it's main purpose. In a foreign environment, there can be no useful division without leaving hundreds of megabytes of .deb files in /var/cache/apt/archives/ completely untouched or partially unpacked and retained anyway (so that the .deb can be reinstalled or replaced files recovered), wasting space in the unconfigured rootfs. That makes it even slower to unpack the unnecessarily large rootfs and then install most of the packages when all that is actually needed is to configure the unpacked packages with nothing at all in /var/cache/apt/archives. The only packages you should need to dpkg -X are these; a three-pass dpkg -X, dpkg --unpack, dpkg --configure of the base system, followed by plain installation of any additional packages, would be reliable without any need to hard-code lists of packages that contain preinsts. That is a backwards step when all that is actually needed is a sensible way of unpacking foreign .deb's without running preinsts. dpkg-divert is the biggest issue with doing that because files get replaced if the .deb is extracted before the preinst can run. Therefore, some way of manipulating diversions in a changed root directory / path is sorely needed. Multistrap can easily identify which packages contain the relevant snippets in their preinst scripts and then store that information. The step I haven't had time to investigate (because I'm moving house soon) is how to modify the files in /path/to/var/lib/dpkg/ and elsewhere such that it looks to dpkg etc. as if the preinst has successfully completed before that particular .deb is extracted. All such manipulations need to be done using the tools running natively outside the foreign chroot. The other roles performed by preinst scripts may also need to have implementations that can be executed from *above* the root directory of the final system and by native tools, not the unpacked foreign ones. Multistap's architecture-neutrality is a vital part of the purpose of the package. If that means that certain packages cannot be put into cross-building chroots due to their maintainer scripts, it doesn't follow that the fix for that can afford to compromise the principal role of creating foreign chroots using external apt to resolve complex dependency chains from multiple repositories - which debootstrap (or the debootstrap model) simply cannot achieve / was never intended to achieve. I'd rather just leave native support broken / retain the current reinstall workaround. It's only affecting a handful of packages currently. -- Neil Williams = http://www.data-freedom.org/ http://www.linux.codehelp.co.uk/ http://e-mail.is-not-s.ms/ -- multistrap needs to be updated for new apt and cross-tools in main https://bugs.launchpad.net/bugs/646901 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 593014] Re: RM: Superceded my multistrap
See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582483 -- RM: Superceded my multistrap https://bugs.launchpad.net/bugs/593014 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 593014] [NEW] RM: Superceded my multistrap
Public bug reported: Binary package hint: emdebian-rootfs emdebian-rootfs has been superceded by multistrap and should be removed from Ubuntu so that multistrap can be added. ** Affects: emdebian-rootfs (Ubuntu) Importance: Undecided Status: Confirmed ** Changed in: emdebian-rootfs (Ubuntu) Status: New = Confirmed ** Summary changed: - Superceded my multistrap + RM: Superceded my multistrap ** Bug watch added: Debian Bug tracker #582483 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582483 -- RM: Superceded my multistrap https://bugs.launchpad.net/bugs/593014 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 580450] Re: Server error Could not understand server response
** Changed in: drivel (Ubuntu) Status: New = Invalid -- Server error Could not understand server response https://bugs.launchpad.net/bugs/580450 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 564850] Re: drivel crashed with SIGFPE in g_cclosure_marshal_VOID__BOXED()
Lots of irrelevant content, one incomplete stracktrace that only puts the blame on libsoup2.4 or some server response chunk. Once again, no effort to get this reported upstream where I might actually be able to do something with it, not even a Debian bug report or a notification to me that the bug even existed. As it's described as Blogger 1.0, I can only assume this is a useless duplicate of an old upstream bug which IS fixed in 3.0.1-1. Closing. ** Changed in: drivel (Ubuntu) Status: New = Invalid -- drivel crashed with SIGFPE in g_cclosure_marshal_VOID__BOXED() https://bugs.launchpad.net/bugs/564850 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 422184] Re: FTBFS with GTK version 2.17
GTK+Extra is dead - this FTBFS still has not been fixed. GPSim does not need it anymore - the Debian package has dropped the dependency. GTK+Extra 2.1.2 is broken and incompatible with GTK 2.18, (as evidenced by this bug) and GTK+Extra 2 is also dead. It is a very bad idea to allow GTK+Extra back into Debian or Ubuntu. It took me nearly a year to get rid of the previous version. There is no version of GTK-Extra3 that is compatible with the upcoming GTK3.0. I was the Debian maintainer for gtk+extra2, I know the package well, I know the upstream and I know that upstream is dead and has not fixed the FTBFS bug. gtk+extra simply abuses the GTK API and there is no fix for this error. If the lack of gtk+extra is such a problem, take the advice of the GTK maintainers and upstream and patch GPSim with the GOffice spreadsheet support used by Gnumeric, available in libgoffice. THAT is the correct solution for GPSim GUI. ** Changed in: gtk+extra2 (Ubuntu) Status: Confirmed = Invalid ** Changed in: gtk+extra2 (Ubuntu) Status: Invalid = Confirmed -- FTBFS with GTK version 2.17 https://bugs.launchpad.net/bugs/422184 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 456905] Re: Dialogue box remains in view during sceenshot
** Changed in: gpe-screenshot (Ubuntu) Status: New = Invalid -- Dialogue box remains in view during sceenshot https://bugs.launchpad.net/bugs/456905 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 454823] Re: can't make screenshot of google suggestions in firefox - suggestions disappear before screenshot is made
** Changed in: gpe-screenshot (Ubuntu) Status: New = Invalid -- can't make screenshot of google suggestions in firefox - suggestions disappear before screenshot is made https://bugs.launchpad.net/bugs/454823 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543977] Re: problems calibrating touch screen (elotouch): ts_calibrate and ts_open are broken
Nobody is tracking this in Ubuntu - I came across it by chance. Report bugs in Debian to get a response. The answer here is in the manpage for ts_calibrate - you need to set the TSLB_TSDEVICE environment variable to be able to use any of the ts_* commands and it sounds like your touchscreen is not appearing in the expected place. You need to work out which device is used and set that environment variable. ** Changed in: tslib (Ubuntu) Status: New = Invalid -- problems calibrating touch screen (elotouch): ts_calibrate and ts_open are broken https://bugs.launchpad.net/bugs/543977 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 531143] Re: emdebian-rootfs package uninstallable
Due to be replaced by multistrap anyway, eventually. ** Changed in: emdebian-rootfs (Ubuntu) Status: New = Fix Committed ** Changed in: emdebian-rootfs (Ubuntu) Assignee: (unassigned) = Neil Williams (codehelp) -- emdebian-rootfs package uninstallable https://bugs.launchpad.net/bugs/531143 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 218264] Re: wrong server address auto-entered
The bug watch is not updating, closing this one in reflection of the closure of the upstream bug. ** Changed in: drivel (Ubuntu) Status: Incomplete = Invalid -- wrong server address auto-entered https://bugs.launchpad.net/bugs/218264 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 151475] Re: Drivel can not handle multiple categories
Closed the upstream bug as wontfix. Closing this one as a duplicate. Current sites for drivel are: http://www.linux.codehelp.co.uk/?q=drivel http://sourceforge.net/projects/drivel/ http://freshmeat.net/projects/drivel/ http://bugzilla.gnome.org/browse.cgi?product=drivel http://drivel.svn.sourceforge.net/viewvc/drivel/ http://drivel.sourceforge.net/ http://mail.gnome.org/mailman/listinfo/drivel-list The mailing list is active, just v.quiet. ** Changed in: drivel (Ubuntu) Status: Incomplete = Invalid -- Drivel can not handle multiple categories https://bugs.launchpad.net/bugs/151475 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 493651] Re: segmentation fault on startup
Unreproducible and no backtrace supplied. Don't file bugs like this in Ubuntu, nobody bothers to feed these bugs upstream so the chance of them being fixed is ZERO. ** Changed in: drivel (Ubuntu) Status: New = Invalid -- segmentation fault on startup https://bugs.launchpad.net/bugs/493651 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 384310] Re: drivel crashed with SIGSEGV in journal_window_build()
No feedback supplied, unreproducible and ubuntu-only. Closing as invalid. ** Changed in: drivel (Ubuntu) Status: Incomplete = Invalid -- drivel crashed with SIGSEGV in journal_window_build() https://bugs.launchpad.net/bugs/384310 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 442093] Re: [Blogger] Drivel craches on logon when . is in UserID
If you want anyone to pay any attention to this upstream, file an upstream bug. Ubuntu-only bugs are commonly ignored. ** Changed in: drivel (Ubuntu) Status: Confirmed = Incomplete ** Changed in: drivel (Ubuntu) Status: Incomplete = Invalid -- [Blogger] Drivel craches on logon when . is in UserID https://bugs.launchpad.net/bugs/442093 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 442093] Re: [Blogger] Drivel craches on logon when . is in UserID
Just noticed that this was in 2.0.x and that's just too old for me to care about. Closing. -- [Blogger] Drivel craches on logon when . is in UserID https://bugs.launchpad.net/bugs/442093 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 122016] Re: Unable to login to blogger with google account
Any bugs from versions of drivel other than 3.0.x will not be fixed. This bug has already been fixed in the current version. -- Unable to login to blogger with google account https://bugs.launchpad.net/bugs/122016 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 421153] Re: package libgpewidget1 0.115-5 failed to install/upgrade: package libgpewidget1 is already installed and configured
Nothing to do with libgpewidget, this was some kind of dbconfig-common bug: (from the attached dpkg log) dbconfig-common: writing config to /etc/dbconfig- common/postfixadmin.conf *** WARNING: ucf was run from a maintainer script that uses debconf, but the script did not pass --debconf-ok to ucf. The maintainer script should be fixed to not stop debconf before calling ucf, and pass it this parameter. For now, ucf will revert to using old-style, non-debconf prompting. Ugh! Please inform the package maintainer about this problem. ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO). unable to connect to mysql server. error encountered creating user: ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO) dbconfig- Log started: 2009-08-29 19:38:00 ** Changed in: libgpewidget (Ubuntu) Status: New = Invalid -- package libgpewidget1 0.115-5 failed to install/upgrade: package libgpewidget1 is already installed and configured https://bugs.launchpad.net/bugs/421153 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 422184] Re: FTBFS with GTK version 2.17
See Debian bug http://bugs.debian.org/563069 - RM: gtk+extra2 -- RoQA; FTBFS, dead upstream, orphaned. gtk+extra2 is now due to be removed from Debian. This removal has already led to the removal of gpsim-led and related packages and is likely to lead to the removal of gpsim and ktechlab too. ** Bug watch added: Debian Bug tracker #563069 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563069 -- FTBFS with GTK version 2.17 https://bugs.launchpad.net/bugs/422184 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 397846] Re: Keyboard shortcuts do not work in gsoko
There is a simple reason for this - gsoko is designed for embedded devices like iPAQs that have direction buttons but not a full keyboard - therefore there would be no 'U' key and hence no shortcut. ** Changed in: gsoko (Ubuntu) Status: New = Invalid -- Keyboard shortcuts do not work in gsoko https://bugs.launchpad.net/bugs/397846 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 442180] Re: No tags and titles in blogger.com entries
** Changed in: drivel (Ubuntu) Status: New = Fix Committed -- No tags and titles in blogger.com entries https://bugs.launchpad.net/bugs/442180 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 442180] Re: No tags and titles in blogger.com entries
Titles are supported in drivel 3.0.0 but I'm not sure if blogger does support tags. Is there any documentation of what XMLRPC is required for blogger to accept tags? http://drivel-dev.blogspot.com/ It looks like labels are available for posts created with blogger.com - are those what you mean? The API appears confused, sometimes calling labels categories, sometimes indicating that these are available on queries but no info on setting them. Posting to multiple blogs is not a likely feature in drivel - you can start multiple instances of drivel or you can save one post as a draft and log out, the log back in to save copy and paste. Please don't make multiple requests in a single bug report. One bug, one issue. I'm only going to deal with this bug as if it only concerns titles in blogger.com entries and that is fixed in drivel 3.0.0 which is already in Debian. If you want the other issues considered, file new bug reports for each - preferably upstream. -- No tags and titles in blogger.com entries https://bugs.launchpad.net/bugs/442180 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 422184] Re: FTBFS with GTK version 2.17
See Debian bug 549758 - http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=549758 I see no prospect of this being fixable. gtk+extra2 has outlived it's usefulness and isn't likely to be fixed (or even fixable). ** Changed in: gtk+extra2 (Ubuntu) Status: New = Confirmed ** Bug watch added: Debian Bug tracker #549758 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549758 -- FTBFS with GTK version 2.17 https://bugs.launchpad.net/bugs/422184 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 384310] Re: drivel crashed with SIGSEGV in journal_window_build()
The bug report is largely useless without details of the blog server involved. If one of the MovableType ones, details of the MT-compatible package (drupal, wordpress, serendipity etc.) as well. Also, whether other blog engines are available to the user and whether any of those have been tried. There have been large changes in upstream SVN (drivel.sourceforge.net) and it may be worth trying drivel 3.0.0 from SVN. This bug report will get no further attention from drivel upstream unless forwarded to bugzilla.gnome.org with the appropriate details of which blog engine was in use at the time. Even then, it is likely to be unreproducible in current SVN due to the internal changes since 2.0.3. ** Changed in: drivel (Ubuntu) Status: New = Incomplete -- drivel crashed with SIGSEGV in journal_window_build() https://bugs.launchpad.net/bugs/384310 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 384310] Re: drivel crashed with SIGSEGV in journal_window_build()
(If it's easier, upstream SVN is now being mirrored by launchpad using bazaar but I've no idea how to export that other than that the LP branch is being updated correctly now.) -- drivel crashed with SIGSEGV in journal_window_build() https://bugs.launchpad.net/bugs/384310 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 384310] Re: drivel crashed with SIGSEGV in journal_window_build()
Current branch, should you want to test with it: http://bazaar.launchpad.net/~vcs-imports/drivel/trunk/files -- drivel crashed with SIGSEGV in journal_window_build() https://bugs.launchpad.net/bugs/384310 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 275710] Re: dpkg-cross failed to install / upgrade : perl error
** Changed in: debhelper (Ubuntu) Status: Incomplete = Invalid -- dpkg-cross failed to install / upgrade : perl error https://bugs.launchpad.net/bugs/275710 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83788] Re: Document font cannot be selected
Fixed upstream, v3.0.0 -- Document font cannot be selected https://bugs.launchpad.net/bugs/83788 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129321] Re: Drivel needs a better Wordpress setup
It is not possible to automate the URL for a wordpress blog because it depends on the individual configuration of that individual server. In many cases, it will be http://myserver/xmlrpc.php but this cannot be assumed and drivel cannot go searching the website for a possible file called xmlrpc.php, it would take too long. It could be any number of levels deep or in a completely different subdomain like http://blog.myserver/ or something. I'm upstream for drivel and I cannot accept the intention of the bug report as-is. All that is possible is that the FAQ can be improved, as documented in the bugzilla version of this bug report. I intend to implement the changes described in the bugzilla report into the next release, at which point I will consider both the bugzilla bug and this bug to be closed as I have had no feedback to the bugzilla bug report for 4 months. Incidentally, this is not just a wordpress issue, it affects ANY blog engine which is user-installable. The only blog engines that are entirely predictable are sites like livejournal and blogger (possibly advogato, need to check that). Therefore it affects my own blog too, which uses serendipity. If there was a reliable way to fix this, I would but user installable blog engines cannot be predictable, by definition. ** Changed in: drivel Status: Incomplete = Invalid ** Changed in: drivel (Ubuntu) Status: Triaged = Invalid -- Drivel needs a better Wordpress setup https://bugs.launchpad.net/bugs/129321 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83788] Re: Document font cannot be selected
** Changed in: drivel Status: Incomplete = Fix Committed -- Document font cannot be selected https://bugs.launchpad.net/bugs/83788 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 122016] Re: Unable to login to blogger with google account
Yes, only Blogger 1.0 is currently supported in drivel, but it does work with the current blogger site albeit with limitations. ** Changed in: drivel Status: New = Fix Committed -- Unable to login to blogger with google account https://bugs.launchpad.net/bugs/122016 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 135253] Re: Drivel does not detect music playing in Rhythmbox
Not all blogs support this query - which blogging engine(s) used to operate in this way? (I'm taking over maintenance of drivel in Debian and I need to know which engines to test for which functionality.) -- Drivel does not detect music playing in Rhythmbox https://bugs.launchpad.net/bugs/135253 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 135253] Re: Drivel does not detect music playing in Rhythmbox
OK, I've got a test setup - the bug is now fixed, upload to Debian has been made. -- Drivel does not detect music playing in Rhythmbox https://bugs.launchpad.net/bugs/135253 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 130815] Re: Please document gnotime's report language
I wanted to develop a new report type for gnotime, but I am unable to find any information about how to do it - beyond the sample reports shipped with gnotime, and the primer, which basically just provides a few more examples. By primer, do you mean /usr/share/gnotime/ghtml/C/gtt.scm ? It is not up to gnotime to document Scheme, it is not a language created for gnotime, it is a scripting language in it's own right - see all the emacs type stuff. Gnotime is far from orphaned, there have been lots of uploads since 2005: * [2008-12-18] gnotime 2.3.0-4 MIGRATED to testing (Britney) * [2008-11-29] Accepted 2.3.0-4 in unstable (low) (Goedson Teixeira Paixao) * [2008-05-13] gnotime 2.3.0-3 MIGRATED to testing (Britney) * [2008-03-19] Accepted 2.3.0-3 in unstable (low) (Goedson Teixeira Paixao) * [2008-02-27] Accepted 2.3.0-2 in unstable (low) (Goedson Teixeira Paixao) * [2008-02-16] Accepted 2.3.0-1 in unstable (low) (Goedson Teixeira Paixao) * [2007-12-06] Accepted 2.2.3-2 in unstable (low) (Goedson Teixeira Paixao) * [2007-09-25] Accepted 2.2.3-1 in unstable (low) (Goedson Teixeira Paixao) * [2007-08-21] gnotime 2.2.2-11 MIGRATED to testing (Britney) * [2007-08-07] Accepted 2.2.2-11 in unstable (low) (Goedson Teixeira Paixao) * [2007-02-10] gnotime 2.2.2-10 MIGRATED to testing (Britney) * [2007-01-29] Accepted 2.2.2-10 in unstable (low) (Goedson Teixeira Paixao) * [2006-12-27] Accepted 2.2.2-9 in unstable (low) (Goedson Teixeira Paixao) * [2006-12-19] Accepted 2.2.2-8 in unstable (low) (Goedson Teixeira Paixao) * [2006-08-10] gnotime 2.2.2-7 MIGRATED to testing (Britney) * [2006-07-29] Accepted 2.2.2-7 in unstable (low) (Goedson Teixeira Paixao) * [2006-04-14] gnotime 2.2.2-6 MIGRATED to testing (Britney) * [2006-03-29] Accepted 2.2.2-6 in unstable (low) (Goedson Teixeira Paixao) * [2006-03-07] gnotime 2.2.2-5 MIGRATED to testing (Britney) * [2006-02-24] Accepted 2.2.2-5 in unstable (low) (Goedson Teixeira Paixao) * [2006-02-24] Accepted 2.2.2-4 in unstable (low) (Goedson Teixeira Paixao) * [2005-12-14] gnotime 2.2.2-3 MIGRATED to testing (Britney) * [2005-12-01] Accepted 2.2.2-3 in unstable (low) (Goedson Teixeira Paixao) * [2005-11-28] Accepted 2.2.2-2 in unstable (low) (Goedson Teixeira Paixao) * [2005-11-03] Accepted 2.2.2-1 in unstable (low) (Goedson Teixeira Paixao) * [2005-09-25] Accepted 2.2.1+20050917-1 in experimental (low) (Goedson Teixeira Paixao) * [2005-08-22] Accepted 2.2.1-18 in unstable (low) (Goedson Teixeira Paixao) * [2005-08-17] Accepted 2.2.1-17 in unstable (low) (Goedson Teixeira Paixao) * [2005-04-29] Accepted 2.2.1-16 in unstable (low) (Goedson Teixeira Paixao) * [2005-04-04] Accepted 2.2.1-15 in unstable (low) (Goedson Teixeira Paixao) http://packages.qa.debian.org/g/gnotime.html Can't be helped if some of those didn't make it into your flavour of Ubuntu. I don't like Scheme, I don't use it but this bug is invalid. Gnotime includes clear guidance that the reports need some scheme programming (see the Gnotime help pages for reports), the rest is up to you. Scheme is big enough to have plenty of examples and documentation, there is no need for Gnotime to duplicate it. -- Please document gnotime's report language https://bugs.launchpad.net/bugs/130815 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 130815] Re: Please document gnotime's report language
The report language is Scheme, documented elsewhere. ** Changed in: gnotime (Ubuntu) Status: New = Invalid -- Please document gnotime's report language https://bugs.launchpad.net/bugs/130815 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 275710] Re: dpkg-cross failed to install / upgrade : perl error
Wrong package. This is/was a debhelper issue afaict. Unreproducible in Debian anyway. ** Changed in: debhelper (Ubuntu) Sourcepackagename: dpkg-cross = debhelper Status: New = Incomplete -- dpkg-cross failed to install / upgrade : perl error https://bugs.launchpad.net/bugs/275710 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 280686] Re: Cache/Apt/Config.pm get_suite() only validates debian suites so fails on ubuntu
Ubuntu releases do not contain suitable binaries for use with apt-cross so a Debian repository is required. Bug is invalid. ** Changed in: apt-cross (Ubuntu) Status: New = Invalid -- Cache/Apt/Config.pm get_suite() only validates debian suites so fails on ubuntu https://bugs.launchpad.net/bugs/280686 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286946] Re: Can't Take Screenshot While A Drop Down Menu Is Open
Wrong package. ** Changed in: gnome-utils (Ubuntu) Sourcepackagename: gpe-screenshot = gnome-utils -- Can't Take Screenshot While A Drop Down Menu Is Open https://bugs.launchpad.net/bugs/286946 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 230588] Re: Allow image to be opened directly from gnome-screenshot
gpe-screenshot is not the GNOME screenshot package, it has nothing to do with GNOME - wrong package. Reassigning. ** Changed in: gnome-utils (Ubuntu) Sourcepackagename: gpe-screenshot = gnome-utils -- Allow image to be opened directly from gnome-screenshot https://bugs.launchpad.net/bugs/230588 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
