[Bug 122814] git clone -q timeout workaround
*** This bug is a duplicate of bug 122988 *** https://bugs.launchpad.net/bugs/122988 This problem is trigered only use of git-daemon's --timeout option with small timeouts. A workaround is to pass a much larger value for --timeout. The value should be large enough to prepare a complete clone of any repo on the server. Eg, --timeout=5000. (The --timeout parameter only helps clean up stuck processes. Stuck processes take a trivial amount of resource and are only a problem if there are very many - as happens if they never get cleaned up. The approximate steady state number of stuck processes on a server can be found by dividing the value of timeout by the interval between generating stuck processes. Eg, if you generate one stuck process every 50 seconds, --timeout=5000 will result in roughly 100 such processes hanging around at any particular time.) Thanks, Ian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/122814 Title: notification-daemon crashed with signal 5 in g_logv() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notification-daemon/+bug/122814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1175557] Re: adt-run fulfills dependencies with --built-tree contrary to the manpage
Robie Basak writes ("Re: [Bug 1175557] Re: adt-run fulfills dependencies with --built-tree contrary to the manpage"): > On Tue, Jan 28, 2014 at 04:22:06PM -, Ian Jackson wrote: > > Do you want me to try to explain how I think they're supposed to > > work ? > > Please! I said this to pitti on IRC earlier: > > 11:10 pitti: incidentally, I find the manpage very confusing > and ambiguous whenever I'm trying to understand what the different > --built-tree, --unbuilt-tree, --source and --binary options will > actually do in terms of build or no build, where the build dependencies > will come from, and what test dependencies will be fulfilled and where > they will come from. So: --unbuilt-tree and --dsc do the same thing: they, by default: * build the tree * use the binaries produced to satisfy any build-dependencies for sources further on the command line * use the binaries produced to satisfy any dependencies for tests further on the command line * run any applicable tests in that source package It is possible to individually control these uses to which the tree is put, though: If --no-built-binaries, or --built-binaries-filter, or --binaries (or --binaries-forbuilds or --binaries-fortests) is specified, then the binaries aren't used for some of those purposes. If --sources-no-tests is used, that source package's tests are not run. The relevant --*binaries* options are all the ones which precede a particular --unbuilt-tree or --dsc, with later options of the same kind overriding earlier ones. I think, but am not sure, that there is an optimisation: if you specify that the binaries from the source should not be used, and the package's tests don't require the built source tree, then perhaps adt-run won't build the source at all - since nothing needs it (and you presumably weren't using adt-run for an archive rebuild test). --binary specifies just a binary package to be used for tests which appear subsequently on the adt-run command line. It will be used (by default) to satisfy dependencies. --binary is subject to the effects of preceding --binaries= and --binaries-forbuilds= and --binaries-fortests= options. So if you say --binaries=install --binary foo.deb --binaries=auto [more stuff] then foo.deb will be unconditionally installed while the tests specified by [more stuff] take place. --built-tree specifies some tests to be run, but does not provide any binaries. Another way to look at it is for me to explain the implementation of the option/argument processor: * --built-binaries-filter sets a set of patterns. The set of patterns is applied to subsequent --unbuilt-tree and --source options. Any packages produced by the build matching the filter are treated as if they had been specified explicitly with --binary at the same place in the command line as the source package dide. * --binaries[-forbuilds|-fortests]=ignore|auto|install: There are two tristate variables, one for --binaries-forbuilds and one for --binaries-fortests. Saying just --binaries= sets both. --binaries-forbuilds applies when we are doing builds, and --binaries-fortests when we are doing tests. The tristates apply to all subsequently encountered binary packages (i.e. .debs on the command line, and binaries (except those filtered out) produced by sources on the command line. This is mostly done with the variable "arghandling" in parse_args. Every time it is modified, it is copied. Every time an actual action argument is supplied, the current arghandling is saved away. Does that help ? Catch me on irc if you have more questions (Diziet on oftc/freenode.) Ian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1175557 Title: adt-run fulfills dependencies with --built-tree contrary to the manpage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1175557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1175557] Re: adt-run fulfills dependencies with --built-tree contrary to the manpage
Martin Pitt writes ("[Bug 1175557] Re: adt-run fulfills dependencies with --built-tree contrary to the manpage"): > oh, you are listening here, nice! Sure. To be honest I'm not doing very much but I can try to clear up any misunderstandings and help explain the tangles in my code... > I'd appreciate if you could review > http://anonscm.debian.org/gitweb/?p=autopkgtest/autopkgtest.git;a=commitdiff;h=0dcce04 > ; I'm fairly sure that this reflects how adt-run currently works, and > that it mostly makes sense that way. If you think the behaviour is > actually wrong, and the previous manpage was right, please let me know. Your new text is generally right. The --apt-source option postdates me so I don't know that your text for that is right. The old text for --built-tree is wrong. | .TP | .BR -B " | " --no-built-binaries |-Specifies that all built binaries should be ignored completely; |-equivalent to |+Specifies that all built binaries from source packages should be ignored |+completely, and dependencies are satisfied with packages from the archive. Note |+that packages still get built if a test requires |+\fBbuild-needed\fR. Equivalent to Of course it isn't quite right to say "from the archive"; they might come from *.deb command line arguments too. Regards, Ian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1175557 Title: adt-run fulfills dependencies with --built-tree contrary to the manpage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1175557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1175557] Re: adt-run fulfills dependencies with --built-tree contrary to the manpage
Martin Pitt writes ("[Bug 1175557] Re: adt-run fulfills dependencies with --built-tree contrary to the manpage"): > I'm trying to understand how these arguments actually work, keeping my > notes here. Probably not interesting to anyone else, but maybe for me > for future reference. Do you want me to try to explain how I think they're supposed to work ? Ian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1175557 Title: adt-run fulfills dependencies with --built-tree contrary to the manpage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1175557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1212208] Re: quilt patches are not applied during --unbuilt-tree build
Martin Pitt writes ("[Bug 1212208] Re: quilt patches are not applied during --unbuilt-tree build"): > ** Changed in: autopkgtest (Ubuntu) >Status: New => Triaged Certainly applying quilt patches by default is entirely wrong. What if you want to use adt-run to see whether a particular patch is still needed, for example ? I guess it would be fine to warn about unapplied patches. Ian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1212208 Title: quilt patches are not applied during --unbuilt-tree build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1212208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1169604] Re: set permission to og+rx on working directory to allow test execution by any user
Jean-Baptiste Lallement writes ("[Bug 1169604] Re: set permission to og+rx on working directory to allow test execution by any user"): > The case I'm trying to address, is a test running as root to prepare the > test environment (for example start/stop services) then drop privileges > to another user with 'su' to run the actual testsuite. The current metadata doesn't support ordering or mutual dependencies between tests, so you have other problems too I think. But in your particular case, you can have your prep make a temporary directory owned by the user. Ian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1169604 Title: set permission to og+rx on working directory to allow test execution by any user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1169604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1169604] [NEW] set permission to og+rx on working directory to allow test execution by any user
Jean-Baptiste Lallement writes ("[Bug 1169604] [NEW] set permission to og+rx on working directory to allow test execution by any user"): > Public bug reported: > > adt-run creates a working directory with mktemp in /tmp/ e.g /tmp/tmp.XX > which is set to the default permissions u+rwx. > This makes impossible to execute tests with another user than the user who > started the tests or root. > > permissions should be changed to og+rx for this directory. Simply changing the permissions is not correct. Tests might contain confidential information, and the test runner might be running on a system which is doing other work. If it is necessary for a test to share information between multiple non-root users, it should create a suitable Unix group, or something. What are you trying to do ? Ian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1169604 Title: set permission to og+rx on working directory to allow test execution by any user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1169604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107023] Re: cfdisk complains about auto-resize generated setup
Phillip Susi writes ("[Bug 107023] Re: cfdisk complains about auto-resize generated setup"): > This is easy to reproduce by simply creating two logical partitions out > of order. This is an error in cfdisk not parted. > > ** Changed in: parted (Ubuntu) >Status: Triaged => Invalid I think the status in util-linux should therefore be Confirmed ? Colin has posted the offending bit of code. Maybe it needs to be simply removed, but someone will have to look at the rest of the cfdisk code to check it doesn't rely on this inaccurate assumption. I suspect it probably does. Ian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/107023 Title: cfdisk complains about auto-resize generated setup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/parted/+bug/107023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 865515] Re: virtual machines should not have nat on servers
Serge Hallyn writes ("[Bug 865515] Re: virtual machines should not have nat on servers"): > How would you suggest configuring out of the box on install for a > server? eth0 should be bridged. Specifically, for a vm host, the primary network interface (by which I mean the one used for the original installation, and set up automatically by the installer) should be enslaved to a new bridge. > I don't believe it is reasonable to assume we can bridge eth0 and have > that be the right thing to do. On a server VM host system with one in-use network interface, it is exactly the right thing to do. > Perhaps we could find the nic for the default route, but that could > be fragile especially in esoteric setups. If there are multiple in-service network interfaces then obviously we don't know what to do. In that case the software shouldn't do anything automatically. But that's OK because if there are multiple in-service network interfaces on a server, the admin has _already_ done some manual setup. So they will know how they want to organise the VM networking and it is fine to expect them to tell the VM system what to do. Specifically, in that case it is fine for the VM setup to ask them "please tell me which bridge to use". > Also, adding a NATed bridge is safe to do at any time, but taking the > primary nic and turning it into a bridge during upgrade is not safe. The question of what to do during upgrade, and what to do during install, are somewhat different. > Is there an alternative? > > ** Changed in: libvirt (Ubuntu) >Status: Confirmed => Incomplete Can you please stop changing the status of this bug ? Ian. ** Changed in: libvirt (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/865515 Title: virtual machines should not have nat on servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/865515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 865515] Re: virtual machines should not have nat on servers
Serge Hallyn writes ("[Bug 865515] Re: virtual machines should not have nat on servers"): > Agreed the default isn't ideal for servers, but I'm not convinced there > is a good wya to set up a works-everywhere ideal solution for servers. > I would assume that any site which cares enough about the network > performance to object to a NATed bridge would have serveral NICs, some > perhaps bonded - and leaving configuration to the admin is best. The problem with NAT is not performance, it is the unwanted address translation. In a server setup, you want a simple bridge. The individual VMs will be allocated their own real addresses (either by the local dhcp server, or statically) just as you would with a physical server. Ian. ** Changed in: libvirt (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/865515 Title: virtual machines should not have nat on servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/865515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 33832] Re: Get browser startpage translated
** Changed in: mozilla-firefox-locale-all (Ubuntu) Assignee: Ian Jackson (ijackson) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/33832 Title: Get browser startpage translated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozilla-firefox-locale-all/+bug/33832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 802626] lvm hangs: watershed and environment
Another possible cause of problems is that, due to the use of watershed, DM_COOKIE is not passed to the actual invocation of vgchange, or vgchange is run fewer times than expected. watershed considers two identical command lines with different environments coalescable. So if you run watershed vgchange -a y & DM_COOKIE=A watershed vgchange -a y & DM_COOKIE=B watershed vgchange -a y & vgchange may see any subset (by DM_COOKIE setting) of the calls. I don't know the innards of the lvm/udev plumbing well enough to know if this is going to be a problem, but from the descriptions in this bug it seems it might be. Of course simply removing the use of watershed, or manually putting the cookie in the watershed command-id (or on the watershed command line, for the same effect), will with the current udev rules result in lots of serialised invocations of vgscan. Ian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/802626 Title: vgchange may deadlock in initramfs when VG present that's not used for rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/802626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 803488] Re: [Oneiric] Load xen_blkback and xen_netback on startup
Dave Walker writes ("[Bug 803488] Re: [Oneiric] Load xen_blkback and xen_netback on startup"): > I think I was confused on what the proposed Oneiric resolution was. I > thought it was being suggested that adding the two modprobes to the init > script would be a suitable resolution. > > Looking at the current archive package for modprobes it contains: > ./debian/xen-utils-common.xend.init: modprobe xenfs 2>/dev/null > ./debian/xen-utils-common.xend.init: modprobe xen-evtchn 2>/dev/null > > Therefore the requirement is to add xen_blkback & xen_netback (and drop > it for P-Series). Yes, that was my understanding. I'm confident that this will be a safe fix. It will only affect people who have xen-utils-common installed, of course, and those people are presumably intending to run Xen and do need those modules loaded. Ian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/803488 Title: [Oneiric] Load xen_blkback and xen_netback on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen-common/+bug/803488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 865502] Re: virtualisation host task does not install xen
Dave Walker writes ("[Bug 865502] Re: virtualisation host task does not install xen"): > Thanks for raising this bug.. I think it's reasonable to have a Xen UDS > session for P-series, which this could fit nicely into. I'm going to > mark this bug Invalid, but I certainly agree that Xen discoverability > needs to be improved. The UDS session should address this. At the very least the description of this task needs to be improved, then, to explain that it doesn't include Xen. In particular, an effect of selecting this option is to install libvirt which then has a detrimental effect on the default networking behaviour of Xen guests (LP#865515). Xen server admins should be _discouraged_ from installing this task, because doing so brings them into the scope of 865515. Ian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/865502 Title: virtualisation host task does not install xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-virt/+bug/865502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 865515] Re: virtual machines should not have nat on servers
Dave Walker writes ("[Bug 865515] Re: virtual machines should not have nat on servers"): > @Ian, If i understand the bug report correctly, this would seem to be a > generic bug regarding the default networking option setup as part of > libvirt. If this is the case, I agree it's not a great ideal for > servers - but also not an unreasonable default for the platform as a > whole use case. I agree with this. But the default should be different for servers and desktops/laptops. > I haven't checked for other virtulisation methods, but I imagine it is > similar. It is easy enough to provide a chosen networking model, so I'm > not fully convinced this is a valid bug. The existence of virbr0 convinces the Xen startup script, in the default configuration, not to do its own networking arrangements. Instead, since there is already a bridge, it causes all the VMs to use it, on the principle that if there is a bridge it should probably be used. Ian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/865515 Title: virtual machines should not have nat on servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/865515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 803488] Re: [Oneiric] Load xen_blkback and xen_netback on startup
Dave Walker writes ("[Bug 803488] Re: [Oneiric] Load xen_blkback and xen_netback on startup"): > ** Changed in: xen-common (Ubuntu Oneiric) >Importance: Wishlist => Medium > > ** Changed in: xen-common (Ubuntu Oneiric) > Assignee: (unassigned) => Dave Walker (davewalker) > > ** Changed in: xen-common (Ubuntu Oneiric) > Milestone: None => ubuntu-11.10 > > ** Tags added: server-o-rs Thanks a lot! Ian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/803488 Title: [Oneiric] Load xen_blkback and xen_netback on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen-common/+bug/803488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 803488] Re: [Oneiric] Load xen_blkback and xen_netback on startup
I will see about getting this bug escalated. I think it should be fixed for oneiric and the fix is trivial and low-risk. ** Changed in: xen-common (Ubuntu) Status: Triaged => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/803488 Title: [Oneiric] Load xen_blkback and xen_netback on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen-common/+bug/803488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 803488] Re: [Oneiric] Load xen_blkback and xen_netback on startup
For oneiric, this should be fixed in the xend init script in the xen- utils-common package, not in the xen-common package (I'm not sure what that is). The ultimate fix is in the kernel, which should do this automatically. That's commit 149bb2fab547253e6359e76f1b86b95247110e68 in the kernel git tree. So an alternative fix for oneiric is to backport that. (Which may also involve backporting cc85e93342c030f8ba07f572afa159ec4518231f.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/803488 Title: [Oneiric] Load xen_blkback and xen_netback on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen-common/+bug/803488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 865515] [NEW] virtual machines should not have nat on servers
Public bug reported: When installing a machine which is to be a VM host, it is necessary to make arrangements for the networking for the VMs. By default at the moment this is done by having libvirt create a "virbr0" bridge. The physical network interface is not enslaved to this bridge. Instead, all of the VM's traffic is routed, and natted, through the host. This is appropriate for a laptop and perhaps for some desktops. It's definitely not appropriate for servers. For servers, the physical interface should be enslaved to the bridge; the networking parameters in /etc/network/interfaces should be applied to the bridge, and VMs should speak directly (ie, bridged) to the local LAN. (By default.) Ideally this should be done by having the bridge be set up by ifup ie configured in /etc/network/interfaces. Apologies for not knowing exactly the right package for this bug report. ** Affects: ubuntu-virt (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/865515 Title: virtual machines should not have nat on servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-virt/+bug/865515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 865502] [NEW] virtualisation host task does not install xen
Public bug reported: When installing oneiric with the "virtualisation host" task, the Xen hypervisor and tools (perhaps, via the xen-hypervisor metapackage) should be automatically installed as well as the kvm (libvirt). ** Affects: ubuntu-virt (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/865502 Title: virtualisation host task does not install xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-virt/+bug/865502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 125017] Re: change defaults for dialup default route and nameservers
Pedro Villavicencio writes ("[Bug 125017] Re: change defaults for dialup default route and nameservers"): > Thanks for the report Ian Jackson , It has been a long time without any > comment or a duplicate in this bug report and It is possible that the > bug has been fixed. May you please try to reproduce it with the latest > Stable Release of Ubuntu the Natty Narwhal and add the respective > comments to the report? You can learn how to get that release at > http://www.ubuntu.com/download . Thanks again and we appreciate your > help. I don't have time to try to repro this problem and I don't have an Ubuntu install to hand to see if it is still there. However, anyone with an Ubuntu install should be able to trivially see whether the bug still exists. Ian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/125017 Title: change defaults for dialup default route and nameservers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/125017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54925] Re: ping provides vague message `Packet filtered'
Josh writes ("[Bug 54925] Re: ping provides vague message `Packet filtered'"): > Ping only knows that the packet was filtered, it doesn't know why and it > is not Ping's job to figure out why the packet was filtered. You are entirely wrong. ping has the complete ICMP unreachable packet, with the reason code, as my tcpdump demonstrates. Please also read the references I gave. Ian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/54925 Title: ping provides vague message `Packet filtered' -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 678201] Re: nautlius lockup with jpg-named svgs referring to svgs
** Attachment added: "Tarball of jpg and svgs for repro" https://bugs.launchpad.net/bugs/678201/+attachment/1740463/+files/iwj.tar -- nautlius lockup with jpg-named svgs referring to svgs https://bugs.launchpad.net/bugs/678201 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 678201] [NEW] nautlius lockup with jpg-named svgs referring to svgs
Public bug reported: Binary package hint: nautilus To reproduce: 1. Create a directory /home/ceb/Desktop/iwj 2. Put the files from the attached tarball into it 3. Open the directory in Nautilus 4. Double-click on outline3.jpg Observed behaviour: nautilus locks up; this window and all other file manager windows become unresponsive. Recovery is possible by running "killall nautilus" in a terminal window. Expected behaviour: the file is opened with image viewer. Note that outline[23].jpg are actually svgs. I don't know whether that is related to the problem. Bugs 305546 and 409409 seem to be related to this one. I doubt that nautilus itself is actually at fault. Here are the versions of librsvg: cla...@felix:~/Desktop/iwj$ dpkg -l '*rsvg*' Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Description +++--- ii librsvg2-2 2.26.3-0ubuntu1 SAX-based renderer library for SVG files (runtim un librsvg2-bin(no description available) ii librsvg2-common 2.26.3-0ubuntu1 SAX-based renderer library for SVG files (extra ii librsvg2-dbg 2.26.3-0ubuntu1 SAX-based renderer library for SVG files (debug) un librsvg2.0-cil (no description available) ii python-rsvg 2.30.0-0ubuntu1 Python bindings for the RSVG library cla...@felix:~/Desktop/iwj$ ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: nautilus 1:2.30.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7 Uname: Linux 2.6.32-25-generic i686 NonfreeKernelModules: wl Architecture: i386 Date: Sun Nov 21 17:33:42 2010 ProcEnviron: LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: nautilus ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- nautlius lockup with jpg-named svgs referring to svgs https://bugs.launchpad.net/bugs/678201 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 521765] [NEW] update-manager silently ignores HTTP 403 on meta-release
Public bug reported: Binary package hint: update-manager I was attempting to use update-manager to upgrade a hardy desktop i386 install to intrepid. We enabled "show updates to normal releases" and did "check for updates" but no new release was advertised. On checking the log on the squid web cache on the local LAN to see what update-manager was trying to download, I saw this: 1266165386.331 24 172.18.45.45 TCP_DENIED/403 1584 GET http://changelogs.ubuntu.com/meta-release - NONE/- text/html Ie, the a mistake in my proxy configuration was preventing update- manager from fetching the meta-release file (although the ordinary upgrade files were fine). The bug I am reporting here is that update-manager should have complained, with an error message of some kind, about the 403 HTTP error fetching the meta-release file. The user needs to know the difference between "there is no new release available" and "the update system is broken". Steps to reproduce: * install squid on a convenient machine on the LAN * configure squid to deny requests to changelogs.ubuntu.com * install hardy, configuring it to use a squid proxy * run update-manager from the command line or menu * say "check for updates" * observe that the upgrade to Intrepid is not offered and no error message is displayed ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New -- update-manager silently ignores HTTP 403 on meta-release https://bugs.launchpad.net/bugs/521765 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 145247] Re: manual partitoning resize lvm lv does not work
There is no reason to think that this bug is not also present in current Ubuntu releases. I don't have the facilities for reproducing it here right now (I'm at Debconf) but the information I provided should be sufficient to either reproduce (and hence confirm) the bug, or to demonstrate that it has been fixed. ** Changed in: partman-lvm (Ubuntu) Status: Incomplete => New -- manual partitoning resize lvm lv does not work https://bugs.launchpad.net/bugs/145247 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 145225] Re: searches for codecs when none can be found and not necessary
There is no reason to think that this bug is not also present in current Ubuntu releases. I don't have the facilities for reproducing it here right now (I'm at Debconf) but the information I provided should be sufficient to either reproduce (and hence confirm) the bug, or to demonstrate that it has been fixed. ** Changed in: gnash (Ubuntu) Status: Incomplete => New -- searches for codecs when none can be found and not necessary https://bugs.launchpad.net/bugs/145225 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 107032] Re: iso image search repetition unavoidable (expert mode)
There is no reason to think that this bug is not also present in current Ubuntu releases. I don't have the facilities for reproducing it here right now (I'm at Debconf) but the information I provided should be sufficient to either reproduce (and hence confirm) the bug, or to demonstrate that it has been fixed. ** Changed in: iso-scan (Ubuntu) Status: Incomplete => New -- iso image search repetition unavoidable (expert mode) https://bugs.launchpad.net/bugs/107032 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 107028] Re: reinstall grub option makes other installs unbootable
There is no reason to think that this bug does not exist in current Ubuntu releases. As I understand it the design has not changed, and the problem is caused by the design. ** Changed in: rescue (Ubuntu) Status: Incomplete => Confirmed -- reinstall grub option makes other installs unbootable https://bugs.launchpad.net/bugs/107028 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 151325] Re: scrollback gesture should be disabled
Martin Mai writes ("[Bug 151325] Re: scrollback gesture should be disabled"): > Thank you for taking the time to report this bug and helping to make > Ubuntu better. You reported this bug a while ago and there hasn't been > any activity in it recently. We were wondering if this is still an issue > for you. Can you try with the latest Ubuntu release? Thanks in advance. I don't have an Ubuntu install to hand right now as I write this email but this should be easy enough to reproduce. Ian. -- scrollback gesture should be disabled https://bugs.launchpad.net/bugs/151325 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 64490] Re: Assertion `dependtry <= 4' failed.
*** This bug is a duplicate of bug 46530 *** https://bugs.launchpad.net/bugs/46530 Matt Zimmerman writes ("[Bug 64490] Re: Assertion `dependtry <= 4' failed."): > *** This bug is a duplicate of bug 46530 *** > https://bugs.launchpad.net/bugs/46530 It is not normally correct to mark bugs as duplicate in this case, simply because it's the same assertion that failed. There may be many causes for this: there is a wide opportunity for any errors in the dependency management code to result in this assertion. The correct approach to debugging it is: * Get the /var/lib/dpkg from the offending system. Normally when this bug triggers, running dpkg --configure --pending with that /var/lib/dpkg will reproduce the bug. * Check whether the version in Debian sid has the same bug. There have been several such bugs fixed in sid recently. * If the version in Debian _does_ have the same bug please file the bug in Debian too and also bring it to my attention by emailing me at [EMAIL PROTECTED] I will prepare a fix. Ian. -- Assertion `dependtry <= 4' failed. https://bugs.launchpad.net/bugs/64490 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 41624] Re: Replaying journals of other OS's filesystems, by mounting them, is unsafe
Phillip Susi writes ("[Bug 41624] Re: Replaying journals of other OS's filesystems, by mounting them, is unsafe"): > Which kernel you are using does not really matter because the linux > kernel developers consider this to be working as intended. I have tried > arguing with the on the LKML a few times with no success. They seem to > think that the read only mount flag does not mean "do not write to this > disk" but rather "do not allow files to be opened for write access". Phillip is correct. > If we want this fixed, we're going to have to fix it ourselves it looks > like. I think we should do so. Just this week I was helping someone recover a machine which was already damaged at the time and was made worse when they typed mount -o ro /dev/mapper/volumegroup-logicalvolume-real /mnt which causes ext3 to write the journal back into the snapshotted volume bypassing the LVM system. You can say "don't do that then" but mount -o ro is exactly what every administrator reaches for in time of trouble, and they expect it to do no harm. Ian. -- Replaying journals of other OS's filesystems, by mounting them, is unsafe https://bugs.launchpad.net/bugs/41624 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 104553] Re: upgrade failed when fontconfig cache dirs are newer than system date
I just had exactly the same experience as jeroenvrp, and thanks to finding this report I was able to work around the problem. It's clear that fontconfig fails to deal properly with font directory timestamps in the future, so I'm setting this bug to Confirmed. Also, the error message is deeply unhelpful. ** Changed in: fontconfig (Ubuntu) Status: Incomplete => Confirmed -- upgrade failed when fontconfig cache dirs are newer than system date https://bugs.launchpad.net/bugs/104553 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 2993] Re: Profile Screen does not come up on First Launch of Firefox
** Changed in: firefox (Ubuntu) Assignee: Ian Jackson (ijackson) => (unassigned) -- Profile Screen does not come up on First Launch of Firefox https://bugs.launchpad.net/bugs/2993 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 31746] Re: Impossible to use multiple profiles at the same time
** Changed in: firefox Assignee: Ian Jackson (ijackson) => (unassigned) -- Impossible to use multiple profiles at the same time https://bugs.launchpad.net/bugs/31746 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 132473] Re: [gutsy] network-manager i have to manually configure wpa/2 enterprise every time to connect
** Changed in: network-manager (Ubuntu) Assignee: Ubuntu Core Development Team (ubuntu-core-dev) => (unassigned) -- [gutsy] network-manager i have to manually configure wpa/2 enterprise every time to connect https://bugs.launchpad.net/bugs/132473 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 26037] Re: Download manager empty
** Changed in: firefox (Ubuntu) Assignee: Ian Jackson (ijackson) => (unassigned) -- Download manager empty https://bugs.launchpad.net/bugs/26037 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 156972] autopkgtest gutsy ghostscript-doc amd64: erroneous package!
Public bug reported: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 affects /ubuntu/ghostscript importance high # version 8.61.dfsg.1~svn8187-0ubuntu3 Test executed for: gutsy binary-amd64 ghostscript-doc Outcome: erroneous package! blame: arg:tmp/ghostscript-doc/src/ghostscript-doc.deb deb:ghostscript-doc ghostscript-doc badpkg: installation of ghostscript-doc failed, exit code 100 quitting: erroneous package: installation of ghostscript-doc failed, exit code 100 erroneous package! This message is automatically generated by the autopkgtest package testing system. You are receiving it because: The test results appear to indicate a problem with the package and reports for package maintainers for gutsy are being directed to [EMAIL PROTECTED] The top and tail of the test log, which is intended to be sufficient to diagnose most failures, can be found below. However, in case this is not sufficient, a complete log can be found along with output files, saved temporary files, and so on, at: http://autopkgtest.ubuntu.com/autopkgtest-output/ The test environment is an amd64 Xen guest with limited amounts of memory. The relevant dependencies are installed for each test but very few other packages. Most autopkgtest reports are FTBFS problems. Please forgive this bug report if the problem is due to archive skew; in that case you've just been unlucky with the timing. Feel free to close the bug if the skew has been fixed, or will be fixed soon. If you have any questions about this service please contact me at: Ian Jackson <[EMAIL PROTECTED]> Regards, Ian - -8<- ++ fetching http://archive.ubuntu.com/ubuntu/dists/gutsy/main/binary-amd64/Packages.gz ++ ++ selecting ++ selected ghostscript-doc (age , score 9494700) Package: ghostscript-doc Priority: optional Section: text Installed-Size: 8404 Maintainer: Ubuntu Core Developers <[EMAIL PROTECTED]> Original-Maintainer: Masayuki Hatta (mhatta) <[EMAIL PROTECTED]> Architecture: all Source: ghostscript Version: 8.61.dfsg.1~svn8187-0ubuntu3 Depends: ghostscript (>= 8.60) Conflicts: ghostscript (<< 8.60) Filename: pool/main/g/ghostscript/ghostscript-doc_8.61.dfsg.1~svn8187-0ubuntu3_all.deb Size: 2641772 MD5sum: 9d4fab4a72da7dc8b2d445147e9fed0c SHA1: 240d565f63abd902b89a841dc3edde52910baadf SHA256: 4a9004722f47cdff9777f7600261660d4cf39b56c2b0613d90f58ea75617dd2d Description: The GPL Ghostscript PostScript/PDF interpreter - Documentation Ghostscript is used for PostScript/PDF preview and printing. Usually as a back-end to a program such as ghostview, it can display PostScript and PDF documents in an X11 environment. . The Ghostscript home page is at http://www.ghostscript.com/ . This package contains the documentation of Ghostscript. As this documentation is only interesting for printer driver developers or advanced users, it is in this separate package which can be left out in space-restricted installations, like for example live CDs. Bugs: mailto:[EMAIL PROTECTED] Origin: Ubuntu ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/g/ghostscript/ghostscript-doc_8.61.dfsg.1~svn8187-0ubuntu3_all.deb ++ ++ starting test ++ + adt-run --tmp-dir tmp/ghostscript-doc/tmp --output-dir tmp/ghostscript-doc/out --log-file tmp/ghostscript-doc/log --summary tmp/_summary --built-binaries-filter=__ --binaries=install --binary tmp/ghostscript-doc/src/ghostscript-doc.deb --instantiate --- adt-virt-xenlvm --userv --distro=gutsy -- adt-run: trace: ** init adt-run: trace: ** start adt-run: trace: $ vserver: adt-virt-xenlvm --userv --distro=gutsy -- File descriptor 6 left open File descriptor 7 left open adt-run: trace: starting adt-run: trace: ** open, scratch=None File descriptor 6 left open File descriptor 11 left open File descriptor 6 left open File descriptor 11 left open adt-run: trace: * initialising adt-run: trace: * no key generation needed adt-run: trace: * reset adt-run: trace: builds ... adt-run: trace: deb deb0 adt-run: trace: * register what=deb0 deb_forbuilds=install pkg=ghostscript-doc af=deb0-deb~tmp/ghostscript-doc/src/ghostscript-doc.deb:tmp/ghostscript-doc/src/ghostscript-doc.deb!|- adt-run: trace: instantiate instantiate1 adt-run: trace: builds done. adt-run: trace: * reset adt-run: trace: tests ... adt-run: trace: test deb deb0 adt-run: trace: * register what=deb0 deb_fortests=install pkg=ghostscript-doc af=deb0-deb~tmp/ghostscript-doc/src/ghostscript-doc.deb:tmp/ghostscript-doc/src/ghostscript-doc.deb!|- adt-run: trace: test instantiate instantiate1 adt-run: trace: ** reset ** File descriptor 6 left open File descriptor 11 left open File descriptor 6 left open File descriptor 11 left open adt-r
[Bug 156971] autopkgtest gutsy ghostscript: erroneous package!
Public bug reported: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 affects /ubuntu/ghostscript importance high # version 8.61.dfsg.1~svn8187-0ubuntu3 Test executed for: gutsy source ghostscript Outcome: erroneous package! blame: arg:tmp/ghostscript/src/ghostscript_8.61.dfsg.1~svn8187-0ubuntu3.dsc dsc:ghostscript badpkg: build-depends install failed, exit code 1 quitting: erroneous package: build-depends install failed, exit code 1 erroneous package! This message is automatically generated by the autopkgtest package testing system. You are receiving it because: The test results appear to indicate a problem with the package and reports for package maintainers for gutsy are being directed to [EMAIL PROTECTED] The top and tail of the test log, which is intended to be sufficient to diagnose most failures, can be found below. However, in case this is not sufficient, a complete log can be found along with output files, saved temporary files, and so on, at: http://autopkgtest.ubuntu.com/autopkgtest-output/ The test environment is an amd64 Xen guest with limited amounts of memory. The relevant dependencies are installed for each test but very few other packages. Most autopkgtest reports are FTBFS problems. Please forgive this bug report if the problem is due to archive skew; in that case you've just been unlucky with the timing. Feel free to close the bug if the skew has been fixed, or will be fixed soon. If you have any questions about this service please contact me at: Ian Jackson <[EMAIL PROTECTED]> Regards, Ian - -8<- ++ fetching http://archive.ubuntu.com/ubuntu/dists/gutsy/main/source/Sources.gz ++ ++ selecting ++ selected ghostscript (age , score 12102520) Package: ghostscript Binary: ghostscript-x, ghostscript, gs-gpl, libgs8, gs, gs-common, libgs-esp-dev, gs-esp, libgs-dev, gs-esp-x, ghostscript-doc, gs-aladdin Version: 8.61.dfsg.1~svn8187-0ubuntu3 Priority: optional Section: text Maintainer: Ubuntu Core Developers <[EMAIL PROTECTED]> Original-Maintainer: Masayuki Hatta (mhatta) <[EMAIL PROTECTED]> Build-Depends: autoconf, automaken, debhelper (>= 4.0.0), dpatch, freeglut3-dev | libglut-dev, libjpeg-dev, libpaper-dev, libpng-dev, libz-dev, libxt-dev, libxext-dev, libx11-dev, gcc-3.4 [s390], libcupsys2-dev (>= 1.2), libcupsimage2-dev (>= 1.1.20final+rc1-4), libice-dev, libsm-dev, pkg-config, libfontconfig1-dev, cdbs Architecture: any Standards-Version: 3.7.2 Format: 1.0 Directory: pool/main/g/ghostscript Files: 8335f8e836d032d326d151d1d06ce659 1219 ghostscript_8.61.dfsg.1~svn8187-0ubuntu3.dsc 7eadf4f53880e96a3846bd318a19d4c6 11689594 ghostscript_8.61.dfsg.1~svn8187.orig.tar.gz f9194e44c01533cccfee608b4cc8e471 40900 ghostscript_8.61.dfsg.1~svn8187-0ubuntu3.diff.gz Uploaders: Torsten Landschoff <[EMAIL PROTECTED]>, Jonas Smedegaard <[EMAIL PROTECTED]> ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/g/ghostscript/ghostscript_8.61.dfsg.1~svn8187-0ubuntu3.dsc ++ ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/g/ghostscript/ghostscript_8.61.dfsg.1~svn8187.orig.tar.gz ++ ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/g/ghostscript/ghostscript_8.61.dfsg.1~svn8187-0ubuntu3.diff.gz ++ ++ starting test ++ + adt-run --tmp-dir tmp/ghostscript/tmp --output-dir tmp/ghostscript/out --log-file tmp/ghostscript/log --summary tmp/_summary --built-binaries-filter=__ --source tmp/ghostscript/src/ghostscript_8.61.dfsg.1~svn8187-0ubuntu3.dsc --- adt-virt-xenlvm --userv --distro=gutsy -- adt-run: trace: ** init adt-run: trace: ** start adt-run: trace: $ vserver: adt-virt-xenlvm --userv --distro=gutsy -- File descriptor 6 left open File descriptor 11 left open adt-run: trace: starting adt-run: trace: ** open, scratch=None File descriptor 6 left open File descriptor 11 left open File descriptor 6 left open File descriptor 11 left open adt-run: trace: * initialising adt-run: trace: * no key generation needed adt-run: trace: * reset adt-run: trace: builds ... adt-run: trace: dsc dsc0 adt-run: trace: * publish adt-run: trace: $ ftparchive: sh -ec
[Bug 156949] autopkgtest gutsy minicom: erroneous package!
Public bug reported: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 affects /ubuntu/minicom importance high # version 2.2-5 Test executed for: gutsy source minicom Outcome: erroneous package! blame: arg:tmp/minicom/src/minicom_2.2-5.dsc dsc:minicom badpkg: rules build failed with exit code 2 quitting: erroneous package: rules build failed with exit code 2 erroneous package! This message is automatically generated by the autopkgtest package testing system. You are receiving it because: The test results appear to indicate a problem with the package and reports for package maintainers for gutsy are being directed to [EMAIL PROTECTED] The top and tail of the test log, which is intended to be sufficient to diagnose most failures, can be found below. However, in case this is not sufficient, a complete log can be found along with output files, saved temporary files, and so on, at: http://autopkgtest.ubuntu.com/autopkgtest-output/ The test environment is an amd64 Xen guest with limited amounts of memory. The relevant dependencies are installed for each test but very few other packages. Most autopkgtest reports are FTBFS problems. Please forgive this bug report if the problem is due to archive skew; in that case you've just been unlucky with the timing. Feel free to close the bug if the skew has been fixed, or will be fixed soon. If you have any questions about this service please contact me at: Ian Jackson <[EMAIL PROTECTED]> Regards, Ian - -8<- ++ fetching http://archive.ubuntu.com/ubuntu/dists/gutsy/main/source/Sources.gz ++ ++ selecting ++ selected minicom (age , score 28453460) Package: minicom Binary: minicom Version: 2.2-5 Priority: optional Section: comm Maintainer: Martin A. Godisch <[EMAIL PROTECTED]> Build-Depends: autotools-dev, gettext, libncurses5-dev Architecture: any Standards-Version: 3.7.2 Format: 1.0 Directory: pool/main/m/minicom Files: 407ac83724514baf472b19a31d81f04b 624 minicom_2.2-5.dsc 13933c8777839f00e3730df23599dc93 720536 minicom_2.2.orig.tar.gz ff4c8e724162e01df47be5e43939dacc 12153 minicom_2.2-5.diff.gz Uploaders: Jordi Mallach <[EMAIL PROTECTED]> ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/m/minicom/minicom_2.2-5.dsc ++ ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/m/minicom/minicom_2.2.orig.tar.gz ++ ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/m/minicom/minicom_2.2-5.diff.gz ++ ++ starting test ++ + adt-run --tmp-dir tmp/minicom/tmp --output-dir tmp/minicom/out --log-file tmp/minicom/log --summary tmp/_summary --built-binaries-filter=__ --source tmp/minicom/src/minicom_2.2-5.dsc --- adt-virt-xenlvm --userv --distro=gutsy -- adt-run: trace: ** init adt-run: trace: ** start adt-run: trace: $ vserver: adt-virt-xenlvm --userv --distro=gutsy -- File descriptor 6 left open File descriptor 7 left open adt-run: trace: starting adt-run: trace: ** open, scratch=None File descriptor 6 left open File descriptor 11 left open File descriptor 6 left open File descriptor 11 left open adt-run: trace: * initialising adt-run: trace: * no key generation needed adt-run: trace: * reset adt-run: trace: builds ... adt-run: trace: dsc dsc0 adt-run: trace: * publish adt-run: trace: $ ftparchive: sh -ec
[Bug 156951] autopkgtest gutsy openjade: erroneous package!
Public bug reported: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 affects /ubuntu/openjade importance high # version 1.4devel1-18build1 Test executed for: gutsy source openjade Outcome: erroneous package! blame: arg:tmp/openjade/src/openjade_1.4devel1-18build1.dsc dsc:openjade badpkg: rules build failed with exit code 2 quitting: erroneous package: rules build failed with exit code 2 erroneous package! This message is automatically generated by the autopkgtest package testing system. You are receiving it because: The test results appear to indicate a problem with the package and reports for package maintainers for gutsy are being directed to [EMAIL PROTECTED] The top and tail of the test log, which is intended to be sufficient to diagnose most failures, can be found below. However, in case this is not sufficient, a complete log can be found along with output files, saved temporary files, and so on, at: http://autopkgtest.ubuntu.com/autopkgtest-output/ The test environment is an amd64 Xen guest with limited amounts of memory. The relevant dependencies are installed for each test but very few other packages. Most autopkgtest reports are FTBFS problems. Please forgive this bug report if the problem is due to archive skew; in that case you've just been unlucky with the timing. Feel free to close the bug if the skew has been fixed, or will be fixed soon. If you have any questions about this service please contact me at: Ian Jackson <[EMAIL PROTECTED]> Regards, Ian - -8<- ++ fetching http://archive.ubuntu.com/ubuntu/dists/gutsy/main/source/Sources.gz ++ ++ selecting ++ selected openjade (age , score 28450120) Package: openjade Binary: openjade, libostyle1c2, libostyle-dev Version: 1.4devel1-18build1 Priority: optional Section: text Maintainer: Neil Roeth <[EMAIL PROTECTED]> Build-Depends: libosp-dev (>= 1.5.1.0-2.1), debhelper (>= 4.1.75), autotools-dev, gettext, dh-buildinfo Architecture: any Standards-Version: 3.7.2 Format: 1.0 Directory: pool/main/o/openjade Files: b103e73076e85cd66a03daaae89584a5 685 openjade_1.4devel1-18build1.dsc 8cfeb179e6451a2b31e5efdb4b4be70a 676095 openjade_1.4devel1.orig.tar.gz 2b7aa0cf11cfb6abb5fcdae67d6998f3 641830 openjade_1.4devel1-18build1.diff.gz ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/o/openjade/openjade_1.4devel1-18build1.dsc ++ ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/o/openjade/openjade_1.4devel1.orig.tar.gz ++ ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/o/openjade/openjade_1.4devel1-18build1.diff.gz ++ ++ starting test ++ + adt-run --tmp-dir tmp/openjade/tmp --output-dir tmp/openjade/out --log-file tmp/openjade/log --summary tmp/_summary --built-binaries-filter=__ --source tmp/openjade/src/openjade_1.4devel1-18build1.dsc --- adt-virt-xenlvm --userv --distro=gutsy -- adt-run: trace: ** init adt-run: trace: ** start adt-run: trace: $ vserver: adt-virt-xenlvm --userv --distro=gutsy -- File descriptor 6 left open File descriptor 11 left open adt-run: trace: starting adt-run: trace: ** open, scratch=None File descriptor 6 left open File descriptor 11 left open File descriptor 6 left open File descriptor 11 left open adt-run: trace: * initialising adt-run: trace: * no key generation needed adt-run: trace: * reset adt-run: trace: builds ... adt-run: trace: dsc dsc0 adt-run: trace: * publish adt-run: trace: $ ftparchive: sh -ec
[Bug 156950] autopkgtest gutsy nant: erroneous package!
Public bug reported: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 affects /ubuntu/nant importance high # version 0.85-1 Test executed for: gutsy source nant Outcome: erroneous package! blame: arg:tmp/nant/src/nant_0.85-1.dsc dsc:nant badpkg: rules build failed with exit code 2 quitting: erroneous package: rules build failed with exit code 2 erroneous package! This message is automatically generated by the autopkgtest package testing system. You are receiving it because: The test results appear to indicate a problem with the package and reports for package maintainers for gutsy are being directed to [EMAIL PROTECTED] The top and tail of the test log, which is intended to be sufficient to diagnose most failures, can be found below. However, in case this is not sufficient, a complete log can be found along with output files, saved temporary files, and so on, at: http://autopkgtest.ubuntu.com/autopkgtest-output/ The test environment is an amd64 Xen guest with limited amounts of memory. The relevant dependencies are installed for each test but very few other packages. Most autopkgtest reports are FTBFS problems. Please forgive this bug report if the problem is due to archive skew; in that case you've just been unlucky with the timing. Feel free to close the bug if the skew has been fixed, or will be fixed soon. If you have any questions about this service please contact me at: Ian Jackson <[EMAIL PROTECTED]> Regards, Ian - -8<- ++ fetching http://archive.ubuntu.com/ubuntu/dists/gutsy/main/source/Sources.gz ++ ++ selecting ++ selected nant (age , score 28450870) Package: nant Binary: nant Version: 0.85-1 Priority: optional Section: devel Maintainer: Dave Beckett <[EMAIL PROTECTED]> Build-Depends: debhelper (>= 5) Build-Depends-Indep: mono-mcs (>= 1.1.6) | c-sharp-compiler, mono-gmcs, mono-gac, libmono-dev (>= 1.1.6), pkg-config, cli-common-dev (>= 0.4.4), dpatch, libnunit2.2-cil, libndoc-cil, libmono-winforms1.0-cil, libmono-winforms2.0-cil Architecture: all Standards-Version: 3.7.2 Format: 1.0 Directory: pool/main/n/nant Files: 77e1c792d2344e8c4eabf76213976993 774 nant_0.85-1.dsc 45ae065439b6cbc0e02051b855843f50 2130856 nant_0.85.orig.tar.gz 61f3ab411ef9e2cc841e4b7ff4e67d5b 4555 nant_0.85-1.diff.gz ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/n/nant/nant_0.85-1.dsc ++ ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/n/nant/nant_0.85.orig.tar.gz ++ ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/n/nant/nant_0.85-1.diff.gz ++ ++ starting test ++ + adt-run --tmp-dir tmp/nant/tmp --output-dir tmp/nant/out --log-file tmp/nant/log --summary tmp/_summary --built-binaries-filter=__ --source tmp/nant/src/nant_0.85-1.dsc --- adt-virt-xenlvm --userv --distro=gutsy -- adt-run: trace: ** init adt-run: trace: ** start adt-run: trace: $ vserver: adt-virt-xenlvm --userv --distro=gutsy -- File descriptor 6 left open File descriptor 7 left open adt-run: trace: starting adt-run: trace: ** open, scratch=None File descriptor 6 left open File descriptor 11 left open File descriptor 6 left open File descriptor 11 left open adt-run: trace: * initialising adt-run: trace: * no key generation needed adt-run: trace: * reset adt-run: trace: builds ... adt-run: trace: dsc dsc0 adt-run: trace: * publish adt-run: trace: $ ftparchive: sh -ec
[Bug 156952] autopkgtest gutsy linux32 amd64: erroneous package!
Public bug reported: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 affects /ubuntu/linux32 importance high # version 1-3build1 Test executed for: gutsy binary-amd64 linux32 Outcome: erroneous package! blame: arg:tmp/linux32/src/linux32.deb deb:linux32 linux32 badpkg: installation of linux32 failed, exit code 100 quitting: erroneous package: installation of linux32 failed, exit code 100 erroneous package! This message is automatically generated by the autopkgtest package testing system. You are receiving it because: The test results appear to indicate a problem with the package and reports for package maintainers for gutsy are being directed to [EMAIL PROTECTED] The top and tail of the test log, which is intended to be sufficient to diagnose most failures, can be found below. However, in case this is not sufficient, a complete log can be found along with output files, saved temporary files, and so on, at: http://autopkgtest.ubuntu.com/autopkgtest-output/ The test environment is an amd64 Xen guest with limited amounts of memory. The relevant dependencies are installed for each test but very few other packages. Most autopkgtest reports are FTBFS problems. Please forgive this bug report if the problem is due to archive skew; in that case you've just been unlucky with the timing. Feel free to close the bug if the skew has been fixed, or will be fixed soon. If you have any questions about this service please contact me at: Ian Jackson <[EMAIL PROTECTED]> Regards, Ian - -8<- ++ fetching http://archive.ubuntu.com/ubuntu/dists/gutsy/main/binary-amd64/Packages.gz ++ ++ selecting ++ selected linux32 (age , score 28794510) Package: linux32 Priority: extra Section: utils Installed-Size: 60 Maintainer: Ubuntu Core Developers <[EMAIL PROTECTED]> Original-Maintainer: Kurt Roeckx <[EMAIL PROTECTED]> Architecture: amd64 Version: 1-3build1 Depends: libc6 (>= 2.6-1) Filename: pool/main/l/linux32/linux32_1-3build1_amd64.deb Size: 5632 MD5sum: a4c9bfaa451986ba8518dc460572855e SHA1: fe855fbc6fb880f26c725ceceec8cf88683f3729 SHA256: 938d12fb72c51ff208b9b23daf56c4e827c34cee68addfc437f93c55e5f761c7 Description: Wrapper to set the execution domain the linux32 tools allows 64bit systems with support for 32 bit applications to set the personality to the 32 bit native type. . For instance, on an amd64 or ia64 machine, commands run with this wrapper will think the machine type is i686, as returned by uname -m. . On systems without support for the PER_LINUX_32 execution domain, this program has no effect. Bugs: mailto:[EMAIL PROTECTED] Origin: Ubuntu ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/l/linux32/linux32_1-3build1_amd64.deb ++ ++ starting test ++ + adt-run --tmp-dir tmp/linux32/tmp --output-dir tmp/linux32/out --log-file tmp/linux32/log --summary tmp/_summary --built-binaries-filter=__ --binaries=install --binary tmp/linux32/src/linux32.deb --instantiate --- adt-virt-xenlvm --userv --distro=gutsy -- adt-run: trace: ** init adt-run: trace: ** start adt-run: trace: $ vserver: adt-virt-xenlvm --userv --distro=gutsy -- File descriptor 6 left open File descriptor 7 left open adt-run: trace: starting adt-run: trace: ** open, scratch=None File descriptor 6 left open File descriptor 11 left open File descriptor 6 left open File descriptor 11 left open adt-run: trace: * initialising adt-run: trace: * no key generation needed adt-run: trace: * reset adt-run: trace: builds ... adt-run: trace: deb deb0 adt-run: trace: * register what=deb0 deb_forbuilds=install pkg=linux32 af=deb0-deb~tmp/linux32/src/linux32.deb:tmp/linux32/src/linux32.deb!|- adt-run: trace: instantiate instantiate1 adt-run: trace: builds done. adt-run: trace: * reset adt-run: trace: tests ... adt-run: trace: test deb deb0 adt-run: trace: * register what=deb0 deb_fortests=install pkg=linux32 af=deb0-deb~tmp/linux32/src/linux32.deb:tmp/linux32/src/linux32.deb!|- adt-run: trace: test instantiate instantiate1 adt-run: trace: ** reset ** File descriptor 6 left open File descriptor 11 left open File descriptor 6 left open File descriptor 11 left open adt-run: trace: * publish adt-run: trace: $ ftparchive: sh -ec
[Bug 156955] autopkgtest gutsy python-kde3: erroneous package!
Public bug reported: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 affects /ubuntu/python-kde3 importance high # version 3.16.0-0ubuntu14 Test executed for: gutsy source python-kde3 Outcome: erroneous package! blame: arg:tmp/python-kde3/src/python-kde3_3.16.0-0ubuntu14.dsc dsc:python-kde3 badpkg: rules build failed with exit code 2 quitting: erroneous package: rules build failed with exit code 2 erroneous package! This message is automatically generated by the autopkgtest package testing system. You are receiving it because: The test results appear to indicate a problem with the package and reports for package maintainers for gutsy are being directed to [EMAIL PROTECTED] The top and tail of the test log, which is intended to be sufficient to diagnose most failures, can be found below. However, in case this is not sufficient, a complete log can be found along with output files, saved temporary files, and so on, at: http://autopkgtest.ubuntu.com/autopkgtest-output/ The test environment is an amd64 Xen guest with limited amounts of memory. The relevant dependencies are installed for each test but very few other packages. Most autopkgtest reports are FTBFS problems. Please forgive this bug report if the problem is due to archive skew; in that case you've just been unlucky with the timing. Feel free to close the bug if the skew has been fixed, or will be fixed soon. If you have any questions about this service please contact me at: Ian Jackson <[EMAIL PROTECTED]> Regards, Ian - -8<- ++ fetching http://archive.ubuntu.com/ubuntu/dists/gutsy/main/source/Sources.gz ++ ++ selecting ++ selected python-kde3 (age , score 28432790) Package: python-kde3 Binary: python-kde3, python-kde3-dev, python-kde3-dbg, python-kde3-doc Version: 3.16.0-0ubuntu14 Priority: optional Section: python Maintainer: Ubuntu Core developers <[EMAIL PROTECTED]> Original-Maintainer: Ricardo Javier Cardenes Medina <[EMAIL PROTECTED]> Build-Depends: debhelper (>= 5.0.37.2), libqt3-mt-dev (>= 3:3.3.7-1ubuntu2), qt3-dev-tools (>= 3:3.1.1-2), qt3-apps-dev (>= 3:3.1.1-2), libqt3-compat-headers (>= 3:3.1.1-2), python-all-dev, python-all-dbg, sip4 (>= 4.7), python-sip4-dev (>= 4.5-0ubuntu2), python-qt3 (>= 3.17.3-1ubuntu1), python-qt3-dbg, python-qt-dev (>= 3.17.3-1ubuntu1), kdelibs4-dev (>= 4:3.5.6), python-central (>= 0.5.0), konsole (>= 4:3.5.6), dpatch Architecture: any Standards-Version: 3.7.2 Format: 1.0 Directory: pool/main/p/python-kde3 Files: cdd50cdb1a3a94e796c0dda9b8420f4a 1207 python-kde3_3.16.0-0ubuntu14.dsc 92fa0f7d6063dc2aad97d5302975ca76 1618988 python-kde3_3.16.0.orig.tar.gz 3ba13eb3e813041b57ecacba08098c64 15903 python-kde3_3.16.0-0ubuntu14.diff.gz Uploaders: Torsten Marek <[EMAIL PROTECTED]> Python-Version: all ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/p/python-kde3/python-kde3_3.16.0-0ubuntu14.dsc ++ ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/p/python-kde3/python-kde3_3.16.0.orig.tar.gz ++ ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/p/python-kde3/python-kde3_3.16.0-0ubuntu14.diff.gz ++ ++ starting test ++ + adt-run --tmp-dir tmp/python-kde3/tmp --output-dir tmp/python-kde3/out --log-file tmp/python-kde3/log --summary tmp/_summary --built-binaries-filter=__ --source tmp/python-kde3/src/python-kde3_3.16.0-0ubuntu14.dsc --- adt-virt-xenlvm --userv --distro=gutsy -- adt-run: trace: ** init adt-run: trace: ** start adt-run: trace: $ vserver: adt-virt-xenlvm --userv --distro=gutsy -- File descriptor 6 left open File descriptor 7 left open adt-run: trace: starting adt-run: trace: ** open, scratch=None File descriptor 6 left open File descriptor 11 left open File descriptor 6 left open File descriptor 11 left open adt-run: trace: * initialising adt-run: trace: * no key generation needed adt-run: trace: * reset adt-run: trace: builds ... adt-run: trace: dsc dsc0 adt-run: trace: * publish adt-run: trace: $ ftparchive: sh -ec
[Bug 156954] autopkgtest gutsy mdadm amd64: erroneous package!
Public bug reported: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 affects /ubuntu/mdadm importance high # version 2.6.2-1ubuntu2 Test executed for: gutsy binary-amd64 mdadm Outcome: erroneous package! blame: arg:tmp/mdadm/src/mdadm.deb deb:mdadm mdadm badpkg: installation of mdadm failed, exit code 100 quitting: erroneous package: installation of mdadm failed, exit code 100 erroneous package! This message is automatically generated by the autopkgtest package testing system. You are receiving it because: The test results appear to indicate a problem with the package and reports for package maintainers for gutsy are being directed to [EMAIL PROTECTED] The top and tail of the test log, which is intended to be sufficient to diagnose most failures, can be found below. However, in case this is not sufficient, a complete log can be found along with output files, saved temporary files, and so on, at: http://autopkgtest.ubuntu.com/autopkgtest-output/ The test environment is an amd64 Xen guest with limited amounts of memory. The relevant dependencies are installed for each test but very few other packages. Most autopkgtest reports are FTBFS problems. Please forgive this bug report if the problem is due to archive skew; in that case you've just been unlucky with the timing. Feel free to close the bug if the skew has been fixed, or will be fixed soon. If you have any questions about this service please contact me at: Ian Jackson <[EMAIL PROTECTED]> Regards, Ian - -8<- ++ fetching http://archive.ubuntu.com/ubuntu/dists/gutsy/main/binary-amd64/Packages.gz ++ ++ selecting ++ selected mdadm (age , score 28707120) Package: mdadm Priority: optional Section: admin Installed-Size: 608 Maintainer: Ubuntu Core Developers <[EMAIL PROTECTED]> Original-Maintainer: Debian mdadm maintainers <[EMAIL PROTECTED]> Architecture: amd64 Version: 2.6.2-1ubuntu2 Replaces: mdctl Depends: libc6 (>= 2.6), makedev, debconf (>= 0.5) | debconf-2.0, lsb-base (>= 3.1-6), udev (>= 113-0ubuntu1), initramfs-tools (>> 0.85eubuntu11), debconf (>= 1.4.72) Recommends: mail-transport-agent, module-init-tools Conflicts: mdctl (<< 0.7.2), raidtools2 (<< 1.00.3-12.1) Filename: pool/main/m/mdadm/mdadm_2.6.2-1ubuntu2_amd64.deb Size: 219412 MD5sum: 1560f4384cc8798b29cedd4ce2317293 SHA1: 5cff6db38b26ba1bef62ce3820a5ff8d8ac3cb49 SHA256: 570012717c6288c5837e0449e72b7cb2db33a8111be2c2e2649936ac0ff8383b Description: tool to administer Linux MD arrays (software RAID) mdadm is a program that can be used to create, manage, and monitor MD arrays (e.g. software RAID, multipath devices). . This package automatically configures mdadm to assemble arrays during the system startup process. If not needed, this functionally can be disabled. Bugs: mailto:[EMAIL PROTECTED] Origin: Ubuntu ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/m/mdadm/mdadm_2.6.2-1ubuntu2_amd64.deb ++ ++ starting test ++ + adt-run --tmp-dir tmp/mdadm/tmp --output-dir tmp/mdadm/out --log-file tmp/mdadm/log --summary tmp/_summary --built-binaries-filter=__ --binaries=install --binary tmp/mdadm/src/mdadm.deb --instantiate --- adt-virt-xenlvm --userv --distro=gutsy -- adt-run: trace: ** init adt-run: trace: ** start adt-run: trace: $ vserver: adt-virt-xenlvm --userv --distro=gutsy -- File descriptor 6 left open File descriptor 7 left open adt-run: trace: starting adt-run: trace: ** open, scratch=None File descriptor 6 left open File descriptor 11 left open File descriptor 6 left open File descriptor 11 left open adt-run: trace: * initialising adt-run: trace: * no key generation needed adt-run: trace: * reset adt-run: trace: builds ... adt-run: trace: deb deb0 adt-run: trace: * register what=deb0 deb_forbuilds=install pkg=mdadm af=deb0-deb~tmp/mdadm/src/mdadm.deb:tmp/mdadm/src/mdadm.deb!|- adt-run: trace: instantiate instantiate1 adt-run: trace: builds done. adt-run: trace: * reset adt-run: trace: tests ... adt-run: trace: test deb deb0 adt-run: trace: * register what=deb0 deb_fortests=install pkg=mdadm af=deb0-deb~tmp/mdadm/src/mdadm.deb:tmp/mdadm/src/mdadm.deb!|- adt-run: trace: test instantiate instantiate1 adt-run: trace: ** reset ** File descriptor 6 left open File descriptor 11 left open File descriptor 6 left open File descriptor 11 left open adt-run: trace: * publish adt-run: trace: $ ftparchive: sh -ec
[Bug 156953] autopkgtest gutsy pychecker: erroneous package!
Public bug reported: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 affects /ubuntu/pychecker importance high # version 0.8.17-3 Test executed for: gutsy source pychecker Outcome: erroneous package! blame: arg:tmp/pychecker/src/pychecker_0.8.17-3.dsc dsc:pychecker badpkg: rules build failed with exit code 2 quitting: erroneous package: rules build failed with exit code 2 erroneous package! This message is automatically generated by the autopkgtest package testing system. You are receiving it because: The test results appear to indicate a problem with the package and reports for package maintainers for gutsy are being directed to [EMAIL PROTECTED] The top and tail of the test log, which is intended to be sufficient to diagnose most failures, can be found below. However, in case this is not sufficient, a complete log can be found along with output files, saved temporary files, and so on, at: http://autopkgtest.ubuntu.com/autopkgtest-output/ The test environment is an amd64 Xen guest with limited amounts of memory. The relevant dependencies are installed for each test but very few other packages. Most autopkgtest reports are FTBFS problems. Please forgive this bug report if the problem is due to archive skew; in that case you've just been unlucky with the timing. Feel free to close the bug if the skew has been fixed, or will be fixed soon. If you have any questions about this service please contact me at: Ian Jackson <[EMAIL PROTECTED]> Regards, Ian - -8<- ++ fetching http://archive.ubuntu.com/ubuntu/dists/gutsy/main/source/Sources.gz ++ ++ selecting ++ selected pychecker (age , score 28433660) Package: pychecker Binary: pychecker Version: 0.8.17-3 Priority: optional Section: devel Maintainer: Kenneth J. Pronovici <[EMAIL PROTECTED]> Build-Depends: python-support (>= 0.3), debhelper (>= 5.0.37.2) Architecture: all Standards-Version: 3.7.2 Format: 1.0 Directory: pool/main/p/pychecker Files: c14f5499db2d94a5c038ea797cf0a7bc 610 pychecker_0.8.17-3.dsc 9d2a2d62b368ce503830f830a89bd230 130689 pychecker_0.8.17.orig.tar.gz 5f3d41097065b315477e7b7fd1360441 13056 pychecker_0.8.17-3.diff.gz ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/p/pychecker/pychecker_0.8.17-3.dsc ++ ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/p/pychecker/pychecker_0.8.17.orig.tar.gz ++ ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/p/pychecker/pychecker_0.8.17-3.diff.gz ++ ++ starting test ++ + adt-run --tmp-dir tmp/pychecker/tmp --output-dir tmp/pychecker/out --log-file tmp/pychecker/log --summary tmp/_summary --built-binaries-filter=__ --source tmp/pychecker/src/pychecker_0.8.17-3.dsc --- adt-virt-xenlvm --userv --distro=gutsy -- adt-run: trace: ** init adt-run: trace: ** start adt-run: trace: $ vserver: adt-virt-xenlvm --userv --distro=gutsy -- File descriptor 6 left open File descriptor 7 left open adt-run: trace: starting adt-run: trace: ** open, scratch=None File descriptor 6 left open File descriptor 11 left open File descriptor 6 left open File descriptor 11 left open adt-run: trace: * initialising adt-run: trace: * no key generation needed adt-run: trace: * reset adt-run: trace: builds ... adt-run: trace: dsc dsc0 adt-run: trace: * publish adt-run: trace: $ ftparchive: sh -ec
[Bug 156956] autopkgtest gutsy time: erroneous package!
Public bug reported: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 affects /ubuntu/time importance high # version 1.7-21build1 Test executed for: gutsy source time Outcome: erroneous package! blame: arg:tmp/time/src/time_1.7-21build1.dsc dsc:time badpkg: build-depends install failed, exit code 1 quitting: erroneous package: build-depends install failed, exit code 1 erroneous package! This message is automatically generated by the autopkgtest package testing system. You are receiving it because: The test results appear to indicate a problem with the package and reports for package maintainers for gutsy are being directed to [EMAIL PROTECTED] The top and tail of the test log, which is intended to be sufficient to diagnose most failures, can be found below. However, in case this is not sufficient, a complete log can be found along with output files, saved temporary files, and so on, at: http://autopkgtest.ubuntu.com/autopkgtest-output/ The test environment is an amd64 Xen guest with limited amounts of memory. The relevant dependencies are installed for each test but very few other packages. Most autopkgtest reports are FTBFS problems. Please forgive this bug report if the problem is due to archive skew; in that case you've just been unlucky with the timing. Feel free to close the bug if the skew has been fixed, or will be fixed soon. If you have any questions about this service please contact me at: Ian Jackson <[EMAIL PROTECTED]> Regards, Ian - -8<- ++ fetching http://archive.ubuntu.com/ubuntu/dists/gutsy/main/source/Sources.gz ++ ++ selecting ++ selected time (age , score 28394180) Package: time Binary: time Version: 1.7-21build1 Priority: standard Section: utils Maintainer: Tollef Fog Heen <[EMAIL PROTECTED]> Build-Depends: debhelper (>> 4.1.0), texi2html, texinfo, automaken, cdbs Architecture: any Standards-Version: 3.6.1.0 Format: 1.0 Directory: pool/main/t/time Files: 9a6d72508626b5d7ea8575dbbd2f63db 599 time_1.7-21build1.dsc e38d2b8b34b1ca259cf7b053caac32b3 103066 time_1.7.orig.tar.gz 65c75608b4a7da4a438edef86df8ddb0 90205 time_1.7-21build1.diff.gz ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/t/time/time_1.7-21build1.dsc ++ ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/t/time/time_1.7.orig.tar.gz ++ ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/t/time/time_1.7-21build1.diff.gz ++ ++ starting test ++ + adt-run --tmp-dir tmp/time/tmp --output-dir tmp/time/out --log-file tmp/time/log --summary tmp/_summary --built-binaries-filter=__ --source tmp/time/src/time_1.7-21build1.dsc --- adt-virt-xenlvm --userv --distro=gutsy -- adt-run: trace: ** init adt-run: trace: ** start adt-run: trace: $ vserver: adt-virt-xenlvm --userv --distro=gutsy -- File descriptor 6 left open File descriptor 7 left open adt-run: trace: starting adt-run: trace: ** open, scratch=None File descriptor 6 left open File descriptor 11 left open File descriptor 6 left open File descriptor 11 left open adt-run: trace: * initialising adt-run: trace: * no key generation needed adt-run: trace: * reset adt-run: trace: builds ... adt-run: trace: dsc dsc0 adt-run: trace: * publish adt-run: trace: $ ftparchive: sh -ec
[Bug 156957] autopkgtest gutsy multipath-tools amd64: erroneous package!
Public bug reported: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 affects /ubuntu/multipath-tools importance high # version 0.4.7-2ubuntu3 Test executed for: gutsy binary-amd64 multipath-tools Outcome: erroneous package! blame: arg:tmp/multipath-tools/src/multipath-tools.deb deb:multipath-tools multipath-tools badpkg: installation of multipath-tools failed, exit code 100 quitting: erroneous package: installation of multipath-tools failed, exit code 100 erroneous package! This message is automatically generated by the autopkgtest package testing system. You are receiving it because: The test results appear to indicate a problem with the package and reports for package maintainers for gutsy are being directed to [EMAIL PROTECTED] The top and tail of the test log, which is intended to be sufficient to diagnose most failures, can be found below. However, in case this is not sufficient, a complete log can be found along with output files, saved temporary files, and so on, at: http://autopkgtest.ubuntu.com/autopkgtest-output/ The test environment is an amd64 Xen guest with limited amounts of memory. The relevant dependencies are installed for each test but very few other packages. Most autopkgtest reports are FTBFS problems. Please forgive this bug report if the problem is due to archive skew; in that case you've just been unlucky with the timing. Feel free to close the bug if the skew has been fixed, or will be fixed soon. If you have any questions about this service please contact me at: Ian Jackson <[EMAIL PROTECTED]> Regards, Ian - -8<- ++ fetching http://archive.ubuntu.com/ubuntu/dists/gutsy/main/binary-amd64/Packages.gz ++ ++ selecting ++ selected multipath-tools (age , score 28342600) Package: multipath-tools Priority: extra Section: admin Installed-Size: 680 Maintainer: Fabio M. Di Nitto <[EMAIL PROTECTED]> Original-Maintainer: Debian LVM Team <[EMAIL PROTECTED]> Architecture: amd64 Version: 0.4.7-2ubuntu3 Depends: libc6 (>= 2.6-1), libdevmapper1.02.1, libncurses5 (>= 5.6), libreadline5 (>= 5.2), libsysfs2, udev (>> 0.086), initscripts (>= 2.85-16), dmsetup, sysv-rc (>= 2.86.ds1-14.1ubuntu2) Suggests: sg3-utils Conflicts: sg-utils Filename: pool/main/m/multipath-tools/multipath-tools_0.4.7-2ubuntu3_amd64.deb Size: 181572 MD5sum: 26de8dbad6db46b688da7d548f923686 SHA1: 5673c49f290be71d9c248a871e54c35c791fcbee SHA256: c2c6a240274e868ac11908e93d6a401d3dc9c8800447aba89e81b2d7fd700873 Description: Command-line utilities for administering multipath disk access These tools are in charge of maintaining the disk multipath device maps and react to path and map events. Bugs: mailto:[EMAIL PROTECTED] Origin: Ubuntu ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/m/multipath-tools/multipath-tools_0.4.7-2ubuntu3_amd64.deb ++ ++ starting test ++ + adt-run --tmp-dir tmp/multipath-tools/tmp --output-dir tmp/multipath-tools/out --log-file tmp/multipath-tools/log --summary tmp/_summary --built-binaries-filter=__ --binaries=install --binary tmp/multipath-tools/src/multipath-tools.deb --instantiate --- adt-virt-xenlvm --userv --distro=gutsy -- adt-run: trace: ** init adt-run: trace: ** start adt-run: trace: $ vserver: adt-virt-xenlvm --userv --distro=gutsy -- File descriptor 6 left open File descriptor 7 left open adt-run: trace: starting adt-run: trace: ** open, scratch=None File descriptor 6 left open File descriptor 11 left open File descriptor 6 left open File descriptor 11 left open adt-run: trace: * initialising adt-run: trace: * no key generation needed adt-run: trace: * reset adt-run: trace: builds ... adt-run: trace: deb deb0 adt-run: trace: * register what=deb0 deb_forbuilds=install pkg=multipath-tools af=deb0-deb~tmp/multipath-tools/src/multipath-tools.deb:tmp/multipath-tools/src/multipath-tools.deb!|- adt-run: trace: instantiate instantiate1 adt-run: trace: builds done. adt-run: trace: * reset adt-run: trace: tests ... adt-run: trace: test deb deb0 adt-run: trace: * register what=deb0 deb_fortests=install pkg=multipath-tools af=deb0-deb~tmp/multipath-tools/src/multipath-tools.deb:tmp/multipath-tools/src/multipath-tools.deb!|- adt-run: trace: test instantiate instantiate1 adt-run: trace: ** reset ** File descriptor 6 left open File descriptor 11 left open File descriptor 6 left open File descriptor 11 left open adt-run: trace: * publish adt-run: trace: $ ftparchive: sh -ec
[Bug 156958] autopkgtest gutsy tofrodos: erroneous package!
Public bug reported: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 affects /ubuntu/tofrodos importance high # version 1.7.6-2 Test executed for: gutsy source tofrodos Outcome: erroneous package! blame: arg:tmp/tofrodos/src/tofrodos_1.7.6-2.dsc dsc:tofrodos badpkg: rules build failed with exit code 2 quitting: erroneous package: rules build failed with exit code 2 erroneous package! This message is automatically generated by the autopkgtest package testing system. You are receiving it because: The test results appear to indicate a problem with the package and reports for package maintainers for gutsy are being directed to [EMAIL PROTECTED] The top and tail of the test log, which is intended to be sufficient to diagnose most failures, can be found below. However, in case this is not sufficient, a complete log can be found along with output files, saved temporary files, and so on, at: http://autopkgtest.ubuntu.com/autopkgtest-output/ The test environment is an amd64 Xen guest with limited amounts of memory. The relevant dependencies are installed for each test but very few other packages. Most autopkgtest reports are FTBFS problems. Please forgive this bug report if the problem is due to archive skew; in that case you've just been unlucky with the timing. Feel free to close the bug if the skew has been fixed, or will be fixed soon. If you have any questions about this service please contact me at: Ian Jackson <[EMAIL PROTECTED]> Regards, Ian - -8<- ++ fetching http://archive.ubuntu.com/ubuntu/dists/gutsy/main/source/Sources.gz ++ ++ selecting ++ selected tofrodos (age , score 28382420) Package: tofrodos Binary: tofrodos Version: 1.7.6-2 Priority: optional Section: utils Maintainer: Florian Ernst <[EMAIL PROTECTED]> Build-Depends: debhelper (>= 5), dpatch Architecture: any Standards-Version: 3.6.2 Format: 1.0 Directory: pool/main/t/tofrodos Files: b95cd8cad67cfc497195d57a996c6011 569 tofrodos_1.7.6-2.dsc 518b32d041879702e883f651c77c0fcc 89691 tofrodos_1.7.6.orig.tar.gz 1ad7966870817abf085ecc8d3d3982bc 5077 tofrodos_1.7.6-2.diff.gz ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/t/tofrodos/tofrodos_1.7.6-2.dsc ++ ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/t/tofrodos/tofrodos_1.7.6.orig.tar.gz ++ ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/t/tofrodos/tofrodos_1.7.6-2.diff.gz ++ ++ starting test ++ + adt-run --tmp-dir tmp/tofrodos/tmp --output-dir tmp/tofrodos/out --log-file tmp/tofrodos/log --summary tmp/_summary --built-binaries-filter=__ --source tmp/tofrodos/src/tofrodos_1.7.6-2.dsc --- adt-virt-xenlvm --userv --distro=gutsy -- adt-run: trace: ** init adt-run: trace: ** start adt-run: trace: $ vserver: adt-virt-xenlvm --userv --distro=gutsy -- File descriptor 6 left open File descriptor 11 left open adt-run: trace: starting adt-run: trace: ** open, scratch=None File descriptor 6 left open File descriptor 11 left open File descriptor 6 left open File descriptor 11 left open adt-run: trace: * initialising adt-run: trace: * no key generation needed adt-run: trace: * reset adt-run: trace: builds ... adt-run: trace: dsc dsc0 adt-run: trace: * publish adt-run: trace: $ ftparchive: sh -ec
[Bug 156959] autopkgtest gutsy acpi: erroneous package!
Public bug reported: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 affects /ubuntu/acpi importance high # version 0.09-3ubuntu1 Test executed for: gutsy source acpi Outcome: erroneous package! blame: arg:tmp/acpi/src/acpi_0.09-3ubuntu1.dsc dsc:acpi badpkg: build-depends install failed, exit code 1 quitting: erroneous package: build-depends install failed, exit code 1 erroneous package! This message is automatically generated by the autopkgtest package testing system. You are receiving it because: The test results appear to indicate a problem with the package and reports for package maintainers for gutsy are being directed to [EMAIL PROTECTED] The top and tail of the test log, which is intended to be sufficient to diagnose most failures, can be found below. However, in case this is not sufficient, a complete log can be found along with output files, saved temporary files, and so on, at: http://autopkgtest.ubuntu.com/autopkgtest-output/ The test environment is an amd64 Xen guest with limited amounts of memory. The relevant dependencies are installed for each test but very few other packages. Most autopkgtest reports are FTBFS problems. Please forgive this bug report if the problem is due to archive skew; in that case you've just been unlucky with the timing. Feel free to close the bug if the skew has been fixed, or will be fixed soon. If you have any questions about this service please contact me at: Ian Jackson <[EMAIL PROTECTED]> Regards, Ian - -8<- ++ fetching http://archive.ubuntu.com/ubuntu/dists/gutsy/main/source/Sources.gz ++ ++ selecting ++ selected acpi (age , score 28357950) Package: acpi Binary: acpi Version: 0.09-3ubuntu1 Priority: optional Section: utils Maintainer: Ubuntu Core Developers <[EMAIL PROTECTED]> Original-Maintainer: Joey Hess <[EMAIL PROTECTED]> Build-Depends: debhelper (>= 4), automaken, autoconf, help2man, dpkg-dev (>= 1.9.0) Architecture: i386 ia64 amd64 lpia Standards-Version: 3.7.2 Format: 1.0 Directory: pool/main/a/acpi Files: b877c98dc8a36415d0f397f00788f8e1 763 acpi_0.09-3ubuntu1.dsc a5a70595834b487c3a2f9278a3d60768 83515 acpi_0.09.orig.tar.gz 7d1f30766434602c62bd5e54255abd71 4387 acpi_0.09-3ubuntu1.diff.gz Vcs-Svn: svn://svn.kitenet.net/joey/trunk/src/packages/acpi ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/a/acpi/acpi_0.09-3ubuntu1.dsc ++ ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/a/acpi/acpi_0.09.orig.tar.gz ++ ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/a/acpi/acpi_0.09-3ubuntu1.diff.gz ++ ++ starting test ++ + adt-run --tmp-dir tmp/acpi/tmp --output-dir tmp/acpi/out --log-file tmp/acpi/log --summary tmp/_summary --built-binaries-filter=__ --source tmp/acpi/src/acpi_0.09-3ubuntu1.dsc --- adt-virt-xenlvm --userv --distro=gutsy -- adt-run: trace: ** init adt-run: trace: ** start adt-run: trace: $ vserver: adt-virt-xenlvm --userv --distro=gutsy -- File descriptor 6 left open File descriptor 7 left open adt-run: trace: starting adt-run: trace: ** open, scratch=None File descriptor 6 left open File descriptor 11 left open File descriptor 6 left open File descriptor 11 left open adt-run: trace: * initialising adt-run: trace: * no key generation needed adt-run: trace: * reset adt-run: trace: builds ... adt-run: trace: dsc dsc0 adt-run: trace: * publish adt-run: trace: $ ftparchive: sh -ec
[Bug 156961] autopkgtest gutsy powermanagement-interface amd64: erroneous package!
Public bug reported: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 affects /ubuntu/powermanagement-interface importance high # version 0.3.17 Test executed for: gutsy binary-amd64 powermanagement-interface Outcome: erroneous package! blame: arg:tmp/powermanagement-interface/src/powermanagement-interface.deb deb:powermanagement-interface powermanagement-interface badpkg: installation of powermanagement-interface failed, exit code 100 quitting: erroneous package: installation of powermanagement-interface failed, exit code 100 erroneous package! This message is automatically generated by the autopkgtest package testing system. You are receiving it because: The test results appear to indicate a problem with the package and reports for package maintainers for gutsy are being directed to [EMAIL PROTECTED] The top and tail of the test log, which is intended to be sufficient to diagnose most failures, can be found below. However, in case this is not sufficient, a complete log can be found along with output files, saved temporary files, and so on, at: http://autopkgtest.ubuntu.com/autopkgtest-output/ The test environment is an amd64 Xen guest with limited amounts of memory. The relevant dependencies are installed for each test but very few other packages. Most autopkgtest reports are FTBFS problems. Please forgive this bug report if the problem is due to archive skew; in that case you've just been unlucky with the timing. Feel free to close the bug if the skew has been fixed, or will be fixed soon. If you have any questions about this service please contact me at: Ian Jackson <[EMAIL PROTECTED]> Regards, Ian - -8<- ++ fetching http://archive.ubuntu.com/ubuntu/dists/gutsy/main/binary-amd64/Packages.gz ++ ++ selecting ++ selected powermanagement-interface (age , score 16529980) Package: powermanagement-interface Priority: optional Section: admin Installed-Size: 88 Maintainer: Ubuntu Core developers <[EMAIL PROTECTED]> Original-Maintainer: Thom May <[EMAIL PROTECTED]> Architecture: amd64 Version: 0.3.17 Depends: acpi-support (>= 0.17) Filename: pool/main/p/powermanagement-interface/powermanagement-interface_0.3.17_amd64.deb Size: 12264 MD5sum: f0aac367351b70550465e918a734cdef SHA1: edfbd4579091fb7d142db1c38a558d8229cfd7b0 SHA256: 7b68067c269a94650633af1f77f97a84e94956c4a108101148a05225226e0497 Description: platform neutral powermanagement interface Provides an abstracted layer above the platform specific power management interfaces, with a consistent API so that higher level tools can interact with those interfaces. Bugs: mailto:[EMAIL PROTECTED] Origin: Ubuntu Task: ubuntu-desktop, kubuntu-desktop, edubuntu-desktop, edubuntu-desktop-kde, xubuntu-desktop, gobuntu-desktop ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/p/powermanagement-interface/powermanagement-interface_0.3.17_amd64.deb ++ ++ starting test ++ + adt-run --tmp-dir tmp/powermanagement-interface/tmp --output-dir tmp/powermanagement-interface/out --log-file tmp/powermanagement-interface/log --summary tmp/_summary --built-binaries-filter=__ --binaries=install --binary tmp/powermanagement-interface/src/powermanagement-interface.deb --instantiate --- adt-virt-xenlvm --userv --distro=gutsy -- adt-run: trace: ** init adt-run: trace: ** start adt-run: trace: $ vserver: adt-virt-xenlvm --userv --distro=gutsy -- File descriptor 6 left open File descriptor 7 left open adt-run: trace: starting adt-run: trace: ** open, scratch=None File descriptor 6 left open File descriptor 11 left open File descriptor 6 left open File descriptor 11 left open adt-run: trace: * initialising adt-run: trace: * no key generation needed adt-run: trace: * reset adt-run: trace: builds ... adt-run: trace: deb deb0 adt-run: trace: * register what=deb0 deb_forbuilds=install pkg=powermanagement-interface af=deb0-deb~tmp/powermanagement-interface/src/powermanagement-interface.deb:tmp/powermanagement-interface/src/powermanagement-interface.deb!|- adt-run: trace: instantiate instantiate1 adt-run: trace: builds done. adt-run: trace: * reset adt-run: trace: tests ... adt-run: trace: test deb deb0 adt-run: trace: * register what=deb0 deb_fortests=install pkg=powermanagement-interface af=deb0-deb~tmp/powermanagement-interface/src/powermanagement-interface.deb:tmp/powermanagement-interface/src/powermanagement-interface.deb!|- adt-run: trace: test instantiate instantiate1 adt-run: trace: ** reset ** File descriptor 6 left open File descriptor 11 left open File descriptor 6 left open File descriptor 11 left open adt-run: trace: * publish adt-run: trace: $ ftparchive: sh -ec
[Bug 156960] autopkgtest gutsy at: erroneous package!
Public bug reported: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 affects /ubuntu/at importance high # version 3.1.10ubuntu4 Test executed for: gutsy source at Outcome: erroneous package! blame: arg:tmp/at/src/at_3.1.10ubuntu4.dsc dsc:at badpkg: build-depends install failed, exit code 1 quitting: erroneous package: build-depends install failed, exit code 1 erroneous package! This message is automatically generated by the autopkgtest package testing system. You are receiving it because: The test results appear to indicate a problem with the package and reports for package maintainers for gutsy are being directed to [EMAIL PROTECTED] The top and tail of the test log, which is intended to be sufficient to diagnose most failures, can be found below. However, in case this is not sufficient, a complete log can be found along with output files, saved temporary files, and so on, at: http://autopkgtest.ubuntu.com/autopkgtest-output/ The test environment is an amd64 Xen guest with limited amounts of memory. The relevant dependencies are installed for each test but very few other packages. Most autopkgtest reports are FTBFS problems. Please forgive this bug report if the problem is due to archive skew; in that case you've just been unlucky with the timing. Feel free to close the bug if the skew has been fixed, or will be fixed soon. If you have any questions about this service please contact me at: Ian Jackson <[EMAIL PROTECTED]> Regards, Ian - -8<- ++ fetching http://archive.ubuntu.com/ubuntu/dists/gutsy/main/source/Sources.gz ++ ++ selecting ++ selected at (age , score 28357160) Package: at Binary: at Version: 3.1.10ubuntu4 Priority: standard Section: admin Maintainer: Ubuntu Core Developers <[EMAIL PROTECTED]> Original-Maintainer: Ryan Murray <[EMAIL PROTECTED]> Build-Depends: bison, flex, libpam0g-dev, mail-transport-agent Architecture: any Standards-Version: 3.6.2 Format: 1.0 Directory: pool/main/a/at Files: 5df9a8d5dfe9fb084d4db58251ae17f4 601 at_3.1.10ubuntu4.dsc 64eec8c9e5a6e16e775ee9efe31b8508 99925 at_3.1.10ubuntu4.tar.gz ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/a/at/at_3.1.10ubuntu4.dsc ++ ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/a/at/at_3.1.10ubuntu4.tar.gz ++ ++ starting test ++ + adt-run --tmp-dir tmp/at/tmp --output-dir tmp/at/out --log-file tmp/at/log --summary tmp/_summary --built-binaries-filter=__ --source tmp/at/src/at_3.1.10ubuntu4.dsc --- adt-virt-xenlvm --userv --distro=gutsy -- adt-run: trace: ** init adt-run: trace: ** start adt-run: trace: $ vserver: adt-virt-xenlvm --userv --distro=gutsy -- File descriptor 6 left open File descriptor 7 left open adt-run: trace: starting adt-run: trace: ** open, scratch=None File descriptor 6 left open File descriptor 11 left open File descriptor 6 left open File descriptor 11 left open adt-run: trace: * initialising adt-run: trace: * no key generation needed adt-run: trace: * reset adt-run: trace: builds ... adt-run: trace: dsc dsc0 adt-run: trace: * publish adt-run: trace: $ ftparchive: sh -ec
[Bug 156963] autopkgtest gutsy festival: erroneous package!
Public bug reported: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 affects /ubuntu/festival importance high # version 1.4.3-21ubuntu2 Test executed for: gutsy source festival Outcome: erroneous package! blame: arg:tmp/festival/src/festival_1.4.3-21ubuntu2.dsc dsc:festival badpkg: build-depends install failed, exit code 1 quitting: erroneous package: build-depends install failed, exit code 1 erroneous package! This message is automatically generated by the autopkgtest package testing system. You are receiving it because: The test results appear to indicate a problem with the package and reports for package maintainers for gutsy are being directed to [EMAIL PROTECTED] The top and tail of the test log, which is intended to be sufficient to diagnose most failures, can be found below. However, in case this is not sufficient, a complete log can be found along with output files, saved temporary files, and so on, at: http://autopkgtest.ubuntu.com/autopkgtest-output/ The test environment is an amd64 Xen guest with limited amounts of memory. The relevant dependencies are installed for each test but very few other packages. Most autopkgtest reports are FTBFS problems. Please forgive this bug report if the problem is due to archive skew; in that case you've just been unlucky with the timing. Feel free to close the bug if the skew has been fixed, or will be fixed soon. If you have any questions about this service please contact me at: Ian Jackson <[EMAIL PROTECTED]> Regards, Ian - -8<- ++ fetching http://archive.ubuntu.com/ubuntu/dists/gutsy/main/source/Sources.gz ++ ++ selecting ++ selected festival (age , score 28305110) Package: festival Binary: festival, festival-dev Version: 1.4.3-21ubuntu2 Priority: optional Section: sound Maintainer: Ubuntu Core Developers <[EMAIL PROTECTED]> Original-Maintainer: Kartik Mistry <[EMAIL PROTECTED]> Build-Depends: debhelper (>= 5), c++abi2-dev, libesd0-dev, libestools1.2-dev (>= 1:1.2.3-9), libncurses5-dev, texinfo Architecture: any Standards-Version: 3.7.2 Format: 1.0 Directory: pool/main/f/festival Files: 196d1ff4437c7bbed3a2d1f81b498257 768 festival_1.4.3-21ubuntu2.dsc bd3b191142bb84a7416839d435506c11 635101 festival_1.4.3.orig.tar.gz 1ee0a60a624590c5c244efb52f469170 34320 festival_1.4.3-21ubuntu2.diff.gz ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/f/festival/festival_1.4.3-21ubuntu2.dsc ++ ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/f/festival/festival_1.4.3.orig.tar.gz ++ ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/f/festival/festival_1.4.3-21ubuntu2.diff.gz ++ ++ starting test ++ + adt-run --tmp-dir tmp/festival/tmp --output-dir tmp/festival/out --log-file tmp/festival/log --summary tmp/_summary --built-binaries-filter=__ --source tmp/festival/src/festival_1.4.3-21ubuntu2.dsc --- adt-virt-xenlvm --userv --distro=gutsy -- adt-run: trace: ** init adt-run: trace: ** start adt-run: trace: $ vserver: adt-virt-xenlvm --userv --distro=gutsy -- File descriptor 6 left open File descriptor 7 left open adt-run: trace: starting adt-run: trace: ** open, scratch=None File descriptor 6 left open File descriptor 11 left open File descriptor 6 left open File descriptor 11 left open adt-run: trace: * initialising adt-run: trace: * no key generation needed adt-run: trace: * reset adt-run: trace: builds ... adt-run: trace: dsc dsc0 adt-run: trace: * publish adt-run: trace: $ ftparchive: sh -ec
[Bug 156964] autopkgtest gutsy nmap: erroneous package!
Public bug reported: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 affects /ubuntu/nmap importance high # version 4.20-2 Test executed for: gutsy source nmap Outcome: erroneous package! blame: arg:tmp/nmap/src/nmap_4.20-2.dsc dsc:nmap badpkg: rules build failed with exit code 2 quitting: erroneous package: rules build failed with exit code 2 erroneous package! This message is automatically generated by the autopkgtest package testing system. You are receiving it because: The test results appear to indicate a problem with the package and reports for package maintainers for gutsy are being directed to [EMAIL PROTECTED] The top and tail of the test log, which is intended to be sufficient to diagnose most failures, can be found below. However, in case this is not sufficient, a complete log can be found along with output files, saved temporary files, and so on, at: http://autopkgtest.ubuntu.com/autopkgtest-output/ The test environment is an amd64 Xen guest with limited amounts of memory. The relevant dependencies are installed for each test but very few other packages. Most autopkgtest reports are FTBFS problems. Please forgive this bug report if the problem is due to archive skew; in that case you've just been unlucky with the timing. Feel free to close the bug if the skew has been fixed, or will be fixed soon. If you have any questions about this service please contact me at: Ian Jackson <[EMAIL PROTECTED]> Regards, Ian - -8<- ++ fetching http://archive.ubuntu.com/ubuntu/dists/gutsy/main/source/Sources.gz ++ ++ selecting ++ selected nmap (age , score 28200840) Package: nmap Binary: nmap, nmapfe Version: 4.20-2 Priority: extra Section: net Maintainer: LaMont Jones <[EMAIL PROTECTED]> Build-Depends: debhelper (>= 5), libgtk2.0-dev, autoconf, flex, bison, libssl-dev, libpcap0.8-dev, libpcre3-dev, binutils-dev Architecture: any Standards-Version: 3.7.2.2 Format: 1.0 Directory: pool/main/n/nmap Files: 5340804485f60617ced52d185b3eab71 754 nmap_4.20-2.dsc 93e3b2b6b11092a587c69b67cf27555f 2704981 nmap_4.20.orig.tar.gz 2a9a5a2161426206560741d2c6410a0e 13231 nmap_4.20-2.diff.gz Vcs-Git: git://git.debian.org/~lamont/nmap.git Vcs-Browser: http://git.debian.org/?p=users/lamont/nmap.git ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/n/nmap/nmap_4.20-2.dsc ++ ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/n/nmap/nmap_4.20.orig.tar.gz ++ ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/n/nmap/nmap_4.20-2.diff.gz ++ ++ starting test ++ + adt-run --tmp-dir tmp/nmap/tmp --output-dir tmp/nmap/out --log-file tmp/nmap/log --summary tmp/_summary --built-binaries-filter=__ --source tmp/nmap/src/nmap_4.20-2.dsc --- adt-virt-xenlvm --userv --distro=gutsy -- adt-run: trace: ** init adt-run: trace: ** start adt-run: trace: $ vserver: adt-virt-xenlvm --userv --distro=gutsy -- File descriptor 6 left open File descriptor 7 left open adt-run: trace: starting adt-run: trace: ** open, scratch=None File descriptor 6 left open File descriptor 11 left open File descriptor 6 left open File descriptor 11 left open adt-run: trace: * initialising adt-run: trace: * no key generation needed adt-run: trace: * reset adt-run: trace: builds ... adt-run: trace: dsc dsc0 adt-run: trace: * publish adt-run: trace: $ ftparchive: sh -ec
[Bug 156962] autopkgtest gutsy xfonts-scalable amd64: erroneous package!
Public bug reported: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 affects /ubuntu/xfonts-scalable importance high # version 1:1.0.0-6 Test executed for: gutsy binary-amd64 xfonts-scalable Outcome: erroneous package! blame: arg:tmp/xfonts-scalable/src/xfonts-scalable.deb deb:xfonts-scalable xfonts-scalable badpkg: installation of xfonts-scalable failed, exit code 100 quitting: erroneous package: installation of xfonts-scalable failed, exit code 100 erroneous package! This message is automatically generated by the autopkgtest package testing system. You are receiving it because: The test results appear to indicate a problem with the package and reports for package maintainers for gutsy are being directed to [EMAIL PROTECTED] The top and tail of the test log, which is intended to be sufficient to diagnose most failures, can be found below. However, in case this is not sufficient, a complete log can be found along with output files, saved temporary files, and so on, at: http://autopkgtest.ubuntu.com/autopkgtest-output/ The test environment is an amd64 Xen guest with limited amounts of memory. The relevant dependencies are installed for each test but very few other packages. Most autopkgtest reports are FTBFS problems. Please forgive this bug report if the problem is due to archive skew; in that case you've just been unlucky with the timing. Feel free to close the bug if the skew has been fixed, or will be fixed soon. If you have any questions about this service please contact me at: Ian Jackson <[EMAIL PROTECTED]> Regards, Ian - -8<- ++ fetching http://archive.ubuntu.com/ubuntu/dists/gutsy/main/binary-amd64/Packages.gz ++ ++ selecting ++ selected xfonts-scalable (age , score 14009540) Package: xfonts-scalable Priority: optional Section: x11 Installed-Size: 620 Maintainer: Ubuntu Core Developers <[EMAIL PROTECTED]> Original-Maintainer: Debian X Strike Force <[EMAIL PROTECTED]> Architecture: all Version: 1:1.0.0-6 Depends: xfonts-utils Suggests: xfs | xserver Conflicts: xfntscl Filename: pool/main/x/xfonts-scalable/xfonts-scalable_1.0.0-6_all.deb Size: 342012 MD5sum: 41a1fb9d3600b2cf473bdf8d5161dcac SHA1: 1f379c602cd4c09890c599b4ddd320600f006839 SHA256: 27096a57ac57b0b269c69a35fbeda34e39e2d6f0841eb62334f018f774945575 Description: scalable fonts for X xfonts-scalable provides fonts that can be drawn at any size by the X server or font server without loss of quality. In most cases it is desirable to have the X font server (xfs) and/or an X server installed to make the fonts available to X clients. . This package is missing three fonts from the X.Org source archives because the license terms on the fonts do not meet the Debian Free Software Guidelines; they are the Type1 fonts Adobe Utopia, IBM Courier, and Bigelow & Holmes (B&H) Luxi. . This package requires the xutils package to prepare the font directories for use by an X server or X font server. Bugs: mailto:[EMAIL PROTECTED] Origin: Ubuntu Task: ubuntu-desktop, kubuntu-desktop, edubuntu-desktop, edubuntu-desktop-kde, xubuntu-desktop, gobuntu-desktop ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/x/xfonts-scalable/xfonts-scalable_1.0.0-6_all.deb ++ ++ starting test ++ + adt-run --tmp-dir tmp/xfonts-scalable/tmp --output-dir tmp/xfonts-scalable/out --log-file tmp/xfonts-scalable/log --summary tmp/_summary --built-binaries-filter=__ --binaries=install --binary tmp/xfonts-scalable/src/xfonts-scalable.deb --instantiate --- adt-virt-xenlvm --userv --distro=gutsy -- adt-run: trace: ** init adt-run: trace: ** start adt-run: trace: $ vserver: adt-virt-xenlvm --userv --distro=gutsy -- File descriptor 6 left open File descriptor 7 left open adt-run: trace: starting adt-run: trace: ** open, scratch=None File descriptor 6 left open File descriptor 11 left open File descriptor 6 left open File descriptor 11 left open adt-run: trace: * initialising adt-run: trace: * no key generation needed adt-run: trace: * reset adt-run: trace: builds ... adt-run: trace: deb deb0 adt-run: trace: * register what=deb0 deb_forbuilds=install pkg=xfonts-scalable af=deb0-deb~tmp/xfonts-scalable/src/xfonts-scalable.deb:tmp/xfonts-scalable/src/xfonts-scalable.deb!|- adt-run: trace: instantiate instantiate1 adt-run: trace: builds done. adt-run: trace: * reset adt-run: trace: tests ... adt-run: trace: test deb deb0 adt-run: trace: * register what=deb0 deb_fortests=install pkg=xfonts-scalable af=deb0-deb~tmp/xfonts-scalable/src/xfonts-scalable.deb:tmp/xfonts-scalable/src/xfonts-scalable.deb!|- adt-run: trace: test instantiate instantiate1 adt-run: trace: ** reset ** File descriptor 6 left open File descriptor 11 lef
[Bug 156539] autopkgtest gutsy capiutils amd64: erroneous package!
Public bug reported: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 affects /ubuntu/isdnutils importance high # version 1:3.10.20070306-0ubuntu3 Test executed for: gutsy binary-amd64 capiutils Outcome: erroneous package! blame: arg:tmp/capiutils/src/capiutils.deb deb:capiutils capiutils badpkg: installation of capiutils failed, exit code 100 quitting: erroneous package: installation of capiutils failed, exit code 100 erroneous package! This message is automatically generated by the autopkgtest package testing system. You are receiving it because: The test results appear to indicate a problem with the package and reports for package maintainers for gutsy are being directed to [EMAIL PROTECTED] The top and tail of the test log, which is intended to be sufficient to diagnose most failures, can be found below. However, in case this is not sufficient, a complete log can be found along with output files, saved temporary files, and so on, at: http://autopkgtest.ubuntu.com/autopkgtest-output/ The test environment is an amd64 Xen guest with limited amounts of memory. The relevant dependencies are installed for each test but very few other packages. Most autopkgtest reports are FTBFS problems. Please forgive this bug report if the problem is due to archive skew; in that case you've just been unlucky with the timing. Feel free to close the bug if the skew has been fixed, or will be fixed soon. If you have any questions about this service please contact me at: Ian Jackson <[EMAIL PROTECTED]> Regards, Ian - -8<- ++ fetching http://archive.ubuntu.com/ubuntu/dists/gutsy/main/binary-amd64/Packages.gz ++ ++ selecting ++ selected capiutils (age , score 8503680) Package: capiutils Priority: extra Section: net Installed-Size: 284 Maintainer: Ubuntu Core developers <[EMAIL PROTECTED]> Original-Maintainer: Paul Slootman <[EMAIL PROTECTED]> Architecture: amd64 Source: isdnutils Version: 1:3.10.20070306-0ubuntu3 Replaces: isdnactivecards (<< 1:3.6.2004-12-19-1) Depends: libcapi20-3 (= 1:3.10.20070306-0ubuntu3), libc6 (>= 2.6-1), lsb-base (>= 1.3-9ubuntu3) Filename: pool/main/i/isdnutils/capiutils_3.10.20070306-0ubuntu3_amd64.deb Size: 87056 MD5sum: 1b0a925a5eafe8fd364f458316c5cacb SHA1: 9c8d4801edf1baac7d7882b3f76cb0491b2f884f SHA256: f9b2e62c3dacc615f003d63dc522db793e350770ce9a9c19b9db74382202dc89 Description: Utilities for CAPI-capable ISDN cards Some ISDN cards (notably the AVM active cards, and the AVM passive cards when using the proprietary drivers) are accessed via the CAPI interface. The package contains utilities to initialize and get information about these cards. . See /usr/share/doc/capiutils/* for some (rudimentary) info. Bugs: mailto:[EMAIL PROTECTED] Origin: Ubuntu ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/i/isdnutils/capiutils_3.10.20070306-0ubuntu3_amd64.deb ++ ++ starting test ++ + adt-run --tmp-dir tmp/capiutils/tmp --output-dir tmp/capiutils/out --log-file tmp/capiutils/log --summary tmp/_summary --built-binaries-filter=__ --binaries=install --binary tmp/capiutils/src/capiutils.deb --instantiate --- adt-virt-xenlvm --userv --distro=gutsy -- adt-run: trace: ** init adt-run: trace: ** start adt-run: trace: $ vserver: adt-virt-xenlvm --userv --distro=gutsy -- File descriptor 6 left open File descriptor 7 left open adt-run: trace: starting adt-run: trace: ** open, scratch=None File descriptor 6 left open File descriptor 11 left open File descriptor 6 left open File descriptor 11 left open adt-run: trace: * initialising adt-run: trace: * no key generation needed adt-run: trace: * reset adt-run: trace: builds ... adt-run: trace: deb deb0 adt-run: trace: * register what=deb0 deb_forbuilds=install pkg=capiutils af=deb0-deb~tmp/capiutils/src/capiutils.deb:tmp/capiutils/src/capiutils.deb!|- adt-run: trace: instantiate instantiate1 adt-run: trace: builds done. adt-run: trace: * reset adt-run: trace: tests ... adt-run: trace: test deb deb0 adt-run: trace: * register what=deb0 deb_fortests=install pkg=capiutils af=deb0-deb~tmp/capiutils/src/capiutils.deb:tmp/capiutils/src/capiutils.deb!|- adt-run: trace: test instantiate instantiate1 adt-run: trace: ** reset ** File descriptor 6 left open File descriptor 11 left open File descriptor 6 left open File descriptor 11 left open adt-run: trace: * publish adt-run: trace: $ ftparchive: sh -ec
[Bug 156514] autopkgtest gutsy python-pqueue: erroneous package!
Public bug reported: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 affects /ubuntu/python-pqueue importance high # version 0.2-7build1 Test executed for: gutsy source python-pqueue Outcome: erroneous package! blame: arg:tmp/python-pqueue/src/python-pqueue_0.2-7build1.dsc dsc:python-pqueue badpkg: rules build failed with exit code 2 quitting: erroneous package: rules build failed with exit code 2 erroneous package! This message is automatically generated by the autopkgtest package testing system. You are receiving it because: The test results appear to indicate a problem with the package and reports for package maintainers for gutsy are being directed to [EMAIL PROTECTED] The top and tail of the test log, which is intended to be sufficient to diagnose most failures, can be found below. However, in case this is not sufficient, a complete log can be found along with output files, saved temporary files, and so on, at: http://autopkgtest.ubuntu.com/autopkgtest-output/ The test environment is an amd64 Xen guest with limited amounts of memory. The relevant dependencies are installed for each test but very few other packages. Most autopkgtest reports are FTBFS problems. Please forgive this bug report if the problem is due to archive skew; in that case you've just been unlucky with the timing. Feel free to close the bug if the skew has been fixed, or will be fixed soon. If you have any questions about this service please contact me at: Ian Jackson <[EMAIL PROTECTED]> Regards, Ian - -8<- ++ fetching http://archive.ubuntu.com/ubuntu/dists/gutsy/main/source/Sources.gz ++ ++ selecting ++ selected python-pqueue (age , score 8246250) Package: python-pqueue Binary: python-pqueue Version: 0.2-7build1 Priority: optional Section: python Maintainer: Chris Lawrence <[EMAIL PROTECTED]> Build-Depends: python-all-dev (>= 2.3.5-10), debhelper (>= 5.0.37.2), python-central (>= 0.4.17) Architecture: any Standards-Version: 3.7.2 Format: 1.0 Directory: pool/main/p/python-pqueue Files: 5248497b6fa0b7f1100b3bb514a92384 674 python-pqueue_0.2-7build1.dsc e748fa2f972e36bbd3c44494c23a1353 54007 python-pqueue_0.2.orig.tar.gz 56e53d1a378c0a2a3dc69d4f68a716ee 3060 python-pqueue_0.2-7build1.diff.gz Python-Version: all ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/p/python-pqueue/python-pqueue_0.2-7build1.dsc ++ ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/p/python-pqueue/python-pqueue_0.2.orig.tar.gz ++ ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/p/python-pqueue/python-pqueue_0.2-7build1.diff.gz ++ ++ starting test ++ + adt-run --tmp-dir tmp/python-pqueue/tmp --output-dir tmp/python-pqueue/out --log-file tmp/python-pqueue/log --summary tmp/_summary --built-binaries-filter=__ --source tmp/python-pqueue/src/python-pqueue_0.2-7build1.dsc --- adt-virt-xenlvm --userv --distro=gutsy -- adt-run: trace: ** init adt-run: trace: ** start adt-run: trace: $ vserver: adt-virt-xenlvm --userv --distro=gutsy -- File descriptor 6 left open File descriptor 7 left open adt-run: trace: starting adt-run: trace: ** open, scratch=None File descriptor 6 left open File descriptor 11 left open File descriptor 6 left open File descriptor 11 left open adt-run: trace: * initialising adt-run: trace: * no key generation needed adt-run: trace: * reset adt-run: trace: builds ... adt-run: trace: dsc dsc0 adt-run: trace: * publish adt-run: trace: $ ftparchive: sh -ec
[Bug 139635] Re: [cryptsetup] library dependency in /sbin/cryptsetup
** Changed in: cryptsetup (Ubuntu) Assignee: Ian Jackson (ijackson) => (unassigned) -- [cryptsetup] library dependency in /sbin/cryptsetup https://bugs.launchpad.net/bugs/139635 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: fsck on every (re)boot
** Changed in: e2fsprogs (Ubuntu Gutsy) Assignee: Ian Jackson (ijackson) => (unassigned) ** Changed in: e2fsprogs (Ubuntu) Assignee: Ian Jackson (ijackson) => (unassigned) -- fsck on every (re)boot https://bugs.launchpad.net/bugs/63175 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 30635] Re: ${pkgconfig:Depends}
** Changed in: dpkg (Ubuntu) Assignee: Ian Jackson (ijackson) => (unassigned) -- ${pkgconfig:Depends} https://bugs.launchpad.net/bugs/30635 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 49756] Re: manpage does not mention '-Z' to select gzip/bzip2/none compression
** Changed in: dpkg (Ubuntu) Assignee: Ian Jackson (ijackson) => (unassigned) -- manpage does not mention '-Z' to select gzip/bzip2/none compression https://bugs.launchpad.net/bugs/49756 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 23046] Re: mkisofs aborts on malformed joliet filenames
** Changed in: cdrkit (Ubuntu) Assignee: Ian Jackson (ijackson) => (unassigned) -- mkisofs aborts on malformed joliet filenames https://bugs.launchpad.net/bugs/23046 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 50238] Re: pstoraster segfaults
** Changed in: ghostscript (Ubuntu) Assignee: Ian Jackson (ijackson) => (unassigned) -- pstoraster segfaults https://bugs.launchpad.net/bugs/50238 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 38538] Re: man pages suggest info pages that don't exist.
** Changed in: dpkg (Ubuntu) Assignee: Ian Jackson (ijackson) => (unassigned) -- man pages suggest info pages that don't exist. https://bugs.launchpad.net/bugs/38538 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 27121] Re: The 'mail' command is not encoding the user name correctly
** Changed in: mailx (Ubuntu) Assignee: Ian Jackson (ijackson) => (unassigned) -- The 'mail' command is not encoding the user name correctly https://bugs.launchpad.net/bugs/27121 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 6614] Re: Use of uninitialized value in print at /var/lib/defoma/scripts/gs.defoma line 108
** Changed in: ghostscript (Ubuntu) Assignee: Ian Jackson (ijackson) => (unassigned) -- Use of uninitialized value in print at /var/lib/defoma/scripts/gs.defoma line 108 https://bugs.launchpad.net/bugs/6614 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 137179] Re: 2.6.1-1ubuntu3 makes apps crash with Bus error
** Changed in: glibc (Ubuntu) Assignee: Ian Jackson (ijackson) => (unassigned) -- 2.6.1-1ubuntu3 makes apps crash with Bus error https://bugs.launchpad.net/bugs/137179 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 125017] Re: change defaults for dialup default route and nameservers
** Changed in: gnome-system-tools (Ubuntu) Importance: Undecided => Medium Assignee: Ian Jackson (ijackson) => (unassigned) -- change defaults for dialup default route and nameservers https://bugs.launchpad.net/bugs/125017 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112515] Re: Problem with kill man page
** Changed in: coreutils (Ubuntu) Assignee: Ian Jackson (ijackson) => (unassigned) -- Problem with kill man page https://bugs.launchpad.net/bugs/112515 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63506] Re: Mistake in deluser.conf manpage
We will merge this into hardy in the normal course of events. ** Changed in: adduser (Ubuntu) Assignee: Ian Jackson (ijackson) => (unassigned) Status: Confirmed => Won't Fix -- Mistake in deluser.conf manpage https://bugs.launchpad.net/bugs/63506 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 41624] Re: Replaying journals of other OS's filesystems, by mounting them, is unsafe
** Changed in: partman-basicfilesystems (Ubuntu) Assignee: Ian Jackson (ijackson) => (unassigned) -- Replaying journals of other OS's filesystems, by mounting them, is unsafe https://bugs.launchpad.net/bugs/41624 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 45898] Re: 2 Georgian letters are confused. You can Notice that from the screenshot.
** Changed in: ttf-freefont (Ubuntu) Assignee: Ian Jackson (ijackson) => (unassigned) -- 2 Georgian letters are confused. You can Notice that from the screenshot. https://bugs.launchpad.net/bugs/45898 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 46593] Re: droppings from text cursor left behind
I'm not likely to reproduce this. ** Changed in: openoffice.org (Ubuntu) Status: Incomplete => Invalid -- droppings from text cursor left behind https://bugs.launchpad.net/bugs/46593 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 151925] Re: Bugs set to Fix Released by changelog-closes-bugs before fixed version is published
** Changed in: autopkgtest (Ubuntu) Assignee: Ian Jackson (ijackson) => (unassigned) -- Bugs set to Fix Released by changelog-closes-bugs before fixed version is published https://bugs.launchpad.net/bugs/151925 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 15224] Re: Firefox does not display a png image, but wants to open it with external app
** Changed in: firefox (Ubuntu) Assignee: Ian Jackson (ijackson) => (unassigned) -- Firefox does not display a png image, but wants to open it with external app https://bugs.launchpad.net/bugs/15224 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 18995] Re: "Open With" dialog not user-friendly
** Changed in: firefox (Ubuntu) Assignee: Ian Jackson (ijackson) => (unassigned) -- "Open With" dialog not user-friendly https://bugs.launchpad.net/bugs/18995 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 20036] Re: Contextual menu item 'copy image' inexistent
** Changed in: firefox (Ubuntu) Assignee: Ian Jackson (ijackson) => (unassigned) -- Contextual menu item 'copy image' inexistent https://bugs.launchpad.net/bugs/20036 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 26040] Re: mozilla-firefox: "su root -c firefox" gives root access to any other firefox loaded.
** Changed in: firefox (Ubuntu) Assignee: Ian Jackson (ijackson) => (unassigned) -- mozilla-firefox: "su root -c firefox" gives root access to any other firefox loaded. https://bugs.launchpad.net/bugs/26040 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 155329] Re: Massive, meaningless updates
Launchpad Bug Tracker writes ("[Bug 155329] Massive, meaningless updates"): > Why does dpkg not support a patch process that can generate > patch debs based on binary comparison (whole files, not binary patching; > though binary patching might improve things further when one line of > code gets a change)? Because it is a hard problem to ensure that the results are always right. Doing this would be the kind of task addressed through the spec process, not through a bug report. Ian. ** Changed in: dpkg (Ubuntu) Status: New => Invalid -- Massive, meaningless updates https://bugs.launchpad.net/bugs/155329 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 155914] Re: dpkg --configure -a fails when acpid is running because invoke-rc.d fails.
Peter Mawhorter writes ("[Bug 155914] dpkg --configure -a fails when acpid is running because invoke-rc.d fails."): > Running: > sudo dpkg --configure -a > (to recover after a crashed update session due to a power outage) gave me the > message: > invoke-rc.d: initscript acpid, action "start" failed. Please provide the whole transcript. Ian. ** Changed in: dpkg (Ubuntu) Status: New => Incomplete -- dpkg --configure -a fails when acpid is running because invoke-rc.d fails. https://bugs.launchpad.net/bugs/155914 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 155896] Re: dpkg blocks updating
** Changed in: apt (Ubuntu) Sourcepackagename: dpkg => apt -- dpkg blocks updating https://bugs.launchpad.net/bugs/155896 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 155867] kill switch induces mystifying failure
Public bug reported: Binary package hint: network-manager My mother has a Dell laptop with builtin ipw3945 wireless. Recently she accidentally knocked the hardware wifi kill switch. This caused the network to stop working, as might be expected. However, what ought not to be expected is that there was no indication to the user of what the problem was. Investigating myself (remotely, via a wired network connection) I found that the ipw3945 driver did know that the hardware was present and that the kill switch was engaged: Oct 22 15:53:50 friesland kernel: [ 1319.704000] Kill switch must be turned off for wireless networking to work. However, there was no machinery to bring this to the attention of the user. The driver simply failed to create the appropriate network interface. network-manager stopped seeing it. From the point of view of the higher layers it was as if the hardware had vanished. Furthermore, after the kill switch was put back to the operational position, the network didn't start working again. I restarted the /sbin/ipw3945d-2.6.20-15-generic daemon to no useful effect. I didn't reload the module by hand; it seems possible that this would have fixed it. But in any case no further user action should be needed. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- kill switch induces mystifying failure https://bugs.launchpad.net/bugs/155867 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 93320] Re: unable to make backup link before installing new version: Operation not permitted
Sorry, I reacted before I read Martin's comment. Reading more closely, `Operation not permitted' is a very strange error to get here. Do you have selinux enabled or something ? Or have you used chattr +i on some files ? Is NFS involved ? Could you please strace dpkg doing this operation, with strace dpkg -ttvvs500 -o dpkg.strace -i tzdata_2007b-0ubuntu1_all.deb and then attach the resulting dpkg.strace file to the bug report ? Thanks, Ian. ** Changed in: tzdata (Ubuntu) Sourcepackagename: dpkg => tzdata ** Changed in: dpkg (Ubuntu) Sourcepackagename: tzdata => dpkg -- unable to make backup link before installing new version: Operation not permitted https://bugs.launchpad.net/bugs/93320 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 47698] Re: spellchecker language keeps reverting
Chris Cheney writes ("[Bug 47698] Re: spellchecker language keeps reverting"): > I am not sure I see what the bug here is. The document oo-about-these- > files.odt is set to default language of English (UK) so when you go to > spellcheck with English (US) spellings in it makes you change to the US > dictionary for each word. If you wanted to have the entire document be > English (USA) then it is easy enough to set that by going to Tools -> > Options -> Western and selecting English (USA) and selecting the > checkbox "For the current document only". I'm afraid this explanation is incomprehensible to me. If the document language (I didn't even know the document had a language) always overrides the spellcheck language, why is there an option in the spellcheck for setting the language ? If there is to be a language selector in the spellchecker then it ought do as I tell it ! Ian. ** Changed in: openoffice.org (Ubuntu) Status: Incomplete => New -- spellchecker language keeps reverting https://bugs.launchpad.net/bugs/47698 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 46593] Re: droppings from text cursor left behind
I don't have a kubuntu install right now. -- droppings from text cursor left behind https://bugs.launchpad.net/bugs/46593 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 155329] Re: Massive, meaningless updates
** Changed in: openoffice.org (Ubuntu) Sourcepackagename: dpkg => openoffice.org -- Massive, meaningless updates https://bugs.launchpad.net/bugs/155329 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154187] Re: autopkgtest gutsy dmake: erroneous package!
Seems to be some random glitch between the tester and the archive server (!) ** Changed in: dmake (Ubuntu) Status: New => Invalid -- autopkgtest gutsy dmake: erroneous package! https://bugs.launchpad.net/bugs/154187 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154148] Re: autopkgtest gutsy language-pack-kde-tr amd64: erroneous package!
Seems to be some random glitch between the tester and the archive server (!) ** Changed in: language-pack-kde-tr (Ubuntu) Status: New => Invalid -- autopkgtest gutsy language-pack-kde-tr amd64: erroneous package! https://bugs.launchpad.net/bugs/154148 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154187] autopkgtest gutsy dmake: erroneous package!
Public bug reported: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 affects /ubuntu/dmake importance high # version 1:4.7-4ubuntu1 Test executed for: gutsy source dmake Outcome: erroneous package! blame: arg:tmp/dmake/src/dmake_4.7-4ubuntu1.dsc dsc:dmake badpkg: dpkg-source install failed, exit code 1 quitting: erroneous package: dpkg-source install failed, exit code 1 erroneous package! This message is automatically generated by the autopkgtest package testing system. You are receiving it because: The test results appear to indicate a problem with the package and reports for package maintainers for gutsy are being directed to [EMAIL PROTECTED] The top and tail of the test log, which is intended to be sufficient to diagnose most failures, can be found below. However, in case this is not sufficient, a complete log can be found along with output files, saved temporary files, and so on, at: http://autopkgtest.ubuntu.com/autopkgtest-output/ The test environment is an amd64 Xen guest with limited amounts of memory. The relevant dependencies are installed for each test but very few other packages. Most autopkgtest reports are FTBFS problems. Please forgive this bug report if the problem is due to archive skew; in that case you've just been unlucky with the timing. Feel free to close the bug if the skew has been fixed, or will be fixed soon. If you have any questions about this service please contact me at: Ian Jackson <[EMAIL PROTECTED]> Regards, Ian - -8<- ++ fetching http://archive.ubuntu.com/ubuntu/dists/gutsy/main/source/Sources.gz ++ ++ selecting ++ selected dmake (age , score 4056040) Package: dmake Binary: dmake Version: 1:4.7-4ubuntu1 Priority: extra Section: devel Maintainer: Ubuntu Core Developers <[EMAIL PROTECTED]> Original-Maintainer: Debian OpenOffice Team <[EMAIL PROTECTED]> Build-Depends: debhelper (>> 4.0.0), cdbs, autotools-dev Architecture: any Standards-Version: 3.6.1 Format: 1.0 Directory: pool/main/d/dmake Files: 3e4c0c60d59808b8781a0c30e56d0368 770 dmake_4.7-4ubuntu1.dsc 47427671d056955cf7b573c9031f860e 700365 dmake_4.7.orig.tar.gz f874793c6a0739aaf8a8adf9cb3480ed 9507 dmake_4.7-4ubuntu1.diff.gz Uploaders: Chris Halls <[EMAIL PROTECTED]>, Rene Engelhard <[EMAIL PROTECTED]> ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/d/dmake/dmake_4.7-4ubuntu1.dsc ++ ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/d/dmake/dmake_4.7.orig.tar.gz ++ ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/d/dmake/dmake_4.7-4ubuntu1.diff.gz ++ ++ starting test ++ + adt-run --tmp-dir tmp/dmake/tmp --output-dir tmp/dmake/out --log-file tmp/dmake/log --summary tmp/_summary --built-binaries-filter=__ --source tmp/dmake/src/dmake_4.7-4ubuntu1.dsc --- adt-virt-xenlvm --userv --distro=gutsy -- adt-run: trace: ** init adt-run: trace: ** start adt-run: trace: $ vserver: adt-virt-xenlvm --userv --distro=gutsy -- File descriptor 6 left open File descriptor 7 left open adt-run: trace: starting adt-run: trace: ** open, scratch=None File descriptor 6 left open File descriptor 11 left open File descriptor 6 left open File descriptor 11 left open adt-run: trace: * initialising adt-run: trace: * no key generation needed adt-run: trace: * reset adt-run: trace: builds ... adt-run: trace: dsc dsc0 adt-run: trace: * publish adt-run: trace: $ ftparchive: sh -ec
[Bug 154148] autopkgtest gutsy language-pack-kde-tr amd64: erroneous package!
Public bug reported: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 affects /ubuntu/language-pack-kde-tr importance high # version 1:7.10+20071012 Test executed for: gutsy binary-amd64 language-pack-kde-tr Outcome: erroneous package! blame: arg:tmp/language-pack-kde-tr/src/language-pack-kde-tr.deb deb:language-pack-kde-tr language-pack-kde-tr badpkg: installation of language-pack-kde-tr failed, exit code 100 quitting: erroneous package: installation of language-pack-kde-tr failed, exit code 100 erroneous package! This message is automatically generated by the autopkgtest package testing system. You are receiving it because: The test results appear to indicate a problem with the package and reports for package maintainers for gutsy are being directed to [EMAIL PROTECTED] The top and tail of the test log, which is intended to be sufficient to diagnose most failures, can be found below. However, in case this is not sufficient, a complete log can be found along with output files, saved temporary files, and so on, at: http://autopkgtest.ubuntu.com/autopkgtest-output/ The test environment is an amd64 Xen guest with limited amounts of memory. The relevant dependencies are installed for each test but very few other packages. Most autopkgtest reports are FTBFS problems. Please forgive this bug report if the problem is due to archive skew; in that case you've just been unlucky with the timing. Feel free to close the bug if the skew has been fixed, or will be fixed soon. If you have any questions about this service please contact me at: Ian Jackson <[EMAIL PROTECTED]> Regards, Ian - -8<- ++ fetching http://archive.ubuntu.com/ubuntu/dists/gutsy/main/binary-amd64/Packages.gz ++ ++ selecting ++ selected language-pack-kde-tr (age , score 4200280) Package: language-pack-kde-tr Priority: optional Section: translations Installed-Size: 36 Maintainer: Martin Pitt <[EMAIL PROTECTED]> Architecture: all Version: 1:7.10+20071012 Replaces: language-pack-kde-tr-base, language-pack-tr-base (<< 1:7.10+20071012), language-pack-gnome-tr-base (<< 1:7.10+20071012), language-pack-kde-tr-base (<< 1:7.10+20071012), language-pack-tr (<< 1:7.10+20071012) Depends: language-pack-kde-tr-base Pre-Depends: dpkg (>= 1.10.27ubuntu1) Filename: pool/main/l/language-pack-kde-tr/language-pack-kde-tr_7.10+20071012_all.deb Size: 2086 MD5sum: 04fb3f7d24cd6a16dd50611b4164f26a SHA1: fea04247a17b2b21184665c1dda80edd497c02d9 SHA256: f97857e80578a3f734c346a0064e854edd53ec837af5b0b9b20ab6c77f4b72fd Description: KDE translation updates for language Turkish Translation data updates for all supported KDE packages for: Turkish . language-pack-kde-tr-base provides the bulk of translation data and is updated only seldom. This package provides frequent translation updates. . Please note that you should install language-support-tr to get full support for this language. Bugs: mailto:[EMAIL PROTECTED] Origin: Ubuntu Task: edubuntu-ship-addon ++ fetching http://archive.ubuntu.com/ubuntu/pool/main/l/language-pack-kde-tr/language-pack-kde-tr_7.10+20071012_all.deb ++ ++ starting test ++ + adt-run --tmp-dir tmp/language-pack-kde-tr/tmp --output-dir tmp/language-pack-kde-tr/out --log-file tmp/language-pack-kde-tr/log --summary tmp/_summary --built-binaries-filter=__ --binaries=install --binary tmp/language-pack-kde-tr/src/language-pack-kde-tr.deb --instantiate --- adt-virt-xenlvm --userv --distro=gutsy -- adt-run: trace: ** init adt-run: trace: ** start adt-run: trace: $ vserver: adt-virt-xenlvm --userv --distro=gutsy -- File descriptor 6 left open File descriptor 7 left open adt-run: trace: starting adt-run: trace: ** open, scratch=None File descriptor 6 left open File descriptor 11 left open File descriptor 6 left open File descriptor 11 left open adt-run: trace: * initialising adt-run: trace: * no key generation needed adt-run: trace: * reset adt-run: trace: builds ... adt-run: trace: deb deb0 adt-run: trace: * register what=deb0 deb_forbuilds=install pkg=language-pack-kde-tr af=deb0-deb~tmp/language-pack-kde-tr/src/language-pack-kde-tr.deb:tmp/language-pack-kde-tr/src/language-pack-kde-tr.deb!|- adt-run: trace: instantiate instantiate1 adt-run: trace: builds done. adt-run: trace: * reset adt-run: trace: tests ... adt-run: trace: test deb deb0 adt-run: trace: * register what=deb0 deb_fortests=install pkg=language-pack-kde-tr af=deb0-deb~tmp/language-pack-kde-tr/src/language-pack-kde-tr.deb:tmp/language-pack-kde-tr/src/language-pack-kde-tr.deb!|- adt-run: trace: test instantiate instantiate1 adt-run: trace: ** reset ** File descriptor 6 left open File descriptor 11 left open File descript
Re: [Bug 94230] Re: thumbnails privacy violation hazard
Loïc Minier writes ("[Bug 94230] Re: thumbnails privacy violation hazard"): > What's the difference with a browser cache? The browser cache contains images you've viewed on websites, ie probably not images that you took and that are probably not of you. (Also browser cache privacy problems are more widely publicised and there are some options available for mitigating the risks.) Ian. -- thumbnails privacy violation hazard https://bugs.launchpad.net/bugs/94230 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 149497] Re: apt-get update returns error
** Changed in: apt (Ubuntu) Sourcepackagename: dpkg => apt -- apt-get update returns error https://bugs.launchpad.net/bugs/149497 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153382] debug log madness after segfault
Public bug reported: Binary package hint: nautilus As I report in bug 153381, I managed to get nautilus to segfault. This resulted in it spinning on the CPU while continuously writing the following message over and over again into nautilus-debug-log.txt: 0x8177510 2007/10/16 19:10:32.9014 (USER): debug log dumped due to signal 11 nautilus (or whatever library it is using) should take steps to ensure that if a segfault occurs when writing the debug log, it doesn't then attempt once more to write the debug log. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: iso-testing -- debug log madness after segfault https://bugs.launchpad.net/bugs/153382 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153381] segfault induced by user switching
Public bug reported: Binary package hint: nautilus I switched users back and forth a few times during testing of a gutsy d-i 20071016.1 i386 oem install. One of the users' sessions seems to have failed to shut down properly. I logged in again to be confronted with four warnings of the form The panel encountered a problem while loading "OAFID:GNOME_FastUserSwitchApplet" The panel encountered a problem while loading "OAFID:GNOME_Deskbar_Applet" The panel encountered a problem while loading "OAFID:GNOME_Panel_TrashApplet" The panel encountered a problem while loading "OAFID:GNOME_MixerApplet" I opened a terminal (which worked) and investigated and found that the nautilus from the previous session was spinning on the CPU. It was continuously writing the following message over and over again into nautilus-debug-log.txt: 0x8177510 2007/10/16 19:10:32.9014 (USER): debug log dumped due to signal 11 I have sent it a SIGSTOP. Please advise what steps I should take to preserve appropriate debug information. (Launchpad suggested that this might be related to bug 150471. In answer to the question asked there: compiz is not enabled on this system because it has a blacklisted video card.) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- segfault induced by user switching https://bugs.launchpad.net/bugs/153381 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153336] Re: oem-config crash
AFAICT from my retest there are two bugs here: * The "Step 1 of 4" counter does not advance " There is no confirmation, after completing the final screen, that everything is OK. Instead the X server just quits and presents the user with a login prompt. This is quite jarring. ** Summary changed: - oem-config crash + oem-config sudden exit -- oem-config sudden exit https://bugs.launchpad.net/bugs/153336 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153336] oem-config crash
Public bug reported: Binary package hint: oem-config I just did an install of 20071016.1 gutsy d-i i386 in OEM mode (with auto resize). I installed in French (with UK keyboard and London timezone). I made only one change in the oem boot: to use Synaptic to install libadns1-bin. I then ran the "prepare for shipping" program. On the reboot when I got the prompts I asked for Dutch as a language, London timezone, UK keyboard (which was sensibly the default), but after entering the new user details (step 1 of 4) the preparer crashed - the X server died and I was presented with a gdm. This gdm session did allow me to log in as the created user. I'm going to try this again with no language switching, with Erase Disk, and without making any changes during the OEM boot. ** Affects: oem-config (Ubuntu) Importance: Undecided Status: New -- oem-config crash https://bugs.launchpad.net/bugs/153336 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153310] oem-prepare cannot cope if oem creates user (?)
Public bug reported: Binary package hint: oem-config I installed gutsy 20071016.1 i386 d-i in oem mode in English (with auto- resize of another gutsy test install): During the oem boot I: * Fiddled a bit with the Software Sources to remove the CD entry * Installed libadns1-bin using Synaptic * Created a user called "guest" using System / Administration / Users and Groups, in the most obvious way Then I double-clicked on "prepare for shipping to end-user" which appeared to work, and rebooted. When I rebooted the usual "enter your details" dialogue appeared as expected. I provided my language (Dutch), keyboard (British English) and timezone (Language) and was asked for my name and username and password. When I confirmed my entering the password for the second time, the X server died immediately (black screen) and I was presented with a gdm prompt. The user and password I had provided during user firstboot did not work (I didn't try the guest user). I rebooted into the other install for forensics and found that the main admin user did not exist. I presume that this problem was caused by the fact that I created a user during the OEM preparation. I think this ought to be supported. ** Affects: oem-config (Ubuntu) Importance: Undecided Status: New ** Tags: iso-testing -- oem-prepare cannot cope if oem creates user (?) https://bugs.launchpad.net/bugs/153310 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153310] Re: oem-prepare cannot cope if oem creates user (?)
I have filed another bug about these events, regarding the poor error handling. That other bug is bug 153311. -- oem-prepare cannot cope if oem creates user (?) https://bugs.launchpad.net/bugs/153310 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153311] poor error handling - lack of recovery
Public bug reported: Binary package hint: oem-config I installed gutsy 20071016.1 i386 d-i in oem mode in English (with auto- resize of another gutsy test install): During the oem boot I: * Fiddled a bit with the Software Sources to remove the CD entry * Installed libadns1-bin using Synaptic * Created a user called "guest" using System / Administration / Users and Groups, in the most obvious way Then I double-clicked on "prepare for shipping to end-user" which appeared to work, and rebooted. When I rebooted the usual "enter your details" dialogue appeared as expected. I provided my language (Dutch), keyboard (British English) and timezone (Language) and was asked for my name and username and password. When I confirmed my entering the password for the second time, the X server died immediately (black screen) and I was presented with a gdm prompt. The user and password I had provided during user firstboot did not work (I didn't try the guest user). I rebooted into the other install for forensics and found that the main admin user did not exist. I am filing another bug about the fact that this problem was apparently caused by the fact that I created a user during the OEM preparation which I think ought to be supported. This bug is about the fact that the oem firstboot program crashed leaving me with an unuseable setup. When the oem firstboot fails it ought to at least present the user with a useful error message and preferably it should try to avoid getting into a situation where the install is irrecoverably broken when it fails. ** Affects: oem-config (Ubuntu) Importance: Undecided Status: New ** Tags: iso-testing -- poor error handling - lack of recovery https://bugs.launchpad.net/bugs/153311 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153311] Re: poor error handling - lack of recovery
The other bug I refer to, about support for oem-created users, is bug 153310. -- poor error handling - lack of recovery https://bugs.launchpad.net/bugs/153311 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs