Bug#671500: 2.0.5 is in fact 2.0.4...
On 2012-05-04 Andreas Metzler wrote:
[...]
> is not optimal, however this is a minor bug, not a serious one. Find a
> trivial patch below.
> ---
> --- swig2.0-2.0.5.orig/debian/control 2011-09-20 22:28:49.0 +0200
> +++ swig2.0-2.0.5/debian/control2012-05-04 19:20:37.0 +0200
> @@ -24,7 +24,7 @@ Build-Depends: bison,
> Package: swig
> Architecture: any
> -Depends: swig2.0 (>= 2.0.0-1), ${misc:Depends}
> +Depends: swig2.0 (= ${source:Version}), ${misc:Depends}
Grr, what was I thinking. This should read >=${source:Version},
otherwise it is uninstallable after a binNMU.
cu andreas
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671550: nodejs: building on kfreebsd-* (WIP)
On 05/05/2012 01:21, Steven Chamberlain wrote: > Package: src:nodejs > Version: 0.6.16~dfsg1-2 > Severity: wishlist > User: debian-...@lists.debian.org > Usertags: kfreebsd > X-Debbugs-Cc: debian-...@lists.debian.org > > Hi, > > Attached are *unfinished* patches for building nodejs on kfreebsd-* > > 3000_kfreebsd-1.diff is bad, as it patches something meant for FreeBSD > 3010_kfreebsd-2.diff just adds GNU/kFreeBSD as a freebsd-like target > 3020_kfreebsd-3.diff patches code so that it can build on GNU/kFreeBSD > > They are published here so that they can be finished someday or someone > can use them to use nodejs in the meantime. > > There are some test failures to note: > * test-fs-watch -- ENOSYS = not supported? > * test-fs-utimes -- not supported? (was building on ZFS) > * test-http-upgrade-server -- looks like some sort of chunking issue, > works if I change the HTTP request to HTTP/1.0 > * test-setproctitle -- currently a no-op in GNU/kFreeBSD's eglibc > > Regards, Thank you. I have no idea why it would fail, but once we have a build log and this set of patches we can contact upstream about it. They seem to have interest in supporting more platforms. nodejs will try to build on kfreebsd soon, since this arch is going to be added soon to libv8. Jérémy. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671340: ipxe: include undionly.kkpxe
On 05/03/2012 03:53 PM, Michael Tokarev wrote: 03.05.2012 14:03, Kasatkin Nikolay wrote: Package: ipxe Version: 1.0.0+git-20120202.f6840ba-3 Severity: wishlist Dear Maintainer, please consider including undionly.kkpxe in ipxe package. We use undionly.kpxe for netbooting computer classes in our university. But there are mainboards that can boot only with undionly.kkpxe, because of buggy BIOS. So for now we compile ipxe manually to boot those computers over the net via iPXE. If undionly.kkpxe will be included in ipxe package we will boot our classes without compiling iPXE manually. How useful this undionly.kkpxe thing is, generally? The thing is: ipxe has really a TON of various options and configuration variations, packaging all these isn't practical. So we decided to package only one, the most universal variant. For other usages, recompiling from source is the best way to go, since you as a user know best which configuration do you need, exactly. It is not like ipxe is changing 10 times a day, so frequent recompile/reinstall isn't necessary: you compile it only when you hit some limitation or bug, in your version. It is not like ipxe is the place where most recent features are always requireed, either. So I'd say keep it the way the package currently is, and compile site-specific versions as needed, locally. And mark this bugreport as wontfix. Unless ther's a very good reason why this undionly.kkpxe can be useful for a much wider userbase. Also, when including other options, I'd say they should be made available using some configuration mechanism (such as debconf), to be included in a bootloader configuration -- like ipxe.lknl currently handled. Thanks, /mjt Hello! In practice the difference between undionly.kpxe and undionly.kkpxe is in support of older network cards. In our environment 90% motherboards can be booted with undionly.kpxe, and other 10% can be booted only with undionly.kkpxe. This is regular cheap desktop computers with consumer motherboards with embedded network cards. So I suppose in environments with mixed cheap and old hardware (like universities and schools) this thing would be useful. -- Nikolay Kasatkin http://rain.ifmo.ru/~kasatkin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671227: ncurses-term: glitches in bterm
[ Adding Samuel to CC. ]
On 2012-05-03 12:27 +0200, Thomas Dickey wrote:
> On Wed, May 02, 2012 at 05:13:07PM +0200, Sven Joachim wrote:
>> Package: ncurses-term
>> Version: 5.9-7
>> Severity: normal
>>
>> On 2012-05-01 12:12 +0200, Samuel Thibault wrote:
>>
>> > There is however apparently a discrepancy between the
>> > bogl-provided bterm and the ncurses-provided bterm (I assumed that they
>> > were the same, but they are not), resulting in quite a few glitches e.g.
>> > in mutt. The ncurses one is probably outdated, we will have to fix that.
>
> It would be nice to have details (or a screenshot).
Indeed. Since I don't actually use bterm or mutt myself, this has to be
provided by Samuel, though.
>> Running infocmp shows the following differences (bterm-bogl being the
>> file from bogl 0.1.18-6, bterm-ncurses the file from ncurses-term
>> 5.9-7):
>>
>> ,
>> | comparing bterm-bogl to bterm-ncurses.
>> | comparing booleans.
>> | comparing numbers.
>> | comparing strings.
>> |acsc: '``aaffggiijjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~',
>> 'aajjkkllmmqqttuuxx'.
>> |op: NULL, '\E49;39m'.
>> |sgr: '\E[0m%?%p1%t\E[7m%;%?%p2%t\E[4m%;', NULL.
>> `
>>
>> There are comments in ncurses' misc/terminfo.src regarding the
>> differences in acsc and sgr:
>>
>> ,
>> | # Notes:
>> | # bterm only supports acs using wide-characters, has case for these:
>> qjxamlkut
>> | # bterm does not support sgr, since it only processes one parameter -TD
>> `
>
> right (I read the source-code using the Debian package as a reference,
> and that's accurate enough barring updates past my review at the end of 2009).
Cheers,
Sven
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671534: Use case?
Russ, Although in general I am all for standardization, I am not actually clear about the use case here. The typical case to which you refer is a browser-like client talking to a webserver-like server using certificates checkable with external authorities. In the MySQL case both client and server must be using MySQL code at some level and the certificates are likely to be managed by an authority internal to the oganization. Do these two cases really have very much in common? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#655689: Announce of an upcoming upload for the cwidget package
Quoting Sven Joachim (svenj...@gmx.de): > Well, translating that Yes/No widget is really the point of the > translation, since other cwidget messages are hardly ever seen by any > user. Yes, and the main use of them is aptitude. I'm not aware of other software using these widgets but that makes at least one good argument to have the widgets translated in at least all languages which aptitude is translated into. Indeed, David, the translations for Yes/No (and maybe even others) could be picked from newt, that has about the same widgets signature.asc Description: Digital signature
Bug#671596: ulatencyd change kernel.sched_autogroup_enabled to 0
Package: ulatencyd
Version: 0.5.0-5
Severity: normal
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
sudo /etc/init.d/ulatencyd restart
* What was the outcome of this action?
sysctl kernel.sched_autogroup_enabled will change to 0
* What outcome did you expect instead?
sysctl kernel.sched_autogroup_enabled will not change.
when i restart ulatencyd(/etc/init.d/ulatencyd restart),
sysctl kernel.sched_autogroup_enabled will change to 0.
*** End of the template - remove these lines ***
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.3.4-core2-amd64 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages ulatencyd depends on:
ii dbus 1.5.12-1
ii dpkg 1.16.3
ii libc6 2.13-32
ii libdbus-1-31.5.12-1
ii libdbus-glib-1-2 0.98-1
ii libglib2.0-0 2.32.2-1
ii liblua5.1-05.1.5-1
ii libpolkit-gobject-1-0 0.105-1
ii libxau61:1.0.7-1
ii libxcb11.8.1-1
ii lua-posix 5.1.19-1
ii lua5.1 [lua] 5.1.5-1
ulatencyd recommends no packages.
ulatencyd suggests no packages.
-- Configuration Files:
/etc/ulatencyd/cgroups.conf changed:
-- this is a lua file
CGROUP_ROOT = "/sys/fs/cgroup"
-- /sys/fs/cgroup is not available on older kernels, we need to change that
-- in those cases
fp = io.open(CGROUP_ROOT, "r")
if not fp then
CGROUP_ROOT = "/dev/cgroup"
else
fp:close()
end
-- edit the below only when you know what you are doing
-- describes which subsystems are mounted under
-- which toplevel path
CGROUP_MOUNTPOINTS = {
cpu={"cpu"},
-- please have a look at README.Debian to see why the memory resource
-- controller was disabled, and how to re-enable it.
memory={"memory"},
blkio={"blkio"},
cpuset={"cpuset"}
}
-- FIXME we need some better solution for that :-/
-- cpuset, very powerfull, but can't create a group with unset cpus or mems
CGROUP_DEFAULT = {
cpu={["notify_on_release"] = "1",},
memory={["notify_on_release"] = "1",},
io={["notify_on_release"] = "1",},
cpuset={["notify_on_release"] = "1",},
}
/etc/ulatencyd/rules/gnome.lua changed:
--[[
Copyright 2010,2011 ulatencyd developers
This file is part of ulatencyd.
License: GNU General Public License 3 or later
]]--
GnomeUI = {
name = "GnomeUI",
re_basename =
"metacity|compiz|gnome-panel|gtk-window-decorator|nautilus|Thunar",
--re_basename = "metacity",
check = function(self, proc)
local flag = ulatency.new_flag("user.ui")
proc:add_flag(flag)
proc:set_oom_score(-300)
rv = ulatency.filter_rv(ulatency.FILTER_STOP)
return rv
end
}
GnomeCore = {
name = "GnomeCore",
re_basename = "x-session-manager",
-- adjust the oom score adjust so x server will more likely survive
check = function(self, proc)
proc:set_oom_score(-300)
return ulatency.filter_rv(ulatency.FILTER_STOP)
end
}
-- gnome does a very bad job in setting grpid's, causing the complete
-- desktop to be run under one group. we fix this problem here, ugly
-- but working
-- filter that instantly sets a fake group on newly spawned processes from
-- gnome-panel or x-session-manager
GnomeFix = RunnerFix.new("GnomeFix", {"gnome-panel", "x-session-manager",
"gnome-session"})
-- on start we have to fix all processes that have descented from kde
local function cleanup_gnome_mess()
cleanup_desktop_mess({"x-session-manager", "gnome-session", "gnome-panel"})
return false
end
ulatency.add_timeout(cleanup_gnome_mess, 1000)
ulatency.register_filter(GnomeCore)
ulatency.register_filter(GnomeUI)
ulatency.register_filter(GnomeFix)
/etc/ulatencyd/scheduler/20-desktop.lua changed:
--[[
Copyright 2010,2011 ulatencyd developers
This file is part of ulatencyd.
License: GNU General Public License 3 or later
]]--
SCHEDULER_MAPPING_DESKTOP = {
info = {
description = "a good default desktop configuration"
}
}
-- cpu & memory configuration
SCHEDULER_MAPPING_DESKTOP["cpu"] =
{
{
name = "rt_tasks",
cgroups_name = "rt_tasks",
param = { ["cpu.shares"]="3048", ["?cpu.rt_runtime_us"] = "949500" },
check = function(proc)
local rv = proc.received_rt or check_label({"sched.rt"}, proc) or
proc.vm_size == 0
return rv
end,
},
{
name = "system_essential",
cgroups_name = "sys_essential",
param = { ["cpu.shares"]="3048" },
label = { "system.essential" }
},
{
name = "user",
cgroups_name = "usr_${euid}",
check = function(proc)
return ( proc.euid > 999 )
end,
param = { ["cpu.shares"]="3048", ["?cpu.r
Bug#671593: mockito: diff for NMU version 1.9.0+ds1-1.1
On 05/04/2012 10:33 PM, David Paleino wrote: > On Fri, 04 May 2012 20:50:25 -0700, tony mancill wrote: > >> Package: mockito >> Version: 1.9.0+ds1-1 >> Severity: normal >> Tags: patch pending >> >> Dear maintainer, >> >> I have sponsored an NMU prepared by Ludovic Claude for mockito >> (versioned as 1.9.0+ds1-1.1) and uploaded it to DELAYED/7. >> Please feel free to tell me if I should delay it longer or remove >> it from the upload queue. > > Please remove it. > > Since the changes are committed to the repository, I'll review them and make a > proper upload. > > Thanks, > David Okay - it has been removed. Ludovic stated that you agreed with the NMU; I guess there was some miscommunication. Thanks, tony signature.asc Description: OpenPGP digital signature
Bug#671523: [Pkg-samba-maint] Bug#671523: Winbind periodically looses the ability to make username lookups
Quoting Kevin Elliott (kevin_elli...@ci.juneau.ak.us): > Performing a 'wbinfo -i Kevin_Elliott' returns the message: "Could not get > info for user kevin_elliot". Maybe a level 10 log excerpt (just like the one you sent) at the moment winbind can no longer get the user info? Still, this bug will be better reported in upstream BTS. Also, are you in the position of trying to use the backported 3.6.5 packages from backports.debian.org? If the bug is reproducible with 3.6, then we have a good bug to report upstream. If it isn't, then I'm not sure that there a lot we can do (finding the right fix among umerous changes between 3.5.6 and 3.6.5 and backport it might be tricky or even impossible). signature.asc Description: Digital signature
Bug#671516: [Pkg-fonts-devel] Bug#671516: [fonts-bpg-georgian] The package does not contain fonts.
Quoting populus tremula (populus.trem...@yahoo.com): > Package: fonts-bpg-georgian > Version: 0.5a-2 > Severity: serious > > > > Package 'fonts-BPG-georgian' does not contain fonts. > It is an empty package, and the description says: > 'This package provides a collection of three Georgian fonts, > provided by BPG-InfoTech. '. > > > Fonts are in a package 'ttf-BPG-georgian-fonts'. > Which description says, 'transitional dummy package'. Ack. I'll look at this. Probably a mistake in the transition. Thanks for reporting. signature.asc Description: Digital signature
Bug#668233: libmockito-java: Intent to NMU: update use of maven-repo-helper
Hello Ludovic, On Tue, 10 Apr 2012 00:44:36 +0200, Ludovic Claude wrote: > [..] > The changes have been commited in the Git repository for mockito Next time, please do *atomic* commits. Committing large unrelated changes makes a VCS useless. Thanks. -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature
Bug#671593: mockito: diff for NMU version 1.9.0+ds1-1.1
On Fri, 04 May 2012 20:50:25 -0700, tony mancill wrote: > Package: mockito > Version: 1.9.0+ds1-1 > Severity: normal > Tags: patch pending > > Dear maintainer, > > I have sponsored an NMU prepared by Ludovic Claude for mockito > (versioned as 1.9.0+ds1-1.1) and uploaded it to DELAYED/7. > Please feel free to tell me if I should delay it longer or remove > it from the upload queue. Please remove it. Since the changes are committed to the repository, I'll review them and make a proper upload. Thanks, David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature
Bug#660574: xserver-xorg-video-dummy: missing symbol DUMMYDGAInit
Hi, maintainers, According to changelog.Debian.gz (0.3.5-2), you wanted to close this bug, but I found it not closed. Best regards, -- Ryo IGARASHI, Ph.D. rigar...@gmail.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#655689: Announce of an upcoming upload for the cwidget package
On 2012-05-05 02:44 +0200, David Prévot wrote: > Le 04/05/2012 13:27, David Prévot a écrit : >> Le 04/05/2012 12:22, Sven Joachim a écrit : >>> On 2012-05-04 01:02 +0200, David Prévot wrote: > >>> The upstream build system installs the message catalogs under the name >>> cwidget.mo, which is bad. Have you looked what it would take to install >>> them under a better name (say, libcwidget3.mo) in order to make room for >>> a later libcwidget4 package? > > The trivial following patch does the trick, but hardcodes libcwidget3 in > the upstream part of the source. Should I include this hack in the soon > to come NMU (once it will display this *$#!© translated [yes] [no] in > aptitude)? I'm not sure. Either way, DOMAIN will need to change if the soname is bumped. > I don't get what is wrong with the current cwidget.mo name, > would you care to elaborate, or give a pointer to the rationale of this > change? See Policy §8.2: If your package contains files whose names do not change with each change in the library shared object version, you must not put them in the shared library package. Otherwise, several versions of the shared library cannot be installed at the same time without filename clashes, making upgrades and transitions unnecessarily difficult. > --- cwidget-0.5.16/po/Makevars 2009-09-25 10:25:58.0 -0400 > +++ cwidget-0.5.16/po/Makevars 2012-05-04 19:02:29.0 -0400 > @@ -1,7 +1,7 @@ > # Makefile variables for PO directory in any package using GNU gettext. > > # Usually the message domain is the same as the package name. > -DOMAIN = $(PACKAGE) > +DOMAIN = libcwidget3 > > # These two variables depend on the location of this directory. > subdir = po The alternative to this hack would be to introduce a cwidget-l10n package with the translations, but I'm not sure how adequate this would be for an NMU. Cheers, Sven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671595: ITP: the-powder-toy -- A physics sandbox game similar to the classic, "Falling Sand"
Package: wnpp Severity: wishlist Owner: Aditya Vaidya * Package name: the-powder-toy Version : 77.0 Upstream Author : HardWIRED and respective owners * URL : http://powdertoy.co.uk/ * License : GPL Programming Lang: C Description : Physics sandbox game The Powder Toy is a desktop version of the classic 'falling sand' physics sandbox game. It simulates air pressure and velocity as well as heat! -- Sincerely, kroq-gar78 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#666889: Problem with this transition, leading to gnome-shell segfault on login
On 05.05.2012 06:59, Josh Triplett wrote: >> I see three different solutions, which all suck in their own way: >> a/ Make gir1.2-coglpango-1.0, gir1.2-cogl-1.0 and libcogl-pango0 break >> libcogl5 > > This seems like the best choice of the three you mentioned. Anything > using any of those and linking against libcogl5 will break, and "Breaks: > libcogl5" seems like the best available proxy for "Breaks: everything > depending on libcogl5 and this package". Just tested it. Looks like downgrading libcogl-pango0 is sufficient to avoid the gnome-shell crash. Seems it doesn't matter if the typelib files in gir1.2-coglpango-1.0 and gir1.2-cogl-1.0 are linked against libcogl9. I'm not quite sure why that is. This probably would need further investigation and more time. > The more optimal but more difficult alternative: figure out all packages > currently depending on libcogl5 and previous versions of the GNOME > introspection bits, and declare a versioned breaks against all of them. As we have packages in experimental, like empathy, which have a higher version number but still link against libcogl5, this is not working that great either. >> b/ Make libcogl9 break libcogl5 > > I don't think this one makes sense; those two libraries work fine on the > same system as long as nothing loads both of them. > >> c/ Make libcogl9 break libclutter-1.0-0 << 1.10 > > I don't think this one makes sense either, though it comes closer. Well, libclutter-1.0-0-1.10 has a breaks against libcogl5 and basically all packages using libcogl also use libclutter. So this would ensure that all three libs (libcogl, libcogl-pango and libclutter) are upgraded in lockstep. It's still a bit early in the morning here, and I had no coffee yet, so I might be missing something and I'd appreciate further comments. That said, I'll probably just make libcogl-pango0 break libcogl5 as this seems to be sufficient and upload this in a few hours. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#666889: Problem with this transition, leading to gnome-shell segfault on login
On Sat, May 05, 2012 at 06:27:10AM +0200, Michael Biebl wrote: > On 05.05.2012 06:21, Michael Biebl wrote: > > Right, the problem is, that you've made a partial upgrade and > > gnome-shell hasn't been recompiled yet. > > As a result gnome-shell tries to load both libcogl9 (via > > libcogl-pango0_1.10.2-2 and gir1.2-cogl*_1.10.2-2) and libcogl5, which > > results in the crash. > > FWIW, I've re-opened and marked #668285 as RC, so hopefully people with > apt-listchanges installed will notice. apt-listbugs you mean? > Sorry for the fuck-up. Happens; hazards of running unstable. Just glad I could catch it quickly, hopefully before too many more users hit it. :) - Josh Triplett -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#666889: Problem with this transition, leading to gnome-shell segfault on login
On Sat, May 05, 2012 at 06:21:29AM +0200, Michael Biebl wrote: > On 05.05.2012 06:04, Josh Triplett wrote: > > Something seems to have gone wrong with this transition. I currently > > have a set of packages installed that satisfy all dependency/conflict > > relationships, but that causes gnome-shell to segfault on start: > > > > > [HOLD, DEPENDENCIES] gir1.2-clutter-1.0:amd64 > > [HOLD, DEPENDENCIES] libclutter-1.0-0:amd64 > > [HOLD, DEPENDENCIES] libclutter-gtk-1.0-0:amd64 > > [HOLD, DEPENDENCIES] libmutter0:amd64 > > [HOLD, DEPENDENCIES] mutter-common:amd64 > > [INSTALL, DEPENDENCIES] libcogl9:amd64 > > > [UPGRADE] libcogl-pango0:amd64 1.8.2-1 -> 1.10.2-2 > > > [UPGRADE] gir1.2-cogl-1.0:amd64 1.8.2-1 -> 1.10.2-2 > > [UPGRADE] gir1.2-coglpango-1.0:amd64 1.8.2-1 -> 1.10.2-2 > > [UPGRADE] gir1.2-gtkclutter-1.0:amd64 1.0.4-1 -> 1.2.0-2 > > > > Note that I didn't upgrade the clutter packages because it Breaks: > > libcogl5, and umpteen other packages depend on libcogl5. Thus, I expect > > that many other people may end up with the same set of installed > > packages, and have their session completely fail to start. > > Right, the problem is, that you've made a partial upgrade and > gnome-shell hasn't been recompiled yet. > As a result gnome-shell tries to load both libcogl9 (via > libcogl-pango0_1.10.2-2 and gir1.2-cogl*_1.10.2-2) and libcogl5, which > results in the crash. Makes sense. > I see three different solutions, which all suck in their own way: > a/ Make gir1.2-coglpango-1.0, gir1.2-cogl-1.0 and libcogl-pango0 break > libcogl5 This seems like the best choice of the three you mentioned. Anything using any of those and linking against libcogl5 will break, and "Breaks: libcogl5" seems like the best available proxy for "Breaks: everything depending on libcogl5 and this package". The more optimal but more difficult alternative: figure out all packages currently depending on libcogl5 and previous versions of the GNOME introspection bits, and declare a versioned breaks against all of them. > b/ Make libcogl9 break libcogl5 I don't think this one makes sense; those two libraries work fine on the same system as long as nothing loads both of them. > c/ Make libcogl9 break libclutter-1.0-0 << 1.10 I don't think this one makes sense either, though it comes closer. - Josh Triplett -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671594: Crashes if directory changes while showing file dialog
Package: libgtk-3-0 Version: 3.4.1-2 Severity: important When a Gtk+ file dialog is open and a file in the directory it shows is renamed, the application crashes: Gtk:ERROR:/build/buildd-gtk+3.0_3.4.1-2-i386-xTOFDg/gtk+3.0-3.4.1/./gtk/gtkfilesystemmodel.c:751:gtk_file_system_model_sort: assertion failed: (r == n_visible_rows) Ben. -- System Information: Debian Release: wheezy/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libgtk-3-0:i386 depends on: ii libatk1.0-0 2.4.0-2 ii libc6 2.13-32 ii libcairo-gobject2 1.12.2-1 ii libcairo2 1.12.2-1 ii libcolord1 0.1.18-1 ii libcomerr2 1.42.2-2 ii libcups21.5.2-10 ii libfontconfig1 2.9.0-3 ii libfreetype62.4.9-1 ii libgcrypt11 1.5.0-3 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-02.32.2-1 ii libgnutls26 2.12.18-1 ii libgssapi-krb5-21.10+dfsg~beta1-2.1 ii libgtk-3-common 3.4.1-2 ii libk5crypto31.10+dfsg~beta1-2.1 ii libkrb5-3 1.10+dfsg~beta1-2.1 ii libpango1.0-0 1.30.0-1 ii libx11-62:1.4.99.901-2 ii libxcomposite1 1:0.4.3-2 ii libxcursor1 1:1.1.13-1 ii libxdamage1 1:1.1.3-2 ii libxext62:1.3.1-2 ii libxfixes3 1:5.0-4 ii libxi6 2:1.6.0-1 ii libxinerama12:1.1.2-1 ii libxrandr2 2:1.3.2-2 ii multiarch-support 2.13-32 ii shared-mime-info0.90-1 ii zlib1g 1:1.2.7.dfsg-1 Versions of packages libgtk-3-0:i386 recommends: ii hicolor-icon-theme 0.12-1 ii libgtk-3-bin3.4.1-2 Versions of packages libgtk-3-0:i386 suggests: ii gvfs 1.12.2-1 ii librsvg2-common 2.36.1-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#666889: Problem with this transition, leading to gnome-shell segfault on login
On 05.05.2012 06:21, Michael Biebl wrote: > Right, the problem is, that you've made a partial upgrade and > gnome-shell hasn't been recompiled yet. > As a result gnome-shell tries to load both libcogl9 (via > libcogl-pango0_1.10.2-2 and gir1.2-cogl*_1.10.2-2) and libcogl5, which > results in the crash. FWIW, I've re-opened and marked #668285 as RC, so hopefully people with apt-listchanges installed will notice. Sorry for the fuck-up. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#668365: gnome-shell: crashes on startup in cogl
Michael Biebl wrote: > It's a different bug > > You have made a partial upgrade of libcogl. Your version of gnome-shell > tries to load both libcogl9 (via libcogl-pango_1.10.2-2) and libcogl5. I downgraded to libcogl-pango_1.8.2-1 (testing), which was enough to work around it for now. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#666889: Problem with this transition, leading to gnome-shell segfault on login
On 05.05.2012 06:04, Josh Triplett wrote: > Something seems to have gone wrong with this transition. I currently > have a set of packages installed that satisfy all dependency/conflict > relationships, but that causes gnome-shell to segfault on start: > > [HOLD, DEPENDENCIES] gir1.2-clutter-1.0:amd64 > [HOLD, DEPENDENCIES] libclutter-1.0-0:amd64 > [HOLD, DEPENDENCIES] libclutter-gtk-1.0-0:amd64 > [HOLD, DEPENDENCIES] libmutter0:amd64 > [HOLD, DEPENDENCIES] mutter-common:amd64 > [INSTALL, DEPENDENCIES] libcogl9:amd64 > [UPGRADE] libcogl-pango0:amd64 1.8.2-1 -> 1.10.2-2 > [UPGRADE] gir1.2-cogl-1.0:amd64 1.8.2-1 -> 1.10.2-2 > [UPGRADE] gir1.2-coglpango-1.0:amd64 1.8.2-1 -> 1.10.2-2 > [UPGRADE] gir1.2-gtkclutter-1.0:amd64 1.0.4-1 -> 1.2.0-2 > > Note that I didn't upgrade the clutter packages because it Breaks: > libcogl5, and umpteen other packages depend on libcogl5. Thus, I expect > that many other people may end up with the same set of installed > packages, and have their session completely fail to start. Right, the problem is, that you've made a partial upgrade and gnome-shell hasn't been recompiled yet. As a result gnome-shell tries to load both libcogl9 (via libcogl-pango0_1.10.2-2 and gir1.2-cogl*_1.10.2-2) and libcogl5, which results in the crash. I see three different solutions, which all suck in their own way: a/ Make gir1.2-coglpango-1.0, gir1.2-cogl-1.0 and libcogl-pango0 break libcogl5 b/ Make libcogl9 break libcogl5 c/ Make libcogl9 break libclutter-1.0-0 << 1.10 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#671518: snd_hda_codec_hdmi OOPS on load when transparent_hugepage=always
Joshua Charles Campbell wrote: > Was unable to reproduce this on my laptop so it may be related to fglrx or > AMD > hardware in general. Thanks for checking. It would be useful to know which of the two: can you reproduce this without the fglrx driver on the machine with a radeon? If so, we can report this upstream and debug it with their help. If not, we can reassign the bug to fglrx-driver and presumably its maintainers would know the proper channels to pass it to AMD. Thanks, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#666889: Problem with this transition, leading to gnome-shell segfault on login
Something seems to have gone wrong with this transition. I currently have a set of packages installed that satisfy all dependency/conflict relationships, but that causes gnome-shell to segfault on start: May 4 20:46:37 leaf kernel: [ 201.565098] gnome-shell[2993]: segfault at 10 ip 7f9ea0b27111 sp 7fffeac60250 error 4 in libcogl.so.9.1.1[7f9ea0ad+87000] May 4 20:46:37 leaf gnome-session[2911]: WARNING: Application 'gnome-shell.desktop' killed by signal 11 May 4 20:46:38 leaf kernel: [ 202.804935] gnome-shell[3110]: segfault at 10 ip 7f9ec719c111 sp 7fff7bd187a0 error 4 in libcogl.so.9.1.1[7f9ec7145000+87000] May 4 20:46:38 leaf gnome-session[2911]: WARNING: App 'gnome-shell.desktop' respawning too quickly May 4 20:46:38 leaf gnome-session[2911]: WARNING: Application 'gnome-shell.desktop' killed by signal 11 This happened after I did the following upgrade: Will install 16 packages, and remove 0 packages. 568 kB of disk space will be used === [HOLD, DEPENDENCIES] anacron:amd64 [HOLD, DEPENDENCIES] cron:amd64 [HOLD, DEPENDENCIES] gir1.2-clutter-1.0:amd64 [HOLD, DEPENDENCIES] libclutter-1.0-0:amd64 [HOLD, DEPENDENCIES] libclutter-gtk-1.0-0:amd64 [HOLD, DEPENDENCIES] libmutter0:amd64 [HOLD, DEPENDENCIES] mutter-common:amd64 [INSTALL, DEPENDENCIES] libcogl9:amd64 [UPGRADE] gettext:amd64 0.18.1.1-6 -> 0.18.1.1-7 [UPGRADE] gettext-base:amd64 0.18.1.1-6 -> 0.18.1.1-7 [UPGRADE] gir1.2-cogl-1.0:amd64 1.8.2-1 -> 1.10.2-2 [UPGRADE] gir1.2-coglpango-1.0:amd64 1.8.2-1 -> 1.10.2-2 [UPGRADE] gir1.2-gtkclutter-1.0:amd64 1.0.4-1 -> 1.2.0-2 [UPGRADE] gir1.2-mutter-3.0:amd64 3.2.2-1 -> 3.2.2-3 [UPGRADE] libasprintf0c2:amd64 0.18.1.1-6 -> 0.18.1.1-7 [UPGRADE] libcogl-pango0:amd64 1.8.2-1 -> 1.10.2-2 [UPGRADE] libgettextpo0:amd64 0.18.1.1-6 -> 0.18.1.1-7 [UPGRADE] libpam-modules:amd64 1.1.3-7 -> 1.1.3-7.1 [UPGRADE] libpam-modules-bin:amd64 1.1.3-7 -> 1.1.3-7.1 [UPGRADE] libpam-runtime:amd64 1.1.3-7 -> 1.1.3-7.1 [UPGRADE] libpam0g:amd64 1.1.3-7 -> 1.1.3-7.1 [UPGRADE] libpam0g-dev:amd64 1.1.3-7 -> 1.1.3-7.1 [UPGRADE] w3m:amd64 0.5.3-5 -> 0.5.3-6 === Note that I didn't upgrade the clutter packages because it Breaks: libcogl5, and umpteen other packages depend on libcogl5. Thus, I expect that many other people may end up with the same set of installed packages, and have their session completely fail to start. - Josh Triplett -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671593: mockito: diff for NMU version 1.9.0+ds1-1.1
Package: mockito Version: 1.9.0+ds1-1 Severity: normal Tags: patch pending Dear maintainer, I have sponsored an NMU prepared by Ludovic Claude for mockito (versioned as 1.9.0+ds1-1.1) and uploaded it to DELAYED/7. Please feel free to tell me if I should delay it longer or remove it from the upload queue. Regards, tony diff -Nru mockito-1.9.0+ds1/debian/changelog mockito-1.9.0+ds1/debian/changelog --- mockito-1.9.0+ds1/debian/changelog 2012-03-19 15:53:49.0 -0700 +++ mockito-1.9.0+ds1/debian/changelog 2012-04-10 15:15:35.0 -0700 @@ -1,3 +1,16 @@ +mockito (1.9.0+ds1-1.1) unstable; urgency=low + + * Non-maintainer upload. + * d/control: update locations of Mockito in Vcs-Git and +Vcs-Browser + * d/control: add version contraint >= 1.7.1 to be able to +use jh_maven_repo_helper plugin + * d/rules: use jh_maven_repo_helper plugin and remove +override_dh_auto_install section. + * Update debian/pom.xml for mockito 1.9.0 + + -- Ludovic Claude Wed, 11 Apr 2012 00:11:24 +0200 + mockito (1.9.0+ds1-1) unstable; urgency=low * New upstream version diff -Nru mockito-1.9.0+ds1/debian/control mockito-1.9.0+ds1/debian/control --- mockito-1.9.0+ds1/debian/control2012-03-19 15:53:49.0 -0700 +++ mockito-1.9.0+ds1/debian/control2012-04-10 15:15:35.0 -0700 @@ -5,7 +5,7 @@ Build-Depends: debhelper (>= 7.0.50~) , javahelper (>= 0.20~) - , maven-repo-helper + , maven-repo-helper (>= 1.7.1) , openjdk-6-jdk , default-jdk Build-Depends-Indep: @@ -16,8 +16,8 @@ , libobjenesis-java Standards-Version: 3.9.3 Homepage: http://mockito.org -Vcs-Git: git://git.debian.org/git/collab-maint/mockito-core.git -Vcs-Browser: http://git.debian.org/?p=collab-maint/mockito-core.git +Vcs-Git: git://git.debian.org/git/collab-maint/mockito.git +Vcs-Browser: http://git.debian.org/?p=collab-maint/mockito.git Package: libmockito-java Architecture: all diff -Nru mockito-1.9.0+ds1/debian/libmockito-java.jlibs mockito-1.9.0+ds1/debian/libmockito-java.jlibs --- mockito-1.9.0+ds1/debian/libmockito-java.jlibs 1969-12-31 16:00:00.0 -0800 +++ mockito-1.9.0+ds1/debian/libmockito-java.jlibs 2012-04-10 15:15:35.0 -0700 @@ -0,0 +1 @@ +mockito-core.jar diff -Nru mockito-1.9.0+ds1/debian/libmockito-java.poms mockito-1.9.0+ds1/debian/libmockito-java.poms --- mockito-1.9.0+ds1/debian/libmockito-java.poms 2012-03-19 15:53:49.0 -0700 +++ mockito-1.9.0+ds1/debian/libmockito-java.poms 2012-04-10 15:15:35.0 -0700 @@ -1 +1,2 @@ -debian/pom.xml --no-parent +debian/pom.xml --no-parent --usj-name=mockito-core + diff -Nru mockito-1.9.0+ds1/debian/pom.xml mockito-1.9.0+ds1/debian/pom.xml --- mockito-1.9.0+ds1/debian/pom.xml2012-03-19 15:53:49.0 -0700 +++ mockito-1.9.0+ds1/debian/pom.xml2012-04-10 15:15:35.0 -0700 @@ -1,34 +1,40 @@ - -http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; -xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd "> -4.0.0 -org.mockito -mockito-core -1.8.5 -Mockito -http://www.mockito.org -Mock objects library for java - - -The MIT License -http://code.google.com/p/mockito/wiki/License -repo - - - -http://code.google.com/p/mockito/source/browse/ - - - -org.hamcrest -hamcrest-core -1.1 - - -org.objenesis -objenesis -1.0 - - - - + +http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; +xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd "> +4.0.0 +org.mockito +mockito-core +1.9.0 +Mockito +http://www.mockito.org +Mock objects library for java + + +The MIT License +http://code.google.com/p/mockito/wiki/License +repo + + + +http://code.google.com/p/mockito/source/browse/ + + + +szczepiq +Szczepan Faber + + + + +org.hamcrest +hamcrest-core +1.1 + + +org.objenesis +objenesis +1.0 + + + + diff -Nru mockito-1.9.0+ds1/debian/rules mockito-1.9.0+ds1/debian/rules --- mockito-1.9.0+ds1/debian/rules 2012-03-19 15:53:49.0 -0700 +++ mockito-1.9.0+ds1/debian/rules 2012-04-10 15:15:35.0 -0700 @@ -16,19 +16,14 @@ find javadoc/ -type f | xargs -r sed -i "s/org.mockito.cglib/net.sf.cglib/g" override_jh_build: - jh_build mockito-core-$(CURVER).jar org/ - -override_dh_auto_install: - dh_auto_install - mh_installpoms -plibmockito-java - mh_installjar -plibmockito-java -l debian/pom.xml
Bug#668365: gnome-shell: crashes on startup in cogl
On 05.05.2012 05:21, Jason White wrote: > Package: gnome-shell > Version: 3.2.2.1-4 > Followup-For: Bug #668365 > > I am seeing this after running dist-upgrade today (under Sid). > >>From /var/log/syslog: > May 5 13:10:40 jdc kernel: [16574.331243] gnome-shell[28802]: segfault at 10 > ip 7f54dfd0 sp 7f5a6030 error 4 in > libcogl.so.9.1.1[7f54dfcaa000+87000] > May 5 13:10:40 jdc x-session-manager[28749]: WARNING: Application > 'gnome-shell.desktop' killed by signal 11 > May 5 13:10:41 jdc kernel: [16575.697634] gnome-shell[28885]: segfault at 10 > ip 7f8240363111 sp 7fff3ce2cb90 error 4 in > libcogl.so.9.1.1[7f824030c000+87000] > May 5 13:10:41 jdc x-session-manager[28749]: WARNING: App > 'gnome-shell.desktop' respawning too quickly > May 5 13:10:42 jdc x-session-manager[28749]: WARNING: Application > 'gnome-shell.desktop' killed by signal 11 > May 5 13:10:49 jdc acpid: client 28687[0:0] has disconnected > > I don't know whether it's the same bug though. It's a different bug > Versions of packages gnome-shell depends on: > ii gir1.2-clutter-1.0 1.8.4-1 > ii gir1.2-cogl-1.0 1.10.2-2 > ii gir1.2-coglpango-1.0 1.10.2-2 > ii libclutter-1.0-0 1.8.4-1 > ii libcogl-pango0 1.10.2-2 > ii libcogl5 1.8.2-1 You have made a partial upgrade of libcogl. Your version of gnome-shell tries to load both libcogl9 (via libcogl-pango_1.10.2-2) and libcogl5. This is an intermediary problem until gnome-shell has been recompiled against the new clutter/cogl versions. Not quite sure, maybe we should add a Breaks: libcogl5 to libcogl-pango0_1.10.2-2 to avoid such a partial upgrade. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#671592: pdns-recursor: CNAME resolution fails
Package: pdns-recursor Version: 3.3-2+b1 Severity: important hi, i can get the exact same broken behaviour as this post demonstrates: http://mailman.powerdns.com/pipermail/pdns-users/2012-March/008647.html it's been fixed in SVN, so i suppose you could backport the fix from there to fix -recursor. thank you simon -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (991, 'unstable'), (990, 'testing'), (200, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/1 CPU core) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pdns-recursor depends on: ii adduser 3.113+nmu1 ii libc62.13-32 ii libgcc1 ii liblua5.1-0 5.1.5-1 ii libstdc++6 ii lsb-base 4.1+Debian2 Versions of packages pdns-recursor recommends: pn pdns-doc pdns-recursor suggests no packages. -- Configuration Files: /etc/logcheck/ignore.d.server/pdns-recursor [Errno 13] Permission denied: u'/etc/logcheck/ignore.d.server/pdns-recursor' /etc/powerdns/recursor.conf [Errno 13] Permission denied: u'/etc/powerdns/recursor.conf' -- 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#659814: dpkg-dev: substvars on Description doesn't behave as documented
On Mon, 2012-02-13 at 18:23:22 -0300, Nicolás Alvarez wrote:
> Package: dpkg-dev
> Version: 1.16.1.2
> Severity: normal
>
> The example on the deb-substvars(5) manpage shows a Description header
> with ${Description}, an empty line, and more text, and the resulting
> substituted control file shows that empty line too. However, it doesn't
> actually work that way. The empty line gets removed.
Indeed, and this is actually noted on the source code. The issue is
that first some modules need to be detangled to be able to fix this
properly, I've some code on a branch which is doing exactly this, so
in principle I'll be fixing this for 1.16.4.
thanks,
guillem
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671591: readahead-fedora: build-lists fails to identify crypt/raid/etc SSDs
Package: readahead-fedora Version: 2:1.5.6-4 Severity: normal /usr/share/readahead-fedora/build-lists does not identify special devices that are on physical SSDs. eg encrypted drives, raid disks, etc. For some such devices, eg encrypted drives, looking up the physical disk shouldn't be too hard, for others it may be harder... Though less common scenarios might not be worth implementing, the common ones like cryptsetup luks partitions should IMHO be handled properly. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (700, 'testing'), (600, 'testing'), (500, 'testing'), (400, 'unstable'), (300, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages readahead-fedora depends on: ii dpkg 1.16.1.2 ii e2fslibs 1.42.1-2 ii initscripts 2.88dsf-22 ii libaudit01:1.7.18-1.1 ii libblkid12.20.1-4 ii libc62.13-27 readahead-fedora recommends no packages. readahead-fedora suggests no packages. -- Configuration Files: /etc/default/readahead-fedora changed: READAHEAD="yes" READAHEAD_COLLECT="yes" READAHEAD_EXTRA_COLLECT="15" RUN_IN_BACKGROUND="yes" NICE_COLLECTOR=5 SORT_AT_SHUTDOWN="yes" -- 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#608934: Fix attached
I'd like to upload this to stable.diff -Nru python-defaults-2.6.6/debian/changelog python-defaults-2.6.6/debian/changelog --- python-defaults-2.6.6/debian/changelog 2011-02-18 16:49:31.0 -0500 +++ python-defaults-2.6.6/debian/changelog 2012-05-04 23:17:50.0 -0400 @@ -1,3 +1,11 @@ +python-defaults (2.6.6-3+squeeze7) stable; urgency=low + + * debian/python.postinst.in: Correctly remove +/var/lib/python/python2.6_already_installed instead of removing +/var/lib/python/python2.5_already_installed twice (closes: #608934) + + -- Scott Kitterman Fri, 04 May 2012 23:14:29 -0400 + python-defaults (2.6.6-3+squeeze6) stable; urgency=low * pycompile: use /usr/bin/pythonX.Y rather than pythonX.Y (to avoid diff -Nru python-defaults-2.6.6/debian/python.postinst.in python-defaults-2.6.6/debian/python.postinst.in --- python-defaults-2.6.6/debian/python.postinst.in 2010-07-11 11:39:14.0 -0400 +++ python-defaults-2.6.6/debian/python.postinst.in 2012-05-04 23:14:22.0 -0400 @@ -96,7 +96,7 @@ $hook rtinstall python2.6 "$oldversion" "$newversion" done fi - rm -f /var/lib/python/python2.5_already_installed + rm -f /var/lib/python/python2.6_already_installed rmdir --ignore-fail-on-non-empty /var/lib/python 2>/dev/null || true esac signature.asc Description: This is a digitally signed message part.
Bug#671590: readahead-fedora: readahead --build does not work if --maxsize is not used
Package: readahead-fedora Version: 2:1.5.6-4 Severity: important If --maxsize is not set, readahead.c:560 calls list_new without setting withsize. If we are not calling with --sort, filesizes never get read, thus every file is of size 0, and thus no files are written to output. This (should) make readahead break entirely on all systems with SSDs for boot drives (mine isnt properly identified, so expect another bug report when I track down the problems there...) Thanks, Matt -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (700, 'testing'), (600, 'testing'), (500, 'testing'), (400, 'unstable'), (300, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages readahead-fedora depends on: ii dpkg 1.16.1.2 ii e2fslibs 1.42.1-2 ii initscripts 2.88dsf-22 ii libaudit01:1.7.18-1.1 ii libblkid12.20.1-4 ii libc62.13-27 readahead-fedora recommends no packages. readahead-fedora suggests no packages. -- Configuration Files: /etc/default/readahead-fedora changed: READAHEAD="yes" READAHEAD_COLLECT="yes" READAHEAD_EXTRA_COLLECT="15" RUN_IN_BACKGROUND="yes" NICE_COLLECTOR=5 SORT_AT_SHUTDOWN="yes" -- 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#668365: gnome-shell: crashes on startup in cogl
Package: gnome-shell Version: 3.2.2.1-4 Followup-For: Bug #668365 I am seeing this after running dist-upgrade today (under Sid). >From /var/log/syslog: May 5 13:10:40 jdc kernel: [16574.331243] gnome-shell[28802]: segfault at 10 ip 7f54dfd0 sp 7f5a6030 error 4 in libcogl.so.9.1.1[7f54dfcaa000+87000] May 5 13:10:40 jdc x-session-manager[28749]: WARNING: Application 'gnome-shell.desktop' killed by signal 11 May 5 13:10:41 jdc kernel: [16575.697634] gnome-shell[28885]: segfault at 10 ip 7f8240363111 sp 7fff3ce2cb90 error 4 in libcogl.so.9.1.1[7f824030c000+87000] May 5 13:10:41 jdc x-session-manager[28749]: WARNING: App 'gnome-shell.desktop' respawning too quickly May 5 13:10:42 jdc x-session-manager[28749]: WARNING: Application 'gnome-shell.desktop' killed by signal 11 May 5 13:10:49 jdc acpid: client 28687[0:0] has disconnected I don't know whether it's the same bug though. If you need a gdb backtrace, a reference to instructions on how to get Gnome-shell running under gdb would be helpful. I'm currently running startx from a terminal to invoke an X session. With luck, lots of people who upgrade will be encountering this, making it easier to diagnose. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.12.1-1 ii gconf-service3.2.5-1 ii gir1.2-accountsservice-1.0 0.6.15-4 ii gir1.2-atk-1.0 2.4.0-2 ii gir1.2-caribou-1.0 0.4.2-2 ii gir1.2-clutter-1.0 1.8.4-1 ii gir1.2-cogl-1.0 1.10.2-2 ii gir1.2-coglpango-1.0 1.10.2-2 ii gir1.2-folks-0.6 0.6.8-2 ii gir1.2-freedesktop 1.32.1-1 ii gir1.2-gconf-2.0 3.2.5-1 ii gir1.2-gdkpixbuf-2.0 2.26.1-1 ii gir1.2-gee-1.0 0.6.4-1 ii gir1.2-gkbd-3.0 3.4.0.2-1 ii gir1.2-glib-2.0 1.32.1-1 ii gir1.2-gmenu-3.0 3.2.0.1-2 ii gir1.2-gnomebluetooth-1.03.2.2-1 ii gir1.2-gtk-3.0 3.4.1-2 ii gir1.2-json-1.0 0.14.2-1 ii gir1.2-mutter-3.03.2.2-3 ii gir1.2-networkmanager-1.00.9.4.0-3 ii gir1.2-pango-1.0 1.30.0-1 ii gir1.2-polkit-1.00.105-1 ii gir1.2-soup-2.4 2.38.1-2 ii gir1.2-telepathyglib-0.120.18.1-2 ii gir1.2-telepathylogger-0.2 0.4.0-1 ii gir1.2-upowerglib-1.00.9.16-2 ii gjs 1.32.0-2 ii gnome-bluetooth 3.2.2-1 ii gnome-icon-theme-symbolic3.4.0-2 ii gnome-settings-daemon3.2.2-3 ii gnome-shell-common 3.2.2.1-4 ii gsettings-desktop-schemas3.4.1-2 ii libatk1.0-0 2.4.0-2 ii libc62.13-32 ii libcairo-gobject21.12.2-1 ii libcairo21.12.2-1 ii libcamel-1.2-29 3.2.2-3 ii libcanberra0 0.28-4 ii libclutter-1.0-0 1.8.4-1 ii libcogl-pango0 1.10.2-2 ii libcogl5 1.8.2-1 ii libcroco30.6.5-1 ii libdbus-1-3 1.5.12-1 ii libdbus-glib-1-2 0.98-1 ii libdrm2 2.4.33-1 ii libebook-1.2-12 3.2.2-3 ii libecal-1.2-10 3.2.2-3 ii libedataserver-1.2-153.2.2-3 ii libedataserverui-3.0-1 3.2.2-3 ii libffi5 3.0.10-3 ii libfolks25 0.6.8-2 ii libfontconfig1 2.9.0-3 ii libfreetype6 2.4.9-1 ii libgconf-2-4 3.2.5-1 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libgee2 0.6.4-1 ii libgirepository-1.0-11.32.1-1 ii libgjs0b [libgjs0-libmozjs185-1.0] 1.32.0-2 ii libgl1-mesa-glx [
Bug#671589: bootlog does not work if the kernel boot command line is too long
Package: initscripts Version: 2.88dsf-13.1 Courtesy of Maciej Zenczykowski: sysvinit - kernel command lines can be longer than 256 characters. Fix a bug where a kernel commandline option of 'console=ttyS0,115200n8' was not being parsed correctly by bootlogd because it was 253 bytes into the string, and thus would get truncated by a 255-byte read into the 256 byte buffer. This results in bootlogd not seeing the console=ttyS0 kernel parameter, and it effectively turns off the serial console. --- /tmp/g4-4428/cache/modules/sysvinit/src/src/bootlogd.c#2 2011-04-11 15:10:58.0 -0700 +++ /tmp/g4-4428/29844861/modules/sysvinit/src/src/bootlogd.c 2012-05-04 19:40:37.0 -0700 @@ -244,7 +244,7 @@ unsigned intkdev; #endif struct stat st, st2; - charbuf[256]; + charbuf[4096]; char*p; int didmount = 0; int n, r; -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#608934: Already fixed in Wheezy
Not an issue for Unstable or Testing. signature.asc Description: This is a digitally signed message part.
Bug#670389: Needs to be against the interpreter packages
This has to be fixed in python3.1 and python3.2, so cloning and reassigning. signature.asc Description: This is a digitally signed message part.
Bug#671586: gjacktransport: FTBFS on hurd-i386.
Package: gjacktransport
Severity: important
Tags: patch
Dear Maintainer,
gjacktransport FTBFS on hurd-i386 because it uses PATH_MAX unconditionally. The
attached patch should fix this issue.
WBR,
Cyril Roelandt.
-- System Information:
Debian Release: wheezy/sid
APT prefers unreleased
APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: hurd-i386 (i686-AT386)
Kernel: GNU-Mach 1.3.99/Hurd-0.3
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
diff --git a/src/gjack.c b/src/gjack.c
index b7a9026..5915dee 100644
--- a/src/gjack.c
+++ b/src/gjack.c
@@ -16,27 +16,39 @@ extern GtkWidget *window1;
void dothejack (gboolean onoff);
void status_msg (char *msg) {
- gchar buf[PATH_MAX];
+ gchar *buf;
guint context = 1;
GtkWidget *statusbar1;
- statusbar1=lookup_widget(window1,"statusbar1");
+ size_t size;
- snprintf(buf, PATH_MAX, "%s", msg);
+ statusbar1=lookup_widget(window1,"statusbar1");
+ size = 1+strlen(msg);
+ buf = malloc(size);
+ if (buf == NULL)
+ return;
+
+ snprintf(buf, size, "%s", msg);
gtk_statusbar_pop(GTK_STATUSBAR(statusbar1), context);
gtk_statusbar_push(GTK_STATUSBAR(statusbar1), context, buf);
+ free(buf);
}
void status_printf (const char *format, ...) {
va_list arglist;
- char text[PATH_MAX];
+ char *text;
+ size_t text_size;
va_start(arglist, format);
- vsnprintf(text, PATH_MAX, format, arglist);
+ text_size = vsnprintf(NULL, 0, format, arglist);
+ text = malloc(text_size);
+ if (text == NULL)
+ return;
+ vsnprintf(text, text_size, format, arglist);
va_end(arglist);
- text[PATH_MAX -1] =0;
status_msg(text);
+ free(text);
}
/* end status bar */
diff --git a/src/resourceconfig.c b/src/resourceconfig.c
index f63e8f2..6e153d1 100644
--- a/src/resourceconfig.c
+++ b/src/resourceconfig.c
@@ -30,6 +30,10 @@
# define SYSCFGDIR "/etc"
#endif
+#ifdef __GNU__
+#include
+#endif
+
#include
#include
#include
@@ -116,6 +120,39 @@ void try_load_rc_file (char *filename) {
}
void load_rc (void) {
+#ifdef __GNU__
+ char *home;
+ char *filename;
+ size_t size, old_size;
+
+ size = strlen(SYSCFGDIR) + strlen(GJACKTRANSPORTRC) + 2;
+ filename = malloc(size);
+ assert(filename);
+ sprintf(filename, "%s/%s", SYSCFGDIR, GJACKTRANSPORTRC);
+ try_load_rc_file(filename);
+
+ home = getenv("HOME");
+ if (home) {
+ old_size = size;
+ size = strlen(home) + strlen(GJACKTRANSPORTRC) + 2;
+ if (old_size < size) {
+ filename = realloc(filename, size);
+ assert(filename);
+ }
+ sprintf(filename, "%s/.%s", home, GJACKTRANSPORTRC);
+ try_load_rc_file(filename);
+ }
+
+ old_size = size;
+ size = strlen(GJACKTRANSPORTRC) + 2;
+ if (old_size < size) {
+ filename = realloc(filename, size);
+ assert(filename);
+ }
+ sprintf(filename, "./%s", GJACKTRANSPORTRC);
+ try_load_rc_file(filename);
+ free(filename);
+#else
char *home;
char filename[PATH_MAX];
if ((strlen(SYSCFGDIR) + strlen(GJACKTRANSPORTRC) + 2) < PATH_MAX) {
@@ -131,6 +168,7 @@ void load_rc (void) {
sprintf(filename, "./%s", GJACKTRANSPORTRC);
try_load_rc_file(filename);
}
+#endif
}
/* vi:set ts=8 sts=2 sw=2: */
Bug#671585: edb: edb-debian-after-find-file
Package: edb Version: 1.31-2 Severity: normal File: /etc/emacs/site-start.d/50edb.el There seems to be a couple of doubtful bits in edb-debian-after-find-file setup by 50edb.el. I think the delq works by side-effect so the let-binding of find-file-hook won't preserve the value, and I think point might not always be at the start of the buffer if bookmarking packages have restored a previous position. I get some joy from the following, leaving the hook in permanently and binding the inhibit variable. Was that the intention anyway? I suppose it'd be even better if there was a db-mode which could act on an already-read buffer, instead of re-running the find-file. But perhaps that's difficult. (defun edb-debian-after-find-file () "Turn on EDB if first like is ';; Database file written by EDB'. This function is normally placed in `find-file-hooks'." (when (and (not edb-debian-inhibit-edb) ;; bookmarking etc might have moved point from start of buffer (save-excursion (goto-char (point-min)) (looking-at ";; Database file written by EDB"))) (let ((file (buffer-file-name))) ;; - We're already in the FILE, so kill buffer ;; and let db-* functions to load the file again ;; - BUT disable ourselves while db-* runs (kill-buffer (current-buffer)) (let ((edb-debian-inhibit-edb t)) (db-find-file file) -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-486 Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages edb depends on: ii dpkg 1.15.8.8 ii emacs22-gtk [emacs22] 22.3+1-1.2 ii emacs2323.4+1-3 ii install-info 4.13a.dfsg.1-8 ii make 3.81-8.1 edb recommends no packages. edb 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#471927: tracing functions
Just for the record, the piece of code that seems to keep looping
forever is in the file ./build-tree/gnu-interp.c, which is
automatically generated in the building process
[...]
if (bytesToShift == 0) {
return 30;
}
totalObjects = 0;
oop = memory + (foo->headerTypeBytes[(longAt(memory)) & TypeMask]);
while usqInt) oop)) < (((usqInt) foo->endOfMemory))) {
if (!(((longAt(oop)) & TypeMask) == HeaderTypeFree)) {
totalObjects += 1;
/* begin adjustFieldsAndClassOf:by: */
if (bytesToShift == 0) {
goto l1;
}
fieldAddr = oop + (lastPointerOf(oop)); // This is
gnu-interp.c:1826 !!!
while usqInt) fieldAddr)) > (((usqInt) oop))) {
fieldOop = longAt(fieldAddr);
if (!((fieldOop & 1))) {
longAtput(fieldAddr, fieldOop +
bytesToShift);
}
fieldAddr -= BYTES_PER_WORD;
}
if (((longAt(oop)) & TypeMask) != HeaderTypeShort) {
classHeader = longAt(oop - (BYTES_PER_WORD));
newClassOop = (classHeader &
(ALL_BUT_TYPE_MASK)) + bytesToShift;
longAtput(oop - (BYTES_PER_WORD), newClassOop |
(classHeader & TypeMask));
}
l1: /* end adjustFieldsAndClassOf:by: */;
}
[...]
Greetings,
Miry
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#670345: [Pkg-erlang-devel] Bug#670345: erlang-mode: help mode access to source code
Sergei Golovan writes: > > Are there any other packages that do this? I don't use Emacs > personally, but could use existing package as an example to fix this > bug. sml-mode or yatex. Or lua-mode is a single elisp file in the package, if that seems simpler. Others like gnuplot-mode or mpg123-el have a for-loop thingie for the ln linking, but I think *.el like sml-mode is fine. The idea started in emacs-goodies-el but that's a complicated package because some .el thee are excluded from emacs versions where they don't work, and autoloads are built per-flavour. -- The sigfile subcultures series: Cairns Goths Did you know Cairns has a thriving Goth scene? It takes real dedication to maintain a pasty complexion under the tropical sun and wear long black overcoats in 95% humidity. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671584: yasnippet: not pre-loaded for all users
Package: yasnippet Version: 0.6.1c-1 Severity: wishlist File: /etc/emacs/site-start.d/50yasnippet.el It'd be good if 50yasnippet.el didn't load and enable the whole yasnippet.el for all users on the system, but instead offered autoloads of whatever yas/global-mode or yas/minor-mode etc entrypoints which users wanting it or wanting to try it can run. Usually lisp startups should be fairly conservative about what they pre-load and pre-enable, since of course it'd be bad if every package loaded everything at startup. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-486 Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages yasnippet depends on: ii emacs21 [emacsen]21.4a+1-5.7 ii emacs22-gtk [emacsen]22.3+1-1.2 ii emacs23 [emacsen]23.4+1-3 ii xemacs21-mule [emacsen] 21.4.22-3.2 yasnippet recommends no packages. yasnippet 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#671583: proofgeneral: byte compile warnings not fatal to install
Package: proofgeneral Version: 4.2~pre120411-2 Severity: wishlist File: /usr/lib/emacsen-common/packages/install/proofgeneral It'd be good if byte compiler warnings were not setup to be fatal when installing, ie. don't set byte-compile-error-on-warn. It's very rare a byte compiler warning is anything which renders the whole package unusable. Almost always it's just a bit of slackness about variable declarations or whatnot which will run perfectly well. I think warnings can be left to the code author to review, no need to stop package installation. I struck this because I made and use a "bytecomp-simplify.el" which adds extra byte compiler warnings, which came up in some proofgeneral bits. Eg. ../coq/coq.el:2441:23:Warning: `(char-after (point))' can be simplified to `(char-after)' Of course that also raises the matter whether a byte compile should be done with "emacs -q -no-site-file" to keep out packaged add-ons like mine. -no-site-file has the benefit of not depending on what any other package might set-up, but on the other hand lisp depending on other lisp might want those setups ... -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-486 Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages proofgeneral depends on: ii emacs23 23.4+1-3 ii mmm-mode 0.4.8-6 proofgeneral recommends no packages. Versions of packages proofgeneral suggests: ii proofgeneral-doc 4.2~pre120206-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#671582: Please enable hardening build flags
Package: rtorrent Version: 0.8.9-2 Severity: normal Hardened build flags are a release goal for Wheezy. Because this program handles untrusted network data, it would be good if hardening was enabled during build. No need to act if it's already hardened. http://wiki.debian.org/ReleaseGoals/SecurityHardeningBuildFlags http://wiki.debian.org/Hardening -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671580: Please enable hardening build flags
Package: qbittorrent Version: 2.9.7-1 Severity: normal Hardened build flags are a release goal for Wheezy. Because this program handles untrusted network data, it would be good if hardening was enabled during build. No need to act if it's already hardened. http://wiki.debian.org/ReleaseGoals/SecurityHardeningBuildFlags http://wiki.debian.org/Hardening -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671503: general: APT repository format is not documented
On Vie 04 May 2012 18:13:01 Russ Allbery escribió: [big snip] I think Russ' proposal is quite a nice solution. Kinds regards, Lisandro. -- The volume of a pizza of thickness a and radius z can be described by the following formula: pi zz a Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#670491: ssh: Virtual servers
I suggest to run another sshd daemon *inside the chroot environment*. That will allow to allocate a pseudo-terminal correctly. Since the chrooted environment has no access to pts of the parent system (where you want to run sshd) - you will not able to run such apps as GNU Screen (for an example) inside the chrooted environment until you run sshd inside it (also you have to mount /proc and /dev/pts). Check it out. Also if there some security holes will be founded in the future then cracking of the child sshd will not cause obtaining the parent system control. Also you must note that if some user have root access in the chrooted envronment - then he can break it out and escape outside it. I suppose to use a modified linux kernel with grsecruity patches (http://grsecurity.net) - there is a lot of useful features include the chroot restrictions. On Thu, Apr 26, 2012 at 12:27 PM, Colin Watson wrote: > On Thu, Apr 26, 2012 at 08:46:35AM +0200, Ph. Marek wrote: > > I asked on openssh-unix-dev, and they said that there's a patch already > > available: > > > http://lists.mindrot.org/pipermail/openssh-unix-dev/2012-April/030399.html > > > > > > Please integrate that into the debian packages, thank you so much. > > This patch makes configuration changes; I won't add any more such > patches to the Debian package until they've actually been committed > upstream, not merely discussed on the upstream mailing list. Darren has > upstream commit access, so if he's confident in that patch he's entirely > capable of committing it. > > -- > Colin Watson [cjwat...@debian.org] > > > > -- > To UNSUBSCRIBE, email to debian-ssh-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > Archive: > http://lists.debian.org/20120426082739.ga7...@riva.dynamic.greenend.org.uk > >
Bug#671579: Please enable hardening build flags
Package: miro Version: 4.0.4-1 Severity: normal Hardened build flags are a release goal for Wheezy. Because this program handles untrusted network data, it would be good if hardening was enabled during build. No need to act if it's already hardened. http://wiki.debian.org/ReleaseGoals/SecurityHardeningBuildFlags http://wiki.debian.org/Hardening -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#655689: Announce of an upcoming upload for the cwidget package
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Sven, Le 04/05/2012 13:27, David Prévot a écrit : > Le 04/05/2012 12:22, Sven Joachim a écrit : >> On 2012-05-04 01:02 +0200, David Prévot wrote: >> The upstream build system installs the message catalogs under the name >> cwidget.mo, which is bad. Have you looked what it would take to install >> them under a better name (say, libcwidget3.mo) in order to make room for >> a later libcwidget4 package? The trivial following patch does the trick, but hardcodes libcwidget3 in the upstream part of the source. Should I include this hack in the soon to come NMU (once it will display this *$#!© translated [yes] [no] in aptitude)? I don't get what is wrong with the current cwidget.mo name, would you care to elaborate, or give a pointer to the rationale of this change? - --- cwidget-0.5.16/po/Makevars 2009-09-25 10:25:58.0 -0400 +++ cwidget-0.5.16/po/Makevars 2012-05-04 19:02:29.0 -0400 @@ -1,7 +1,7 @@ # Makefile variables for PO directory in any package using GNU gettext. # Usually the message domain is the same as the package name. - -DOMAIN = $(PACKAGE) +DOMAIN = libcwidget3 # These two variables depend on the location of this directory. subdir = po Regards David -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJPpHfhAAoJELgqIXr9/gny21sP/ReOqDiFgegYJq4G66Aw18RS jr2d2e9Ll8bxyadRc9d049R4ZLvahtSU2ketnzKbQ0Pk//5AVl5h31X+5bqy6EA9 oV5HjKXxOYvrNYg5QubixK5bhMi8al9nz8R8sM2hBgV5eTDNpVApY2sAaOZIVvsm 4+H3lfL741AAmMM439H38AoE7J3oUnAOAMzBGoFxiuHkNLHhrJLoLcsYFTyCCh7u utdvafQ0iVgndT6Q22/wrqk7IuISR/uqn7bGfzGWg2gEqcdfJbRl1pia3DBPyznr xYzR39lsIhbF+je9roOltkkOoDfj72DLvaEMLSNNT/h6sCoP/UGBEWM1puoOCGwG OfIsC8PIGjdy70FBBPIClxt0JetKVNRBG/4J4Zg8lVu4YlvK7xTSokh0DMTTICej yV8SIMVuyCgcBC2rcALYOBbPnsl5cwq+Eyk8gRH2qWDJhHwazJHzuAgr15LxhOf9 tcT/OB80mP95HQC6ucDKgz7lWua5OWQYovt3FAIJdsx0MQcwiEBRkhgWBtPGd52E vfX6QfOqBiMKWmWtrkvXvoaDr4MgPSNGL1Kl5mUVITaSEBunXIVuG4xYsTBMgMML t1QQjbXvhYDOQg0oLO5SDK+o1g5J2Rw/vT6PuAbNHkStOVkNDaq88h2j/W3xqtUu Kbd9VgiIuzn5KdlJwq27 =mn2R -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#671578: Please enable hardening build flags
Package: flush Version: 0.9.12-1 Severity: normal Hardened build flags are a release goal for Wheezy. Because this program handles untrusted network data, it would be good if hardening was enabled during build. No need to act if it's already hardened. http://wiki.debian.org/ReleaseGoals/SecurityHardeningBuildFlags http://wiki.debian.org/Hardening -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#648751: linux-image-3.0.0-1-rt-amd64: rcu_preempt_state whileshutdown
Hi Uwe, Sorry for the real late response. I installed the kernel you suggested in the same day but I forgot to give my feedback. It solved all my issues, so I think this bugreport should be closed as fixed. I'm currently running 3.2.0 and it's also well so far. Thanks for your help!
Bug#611136: closed by Michael Gilbert (Bug#611136: fixed in pam 1.1.3-7.1)
On Fri, May 04, 2012 at 04:21:08PM +, Debian Bug Tracking System wrote: > pam (1.1.3-7.1) unstable; urgency=low > . >* Non-maintainer upload. >* Fix cve-2011-4708: user-configurable .pam_environment allows > administrator-level changes without root access (closes: #611136). Typo: that should say CVE-2010-4708. - Josh Triplett -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671577: Please enable hardening build flags
Package: fatrat Version: 1.1.3-3 Severity: normal Hardened build flags are a release goal for Wheezy. Because this program handles untrusted network data, it would be good if hardening was enabled during build. No need to act if it's already hardened. http://wiki.debian.org/ReleaseGoals/SecurityHardeningBuildFlags http://wiki.debian.org/Hardening -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#634538: tcpreplay: FTBFS: configure: error: Unable to find matching library for header file in /usr
On Wed, Mar 14, 2012 at 06:44:39PM +0100, gregor herrmann wrote:
> On Tue, 19 Jul 2011 08:30:51 +0200, Lucas Nussbaum wrote:
> > Source: tcpreplay
> > Version: 3.4.3-2
> > Severity: serious
> > Tags: wheezy sid
> > User: debian...@lists.debian.org
> > Usertags: qa-ftbfs-20110718 qa-ftbfs
> > Justification: FTBFS on amd64
> >
> > During a rebuild of all packages in sid, your package failed to build on
> > amd64.
>
> Attached is a debdiff based on the Ubuntu patch that makes the
> package build.
>
> But:
>
> % lintian -F tcpreplay_3.4.3-2.1_amd64.changes
> E: tcpreplay: embedded-library usr/bin/tcpbridge: libpcap
> E: tcpreplay: embedded-library usr/bin/tcpprep: libpcap
> E: tcpreplay: embedded-library usr/bin/tcpreplay: libpcap
> E: tcpreplay: embedded-library usr/bin/tcpreplay-edit: libpcap
> E: tcpreplay: embedded-library usr/bin/tcprewrite: libpcap
Fixed and build tested (once updated for tcpreplay 3.4.4), with configure.ac
modification and call of --enable-dynamic-link
However, as a autoconf newbie, I didn't understood why I had to hardcode
libpcap.so instead of lipbcap${shrext_cmds}.
--
Simon Paillard
--- a/configure.ac
+++ b/configure.ac
@@ -354,6 +354,8 @@ for testdir in $trypcapdir /usr/local /opt/local /usr /wpdpack ; do
if test $dynamic_link = yes; then
if test -f "${testdir}/lib64/libpcap${shrext_cmds}" ; then
LPCAPLIB="-L${testdir}/lib64 -lpcap"
+elif test -f "${testdir}/lib/$multiarch/libpcap.so" ; then
+LPCAPLIB="-L${testdir}/lib/$multiarch -lpcap"
elif test -f "${testdir}/lib/libpcap${shrext_cmds}" ; then
LPCAPLIB="-L${testdir}/lib -lpcap"
else
--- a/debian/rules
+++ b/debian/rules
@@ -25,6 +25,7 @@ config.status: configure
./configure --host=$(DEB_HOST_GNU_TYPE) \
--build=$(DEB_BUILD_GNU_TYPE) \
--enable-debug \
+ --enable-dynamic-link \
--prefix=/usr \
--mandir=\$${prefix}/share/man \
--infodir=\$${prefix}/share/info
Bug#669427: apt segfaults on s390x
package apt forcemerge 669427 669243 severity 669427 serious tag 669427 + patch thanks On Wed, May 2, 2012 at 5:23 PM, David Kalnischkies wrote: > We are missing a bit of error checking here (callers of NewDescription() do > not check if return is != 0 and IsDuplicateDescription doesn't check if the > given Description is valid), but both shouldn't be a problem as NewDescription > can only really fail if new memory can't be allocated and as each version has > at least one description you shouldn't hit a problem in the dup check either. > Both wouldn't be limited to s390x either way: > We seem to have a similar bugreport from ppc64 (#669243), > if i understand right it's also bigendian 64bit, but no other report. Lesson learned today: If you know you have a bug in your code, don't put it on the todolist, just fix it! (or at least the parts which are trivial to fix) The assumption that each version has a description is correct for all but one version: In line 442ff we iterate over all packages with the same name and all versions for these packages to check if we already have a version with this description. The problem: We iterate also over the version we have added just a few lines above which has no description yet as we are in the process of (maybe) adding one for it. Result: The duplication check will use a dangling pointer to a string which should be a md5sum but properly is whatever it wants to be. On the pro side this usually has the intended effect as a random string properly doesn't fit the constraints for an md5sum (yet alone that it matches). Still, i am really fascinated that this worked for months here and everywhere else (expect s390x and ppc64). I would have expected a segfault at least once in a while as this is not done once or twice but for every version, so more like 100.000 times. Amazing. I am going to play in the lottery now, maybe this segfault prevention luck is transitive… (properly more like: I wasted all my luck on this one here) [Raising severity and therefore blocking transition as depending on dangling pointers isn't a great idea, even if it seems to work for all but not-yet release architectures… Upload next week or so] Thanks to both of you for debugging this and sorry for the inconvenience! Best regards David Kalnischkies apt-669427-dangling-description-duplication-check-segfaults.diff Description: Binary data
Bug#670913: Making it work again, but plotting not right
Hi Gaubitzer Erwin, On Mon, 30 Apr 2012 16:14:25 +0200, Gaubitzer Erwin wrote: > I found out that compilation of tm_r.c fails because of a missing util.h . > However by removing the line > #include > in tm_r.c leads to a working tm_r and copying it to Thanks for your report. I'll investigate the problem afterwards and sorry for late reply. Best regards, 2012-5-5(Sat) -- Debian Developer - much more I18N of Debian Atsuhito Kohda Department of Math., Univ. of Tokushima -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#657565: xorg-server: please switch to the standard FontPath setup
On Fri, 2012-05-04 at 21:03 +0200, Julien Cristau wrote: > My main worry is who would maintain that script? I don't expect it would need much maintenance, but if it has any issues, since I wrote it, I will take care of any needed fixes. You would just need to bounce me the bug since I'm not subscribed to xorg bugs. The alternative to the script would just be to ignore fonts not installed in the X11 dirs and let users create symlinks manually in the fontpath catalogue dirs. The consequence would be that apps that use server-side fonts could only use fonts from the standard builtin dirs under /usr/share/fonts/X11/ which has been the case since font packages are dropping defoma hints. -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#509335: flag to rsync raw device files
Package: rsync Version: 3.0.9-1 Followup-For: Bug #509335 I applied rw-devices patch (see http://goo.gl/1zvvg for more info about it) agains latest stable sources from v3.0.9 - you can find diff here: https://github.com/cub-uanic/rsync/commit/32ac2208be7722d2e565dbdeff1a3af81c4b58d3 (http://goo.gl/FyVTq) I can confirm that after patching it compiles and works fine (tested on adm64 platform only). I hope, this will speedup things a bit. Thanks! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671569: Please enable hardening build flags
Package: transmission-gtk Version: 2.51-1 Severity: normal Hardened build flags are a release goal for Wheezy. Because this program handles untrusted network data, it would be good if hardening was enabled during build. http://wiki.debian.org/ReleaseGoals/SecurityHardeningBuildFlags http://wiki.debian.org/Hardening -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#614907: Question of sincerity on the node/nodejs nausia
* Patrick Ouellette , 2012-05-04, 19:12: (I'm assuming Jonathan Nieder is some how acting with their knowledge or approval at some level) Why? I wouldn't assume so. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671565: Wheezy: Iceweasel no longer using busy cursor as per KDE cursor theme
Package: iceweasel Version: 10.0.3esr-3 Iceweasel is no longer using busy cursor as per KDE cursor theme. By busy cursor I mean the cursor that Iceweasel shows when it's waiting for the web server to transmit the data. It used to work in previous Iceweasel versions, as late as version 8, I believe, but not in version 9 or 10. Now Iceweasel shows *some* (default?) busy cursor but it's not a part of the KDE cursor theme. # aptitude show kdebase Package: kdebase State: installed Automatically installed: no Version: 5:66 Priority: optional -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671564: src:xtables-addons: Fails to build twice in a row
Package: src:xtables-addons Version: 1.42-1 Severity: important User: debian...@lists.debian.org Usertags: qa-doublebuild Hi! The xtables-addons package fails to build twice in a row. The clean target leaves lots of files behind leading to the following error: make[1]: Leaving directory `/tmp/xtables-addons-1.42' dh_autoreconf_clean dh_clean dpkg-source -b xtables-addons-1.42 dpkg-source: info: using source format `3.0 (quilt)' dpkg-source: info: building xtables-addons using existing ./xtables-addons_1.42.orig.tar.gz dpkg-source: warning: ignoring deletion of file Makefile.in dpkg-source: warning: ignoring deletion of file configure dpkg-source: warning: ignoring deletion of file aclocal.m4 dpkg-source: warning: ignoring deletion of file m4/ltoptions.m4 dpkg-source: warning: ignoring deletion of file m4/libtool.m4 dpkg-source: warning: ignoring deletion of file m4/ltversion.m4 dpkg-source: warning: ignoring deletion of file build-aux/config.guess dpkg-source: warning: ignoring deletion of file build-aux/missing dpkg-source: warning: ignoring deletion of file build-aux/ltmain.sh dpkg-source: warning: ignoring deletion of file build-aux/config.sub dpkg-source: warning: ignoring deletion of file build-aux/compile dpkg-source: warning: ignoring deletion of file build-aux/depcomp dpkg-source: warning: ignoring deletion of file build-aux/install-sh dpkg-source: warning: ignoring deletion of file extensions/Makefile.in dpkg-source: warning: ignoring deletion of file extensions/ACCOUNT/Makefile.in dpkg-source: warning: ignoring deletion of file extensions/pknock/Makefile.in dpkg-source: warning: ignoring deletion of file geoip/Makefile.in dpkg-source: info: local changes detected, the modified files are: xtables-addons-1.42/extensions/.libxt_CHAOS.oo.d xtables-addons-1.42/extensions/.libxt_DELUDE.oo.d xtables-addons-1.42/extensions/.libxt_DHCPMAC.oo.d xtables-addons-1.42/extensions/.libxt_DNETMAP.oo.d xtables-addons-1.42/extensions/.libxt_ECHO.oo.d xtables-addons-1.42/extensions/.libxt_IPMARK.oo.d xtables-addons-1.42/extensions/.libxt_LOGMARK.oo.d xtables-addons-1.42/extensions/.libxt_RAWDNAT.oo.d xtables-addons-1.42/extensions/.libxt_RAWSNAT.oo.d xtables-addons-1.42/extensions/.libxt_STEAL.oo.d xtables-addons-1.42/extensions/.libxt_SYSRQ.oo.d xtables-addons-1.42/extensions/.libxt_TARPIT.oo.d xtables-addons-1.42/extensions/.libxt_condition.oo.d xtables-addons-1.42/extensions/.libxt_dhcpmac.oo.d xtables-addons-1.42/extensions/.libxt_fuzzy.oo.d xtables-addons-1.42/extensions/.libxt_geoip.oo.d xtables-addons-1.42/extensions/.libxt_gradm.oo.d xtables-addons-1.42/extensions/.libxt_iface.oo.d xtables-addons-1.42/extensions/.libxt_ipp2p.oo.d xtables-addons-1.42/extensions/.libxt_ipv4options.oo.d xtables-addons-1.42/extensions/.libxt_length2.oo.d xtables-addons-1.42/extensions/.libxt_lscan.oo.d xtables-addons-1.42/extensions/.libxt_psd.oo.d xtables-addons-1.42/extensions/.libxt_quota2.oo.d xtables-addons-1.42/extensions/ACCOUNT/.libxt_ACCOUNT.oo.d xtables-addons-1.42/extensions/pknock/.libxt_pknock.oo.d dpkg-source: info: you can integrate the local changes with dpkg-source --commit dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/xtables-addons_1.42-1.diff.UQjc1V dpkg-buildpackage: error: dpkg-source -b xtables-addons-1.42 gave error exit status 2 cheers Stuart -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#666067: transition: libkpathsea6
Hi Adam and all, On Fri, 04 May 2012 23:21:53 +0100, "Adam D. Barratt" wrote: > After a few more removals and a small breakage (scalable-cyrfonts-tex) > the new texlive stack is now in testing. I missed aging a catdvi > upload, which is keeping libkpathsea5 in testing still, so I'm not > closing the bug yet. Hopefully that should be sorted in tomorrow > morning's run. Great! Thanks for your work. I'd like to know a bit more. If I understand correctly jbibtex-bin is (will be) removed, then I'd like to know what is the situation of jbibtex-base. jbibtex-base is completely included in texlive-lang-cjk as follows: $ diff -ur /usr/share/texmf/jbibtex/bst/ /usr/share/texlive/texmf-dist/pbibtex/bst/ $ diff -ur /usr/share/texmf/jbibtex/bib/ /usr/share/texlive/texmf-dist/pbibtex/bib/ It might cause no problem at present but I believe there is no need to keep jbibtex-base anymore. Next, I'd like to know about texfam. Is it correct to think it is in unstable and we have more time to try migrating it to kpathsea6 environment? Best regards, 2012-5-5(Sat) -- Debian Developer - much more I18N of Debian Atsuhito Kohda Department of Math., Univ. of Tokushima -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671558: tuareg-mode: auto-mode-alist regexp string end
Package: tuareg-mode
Version: 1:2.0.4-3
Severity: normal
File: /etc/emacs/site-start.d/51tuareg-mode.el
51tuareg-mode.el sets up
(add-to-list 'auto-mode-alist '("\\.ml\\w?" . tuareg-mode))
but I wonder if the regexp is meant to have a \\' anchor as per the
autoload cookie of /usr/share/emacs/site-lisp/tuareg-mode/tuareg.el
;;;###autoload (add-to-list 'auto-mode-alist '("\\.ml\\w?\\'" . tuareg-mode))
The string end would ensure for example foo.ml.html is opened in html
mode. Not that a name like that would be very likely, but it's just .ml
as a suffix which is intended is it?
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (990, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-486
Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Versions of packages tuareg-mode depends on:
ii emacs21 [emacsen]21.4a+1-5.7
ii emacs22-gtk [emacsen]22.3+1-1.2
ii emacs23 [emacsen]23.4+1-3
ii xemacs21-mule [emacsen] 21.4.22-3.2
Versions of packages tuareg-mode recommends:
ii ocaml-interp
ii ocaml-mode3.12.1-2
tuareg-mode 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#671548: python-qt4 4.9.1-2 broke hgview
I believe this will be fixed by the qscintilla2 binNMU I had done today. Please check if you still have this problem after updating it. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#669208: boinc-client: Upstart issues
Package: boinc-client Version: 7.0.24+dfsg-1 Followup-For: Bug #669208 Hello, I'm not familiar with Debian's policies and goals but I think the main problem is not the point at which boinc-client starts automatically but that this point is not configurable by the user. How about simply picking a sensible default automatically (like start BOINC after the graphics card is initialized if a GUI is installed and at a lower runlevel if not) and letting users configure their system otherwise if they want to? It's great if you're able to make the init script more clever but please keep it configurable! And please don't introduce regressions for people who have no graphics cards, no GUI or more generally who have systems which are different from yours. If you're saying that Upstart in its current form is designed to make it impossible for users to choose runlevels for their services... well that would a bug with Upstart in my opinion. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#614907: Question of sincerity on the node/nodejs nausia
Can anyone explain to me why the message I sent with a proposal containing a MAJOR concession to the Node.js maintainers has not received a response from the Node.js maintainers but rather caused them (I'm assuming Jonathan Nieder is some how acting with their knowledge or approval at some level) to run crying to the technical committee? The proposal gave them their way provided they were willing to do the heavy lifting everybody claims should be "so easy." I have received absolutely no comments, no counter offers, no "sure," no "we'll need some help, but ok" and not even "you're nuts." Reflecting on this has lead me to the following possible conclusions: 0. The Node.js maintainers were so shocked they have lost all cognitive abilities and are delirious with joy 1. The Node.js maintainers were never interested in a compromise solution of any kind 2. Node.js maintainers are not really interested in doing any work to solve the issue beyond changing their binary back to node What did I get from proposing a major concession to solve the issue? I got called a passive aggressive, stonewalling individual not interested in moving the issue forward. Thanks for the time and effort, sorry for the noise - Pat -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#598745: Bug#661283: cmor: FTBFS on kfreebsd-amd64
2012/5/5 Steven Chamberlain : > Upstream does it that way, but I'm not sure if GNU/kFreeBSD does (I see > no mention of ulimit in /etc?). But if so, it would explain why this > was reproducible on buildd's and not on the asdfasdf porter box. ulimit is just the user interface. This is set by PAM, see pam_limits(8) and setrlimit(2). > Raising DFLSIZ seems like the best way to me, as the buildd's will need > it, and some daemons like mysql or postgres seem to want a larger data > size anyway. I'm on your side. I had this discussion with upstream already :-) > Even with 'ulimit -d unlimited', kfreebsd-i386 is bounded by MAXDSIZ = > 512 MiB whereas cmor would need ~700ish. I suppose that and DFLDSIZ > could be raised to 1 GiB on kfreebsd-i386 to try to fix this, but no > higher as explained in: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598745#20 If it can be set to 1 GiB, why hasn't upstream done this? I think it wouldn't be a good idea to increase this limit in Debian unless upstream does. -- Robert Millan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671550: nodejs: building on kfreebsd-* (WIP)
Package: src:nodejs
Version: 0.6.16~dfsg1-2
Severity: wishlist
User: debian-...@lists.debian.org
Usertags: kfreebsd
X-Debbugs-Cc: debian-...@lists.debian.org
Hi,
Attached are *unfinished* patches for building nodejs on kfreebsd-*
3000_kfreebsd-1.diff is bad, as it patches something meant for FreeBSD
3010_kfreebsd-2.diff just adds GNU/kFreeBSD as a freebsd-like target
3020_kfreebsd-3.diff patches code so that it can build on GNU/kFreeBSD
They are published here so that they can be finished someday or someone
can use them to use nodejs in the meantime.
There are some test failures to note:
* test-fs-watch -- ENOSYS = not supported?
* test-fs-utimes -- not supported? (was building on ZFS)
* test-http-upgrade-server -- looks like some sort of chunking issue,
works if I change the HTTP request to HTTP/1.0
* test-setproctitle -- currently a no-op in GNU/kFreeBSD's eglibc
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--- nodejs-0.6.16~dfsg1.orig/deps/uv/src/unix/eio/eio.c
+++ nodejs-0.6.16~dfsg1/deps/uv/src/unix/eio/eio.c
@@ -316,7 +316,7 @@ static int gettimeofday(struct timeval *
#if HAVE_SENDFILE
# if __linux
# include
-# elif __FreeBSD__ || __DragonFly__ || defined __APPLE__
+# elif __FreeBSD__ || __FreeBSD_kernel__ || __DragonFly__ || defined __APPLE__
# include
# include
# elif __hpux
--- nodejs-0.6.16~dfsg1.orig/src/platform_freebsd.cc
+++ nodejs-0.6.16~dfsg1/src/platform_freebsd.cc
@@ -34,7 +34,11 @@
#include
#include
#include
+#if defined(__GLIBC__)
+#include
+#else
#include
+#endif
#include
--- nodejs-0.6.16~dfsg1.orig/tools/wafadmin/Tools/ccroot.py 2012-04-30 18:42:50.0 +0100
+++ nodejs-0.6.16~dfsg1/tools/wafadmin/Tools/ccroot.py 2012-05-04 23:50:08.767391792 +0100
@@ -66,6 +66,7 @@
'__linux__' : 'linux',
'__GNU__' : 'hurd',
'__FreeBSD__' : 'freebsd',
+ '__FreeBSD_kernel__' : 'freebsd',
'__NetBSD__' : 'netbsd',
'__OpenBSD__' : 'openbsd',
'__sun' : 'sunos',
--- nodejs-0.6.16~dfsg1.orig/deps/uv/config-unix.mk 2012-05-04 23:45:19.0 +0100
+++ nodejs-0.6.16~dfsg1/deps/uv/config-unix.mk 2012-05-04 23:50:10.817219567 +0100
@@ -72,6 +72,15 @@
OBJS += src/unix/kqueue.o
endif
+ifeq (GNU/kFreeBSD,$(uname_S))
+EV_CONFIG=config_freebsd.h
+EIO_CONFIG=config_freebsd.h
+CPPFLAGS += -Isrc/ares/config_freebsd
+LINKFLAGS+=
+OBJS += src/unix/freebsd.o
+OBJS += src/unix/kqueue.o
+endif
+
ifeq (DragonFly,$(uname_S))
EV_CONFIG=config_freebsd.h
EIO_CONFIG=config_freebsd.h
--- nodejs-0.6.16~dfsg1.orig/wscript 2012-05-04 23:45:19.0 +0100
+++ nodejs-0.6.16~dfsg1/wscript 2012-05-04 23:50:05.187249113 +0100
@@ -327,12 +327,12 @@
if Options.options.efence:
conf.check(lib='efence', libpath=['/usr/lib', '/usr/local/lib'], uselib_store='EFENCE')
- if 'bsd' in sys.platform:
- if not conf.check(lib="execinfo",
- includes=['/usr/include', '/usr/local/include'],
- libpath=['/usr/lib', '/usr/local/lib'],
- uselib_store="EXECINFO"):
- conf.fatal("Install the libexecinfo port from /usr/ports/devel/libexecinfo.")
+# if 'bsd' in sys.platform:
+# if not conf.check(lib="execinfo",
+# includes=['/usr/include', '/usr/local/include'],
+# libpath=['/usr/lib', '/usr/local/lib'],
+# uselib_store="EXECINFO"):
+# conf.fatal("Install the libexecinfo port from /usr/ports/devel/libexecinfo.")
if not Options.options.without_ssl:
# Don't override explicitly supplied openssl paths with pkg-config results.
Bug#671549: pyaimt: FTBFS if built twice in a row: aborting due to unexpected upstream changes
Source: pyaimt Version: 0.8.0.1-2 Severity: important User: debian...@lists.debian.org Usertags: qa-doublebuild pyaimt FTBFS if built twice in a row: | dpkg-source -b pyaimt-0.8.0.1 | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: building pyaimt using existing ./pyaimt_0.8.0.1.orig.tar.gz | dpkg-source: info: local changes detected, the modified files are: | pyaimt-0.8.0.1/pyaimt.conf.xml | dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/pyaimt_0.8.0.1-2.diff.n_Owqq | dpkg-source: info: you can integrate the local changes with dpkg-source --commit | dpkg-buildpackage: error: dpkg-source -b pyaimt-0.8.0.1 gave error exit status 2 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671128: galculator: Binary mode isn't really binary
Package: galculator Version: 1.3.4-1 Followup-For: Bug #671128 Dear Maintainer, I forwarded this bug upstream, cf. https://sourceforge.net/tracker/?func=detail&aid=3523627&group_id=80471&atid=559874 . -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-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 galculator depends on: ii libatk1.0-02.4.0-2 ii libc6 2.13-30 ii libcairo2 1.10.2-7 ii libglade2-01:2.6.4-1 ii libglib2.0-0 2.32.0-4 ii libgtk2.0-02.24.10-1 ii libpango1.0-0 1.29.4-3+b1 ii libxml22.7.8.dfsg-9 galculator recommends no packages. galculator 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#671127: galculator: Inconsistent behaviour of left and right shifts
Package: galculator Version: 1.3.4-1 Followup-For: Bug #671127 Dear Maintainer, I forwarded this bug upstream, cf. https://sourceforge.net/tracker/?func=detail&aid=3523625&group_id=80471&atid=559874 . -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-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 galculator depends on: ii libatk1.0-02.4.0-2 ii libc6 2.13-30 ii libcairo2 1.10.2-7 ii libglade2-01:2.6.4-1 ii libglib2.0-0 2.32.0-4 ii libgtk2.0-02.24.10-1 ii libpango1.0-0 1.29.4-3+b1 ii libxml22.7.8.dfsg-9 galculator recommends no packages. galculator 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#671408: Even in English
My updated icedove did something similar.
iU icedove 3.0.11-1+squeeze9 mail/news client with
RSS and integrated spam filter support
Many of my (all ASCII/English) folders now have "-1" appended to them. The
folder-subscription list now has a bunch of blank ("") folders with check
boxes.
Daniel
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671125: galculator: Difficulties entering shift operations
Package: galculator Version: 1.3.4-1 Followup-For: Bug #671125 Dear Maintainer, I forwarded this bug upstream, cf. https://sourceforge.net/tracker/?func=detail&aid=3523624&group_id=80471&atid=559874 . -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-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 galculator depends on: ii libatk1.0-02.4.0-2 ii libc6 2.13-30 ii libcairo2 1.10.2-7 ii libglade2-01:2.6.4-1 ii libglib2.0-0 2.32.0-4 ii libgtk2.0-02.24.10-1 ii libpango1.0-0 1.29.4-3+b1 ii libxml22.7.8.dfsg-9 galculator recommends no packages. galculator 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#671515: ioctl_list(2): table wider than line width
tag 671515 upstream thanks Hello Bjarni, On Fri, May 04, 2012 at 06:46:57PM +, Bjarni Ingi Gislason wrote: > Package: manpages-dev > Version: 3.27-1 > Severity: minor > Tags: patch Thanks. > Version 3.40 of "manpages" from upstream is used. As ioctl_list.2 is no patched in Debian, and as there is no 3.40 in Debian yet (in deferred upload), you can probably report such patch directly to upstream at linux-...@vger.kernel.org (though it happens upstream receives Debian bugs). > From "groff": > > ioctl_list.2: warning: around line 126: table wider than line width > ioctl_list.2: warning: around line 182: table wider than line width > ioctl_list.2: warning: around line 203: table wider than line width > ioctl_list.2: warning: around line 260: table wider than line width > ioctl_list.2: warning: around line 368: table wider than line width > ioctl_list.2: warning: around line 473: table wider than line width > ioctl_list.2: warning: around line 488: table wider than line width > ioctl_list.2: warning: around line 533: table wider than line width > > Long tables split into two or more. Some "l l l l." reduced > to "l l l.". There is a jump in some column alignments (empty > line between parts of the same table). > > Patch is in the attachment. -- Simon Paillard -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671123: galculator: Some expressions are not accepted in Formula Entry input mode
Package: galculator Version: 1.3.4-1 Followup-For: Bug #671123 Dear Maintainer, I forwarded this bug upstream, cf. https://sourceforge.net/tracker/?func=detail&aid=3523623&group_id=80471&atid=559874 . -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-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 galculator depends on: ii libatk1.0-02.4.0-2 ii libc6 2.13-30 ii libcairo2 1.10.2-7 ii libglade2-01:2.6.4-1 ii libglib2.0-0 2.32.0-4 ii libgtk2.0-02.24.10-1 ii libpango1.0-0 1.29.4-3+b1 ii libxml22.7.8.dfsg-9 galculator recommends no packages. galculator 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#663868: Blacklisting usblp helps
Please remove the blacklisting for usblp, run # modprobe usblp set CUPS into debug mode: # cupsctl LogLevel=debug and then turn off and turn on the printer again. Does it load its firmware? If not, attach your /var/log/cups/error_log file. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#663320: sqlheavy: planned vala 0.12 removal
Hi, sqlheavy version 0.1.1 has just been released [1], which properly builds against vala 0.16. Please update the Debian package accordingly. If you need a sponsor, please ask. sqlheavy is currently the only remaining package depending on vala 0.12. Cheers, Michael [1] http://code.google.com/p/sqlheavy/downloads/list -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#671518: Update
Was unable to reproduce this on my laptop so it may be related to fglrx or AMD hardware in general. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#633634: random hangups -- BUG: unable to handle kernel paging request at 00007fafb1245388
reassign 633634 linux-image-2.6.32-5-amd64 found 633634 2.6.32-34squeeze1 stop Hello Jan, kernel team, I happen to have stumbled upon this bug report, which was incorrectly assigned to the package "none". Jan: this one is not valid, you either have to assign to "general" (avoid if possible!) or else to some specific package that you think that it's causing the problem. So I am reassigning it to the package/version that is closer to the description and dates given. I verified that there's no bug submitted with similar title with this specific binary package, but that's as far as I got. (Please CC-me in the reply if you want to communicate with me, otherwise I won't receive any e-mail... but anyway, I don't think that I have much else to say). Regards. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671548: python-qt4 4.9.1-2 broke hgview
Package: python-qt4 Version: 4.9.1-2 Severity: important hgview worked fine with 4.9.1-1, but when I upgrade to 4.9.1-3, hgview fails with: $ hgview Traceback (most recent call last): File "/usr/bin/hgview", line 33, in main() File "/usr/lib/python2.7/dist-packages/hgviewlib/application.py", line 188, in main sys.exit(start(repo, opts, args, parser.error)) File "/usr/lib/python2.7/dist-packages/hgviewlib/application.py", line 135, in start app = Application(repo, opts, args) File "/usr/lib/python2.7/dist-packages/hgviewlib/qt4/application.py", line 48, in __init__ super(HgViewQtApplication, self).__init__(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/hgviewlib/application.py", line 78, in __init__ self.choose_viewer() File "/usr/lib/python2.7/dist-packages/hgviewlib/application.py", line 102, in choose_viewer viewer = self.HgRepoViewer(self.repo) File "/usr/lib/python2.7/dist-packages/hgviewlib/qt4/hgrepoviewer.py", line 58, in __init__ HgDialogMixin.__init__(self) File "/usr/lib/python2.7/dist-packages/hgviewlib/qt4/hgdialogmixin.py", line 69, in __init__ self.setupUi(self) File "/usr/lib/python2.7/dist-packages/hgviewlib/qt4/hgqv_ui.py", line 59, in setupUi self.textview_status = HgFileView(self.splitter) File "/usr/lib/python2.7/dist-packages/hgviewlib/qt4/hgfileview.py", line 119, in __init__ self.sci = qsci(self) TypeError: QsciScintilla(QWidget parent=None): argument 1 has unexpected type 'HgFileView' I'm creating the bug against python-qt4 because it was its update who broke it but feel free to reassign it. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/6 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-qt4 depends on: ii libc6 2.13-32 ii libgcc1 1:4.7.0-7 ii libpython2.7 2.7.3~rc2-2.1 ii libqt4-dbus 4:4.8.1-1 ii libqt4-declarative4:4.8.1-1 ii libqt4-designer 4:4.8.1-1 ii libqt4-help 4:4.8.1-1 ii libqt4-network4:4.8.1-1 ii libqt4-script 4:4.8.1-1 ii libqt4-scripttools4:4.8.1-1 ii libqt4-svg4:4.8.1-1 ii libqt4-test 4:4.8.1-1 ii libqt4-xml4:4.8.1-1 ii libqt4-xmlpatterns4:4.8.1-1 ii libqtassistantclient4 4.6.3-4 ii libqtcore44:4.8.1-1 ii libqtgui4 4:4.8.1-1 ii libqtwebkit4 2.2.1-2 ii libstdc++64.7.0-7 ii python2.7.2-10 ii python-sip [sip-api-8.1] 4.13.2-1 ii python2.6 2.6.7-4 ii python2.7 2.7.3~rc2-2.1 python-qt4 recommends no packages. Versions of packages python-qt4 suggests: pn python-qt4-dbg -- 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#663321: NMU: steadyflow: planned vala 0.12 removal
tags 663321 + patch pending
thanks
Hi,
I've prepared an NMU to make steadyflow compile against vala 0.14 and
uploaded it to DELAYED/10. Please let me know if you want me to delay it
further or cancel it.
Attached is the full debdiff.
The changelog reads:
steadyflow (0.1.7-2.1) unstable; urgency=low
* Non-maintainer upload.
* Build against vala 0.14. (Closes: #663321)
- Update debian/patches/vala_executable.patch to check for valac-0.14.
- Bump Build-Depends to valac-0.14.
- Add debian/patches/vala-0.14.patch to fix ActionEntry and Menu
ambiguity
errors with newer Vala versions.
-- Michael Biebl Sat, 05 May 2012 00:42:19 +0200
Cheers,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
diff -Nru steadyflow-0.1.7/debian/changelog steadyflow-0.1.7/debian/changelog
--- steadyflow-0.1.7/debian/changelog 2011-07-13 03:32:49.0 +0200
+++ steadyflow-0.1.7/debian/changelog 2012-05-05 00:44:47.0 +0200
@@ -1,3 +1,14 @@
+steadyflow (0.1.7-2.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Build against vala 0.14. (Closes: #663321)
+- Update debian/patches/vala_executable.patch to check for valac-0.14.
+- Bump Build-Depends to valac-0.14.
+- Add debian/patches/vala-0.14.patch to fix ActionEntry and Menu ambiguity
+ errors with newer Vala versions.
+
+ -- Michael Biebl Sat, 05 May 2012 00:42:19 +0200
+
steadyflow (0.1.7-2) unstable; urgency=low
* Remove libappindicator-dev | hello build-dependency; confuses Debian
diff -Nru steadyflow-0.1.7/debian/control steadyflow-0.1.7/debian/control
--- steadyflow-0.1.7/debian/control 2011-07-13 03:31:26.0 +0200
+++ steadyflow-0.1.7/debian/control 2012-05-05 00:41:18.0 +0200
@@ -4,7 +4,7 @@
Maintainer: Maia Kozheva
Build-Depends: debhelper (>= 7.0.50~),
cmake (>= 2.6),
- valac-0.12,
+ valac-0.14,
libgtk2.0-dev (>= 2.16),
libglib2.0-dev (>= 2.26),
libgee-dev,
diff -Nru steadyflow-0.1.7/debian/patches/series steadyflow-0.1.7/debian/patches/series
--- steadyflow-0.1.7/debian/patches/series 2011-07-10 19:42:49.0 +0200
+++ steadyflow-0.1.7/debian/patches/series 2012-05-05 00:42:08.0 +0200
@@ -1 +1,2 @@
vala_executable.patch
+vala-0.14.patch
diff -Nru steadyflow-0.1.7/debian/patches/vala-0.14.patch steadyflow-0.1.7/debian/patches/vala-0.14.patch
--- steadyflow-0.1.7/debian/patches/vala-0.14.patch 1970-01-01 01:00:00.0 +0100
+++ steadyflow-0.1.7/debian/patches/vala-0.14.patch 2012-05-05 00:37:54.0 +0200
@@ -0,0 +1,138 @@
+Index: steadyflow-0.1.7/Steadyflow/IndicatorController.vala
+===
+--- steadyflow-0.1.7.orig/Steadyflow/IndicatorController.vala 2011-05-22 11:29:17.0 +0200
steadyflow-0.1.7/Steadyflow/IndicatorController.vala 2012-05-05 00:36:26.59332 +0200
+@@ -57,11 +57,11 @@
+ stock_quit_label = item.label;
+ }
+
+- private ActionEntry[] actions = {
+- ActionEntry () { name = "Add", stock_id = "list-add", label = _("_Add download...") },
+- ActionEntry () { name = "Quit", stock_id = "system-shutdown", label = stock_quit_label },
+- ActionEntry () { name = "PauseAll", stock_id = "media-playback-pause", label = _("_Pause all") },
+- ActionEntry () { name = "ResumeAll", stock_id = "media-playback-start", label = _("_Resume all") }
++ private Gtk.ActionEntry[] actions = {
++ Gtk.ActionEntry () { name = "Add", stock_id = "list-add", label = _("_Add download...") },
++ Gtk.ActionEntry () { name = "Quit", stock_id = "system-shutdown", label = stock_quit_label },
++ Gtk.ActionEntry () { name = "PauseAll", stock_id = "media-playback-pause", label = _("_Pause all") },
++ Gtk.ActionEntry () { name = "ResumeAll", stock_id = "media-playback-start", label = _("_Resume all") }
+ };
+
+ private ToggleActionEntry[] toggle_actions = {
+@@ -69,7 +69,7 @@
+ };
+
+ private UIManager ui_manager;
+- private Menu menu;
++ private Gtk.Menu menu;
+ private ToggleAction show_hide_action;
+ private Gtk.Action pause_all_action;
+ private Gtk.Action resume_all_action;
+@@ -89,7 +89,7 @@
+ Util.fatal_error (e);
+ }
+
+- menu = (Menu) ui_manager.get_widget ("/ui/IndicatorMenu");
++ menu = (Gtk.Menu) ui_manager.get_widget ("/ui/IndicatorMenu");
+ Services.indicator.set_menu (menu);
+ Services.indicator.visible = Services.settings.get_boolean ("show-indicator");
+
+Index: steadyflow-0.1.7/Steadyflow.UI/TrayIndicatorService.vala
+===
+--- steadyflow-0.1.7.orig/Steadyflow.UI/TrayIndicatorService.vala 2011-05-22 11:29:17.0 +0200
steadyflow-0.1.7/Steadyflow.UI/TrayIndicatorService.vala 2012-05-05 00:37:50.518256351 +0200
+@@ -23,7 +23,7 @@
+
+ public class TrayIndicatorService : GLib.Object, IIndicatorService {
+ private StatusIcon status_icon;
+- private Menu menu;
++ private Gtk.Menu menu;
+
+ public TrayIndicator
Bug#671547: [INTL:pl] Polish debconf translation
Package: condor Severity: wishlist Tags: l10n patch Hi! Please add the attached Polish debconf translation. Thanks in advance, -- Michał Kułach pl.po Description: Binary data
Bug#671546: udev: loop device: add backing file in udev database
Package: udev
Version: 175-3.1
Severity: wishlist
Dear Maintainer,
Since kernel 2.6.37, some infos are available in /sys for associated loop
devices, especially the backing file.
I have written a rules file:
== /etc/udev/rules.d/60-loopback.rules =
SUBSYSTEM!="block", GOTO="loopback_end"
KERNEL=="loop?*", OPTIONS+="watch"
ACTION=="add|change", \
KERNEL=="loop?*", \
TEST=="%S/block/%k/loop/backing_file", \
PROGRAM=="/bin/cat %S/block/%k/loop/backing_file", \
ENV{BACKING_FILE}="%c"
LABEL="loopback_end"
Works fine
Is it possible to add a similar file in the udev package (but maybe this is a
task for 'util-linux') or to modify an
existing file (maybe 60-persistent-storage.rules) ?
Thanks
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'testing-proposed-updates')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-2-486
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 udev depends on:
ii debconf [debconf-2.0] 1.5.42
ii libc6 2.13-30
ii libselinux12.1.9-2
ii libudev0 175-3.1
ii lsb-base 4.1+Debian0
ii util-linux 2.20.1-4
Versions of packages udev recommends:
ii pciutils 1:3.1.9-2
ii usbutils 1:005-3
udev suggests no packages.
-- debconf information:
udev/new_kernel_needed: false
udev/title/upgrade:
udev/reboot_needed:
udev/sysfs_deprecated_incompatibility:
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671507: debian-policy: policy section 7.4 conflicts with section 10.1
Carsten Hey wrote: > * Patrick Ouellette [2012-05-04 13:38 -0400]: >> If you read the entire section 7.4 is seems entirely reasonable to >> create a package with an executable name that already exists in Debian >> with a package conflicts tag if the two executables have different >> functionality. > > But I want to play the boulder dash clone epiphany whilst browsing the > web using the epiphany browser! This misses the point. The goal of policy §10.1 is that other packages (in Debian and elsewhere) can rely on a command name having a single, reliable meaning, independent of the $PATH setting and installed package set. For example, it would be awfully strange if xdg-open or sensible-browser caused the boulder dash clone epiphany to open. If other packages use the "node" command to refer to Node.js, then the Conflicts or Breaks being prevented would be by node against all of those packages and by nodejs against packages that use "node" to refer to LinuxNode. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#598745: Bug#661283: cmor: FTBFS on kfreebsd-amd64
On 04/05/12 23:10, Robert Millan wrote: > Actually, I think that increasing DFLDSIZ might not be the only > solution. DFLDSIZ only sets the default limit, but for login shells > it is increased automatically. Upstream does it that way, but I'm not sure if GNU/kFreeBSD does (I see no mention of ulimit in /etc?). But if so, it would explain why this was reproducible on buildd's and not on the asdfasdf porter box. Raising DFLSIZ seems like the best way to me, as the buildd's will need it, and some daemons like mysql or postgres seem to want a larger data size anyway. > I think it's still an issue for kfreebsd-i386? But in any case, it's > not RC as cmor never supported kfreebsd-i386 before. You're right, there's still a separate, non-RC bug for that: #598745 Even with 'ulimit -d unlimited', kfreebsd-i386 is bounded by MAXDSIZ = 512 MiB whereas cmor would need ~700ish. I suppose that and DFLDSIZ could be raised to 1 GiB on kfreebsd-i386 to try to fix this, but no higher as explained in: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598745#20 Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#85535: builtin memcmp() could be optimised
reassign 85535 gcc,gcc-4.7 found 85535 4.7.0-1 stop Hello, Thanks for the detailed bug report and your interest in improving Debian. I'm just doing some cleanup, I am not involved with the GCC package. The bug is still present/open in the upstream bug tracker, so I am reassigning the orphan bug (was assigned to gcc-4.0) to recent versions of the package. Regards. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#666067: transition: libkpathsea6
On Fri, 2012-04-27 at 22:51 +0900, Norbert Preining wrote: > On Fr, 27 Apr 2012, Adam D. Barratt wrote: > > testing and breaking it in unstable in the process - texlive people, > > does that sound okay? > > Definitely. After a few more removals and a small breakage (scalable-cyrfonts-tex) the new texlive stack is now in testing. I missed aging a catdvi upload, which is keeping libkpathsea5 in testing still, so I'm not closing the bug yet. Hopefully that should be sorted in tomorrow morning's run. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#666067: transition: libkpathsea6
On Thu, 2012-05-03 at 20:53 +0100, Adam D. Barratt wrote: > Cc:ed maintainers, please comment on the relevant note below which > corresponds to your package. > > For context, these four packages are broken by the transition of the new > libkpathsea + texlive stack to testing, which I'm trying to finalise. > I'd like to get that out of the way over the weekend, if not before, so > speedy responses would be appreciated. There's a possibility the > packages may be removed from testing if necessary. I realise the above mail was only sent yesterday, but the libkpathsea transition's been going on for well over a month now and coincides with other transitions we'd like to start. I've therefore removed most the listed packages from testing with tonight's britney run; all of the issues listed already affect the packages in unstable. If you need any help to get the packages back in to testing once they're fixed, please let us know. scalable-cyrfonts couldn't be removed as one of its binary packages is depended on by task-cyrillic-desktop. I've broken the -tex binary package temporarily to get things done, but that'll either need fixing or removing. > On Wed, 2012-05-02 at 14:45 +0900, Norbert Preining wrote: > > > - cadabra depends on texlive-latex3, which no longer exists > > > > I don't know which package (LaTeX package) they need, but it is > > probably in tl-latex-recommended or -extra. If they install > > texlive-full and the use dlocate to find the respective replacement it > > will be fixed in a minute. But I don't know what they need from the > > former -latex3 > > > > > - itrans depends on tex-common; the new version of tex-common Breaks > > the > > > current version of itrans. > > > > I know, this packagehas serious problems and I tried to fix a few of > > them but not all. I already informed the maintainers long time ago. > > > > > > > Likewise scalable-cyrfonts-tex. > > > > Same here, I had several contacts with the maintainer. The problem is > > that this package provides a tex font name that is already in use > > since long and also since long in TeX Live. So installing this package > > would suddenly change all documents using the standard font names. > > > > The maintainer seems to have orphaned this package, so probably the > > best is to male an upload of the source package were this one bin > > package is not build anymore. > > > > > > > - dvi2ps-fontdesc-morisawa5 has a versioned dependency on > > > vfdata-morisawa5 which can't be satisfied by the Provides > > > > Should be adapted by the maintainers. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671545: gphoto2: FTBFS on hurd-i386.
Package: gphoto2
Severity: important
Tags: patch
Dear Maintainer,
gphoto2 currently FTBFS on hurd-i386 because of the unconditional use of
PATH_MAX in gphoto2/main.c. The attached patch should fix this issue.
I've set the size of the buf variable to 256 instead of PATH_MAX, as it is done
a few lines above. I'm not sure there is a way to get the real size of the
buffer, but it seems to be supposed to be 256
(http://libgphoto2.sourcearchive.com/documentation/2.4.6/structSetting.html).
WBR,
Cyril Roelandt.
-- System Information:
Debian Release: wheezy/sid
APT prefers unreleased
APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: hurd-i386 (i686-AT386)
Kernel: GNU-Mach 1.3.99/Hurd-0.3
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
diff --git a/gphoto2/main.c b/gphoto2/main.c
index d523486..1ea824f 100644
--- a/gphoto2/main.c
+++ b/gphoto2/main.c
@@ -43,7 +43,6 @@
#include
#include
#include
-#include
#include
#include
@@ -1952,7 +1951,7 @@ main (int argc, char **argv, char **envp)
}
}
if (!gp_params.hook_script) {
- char buf[PATH_MAX];
+ char buf[256];
if (gp_setting_get("gphoto2","hook-script",buf)>=0) {
gp_params.hook_script = strdup(buf);
/* Run init hook */
Bug#671544: dh_compress: Optionally compress with bzip2 or xz
Package: debhelper Version: 9.20120419 Severity: wishlist Dear Joey, it would be neat, if dh_compress would have command line options similar to dpkg-source to allow different compression methods and maybe also other compression levels than the hardcoded 9, e.g. dh_compress --compression-level=6 --compression=xz dh_compress -z7 -Zbzip2 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (400, 'stable'), (110, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.3.0-trunk-amd64 (SMP w/1 CPU core) 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 debhelper depends on: ii binutils2.22-6 ii dpkg-dev1.16.3 ii file5.11-1 ii html2text 1.3.2a-15 ii man-db 2.6.1-2 ii perl5.14.2-9 ii po-debconf 1.0.16+nmu2 debhelper recommends no packages. Versions of packages debhelper suggests: ii dh-make 0.60 -- 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#671543: pyqwt3d: FTBFS: qwt3d_openglhelper.h:67:31: error: 'gluErrorString' was not declared in this scope
Source: pyqwt3d Version: 0.1.7~cvs20090625-8 Severity: serious Justification: fails to build from source pyqwt3d FTBFS: | for pyvers in 2.7 2.6;\ | do\ | for qtvers in 4;\ | do\ | export QTDIR=/usr/share/qt$qtvers;\ | (cd build/py$pyvers-qt$qtvers/configure;\ | /usr/bin/make);\ | done;\ | done | make[1]: Entering directory `/build/pyqwt3d-Es6U5q/pyqwt3d-0.1.7~cvs20090625/build/py2.7-qt4/configure' | make[2]: Entering directory `/build/pyqwt3d-Es6U5q/pyqwt3d-0.1.7~cvs20090625/build/py2.7-qt4/configure/Qwt3D_Qt4' | g++ -c -pipe -fPIC -Os -Wall -W -D_REENTRANT -DNDEBUG -DGL2PS_HAVE_ZLIB -DHAS_NUMPY -DQT_NO_DEBUG -DQT_CORE_LIB -DQT_GUI_LIB -DQT_OPENGL_LIB -I. -I/usr/include/qwtplot3d-qt4 -I/usr/include/python2.7 -I/usr/lib/pymodules/python2.7/numpy/core/include -I/usr/include/qt4/Qt -I/usr/share/qt4/mkspecs/default -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtOpenGL -I/usr/include/qt4 -I/usr/X11R6/include -o sip_Qwt3Dcmodule.o sip_Qwt3Dcmodule.cpp | In file included from /usr/include/qwtplot3d-qt4/qwt3d_types.h:26:0, | from /usr/include/qwtplot3d-qt4/qwt3d_io_gl2ps.h:12, | from ../sip/qwt3d_io_gl2ps.sip:77, | from sip_Qwt3Dcmodule.cpp:7: | /usr/include/qwtplot3d-qt4/qwt3d_openglhelper.h: In function 'const GLubyte* Qwt3D::gl_error()': | /usr/include/qwtplot3d-qt4/qwt3d_openglhelper.h:67:31: error: 'gluErrorString' was not declared in this scope | /usr/include/qwtplot3d-qt4/qwt3d_openglhelper.h: In function 'bool Qwt3D::ViewPort2World(double&, double&, double&, double, double, double)': | /usr/include/qwtplot3d-qt4/qwt3d_openglhelper.h:104:97: error: 'gluUnProject' was not declared in this scope | /usr/include/qwtplot3d-qt4/qwt3d_openglhelper.h: In function 'bool Qwt3D::World2ViewPort(double&, double&, double&, double, double, double)': | /usr/include/qwtplot3d-qt4/qwt3d_openglhelper.h:120:95: error: 'gluProject' was not declared in this scope | In file included from /usr/include/qwtplot3d-qt4/qwt3d_plot.h:5:0, | from /usr/include/qwtplot3d-qt4/qwt3d_surfaceplot.h:4, | from ../sip/qwt3d_surfaceplot.sip:36: | /usr/include/qwtplot3d-qt4/qwt3d_enrichment_std.h: At global scope: | /usr/include/qwtplot3d-qt4/qwt3d_enrichment_std.h:65:2: error: 'GLUquadricObj' does not name a type | /usr/include/qwtplot3d-qt4/qwt3d_enrichment_std.h:66:2: error: 'GLUquadricObj' does not name a type | /usr/include/qwtplot3d-qt4/qwt3d_enrichment_std.h:96:2: error: 'GLUquadricObj' does not name a type | /usr/include/qwtplot3d-qt4/qwt3d_enrichment_std.h:97:2: error: 'GLUquadricObj' does not name a type | /usr/include/qwtplot3d-qt4/qwt3d_enrichment_std.h:98:2: error: 'GLUquadricObj' does not name a type | /usr/include/qwtplot3d-qt4/qwt3d_enrichment_std.h:99:2: error: 'GLUquadricObj' does not name a type | make[2]: *** [sip_Qwt3Dcmodule.o] Error 1 | make[2]: Leaving directory `/build/pyqwt3d-Es6U5q/pyqwt3d-0.1.7~cvs20090625/build/py2.7-qt4/configure/Qwt3D_Qt4' | make[1]: *** [all] Error 2 | make[1]: Leaving directory `/build/pyqwt3d-Es6U5q/pyqwt3d-0.1.7~cvs20090625/build/py2.7-qt4/configure' Despite the error, the build continued (violating Policy §4.6), only to fail again: | make[1]: Entering directory `/build/pyqwt3d-Es6U5q/pyqwt3d-0.1.7~cvs20090625/build/py2.6-qt4/configure' | make[2]: Entering directory `/build/pyqwt3d-Es6U5q/pyqwt3d-0.1.7~cvs20090625/build/py2.6-qt4/configure/Qwt3D_Qt4' | g++ -c -pipe -fPIC -Os -Wall -W -D_REENTRANT -DNDEBUG -DGL2PS_HAVE_ZLIB -DHAS_NUMPY -DQT_NO_DEBUG -DQT_CORE_LIB -DQT_GUI_LIB -DQT_OPENGL_LIB -I. -I/usr/include/qwtplot3d-qt4 -I/usr/include/python2.6 -I/usr/lib/pymodules/python2.6/numpy/core/include -I/usr/include/qt4/Qt -I/usr/share/qt4/mkspecs/default -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtOpenGL -I/usr/include/qt4 -I/usr/X11R6/include -o sip_Qwt3Dcmodule.o sip_Qwt3Dcmodule.cpp | In file included from /usr/include/qwtplot3d-qt4/qwt3d_types.h:26:0, | from /usr/include/qwtplot3d-qt4/qwt3d_io_gl2ps.h:12, | from ../sip/qwt3d_io_gl2ps.sip:77, | from sip_Qwt3Dcmodule.cpp:7: | /usr/include/qwtplot3d-qt4/qwt3d_openglhelper.h: In function 'const GLubyte* Qwt3D::gl_error()': | /usr/include/qwtplot3d-qt4/qwt3d_openglhelper.h:67:31: error: 'gluErrorString' was not declared in this scope | /usr/include/qwtplot3d-qt4/qwt3d_openglhelper.h: In function 'bool Qwt3D::ViewPort2World(double&, double&, double&, double, double, double)': | /usr/include/qwtplot3d-qt4/qwt3d_openglhelper.h:104:97: error: 'gluUnProject' was not declared in this scope | /usr/include/qwtplot3d-qt4/qwt3d_openglhelper.h: In function 'bool Qwt3D::World2ViewPort(double&, double&, double&, double, double, double)': | /usr/include/qwtplot3d-qt4/qwt3d_openglhelper.h:120:95: error: 'gluProject' was no
Bug#661283: cmor: FTBFS on kfreebsd-amd64
2012/5/4 Steven Chamberlain :
> This issue was worked around with a binNMU. It is fixed in kfreebsd-8
> VCS and kfreebsd-9 unstable by raising DFLDSIZ.
>
> I don't know if this has been changed yet on the buildd's, which I think
> run a squeeze kernel but DFLDSIZ is a boot-time configurable setting.
Actually, I think that increasing DFLDSIZ might not be the only
solution. DFLDSIZ only sets the default limit, but for login shells
it is increased automatically. Or if you're root you can increase it
by hand ("ulimit -d unlimited").
> So I think I should downgrade this to non-RC severity until we know
> whether it definitely is/isn't still an issue.
I think it's still an issue for kfreebsd-i386? But in any case, it's
not RC as cmor never supported kfreebsd-i386 before.
--
Robert Millan
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671542: pyicqt: FTBFS if built twice in a row: aborting due to unexpected upstream changes
Source: pyicqt Version: 0.8.1.5-4 Severity: important User: debian...@lists.debian.org Usertags: qa-doublebuild pyicqt FTBFS if built twice in a row: | dpkg-source -b pyicqt-0.8.1.5 | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: building pyicqt using existing ./pyicqt_0.8.1.5.orig.tar.gz | dpkg-source: info: local changes detected, the modified files are: | pyicqt-0.8.1.5/pyicqt.conf.xml | dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/pyicqt_0.8.1.5-4.diff.68IhlA | dpkg-source: info: you can integrate the local changes with dpkg-source --commit | dpkg-buildpackage: error: dpkg-source -b pyicqt-0.8.1.5 gave error exit status 2 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671541: catfish: FTBFS if built twice in a row: No rule to make target `distclean'. Stop.
Source: catfish Version: 0.3.2-2 Severity: important User: debian...@lists.debian.org Usertags: qa-doublebuild catfish FTBFS if built twice in a row: | fakeroot debian/rules clean | dpatch deapply-all | reverting patch 40Fix_gtkiconload from ./ ... ok. | reverting patch 30Fix_tracker_backend from ./ ... ok. | reverting patch 20Fix_desktopfile from ./ ... ok. | reverting patch 10Fix_makefile from ./ ... ok. | rm -rf patch-stamp patch-stampT debian/patched | dh_testdir | dh_testroot | rm -f build-stamp | [ ! -f Makefile ] || /usr/bin/make distclean | make[1]: Entering directory `/build/catfish-2w91mp/catfish-0.3.2' | make[1]: *** No rule to make target `distclean'. Stop. | make[1]: Leaving directory `/build/catfish-2w91mp/catfish-0.3.2' | make: *** [clean] Error 2 | dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#666889: transition: GNOME 3.4: clutter/cogl
On 02.05.2012 00:53, Cyril Brulebois wrote: > tag 666889 pending > thanks > > Adam D. Barratt (01/05/2012): >> If the tracker looks correct now, then I think we can get this started. > > From the discussion tonight on IRC, potential issues are: > gnome-sushi > eog-plugins > > and they can be removed if needed. > > Green light it is, then. I've uploaded cogl, clutter-1.0, clutter-gtk and mutter. So I guess you can schedule the first round of binNMUs, i.e. clutter-gesture, clutter-gst and clutter-imcontext. As clutter-1.0 has not been built everywhere yet, a dw is necessary atm. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#661283: cmor: FTBFS on kfreebsd-amd64
severity 661283 important thanks Hi, This issue was worked around with a binNMU. It is fixed in kfreebsd-8 VCS and kfreebsd-9 unstable by raising DFLDSIZ. I don't know if this has been changed yet on the buildd's, which I think run a squeeze kernel but DFLDSIZ is a boot-time configurable setting. So I think I should downgrade this to non-RC severity until we know whether it definitely is/isn't still an issue. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#659832: Quick and dirty workaround using sudo
Until this bug can be fixed, I am using the following quick and dirty bash script to work around the issue. Note, this quick and dirty work around really is quick and dirty and may have security problems or other issues. The way it is written requires sudo, but if you don't mind entering passwords multiple times, it could be used with su -c instead of the first sudo and eliminate the second sudo in front of the su. I put this script in ~/bin/ as I'm the only one on my computer that ever needs to be root. I use this script in conjunction with a custom Konsole profile for whenever I need a root command line. This script, as written, gets your xauth magic cookie, asks for your user password once to add the magic cookie to root's xauth file, then immediately reuses the sudo authorization to start a root command line. ~/bin/mysux #!/bin/bash cookie=`xauth list $DISPLAY` sudo xauth add $cookie sudo su - -- BH Randomly selected fortune cookie: Rules for driving in New York: (1) Anything done while honking your horn is legal. (2) You may park anywhere if you turn your four-way flashers on. (3) A red light means the next six cars may go through the intersection. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#669427: apt segfaults on s390x
On Wed, May 02, 2012 at 05:28:16PM +0200, Philipp Kern wrote:
> On Wed, May 02, 2012 at 05:23:30PM +0200, David Kalnischkies wrote:
> > > 2129.4.17 Â kalnisc | Â Â /* Record the Description (it is not
> > > translated) */
> > > Â Â Â Â Â Â Â Â Â | Â Â MD5SumValue CurMd5 =
> > > List.Description_md5();
> > > Â Â Â Â Â Â Â Â Â | Â Â if (CurMd5.Value().empty() == true)
> > > Â Â Â Â Â Â Â Â Â | Â Â Â return true;
> > > Â Â Â Â Â Â Â Â Â | Â Â std::string CurLang =
> > > List.DescriptionLanguage();
> > > Â Â Â Â Â Â Â Â Â |
> > > Â Â Â Â Â Â Â Â Â | Â Â /* Before we add a new description we
> > > first search in the group for
> > > Â Â Â Â Â Â Â Â Â | Â Â Â a version with a description of the
> > > same MD5 - if so we reuse this
> > > Â Â Â Â Â Â Â Â Â | Â Â Â description group instead of
> > > creating our own for this version */
> > > Â Â Â Â Â Â Â Â Â | Â Â for (pkgCache::PkgIterator P =
> > > Grp.PackageList();
> > > Â Â Â Â Â Â Â Â Â | Â Â P.end() == false; P = Grp.NextPkg(P))
> > > Â Â Â Â Â Â Â Â Â | Â Â {
> > > Â Â Â Â Â Â Â Â Â | Â Â Â for (pkgCache::VerIterator V =
> > > P.VersionList();
> > > Â Â Â Â Â Â Â Â Â | Â Â Â V.end() == false; ++V)
> > > Â Â Â Â Â Â Â Â Â | Â Â Â {
> > > Â Â Â Â Â Â Â Â Â | Â Â if
> > > (IsDuplicateDescription(V.DescriptionList(), CurMd5, "") == false)
> > > Â Â Â Â Â Â Â Â Â | Â Â Â Â continue;
> > > Â Â Â Â Â Â Â Â Â | Â Â Ver->DescriptionList =
> > > V->DescriptionList;
> > > Â Â Â Â Â Â Â Â Â | Â Â return true;
> > > Â Â Â Â Â Â Â Â Â | Â Â Â }
> > > Â Â Â Â Â Â Â Â Â | Â Â }
> > >
> > > When IsDuplicateDescription is called, calling md5() on the
> > > V.DescriptionList()
> > > points to unallocated memory. Â Any idea why that could be?
> >
> > So you mean the Description struct is invalid (V.DescriptionList()) or
> > the V.DescriptionList().md5() char* ?
>
> The latter does not point to any initialized memory.
>
> > We are missing a bit of error checking here (callers of NewDescription() do
> > not check if return is != 0 and IsDuplicateDescription doesn't check if the
> > given Description is valid), but both shouldn't be a problem as
> > NewDescription
> > can only really fail if new memory can't be allocated and as each version
> > has
> > at least one description you shouldn't hit a problem in the dup check
> > either.
> > Both wouldn't be limited to s390x either way:
> > We seem to have a similar bugreport from ppc64 (#669243),
> > if i understand right it's also bigendian 64bit, but no other report.
>
> Yes. So would be sparc64. s390x is the only in-archive arch that's 64bit be.
>
> > The code in pkgcachegen.cc was reworked for multi-arch and especially the
> > dup
> > check is new and the code as such works wih pointer left and right, but non
> > of
> > it should be architecture dependent⦠Somehow i fear that it's more
> > related to
> > our checksum changes. We had way to many problems with sha1 and sha2 to
> > assume
> > md5 would be okay (the code for md5 itself is not new, but the code warping
> > around it).
>
> At least the problem was not in constructing the checksum object, but in
> retrieving the content for it (i.e. md5() in IsDuplicateDescription).
>
> > You mentioned bisecting? Any insigns which revisions are (not) effected?
> > (bzr has no bisect included by default, and last time i check the plugin
> > wasâ¦
> > lets say suboptimal for us as we tend to have "big" merges)
>
> Either the plugin was broken or the tree it acted upon was useless to bisect.
> I don't know.
>
I have been able to bisect the issue, by first converting the bzr
repository to git, and then with the usual method. The commit that has
broken apt on s390x is the following:
commit 22f07fc5e77bcedbc774a4b60d305da847fab287
Author: David Kalnischkies
Date: Wed Oct 12 15:47:56 2011 +0200
a version can have only a single md5 for descriptions, so we can optimize
the merging with this knowledge a bit and by correctly sharing the lists
we only need to have a single description list for possibly many different
versions. This also means that description translations are shared between
different sources
diff --git a/apt-pkg/pkgcachegen.cc b/apt-pkg/pkgcachegen.cc
index 3545517..3b2c08e 100644
--- a/apt-pkg/pkgcachegen.cc
+++ b/apt-pkg/pkgcachegen.cc
@@ -279,33 +279,36 @@ bool pkgCacheGenerator::MergeListPackage(ListParser
&List, pkgCache::PkgIterator
for (Ver = Pkg.VersionList(); Ver.end() == false; ++Ver)
{
pkgCache::DescIterator Desc = Ver.DescriptionList();
- Dynamic DynDesc(Desc);
- map_ptrloc *LastDesc = &Ver->DescriptionList;
+
+ // a version can only have one md5 describing it
+ if (MD5SumValue(Desc.md5()) != CurMd5)
+continue;
// don't add a new description
Bug#671540: tpp: please update to gem2deb packaging
Package: tpp
Version: 1.3.1-2
Severity: important
Dear Maintainer,
The Debian Ruby Team is working on transition to gem2deb packaging [0].
All ruby packages should follow the guidelines [1] for a more consistent
user experience with ruby packages in Debian.
Necessary changes are as follows:
debian/compat:
7
debian/control:
Build-Depends: debhelper (>= 7.0.50~), gem2deb (>= 0.2.13~), dpatch (>= 1.11)
XS-Ruby-Versions: 1.8
XB-Ruby-Versions: ${ruby:Versions}
Depends: ruby1.8, ruby-ncurses
debian/rules:
#!/usr/bin/make -f
%:
dh $@ --buildsystem=ruby --with ruby
[0] http://wiki.debian.org/Teams/Ruby#Finish_the_transition_to_gem2deb
[1] http://wiki.debian.org/Teams/Ruby/Packaging#Guidelines_for_Ruby_packaging
Best,
Per
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-4-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 tpp depends on:
ii ruby 4.8
ii ruby-ncurses [libncurses-ruby1.8] 1.2.4-4
ii ruby1.8 [ruby] 1.8.7.352-2
tpp recommends no packages.
Versions of packages tpp suggests:
ii figlet
ii texpower 0.2-7
-- 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#568993: tpp does not work correctly with UTF-8 encoded files
tags 568993 +pending kthxbye Hi! With the pending upload of ruby-ncurses (1.3.1-1) this will be resolved. The new version of ruby-ncurses is built with wide character support. Best, Per -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671539: svnmailer: FTBFS if built twice in a row: rm -f -- build-stamp build returned exit code 1
Source: svnmailer Version: 1.0.8-12 Severity: important User: debian...@lists.debian.org Usertags: qa-doublebuild svnmailer FTBFS if built twice in a row: | fakeroot debian/rules clean | dpatch deapply-all | reverting patch 01_restore_pristine_code from ./ ... ok. | rm -rf patch-stamp patch-stampT debian/patched | dh_testdir | dh_testroot | # Add here commands to clean up after the build process. | python setup.py clean | WARNING: Subversion/Python bindings could not be imported | running clean | dh_clean build-stamp build | rm: cannot remove `build': Is a directory | dh_clean: rm -f -- build-stamp build returned exit code 1 | make: *** [clean] Error 25 | dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
