Bug#1059089: Please add virtio-snd module
Correction: CONFIG_SND_VIRTIO instead of CONFIG_VIRTIO_SND.
Bug#1059089: Please add virtio-snd module
Package: linux Version: 6.5.13 Can we add CONFIG_VIRTIO_SND to debian/config/config as module ? It's useful when I want to hear something from inside virtual machine.
Bug#1054403: python3-plotly: Does not draw waterfall charts
Package: python3-plotly
Version: 5.15.0+dfsg1-1
I can't get Waterfall graph to render, it seems to just render a
regular line chart. The same graph works on 5.4.1+dfsg-1.
https://plotly.com/python/waterfall-charts/
sample modified to output HTML
```
import plotly.graph_objects as go
fig = go.Figure(go.Waterfall(
name = "20", orientation = "v",
measure = ["relative", "relative", "total", "relative", "relative",
"total"],
x = ["Sales", "Consulting", "Net revenue", "Purchases", "Other expenses",
"Profit before tax"],
textposition = "outside",
text = ["+60", "+80", "", "-40", "-20", "Total"],
y = [60, 80, 0, -40, -20, 0],
connector = {"line":{"color":"rgb(63, 63, 63)"}},
))
fig.update_layout(
title = "Profit and loss statement 2018",
showlegend = True
)
fig.write_html("example.html")
```
Bug#1051949: ITS: binfmtc
On Fri, 15 Sep 2023 03:02:15 +0900, Bastian Germann wrote: > > Source: binfmtc > > binfmtc does not seem to be maintained anymore. > I intend to salvage the package with the plan to orphan it in three weeks. > Please notify me if you object. > What does ITS stand for ?
Bug#1042062: RFP: mdformat -- Markdown formatter that can be used to enforce a consistent style in Markdown files.
Package: wnpp Severity: wishlist * Package name: mdformat Version : 0.7.16 Upstream Contact: Taneli Hukkinen * URL : https://pypi.org/project/mdformat/ * License : MIT Programming Lang: python Description : Markdown formatter that can be used to enforce a consistent style in Markdown files.
Bug#1024997: what kind of bug was it?
Hi, On Sat, 01 Jul 2023 06:35:06 +0900, Preuße, Hilmar wrote: > > [1 ] > [1.1 ] > [1.1.1 ] > On 26.06.2023 08:26, Junichi Uekawa wrote: > > Hi Junichi, > > > From my guess it's some kind of buffer management issue; what was the > > bug and is there a minimal fix ? > > > To be honest: I don't really care. I know the issue is solved in > texinfo 7.0.x, hence I perform no further investigation. Uploading TI > 7.0 to unstable however will break a few packages [1], currently I'm > waiting that at least the new version of octave hits unstable. > > If you think this could be a security issue, let me know. As bookworm shipped with this bug which dumps some kind of corrupted buffer content, I am concerned this can be a security issue.
Bug#1024997: what kind of bug was it?
Hi, From my guess it's some kind of buffer management issue; what was the bug and is there a minimal fix ?
Bug#1039043: update-info-dir does not honor system locale
Package: install-info
Version: 6.8-6+b1
Because update-info-dir unsets (and unexports) LANGUAGE and LANG settings and
only sets a shell variable by importing /etc/default/locale, locale is not set.
There's two major things that seem to be an issue
1. export them.
2. also handle LC_ALL (and other LC_ variables) which tends to overrride
LANGUAGE/LANG variables.
Suggested change:
commit dd6e2970da0a3c675889da8c93feaab7aaca741a
Author: Junichi Uekawa
Date: Sun Jun 25 08:33:19 2023 +0900
Export locale variables so that they actually take effect.
diff --git a/hoge/update-info/update-info-dir b/hoge/update-info/update-info-dir
index 2856647a..d4bffd36 100755
--- a/hoge/update-info/update-info-dir
+++ b/hoge/update-info/update-info-dir
@@ -15,12 +15,16 @@ set -e
# the system wide settings. See bug #536476
unset LANGUAGE
unset LANG
+unset LC_ALL
if [ -r /etc/environment ] ; then
. /etc/environment
fi
if [ -r /etc/default/locale ] ; then
. /etc/default/locale
fi
+export LANGUAGE
+export LANG
+export LC_ALL
Help ()
{
Bug#1038414: make podman error message about storage driver friendlier
Package: podman Version: 4.3.1+ds1-8+b1 After upgrade from bullseye to bookworm, there's error from local storage format. ERRO[] User-selected graph driver "vfs" overwritten by graph driver "overlay" from database - delete libpod local files to resolve. May prevent use of images created by other tools upstream seems to have better error message https://github.com/containers/podman/pull/16311 worth backporting? (might be challenging). Warning disappeared after deleting ~/.local/share/containers/ and recreating.
Bug#1038386: get_nprocs_conf value higher than is present CPUs.
Package: libc6 Version: 2.36-9 Documentation tells me that sysconf(_SC_NPROCESSORS_CONF) get_nprocs_conf() gives me the upper bound of CPUs and sysconf(_SC_NPROCESSORS_ONLN) get_nprocs() gives the currently online CPUs. get_nprocs_conf seems to return "possible" value, and it seems like the value is 32 on my system. However from reading Documentation/ABI/testing/sysfs-devices-system-cpu "present" might be more suited instead of "possible". (the value used to be 12 on bullseye kernel, and bookworm kernel started reporting 32 for possible, which maybe possible but not very useful as only 12 is present on my system.) I think one of the following could be useful - use "present" instead of possible for get_nprocs_conf - update get_nprocs_conf to document that it's a theoretical value and not the number of present cpus. - introduce another API for the present CPUs that may or may not be online.
Bug#1035838: gbp-pq manpage could refer to the moved location
Package: git-buildpackage
Version: 0.9.22
gbp-pq manpage refers to a page that says the content has moved.
I think it can refer to the local html copy[1], or the internet copy.
[1] /usr/share/doc/git-buildpackage/manual-html/gbp.patches.html
diff -ur git-buildpackage-0.9.22{,-}
diff -ur git-buildpackage-0.9.22/docs/manpages/gbp-pq.xml
git-buildpackage-0.9.22-/docs/manpages/gbp-pq.xml
--- git-buildpackage-0.9.22/docs/manpages/gbp-pq.xml2019-01-09
04:15:13.0 +0900
+++ git-buildpackage-0.9.22-/docs/manpages/gbp-pq.xml 2023-05-10
08:49:24.326208037 +0900
@@ -54,7 +54,7 @@
called patch-queue/master.
-See https://honk.sigxcpu.org/piki/development/debian_packages_in_git/";>
+See https://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.patches.html";>
for example workflows.
Bug#1026126: update on crosvm dependencies
more dependencies, named-lock and bitreader uploaded to NEW queue.
Bug#1026126: crosvm update
After removing all optional dependencies, crosvm builds with cargo now with changes at: https://github.com/dancerj/crosvm/tree/+wip-debian
Bug#1029536: wine64-stable ENOENT
> > The -stable suffix was added for the Debian alternatives system. While > I don't expect an issue with adding an /usr/lib/wine/wine64-stable > link, I wonder if the whole issue is really a bug (still probably a > regression, which I can't comment on since I'm not involved in current > packaging) or wrong usage. Somehow /usr/bin/wine-stable has correct files in the right place, so /usr/bin/wine-stable works /usr/bin/wine64-stable fails because of missing files. Should /usr/bin/wine64-stable be there at all?
Bug#1029536: wine64-stable ENOENT
> [Ex-maintainer here] > > The -stable suffix was added for the Debian alternatives system. While > I don't expect an issue with adding an /usr/lib/wine/wine64-stable > link, I wonder if the whole issue is really a bug (still probably a > regression, which I can't comment on since I'm not involved in current > packaging) or wrong usage. /usr/bin/wine-stable, and /usr/bin/wine64-stable exist but do not work; shouldn't they either be removed or fixed with a symlink.
Bug#1026126: (no subject)
found that cargo debstatus has a bug that it drops optional dependencies from the dependency tree and I still have bunch of optional dependencies (gdbstub etc) to go.
Bug#1029536: wine64-stable ENOENT
`wine64 wineboot` runs, /usr/lib/wine/wine64 is there.
`wine64-stable wineboot` fails, /usr/lib/wine/wine64-stable is not there.
according to strace:
execve("/usr/lib/wine/wine64-stable", ["/usr/lib/wine/wine64-stable",
"wineboot"], 0x7e641390 /* 21 vars */) = -1 ENOENT (No such file or directory)
write(2, "wine: ", 6wine: ) = 6
write(2, "could not exec the wine loader\n", 31could not exec the wine loader
) = 31
and indeed the file is not there.
Not sure what it was before.
Bug#1026126: crosvm
I have some working intrusive-collections packages: https://salsa.debian.org/rust-team/debcargo-conf/-/merge_requests/436 I think the remaining is argh packages and other dependencies can be work around on crosvm side.
Bug#1026126: update on crosvm dependencies
enumn and remain are ACCEPTED. remaining thing: - intrusive-collections I believe someone else is actively working on argh.
Bug#1026126: Dependencies for crosvm.
Ran cargo debstatus and looked through the output, I think here's what's missing: remain v0.2.3 uuid v0.8.2 -- 1.2.1 is packaged heck v0.3.3 -- 0.4.0 is packaged argh_derive v0.1.8 argh v0.1.8 memoffset v0.5.6 -- 0.6.5 is packaged, can we use that instead? intrusive-collections v0.9.4 enumn v0.1.4 -- probably can be removed? terminal_size v0.1.17 -- 0.2.1 is packaged. document-features v0.2.6
Bug#1026126: crosvm -- The Chrome OS Virtual Machine Monitor
Package: wnpp Severity: wishlist X-Debbugs-CC: debian-r...@lists.debian.org X-Debbugs-CC: debian-de...@lists.debian.org Package name: crosvm Version : 0.0.1? Upstream Contact: crosvm-...@chromium.org URL : https://chromium.googlesource.com/crosvm/crosvm/ License : BSD 3-clause Programming Lang: Rust Description : The Chrome OS Virtual Machine Monitor crosvm is a Virtual Machine Monitor for full system emulation using KVM, useful for running Linux guest OS inside a virtual machine of the same architecture as the host, similar to qemu. crosvm is designed with a multi-process architecture where each emulated device is running inside a sandbox.
Bug#927408: novnc upstream 1.2
Hi, It seems like the latest upstream version is 1.2. https://github.com/novnc/noVNC/releases/tag/v1.2.0 Do you need help updating ?
Bug#990088: lld: please provide lld-link symlink
Package: lld Version: 1:11.0-51+nmu5 Severity: wishlist Dear Maintainer, Seems like lld-11 package provides /usr/bin/lld-link-11 symlink, and some documentation refers to lld-link. Please provide a lld-link symlink. [1] https://github.com/uchan-nos/mikanos-build/blob/master/day01/c/Makefile#L7 -- System Information: Debian Release: 11.0 APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-7-amd64 (SMP w/12 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lld depends on: ii lld-11 1:11.0.1-2 lld recommends no packages. lld suggests no packages. -- no debconf information
Bug#989030: memtest86+: New upstream version available v5.31b
Package: memtest86+
Version: 5.01-3.1
Severity: wishlist
Dear Maintainer,
According to memtest.org site, there's a new upstream version available for
testing.
https://www.memtest.org/#downcode
In diff I see something like:
+ }else if (mem_devs[i]->size == 0x7FFF){
+ // SMBIOS 2.7+
+ size_in_mb = mem_devs[i]->ext_size;
+ itoa(string, size_in_mb);
+ cprint(yof, POP2_X+4+18, st
so might be interesting.
-- System Information:
Debian Release: 11.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-6-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to ja_JP.UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages memtest86+ depends on:
ii debconf [debconf-2.0] 1.5.75
memtest86+ recommends no packages.
Versions of packages memtest86+ suggests:
pn grub-pc | grub-legacy
pn hwtools
pn kernel-patch-badram
pn memtest86
pn memtester
pn mtools
-- debconf information:
shared/memtest86-run-lilo: false
Bug#989001: follow up on memtest86+ issue
Hi, Seems like I was too quick to decide it was graphics mode, after setting /etc/default/grub with: # Uncomment to disable graphical terminal (grub-pc only) GRUB_TERMINAL=console with a text mode console, after selecting memtest86+ in grub menu the screen is black and nothing appears. Might be something with the machine.
Bug#989001: memtest86+: Fails to run in Grub graphical(?) mode?
Package: memtest86+ Version: 5.01-3.1 Severity: normal Dear Maintainer, I think I default installed Debian bullseye and Grub is configured to use graphical framebuffer and render text. When invoked from there memtest86+ doesn't seem to update the screen at all (presumably trying to write to text buffer?). -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-6-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages memtest86+ depends on: ii debconf [debconf-2.0] 1.5.75 memtest86+ recommends no packages. Versions of packages memtest86+ suggests: pn grub-pc | grub-legacy pn hwtools pn kernel-patch-badram pn memtest86 pn memtester pn mtools -- debconf information: shared/memtest86-run-lilo: false
Bug#975287: rust-clippy is in experimental now
Hi, I've noticed that 1.52.1 includes rust-clippy package, hence this RFP can be considered closed.
Bug#988533: ifupdown: please enable systemd configuration for waiting for network interfaces
Package: ifupdown Version: 0.8.36 Severity: normal Dear Maintainer, The default network configuration for Debian is ifupdown after running debian-installer, however systemd network-online.target by default does not wait for ifupdown-wait-online.service. sudo systemctl enable ifupdown-wait-online.service after installation makes the desired effect but before doing this network services start before DHCP is completed. Shouldn't the default to be to enable ifupdown-wait-online.service ? -- Package-specific info: --- /etc/network/interfaces: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug eno1 iface eno1 inet dhcp # This is an autoconfigured IPv6 interface iface eno1 inet6 auto ethernet-wol g --- /etc/network/interfaces.d/*: cat: '/etc/network/interfaces.d/*': No such file or directory --- up and down scripts installed: /etc/network/if-down.d: total 0 lrwxrwxrwx 1 root root 32 Feb 26 06:19 wpasupplicant -> ../../wpa_supplicant/ifupdown.sh /etc/network/if-post-down.d: total 0 lrwxrwxrwx 1 root root 32 Feb 26 06:19 wpasupplicant -> ../../wpa_supplicant/ifupdown.sh /etc/network/if-pre-up.d: total 4 -rwxr-xr-x 1 root root 344 Jun 30 2016 ethtool lrwxrwxrwx 1 root root 32 Feb 26 06:19 wpasupplicant -> ../../wpa_supplicant/ifupdown.sh /etc/network/if-up.d: total 4 -rwxr-xr-x 1 root root 1685 Jun 30 2016 ethtool lrwxrwxrwx 1 root root 32 Feb 26 06:19 wpasupplicant -> ../../wpa_supplicant/ifupdown.sh -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-6-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ifupdown depends on: ii adduser 3.118 ii iproute2 5.10.0-4 ii libc6 2.31-11 ii lsb-base 11.1.0 Versions of packages ifupdown recommends: ii isc-dhcp-client [dhcp-client] 4.4.1-2.2 Versions of packages ifupdown suggests: ii ppp 2.4.9-1+1 pn rdnssd -- no debconf information
Bug#986029: [Virtualsquare] Bug#986029: fuse-umfuse-fat: newer upstream version available?
Thanks for the info, looking forward to the new version! On Sun, 28 Mar 2021 19:14:16 +0900, Renzo Davoli wrote: > > Hi Junichi, > > Virtualsquare's FAT module for fuse (compatible with umfuse and vufuse) has > been rewritten. > [1] is the new source code based on the FAT file system module for embedded > systems fatfs by ChaN. > The virtualsquare team is working to package this new implementation as a > Debian package as > soon as possible. It is in the queue, maybe we'll work on it just after > bullseye's release. > ChaN's module is mode stable and complete than our former libfat. > > The source code of the current fuse-umfuse-fat package can be found here > (it is a subdir of the view-os source tree): > [2] [3] > > [1] https://github.com/virtualsquare/fusefatfs > [2] https://github.com/virtualsquare/view-os/tree/master/fuse-modules/fat > [3] https://sourceforge.net/projects/view-os/ > > * wishes, > > renzo > > On Sun, Mar 28, 2021 at 05:07:59PM +0900, Junichi Uekawa wrote: > > Source: fuse-umfuse-fat > > Version: 0.1a-1.2 > > Severity: wishlist > > > > Dear Maintainer, > > > > I was looking at some issues with fusefat and noticed that the > > upstream wiki page [1] links to github repository [2]. Is this a new > > upstream release? > > > > One thing that confuses me is that history file [3] seems to suggest > > that the release would have been 0.06 by June 2008, so not sure if > > this was the project that was packaged in Debian. > > > > [1] http://wiki.virtualsquare.org/#!repos.md > > [2] https://github.com/virtualsquare/fusefatfs > > [3] > > https://github.com/virtualsquare/fusefatfs/blob/master/fatfs/source/00history.txt > > > > -- System Information: > > Debian Release: 10.8 > > APT prefers stable > > APT policy: (500, 'stable') > > Architecture: amd64 (x86_64) > > > > Kernel: Linux 5.4.88-12224-gf05236dbdecf (SMP w/8 CPU cores; PREEMPT) > > Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set > > to ja_JP.UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to > > ja_JP.UTF-8) > > Shell: /bin/sh linked to /bin/dash > > Init: systemd (via /run/systemd/system) >
Bug#986065: fuse-umfuse-fat: Please add other architectures for fusefat
Source: fuse-umfuse-fat Version: 0.1a-1.2 Severity: wishlist Dear Maintainer, Observing the source code for fusefat I think it isn't architecture agnostic; is this because of build-dependency to libumlib-dev that fusefat can't be installed? Is it possible to make that build-dependency be arch-optional for now and allow other arch to build? (I'm interested in aarch64 and armel packages). -- System Information: Debian Release: 10.8 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.88-12224-gf05236dbdecf (SMP w/8 CPU cores; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to ja_JP.UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to ja_JP.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#986029: fuse-umfuse-fat: newer upstream version available?
Source: fuse-umfuse-fat Version: 0.1a-1.2 Severity: wishlist Dear Maintainer, I was looking at some issues with fusefat and noticed that the upstream wiki page [1] links to github repository [2]. Is this a new upstream release? One thing that confuses me is that history file [3] seems to suggest that the release would have been 0.06 by June 2008, so not sure if this was the project that was packaged in Debian. [1] http://wiki.virtualsquare.org/#!repos.md [2] https://github.com/virtualsquare/fusefatfs [3] https://github.com/virtualsquare/fusefatfs/blob/master/fatfs/source/00history.txt -- System Information: Debian Release: 10.8 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.88-12224-gf05236dbdecf (SMP w/8 CPU cores; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to ja_JP.UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to ja_JP.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#921441: dsh: Suggested package "update-cluster" not available
> > I wanted to try dsh with the background to check (upgrade) all nodes on our > Ganeti cluster (see [1]). > > This is the first time I wanted to use dsh. > > Unfortunately, the suggested package "update-cluster" is not available on > Debian/buster AMD64. > > Is this a known issue? > If not, shall I open a bug report? > maybe we should remove suggestion to a removed package. update-cluster was a way to manage list of hosts. I doubt many people use NIS host groups these days, so how do people manage the list of hosts these days?
Bug#775463: psgml: Loading XML, HTML or SGML crashes
I initially thought I could reproduce with 'emacs -q' but not. will need to dig further into why this is the case. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#775463: psgml: Loading XML, HTML or SGML crashes
Package: psgml
Version: 1.4.0-5
Severity: normal
Dear Maintainer,
Loading anything that is not html5 seems to crash psgml.
Procedure:
(require 'psgml-html)
open AndroidManifest.xml (or any XML or HTML file that is not HTML5)
The next time I try to insert a tag crashes with this backtrace:
Debugger entered--Lisp error: (cl-assertion-failed (not (eq sgml-scratch-buffer
(default-value (quote sgml-scratch-buffer)
signal(cl-assertion-failed ((not (eq sgml-scratch-buffer (default-value
(quote sgml-scratch-buffer))
sgml-cleanup-entities()
sgml-need-dtd()
sgml-parse-to(1)
sgml-find-context-of(1)
sgml-parse-to-here()
sgml-read-element-name("Element: ")
(list (sgml-read-element-name "Element: ") sgml-leave-point-after-insert)
call-interactively(sgml-insert-element nil nil)
command-execute(sgml-insert-element)
-- System Information:
Debian Release: 8.0
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to ja_JP.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages psgml depends on:
ii dpkg 1.17.23
ii emacs24 24.4+1-4.1
ii install-info 5.2.0.dfsg.1-6
ii sgml-base 1.26+nmu4
ii sgml-data 2.0.10
ii ucf 3.0030
Versions of packages psgml recommends:
ii opensp 1.5.2-11.1
Versions of packages psgml suggests:
pn debiandoc-sgml
pn linuxdoc-sgml
ii make4.0-8
pn w3-dtd-mathml
pn w3c-dtd-xhtml
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765857: [cowbuilder] Unable to create Jessie i386 environment on amd64 host, pbuilder works on its own
Scratch that, creation is something different. I have no idea. At Wed, 05 Nov 2014 15:30:28 +, OmegaPhil wrote: > > [1 ] > On 05/11/14 06:39, Junichi Uekawa wrote: > > > > cowbuilder uses LD_PRELOAD'ed library that it won't have a chance of > > working on a different architecture (well, if you implement enough it > > probably works). > > > > > >> On my Testing amd64 install, the following call fails: > >> > >> = > >> > >> # sudo HOME=$HOME eatmydata cowbuilder --create --mirror > >> http://10.1.0.3:3142/ftp.uk.debian.org/debian --basepath > >> /var/cache/pbuilder/jessie-i386-test/base.cow --distribution jessie > >> --debootstrapopts --arch --debootstrapopts i386 > > > This is all new to me, but I remember successfully doing it before. > > What about the fact this issue affects a bogstandard Jessie amd64 > environment creation, which is the current installed environment? > > > -- > Libre software on Github: https://github.com/OmegaPhil > FSF member #9442 > > [2 OpenPGP digital signature ] > No public key for 17D23C7DFDC2F38F created at 2014-11-06T00:30:36+0900 using > RSA -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765857: [cowbuilder] Unable to create Jessie i386 environment on amd64 host, pbuilder works on its own
cowbuilder uses LD_PRELOAD'ed library that it won't have a chance of working on a different architecture (well, if you implement enough it probably works). > On my Testing amd64 install, the following call fails: > > = > > # sudo HOME=$HOME eatmydata cowbuilder --create --mirror > http://10.1.0.3:3142/ftp.uk.debian.org/debian --basepath > /var/cache/pbuilder/jessie-i386-test/base.cow --distribution jessie > --debootstrapopts --arch --debootstrapopts i386 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#760359: libssh2-1-dev: pkgconfig missing dependency on -lgpg-error
Package: libssh2-1-dev Version: 1.4.3-3 Severity: normal Dear Maintainer, /usr/lib/x86_64-linux-gnu/pkgconfig/libssh2.pc has line: Libs.private: -lgcrypt however, libgcrypt depends on libgpg-error, so static linking fails. This should be: Libs.private: -lgcrypt -lgpg-error -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to ja_JP.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libssh2-1-dev depends on: ii libgcrypt20-dev 1.6.1-3 ii libssh2-11.4.3-3 libssh2-1-dev recommends no packages. libssh2-1-dev suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#728279: cowbuilder: Document --save option in man-page
I think it's --save-after-login you mention. It is documented in pbuilder.8 At Wed, 30 Oct 2013 09:05:11 +0100, Ralf Jung wrote: > > Package: cowbuilder > Version: 0.73 > Severity: normal > > Dear Maintainer, > > the manpage does not mention the "--save" parameter which allows to --login > to the cowbuilder > and do persistent changes. > I don't know how foten I already had to look up this argument elsewhere, als > I only rarely need it, > but it should really be mentioned in the manpage. > > Kind regards > Ralf > > -- System Information: > Debian Release: jessie/sid > APT prefers testing > APT policy: (990, 'testing'), (100, 'unstable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 3.10-3-amd64 (SMP w/4 CPU cores) > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > > Versions of packages cowbuilder depends on: > ii cowdancer 0.73 > ii libc6 2.17-93 > ii pbuilder 0.215 > > cowbuilder recommends no packages. > > cowbuilder suggests no packages. > > -- no debconf information > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#708566: library -dev naming policy encourages unnecessary transitions
Hi, At Mon, 20 May 2013 19:33:43 -0700, Russ Allbery wrote: > > Guillem Jover writes: > > > Perhaps, but I think we just lack better documentation and advice when > > it comes to shared library handling in general. > > > There was an attempt by Junichi Uekawa (CCed) some time ago [L], but > > AFAIR some people shunned it because supposedly it contained inaccuracies > > or suboptimal advice (I've to confess I never reviewed it). IMO these > > should have been corrected instead of trying to banish it from Debian. > > I think something like that should be revived, reviewed and subsumed > > into the policy manual or the devref. > > > [L] <http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html> > > I'm wholeheartedly in favor of this, and even had some thoughts from time > to time about helping with (or adopting) that guide and rolling it into > Policy. But I haven't been doing a very good job finding time for Debian > things lately. I'd love to see someone take this on. Some preconditions from that time has changed, and major change since then has been that binary-only uploads are much easier infrastructure-wise than before that there's less reason to rename a -dev package than when this was authored about 8 years ago. The last time I seriously worked on this document was 2006 and in the hindsight, I was learning this stuff as I wrote this document, there must be inaccuracies. But I lack the motivation to revise this document now. > > -- > Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#704744: pbuilder: umounts /{dev,run}/shm of the *host* system
At Fri, 05 Apr 2013 13:55:16 +0200,
Thorsten Glaser wrote:
>
> Package: pbuilder
> Version: 0.215
0.215 should have already fixed it, are you sure?
0.214 would do that.
> Severity: critical
> Justification: breaks unrelated software
>
> I’ve just did the following:
>
> ① get https://www.mirbsd.org/cvs.cgi/contrib/hosted/tg/deb/pbuilderrc?rev=1.34
> and install that file as /etc/pbuilderrc
> ② edit the MIRROR_wheezy line to use a local mirror
> ③ remove ~/.pbuilderrc
> ④ run sudo env DIST=wheezy cowbuilder --create
> ⑤ run sudo env DIST=wheezy cowbuilder --update
>
> I’ve had /run/shm mounted a tmpfs before, as is normal for
> a system running sid, and /dev/shm is a symbolic link pointing
> to it.
>
> Now, I don’t have that any more:
>
> tglase@tglase:~ $ mount | fgrep shm; echo $?
>
> 1
> tglase@tglase:~ $ ls -la /{dev,run}/shm
>
> lrwxrwxrwx 1 root root 8 Apr 3 09:55 /dev/shm -> /run/shm
>
> /run/shm:
> total 0
> drwxr-xr-x 2 root root 40 Apr 5 13:49 .
> drwxr-xr-x 26 root root 980 Apr 5 13:45 ..
>
> This breaks unrelated software on the system, i.e. anything
> that uses /dev/shm/ stuff. Additionally, it will *remove*
> everything currently in there.
>
> I don’t know if it was the --create or the --upgrade though.
>
> Running sudo mount -t tmpfs swap /run/shm followed by
> another instance of sudo env DIST=wheezy cowbuilder --update
> however keeps the current contents of /dev/shm/ intact, so
> I believe it was the --create operation. Similarily, running
> sudo env DIST=wheezy cowbuilder --build feistermops_51.dsc
> to compile a local package keeps it there.
>
> -- System Information:
> Debian Release: 7.0
> APT prefers unstable
> APT policy: (500, 'unstable')
> Architecture: i386 (i686)
>
> Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
> Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/mksh-static
>
> Versions of packages pbuilder depends on:
> ii coreutils 8.13-3.5
> ii debconf [debconf-2.0] 1.5.49
> ii debianutils4.3.4
> ii debootstrap1.0.48
> ii dpkg-dev 1.16.10
> ii wget 1.14-1
>
> Versions of packages pbuilder recommends:
> ii devscripts 2.12.6
> ii fakeroot1.18.4-2
> ii sudo1.8.5p2-1+nmu1
>
> Versions of packages pbuilder suggests:
> ii cowdancer 0.72
> pn gdebi-core
> pn pbuilder-uml
>
> -- Configuration Files:
> /etc/bash_completion.d/pbuilder [Errno 2] No such file or directory:
> u'/etc/bash_completion.d/pbuilder'
>
> -- debconf information:
> pbuilder/mirrorsite: http://mirror.virt.tarent.de/mirror/ubuntu
> pbuilder/nomirror:
> * pbuilder/rewrite: false
>
> ___
> Pbuilder-maint mailing list
> pbuilder-ma...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pbuilder-maint
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#704577: pbuilder: please update manual for use alternative compilers
At Wed, 3 Apr 2013 15:06:06 +0900, Hideki Yamane wrote: > > >From 3707d379f73cf6a86c5418e8e64e5a67010fec7c Mon Sep 17 00:00:00 2001 > From: Hideki Yamane > Date: Wed, 3 Apr 2013 15:02:59 +0900 > Subject: [PATCH] mention hook script instead of pentium-builder > > --- > Documentation/pbuilder-doc.xml | 24 +++- > 1 file changed, 3 insertions(+), 21 deletions(-) > > diff --git a/Documentation/pbuilder-doc.xml b/Documentation/pbuilder-doc.xml > index 8d4073b..d958ca3 100644 > --- a/Documentation/pbuilder-doc.xml > +++ b/Documentation/pbuilder-doc.xml > @@ -469,27 +469,9 @@ > > Most packages are compiled with gcc > or g++ > - and using the default compiler version, which was gcc 2.95 for Debian > GNU/Linux 3.0 (i386). > - However, Debian 3.0 was distributed with other compilers, under package > names > -such as gcc-3.2 for gcc compiler > - version 3.2. > - It was therefore possible to try compiling packages against different > - compiler versions. > - pentium-builder provides an infrastructure for > - using a different compiler for building packages than the default gcc, > by > - providing a wrapper script called gcc which calls the real gcc. > - To use pentium-builder in > pbuilder, it is possible to set up the > - following in the configuration: > - > -EXTRAPACKAGES="pentium-builder gcc-3.2 g++-3.2" > -export DEBIAN_BUILDARCH=athlon > -export DEBIAN_BUILDGCCVER=3.2 > - > - > - It will instruct pbuilder to install the > pentium-builder package > - and also the GCC 3.2 compiler packages inside the chroot, > - and set the environment variables required for > - pentium-builder to function. > + and using the default compiler version which was gcc 4.7 for Debian > GNU/Linux 7.0 (amd64), > + but you can try compiling packages against different compilers (like > clang) > + by using D65various-compiler-support in hook > directory. I think it would be good to have examples of what the configuration would be. > > > > -- > 1.7.10.4 > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700290: pbuilder: clang support
At Fri, 8 Mar 2013 14:38:24 +0900,
Hideki Yamane wrote:
>
>
by the way,
asn1c)
asn1c is a compiler for ASN.1 which probably won't compile any C program, is
that a joke or did you actually find a use for it?
--
dancer@{netfort.gr.jp,debian.org}
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#702102: fails to upgrade (cowbuilder) chroot
I've read the full thread now, sorry for the quick response, I was working down the list. At Tue, 26 Mar 2013 13:46:08 +0100, Michael Biebl wrote: > > [1 ] > Am 26.03.2013 09:48, schrieb Junichi Uekawa: > > not enough information in the bug, 702811 seems to be a better bug. > > Say what? Have you read the full bug report, including the analysis that > it is because of /run/shm vs /dev/shm? > > It's trivial to reproduce the bug this way. So I don't understand which > information you are missing > > Michael > > > -- > Why is it that all of the instruments seeking intelligent life in the > universe are pointed away from Earth? > > [2 OpenPGP digital signature ] > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#703406: cowbuilder deletes content of bind-mounted directories
Hi,
Thanks for the patch, will apply in next release.
At Tue, 19 Mar 2013 10:11:28 +0100,
Jean-Baptiste Lallement wrote:
>
> [1 ]
> Package: cowdancer
> Version: 0.71
> Tags: patch
>
> Reference issue in Ubuntu [1]
>
> If a bind-mounted directory is still mounted during the clean-up phase
> (device busy for example) cowbuilder unconditionally deletes its content.
>
> Excerpt from a log with this bug (complete log attached)
> =
> I: umounting /var/lib/jenkins/cu2d
> umount: /var/cache/pbuilder/build/cow.15281/var/lib/jenkins/cu2d: device
> is busy.
> (In some cases useful info about processes that use
> the device is found by lsof(8) or fuser(1))
> [...]
> -> Cleaning COW directory
>forking: rm -rf /var/cache/pbuilder/build//cow.1195
> rm: cannot remove
> `/var/cache/pbuilder/build//cow.1195/var/cache/pbuilder/ccache': Device
> or resource busy
> rm: cannot remove
> `/var/cache/pbuilder/build//cow.1195/var/lib/jenkins/cu2d/work/experimental/100scopes':
>
> Device or resource busy
> rm: cannot remove
> `/var/cache/pbuilder/build//cow.1195/var/lib/jenkins/cu2d/launchpad.cache':
> Directory not empty
> =
>
> This bug occurs when pbuilder fails to mount a bindmounted directory,
> then fails to unmount previously successfully mounted directories. This
> condition is not so rare when executing several cowbuilder processes in
> parallel using the same bind-mounted directories.
wait, what? Not sure I understand.
>
> The attached patch has been proposed to Ubuntu and skips cleanup if
> anything is mounted under the chroot.
>
> [1] https://bugs.launchpad.net/ubuntu/+source/cowdancer/+bug/1156540
>
> --
> Jean-Baptiste
> IRC: jibel
> [2 cowdancer_0.71ubuntu1.debdiff ]
> diff -Nru cowdancer-0.71/cowbuilder.c cowdancer-0.71ubuntu1/cowbuilder.c
> --- cowdancer-0.71/cowbuilder.c 2011-07-29 15:01:39.0 +0200
> +++ cowdancer-0.71ubuntu1/cowbuilder.c2013-03-19 09:27:03.0
> +0100
> @@ -46,6 +46,7 @@
> #include
> #include
> #include
> +#include
> #include "parameter.h"
> #include "ilist.h"
>
> @@ -220,7 +221,61 @@
> */
> static int cpbuilder_internal_cleancow(const struct pbuilderconfig* pc)
> {
> + /*
> + * A directory bind-mounted into pc->buildplace, will be cleaned out by
> + * rmrf()
> + * To avoid that potential disaster we want to make sure that there is
> + * *nothing* mounted under the chroot before running the cleanup procedure
> + */
> +
> + char dest[strlen(pc->buildplace)];
> + int i=0;
> + int j=0;
> + unsigned char ch;
> +
>printf(" -> Cleaning COW directory\n");
> +
> + /* Remove // from pc->buildplace */
> + while(pc->buildplace[i])
> +{
> + ch = pc->buildplace[i];
> + if(i==0)
> +{
> + j++;
> + dest[0] = pc->buildplace[0];
> +}
> + else
> +{
> + if (ch != pc->buildplace[i-1] || ch != '/')
> +{
> + dest[j] = ch;
> + j++;
> +}
> +}
> + i++;
> +}
> + dest[j] = '\0';
> +
> + /* Check if buildplace is still mounted */
> + FILE *mtab = NULL;
> + struct mntent * part = NULL;
> + if ((mtab = setmntent("/etc/mtab", "r")) != NULL)
> +{
> + while ((part = getmntent(mtab) ) != NULL)
> +{
> + if ( part->mnt_fsname != NULL )
> +{
> + if (strstr(part->mnt_dir, dest) )
> +{
> + printf("E: Something is still mounted under %s; unmount
> and remove %s manually\n", dest, dest);
> + endmntent(mtab);
> + return 1;
> +}
> +}
> +}
> + endmntent(mtab);
> +}
> +
>if (0!=rmrf(pc->buildplace))
> return 1;
>return 0;
> Binary files /tmp/2njoJ6paZ0/cowdancer-0.71/.cowbuilder.c.swp and
> /tmp/C4QmySsSlo/cowdancer-0.71ubuntu1/.cowbuilder.c.swp differ
> diff -Nru cowdancer-0.71/debian/changelog
> cowdancer-0.71ubuntu1/debian/changelog
> --- cowdancer-0.71/debian/changelog 2012-08-23 21:51:56.0 +0200
> +++ cowdancer-0.71ubuntu1/debian/changelog2013-03-19 09:38:12.0
> +0100
> @@ -1,3 +1,11 @@
> +cowdancer (0.71ubuntu1) UNRELEASED; urgency=low
> +
> + * A directory bind-mounted into pc->buildplace, will be cleaned out by
> +rmrf() To avoid this disaster, we skip buildplace clean-up if a directory
> +is bind-mounted under the chroot (LP: #1156540)
> +
> + -- Jean-Baptiste Lallement Tue, 19
> Mar 2013 09:35:26 +0100
> +
> cowdancer (0.71) unstable; urgency=low
>
>* copyright file in copyright-format-1.0 as specified in policy version
> 3.9.3.1
> [3
> cu2d-100scopes-experimental-1.1prepare-unity-scope-calculator_2013-03-18_07-23-49_log
> ]
> Started by upstream project
> "[8mha:rB+LCABb85aBtbiIQSajNKU4P08vOT+vOD8nVc+jsiC1KCczL9svvyT1dMUiOWdZ/mImBiZPBrac1Lz0kgwfBubSopwSBiGfrMSyRP2cxLx0/eCSosy8dOuKIgYpNOOcITTIMAYIYGRiYKgoADLUShh09LPyk/STS41SdA0NDIqT
Bug#702102: fails to upgrade (cowbuilder) chroot
I think that patch is completely borken too. /dev/shm seems to be a symlink to /run/shm and /run/shm doesn't seem to exist (in older debootstrap ? how did they get generated?) anyway, I've committed a change to only look at /run/shm. At Tue, 26 Mar 2013 18:48:40 + (UTC), Thorsten Glaser wrote: > > Chris Knadle dixit: > > >+if [ "$DEB_BUILD_ARCH_OS" = "linux" ] && [ "$USEDEVSHM" = "yes" ]; then > >+ SHM_PATH="run/shm" > > > >+ [ ! -d "/$SHM_PATH" ] && SHM_PATH="dev/shm" > > This logic is totally and utterly borken. > > Correct logic would be: > > if outside_os = linux and inside_os = linux and USEDEVSHM: > if exists CHROOT/run/shm: > targetdir=run/shm > else if exists CHROOT/dev/shm: > targetdir=dev/shm > else: > abort > mount --bind $(realpath /dev/shm) CHROOT/$targetdir > > This separates the resolution of /dev/shm outside (Linux) > from the resolution of /dev/shm or /run/shm inside. > > I still believe this is not entirely right. If CHROOT/run > exists, it should be populated with a tmpfs, including > creation of subdirectories. > > Does CHROOT/dev/shm/. need to be bind-mounted to whatever > /dev/shm/. is outside of the chroot, for the eglibc shm > semantics to work? If not… just mount a tmpfs there, too! > > bye, > //mirabilos > -- > [DJBDNS Zone] TTL 86400 – kann man da auch 1d schreiben? > nö, außerdem kann ein Deutscher oder ein Japaner mit 1d > ja erstmal nix anfangen, oder könntest du 1日 im zone file lesen? > das heißt für mich: ein Regal, das u.U. schiefstehen könnte > > ___ > Pbuilder-maint mailing list > pbuilder-ma...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pbuilder-maint -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#702102: fails to upgrade (cowbuilder) chroot
not enough information in the bug, 702811 seems to be a better bug. At Sat, 02 Mar 2013 20:05:43 +0100, Michael Biebl wrote: > > Package: pbuilder > Version: 0.214 > Severity: serious > > Using cowbuilder in combination with pbuilder. > The latest update broke cowbuilder --update > Getting hundreds of: > rm: cannot remove > '/var/cache/pbuilder/build//cow.18262/proc/273/net/sockstat6': Operation > not permitted > > > > > -- System Information: > Debian Release: 7.0 > APT prefers unstable > APT policy: (500, 'unstable'), (200, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) > Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > > Versions of packages pbuilder depends on: > ii coreutils 8.20-3 > ii debconf [debconf-2.0] 1.5.49 > ii debianutils4.3.4 > ii debootstrap1.0.46 > ii dpkg-dev 1.16.9 > ii wget 1.14-1 > > Versions of packages pbuilder recommends: > ii devscripts 2.12.6 > ii fakeroot1.18.4-2 > ii sudo1.8.5p2-1+nmu1 > > Versions of packages pbuilder suggests: > ii cowdancer 0.71 > ii gdebi-core0.8.7 > pn pbuilder-uml > > -- debconf information excluded > > ___ > Pbuilder-maint mailing list > pbuilder-ma...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pbuilder-maint > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700591: [pbuilder] Add support for shared memory mounting point
At Wed, 27 Feb 2013 22:30:58 + (UTC), Thorsten Glaser wrote: > > Junichi Uekawa dixit: > > >I think the reason it's not done yet is that pbuilder predates > >/run/shm and we need to be updated... > > No, it was not done for /dev/shm either. /me smells security issues > or something like that, though I never understood what GNU libc uses > this for. I would imagine shmget etc will probably create temporary file there and mmap. If someone depends on /run/shm and is just using that for creating temp files, that's bad. (I don't particularly like the fact that simple builds requiring directories outside of your home directory other than /tmp to be writeable) > > > At Fri, 15 Feb 2013 16:36:36 + (UTC), > >Thorsten Glaser wrote: > > http://www.afaik.de/usenet/faq/zitieren/ > > bye, > //mirabilos > -- > 13:37⎜«Natureshadow» Deep inside, I hate mirabilos. I mean, he's a good > guy. But he's always right! In every fsckin' situation, he's right. Even > with his deeply perverted taste in software and borked ambition towards > broken OSes - in the end, he's damn right about it :(! […] works in mksh > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700290: pbuilder: clang support
At Thu, 28 Feb 2013 12:05:32 +0900, Hideki Yamane wrote: > > Hi, > > On Thu, 28 Feb 2013 07:02:54 +0900 > Junichi Uekawa wrote: > > I like the way this is very compact patch, but I dislike that it > > requires adding a config parameter to pbuilder (because it will need > > to be propagated to cowbuilder etc. I wonder if it could just be > > implemented in a hook and configuration. > > I thought it as you, but hook is not handy for check with switching > between gcc and clang for testing, then take the way to add parameter. Sorry, no please use a hookdir, it's there to be used. I don't like to add too many options to pbuilder. > > > > wait, there's no A10clang hook file. > > Yes, it's wrong, so removed in the newer patch. > > -- > Regards, > > Hideki Yamane henrich @ debian.or.jp/org > http://wiki.debian.org/HidekiYamane > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700290: pbuilder: clang support
I'm attaching a proposed hook script. Will this work for you?
#!/bin/bash
# Force use of clang instead of GCC.
function setup_clang() {
local GCC_VERSION=$(readlink /usr/bin/gcc | sed 's/^gcc\-//')
apt-get -y "${APTGETOPT[@]}" install clang
echo -e "\e[33mReplace gcc, g++ & cpp by clang\e[m"
for compiler in gcc-"$GCC_VERSION" cpp-"$GCC_VERSION" g++-"$GCC_VERSION"; do
rm /usr/bin/$compiler &&
ln -s /usr/bin/clang /usr/bin/$compiler
done
echo -e "\e[33mCheck if gcc, g++ & cpp are actually clang\e[m"
usr/bin/gcc --version| grep clang > /dev/null || exit 1
}
setup_clang
At Sat, 23 Feb 2013 22:39:04 +0900,
Hideki Yamane wrote:
>
> diff -Nru pbuilder-0.213/bash_completion.d/pbuilder
> pbuilder-0.213+nmu1/bash_completion.d/pbuilder
> --- pbuilder-0.213/bash_completion.d/pbuilder 2012-03-25 14:53:45.0
> +0900
> +++ pbuilder-0.213+nmu1/bash_completion.d/pbuilder2013-02-11
> 14:21:58.0 +0900
> @@ -60,7 +60,7 @@
> --aptconfdir --timeout --override-config --binary-arch \
> --preserve-buildplace --bindmounts --debug --twice
> --autocleanaptcache \
> --compressprog --debootstrapopts --save-after-login
> --save-after-exec \
> ---debootstrap' \
> +--debootstrap --with-clang' \
> -- "$cur" ) )
> if [[ $prev = @(--aptcache|--hookdir) ]]; then
> # Optionally provide a directory
> diff -Nru pbuilder-0.213/debian/changelog pbuilder-0.213+nmu1/debian/changelog
> --- pbuilder-0.213/debian/changelog 2012-10-08 08:30:05.0 +0900
> +++ pbuilder-0.213+nmu1/debian/changelog 2013-02-11 15:01:07.0
> +0900
> @@ -1,3 +1,13 @@
> +pbuilder (0.213+nmu1) UNRELEASED; urgency=low
> +
> + [ Hideki Yamane ]
> + * Non-maintainer upload.
> + * add "--with-clang" option to build your package with clang.
> +It would replace GCC by default(Thanks Luca Falavigna
> ),
> +also you can specify it any version with GCC_VERSION environment
> variable.
> +
> + -- Hideki Yamane Mon, 11 Feb 2013 14:22:38 +0900
> +
> pbuilder (0.213) unstable; urgency=low
>
>[ Beatrice Torracca ]
> diff -Nru pbuilder-0.213/pbuilder-buildpackage
> pbuilder-0.213+nmu1/pbuilder-buildpackage
> --- pbuilder-0.213/pbuilder-buildpackage 2012-03-13 17:25:15.0
> +0900
> +++ pbuilder-0.213+nmu1/pbuilder-buildpackage 2013-02-11 15:18:41.0
> +0900
> @@ -97,6 +97,9 @@
> executehooks "D"
> trap saveaptcache_umountproc_cleanbuildplace_trap exit sighup sigpipe
> checkbuilddep "$PACKAGENAME"
> +if [ "$CLANG" = "yes" ]; then
> +setup_clang
> +fi
> save_aptcache
> trap umountproc_cleanbuildplace_trap exit sighup sigpipe
>
> diff -Nru pbuilder-0.213/pbuilder-buildpackage-funcs
> pbuilder-0.213+nmu1/pbuilder-buildpackage-funcs
> --- pbuilder-0.213/pbuilder-buildpackage-funcs2012-03-31
> 13:51:11.0 +0900
> +++ pbuilder-0.213+nmu1/pbuilder-buildpackage-funcs 2013-02-11
> 16:44:51.0 +0900
> @@ -112,3 +112,22 @@
> export CCACHE_DIR="$CCACHEDIR"
> fi
> }
> +
> +function setup_clang() {
> +# set appropriate GCC version.
> +if [ -z $GCC_VERSION ]; then
> + GCC_VERSION=$(readlink /usr/bin/gcc | sed 's/^gcc\-//')
> +fi
> +
> +$CHROOTEXEC usr/bin/apt-get -y "${APTGETOPT[@]}" install clang
> +
> +echo -e "\e[33mReplace gcc, g++ & cpp by clang\e[m"
> +for compiler in gcc-"$GCC_VERSION" cpp-"$GCC_VERSION" g++-"$GCC_VERSION"
> +do
> + $CHROOTEXEC rm /usr/bin/$compiler &&
> + $CHROOTEXEC ln -s /usr/bin/clang /usr/bin/$compiler
> +done
> +
> +echo -e "\e[33mCheck if gcc, g++ & cpp are actually clang\e[m"
> +$CHROOTEXEC usr/bin/gcc --version| grep clang > /dev/null || exit 1
> +}
> diff -Nru pbuilder-0.213/pbuilder-checkparams
> pbuilder-0.213+nmu1/pbuilder-checkparams
> --- pbuilder-0.213/pbuilder-checkparams 2012-03-09 07:54:41.0
> +0900
> +++ pbuilder-0.213+nmu1/pbuilder-checkparams 2013-02-11 14:20:54.0
> +0900
> @@ -260,6 +260,10 @@
> TWICE="yes"
> shift;
> ;;
> + --with-clang)
> + CLANG="yes"
> + shift;
> + ;;
> --) # end of processing for this
> shift;
> break;
> diff -Nru pbuilder-0.213/pbuilder-modules pbuilder-0.213+nmu1/pbuilder-modules
> --- pbuilder-0.213/pbuilder-modules 2012-03-31 13:50:46.0 +0900
> +++ pbuilder-0.213+nmu1/pbuilder-modules 2013-02-11 14:51:33.0
> +0900
> @@ -79,6 +79,7 @@
> --debootstrapopts [debootstrap options]
> --save-after-login/--save-after-exec
> --debootstrap [debootstrap|cdebootstrap]
> + --with-clang
>
> pdebuild-specific pbuilder-options:
> --pbuilderroot [command to obtain root privilege for pbuilder]
> diff -Nru pbuilder-0.213/pbuilder.8 pbuilder-0.213+nmu1/pbuilder.8
> --- pbuilder-0.213/pbuilder.8 2012-03-09 07:54:41.0 +0900
> +++ p
Bug#700591: [pbuilder] Add support for shared memory mounting point
I think the reason it's not done yet is that pbuilder predates /run/shm and we need to be updated... At Fri, 15 Feb 2013 16:36:36 + (UTC), Thorsten Glaser wrote: > > Agustin Henze dixit: > > >that's sounds "a little" easier :). Ok, I think that > >/run/shm should be add by default into BINDMOUNTS option. > > There’s probably a reason it’s not default… > but I’ll leave that to the pbuilder/cowbuilder > people to discover or explain. > > bye, > //mirabilos > -- > „nein: BerliOS und Sourceforge sind Plattformen für Projekte, github ist > eine Plattform für Einzelkämpfer“ > -- dieses Zitat ist ein Beweis dafür, daß auch ein blindes Huhn > mal ein Korn findet, bzw. – in diesem Fall – Recht haben kann > > ___ > Pbuilder-maint mailing list > pbuilder-ma...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pbuilder-maint -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700290: pbuilder: clang support
Hi,
Thanks for the patch.
I have a question.
At Mon, 11 Feb 2013 17:01:29 +0900,
Hideki Yamane wrote:
>
> diff -Nru pbuilder-0.213/bash_completion.d/pbuilder
> pbuilder-0.213+nmu1/bash_completion.d/pbuilder
> --- pbuilder-0.213/bash_completion.d/pbuilder 2012-03-25 14:53:45.0
> +0900
> +++ pbuilder-0.213+nmu1/bash_completion.d/pbuilder2013-02-11
> 14:21:58.0 +0900
> @@ -60,7 +60,7 @@
> --aptconfdir --timeout --override-config --binary-arch \
> --preserve-buildplace --bindmounts --debug --twice
> --autocleanaptcache \
> --compressprog --debootstrapopts --save-after-login
> --save-after-exec \
> ---debootstrap' \
> +--debootstrap --with-clang' \
> -- "$cur" ) )
> if [[ $prev = @(--aptcache|--hookdir) ]]; then
> # Optionally provide a directory
> diff -Nru pbuilder-0.213/debian/changelog pbuilder-0.213+nmu1/debian/changelog
> --- pbuilder-0.213/debian/changelog 2012-10-08 08:30:05.0 +0900
> +++ pbuilder-0.213+nmu1/debian/changelog 2013-02-11 15:01:07.0
> +0900
> @@ -1,3 +1,13 @@
> +pbuilder (0.213+nmu1) UNRELEASED; urgency=low
> +
> + [ Hideki Yamane ]
> + * Non-maintainer upload.
> + * add "--with-clang" option to build your package with clang.
> +It would replace GCC-4.7 by default, you can specify it any version
> +with GCC_VERSION environment variable
> +
> + -- Hideki Yamane Mon, 11 Feb 2013 14:22:38 +0900
> +
> pbuilder (0.213) unstable; urgency=low
>
>[ Beatrice Torracca ]
> diff -Nru pbuilder-0.213/pbuilder-buildpackage
> pbuilder-0.213+nmu1/pbuilder-buildpackage
> --- pbuilder-0.213/pbuilder-buildpackage 2012-03-13 17:25:15.0
> +0900
> +++ pbuilder-0.213+nmu1/pbuilder-buildpackage 2013-02-11 15:18:41.0
> +0900
> @@ -97,6 +97,9 @@
> executehooks "D"
> trap saveaptcache_umountproc_cleanbuildplace_trap exit sighup sigpipe
> checkbuilddep "$PACKAGENAME"
> +if [ "$CLANG" = "yes" ]; then
> +setup_clang
> +fi
> save_aptcache
> trap umountproc_cleanbuildplace_trap exit sighup sigpipe
>
> diff -Nru pbuilder-0.213/pbuilder-buildpackage-funcs
> pbuilder-0.213+nmu1/pbuilder-buildpackage-funcs
> --- pbuilder-0.213/pbuilder-buildpackage-funcs2012-03-31
> 13:51:11.0 +0900
> +++ pbuilder-0.213+nmu1/pbuilder-buildpackage-funcs 2013-02-11
> 16:44:51.0 +0900
> @@ -112,3 +112,22 @@
> export CCACHE_DIR="$CCACHEDIR"
> fi
> }
> +
I like the way this is very compact patch, but I dislike that it
requires adding a config parameter to pbuilder (because it will need
to be propagated to cowbuilder etc. I wonder if it could just be
implemented in a hook and configuration.
> +function setup_clang() {
> +# set appropriate GCC version.
> +if [ -z $GCC_VERSION ]; then
> + GCC_VERSION="4.7"
> +fi
> +
> +$CHROOTEXEC usr/bin/apt-get -y "${APTGETOPT[@]}" install clang
> +
> +echo -e "\e[33mReplace gcc, g++ & cpp by clang\e[m"
> +for compiler in gcc-"$GCC_VERSION" cpp-"$GCC_VERSION" g++-"$GCC_VERSION"
> +do
> + $CHROOTEXEC rm /usr/bin/$compiler &&
> + $CHROOTEXEC ln -s /usr/bin/clang /usr/bin/$compiler
> +done
> +
> +echo -e "\e[33mCheck if gcc, g++ & cpp are actually clang\e[m"
> +$CHROOTEXEC usr/bin/gcc --version| grep clang > /dev/null || exit 1
> +}
> diff -Nru pbuilder-0.213/pbuilder-checkparams
> pbuilder-0.213+nmu1/pbuilder-checkparams
> --- pbuilder-0.213/pbuilder-checkparams 2012-03-09 07:54:41.0
> +0900
> +++ pbuilder-0.213+nmu1/pbuilder-checkparams 2013-02-11 14:20:54.0
> +0900
> @@ -260,6 +260,10 @@
> TWICE="yes"
> shift;
> ;;
> + --with-clang)
> + CLANG="yes"
> + shift;
> + ;;
> --) # end of processing for this
> shift;
> break;
> diff -Nru pbuilder-0.213/pbuilder-modules pbuilder-0.213+nmu1/pbuilder-modules
> --- pbuilder-0.213/pbuilder-modules 2012-03-31 13:50:46.0 +0900
> +++ pbuilder-0.213+nmu1/pbuilder-modules 2013-02-11 14:51:33.0
> +0900
> @@ -79,6 +79,7 @@
> --debootstrapopts [debootstrap options]
> --save-after-login/--save-after-exec
> --debootstrap [debootstrap|cdebootstrap]
> + --with-clang
>
> pdebuild-specific pbuilder-options:
> --pbuilderroot [command to obtain root privilege for pbuilder]
> diff -Nru pbuilder-0.213/pbuilder.8 pbuilder-0.213+nmu1/pbuilder.8
> --- pbuilder-0.213/pbuilder.8 2012-03-09 07:54:41.0 +0900
> +++ pbuilder-0.213+nmu1/pbuilder.82013-02-11 14:35:27.0 +0900
> @@ -534,6 +534,11 @@
> properly. The resulting packages are the ones from the second build.
>
> .TP
> +.BI "\-\-with\-clang"
> +Build the package with clang, instead of gcc.
> +Also you should use A10clang hook file in example.
wait, there's no A10clang hook file.
> +
> +.TP
> .BI "\-\-preserve\-buildplace"
> Do not clean t
Bug#694311: pbuilder: fails to --create with EXTRAPACKAGES=ccache
At Sun, 25 Nov 2012 12:20:08 +0100,
Helmut Grohne wrote:
>
> Package: pbuilder
> Version: 0.213
> Severity: normal
>
> I tried using the documented[1] approach to pbuilder. Unfortunately it
> fails. Here is the tail of the create log:
>
> | I: Obtaining the cached apt archive contents
> | Reading package lists...
> | Building dependency tree...
> | Reading state information...
> | 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> | Reading package lists...
> | Building dependency tree...
> | Reading state information...
> | Package 'ccache' is not installed, so not removed
> | build-essential is already the newest version.
> | dpkg-dev is already the newest version.
> | The following extra packages will be installed:
> | aptitude-common libboost-iostreams1.49.0 libcwidget3 libept1.4.12
> libncursesw5 libsigc++-2.0-0c2a libsqlite3-0 libxapian22
> | Suggested packages:
> | tasksel debtags distcc libcwidget-dev xapian-tools
> | Recommended packages:
> | aptitude-doc-en aptitude-doc apt-xapian-index
> libparse-debianchangelog-perl libgpm2
> | The following NEW packages will be installed:
> | aptitude aptitude-common ccache libboost-iostreams1.49.0 libcwidget3
> libept1.4.12 libncursesw5 libsigc++-2.0-0c2a libsqlite3-0 libxapian22
> | The following held packages will be changed:
> | ccache
> | 0 upgraded, 10 newly installed, 0 to remove and 0 not upgraded.
> | Need to get 0 B/6417 kB of archives.
> | After this operation, 22.4 MB of additional disk space will be used.
> | E: There are problems and -y was used without --force-yes
> | I: unmounting /var/cache/pbuilder/ccache filesystem
> | I: unmounting dev/pts filesystem
> | I: unmounting proc filesystem
> | I: cleaning the build env
> | I: removing directory /var/cache/pbuilder/build//18320 and its
> subdirectories
>
> After commenting out EXTRAPACKAGES=ccache, the --create works flawlessly.
>
> Maybe you already have an idea what is going wrong here?
>
> Helmut
>
> [1] http://pbuilder.alioth.debian.org/#ccache
seems like this webpage is stale, I haven't ran 'make release' in
Documentation/ directory for quite a while.
>
> -- System Information:
> Versions of packages pbuilder depends on:
> ii cdebconf [debconf-2.0] 0.179
> ii cdebootstrap0.5.9
> ii coreutils 8.20-3
> ii debconf [debconf-2.0] 1.5.46
> ii debianutils 4.3.4
> ii debootstrap 1.0.44
> ii dpkg-dev1.16.9
> ii wget1.14-1
>
> -- Configuration Files:
> /etc/pbuilderrc changed: (only notable settings, ask for specific
> settings if necessary)
> export CCACHE_DIR="/var/cache/pbuilder/ccache"
> EXTRAPACKAGES=ccache
> export PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin"
> export PATH="/usr/lib/ccache:${PATH}"
> BINDMOUNTS="${CCACHE_DIR}"
> DEBOOTSTRAP="cdebootstrap"
>
> ___
> Pbuilder-maint mailing list
> pbuilder-ma...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pbuilder-maint
>
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#693952: pbuilder: please change the default build place from /tmp/buildd to what Debian uses
Sounds like it's a good thing if it were done. This has been hardcoded default for more than 10 years and scripts assume this path, one problem I see is that this build path is hardcoded in user scripts and hard to modify without breaking anything. At Thu, 22 Nov 2012 14:07:36 +0800, Paul Wise wrote: > > Package: pbuilder > Version: 0.213 > Severity: wishlist > > The Debian buildd machines use this path to unpack and build source > packages, please switch to it for compatibility: > > /build/buildd-_--/ pbuilder uses one chroot for one package, would /build/buildd/ work or should I have to use the randomized and long path; what's the advantage (apart from compatibility) ? > > The XX is the template from the mktemp --directory invocation. > > The advantage of this is that no build systems will embed /tmp in their > binaries nor build system, which means no potential security issues from > that and also grepping source code for /tmp after a build becomes much > less noisy. > > -- > bye, > pabs > > http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#678407: pbuilder: pdebuild --use-pdebuild-internal gets it's knickers into a twist when in symplinked dir
I believe you can work around by sending extra directories to --bindmounts option. Currently for convenience the default is: --bindmounts $(readlink -f ..) \ I assume that .. is symlinked to somewhere else and that breaks some assumption here. Not sure what the generic solution will be. Would doing 'cd $(readlink -f .)' inside pdebuild help ? At Thu, 21 Jun 2012 15:18:56 +0100, Robert Lemmen wrote: > > Package: pbuilder > Version: 0.211 > Severity: normal > > Dear Maintainer, > > I am symlinking various directories under my home to a different, > faster and not backup-ed, filesystem. when running pdebuild > --use-pdebuild-internal from one of these, funny things happen. assume > /home/test is a symlink to /store/test: > > cd /home/test/wM7cwjmM0I/gzip-1.4/ > pdebuild --use-pdebuild-internal > ... > I: Mounting /store/test/wM7cwjmM0I > ... > /runscript: line 38: cd: /home/test/wM7cwjmM0I/gzip-1.4: No such file or > directory > > so it seems to mount the /store/ part ( i assume it mounts it to the > same location within the cchroot), but then tries to mount the /home/ > version > > this can of course be worked around by starting pdebuild from > /store/test/wM7cwjmM0I/gzip-1.4. > > regards robert > > -- System Information: > Debian Release: wheezy/sid > APT prefers testing > APT policy: (500, 'testing') > Architecture: amd64 (x86_64) > > Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) > Locale: LANG=en_GB.UTF-8, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15) > Shell: /bin/sh linked to /bin/dash > > Versions of packages pbuilder depends on: > ii cdebootstrap 0.5.9 > ii coreutils 8.13-3.2 > ii debconf [debconf-2.0] 1.5.43 > ii debianutils4.3.1 > ii debootstrap1.0.40 > ii dpkg-dev 1.16.3 > ii wget 1.13.4-3 > > Versions of packages pbuilder recommends: > ii devscripts 2.11.8 > ii fakeroot1.18.4-2 > ii sudo1.8.3p2-1.1 > > Versions of packages pbuilder suggests: > pn cowdancer > pn gdebi-core > pn pbuilder-uml > > -- debconf information excluded > > > > ___ > Pbuilder-maint mailing list > pbuilder-ma...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pbuilder-maint > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#693458: pbuilder: [TYPO] pbuilder-buildpackage and /etc/pbuilderrc: s/EXTENTION/EXTENSION/
At Fri, 16 Nov 2012 23:01:27 + (UTC), Thorsten Glaser wrote: > > Simon L'nu dixit: > > >/etc/pbuilderrc line 85: > >-PKGNAME_LOGFILE_EXTENTION="_$(dpkg --print-architecture).build" > >+PKGNAME_LOGFILE_EXTENSION="_$(dpkg --print-architecture).build" > > You can't fix that now, otherwise different pbuilderrcs > will start to break... :( Unfortunate, amen. > > bye, > //mirabilos > -- > Yay for having to rewrite other people's Bash scripts because bash > suddenly stopped supporting the bash extensions they make use of > -- Tonnerre Lombard in #nosec > > ___ > Pbuilder-maint mailing list > pbuilder-ma...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pbuilder-maint > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#690313: google-perftools: google-pprof manpage refers to /usr/share/gperftools/cpu_profiler.html which doesn't exist
Package: google-perftools Version: 2.0-2 Severity: minor Dear Maintainer, please make it link to /usr/share/doc/libgoogle-perftools-dev/index.html instead. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to ja_JP.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages google-perftools depends on: ii curl 7.26.0-1 ii libgoogle-perftools4 2.0-2 Versions of packages google-perftools recommends: ii graphviz 2.26.3-12 ii gv1:3.7.3-1 google-perftools suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#689213: pbuilder: Deletes pbuilderrc's contents and then fails to configure under some circumstances
Hi, I've looked into your case, pbuilder doesn't delete any file. dpkg is installing a pbuilder file; the symbollic link /etc/pbuilder/pbuilderrc isn't a conffile and is reinstalled on every package install, therefore you have introduced a symlink loop. It's not entirely obvious how to fix this. /etc/pbuilder/pbuilderrc was created just for convenience purpose and not for editing. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=174155 Maybe that was the original problem, we should remove the /etc/pbuilder/pbuilderrc symlik in order to remove the false impression that you can do this. At Sun, 30 Sep 2012 14:28:03 +0200, Axel Beckert wrote: > > Package: pbuilder > Version: 0.212 > Severity: grave > Justification: may cause data loss > > Dear pbuilder Maintainers, > > pbuilder fails to configure on wheezy (and sid) if /etc/pbuilderrc is a > symlink to /etc/pbuilder/pbuilderrc after it replaces > /etc/pbuilder/pbuilderrc with a symlink despite pbuilder/rewrite is set > to false. > >* What led up to the situation? > > I have my pbuilder in a git repository. Hence the complete > /etc/pbuilder/ is under version control while /etc/pbuilderrc is not, > but a symlink to /etc/pbuilder/pbuilderrc (to have it under version > control). > >* What exactly did you do (or not do) that was effective (or > ineffective)? > > I upgraded today pbuilder from 0.211 to 0.212. It asked me via debconf > if it should update pbuilderrc and I denied that question. > >* What was the outcome of this action? > > Setting up pbuilder (0.212) ... > /var/lib/dpkg/info/pbuilder.config: 40: /var/lib/dpkg/info/pbuilder.config: > cannot create /etc/pbuilderrc: Too many levels of symbolic links > dpkg: error processing pbuilder (--configure): > subprocess installed post-installation script returned error exit status 2 > Processing triggers for menu ... > Errors were encountered while processing: > pbuilder > > And, even worse: My real pbuilderrc has been deleted despite > pbuilder/rewrite being set to false: > > lrwxrwxrwx 1 root root 13 Aug 23 21:53 /etc/pbuilder/pbuilderrc -> > ../pbuilderrc > lrwxrwxrwx 1 root root 19 Sep 16 13:33 /etc/pbuilderrc -> pbuilder/pbuilderrc > > If I wouldn't have /etc/pbuilder/ in git but choosen that layout for > other reasons (and would have no other means of backup), my handcrafted > pbuilderrc would have been lost. > >* What outcome did you expect instead? > > That it just doesn't touch my handcrafted pbuilderrc independent of its > location and that it still would have looked like before: > > -rw-r--r-- 1 root root 858 Sep 30 14:20 /etc/pbuilder/pbuilderrc > lrwxrwxrwx 1 root root 19 Sep 16 13:33 /etc/pbuilderrc -> pbuilder/pbuilderrc > > (A "git checkout pbuilderrc" and then a "dpkg --configure --pending" > solved the issue for me. Nevertheless this shouldn't happen.) > > -- System Information: > Debian Release: wheezy/sid > APT prefers testing > APT policy: (500, 'testing') > Architecture: amd64 (x86_64) > > Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > > Versions of packages pbuilder depends on: > ii cdebconf [debconf-2.0] 0.175 > ii cdebootstrap0.5.9 > ii coreutils 8.13-3.2 > ii debconf [debconf-2.0] 1.5.46 > ii debianutils 4.3.2 > ii debootstrap 1.0.42 > ii dpkg-dev1.16.8 > ii wget1.13.4-3 > > Versions of packages pbuilder recommends: > ii devscripts 2.12.4 > ii fakeroot1.18.4-2 > ii sudo1.8.5p2-1 > > Versions of packages pbuilder suggests: > ii cowdancer 0.70 > ii gdebi-core0.8.5 > pn pbuilder-uml > > -- debconf information: > pbuilder/mirrorsite: http://ftp.ch.debian.org/debian/ > pbuilder/nomirror: > pbuilder/rewrite: false > > ___ > Pbuilder-maint mailing list > pbuilder-ma...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pbuilder-maint > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#687939: libjson-spirit-dev: add documentation for this package
Package: libjson-spirit-dev Version: 4.04-1+b1 Severity: wishlist Dear Maintainer, This package doesn't contain any documentation. It would be useful if ./json_demo ./json_headers_only_demo ./json_map_demo from source tree were installed in as examples. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to ja_JP.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libjson-spirit-dev depends on: ii libboost-dev 1.49.0.1 libjson-spirit-dev recommends no packages. libjson-spirit-dev suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#687289: libexiv2-doc: Contains js and css but not HTML in doc package
Package: libexiv2-doc Version: 0.23-1 Severity: normal Dear Maintainer, /usr/share/doc/libexiv2-doc/include seems to have js and png and css files that looks like it's usable for HTML document, but there's no HTML documentation found. Are we missing some docs here? /usr/share/doc/libexiv2-doc$ find . . ./changelog.gz ./copyright ./changelog.Debian.gz ./include ./include/ascending.png ./include/sortabletable.js ./include/blank.png ./include/exiv2-components.png ./include/sortabletable.css ./include/descending.png ./TODO ./examples ./examples/samples ./examples/samples/xmpparser-test.cpp ./examples/samples/prevtest.cpp ./examples/samples/werror-test.cpp ./examples/samples/mmap-test.cpp ./examples/samples/iptcprint.cpp ./examples/samples/iptctest.cpp.gz ./examples/samples/xmpparse.cpp ./examples/samples/xmpsample.cpp.gz ./examples/samples/tiff-test.cpp ./examples/samples/key-test.cpp.gz ./examples/samples/iotest.cpp.gz ./examples/samples/easyaccess-test.cpp ./examples/samples/write2-test.cpp.gz ./examples/samples/convert-test.cpp ./examples/samples/addmoddel.cpp.gz ./examples/samples/Makefile.gz ./examples/samples/tiffaddpath-test.cpp ./examples/samples/exifprint.cpp ./examples/samples/iptceasy.cpp ./examples/samples/write-test.cpp.gz ./examples/samples/exifdata-test.cpp.gz ./examples/samples/stringto-test.cpp ./examples/samples/largeiptc-test.cpp ./examples/samples/exifcomment.cpp ./cmdxmp.txt -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to ja_JP.UTF-8) Shell: /bin/sh linked to /bin/dash -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#687278: libexiv2-doc: libexiv2-doc documentation package seems to be lacking in content
Package: libexiv2-doc Version: 0.23-1 Severity: normal Dear Maintainer, doc/html/ directory (the generated doxygen documentation) is not included in libexiv2-doc package and makes the documentation package rather less useful than it should be. Something like the following should fix the problem. diff --git a/debian/libexiv2-doc.docs b/debian/libexiv2-doc.docs index e48d89c..ba05107 100644 --- a/debian/libexiv2-doc.docs +++ b/debian/libexiv2-doc.docs @@ -1,3 +1,4 @@ doc/include +doc/html/ doc/*.txt src/TODO diff --git a/debian/rules b/debian/rules index f5bafdd..eab282d 100755 --- a/debian/rules +++ b/debian/rules @@ -9,6 +9,7 @@ override_dh_auto_configure: override_dh_clean: dh_clean rm -rf doc/html + -rm Makefile xmpsdk/src/.libs/libxmpsdk.la # why? debuild complains of diff. override_dh_strip: dh_strip -a --dbg-package=libexiv2-dbg -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to ja_JP.UTF-8) Shell: /bin/sh linked to /bin/dash -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#683848: bin-NMU support
Hi,
Having two parameters delimited by space is probably not usual, shouldn't that
be more like another parameter to set message for bin nmu?
Is this the usual expected interface for other tools too ?
to be somewhat consistent with, http://release.debian.org/wanna-build.txt,
version number should be autoincremented, and message should be specified via
something like -m ?
At Sat, 04 Aug 2012 20:53:29 +0200,
Luca Falavigna wrote:
>
> diff -Nru pbuilder-0.211/pbuilder.8 pbuilder-0.212/pbuilder.8
> --- pbuilder-0.211/pbuilder.8 2012-03-08 23:54:41.0 +0100
> +++ pbuilder-0.212/pbuilder.8 2012-08-04 20:48:02.0 +0200
> @@ -353,6 +353,14 @@
> .B "\-\-debbuildopts -B"
>
> .TP
> +.BI "\-\-bin\-nmu [" "version" "/" "message" "]"
The notation should be
+.BI "\-\-bin\-nmu [" "version" "] [" "message" "]"
> +
> +Specify to build a binary NMU instead of a standard package.
> +You must pass two parameters, the first one is a numeric value indicating
> +the progressive binNMU version, the second one is a message that will
> +appear in the changelog entry.
> +
> +.TP
> .BI "\-\-bindmounts " "bind-mount-points"
> Bind-mount the specified directories to inside the chroot.
> .I "bind-mount-points"
> diff -Nru pbuilder-0.211/pbuilder-checkparams
> pbuilder-0.212/pbuilder-checkparams
> --- pbuilder-0.211/pbuilder-checkparams 2012-03-08 23:54:41.0
> +0100
> +++ pbuilder-0.212/pbuilder-checkparams 2012-08-04 20:34:57.0
> +0200
> @@ -33,6 +33,7 @@
> OVERRIDE_APTLINES="no"
> OVERRIDE_APTLINES_WARN="" # set this if --override-config option should be
> set.
> BINARY_ARCH="no"
> +BIN_NMU="no"
> PBUILDER_BUILD_LOGFILE=
> PRESERVE_BUILDPLACE="no"
> unset EXTRA_CONFIGFILE || true
> @@ -189,6 +190,14 @@
> DEBBUILDOPTS="${DEBBUILDOPTS} -B"
> shift;
> ;;
> + --bin-nmu)
> + BIN_NMU="yes"
> + # XXX this might be overwriten by --debbuildopts ""
> + DEBBUILDOPTS="${DEBBUILDOPTS} -B"
> + BINNMU_VERSION="$2"
> + BINNMU_MESSAGE="$3"
> + shift; shift; shift;
> + ;;
> --preserve-buildplace)
> PRESERVE_BUILDPLACE="yes"
> shift;
> diff -Nru pbuilder-0.211/pbuilder-modules pbuilder-0.212/pbuilder-modules
> --- pbuilder-0.211/pbuilder-modules 2012-03-31 06:50:46.0 +0200
> +++ pbuilder-0.212/pbuilder-modules 2012-08-04 20:37:28.0 +0200
> @@ -70,6 +70,7 @@
> --timeout [timeout time]
> --override-config
> --binary-arch
> + --bin-nmu [version number | description]
+ --bin-nmu [version number] [description]
> --preserve-buildplace
> --bindmounts [bind-mount-point]
> --debug
> @@ -595,6 +596,44 @@
> done
> }
>
> +function binNMU() {
> +if [ "$BIN_NMU" == "no" ]; then
> + return
> +fi
> +if [ -z $BINNMU_VERSION ]; then
> + echo "No version provided for binNMU entry."
> + exit 1
> +fi
> +if [ -z $BINNMU_MESSAGE ]; then
> + echo "No changelog message provided for binNMU entry."
> + exit 1
> +fi
> +local cl=$(ls $BUILDPLACE/tmp/buildd/*/debian/changelog)
> +local tmpcl=$cl.pbuildertmp
> +if [ ! -f $cl ]; then
> + echo "Cannot open debian/changelog for binNMU version handling."
> + exit 1
> +fi
> +if [ -z $DEBEMAIL ]; then
> + echo "No maintainer addres provided, use --debemail option."
> + exit 1
> +fi
> +mv $cl $tmpcl
> +local package=$(head -n1 $tmpcl | cut -d" " -f1)
> +local version=$(head -n1 $tmpcl | sed 's/.*(\(.*\)).*/\1/')
> +local arch=$($CHROOTEXEC dpkg-architecture -qDEB_HOST_ARCH)
> +local date=$(date -R)
> +echo "$package ($version+b$BINNMU_VERSION) $DISTRIBUTION; urgency=low" >
> $cl
> +echo >> $cl
> +echo " * Binary-only non-maintainer upload for $arch; no source
> changes." >> $cl
> +echo " * $BINNMU_MESSAGE" >> $cl
> +echo >> $cl
> +echo " -- $DEBEMAIL $date" >> $cl
> +echo >> $cl
> +cat $tmpcl >> $cl
> +rm $tmpcl
> +}
> +
> #Setting environmental variables that are really required:
> #required for some packages to install...
> export LANG=C
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#638856: [pbuilder] fails to create with option --distribution experimental
At Wed, 01 Aug 2012 12:27:21 +0200, Ansgar Burchardt wrote: > > This might be caused by > > APT::Default-Release "experimental"; > > in apt.conf which pbuilder seems to add for a experimental chroot. > Doing this is wrong as it will cause all dependencies to be taken from > experimental, including those having a high enough version in unstable. > > In particular I heard that pbuilder currently tries to install perl 5.16 > from experimental (perl 5.16 is not really installable). What's the value of keeping something that's not installable in experimental? > > Ansgar > > ___ > Pbuilder-maint mailing list > pbuilder-ma...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pbuilder-maint > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#681649: yatex: YaTeX status mode line is in wrong char code.
Package: yatex Version: 1.76+dfsg1-1 Severity: normal Dear Maintainer, characters in the status line look garbled. screenshot attached. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to ja_JP.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages yatex depends on: ii emacs23 23.4+1-3 ii install-info 4.13a.dfsg.1-10 Versions of packages yatex recommends: ii ptex-bin 2012.20120611-2 pn texlive-bin Versions of packages yatex suggests: ii epiphany-browser [www-browser] 3.4.2-1 pn gimageview ii google-chrome-stable [www-browser] 20.0.1132.57-r145807 ii iceweasel [www-browser] 10.0.5esr-2 pn jbibtex pn jweblint | weblint ii texlive-binaries [mendexk] 2012.20120628-1 ii w3m [www-browser] 0.5.3-8 -- no debconf information <>
Bug#675939: emacs-mozc: emacs mozc does not initialize with require 'mozc
Package: emacs-mozc Version: 1.5.1053.102-3+b1 Severity: normal Dear Maintainer, I think mozc load paths are not correctly set. README.Debian says (add-to-list 'load-path "/usr/share/emacs/site-lisp/emacs-mozc") but that should be set in /etc/emacs/site-start.d/50emacs-mozc.el and I think emacs23 precompiled elc file should be installed in /usr/share/emacs23/site-lisp/emacs-mozc as per /usr/share/doc/emacsen-common/debian-emacs-policy.gz Warning (initialization): An error occurred while loading `/home/dancer/.emacs': File error: Cannot open load file, mozc To ensure normal operation, you should investigate and remove the cause of the error in your initialization file. Start Emacs with the `--debug-init' option to view a complete error backtrace. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to ja_JP.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages emacs-mozc depends on: ii emacs-mozc-bin 1.5.1053.102-3+b1 ii emacs23 23.4+1-3 emacs-mozc recommends no packages. emacs-mozc suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#673248: advi: Japanese fonts no longer work
Package: advi Version: 1.10.2-1 Severity: normal It seems like advi no longer can handle Japanese fonts. I haven't quite dug into why this might be. $ platex simple.tex This is e-pTeX, Version 3.1415926-p3.2-110825-2.3 (utf8.euc) (TeX Live 2012/dev/Debian) restricted \write18 enabled. entering extended mode (./simple.tex pLaTeX2e <2006/11/10> (based on LaTeX2e <2011/06/27> patch level 0) Babel and hyphenation patterns for english, dumylang, nohyphenation, pi nyin, loaded. (/usr/share/texlive/texmf-dist/tex/platex/base/jarticle.cls Document Class: jarticle 2006/06/27 v1.6 Standard pLaTeX class (/usr/share/texlive/texmf-dist/tex/platex/base/jsize10.clo)) (./simple.aux) [1] (./simple.aux) ) Output written on simple.dvi (1 page, 436 bytes). Transcript written on simple.log. $ advi simple.dvi kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600 min10 mktexpk: don't know how to create bitmap font for min10. mktexpk: perhaps min10 is missing from the map file. kpathsea: Appending font creation commands to missfont.log. kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600 goth10 mktexpk: don't know how to create bitmap font for goth10. mktexpk: perhaps goth10 is missing from the map file. kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600 goth10 mktexpk: don't know how to create bitmap font for goth10. mktexpk: perhaps goth10 is missing from the map file. kpathsea: Appending font creation commands to missfont.log. Warning: file goth10.600pk is not found kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600 min10 mktexpk: don't know how to create bitmap font for min10. mktexpk: perhaps min10 is missing from the map file. kpathsea: Appending font creation commands to missfont.log. Warning: file min10.600pk is not found Uncaught exception: File "search.ml", line 209, characters 2-8: Assertion failed -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to ja_JP.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages advi depends on: ii dpkg 1.16.3 ii ghostscript-x9.05~dfsg-5 ii libc62.13-32 ii libfreetype6 2.4.9-1 ii libx11-6 2:1.4.99.901-2 ii libxinerama1 2:1.1.2-1 ii perl 5.14.2-9 ii tex-common 3.10 ii texlive-base 2011.20120424-1 ii texlive-binaries [texlive-base-bin] 2011.20120410-1 ii zlib1g 1:1.2.7.dfsg-1 advi recommends no packages. Versions of packages advi suggests: ii bzip2 1.0.6-1 ii fonts-ipaexfont-gothic [fonts-japanese-gothic] 00103-9 ii fonts-ipaexfont-mincho [fonts-japanese-mincho] 00103-9 ii fonts-ipafont-gothic [fonts-japanese-gothic]00303-6 ii fonts-ipafont-mincho [fonts-japanese-mincho]00303-6 ii fonts-ipafont-nonfree-jisx0208 [fonts-japanese-mincho] 00103-18 ii fonts-vlgothic [fonts-japanese-gothic] 20120325-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#673247: advi: Japanese fonts no longer work
Package: advi Version: 1.10.2-1 Severity: normal It seems like advi no longer can handle Japanese fonts. I haven't quite dug into why this might be. $ platex simple.tex This is e-pTeX, Version 3.1415926-p3.2-110825-2.3 (utf8.euc) (TeX Live 2012/dev/Debian) restricted \write18 enabled. entering extended mode (./simple.tex pLaTeX2e <2006/11/10> (based on LaTeX2e <2011/06/27> patch level 0) Babel and hyphenation patterns for english, dumylang, nohyphenation, pi nyin, loaded. (/usr/share/texlive/texmf-dist/tex/platex/base/jarticle.cls Document Class: jarticle 2006/06/27 v1.6 Standard pLaTeX class (/usr/share/texlive/texmf-dist/tex/platex/base/jsize10.clo)) (./simple.aux) [1] (./simple.aux) ) Output written on simple.dvi (1 page, 436 bytes). Transcript written on simple.log. $ advi simple.dvi kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600 min10 mktexpk: don't know how to create bitmap font for min10. mktexpk: perhaps min10 is missing from the map file. kpathsea: Appending font creation commands to missfont.log. kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600 goth10 mktexpk: don't know how to create bitmap font for goth10. mktexpk: perhaps goth10 is missing from the map file. kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600 goth10 mktexpk: don't know how to create bitmap font for goth10. mktexpk: perhaps goth10 is missing from the map file. kpathsea: Appending font creation commands to missfont.log. Warning: file goth10.600pk is not found kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600 min10 mktexpk: don't know how to create bitmap font for min10. mktexpk: perhaps min10 is missing from the map file. kpathsea: Appending font creation commands to missfont.log. Warning: file min10.600pk is not found Uncaught exception: File "search.ml", line 209, characters 2-8: Assertion failed -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to ja_JP.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages advi depends on: ii dpkg 1.16.3 ii ghostscript-x9.05~dfsg-5 ii libc62.13-32 ii libfreetype6 2.4.9-1 ii libx11-6 2:1.4.99.901-2 ii libxinerama1 2:1.1.2-1 ii perl 5.14.2-9 ii tex-common 3.10 ii texlive-base 2011.20120424-1 ii texlive-binaries [texlive-base-bin] 2011.20120410-1 ii zlib1g 1:1.2.7.dfsg-1 advi recommends no packages. Versions of packages advi suggests: ii bzip2 1.0.6-1 ii fonts-ipaexfont-gothic [fonts-japanese-gothic] 00103-9 ii fonts-ipaexfont-mincho [fonts-japanese-mincho] 00103-9 ii fonts-ipafont-gothic [fonts-japanese-gothic]00303-6 ii fonts-ipafont-mincho [fonts-japanese-mincho]00303-6 ii fonts-ipafont-nonfree-jisx0208 [fonts-japanese-mincho] 00103-18 ii fonts-vlgothic [fonts-japanese-gothic] 20120325-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668138: pbuilder-uml doesn't work anymore
I think there is '--uml-debugmode' option that could be used. At Thu, 12 Apr 2012 18:01:48 +0400, Dmitry E. Oboukhov wrote: > > > $ pbuilder-user-mode-linux create --distribution sid --debug > Error: Unknown option [--debug] was specified > $ pbuilder-user-mode-linux create --debug --distribution sid > Error: Unknown option [--debug] was specified > $ pbuilder-user-mode-linux --debug create --distribution sid > Error: Unknown option [--debug] was specified > > > running with '--debug ' option might give more logs; looks like > > debootstrap is failing and it is usually a transient error, but not > > quite sure. > > > At Mon, 9 Apr 2012 10:39:54 +0400, > > Dmitry E. Oboukhov wrote: > >> > >> Package: pbuilder-uml > >> Version: 0.210 > >> > >> Recently I've upgraded my pbuilder (and pbuilder-uml) upto sid. > >> Since the action it doesn't work. It always finishes with such log: > >> > >> $ pbuilder-user-mode-linux create --distribution testing > >> Core dump limits : > >> soft - 0 > >> hard - NONE > >> Checking that ptrace can change system call numbers...OK > >> Checking syscall emulation patch for ptrace...OK > >> Checking advanced syscall emulation patch for ptrace...OK > >> Checking for tmpfs mount on /dev/shm...nothing mounted on /dev/shm > >> Checking PROT_EXEC mmap in /tmp/...OK > >> Checking for the skas3 patch in the host: > >> - /proc/mm...not found: No such file or directory > >> - PTRACE_FAULTINFO...not found > >> - PTRACE_LDT...not found > >> UML running in SKAS0 mode > >> Adding 31084544 bytes to physical memory to account for exec-shield gap > >> Initializing cgroup subsys cpuset > >> Linux version 2.6.32 (2.6.32) (root@fluid) (gcc version 4.4.5 (Debian > >> 4.4.5-8) ) #2 Tue Jan 17 15:44:25 UTC 2012 > >> Built 1 zonelists in Zone order, mobility grouping on. Total pages: 15565 > >> Kernel command line: eth0=tuntap,,,10.255.1.241 con0=fd:0,fd:1 con=pts > >> root=/dev/root rootflags=/ rootfstype=hostfs > >> ubd1=/home/dimka/.pbuilder-user-mode-linux/pbuilder-image > >> init=/usr/lib/rootstrap/builder devfs=nomount > >> rsworkdir=/home/dimka/.pbuilder-user-mode-linux > >> PID hash table entries: 256 (order: -1, 2048 bytes) > >> Dentry cache hash table entries: 8192 (order: 4, 65536 bytes) > >> Inode-cache hash table entries: 4096 (order: 3, 32768 bytes) > >> allocated 631240 bytes of page_cgroup > >> please try 'cgroup_disable=memory' option if you don't want memory cgroups > >> Memory: 24804k available > >> SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 > >> Hierarchical RCU implementation. > >> NR_IRQS:15 > >> Calibrating delay loop... 629.14 BogoMIPS (lpj=3145728) > >> Security Framework initialized > >> TOMOYO Linux initialized > >> Mount-cache hash table entries: 256 > >> Initializing cgroup subsys ns > >> Initializing cgroup subsys cpuacct > >> Initializing cgroup subsys memory > >> Initializing cgroup subsys devices > >> Initializing cgroup subsys freezer > >> Checking that host ptys support output SIGIO...Yes > >> Checking that host ptys support SIGIO on close...No, enabling workaround > >> Using 2.6 host AIO > >> NET: Registered protocol family 16 > >> bio: create slab at 0 > >> Switching to clocksource itimer > >> NET: Registered protocol family 2 > >> IP route cache hash table entries: 512 (order: 0, 4096 bytes) > >> TCP established hash table entries: 2048 (order: 3, 32768 bytes) > >> TCP bind hash table entries: 2048 (order: 2, 16384 bytes) > >> TCP: Hash tables configured (established 2048 bind 2048) > >> TCP reno registered > >> NET: Registered protocol family 1 > >> IRQ 9/mconsole: IRQF_DISABLED is not guaranteed on shared IRQs > >> mconsole (version 2) initialized on /home/dimka/.uml/AYm1mF/mconsole > >> Checking host MADV_REMOVE support... > >> MADV_REMOVE failed, err = -38 > >> Can't release memory to the host - memory hotplug won't be supported > >> Mapper v0.1 > >> mmapper_init - find_iomem failed > >> UML Watchdog Timer > >> VFS: Disk quotas dquot_6.5.2 > >> Dquot-cache hash table entries: 512 (order 0, 4096 bytes) > >> squashfs: version 4.0 (2009/01/31) Phillip Lougher > >> JFS: nTxBlock = 194, nTxLock = 1554 > >> SGI XFS with ACLs, security attributes, realtime, large block/inode > >> numbers, no debug enabled > >> SGI XFS Quota Management subsystem > >> Btrfs loaded > >> msgmni has been set to 48 > >> alg: No test for stdrng (krng) > >> io scheduler noop registered > >> io scheduler anticipatory registered > >> io scheduler deadline registered > >> io scheduler cfq registered (default) > >> SoftDog: cannot register miscdev on minor=130 (err=-16) > >> TCP cubic registered > >> NET: Registered protocol family 17 > >> Initialized stdio console driver > >> Console initialized on /dev/tty0 > >> console [tty0] enabled > >> Initializing software serial port version 1 > >> console [mc-1] enabled > >> Failed to initialize ubd device 0 :Couldn't determine size of device's file > >> ubdb: unknown partition table >
Bug#668138: pbuilder-uml doesn't work anymore
running with '--debug ' option might give more logs; looks like debootstrap is failing and it is usually a transient error, but not quite sure. At Mon, 9 Apr 2012 10:39:54 +0400, Dmitry E. Oboukhov wrote: > > Package: pbuilder-uml > Version: 0.210 > > Recently I've upgraded my pbuilder (and pbuilder-uml) upto sid. > Since the action it doesn't work. It always finishes with such log: > > $ pbuilder-user-mode-linux create --distribution testing > Core dump limits : > soft - 0 > hard - NONE > Checking that ptrace can change system call numbers...OK > Checking syscall emulation patch for ptrace...OK > Checking advanced syscall emulation patch for ptrace...OK > Checking for tmpfs mount on /dev/shm...nothing mounted on /dev/shm > Checking PROT_EXEC mmap in /tmp/...OK > Checking for the skas3 patch in the host: > - /proc/mm...not found: No such file or directory > - PTRACE_FAULTINFO...not found > - PTRACE_LDT...not found > UML running in SKAS0 mode > Adding 31084544 bytes to physical memory to account for exec-shield gap > Initializing cgroup subsys cpuset > Linux version 2.6.32 (2.6.32) (root@fluid) (gcc version 4.4.5 (Debian > 4.4.5-8) ) #2 Tue Jan 17 15:44:25 UTC 2012 > Built 1 zonelists in Zone order, mobility grouping on. Total pages: 15565 > Kernel command line: eth0=tuntap,,,10.255.1.241 con0=fd:0,fd:1 con=pts > root=/dev/root rootflags=/ rootfstype=hostfs > ubd1=/home/dimka/.pbuilder-user-mode-linux/pbuilder-image > init=/usr/lib/rootstrap/builder devfs=nomount > rsworkdir=/home/dimka/.pbuilder-user-mode-linux > PID hash table entries: 256 (order: -1, 2048 bytes) > Dentry cache hash table entries: 8192 (order: 4, 65536 bytes) > Inode-cache hash table entries: 4096 (order: 3, 32768 bytes) > allocated 631240 bytes of page_cgroup > please try 'cgroup_disable=memory' option if you don't want memory cgroups > Memory: 24804k available > SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 > Hierarchical RCU implementation. > NR_IRQS:15 > Calibrating delay loop... 629.14 BogoMIPS (lpj=3145728) > Security Framework initialized > TOMOYO Linux initialized > Mount-cache hash table entries: 256 > Initializing cgroup subsys ns > Initializing cgroup subsys cpuacct > Initializing cgroup subsys memory > Initializing cgroup subsys devices > Initializing cgroup subsys freezer > Checking that host ptys support output SIGIO...Yes > Checking that host ptys support SIGIO on close...No, enabling workaround > Using 2.6 host AIO > NET: Registered protocol family 16 > bio: create slab at 0 > Switching to clocksource itimer > NET: Registered protocol family 2 > IP route cache hash table entries: 512 (order: 0, 4096 bytes) > TCP established hash table entries: 2048 (order: 3, 32768 bytes) > TCP bind hash table entries: 2048 (order: 2, 16384 bytes) > TCP: Hash tables configured (established 2048 bind 2048) > TCP reno registered > NET: Registered protocol family 1 > IRQ 9/mconsole: IRQF_DISABLED is not guaranteed on shared IRQs > mconsole (version 2) initialized on /home/dimka/.uml/AYm1mF/mconsole > Checking host MADV_REMOVE support... > MADV_REMOVE failed, err = -38 > Can't release memory to the host - memory hotplug won't be supported > Mapper v0.1 > mmapper_init - find_iomem failed > UML Watchdog Timer > VFS: Disk quotas dquot_6.5.2 > Dquot-cache hash table entries: 512 (order 0, 4096 bytes) > squashfs: version 4.0 (2009/01/31) Phillip Lougher > JFS: nTxBlock = 194, nTxLock = 1554 > SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, > no debug enabled > SGI XFS Quota Management subsystem > Btrfs loaded > msgmni has been set to 48 > alg: No test for stdrng (krng) > io scheduler noop registered > io scheduler anticipatory registered > io scheduler deadline registered > io scheduler cfq registered (default) > SoftDog: cannot register miscdev on minor=130 (err=-16) > TCP cubic registered > NET: Registered protocol family 17 > Initialized stdio console driver > Console initialized on /dev/tty0 > console [tty0] enabled > Initializing software serial port version 1 > console [mc-1] enabled > Failed to initialize ubd device 0 :Couldn't determine size of device's file > ubdb: unknown partition table > Choosing a random ethernet address for device eth0 > Netdevice 0 (72:6a:aa:1b:e4:71) : > TUN/TAP backend - IP = 10.255.1.241 > registered taskstats version 1 > VFS: Mounted root (hostfs filesystem) readonly on device 0:12. > IRQ 3/console-write: IRQF_DISABLED is not guaranteed on shared IRQs > IRQ 2/console: IRQF_DISABLED is not guaranteed on shared IRQs > IRQ 10/winch: IRQF_DISABLED is not guaranteed on shared IRQs > builder running... > Using rootstrap module network from: > /usr/lib/rootstrap/modules/network > helper_wait : waitpid process 8265 failed, errno = 10 > * modprobe tun > * ifconfig tap1 10.255.1.241 netmask 255.255.255.255 up > * bash -c echo 1 > /proc/sys/net/ipv4/ip_forward > helper_wait : waitpid process 8274 failed, errno = 10 > * route add -host 10
Bug#666645: whizzytex: FTBFS: ! Package xkeyval Error: value `0pt' is not allowed.
At Sat, 31 Mar 2012 22:00:05 +0200, Lucas Nussbaum wrote: > > Source: whizzytex > Version: 1.3.2-1 > Severity: serious > Tags: wheezy sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20120331 qa-ftbfs > Justification: FTBFS on amd64 > > Hi, > > During a rebuild of all packages in sid, your package failed to build on > amd64. > Thanks, reproduced. Seems like latest texlive update breaks whizzytex documentation build. Any help welcome to fix this, I don't have a good idea of what's broken. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#667727: not multiarch-ready
Hi, Yeah, that's expected in the current design. What's the multiarch-way of LD_PRELOADing ? At Fri, 06 Apr 2012 11:50:06 +0200, St$(D+1(Bphane Glondu wrote: > > Package: cowbuilder > Version: 0.69 > Severity: wishlist > User: multiarch-de...@lists.alioth.debian.org > Usertags: multiarch > > Hello, > > cowbuilder doesn't work properly with multiarch. For example: > > # cowbuilder --login > # dpkg --add-architecture i386 > # apt-get update > [...] > # rm -f /usr/share/doc/gcc-4.7-base/changelog.Debian.gz # workaround another > unrelated multiarch bug > # apt-get install mg:i386 > [...] > # mg -n /etc/apt/sources.list > [... make some changes, save and quit ...] > ERROR: ld.so: object '/usr/lib/cowdancer/libcowdancer.so' from LD_PRELOAD > cannot be preloaded: ignored. > # exit > > After this sequence of commands, /etc/apt/sources.list has been edited > outside of the throw-away chroot. > > > Cheers, > > -- > St$(D+1(Bphane > > -- System Information: > Debian Release: wheezy/sid > APT prefers testing > APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 3.2.0-2-amd64 (SMP w/8 CPU cores) > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > > Versions of packages cowbuilder depends on: > ii cowdancer 0.68 > ii libc6 2.13-27 > ii pbuilder 0.208 > > cowbuilder recommends no packages. > > cowbuilder suggests no packages. > > -- no debconf information > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#613854: It should be useful to have those values printed also while --create and --update
At Wed, 25 Jan 2012 15:16:00 -0800 (PST), Regid Ichira wrote: > > I think it is useful to have it at the head of a log file. > And while I am at it, I think it is also useful to record the entire pbuilder > command line at the head of the log file. I don't think I should be further cluttering the logs here. > > --- On Wed, 1/25/12, Junichi Uekawa wrote: > > > I don't think it's really useful after all, you can always type date. > > > > At Thu, 17 Feb 2011 12:02:25 -0800 (PST), Regid Ichira wrote: > > > > > > It should be useful to have those values printed also while --create > > >and > > > --update. > > > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#664660: npm: npm throws exception on execution
Huh, I guess I just filed a duplicate bug with 'new upstream version' request. Please disregard. At Sun, 18 Mar 2012 17:59:32 +0900, Junichi Uekawa wrote: > > Package: npm > Severity: normal > Version: 0.2.19-1 > > > I've tried running npm inside a sid chroot, and it seems to be doing nothing > useful today apart from throwing an exception: > > $ npm > > node.js:201 > throw e; // process.nextTick error, or 'error' event on first tick > ^ > Error: No such module > at Object. (/usr/share/npm/lib/utils/output.js:8:21) > at Module._compile (module.js:441:26) > at Object..js (module.js:459:10) > at Module.load (module.js:348:32) > at Function._load (module.js:308:12) > at Module.require (module.js:354:17) > at require (module.js:370:17) > at Object. (/usr/share/npm/lib/utils/log.js:21:14) > at Module._compile (module.js:441:26) > at Object..js (module.js:459:10) > > > > > > -- System Information: > Debian Release: 6.0.4 > APT prefers stable > APT policy: (500, 'stable') > Architecture: i386 (i686) > > Kernel: Linux 2.6.32-bpo.5-686 (SMP w/2 CPU cores) > Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) (ignored: > LC_ALL set to ja_JP.UTF-8) > Shell: /bin/sh linked to /bin/bash > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#664660: npm: npm throws exception on execution
Package: npm Severity: normal Version: 0.2.19-1 I've tried running npm inside a sid chroot, and it seems to be doing nothing useful today apart from throwing an exception: $ npm node.js:201 throw e; // process.nextTick error, or 'error' event on first tick ^ Error: No such module at Object. (/usr/share/npm/lib/utils/output.js:8:21) at Module._compile (module.js:441:26) at Object..js (module.js:459:10) at Module.load (module.js:348:32) at Function._load (module.js:308:12) at Module.require (module.js:354:17) at require (module.js:370:17) at Object. (/usr/share/npm/lib/utils/log.js:21:14) at Module._compile (module.js:441:26) at Object..js (module.js:459:10) -- System Information: Debian Release: 6.0.4 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-bpo.5-686 (SMP w/2 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to ja_JP.UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#663950: [cowbuilder] Fails to build packages with read-only source oackage
I think pbuilder just preserves the permissions and fail if it's read-only; hard to understand if it is an unexpected behavior ? At Wed, 14 Mar 2012 08:37:27 + (GMT), Franz Schrober wrote: > > Package: cowbuilder > Version: 0.67 > Severity: normal > > Tried to build a package copied from a read-only medium. It fails during the > creation of the new source package. This can easily be reproduced > > > $ dget > -d http://snapshot.debian.org/archive/debian/20120310T034347Z/pool/main/c/cowdancer/cowdancer_0.68.dsc > $ chmod a=r cowdancer_0.68.dsc cowdancer_0.68.tar.gz > $ /usr/sbin/cowbuilder --build --buildresult "$HOME/results" > cowdancer_0.68.dsc > . > dpkg-source -b cowdancer-0.68 > dpkg-source: warning: no source format specified in debian/source/format, see > dpkg-source(1) > dpkg-source: info: using source format `1.0' > dpkg-source: info: building cowdancer in cowdancer_0.68.tar.gz > dpkg-source: info: building cowdancer in cowdancer_0.68.dsc > dpkg-source: error: cannot write cowdancer_0.68.dsc: Permission denied > dpkg-buildpackage: error: dpkg-source -b cowdancer-0.68 gave error exit > status 13 > E: Failed autobuilding of package > . > > This also happens for *.debian.tar.gz and *.diff.gz files (for non-native > packages of course) > > --- System information. --- > Architecture: amd64 > Kernel: Linux 3.2.0-2-amd64 > Debian Release: wheezy/sid > 500 testing www.debian-multimedia.org > --- Package information. --- > Depends(Version) | Installed > -+-=== > libc6 (>= 2.7) | 2.13-27 > pbuilder | 0.206 > cowdancer| 0.67 > Package's Recommends field is empty. > Package's Suggests field is empty. > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567484: pbuilder: -e$DEBEMAIL instead of -e$DEBFULLNAME
At Tue, 13 Mar 2012 19:53:01 + (UTC), Thorsten Glaser wrote: > > Miguel Colon dixit: > > >>That makes sense: with no args, dpkg-buildpackage does the right thing > >>if DEBEMAIL is set and DEBFULLNAME is set. > >>So let the work be done by dpkg-buildpackage. > > I’ve found that most Debian tools work best if DEBFULLNAME is not set > and DEBEMAIL is "Foo Bar ". > Any change should be accompanied by a documentation update. I think the documentation pbuilderrc is already out of sync with code, so whatever we decide upon should be documented. > bye, > //mirabilos > -- > “Having a smoking section in a restaurant is like having > a peeing section in a swimming pool.” > -- Edward Burr > > > > ___ > Pbuilder-maint mailing list > pbuilder-ma...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pbuilder-maint -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661856: Add SMP support to qemubuilder
At Fri, 09 Mar 2012 11:04:59 +0100,
Mike Gabriel wrote:
>
> [1 ]
> [1.1 ]
> Hi Junichi,
>
> On Do 08 M$(D+#(Br 2012 22:53:26 CET Junichi Uekawa wrote:
>
> >
> > I usually work offline and if you can attach the patch to the mail
> > as git-format-patch, things would work much faster.
> >
> > At Fri, 02 Mar 2012 00:33:05 +0100,
> > Mike Gabriel wrote:
> >>
> >> Package: qemubuilder
> >> Version: 0.67
> >> Severity: wishlist
> >> Tags: patch
> >>
> >> Under this URL:
> >> http://code.das-netzwerkteam.de/gitweb?p=build/cowdancer.git;a=commitdiff;h=fa63fa1257701e9097c8042f686b1555cfb25c2c
> >>
> >> ...you find a patch that shows how to add support for qemu's -smp
> >> option to qemubuilder.
>
> Patch is attached...
Seems like missing documentation and handling for when --smp option is not
available; added.
>
> Greets,
> Mike
>
>
> --
>
> DAS-NETZWERKTEAM
> mike gabriel, dorfstr. 27, 24245 barmissen
> fon: +49 (4302) 281418, fax: +49 (4302) 281419
>
> GnuPG Key ID 0xB588399B
> mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de
>
> freeBusy:
> https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb
> [1.2 0001-Add-SMP-option-and-environment-variable-support.patch
> ]
> >From fa63fa1257701e9097c8042f686b1555cfb25c2c Mon Sep 17 00:00:00 2001
> From: Mike Gabriel
> Date: Fri, 2 Mar 2012 00:03:27 +0100
> Subject: [PATCH] Add SMP option and environment variable support.
>
> ---
> debian/changelog |1 +
> parameter.c | 14 ++
> parameter.h |1 +
> qemubuilder.c|2 ++
> 4 files changed, 18 insertions(+), 0 deletions(-)
>
> diff --git a/debian/changelog b/debian/changelog
> index aaa47cd..132f285 100644
> --- a/debian/changelog
> +++ b/debian/changelog
> @@ -4,6 +4,7 @@ cowdancer (0.67+nmu1) UNRELEASED; urgency=low
>* Prefer ext2 over ext3.
>* Fix ext2/ext3 fs patch for arm/armel architecture.
>* Mount / partition rw by kernel.
> + * Add SMP option and environment variable support.
>
> -- Mike Gabriel Wed, 15 Feb 2012
> 22:20:39 +0100
>
> diff --git a/parameter.c b/parameter.c
> index 83760c1..83b3a34 100644
> --- a/parameter.c
> +++ b/parameter.c
> @@ -141,6 +141,10 @@ int load_config_file(const char* config, pbuilderconfig*
> pc)
> {
> pc->othermirror=strdup(delim);
> }
> + else if (!strcmp(buf, "SMP"))
> + {
> + pc->smp=strdup(delim);
> + }
> else if (!strcmp(buf, "DEBBUILDOPTS"))
> {
> pc->debbuildopts=strdup(delim);
> @@ -208,6 +212,7 @@ int cpbuilder_dumpconfig(pbuilderconfig* pc)
>DUMPSTR(distribution);
>DUMPSTR(components);
>DUMPSTR(othermirror);
> + DUMPSTR(smp);
>DUMPSTR(debbuildopts);
>DUMPINT(binary_arch);
>DUMPSTR(http_proxy);
> @@ -259,6 +264,7 @@ int parse_parameter(int ac, char** av,
> {"distribution", required_argument, 0, 0},
> {"components", required_argument, 0, 0},
> {"othermirror", required_argument, 0, 0},
> +{"smp", required_argument, 0, 0},
> {"debbuildopts", required_argument, 0, 0},
> {"binary-arch", no_argument, 0, 0},
> {"inputfile", required_argument, 0, 0},
> @@ -462,6 +468,14 @@ int parse_parameter(int ac, char** av,
> /* pass it for cowbuilder */
> PASS_TO_PBUILDER_WITH_PARAM
> }
> + else if (!strcmp(long_options[index_point].name,"smp"))
> + {
> + /* this is for qemubuilder */
> + pc.smp=strdup(optarg);
> +
> + /* pass it for cowbuilder */
> + PASS_TO_PBUILDER_WITH_PARAM
> + }
> else if (!strcmp(long_options[index_point].name,"http-proxy"))
> {
> /* this is for qemubuilder */
> diff --git a/parameter.h b/parameter.h
> index e3d8536..bc72b3a 100644
> --- a/parameter.h
> +++ b/parameter.h
> @@ -54,6 +54,7 @@ typedef struct pbuilderconfig
>/* more qemu-isque options */
>char* kernel_image;
>char* initrd;
> + char* smp;
>int memory_megs; /* megabytes of memory */
>char* arch;
>char* arch_diskdevice;
> diff --git a/qemubuilder.c b/qemubuilder.c
> index 77c9282..db74d47 100755
> --- a/qemubuilder.c
> +++ b/qemubuilder.c
> @@ -355,6 +355,8 @@ static int fork_qemu(const char* hda, const char* hdb,
> const struct pbuilderconf
>argv[argc++]=strdupa(machine);
>argv[argc++]="-m";
>argv[argc++]=mem;
> + argv[argc++]="-smp";
> + argv[argc++]=strdupa(pc->smp);
>argv[argc++]="-kernel";
>argv[argc++]=strdupa(kernel_image);
>if (initrd && strcmp(initrd, ""))
> --
> 1.7.2.5
>
> [2 Digitale PGP-Unterschrift ]
>
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#660823: qemubuilder: Gnu Hurd support
I don't think qemu has support for directly loading HURD kernel... and
looks up the manpage and the man page says '-kernel' can be any kernel
in multiboot format. Maybe most parts are already ready in qemu /
debootstrap side too.
Cool.
At Wed, 22 Feb 2012 19:06:17 +1100,
Dmitry Smirnov wrote:
>
> Author: Dmitry Smirnov
> Last-Update: 2012-02-22
> Forwarded: no
> Description: partial support for Gnu Hurd "hurd-i386"
> This patch help to set qemu/kvm arch for "hurd-i386"
> architecture to prevent error
> "Your architecture hurd-i386 does not seem to be supported"
>
>
> --- a/qemuarch.c
> +++ b/qemuarch.c
> @@ -121,8 +121,10 @@
> return "qemu-system-mips";
>else if (!strcmp(arch, "mipsel"))
> return "qemu-system-mipsel";
> - else if (!strcmp(arch, "i386") ||
> -!strcmp(arch, "amd64"))
> + else if (!strcmp(arch, "i386")
> +|| !strcmp(arch, "amd64")
> +|| !strcmp(arch, "hurd-i386")
> + )
> {
>/* we're leaking this memory, but don't care too much */
>char* host_arch = get_host_dpkg_arch();
> @@ -143,6 +145,8 @@
>else
> return "qemu-system-x86_64";
> }
> + else if (!strcmp(arch, "hurd-i386"))
> +return "qemu";
>else if (!strcmp(arch, "powerpc"))
> return "qemu-system-ppc";
>else if (!strcmp(arch, "sparc"))
> @@ -160,7 +164,8 @@
>!strcmp(arch, "armel"))
> return "versatilepb";
>else if (!strcmp(arch, "i386") ||
> -!strcmp(arch, "amd64"))
> +!strcmp(arch, "hurd-i386") ||
> + !strcmp(arch, "amd64"))
> return "pc";
>else if (!strcmp(arch, "mips")||
> !strcmp(arch, "mipsel"))
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#579028: pbuilder: installs untrusted packages without asking
At Tue, 06 Mar 2012 02:29:25 +0100, Simon Ruderich wrote: > > Package: pbuilder > Version: 0.206 > Tags: patch > Followup-For: Bug #579028 > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Dear Maintainer, > > The attached patch changes the defaults to always enforce signed > repositories and aborts if an untrusted/manipulated package is > installed. It adds the new option --keyring (APTKEYRINGS) to add > additional keyrings, which are then used to verify the (local) > signed repositories. This way no untrusted packages can be > installed. > > To still allow untrusted/unsigned repositories - they are a very > bad idea and allow remote attackers performing a MITM to take > over the system, including all built packages - the new option > - --allow-untrusted (ALLOWUNTRUSTED) was added. > > I tested it with the official Debian repository, signed and > unsigned local repositories and it works fine for me. But I'm > only a "normal" pbuilder user, so I might have missed something. > Please test the patch. > > I haven't tested it with cdebootstrap, but it should work as > well. I think cowbuilder/qemubuilder won't let you an unknown arbitrary option to pbuilder; you'll need to add a patch there as well. I don't know if pdebuild will need any change; I guess not. > > The old PBUILDERSATISFYDEPENDSOPT --check-key option was > deprecated and is no longer used (it emits a warning now) as > validation is the default now. > > The patch also contains documentation updates for the new > options/variables and updates for the NEWS file describing the > necessary changes to continue using untrusted packages (but > please don't do that - especially as a Debian developer). > > Please have a look and include the patch as soon as possible to > fix this security issue. > > Regards, > Simon > > - -- System Information: > Debian Release: wheezy/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 3.2.0-1-amd64 (SMP w/8 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > > Versions of packages pbuilder depends on: > ii cdebootstrap 0.5.8+b1 > ii coreutils 8.13-3 > ii debconf [debconf-2.0] 1.5.41 > ii debianutils4.2.1 > ii debootstrap1.0.38 > ii dpkg-dev 1.16.1.2 > ii wget 1.13.4-2 > > Versions of packages pbuilder recommends: > pn devscripts 2.11.4 > pn fakeroot1.18.2-1 > pn sudo > > Versions of packages pbuilder suggests: > pn cowdancer > pn gdebi-core > pn pbuilder-uml > > - -- debconf information excluded > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.12 (GNU/Linux) > > iQIcBAEBCAAGBQJPVWhvAAoJEJL+/bfkTDL5ivAP/iayE8NRQnyk2HW8R+NiRXU3 > uavLilwwpmEZyuciu8GxMQIAhT9HYd/DlkhF9I+yBSd30TO3fl0xW7YV9SaIZ+bv > IPwnZbHri4KfeV9Zob/gd2jrT9A2QCoFRW0ny4XNCK3NvtWH5KuH+TG2Mq5CQqdN > j4VJ3+76oJcbQbU7AUYXfvKDAsEb7gX+VwTEFLS4GrPkni/FIQJ8HHJhlTscyuCD > gQANCoRFZHVSMaas3xqi9KYFKgVS4BZ5Z/9FZuLeY5kWBfcbnIhQloVOWTQZIMRI > PhnqP1g62XlPu71K3a/Y2RMAcy3Gs6sUbW4OianIr2iskCndejih/MCb+3LmBFCg > Ekxi/CcJGrc7a0pV57Qs8Iwkm1siRZZUxcp4xdD3mo9iayoOt4sfFyrvBCYryilQ > 7JKpQc3iNoV3EQql6KBu5G+GmFFWHmokpLvVY27n8LgkV2YSb2wrgxqXPfxcYHj7 > 0j/y2MFw+HOX/d5YSESMLxn9aiZBi7CkMtlMemzqizxlNlL/+OOZiDsi4vdH8L/j > Y0c2i9efjNeooc0/B9wASu/Ck8SWV8wW1EcfTag0p9Rp0avy4hoQUmG+MtgQsV0l > MQuWWysyxeJFX4Z8ooau82L6sIGC0L073JH6Y/C7uTOz9gKt+e5tV3fnU+pkWpqH > oF3CcmlykKX4SYzhUI/e > =6EPj > -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#579028: pbuilder: installs untrusted packages without asking
At Tue, 06 Mar 2012 02:29:25 +0100, Simon Ruderich wrote: > > [1 ] > Package: pbuilder > Version: 0.206 > Tags: patch > Followup-For: Bug #579028 > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Dear Maintainer, > > The attached patch changes the defaults to always enforce signed > repositories and aborts if an untrusted/manipulated package is > installed. It adds the new option --keyring (APTKEYRINGS) to add > additional keyrings, which are then used to verify the (local) > signed repositories. This way no untrusted packages can be > installed. I don't share the opinion that this should be a grave bug to change the default, and in order to change the default you need to deprecate a command-line option and introduce two new command-line options when you could have just changed the default shipping pbuilderrc. > To still allow untrusted/unsigned repositories - they are a very > bad idea and allow remote attackers performing a MITM to take > over the system, including all built packages - the new option > - --allow-untrusted (ALLOWUNTRUSTED) was added. I don't care what you think is a bad idea. > > I tested it with the official Debian repository, signed and > unsigned local repositories and it works fine for me. But I'm > only a "normal" pbuilder user, so I might have missed something. > Please test the patch. > > I haven't tested it with cdebootstrap, but it should work as > well. > > The old PBUILDERSATISFYDEPENDSOPT --check-key option was > deprecated and is no longer used (it emits a warning now) as > validation is the default now. > > The patch also contains documentation updates for the new > options/variables and updates for the NEWS file describing the > necessary changes to continue using untrusted packages (but > please don't do that - especially as a Debian developer). > > Please have a look and include the patch as soon as possible to > fix this security issue. Although I don't agree with most of the things you have stated in the mail, your patch looks reasonably well written and I don't object to applying it first and see who suffers; I suppose cowbuilder / qemubuilder people will, because they don't yet support the new option. > > Regards, > Simon > > - -- System Information: > Debian Release: wheezy/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 3.2.0-1-amd64 (SMP w/8 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > > Versions of packages pbuilder depends on: > ii cdebootstrap 0.5.8+b1 > ii coreutils 8.13-3 > ii debconf [debconf-2.0] 1.5.41 > ii debianutils4.2.1 > ii debootstrap1.0.38 > ii dpkg-dev 1.16.1.2 > ii wget 1.13.4-2 > > Versions of packages pbuilder recommends: > pn devscripts 2.11.4 > pn fakeroot1.18.2-1 > pn sudo > > Versions of packages pbuilder suggests: > pn cowdancer > pn gdebi-core > pn pbuilder-uml > > - -- debconf information excluded > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.12 (GNU/Linux) > > iQIcBAEBCAAGBQJPVWhvAAoJEJL+/bfkTDL5ivAP/iayE8NRQnyk2HW8R+NiRXU3 > uavLilwwpmEZyuciu8GxMQIAhT9HYd/DlkhF9I+yBSd30TO3fl0xW7YV9SaIZ+bv > IPwnZbHri4KfeV9Zob/gd2jrT9A2QCoFRW0ny4XNCK3NvtWH5KuH+TG2Mq5CQqdN > j4VJ3+76oJcbQbU7AUYXfvKDAsEb7gX+VwTEFLS4GrPkni/FIQJ8HHJhlTscyuCD > gQANCoRFZHVSMaas3xqi9KYFKgVS4BZ5Z/9FZuLeY5kWBfcbnIhQloVOWTQZIMRI > PhnqP1g62XlPu71K3a/Y2RMAcy3Gs6sUbW4OianIr2iskCndejih/MCb+3LmBFCg > Ekxi/CcJGrc7a0pV57Qs8Iwkm1siRZZUxcp4xdD3mo9iayoOt4sfFyrvBCYryilQ > 7JKpQc3iNoV3EQql6KBu5G+GmFFWHmokpLvVY27n8LgkV2YSb2wrgxqXPfxcYHj7 > 0j/y2MFw+HOX/d5YSESMLxn9aiZBi7CkMtlMemzqizxlNlL/+OOZiDsi4vdH8L/j > Y0c2i9efjNeooc0/B9wASu/Ck8SWV8wW1EcfTag0p9Rp0avy4hoQUmG+MtgQsV0l > MQuWWysyxeJFX4Z8ooau82L6sIGC0L073JH6Y/C7uTOz9gKt+e5tV3fnU+pkWpqH > oF3CcmlykKX4SYzhUI/e > =6EPj > -END PGP SIGNATURE- > [2 0001-Enforce-valid-signed-repositories-by-default.patch us-ascii (7bit)>] > >From cadc48fb599d436577a6efedc7f25e175652a3a1 Mon Sep 17 00:00:00 2001 > Message-Id: > > From: Simon Ruderich > Date: Tue, 6 Mar 2012 02:00:48 +0100 > Subject: [PATCH] Enforce valid signed repositories by default. > > --- > debian/NEWS | 19 ++ > debian/pbuilder-test/00_prepinstall |2 +- > pbuilder-checkparams| 18 + > pbuilder-createbuildenv |5 > pbuilder-satisfydepends-aptitude|2 +- > pbuilder-satisfydepends-checkparams | 19 + > pbuilder-updatebuildenv |6 + > pbuilder.8 | 20 ++- > pbuilderrc | 23 + > pbuilderrc.5| 36 ++ > 10 files changed, 124 insertions(+), 26 deletions(-) > > diff --git a/debian/NEWS b/debian/NEWS > index 6d1
Bug#659419: pbuilder: security in pbuilder
I take this as a request to change the default behavior.
At Sat, 11 Feb 2012 00:27:54 +0100,
Christoph Anton Mitterer wrote:
>
> Package: pbuilder
> Version: 0.206
> Severity: important
>
>
> Hi.
>
> Marking this as important, as it might be secrutiy relevant:
>
>
> Installing potentially unverified packages is basically like posting your
> root password on the internet and removing the last character.
>
>
> Reading through pbuilderrc(5) I found these:
>
> 1) > PBUILDERSATISFYDEPENDSOPT=('--check-key')
>> Array of flags to give to pbuilder-satisfydepends. Specifying
>> --check-key here will try to verify key signatures.
> What does try mean here? Can't this be changed to just fail if verification
> doesn't work?
>
>
> 2) > APTGETOPT=('--force-yes')
>> Extra flags to give to apt-get. Default is --force-yes, which
>> will skip key verification of packages to be installed. Unset if
>> you want to enable key verification.
>
> If this disables key verification it should be disabled per default.
>
>
> Cheers,
> Chris.
>
> btw: Some time ago, I've already reported a bug about the insecure usage
> of debootstrap.
> You've then added the --keyring option as default.
> It seems that debbootstrap changed to do this per default itself (have a
> look).
> So when you depend on the recent enough version, you could drop this again.
>
>
>
> ___
> Pbuilder-maint mailing list
> pbuilder-ma...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pbuilder-maint
>
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661856: Add SMP support to qemubuilder
I usually work offline and if you can attach the patch to the mail as git-format-patch, things would work much faster. At Fri, 02 Mar 2012 00:33:05 +0100, Mike Gabriel wrote: > > Package: qemubuilder > Version: 0.67 > Severity: wishlist > Tags: patch > > Under this URL: > http://code.das-netzwerkteam.de/gitweb?p=build/cowdancer.git;a=commitdiff;h=fa63fa1257701e9097c8042f686b1555cfb25c2c > > ...you find a patch that shows how to add support for qemu's -smp > option to qemubuilder. > > Greets, > Mike > > -- > > DAS-NETZWERKTEAM > mike gabriel, dorfstr. 27, 24245 barmissen > fon: +49 (4302) 281418, fax: +49 (4302) 281419 > > GnuPG Key ID 0xB588399B > mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de > > freeBusy: > https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#659220: please support bzip2, pbzip2 and pigz
Did you check out the --compressprog option? At Thu, 9 Feb 2012 10:24:37 +0100, Holger Levsen wrote: > > package: pbuilder > severity: wishlist > > Hi, > > it would be awesome if pbuilder would support packging the base.tgz with > (p)bzip2 or pigz, thus using more than one cpu-core for packing and unpacking > of it. > > bzip2 support would be "enough" as pbzip2 behaves close enough to bzip2 > (which > pigz deosnt achieve for gzip), though obviously native support for parallel > implementations would be much better. > > +, thanks for pbuilder! > > > cheers, > Holger > > > > ___ > Pbuilder-maint mailing list > pbuilder-ma...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pbuilder-maint > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#658991: qemu is uninstallable in sid
Package: ipxe Version: 1.0.0+git-20120202.f6840ba-2 Severity: grave # justification; makes packages uninstallable in sid. I don't quite get it. Your changelog seems to imply some files moved from qemu to one of ipxe packages; I think that usually implies Replaces, not Breaks. Is that what you mean? ipxe (1.0.0+git-20120202.f6840ba-2) unstable; urgency=low * Fix grub setup and restrict entry by default. (closes: #658465) * Install only combined images into ipxe package. * Install rom images needed for qemu into ipxe-qemu package. - Add breaks against qemu and qemu-kvm. * Disable rom banner timeout. (closes: #638574) -- Bastian Blank Fri, 03 Feb 2012 19:04:56 +0100 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#606158: pbuilder: Please integrate eatmydata
Hi, Sounds interesting, except for that I don't see a patch actually attached. At Mon, 06 Dec 2010 22:39:20 +0100, Adrian von Bidder wrote: > > Package: pbuilder > Version: 0.199+nmu1 > Severity: wishlist > Tags: patch > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Yodel! > > As previously threatened^Wannounced: Here's my proposed eatmydata > integration in a rough draft. > > Eatmydata is basically always used (and installed in the chroot) unless > - --no-eatmydata is specified. > > To be honest: I didn't test the --no-eatmydata option at all, will do > that soon-ish. I did test that eatmydata is used in pbuilder create > (works), pbuilder build (works), btrfsbuilder create (doesn't seem to > use eatmydata for some reason, have yet to investigate this) and > btrfsbuilder build (works.) Where it is used, especially in btrfs which > is allergic to sync/fsync, it makes quite a big difference. > > cheers > - -- vbi > > > > > - -- System Information: > Debian Release: squeeze/sid > APT prefers testing > APT policy: (700, 'testing'), (600, 'unstable'), (1, 'experimental') > Architecture: i386 (i686) > > Kernel: Linux 2.6.36-trunk-686 (SMP w/2 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > > Versions of packages pbuilder depends on: > ii cdebootstrap 0.5.7 Bootstrap a Debian system > ii coreutils 8.5-1 GNU core utilities > ii debconf [debconf-2.0] 1.5.36 Debian configuration management > sy > ii debianutils 3.4Miscellaneous utilities specific > t > ii debootstrap 1.0.26 Bootstrap a basic Debian system > ii wget 1.12-2.1 retrieves files from the web > > Versions of packages pbuilder recommends: > ii devscripts2.10.69scripts to make the life of a > Debi > ii fakeroot 1.14.4-1 Gives a fake root environment > ii sudo 1.7.4p4-2 Provide limited super user > privile > > Versions of packages pbuilder suggests: > pn cowdancer (no description available) > ii eatmydata 15-4 library and utilities designed > to > pn gdebi-core (no description available) > pn pbuilder-uml (no description available) > > - -- debconf information: > pbuilder/mirrorsite: http://ftp.ch.debian.org/debian/ > pbuilder/nomirror: > pbuilder/rewrite: false > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.10 (GNU/Linux) > > iEYEARECAAYFAkz9WAgACgkQKqpm2L3fmXpSpgCePIMyd0Bu9MqbH3JlT2GTYsWz > rK4An1QOs2OM5PZzSNNrRwYbVoX4C1gq > =Sx1h > -END PGP SIGNATURE- > > > > ___ > Pbuilder-maint mailing list > pbuilder-ma...@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/pbuilder-maint > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#618959: pdebuild -- --debbuildopts=whatever not propagated to dpkg-buildpackage
I think I added this line in the man page to make it clearer: Note that for pdebuild, debbuildopts needs to be specified as a pdebuild option in the command-line, not as a pbuilder option. I think the reason was that pdebuild needs to change behavior depending on some parts of debbuildopts, and so it cannot be sent as a pass-thru option. At Sat, 19 Mar 2011 22:40:08 +0100, Yann Dirson wrote: > > Package: pbuilder > Version: 0.199+nmu2 > Severity: normal > > OTOH, setting DEBBUILDOPTS in pbuilderrc does work - but my reading of > the doc is that the flag ought to work. I did not check however if the > problem was on pbuilder's or pdebuild's side. > > -- System Information: > Debian Release: wheezy/sid > APT prefers testing > APT policy: (990, 'testing'), (500, 'oldstable'), (500, 'unstable'), (500, > 'stable'), (101, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 2.6.37.2 (SMP w/4 CPU cores) > Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/bash > > Versions of packages pbuilder depends on: > ii coreutils 8.5-1 GNU core utilities > ii debconf [debconf-2.0] 1.5.38 Debian configuration management > sy > ii debianutils 3.4.4 Miscellaneous utilities specific > t > ii debootstrap 1.0.28 Bootstrap a basic Debian system > ii wget 1.12-2.1 retrieves files from the web > > Versions of packages pbuilder recommends: > ii devscripts2.10.71scripts to make the life of a > Debi > ii fakeroot 1.14.5-1 Gives a fake root environment > ii sudo 1.7.4p6-1 Provide limited super user > privile > > Versions of packages pbuilder suggests: > ii cowdancer 0.62+nmu2 Copy-on-write directory tree > utili > pn gdebi-core (no description available) > pn pbuilder-uml (no description available) > > -- debconf information: > pbuilder/mirrorsite: ftp://ftp.fr.debian.org/debian > pbuilder/nomirror: > pbuilder/rewrite: false > > > > ___ > Pbuilder-maint mailing list > pbuilder-ma...@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/pbuilder-maint > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#613854: It should be useful to have those values printed also while --create and --update
I don't think it's really useful after all, you can always type date. At Thu, 17 Feb 2011 12:02:25 -0800 (PST), Regid Ichira wrote: > > It should be useful to have those values printed also while --create and > --update. > > > > > > > > ___ > Pbuilder-maint mailing list > pbuilder-ma...@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/pbuilder-maint > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#626056: pbuilder: Corrupt Packages.gz
I assume this was a transient bug ? At Sun, 08 May 2011 13:31:41 +0200, Torquil Macdonald S$(D)L(Brensen wrote: > > Package: pbuilder > Version: 0.199+nmu1 > Severity: normal > > When running "pbuilder --create --distribution sid", I get this error message: > > tmac@tmac:~$ su > Password: > tmac:/home/tmac# nano /etc/pbuilderrc > tmac:/home/tmac# pbuilder --create --distribution sid > W: /root/.pbuilderrc does not exist > I: Distribution is sid. > I: Building the build environment > I: running debootstrap > /usr/sbin/debootstrap > I: Retrieving Release > I: Retrieving Release.gpg > I: Checking Release signature > I: Valid Release signature (key id 9FED2BCBDCD29CDF762678CBAED4B06F473041FA) > I: Retrieving Packages > I: Validating Packages > W: http://ftp.uk.debian.org/debian/dists/sid/main/binary-i386/Packages.bz2 > was corrupt > I: Retrieving Packages > I: Validating Packages > W: http://ftp.uk.debian.org/debian/dists/sid/main/binary-i386/Packages.gz was > corrupt > I: Retrieving Packages > E: Couldn't download dists/sid/main/binary-i386/Packages > E: debootstrap failed > W: Aborting with an error > I: cleaning the build env > I: removing directory /var/cache/pbuilder/build//2943 and its subdirectories > > The same happends with no --distribution argument. My /etc/pbuilderrc is very > simply, containing only a mirror: > > # this is your configuration file for pbuilder. > # the file in /usr/share/pbuilder/pbuilderrc is the default template. > # /etc/pbuilderrc is the one meant for overwritting defaults in > # the default template > # > # read pbuilderrc.5 document for notes on specific options. > MIRRORSITE=http://ftp.de.debian.org/debian > > I have not modified anything within /etc/pbuilder/. The same problem happens > with > MIRRORSITE=http://ftp.uk.debian.org/debian > > Best regards > Torquil S$(D)L(Brensen > > -- System Information: > Debian Release: 6.0.1 > APT prefers stable > APT policy: (500, 'stable') > Architecture: i386 (i686) > > Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/bash > > Versions of packages pbuilder depends on: > ii coreutils8.5-1 GNU core utilities > ii debconf [debconf-2.0]1.5.36.1Debian configuration management > sy > ii debianutils 3.4 Miscellaneous utilities specific > t > ii debootstrap 1.0.26+squeeze1 Bootstrap a basic Debian system > ii wget 1.12-2.1retrieves files from the web > > Versions of packages pbuilder recommends: > pn devscripts (no description available) > ii fakeroot 1.14.4-1Gives a fake root environment > ii sudo 1.7.4p4-2.squeeze.2 Provide limited super user > privile > > Versions of packages pbuilder suggests: > pn cowdancer (no description available) > pn gdebi-core (no description available) > pn pbuilder-uml (no description available) > > -- debconf information: > * pbuilder/mirrorsite: http://ftp.de.debian.org/debian > pbuilder/nomirror: > * pbuilder/rewrite: false > > > > ___ > Pbuilder-maint mailing list > pbuilder-ma...@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/pbuilder-maint -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#655297: [examples/rebuild]: buildall executes dget with wrong url
At Tue, 10 Jan 2012 13:53:36 +0800,
Aron Xu wrote:
>
> Package: pbuilder
> Severity: normal
> Tags: patch
> Version: 0.205
>
> When I was trying to rebuild some packages of Sid from archive, I
> tried to use examples/rebuild/buildall and then resulted into many
> failures like this:
>
> dget: curl aisleriot_1:3.2.2-1.dsc
> http://mirrors/debian/pool/main/a/aisleriot/aisleriot_1:3.2.2-1.dsc
> failed
>
> This was caused by having urls with ":" inside. The following patch
> can fix the problem.
>
> --- /usr/share/doc/pbuilder/examples/rebuild/buildall 2010-06-29
> 09:33:04.0 +0800
> +++ buildall2012-01-10 13:52:22.867288056 +0800
> @@ -34,7 +34,7 @@
> G=$(grep-dctrl -S -n -s Directory,Version $PACKAGE ../../Sources)
> set -- $G
> DIR=$1 VER=$2
> -dget -x ${MIRROR}/debian/${DIR}/${PACKAGE}_${VER}.dsc > /dev/null
> 2> $LOGDIR/.$PACKAGE
> +dget -x ${MIRROR}/debian/${DIR}/${PACKAGE}_${VER##:}.dsc >
> /dev/null 2> $LOGDIR/.$PACKAGE
## doesn't work here, does it?
something more like ${VER//:*}
>
> cd $(find . -type d ! -name .)
> mkdir -p $BUILDDIR/$PACKAGE/result
>
> --
> Regards,
> Aron Xu
>
>
>
> ___
> Pbuilder-maint mailing list
> pbuilder-ma...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pbuilder-maint
>
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#606687: ccache support fails in the face of su PATH mangling
Looks reasonable, applied. This fell through the cracks (I haven't been reading all the mail backlogs during my MIA period last year, so if you find good bug reports that need triaging, it might be helpful to just raise the subject). At Wed, 28 Dec 2011 17:24:34 +1300, Dean Evans wrote: > > Is there any chance this patch could be included in a future release? > > The ability to use ccache in pbuilder is extremely handy so it would be > great if it could be. > > > Thanks, > Dean > > > > ___ > Pbuilder-maint mailing list > pbuilder-ma...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pbuilder-maint > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#641118: question answered.
At Mon, 26 Dec 2011 20:34:39 +0100, J$(D+S(Brg Sommer wrote: > > [1 ] > Junichi Uekawa hat am Sun 04. Dec, 22:27 (+0900) geschrieben: > > I think the bug report was asking a question about existing feature and > > that's already a solved bug. > > I would object this. The buildplace option is more a workaround than a > solution. and I object to your objection, because the knob is already there. More seriously though, if we were to go and make it reasonably random; then I think we'll want to have some way of easily knowing which chroot is running on which directory. Is there a good way to do that? > -- > Wer geliebt, kann nicht vergessen, > Wer vergisst, hat nie geliebt, > Wer geliebt und doch vergessen, > Hat vergessen, wie man liebt! > [2 Digital signature http://en.wikipedia.org/wiki/OpenPGP > ] > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#641118: question answered.
At Mon, 26 Dec 2011 20:34:39 +0100, J$(D+S(Brg Sommer wrote: > > [1 ] > Junichi Uekawa hat am Sun 04. Dec, 22:27 (+0900) geschrieben: > > I think the bug report was asking a question about existing feature and > > that's already a solved bug. > > I would object this. The buildplace option is more a workaround than a > solution. and I object to your objection, because the knob is already there. > -- > Wer geliebt, kann nicht vergessen, > Wer vergisst, hat nie geliebt, > Wer geliebt und doch vergessen, > Hat vergessen, wie man liebt! > [2 Digital signature http://en.wikipedia.org/wiki/OpenPGP > ] > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#652634: Allow to copy additional files out of the build directory
Hi,
I'd use a shell array for specifying the values; but yes I think I
too wanted this feature at one point.
Would list of filename (I will imagine there will be requests for all
sorts of wildcards after release, which is kind of a pain) be useful
or a directory that a post-build script can write to after build be
useful? (I think qemubuilder needed something to do with a specific
directory that you can write to, but I will need to check how I did
it).
At Mon, 19 Dec 2011 14:12:38 +0100,
Guido G$(D+d(Bnther wrote:
>
> [1 ]
> Package: pbuilder
> Version: 0.204
> Severity: wishlist
> Tags: patch
>
> Hi,
> I needed to nose's nosetests.xml and coverage file out of the build
> directory so it can be consumed by Jenkins to display the test results.
>
> Attached patch allows for this by introducing $ADDITIONAL_BUILDRESULT
> which can be set to a file list to be copied out of the builddir. This
> might need some tweaking before it can be applied but I wanted to get
> some feedback first whether this is the right way to go?
>
> Cheers,
> -- Guido
>
>
> -- System Information:
> Debian Release: wheezy/sid
> APT prefers testing
> APT policy: (990, 'testing'), (50, 'unstable'), (1, 'experimental')
> Architecture: i386 (i686)
>
> Kernel: Linux 3.1.0-1-686-pae (SMP w/2 CPU cores)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
>
> Versions of packages pbuilder depends on:
> ii cdebootstrap 0.5.8+b1
> ii coreutils 8.13-3
> ii debconf [debconf-2.0] 1.5.41
> ii debianutils4.1
> ii debootstrap1.0.38
> ii wget 1.13.4-1
>
> Versions of packages pbuilder recommends:
> ii devscripts 2.11.2
> ii fakeroot1.18.2-1
> ii sudo1.8.3p1-2
>
> Versions of packages pbuilder suggests:
> pn cowdancer 0.66
> pn gdebi-core
> pn pbuilder-uml
>
> -- debconf information excluded
> [2 0001-Add-ADDITIONAL_BUILDRESULT-variable.patch (7bit)>]
> >From ff5de7c5ca47f92d47ed755348702f173484c513 Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?Guido=20G=C3=BCnther?=
> Date: Mon, 19 Dec 2011 13:31:59 +0100
> Subject: [PATCH] Add ADDITIONAL_BUILDRESULT variable
>
> this can be used to copy additional build results out of the build
> directory. This is useful to e.g. preserve a xml testresult file when
> using a build system like Jenkins.
> ---
> pbuilder-buildpackage |6 ++
> pdebuild |6 ++
> 2 files changed, 12 insertions(+), 0 deletions(-)
>
> diff --git a/pbuilder-buildpackage b/pbuilder-buildpackage
> index b711934..580bb66 100755
> --- a/pbuilder-buildpackage
> +++ b/pbuilder-buildpackage
> @@ -171,6 +171,12 @@ if [ -d "${BUILDRESULT}" ]; then
> cp -p ${FILE} "${BUILDRESULT}" || true
> fi
> done
> +if [ -n "${ADDITIONAL_BUILDRESULT}" ]; then
> + echo "Saving additional results ${ADDITIONAL_BUILDRESULT}"
> + for FILE in ${ADDITIONAL_BUILDRESULT}; do
> + cp -a "${BUILDPLACE}/tmp/buildd/*/${FILE}" "${BUILDRESULT}"
> + done
> +fi
> else
> log "E: BUILDRESULT=[$BUILDRESULT] is not a directory."
> fi
> diff --git a/pdebuild b/pdebuild
> index 2bfe858..149f8ab 100644
> --- a/pdebuild
> +++ b/pdebuild
> @@ -50,6 +50,12 @@ if [ "${USE_PDEBUILD_INTERNAL}" = 'yes' ]; then
> conditional_cp_a ../"$files" "${BUILDRESULT}"
> done
> conditional_cp_a ../${CHANGES} "${BUILDRESULT}"
> + if [ -n "${ADDITIONAL_BUILDRESULT}" ]; then
> + echo "Saving additional results ${ADDITIONAL_BUILDRESULT}"
> + for FILE in ${ADDITIONAL_BUILDRESULT}; do
> + conditional_cp_a "${FILE}" "${BUILDRESULT}"
> +done
> + fi
> else
> log "E: BUILDRESULT=[$BUILDRESULT] is not a directory."
> exit 1
> --
> 1.7.7.3
>
> [3 ]
> ___
> Pbuilder-maint mailing list
> pbuilder-ma...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pbuilder-maint
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#647345: cowdancer: warning: 'mode_t' is promoted to 'int' when passed through '...'
Hi, I was wondering in the sense that 'does it not break existing platforms and fixes freebsd' and 'is this the only change that freebsd needs?' From your explanation, this still sounds like a very hacky and not very good approach to fix the problem at hand though. At Tue, 29 Nov 2011 06:36:43 -0600, Jonathan Nieder wrote: > > Junichi Uekawa wrote: > > > Does this actually help? I kind of doubt it. > > If "help" means "make the code any saner for humans reading", then no. > In principle if not in practice, mode_t could be wider than an int > (so it would end up being promoted to something wider than an int). > > If it means "ensure the code compiles and works correctly on amd64 and > kfreebsd-amd64 (not a very wide range of platforms to try, I admit)", > then yes. > > *checks* It seems that glibc uses va_arg(..., int) for this purpose, > too. So I think it should work on all platforms Debian supports. > > Hope that clarifies a little, > Jonathan > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#422272: fails to copy dsc with built-internal and buildresult=..
Hi,
It's not obvious where PARENT_DIR is defined, is this correct?
At Tue, 1 Nov 2011 15:55:25 -0700,
Tom Hughes (Palm GBU) wrote:
>
> From 9cf8a0cb800b734e2e3a4e67a14cf78442378144 Mon Sep 17 00:00:00 2001
> From: Tom Hughes
> Date: Tue, 1 Nov 2011 15:50:41 -0700
> Subject: [PATCH] Avoid dsc copy error when using build-internal and
> buildresult=.. (closes: #422272)
>
> ---
> pdebuild |9 +++--
> 1 files changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/pdebuild b/pdebuild
> index 28dff21..1b1c132 100644
> --- a/pdebuild
> +++ b/pdebuild
> @@ -46,10 +46,15 @@ export BUILDRESULTGID=$(id -g)
> if [ "${USE_PDEBUILD_INTERNAL}" = 'yes' ]; then
> ${PBUILDERROOTCMD} ${PDEBUILD_PBUILDER} --execute
> ${EXTRA_CONFIGFILE[@]/#/--configfile } --bindmounts $(readlink -f ..) "$@" --
> /usr/lib/pbuilder/pdebuild-internal ${PWD} --debbuildopts "" --debbuildopts
> "${DEBBUILDOPTS}" --uid "${BUILDRESULTUID}" --gid "${BUILDRESULTGID}"
> --pbuildersatisfydepends "$PBUILDERSATISFYDEPENDSCMD"
> if [ -d "${BUILDRESULT}" ]; then
> +echo "parent dir: ${PARENT_DIR}"
> for files in $(sed -rn '/^Files:/,${s/^ .* ([^ ]+)$/\1/p}'
> ../${CHANGES}); do
> - cp -a ../"$files" "${BUILDRESULT}"
> +if [ "${PARENT_DIR}" != "${BUILDRESULT}" ]; then
> + cp -a ../"$files" "${BUILDRESULT}"
> +fi
> done
> - cp -a ../${CHANGES} "${BUILDRESULT}"
> +if [ "${PARENT_DIR}" != "${BUILDRESULT}" ]; then
> + cp -a ../${CHANGES} "${BUILDRESULT}"
> +fi
> else
> log "E: BUILDRESULT=[$BUILDRESULT] is not a directory."
> exit 1
> --
> 1.7.7.1
>
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#569917: Support base.tar.xz/bz2 as well as tgz
Hi,
Heh, thanks for the patch.
I don't know how really it makes things fast, but it probably doesn't hurt.
I assume --use-compress-program has been available for tar since forever?
At Tue, 22 Nov 2011 19:30:55 +0100,
Tino Keitel wrote:
>
> diff -ru pbuilder-0.203/debian/changelog pbuilder-0.204~/debian/changelog
> --- pbuilder-0.203/debian/changelog 2011-09-22 04:31:08.0 +0200
> +++ pbuilder-0.204~/debian/changelog 2011-11-22 13:22:59.198920940 +0100
> @@ -1,3 +1,9 @@
> +pbuilder (0.204~) unstable; urgency=low
> +
> + * add --compressprog option
> +
> + -- Tino Keitel Mon, 21 Nov 2011 21:10:11 +0100
> +
> pbuilder (0.203) unstable; urgency=low
>
>* lighttpd test fails with cowdancer loaded. (closes: #640684)
> diff -ru pbuilder-0.203/pbuilder-checkparams
> pbuilder-0.204~/pbuilder-checkparams
> --- pbuilder-0.203/pbuilder-checkparams 2010-01-03 03:38:09.0
> +0100
> +++ pbuilder-0.204~/pbuilder-checkparams 2011-11-22 14:02:22.892153288
> +0100
> @@ -105,6 +105,12 @@
> fi
> shift; shift;
> ;;
> + --compressprog)
> + if [ -n "$2" ]; then
> + COMPRESSPROG="$2"
> + fi
> + shift; shift;
> + ;;
> --aptcache)
> if [ -n "$2" ]; then
> if [ -d "$2" ]; then
> diff -ru pbuilder-0.203/pbuilder-modules pbuilder-0.204~/pbuilder-modules
> --- pbuilder-0.203/pbuilder-modules 2011-06-25 01:06:40.0 +0200
> +++ pbuilder-0.204~/pbuilder-modules 2011-11-22 10:12:11.429410023 +0100
> @@ -75,6 +75,7 @@
> --debug
> --twice
> --autocleanaptcache
> + --compressprog [program]
> --debootstrapopts [debootstrap options]
> --save-after-login/--save-after-exec
> --debootstrap [debootstrap|cdebootstrap]
> @@ -434,7 +435,7 @@
> log "E: failed to find $BASETGZ, have you done to
> create your base tarball yet?"
> exit 1
> fi
> - if ! (cd "$BUILDPLACE" && tar xfzp "$BASETGZ"); then
> + if ! (cd "$BUILDPLACE" && tar -x --use-compress-program "$COMPRESSPROG"
> -p -f "$BASETGZ"); then
> log "E: failed to extract $BASETGZ to $BUILDPLACE"
> exit 1
> fi
> @@ -508,7 +509,7 @@
> sleep 10s
> done
> log "I: creating base tarball [${BASETGZ}]"
> - if ! tar cfz "${BASETGZ}.tmp" * ; then
> + if ! tar -c --use-compress-program "$COMPRESSPROG" -f "${BASETGZ}.tmp"
> * ; then
> log "E: failed building base tarball"
> rm -f "${BASETGZ}.tmp"
> exit 1;
> diff -ru pbuilder-0.203/pbuilder.8 pbuilder-0.204~/pbuilder.8
> --- pbuilder-0.203/pbuilder.8 2010-01-31 04:52:57.0 +0100
> +++ pbuilder-0.204~/pbuilder.82011-11-22 10:27:24.246037691 +0100
> @@ -502,6 +502,15 @@
> .B "pbuilder."
>
> .TP
> +.BI "\-\-compressprog"
> +Program to use for compression and decompression of the base.tgz.
> +The default is to use gzip, and any program that can be used for
> +the --use-compress-program option of tar can be given.
> +
> +If set to "pigz", compression and decompression is gzip compatible
> +but will use all available CPUs.
> +
> +.TP
> .BI "\-\-twice"
> Build the package twice in a row. Useful to ensure the package cleans up
> properly. The resulting packages are the ones from the second build.
> diff -ru pbuilder-0.203/pbuilderrc pbuilder-0.204~/pbuilderrc
> --- pbuilder-0.203/pbuilderrc 2010-07-05 15:06:08.0 +0200
> +++ pbuilder-0.204~/pbuilderrc2011-11-22 10:02:44.436100912 +0100
> @@ -99,3 +99,6 @@
>
> # default AUTOCLEANAPTCACHE
> AUTOCLEANAPTCACHE=""
> +
> +#default COMPRESSPROG
> +COMPRESSPROG="gzip"
> diff -ru pbuilder-0.203/pbuilderrc.5 pbuilder-0.204~/pbuilderrc.5
> --- pbuilder-0.203/pbuilderrc.5 2011-06-25 01:06:40.0 +0200
> +++ pbuilder-0.204~/pbuilderrc.5 2011-11-22 10:27:09.436038322 +0100
> @@ -153,6 +153,14 @@
> .B "pbuilder update"
> option.
> .TP
> +.BI "COMPRESSPROG=" "gzip"
> +Program to use for compression and decompression of the base.tgz.
> +The default is to use gzip, and any program that can be used for
> +the --use-compress-program option of tar can be given.
> +
> +If set to "pigz", compression and decompression is gzip compatible
> +but will use all available CPUs.
> +.TP
> .BI "export http_proxy=" "http://your-proxy:8080/";
> Defines the proxy for http connection.
> .TP
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#648662: cowbuilder --login ignores --distribution and doesn't pass it to pbuilder
Hi,
I think
1. the patch is broken because it's missing all punctuation marks and spaces;
2. what the patch is trying to do is already in Git tree that I don't quite
understand what you want to do.
At Sun, 13 Nov 2011 20:02:44 +,
Nicolas Bonnefon wrote:
>
> diff -ru cowdancer-0.65/cowbuilder.c cowdancer-0.65.new//cowbuilder.c
> --- cowdancer-0.65/cowbuilder.c2011-07-29 14:01:39.0 +0100
> +++ cowdancer-0.65.new//cowbuilder.c2011-11-13 19:16:54.356924971 +
> @@ -447,6 +447,16 @@
>pbuildercommandline[1]=login;
>PBUILDER_ADD_PARAM(--buildplace);
>PBUILDER_ADD_PARAM(pc->buildplace);
> + if (find_matching_param(--override-config))
> +{
> + if (pc->mirror)
> +{
> + PBUILDER_ADD_PARAM(--mirror);
> + PBUILDER_ADD_PARAM(pc->mirror);
> +}
> + PBUILDER_ADD_PARAM(--distribution);
> + PBUILDER_ADD_PARAM(pc->distribution);
> +}
>PBUILDER_ADD_PARAM(--no-targz);
>PBUILDER_ADD_PARAM(--internal-chrootexec);
>PBUILDER_ADD_PARAM(buf_chroot);
>
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#647345: cowdancer: warning: 'mode_t' is promoted to 'int' when passed through '...'
Hi,
Does this actually help? I kind of doubt it.
At Tue, 1 Nov 2011 20:30:40 -0500,
Jonathan Nieder wrote:
>
> Source: cowdancer
> Version: 0.65
> Tags: patch
>
> Hi,
>
> Trying to build cowdancer on kfreebsd-amd64, I get:
>
> cowdancer.c: In function 'open64':
> cowdancer.c:447:10: warning: 'mode_t' is promoted to 'int' when passed
> through '...' [enabled by default]
> cowdancer.c:447:10: note: (so you should pass 'int' not 'mode_t' to
> 'va_arg')
> cowdancer.c:447:10: note: if this code is reached, the program will
> abort
>
> Later, when running the test suite, some programs do abort, though I
> think that's for another reason. :)
>
> Unfortunately, POSIX does not tell us anything about the width of
> mode_t --- it just says that it is an integer type and historical
> BSD- and Sys-V-derived systems used "unsigned short". glibc on
> linux-amd64 uses uint32_t.
>
> $(getconf POSIX_V7_WIDTH_RESTRICTED_ENVS) is a list of programming
> environments (i.e., sets of build flags) in which certain types,
> including mode_t, are no wider than a "long". There must be at least
> one such environment, but not all environments have to be that way.
>
> Anyway, in practice (by which I mean "on the two systems I tried") it
> seems safe enough to assume it's promoted to "int". How about this
> patch?
> ---
> cowdancer.c |4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git i/cowdancer.c w/cowdancer.c
> index 6285ec46..cf347291 100644
> --- i/cowdancer.c
> +++ w/cowdancer.c
> @@ -411,7 +411,7 @@ int open(const char * a, int flags, ...)
>mode_t mode;
>va_list args;
>va_start(args, flags);
> - mode = va_arg(args, mode_t);
> + mode = va_arg(args, int);
>va_end(args);
>if (initialize_functions())
> {
> @@ -444,7 +444,7 @@ int open64(const char * a, int flags, ...)
>mode_t mode;
>va_list args;
>va_start(args, flags);
> - mode = va_arg(args, mode_t);
> + mode = va_arg(args, int);
>va_end(args);
>if (initialize_functions())
> {
> --
>
>
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#648438: cowdancer: FTBFS with ld that defaults to --as-needed: bad link order
Hi, Thanks for the patch. At Fri, 11 Nov 2011 15:05:32 +, Colin Watson wrote: > > Package: cowdancer > Version: 0.65 > Severity: important > Tags: patch > User: ubuntu-de...@lists.ubuntu.com > Usertags: origin-ubuntu ubuntu-patch oneiric > > cowdancer fails to build with a linker that defaults to --as-needed, as > shown in this Ubuntu build log: > > > https://launchpadlibrarian.net/83906438/buildlog_ubuntu-precise-i386.cowdancer_0.65_FAILEDTOBUILD.txt.gz > > This is because of incorrect link ordering: it puts libraries before the > objects that use them rather than after. See: > > http://wiki.debian.org/ToolChain/DSOLinking#Only_link_with_needed_libraries > > The following patch fixes this. > > * Fix link order to list libraries after the objects that require them. > * Use -pthread rather than -lpthread, since it should be a superset, it's > what's recommended in pthread_create(3), and it isn't so sensitive to > link order. Wow, the link order feels a bit backwards. Are you sure this isn't reversed? > > diff -Nru cowdancer-0.65/Makefile cowdancer-0.65ubuntu1/Makefile > --- cowdancer-0.65/Makefile 2009-11-29 10:26:13.0 + > +++ cowdancer-0.65ubuntu1/Makefile2011-11-11 14:32:37.0 + > @@ -37,7 +37,7 @@ > $(INSTALL_FILE) bash_completion.cowbuilder > $(DESTDIR)/etc/bash_completion.d/cowbuilder > > libcowdancer.so: cowdancer.lo ilistcreate.lo > - $(CC) $(CFLAGS) -ldl -shared -o $@ $^ > + $(CC) $(CFLAGS) -shared -o $@ $^ -ldl > > cow-shell: cow-shell.o ilistcreate.o > $(CC) $(CFLAGS) -o $@ $^ > diff -Nru cowdancer-0.65/tests/015_test_ilistdelete.c > cowdancer-0.65ubuntu1/tests/015_test_ilistdelete.c > --- cowdancer-0.65/tests/015_test_ilistdelete.c 2009-06-24 > 15:47:46.0 +0100 > +++ cowdancer-0.65ubuntu1/tests/015_test_ilistdelete.c2011-11-11 > 14:48:57.0 + > @@ -1,4 +1,4 @@ > -/*BINFMTC: -lpthread > +/*BINFMTC: -pthread > * > * Check deleting .ilist file is handled gracefully. > * > > Thanks, > > -- > Colin Watson [cjwat...@ubuntu.com] > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#527407: ecasound2.2 package
Hi, I've noticed that there's this bug that's pending; but I think there's nothing I can really do about it: the package is no longer relevant in sid. The bug logs are quite a bit confusing, but maybe I should file a request to remove the source package ecasound2.2 ? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#597104: qemubuilder: directory for BUILDRESULT is not created if not existent
Hi, I think we should error out, because the default permissions for BUILDRESULT isn't obvious. (for pbuilder case) and I have a feeling that we should mirror that for qemubuilder. At Thu, 16 Sep 2010 18:49:01 +0200, Johannes Schauer wrote: > > Package: qemubuilder > Version: 0.62 > Severity: normal > > the directory for BUILDPLACE is created if it doesnt exist. > > if the BUILDRESULT directory doesnt exist it is not created and > not even an error is thrown when qemubuilder tries to copy the > debs there. > > if not existent, BUILDRESULT should be created. > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
