Bug#549011: dpkg: Uses PATH rm (so might use safe-rm, which can be broken by broken perl), should use /bin/rm
Le mercredi 30 septembre 2009 15:06:15 Guillem Jover, vous avez écrit : One of the features of PATH is to allow the admin to override the system binaries. You had safe-rm installed and shot yourself in the foot when it broke, the same could have happened with coreutils (less probable though, but still). Programs should be able to rely on a functional rm to operate correctly (say, be able to remove stuff under /usr) w/o needing to hardcode the whole path, which safe-rm does not guarantee. That makes me think having safe-rm in the PATH at all is probably not a good idea anyway and I don't think we should be required to use hardcoded paths because safe-rm (or similar) might be there. At most safe-rm should explain its flakiness, as rm is a command that is Essential, and thus should always work, no matter what. Or yes, taken out of PATH and be used through aliases. Thus reassigning. regards, guillem Okay; fine for me. I was slightly too fast in my analysis of the problem. Best regards and thanks for your reassigning, OdyX -- Didier Raboud, proud Debian user. CH-1802 Corseaux did...@raboud.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605092: when sh is linked to dash /usr/sbin/amavisd-new-cronjob will not work
reassign 605092 amavisd-new 1:1:2.6.4-2
thanks
Le Thursday 2 December 2010 13:12:14 Ruud Baart, vous avez écrit :
In /usr/sbin/amavisd-new-cronjob:
do_amavis_cmd() {
if [ $(id -u -n) != ${SUUSER} ]; then
exec /bin/su -s /bin/sh - ${SUUSER} -c $* /dev/null
else
# to get the same quoting level as the su path
CMD=$*
exec ${CMD} /dev/null
fi
}
does not work. Change it to:
do_amavis_cmd() {
if [ $(id -u -n) != ${SUUSER} ]; then
exec /bin/su -s /bin/bash - ${SUUSER} -c $* /dev/null
else
# to get the same quoting level as the su path
CMD=$*
exec ${CMD} /dev/null
fi
}
and it works again.
This script is called /etc/cron.daily/amavisd-/usr/sbin/amavisd-new:
/usr/sbin/amavisd-new-cronjob sa-clean
This problem can also be seen as an amavisd-new problem.
It is an amavisd-new problem… Hence reassigning.
Cheers,
OdyX
--
Didier Raboud, proud Debian Maintainer (DM).
CH-1020 Renens
did...@raboud.com
signature.asc
Description: This is a digitally signed message part.
Bug#605692: when sh is linked to dash /usr/sbin/amavisd-new-cronjob will not work
reassign 605692 amavisd-new 1:1:2.6.4-2
thanks
Le Thursday 2 December 2010 13:12:14 Ruud Baart, vous avez écrit :
In /usr/sbin/amavisd-new-cronjob:
do_amavis_cmd() {
if [ $(id -u -n) != ${SUUSER} ]; then
exec /bin/su -s /bin/sh - ${SUUSER} -c $* /dev/null
else
# to get the same quoting level as the su path
CMD=$*
exec ${CMD} /dev/null
fi
}
does not work. Change it to:
do_amavis_cmd() {
if [ $(id -u -n) != ${SUUSER} ]; then
exec /bin/su -s /bin/bash - ${SUUSER} -c $* /dev/null
else
# to get the same quoting level as the su path
CMD=$*
exec ${CMD} /dev/null
fi
}
and it works again.
This script is called /etc/cron.daily/amavisd-/usr/sbin/amavisd-new:
/usr/sbin/amavisd-new-cronjob sa-clean
This problem can also be seen as an amavisd-new problem.
It is an amavisd-new problem… Hence reassigning.
Cheers,
OdyX
--
Didier Raboud, proud Debian Maintainer (DM).
CH-1020 Renens
did...@raboud.com
signature.asc
Description: This is a digitally signed message part.
Bug#605092: Sorry for the noise
reassign 605092 collectd 4.4.2-3 thanks Sorry for the typo; fixing hereby. Cheers, OdyX -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#602731: TinyMCE non-free plugin RC bugs fixed by the resolution of #591206 ?
Hi dear 60273{1,2} bugs,
TinyMCE got NMU'ed with a fix to #591206 (aka simple removal of the swf'es).
Could you please test if those bugs are now void (aka the package works without
modification with a sid TinyMCE) or what the fix needs to be.
TIA, cheers,
OdyX
--
Didier Raboud, proud Debian Maintainer (DM).
CH-1020 Renens
did...@raboud.com
signature.asc
Description: This is a digitally signed message part.
Bug#600374: #600374: NMU for Mokomaze ?
Le Monday 29 November 2010 03:18:55 Paul Wise, vous avez écrit : We are just waiting on the pkg-fso team to make an upload removing the icons and adding the patch I sent upstream. Hi, (Removing the RM bug CC, I'll send a mail to both bugreports if/when the upload is done.) As there hasn't been much of an answer from the pkg-fso team, I'd like to propose an NMU for mokomaze, in order to get this RC bug solved in time for Squeeze. Its changelog entry would be: mokomaze (0.5.5+git8+dfsg0-0.1) unstable; urgency=low * Non-maintainer upload. * Repack the orig tarball to remove non-free files (Closes: #600374) - therefore cherry-pick two upstream commits: + [084f1e7] Menu icons replaced with the free ones. + [920fb49] Build all the images from a set of SVG files. - Add a librsvg2-bin B-D to build the png images from their svg source. - Add automake B-Ds and an autoreconf call before the build. - Thanks go to Paul Wise for the patches. -- Didier Raboud did...@raboud.com Wed, 08 Dec 2010 10:23:12 +0100 I pushed the git repository I used to prepare the orig tarball there: http://git.debian.org/?p=users/odyx-guest/mokomaze-orig.git (branch dfsg-free) and my update of the packaging git repository there: http://git.debian.org/?p=users/odyx-guest/mokomaze.git (branch debian-squeeze) I built the package and pushed it to alioth: http://alioth.debian.org/~odyx-guest/debian/unstable/mokomaze_0.5.5+git8+dfsg0-0.1.dsc Now if one DD could review and upload this package for me, it'd be great. After the upload, I'll send a mail to debian-release + the RM bug (#605205) to ask the Release Team to choose between an unblock and a removal. Cheers, OdyX -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#600374: [pkg-fso-maint] Bug#600374: #600374: NMU for Mokomaze ?
Le Wednesday 8 December 2010 13:17:10 Sebastian Reichel, vous avez écrit : On Wed, Dec 08, 2010 at 11:12:03AM +0100, Didier 'OdyX' Raboud wrote: As there hasn't been much of an answer from the pkg-fso team, I'd like to propose an NMU for mokomaze, (…) Sorry for the long delay, I waited for Joachim (nomeata) to eventually answer you. The package was previously maintained by him, but he is no longer active in pkg-fso. No problem. mokomaze (0.5.5+git8+dfsg0-0.1) unstable; urgency=low * Non-maintainer upload. * Repack the orig tarball to remove non-free files (Closes: #600374) - therefore cherry-pick two upstream commits: + [084f1e7] Menu icons replaced with the free ones. + [920fb49] Build all the images from a set of SVG files. - Add a librsvg2-bin B-D to build the png images from their svg source. - Add automake B-Ds and an autoreconf call before the build. - Thanks go to Paul Wise for the patches. -- Didier Raboud did...@raboud.com Wed, 08 Dec 2010 10:23:12 +0100 Changelog looks fine to me. go on :) If all goes fine, Xavier Oswald will upload this for me during the day. Do you want to become a member of pkg-fso and push the git stuff into [0]? Hrm. While the offer is tempting, I'm too overloaded already, so no thanks. With the git repositories I linked here, you should be able to import my changes without me doing it… Now if one DD could review and upload this package for me, it'd be great. After the upload, I'll send a mail to debian-release + the RM bug (#605205) to ask the Release Team to choose between an unblock and a removal. I'm currently busy, but I can check it this evening. I'll send the NMUdiff as soon as the package is uploaded, so stay tuned. :-) Cheers, OdyX -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#600374: mokomaze: diff for NMU version 0.5.5+git8+dfsg0-0.1
tags 600374 + pending thanks Dear maintainer, I've prepared an NMU for mokomaze (versioned as 0.5.5+git8+dfsg0-0.1) and got it uploaded by Xavier Oswald (xoswald) to DELAYED/2. Please feel free to tell me if I get it delayed any longer. Regards, OdyX N.B. The debdiff being huge, I compressed it… -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com mokomaze_0.5.5+git8+dfsg0-0.1.debdiff.bz2 Description: application/bzip signature.asc Description: This is a digitally signed message part.
Bug#605205: 605205: RM: mokomaze/0.5.5+git8-1 or unblock mokomaze/0.5.5+git8+dfsg0-0.1
user release.debian@packages.debian.org usertags 605205 +unblock thanks Le Monday 29 November 2010 03:18:55 Paul Wise, vous avez écrit : On Sun, 2010-11-28 at 12:24 +0100, Didier 'OdyX' Raboud wrote: In the light of the discussion in this RC bug (in particular #20), I asked for a removal of the mokomaze package from Squeeze. See bug #605205 for the reasoning (and if you want to argue in favor or against). I don't think those reasons apply any longer since they were mainly about giving upstream time to fix the bug and the removal from testing took longer than the fix. While there isn't a Linux image or bootloader in squeeze that can run on the OpenMoko FreeRunner, that doesn't mean that mokomaze isn't useful on other systems running squeeze, for example it supports the ThinkPad HDAPS device or just a plain keyboard. I've personally played it on my laptop using just the keyboard. In addition people can run a custom kernel/bootloader on the OpenMoko FreeRunner and squeeze will work just fine. We are just waiting on the pkg-fso team to make an upload removing the icons and adding the patch I sent upstream. Hi dear Release Team, An upload of mokomaze fixing its RC bug (#600374) has been uploaded to unstable with the following changelog: mokomaze (0.5.5+git8+dfsg0-0.1) unstable; urgency=low * Non-maintainer upload. * Repack the orig tarball to remove non-free files (Closes: #600374) - therefore cherry-pick two upstream commits: + [084f1e7] Menu icons replaced with the free ones. + [920fb49] Build all the images from a set of SVG files. - Add a librsvg2-bin B-D to build the png images from their svg source. - Add automake B-Ds and an autoreconf call before the build. - Thanks go to Paul Wise for the patches. -- Didier Raboud did...@raboud.com Wed, 08 Dec 2010 10:23:12 +0100 … which compressed debdiff is available there: http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=77;filename=mokomaze_0.5.5+git8+dfsg0-0.1.debdiff.bz2;att=1;bug=600374 The debdiff is pretty big, but I believe it represents the minimal step needed to solve the RC bug. So; dear Release Team, please either unblock mokomaze_0.5.5+git8+dfsg0-0.1 or remove mokomaze_0.5.5+git8-1 from Squeeze. Both options would make Squeeze free from the #600374 RC bug. Cheers, OdyX -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#568126: lm-sensors: Resource conflicts policy in kernel has changed
tag 568126 -moreinfo +patch thanks Le Sunday 2 January 2011 15:57:30 Julien Cristau, vous avez écrit : tag 568126 moreinfo severity 568126 minor kthxbye On Thu, Aug 5, 2010 at 11:59:59 -0400, Moritz Muehlenhoff wrote: We won't diverge from the kernel default settings, so I'm reassigning to release-notes. Please provide a proposed text to ease the work of the people preparing the release notes. I don't really understand what we're supposed to be documenting here, so if you want it in the release notes it'd be really helpful to provide proposed text and references as Moritz asked. Cheers, Julien Although I'm not convinced that this bug would warrant a release-notes entry (as it doesn't necessarily affect many people), let's propose a text (linux-only of course): -%- 5.1.5. Change in kernel policy regarding resource conflicts The default setting for the acpi_enforce_resources parameter in the new Linux kernel version has changed to be strict by default. This can lead some legacy sensor drivers to be denied access the sensors hardware. This can be workarounded by setting this parameter to lax, e.g. by appending acpi_enforce_resources=lax to the kernel boot line. -%- Hrm; I'm no native english speaker nor kernel specialist; I hope my text helps. Cheers, OdyX -- Didier Raboud, proud Debian Developer. CH-1020 Renens did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#610727: rawtherapee: Crashes in some conditions
Le Saturday 22 January 2011 12:23:15 Philip Rinn, vous avez écrit : tags 610727 + moreinfo thanks Hi, could you please give some more information (eg. what do you mean with accessing specific files?). I don't see why rawtherapee should be removed from squeeze. If we would remove every package that crashes in some conditions from our archives we would loose a lot of useful software. Cheers, Philip Hi Philip, I was in a hurry when I did the bugreport, so I just copy-pasted the log I got; I will try to reproduce this in a cleaner way, with a file I can attach to the bugreport. As for the severity and my opinion statement, please accept my apologies; given the freeze state, I overreacted to the crash. Hence I did set a too high severity and gave my opinion on a matter I am not responsible of, based on wrong assumptions on my side. I hope I haven't offended you; sorry if I did, it was not my intention. Cheers, OdyX -- Didier Raboud, proud Debian Developer. CH-1020 Renens o...@debian.org signature.asc Description: This is a digitally signed message part.
Bug#509186: Closing 509186
reopen 509186 retitle 509186 [Installation-Report] D-I doesn't check for available space in /var before downloading packages thanks Le Saturday 22 January 2011 18:56:37 Miguel Figueiredo, vous avez écrit : Hi, Thanks for your report. Closing as it's an installation report from a debian installer version which isn't supported anymore. Feel free to test and report any issues against the current debian installer release (Squeeze RC1) which supports more hardware and also it's improved. Thanks! http://cdimage.debian.org/cdimage/squeeze_di_rc1/ Hi Miguel, and thanks for your message! Unfortunately, this issue hasn't been solved since then, hence I am re-opening this bug; re-title'ing it for clarity too. Please reassign to the correct d-i component. As for the issue, I think d-i should check for available space in /var before launching the actual download of packages. Cheers, OdyX -- Didier Raboud, proud Debian Developer. CH-1020 Renens o...@debian.org signature.asc Description: This is a digitally signed message part.
Bug#607417: ΑΠ: win32-loader: please offer a Boot from network with gPXE option
tags 607417 +pending thanks Le Tuesday 11 January 2011 12:40:33 Papakirikou Vaggelis, vous avez écrit : Hello, I attach the patch for the files we have modified... Evangelos Papakirikou (papak...@cti.gr) Ioannis Siahos (sia...@cti.gr) Hi Evangelos, Ioannis, and Alkis, (I hope I got the first names correctly…) Many thanks for your patch; I have now taken some time to inspect it and I created a branch on the Win32-Loader git repository, that includes most of the changes you propose: http://git.debian.org/?p=d-i/win32-loader.git;a=commitdiff;h=61e7dae042308d010ff897c7a7df9e98ac030be7 (on the pxe branch) Here's what I did: * Add the PXE functionality as an option (aka without PXE=yes make, win32-loader will work as usual) * Make the functionality gPXE/iPXE independent (aka you must provide a pxe.lkrn file at the sources root) * No mention of LTSP, but PXE everywhere * Add as few new strings as possible * No change of the Windows Registry key name I tested that here on a Windows7 machine with a renamed ipxe.lkrn and it just worked, so many thanks for your patch ! My current plan is to give you some time to test my patch (possibly adding yours on top) and if it works correctly, I'll merge it on the master branch; hence releasing a win32-loader source that allows the installation of a PXE loader, but without enabling it on the binaries (as neither gPXE nor iPXE is in Debian yet). So please keep me informed about the correctness of my patch for your purpose ! And by the way, if you could publish your changes in a git repository somewhere, it'd just be great for more collaboration ! Cheers, OdyX -- Didier Raboud, proud Debian Developer. CH-1020 Renens o...@debian.org signature.asc Description: This is a digitally signed message part.
Bug#444017: Please document win32-loader as a possible boot method for i386 and amd64
package installation-guide retitle 444017 Please point to the win32-loader standalone version as possible boot method for x86 tags 444017 +patch thanks tags Le Tuesday 25 September 2007 15:39:30 Jérémy Bobbio, vous avez écrit : Package: installation-guide Version: 20070319 Severity: wishlist Hi! As win32-loader is now present on Debian CDs and DVDs, it should be documented in the documented as a possible boot method for the relevant architectures (i386 and amd64). This would fit in sections 5 and A of the installation guide. Cheers, Hi Jérémy, as far as I can tell, this is fixed by the 5.1.2 section. But now that the standalone flavour will be shipped as tools/win32-loader/stable/win32-loader.exe on the mirrors, this ought to be documented too. Hence retitling and tagging accordingly. Here would be a proposed patch: Index: boot-installer/x86.xml === --- boot-installer/x86.xml (révision 66346) +++ boot-installer/x86.xml (copie de travail) @@ -81,6 +81,14 @@ /parapara +It is also possible to run a small Windows executable that will download the +installer, collect some configuration options and modify the Windows +bootloader accordingly. Then, on reboot, one can start the installer. +This executable is available as tools/win32-loader/stable/win32-loader.exe on +the debian; mirrors. + +/parapara + If you use an installation CD or DVD, a pre-installation program should be launched automatically when you insert the disc. In case Windows does not start it automatically, or if you are using a USB TIA, cheers, OdyX -- Didier Raboud, proud Debian Developer. CH-1020 Renens o...@debian.org signature.asc Description: This is a digitally signed message part.
Bug#545022: (no subject)
Le Tuesday 1 February 2011 03:13:06 Leonhard Weber, vous avez écrit :
Sorry, sounds rude, let me rephrase…
i would love to see the tools out there as a debian package. It is *the*
thing that is missing to take PySide as the productive bindings of choice
instead of PyQt4. Many run away in fear when they see the troublesome way
signals are linked. Specially if they are accustomed to things I am not
really proud of pronouncing like VisualBasic and the likes.
If there is anything y can contribute as a debian packaging layman, please
tell me.
Thank you very much for your efforts on PySide and packaging,
best regards,
~Shogun
Hi Shogun, and thanks for this rephrasing, it's much clearer and sounds better
to my ears too.
In fact, the packaging is almost ready, and already used in PPAs for Ubuntu
distributions, on the official PPA: https://launchpad.net/~pyside/+archive/ppa
(unfortunately, pyside-tools tests fail to run, but that should be fixed by the
next upstream release).
My current plan is to upload all the PySide stack (apiextractor,
generatorrunner, shiboken, pyside, _pyside-tools_, pyside-mobility) when
upstream tags them 1.0.0 (which should happen in some weeks now). The reason of
the waiting is that as upstream breaks A{P,B}Is frequently during ~beta and ~rc
releases, it's just a great amount of work to do it cleanly on Debian (where I
can break everything on the PPAs).
Don't worry, packaging is mostly ready and will land in unstable rapidly after
PySide 1.0.0 release.
Thanks for your understanding, cheers,
OdyX
--
Didier Raboud, proud Debian Developer.
CH-1020 Renens
o...@debian.org
signature.asc
Description: This is a digitally signed message part.
Bug#607417: ΑΠ: win32-loader: please offer a Boot from network with gPXE option
Le Wednesday 2 February 2011 14:26:25, vous avez écrit :
Hi,
Hi Yannis and thanks for your extended review,
Vaggelis forgot to mention that in order to have the pxe functionality work
properly you must follow the 1-4 steps:
1)The linux, initrd.gz, pxe.lkrn (gpxe 1.0.0) files must be placed in the
root folder.
I agree that pxe.lkrn has to be placed in the root folder. That's the point of
the pxe.target to depend on pxe.lkrn. I will enhance the code when {g,i}PXE
enters Debian in order to copy the pxe.lkrn directly (as is done for gl2dr and
loadlin.exe).
But I disagree with including linux and initrd.gz within the PXE patch, see
below.
2)The file debian/rules must have the PXE=yes option, instead
of STANDALONE=yes.
… only if you want to build a Debian package out of it. Otherwise, just run
PXE=yes make and you'll get a PXE-enabled win32-loader.exe.
3)The Makefile must have:
pxe.target: pxe.lkrn linux initrd.gz templates/ternary_choice.ini
instead of
pxe.target: pxe.lkrn templates/ternary_choice.ini
Same remark as 1), see below.
4)The main.nsi should be patched with main.nsi.diff.
(As a side remark, could you please use diff -Naur when providing diffs, it's
way easier to patch back.)
What your main.nsi.diff patch does is that it embeds a complete debian-
installer linux kernel and initrd.gz (which makes it fail with kfreebsd…). The
current win32-loader approach is to rely on Debian mirrors (and internet
connectivity) to get the latest released debian-installer kernels and initrd's.
Bundling a specific d-i version into a Windows executable defeats the fact that
the current 0.6.22 win32-loader will be able to download _any_ future stable
Debian-Installer.
But I can acknowledge that bundling specific versions can be useful. Could you
please report a bug (with wishlist severity) against win32-loader with a title
like Please add a d-i bundling possiblity ?
Another issue to consider is that when a user installs win32loader in pxe
mode, description in boot menu isn't very clear (continue with install
process). I think that in pxe mode you should better change this message
to Continue with network boot in file l10n/win32-loader.sh (line 81)
Same here; I plan to enhance the reboot messages shown by the Windows
bootloader. It'd be nice if you could report a wishlist bug against
win32-loader
with a title like Please enhance the reboot messages.
Yannis
So, given the messages received so far and my present answer, I am pretty
confident that the PXE patch does basically what you need; I will proceed in
merging the pxe branch to master. Other enhancements will certainly happen,
but please report separate bugs (it's not a matter of blocking discussion, but
to keep the one problem is one bug motto).
Cheers,
OdyX
--
Didier Raboud, proud Debian Developer.
CH-1020 Renens
o...@debian.org
signature.asc
Description: This is a digitally signed message part.
Bug#612226: Bug? xdm + nouveau + fluxbox
reassign 612226 xserver-xorg 1:7.5+8 thanks Le Sunday 6 February 2011 23:21:00 Lademann, Klaus, vous avez écrit : Package: ? Today i have new install of Debian Squeeze. First without Grafic. Then i install via netinst xorg xdm fluxbox with all depends. After few minutes its gone nothing. No external Mouse and no keyboard. Then i go on the first Term. Error: glibc /usr/bin/X doublefree or corruption (fasttop) 0x09136660. with shows of many libs about the X-System. Sorry. Hi Klaus, when you report a bug, you need to assign it to a specific package (which ? is not). I'm hereby reassigning to xserver-xorg's Squeeze version. Cheers, OdyX -- Didier Raboud, proud Debian Developer. CH-1020 Renens o...@debian.org signature.asc Description: This is a digitally signed message part.
Bug#612462: [Pkg-gnupg-maint] Bug#612462: gnupg: Please provide a win32 port of gpgv
Le Tuesday 8 February 2011 20:36:37 Thijs Kinkhorst, vous avez écrit :
On Tuesday 08 February 2011 17:06:37 Didier Raboud wrote:
a current flaw of the standalone version of win32-loader (source and
binary package in Debian) is that it downloads the d-i kernel and
initrds through Internet without any form of checking that those are
authenticated binaries from the Debian project (see #442180 for
details).
In order to solve this, the Windows executable needs to check the
signature on the downloaded Release{,.gpg} file and then check the
md5sums of various files. The md5sum checksum verification is already
implemented (although not uploaded yet) with a md5sum implementation
internal to NSIS. There are still missing pieces on FTP-Master side (see
#611087, which will get solved in their upcoming meeting, I heard), but
I would also need a gpgv.exe that could run on the target Windows host,
to check the downloaded Release{,.gpg} files.
I'm not aversive to this plan but I do not completely understand it. You
need gpgv.exe on the Windows platform, but you cannot install debs there,
right? So what would the role of this deb be exactly?
Hi Thijs,
thanks for your rapid answer.
This new binary package would serve the same purpose (and is designed likewise)
as cpio-win32 or gzip-win32: they are Build-Depends of win32-loader.
During the win32-loader build, they get embedded in the win32-loader.exe
Windows executable. When launched, this executable collects some informations
from the running Windows host and then uses cpio.exe and gzip.exe to repack a
new initrd with embedded preseeding.
(The executables are embedded in the win32-loader.exe using the
File /oname=$INSTDIR\cpio.exe /usr/share/win32/cpio.exe
File /oname=$INSTDIR\gzip.exe /usr/share/win32/gzip.exe
commands (in s_install.nsi in current win32-loader git). First argument being
the path in Windows, second being the (build-)source of said executables.)
Hence I would like to bundle gpgv.exe similarly, in order to unpack it in the
C:\win32-loader path ($INSTDIR above), to be able to check Release file
signatures, on the Windows host.
Is that clearer ? I can develop furthermore if needed.
Also I cannot test it. Would you assume responsibility for dealing with
potential bug reports for this?
If your Debian can run wine, gpgv.exe runs correctly under wine (although with
glitches around path handling in the --keyring option; which are
workaround'able).
But yes, I can handle this, and I'll make sure to be subscribed to gnupg's
bugreports if my patch gets accepted.
Cheers,
OdyX
--
Didier Raboud, proud Debian Developer.
CH-1020 Renens
o...@debian.org
signature.asc
Description: This is a digitally signed message part.
Bug#612690: Please move data files to /lib/ or /usr/share
package usb-modeswitch-data forwarded 612690 digidie...@draisberghof.de thanks Hi Michael, and thanks for your bugreport, first, I am hereby forwarding your bugreport to my nice upstream author (Hi Josh !). Le Thursday 10 February 2011 00:11:04 Michael Biebl, vous avez écrit : Package: usb-modeswitch-data Version: 20101222-3 Severity: normal Hi, usb-modeswitch-data ships around 150 small files in /etc/usb_modeswitch.d/ which don't look like configuration files at all, but more like a hardware database. Correct. I'd say it's a hardware database of configuration files. Given the nature of the problem usb-modeswitch addresses, it is very convenient to be able to debug using real configuration files. In addition if you use tools like etckeeper having a constantly changing usb-modeswitch-data is painful. I'm not personally using etckeeper, but I understand the problem. Please consider moving those files to /usr/share, or if they are needed during boot to /lib/usb-modeswitch. Note that this solution is implemented as the usb-modeswitch-data-packed package, which ships a tarball of what lives in /etc/usb-modeswitch.d. Both u-m- d and u-m-d-packed conflict with eachother, as they both ship the udev rules file (/lib/udev/rules.d/40-usb_modeswitch.rules). The idea behind providing both packages is to allow small disk impact under /usr xor configuration files for debugging. If there really is a need for a user to overwrite certain settings, make it possible, that a file can be copied from /usr/share to files in /etc taking preference. Since version 1.1.4, the usb-modeswitch.tcl script in package usb-modeswitch will give precedence to database entries found in the /usr/share/usb- modeswitch/configPack.tar.gz, without trying to fallback to /etc/usb- modeswitch.d/ entries (which cannot be present at the same time due to Conflicts anyway). I would be inclined to say that your bugreport is already addressed by the usb- modeswitch-data-packed package, but I'll let you comment on that. Cheers, OdyX -- Didier Raboud, proud Debian Developer. CH-1020 Renens o...@debian.org signature.asc Description: This is a digitally signed message part.
Bug#606121: Reopening; doesn't work at all
found 606121 1.6.6-2 reopen 606121 thanks Hi Ludovic, I'm sorry to reopen this bug now, but I must confess that I hadn't retried the pcsc-lite versions from experimental. Now that you uploaded pcsc-lite to unstable, I'm using this again, and it fails to work. For reasons I can't explain, I completely fail to access my smartcard, be it for GPG or SSH keys (for both of which I'm using gpg-agent). So for now I downgraded libpcsclite1 and pcscd to 1.5.5-4 and libccid to 1.3.11-2 (which then works). I noticed that it also fails to work if I upgrade only libccid to 1.4.1-2. (Therefor, I'm tempted to rise the severity of this bug to serious (aka above RC) to avoid testing migration, but I'll let you decide.) Please ask for any details you might need ! Cheers, OdyX -- Didier Raboud, proud Debian Developer. CH-1020 Renens o...@debian.org signature.asc Description: This is a digitally signed message part.
Bug#253612: Use of uninitialized value in string eq at /usr/bin/foomatic-configure line 332.
package foomatic-db-engine tag 253612 +unreproducible +moreinfo +upstream thanks Le Thursday 10 June 2004 15:01:52 Bill Allombert, vous avez écrit : I tried the following command: ~# foomatic-configure -p Epson-Stylus_Photo_EX -d gimp-print -s lpd -n lp -c file:/dev/lp0 and I got: Use of uninitialized value in string eq at /usr/bin/foomatic-configure line 332. I suppose this warning is a bug in itself (probably minor though). I get /etc/printcap contend removed and replaced by: # Entry edited Thu Jun 10 14:54:49 2004 by foomatic-configure. # Additional configuration atop /etc/foomatic/lpd/lp.ppd lp|photoex|Photo EX:\ :lf=/var/log/lp-errs:\ :sd=/var/spool/lpd/lp:\ :lp=/dev/lp0:\ :sh:\ :mx#0:\ :pw#80:\ :px#1440:\ :pl#66: which some how do not feel quite right. So I suspect something is wrong. Hi Bill, sorry for having taken so long in answering your bugreport. Can you still reproduce one of the two issues you were mentioning back in 2004 with the foomatic-db-engine version in Squeeze ? I can't succeed in reproducing this (gimp-print has disappeared, etc.), tagging accordingly. Cheers, OdyX -- Didier Raboud, proud Debian Developer. CH-1020 Renens o...@debian.org signature.asc Description: This is a digitally signed message part.
Bug#509189: #509189: foomatic-db-engine: device-uri is mixed up with printers
package foomatic-db-engine tags 509189 +moreinfo thanks Le Friday 19 December 2008 14:31:37 Steffen Joeris, vous avez écrit : Package: foomatic-db-engine Version: 3.0.2-20080211-1 Severity: important Hi I have the problem that my printers are both detected (I am using a modified version of printconf), but the device uris are mixed up. Therefore, my Epson points to the HP printer and vice-versa :) I believe the problem exists in cups_generate_usb_device_lists(). IMHO it would be nice, if that could somehow compare, if the cups device and the system device match. Not sure how to realize that. Alternatively, it could be possible to compare the cups device-uri later on with some other printer information. Please let me know your thoughts. :) Thanks for your work on foomatic. Cheers Steffen Hi Steffen, Sorry for waiting so long Is this issue still alive in the foomatic-db-engine as released in Squeeze ? If it is still the case, could you please provide an enlightenment of the problem for my (dummy eyes): I must confess I don't understand your problem very well. Thanks in advance, cheers, OdyX -- Didier Raboud, proud Debian Developer. CH-1020 Renens o...@debian.org signature.asc Description: This is a digitally signed message part.
Bug#598248: foomatic-db-engine: Takes a long time to spool/print after recent upgrade
reassign 598248 zathura 0.0.8.1-2 thanks Le Tuesday 28 September 2010 15:41:13 synt...@gmail.com, vous avez écrit : Please reassign to zathura. Sorry to have filed this against foomatic-db-engine. Thanks Hi Michel, as you asked, I'm hereby reassigning your bug to zathura's version in Squeeze. Cheers and thanks for your bugreport, OdyX -- Didier Raboud, proud Debian Developer. CH-1020 Renens o...@debian.org signature.asc Description: This is a digitally signed message part.
Bug#606121: Reopening; doesn't work at all
Le Thursday 10 February 2011 22:25:16, vous avez écrit : Can you follow http://pcsclite.alioth.debian.org/ccid.html#support to generate logs? Sure, here you are. 1) Insert my smartcard. With testing versions: $ cd /tmp; touch a; gpg --sign /tmp/a (pinentry-qt appears, I enter my password, /tmp/a gets signed). Upgrading libpcsclite1 and pcscd to 1.6.6-2 and libccid to 1.4.1-2. # killall -9 pcscd pcscd: no process found $ sudo -s # killall -9 pcscd pcscd: no process found # #(sounds normal wrt pcsc-lite changelog) # LIBCCID_ifdLogLevel=0x000F # export LIBCCID_ifdLogLevel # pcscd --foreground --debug --apdu debuglog.c:277:DebugLogSetLevel() debug level=debug 0031 debuglog.c:306:DebugLogSetCategory() Debug options: APDU 0131 configfile.l:245:DBGetReaderListDir() Parsing conf directory: /etc/reader.conf.d 0032 configfile.l:287:DBGetReaderList() Parsing conf file: /etc/reader.conf.d/0comments 0061 configfile.l:287:DBGetReaderList() Parsing conf file: /etc/reader.conf.d/libccidtwin 0030 pcscdaemon.c:553:main() pcsc-lite 1.6.6 daemon ready. 4218 hotplug_libhal.c:319:get_driver() Looking a driver for VID: 0x413C, PID: 0x8140 0600 hotplug_libhal.c:319:get_driver() Looking a driver for VID: 0x413C, PID: 0x8140 0681 hotplug_libhal.c:319:get_driver() Looking a driver for VID: 0x413C, PID: 0x8140 00026972 hotplug_libhal.c:319:get_driver() Looking a driver for VID: 0x1D6B, PID: 0x0002 1623 hotplug_libhal.c:319:get_driver() Looking a driver for VID: 0x0483, PID: 0x2016 1186 hotplug_libhal.c:319:get_driver() Looking a driver for VID: 0x0B97, PID: 0x7761 0856 hotplug_libhal.c:319:get_driver() Looking a driver for VID: 0x0B97, PID: 0x7772 1387 hotplug_libhal.c:319:get_driver() Looking a driver for VID: 0x1D6B, PID: 0x0001 2283 hotplug_libhal.c:319:get_driver() Looking a driver for VID: 0x1D6B, PID: 0x0001 1039 hotplug_libhal.c:319:get_driver() Looking a driver for VID: 0x1D6B, PID: 0x0001 2300 hotplug_libhal.c:319:get_driver() Looking a driver for VID: 0x1D6B, PID: 0x0002 1026 hotplug_libhal.c:319:get_driver() Looking a driver for VID: 0x1D6B, PID: 0x0001 1299 hotplug_libhal.c:319:get_driver() Looking a driver for VID: 0x1D6B, PID: 0x0001 25843842 winscard_msg_srv.c:202:ProcessEventsServer() Common channel packet arrival 0024 winscard_msg_srv.c:214:ProcessEventsServer() ProcessCommonChannelRequest detects: 5 0007 pcscdaemon.c:93:SVCServiceRunLoop() A new context thread creation is requested: 5 0082 winscard_svc.c:296:ContextThread() Thread is started: dwClientID=5, threadContext @21B9660 0024 winscard_svc.c:314:ContextThread() Received command: CMD_VERSION from client 5 0012 winscard_svc.c:326:ContextThread() Client is protocol version 4:2 0006 winscard_svc.c:346:ContextThread() CMD_VERSION rv=0x0 for client 5 0169 winscard_svc.c:314:ContextThread() Received command: ESTABLISH_CONTEXT from client 5 0020 winscard.c:193:SCardEstablishContext() Establishing Context: 0x103EB60 0006 winscard_svc.c:402:ContextThread() ESTABLISH_CONTEXT rv=0x0 for client 5 0135 winscard_svc.c:314:ContextThread() Received command: CMD_GET_READERS_STATE from client 5 0063 winscard_svc.c:314:ContextThread() Received command: CMD_WAIT_READER_STATE_CHANGE from client 5 0017 winscard_svc.c:314:ContextThread() Received command: CMD_STOP_WAITING_READER_STATE_CHANGE from client 5 0011 winscard_svc.c:383:ContextThread() CMD_STOP_WAITING_READER_STATE_CHANGE rv=0x0 for client 5 0031 winscard_svc.c:314:ContextThread() Received command: CMD_GET_READERS_STATE from client 5 0060 winscard_svc.c:314:ContextThread() Received command: CMD_GET_READERS_STATE from client 5 0037 winscard_svc.c:314:ContextThread() Received command: CMD_GET_READERS_STATE from client 5 0143 winscard_svc.c:314:ContextThread() Received command: CMD_GET_READERS_STATE from client 5 0031 winscard_svc.c:314:ContextThread() Received command: CMD_WAIT_READER_STATE_CHANGE from client 5 60049158 winscard_svc.c:314:ContextThread() Received command: CMD_STOP_WAITING_READER_STATE_CHANGE from client 5 0034 winscard_svc.c:383:ContextThread() CMD_STOP_WAITING_READER_STATE_CHANGE rv=0x0 for client 5 0041 winscard_svc.c:314:ContextThread() Received command: CMD_GET_READERS_STATE from client 5 0056 winscard_svc.c:314:ContextThread() Received command: CMD_WAIT_READER_STATE_CHANGE from client 5 60009131 winscard_svc.c:314:ContextThread() Received command: CMD_STOP_WAITING_READER_STATE_CHANGE from client 5 0025 winscard_svc.c:383:ContextThread() CMD_STOP_WAITING_READER_STATE_CHANGE rv=0x0 for client 5 0032 winscard_svc.c:314:ContextThread() Received command: CMD_GET_READERS_STATE from client 5 0036 winscard_svc.c:314:ContextThread() Received command: CMD_WAIT_READER_STATE_CHANGE from client 5 60060140 winscard_svc.c:314:ContextThread() Received command: CMD_STOP_WAITING_READER_STATE_CHANGE
Bug#606121: Reopening; doesn't work at all
Le Friday 11 February 2011 00:00:41, vous avez écrit : What smart card reader are you using? Oh yeah; damn. Forgot that. I think it's O2 Micro Oz776. Here's the pcsc_scan log, first with the card in, then without; both with pcscd, libpcsclite1 and libccid from testing: $ pcsc_scan PC/SC device scanner V 1.4.17 (c) 2001-2009, Ludovic Rousseau ludovic.rouss...@free.fr Compiled with PC/SC lite version: 1.5.5 Scanning present readers... 0: O2 Micro Oz776 00 00 Fri Feb 11 00:18:33 2011 Reader 0: O2 Micro Oz776 00 00 Card state: Card inserted, Exclusive Mode, ATR: 3B FA 13 00 FF 81 31 80 45 00 31 C1 73 C0 01 00 00 90 00 B1 ATR: 3B FA 13 00 FF 81 31 80 45 00 31 C1 73 C0 01 00 00 90 00 B1 + TS = 3B -- Direct Convention + T0 = FA, Y(1): , K: 10 (historical bytes) TA(1) = 13 -- Fi=372, Di=4, 93 cycles/ETU 43010 bits/s at 4 MHz, fMax for Fi = 5 MHz = 53763 bits/s TB(1) = 00 -- VPP is not electrically connected TC(1) = FF -- Extra guard time: 255 (special value) TD(1) = 81 -- Y(i+1) = 1000, Protocol T = 1 - TD(2) = 31 -- Y(i+1) = 0011, Protocol T = 1 - TA(3) = 80 -- IFSC: 128 TB(3) = 45 -- Block Waiting Integer: 4 - Character Waiting Integer: 5 + Historical bytes: 00 31 C1 73 C0 01 00 00 90 00 Category indicator byte: 00 (compact TLV data object) Tag: 3, len: 1 (card service data byte) Card service data byte: C1 - Application selection: by full DF name - Application selection: by partial DF name - EF.DIR and EF.ATR access services: by GET RECORD(s) command - Card without MF Tag: 7, len: 3 (card capabilities) Selection methods: C0 - DF selection by full DF name - DF selection by partial DF name Data coding byte: 01 - Behaviour of write functions: one-time write - Value 'FF' for the first byte of BER-TLV tag fields: invalid - Data unit in quartets: 2 Command chaining, length fields and logical channels: 00 - Logical channel number assignment: No logical channel - Maximum number of logical channels: 1 Mandatory status indicator (3 last bytes) LCS (life card cycle): 00 (No information given) SW: 9000 (Normal processing.) + TCK = B1 (correct checksum) Possibly identified card (using /usr/share/pcsc/smartcard_list.txt): 3B FA 13 00 FF 81 31 80 45 00 31 C1 73 C0 01 00 00 90 00 B1 OpenPGP ^C $ pcsc_scan PC/SC device scanner V 1.4.17 (c) 2001-2009, Ludovic Rousseau ludovic.rouss...@free.fr Compiled with PC/SC lite version: 1.5.5 Scanning present readers... 0: O2 Micro Oz776 00 00 Fri Feb 11 00:18:54 2011 Reader 0: O2 Micro Oz776 00 00 Card state: Card removed, Exclusive Mode, ^C Cheers, OdyX -- Didier Raboud, proud Debian Developer. CH-1020 Renens o...@debian.org signature.asc Description: This is a digitally signed message part.
Bug#606121: Problem's in pcsc-lite…
Hi again, I just tried with pcsc-lite components from testing and the libccid snapshot (1.4.1+svn5585-1~OdyX1) and it works, so problem sounds to be in pcscd not run as system daemon. OdyX -- Didier Raboud, proud Debian Developer. CH-1020 Renens o...@debian.org signature.asc Description: This is a digitally signed message part.
Bug#606121: #606121: Bisection…
Hi again Ludovic, so far, what I understood is that support for my O2 Micro Oz776 reader had been removed in ccid 1.4.0 and will get reintroduced in 1.4.2. I'm currently with libccid 1.4.1+svn5585-1~OdyX1. But I still can't gpg --sign with pcscd/libpcsclite1 1.6.6 (be it the -2 in unstable or a +svn5585 snapshot). So I tried to get closer to the turnpoint: went to snapshot.d.org and tried all versions from 1.5.5-4 upwards. Each time, I killed any pcscd and any scdaemon running. It works flawlessly in 1.6.0 and 1.6.1, but fails from 1.6.2 upwards. So there is something in the 1.6.1-1.6.2 update that make the signing (or pcscd launching or whatever) fail for me. (I'm currently trying to svn-bisect the source between those two, but am failing at compiling correctly so far…) -- Didier Raboud, proud Debian Developer. CH-1020 Renens o...@debian.org signature.asc Description: This is a digitally signed message part.
Bug#614428: win32-loader: [l10n] Updated Finnish translation
Le Monday 21 February 2011 23:25:38 Tommi Vainikainen, vous avez écrit : Package: win32-loader Severity: wishlist Here is an updated version of Finnish translation. Hi Tommi, and thanks for your translation, unfortunately, your file seems to be encoded in ISO-8859-1 (where it claims to be; and uses caracters from; UTF-8). Hence produces an error at build time. I converted your file to UTF-8 using the following command: $ iconv -f ISO-8859-1 -t UTF-8 win32-loader.fi.po win32-loader.fi_utf8.po I attached the *.fi_utf8.po to this mail; can you please check that the file is correct ? Thanks in advance, cheers, OdyX -- Didier Raboud, proud Debian Developer. CH-1020 Renens o...@debian.org # Finnish translation for win32-loader d-i # Copyright © 2007-2011 Tommi Vainikainen # This file is distributed under the same license as the package. # Tommi Vainikainen tvain...@debian.org, 2007-2011. # msgid msgstr Project-Id-Version: win32-loader\n Report-Msgid-Bugs-To: \n POT-Creation-Date: 2011-02-21 17:01+\n PO-Revision-Date: 2011-02-22 00:18+0200\n Last-Translator: Tommi Vainikainen tvain...@debian.org\n Language-Team: Finnish debian-l10n-finn...@lists.debian.org\n Language: fi\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n #. translate: #. This must be a valid string recognised by Nsis. If your #. language is not yet supported by Nsis, please translate the #. missing Nsis part first. #. #: win32-loader.sh:36 win32-loader.c:39 msgid LANG_ENGLISH msgstr LANG_FINNISH #. translate: #. This must be the string used by GNU iconv to represent the charset used #. by Windows for your language. If you don't know, check #. [wine]/tools/wmc/lang.c, or http://www.microsoft.com/globaldev/reference/WinCP.mspx #. #. IMPORTANT: In the rest of this file, only the subset of UTF-8 that can be #. converted to this charset should be used. #: win32-loader.sh:52 msgid windows-1252 msgstr windows-1252 #. translate: #. Charset used by NTLDR in your localised version of Windows XP. If you #. don't know, maybe http://en.wikipedia.org/wiki/Code_page helps. #: win32-loader.sh:57 msgid cp437 msgstr cp850 #. translate: #. The name of your language _in English_ (must be restricted to ascii) #: win32-loader.sh:67 msgid English msgstr Finnish #. translate: #. IMPORTANT: only the subset of UTF-8 that can be converted to NTLDR charset #. (e.g. cp437) should be used in this string. If you don't know which charset #. applies, limit yourself to ascii. $target_distro; will be Debian and $kernel_name; #. will be either GNU/Linux or GNU/kFreeBSD (in ASCII) #: win32-loader.sh:82 #, sh-format msgid $target_distro $kernel_name - Continue with install process msgstr $target_distro $kernel_name - Jatka asennusta #. translate: #. IMPORTANT: only the subset of UTF-8 that can be converted to NTLDR charset #. (e.g. cp437) should be used in this string. If you don't know which charset #. applies, limit yourself to ascii. #: win32-loader.sh:88 msgid PXE - Network boot msgstr PXE - verkkokäynnistys #. translate: #. The nlf file for your language should be found in #. /usr/share/nsis/Contrib/Language files/ #. #: win32-loader.c:68 msgid English.nlf msgstr Finnish.nlf #. translate: #. This is the program name, that appears in the installer windows captions and in the Windows Uninstaller dialog. #. Ampersands () are _forbidden_ in that string. #. #: win32-loader.c:75 msgid Debian-Installer loader msgstr Debian-asentimen latain #: win32-loader.c:76 msgid Cannot find win32-loader.ini. msgstr Ei löydy win32-loader.iniä. #: win32-loader.c:77 msgid win32-loader.ini is incomplete. Contact the provider of this medium. msgstr win32-loader.ini on epätäydellinen. Ota yhteyttä tämän median toimittajaan. #: win32-loader.c:78 msgid This program has detected that your keyboard type is \$0\. Is this correct? msgstr Näppäimistötyypiksi on tunnistettu \$0\. Onko tämä oikein? #: win32-loader.c:79 msgid Please send a bug report with the following information:\n \n - Version of Windows.\n - Country settings.\n - Real keyboard type.\n - Detected keyboard type.\n \n Thank you. msgstr Ole hyvä ja lähetä vikailmoitus seuraavilla tiedoilla:\n \n - Windows-versio\n - Maa-asetukset\n - Todellinen näppäimistön tyyppi\n - Tunnistettu näppäimistön tyyppi\n \n Kiitos avustasi. #: win32-loader.c:80 msgid There doesn't seem to be enough free disk space in drive $c. For a complete desktop install, it is recommended to have at least 3 GB. If there is already a separate disk or partition for this install, or if you plan to replace Windows completely, you can safely ignore this warning. msgstr Levyllä $c ei ole riittävästi tilaa. Täydelliselle työpöytäasennukselle suositellaan vähintään 3 Gt vapaata levytilaa. Tämän viestin voi ohittaa mikäli asennukselle on erillinen levy taikka osio taikka suunnitelmana on korvata Windows kokonaan. #: win32-loader.c:81 msgid Error: not enough free disk space.
Bug#614552: win32-loader: [INTL:sk] Slovak po-debconf translation
tags 614552 +pending thanks Le Tuesday 22 February 2011 09:21:37, vous avez écrit : Package: win32-loader Version: 0.6.90 Priority: wishlist Tags: l10n patch .po attached ~~helix84 Hi Ivan, and thanks for your translation, I have committed your translation to the win32-loader git repository and it will be part of the next win32-loader upload. Thanks again, cheers, OdyX -- Didier Raboud, proud Debian Developer. CH-1020 Renens o...@debian.org signature.asc Description: This is a digitally signed message part.
Bug#614613: win32-loader: [INTL:ru] Russian program translation update
tags 614613 +pending thanks Le Tuesday 22 February 2011 17:49:33 Yuri Kozlov, vous avez écrit : Package: win32-loader Version: 0.6.90 Severity: wishlist Tags: l10n patch Russian program translation update is attached. Hi Yuri, Thanks for your translation; I just committed it to the win32-loader repository. It will be part of the next win32-loader upload. Cheers, OdyX -- Didier Raboud, proud Debian Developer. CH-1020 Renens o...@debian.org signature.asc Description: This is a digitally signed message part.
Bug#614843: win32-loader: [i18n:bg] Updated Bulgarian translation
tags 614843 +pending thanks Le Wednesday 23 February 2011 20:36:51 Damyan Ivanov, vous avez écrit : Package: win32-loader Severity: wishlist Tags: l10n Please find attached updated Bulgarian tranlation of win32-loader. Thanks, dam Hi Damyan, annd thanks for your translation, I just committed it to the win32-loader repository and it will be part of the next upload. Cheers, OdyX -- Didier Raboud, proud Debian Developer. CH-1020 Renens o...@debian.org signature.asc Description: This is a digitally signed message part.
Bug#594322: [Foo2zjs-maintainer] Bug#594322: foo2zjs: Please upgrade to more recent version for Squeeze.
Le Thursday 24 February 2011 13:12:13 Till Kamppeter, vous avez écrit : OK. Then take the Apport hook into the Debian package and we keep foo2zjs identical on Debian and Ubuntu. Till If this is done (and I think it's desirable for Ubuntu), please do it in a Distribution-dependent way, see e.g. the foomatic-filters debian/rules: derives_from_ubuntu := $(shell (dpkg-vendor --derives-from Ubuntu echo yes) || echo no) (…) override_dh_install: dh_install ifeq ($(derives_from_ubuntu),yes) install -D -m 644 debian/ubuntu/apport-hook.py $(CURDIR)/debian/foomatic-filters/usr/share/apport/package-hooks/source_foomatic-filters.py endif This way you have one source package, but the binary package gets different contents depending on the distribution. Cheers, OdyX -- Didier Raboud, proud Debian Developer. CH-1020 Renens o...@debian.org signature.asc Description: This is a digitally signed message part.
Bug#616024: ghostscript: please provide debugging package
Le Wednesday 2 March 2011 12:40:09 Jonas Smedegaard, vous avez écrit : On Tue, Mar 01, 2011 at 11:39:50PM +0100, Yves-Alexis Perez wrote: I'm experiencing segfaults with ghostscript (using it from epstopdf or directly on eps files) and would like to provide a meaningful backtrace. But as there's no -dbg package that means I have to rebuild it completely with -g and -O0. It'd be nice to have the debugging symbols somewhere. Help much appreciated here. I do understand that a -dbg package is essentially a rebuild without optimizations and without stripping. But I have no expecience in this, so could use a pointer to some guidelines of whatminimal pieces are needed to extract and include in that -dbg package and where to put it (I believe I saw somewhere that there's a trick of putting -dbg libs in a subdir which makes it extend (not replace) the normal package and get used if available). - Jonas AFAIK, providing debugging symbols is just a matter of 1) building with -g -O2 (policy defaults) 2) stripping the symbols without throwing them away (dh_strip has an --dbg- package option therefor). CDBS (which I don't know) has a Debug package support entry in its documentation, which seems to indicate that adding a ghostscript-dbg package in debian/control is sufficient. /me tries… -- Didier Raboud, proud Debian Developer. CH-1020 Renens o...@debian.org signature.asc Description: This is a digitally signed message part.
Bug#616024: ghostscript: please provide debugging package
tags 515024 +pending thanks Le Wednesday 2 March 2011 20:11:35 Yves-Alexis Perez, vous avez écrit : Yes, with cdbs just adding a -dbg package in debian/control should be enough. Regards, This has been committed to ghostscript's git (with pre-ack from Jonas). Cheers, -- Didier Raboud, proud Debian Developer. CH-1020 Renens o...@debian.org signature.asc Description: This is a digitally signed message part.
Bug#607417: win32-loader: please offer a Boot from network with gPXE option
block 607417 by 474034 thanks Hi Alkis, and thanks for your bugreport, We've modified it a bit so that it adds a Boot from network entry in the Windows boot loader, instead of loading a Linux kernel. To accomplish this we statically linked gpxe.lkrn [1] to win32-loader.exe, and we modified main.nsi to load this instead of vmlinuz. No initrd was necessary. Nice. Currently the resulting ltsp-loader.exe [2] is used in some thousand Greek school PCs to netboot thin and fat clients. But many others have asked for this functionality in the #ltsp irc channel and in the ltsp-discuss mailing list, so we think it'd be much better if the upstream win32-loader Makefile supported a Boot from network with gPXE target. Unfortunately gPXE is not yet in Debian due to (afaik) some unresolved licensing issues. However if the win32-loader Makefile supported a gPXE target, maybe one of the following would be possible: * The gPXE devs to compile win32-loader with the gPXE target, and to host the resulting win32-loader-gpxe.exe on their site themselves. * Or a sysadmin or user could do that for his own use. * Or win32-loader.exe could dynamically download gpxe.lkrn from the gPXE website. As gPXE is not in Debian, I don't think it would be correct to upload a win32-loader including said functionality in Debian right now (in particular not in these times of freeze). Hence I marked that bug blocked by the gPXE ITP. But more generally, I don't see a reason to keep your patch out: merging is always good. If you want we can send you the .diff for main.nsi that we currently have, but we aren't very skilled with NSIS scripting so if you decide to add that functionality upstream you'd probably want to properly reimplement this yourselves. :) Please do so; attach the patch to this bugreport so that we can take a look at it. In any case thanks again, Alkis Georgopoulos Thanks also go to you for making such a nice use of win32-loader. :- Cheers, OdyX -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#607669: linux-image-2.6.37-rc5-amd64: Dell Latitude D630 backlight fails to resume to on
reopen 607669 found 607669 2.6.37-1~experimental.1 retitle 607669 linux-image-2.6.37-trunk: Dell Latitude D630 backlight fails to resume to on thanks Hi, sorry, but despite what I thought, this has happened again using the 2.6.37- trunk version. Hence re-opening. Cheers, OdyX -- Didier Raboud, proud Debian Developer. CH-1020 Renens o...@debian.org signature.asc Description: This is a digitally signed message part.
Bug#609761: [Foo2zjs-maintainer] Processed: severity of 609761 is serious, tagging 609761
Le Monday 17 January 2011 10:00:08 Julien Cristau, vous avez écrit : Rescheduling Didier's upload would probably be a good idea. I can change urgency afterwards. That's now done; to 0-day: reschedule foo2zjs_20090908dfsg-5.1_amd64.changes 0-day foo2zjs_20090908dfsg-5.1_amd64.changes moved to 0-day … Cheers, OdyX -- Didier Raboud, proud Debian Developer. CH-1020 Renens o...@debian.org signature.asc Description: This is a digitally signed message part.
Bug#566932: Provide a 'deamon-like' sm
clone 566932 -1 reassign -1 reportbug retitle -1 reportbug sm shows bugs of the binary package sm (of source screen-message) but finally reports against sm (source) thanks Le mardi 26 janvier 2010 00:45:23, vous avez écrit : reassign 566932 screen-message thanks Source package sm is something else which I happen to maintain. Cheers, Dirk Hi Dirk, Sorry for the noise ! I really meant to do it correctly… I think that this is a bug of reportbug, because I launched reportbug sm, could consult the Debian BTS reports on screen-message (source), and write my report directly in reportbug. The fact that my bug lands on your source package sm is highly confusing to me and should somehow be turnarounded… So cloning this bug to a a bug against reportbug. Best regards, OdyX -- Didier Raboud, proud Debian user. CH-1020 Renens did...@raboud.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#567327: usb-modeswitch: Add versioned depdendency on udev
reassign 567327 usb-modeswitch-data 20100110-1 tag 567327 +pending thanks Le jeudi 28 janvier 2010 14:57:41 Sam Morris, vous avez écrit : Package: usb-modeswitch Version: 1.0.7-1 Severity: wishlist I wanted to set up a laptop running lenny to be able to use a usb mobile broadband connection. In order to do this, I had to install usb-modeswitch to have the device flip into modem mode when plugged in. The version of usb-modeswitch in squeeze drops its udev rules in /lib/udev/rules.d, which lenny's udev does not appear to use. So I had to also upgrade udev to squeeze's version to get usb-modeswitch to function. It would be helpful if usb-modeswitch would depend on an appropriate version of udev; since squeeze currently contains such a version, 150-2 would be fine by me if you don't want to work out exactly which version first added support for /lib/udev/rules.d. Hi Sam, and thanks for your bugreport, As the actual package in sid containing the file in /lib/udev/rules.d is usb- modeswitch-data, I am hereby reassigning this bug to this other package. I rapidly went through the udev changelog and its NEWS file, and it appears that the version propagating the change is 0.140-1 (thus bigger than stable-security, but smaller than actual testing). I am also tagging this bug as pending, thanks to the following commit: http://git.debian.org/?p=collab-maint/usb-modeswitch- data.git;a=commitdiff;h=60460b090afb2c28cd25a849002f4bce2edfcf52 I am seeking a sponsor for the upload : if you know one… :-) Best regards, OdyX -- Didier Raboud, proud Debian user. CH-1020 Renens did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#567438: usb-modeswitch: Upgrade failure from 1.0.7-1 to 1.1.0-1
# pending by http://git.debian.org/?p=collab-maint/usb-modeswitch.git;a=commitdiff;h=3a0ecad tag 567438 +pending thanks Le vendredi 29 janvier 2010 05:43:37, vous avez écrit : Package: usb-modeswitch Version: 1.0.7-1 Severity: normal Preparing to replace usb-modeswitch 1.0.7-1 (using .../usb-modeswitch_1.1.0-1_i386.deb) ... Unpacking replacement usb-modeswitch ... dpkg: error processing /var/cache/apt/archives/usb-modeswitch_1.1.0-1_i386.deb (--unpack): trying to overwrite '/lib/udev/rules.d/40-usb_modeswitch.rules', which is also in package usb-modeswitch-data 0:20100127-1 Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/usb-modeswitch_1.1.0-1_i386.deb Hi Sven-Haegar, and thanks for your bugreport,! I should have checked that, it just slipped under my radar. The fix was easy and is already in the pipes (should be there for the next dinstall run ). Thanks again and sorry for the disturbance. Best regards, OdyX -- Didier Raboud, proud Debian user. CH-1020 Renens did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#525292: [Debian #525292] Re: Any news on this?
Le mercredi 24 juin 2009 18:21:35 Jeffrey G Thomas, vous avez écrit : Any news on the status of KDESUDO and the possibility of getting a working package? Hi Jeffrey, In collaboration with upstream author Anthony Mercatante, I hunted this bug a little more. What I discovered so far is that the xauth command launched on line 166 of kdesudo/kdesudo.cpp fails on Debian and succeeds on Ubuntu. It seems that the X server configurations differ in a sufficiently significant way to make the xauth command fail. I began to discuss this with the Debian X Team on IRC and will file a bug for this in the next days (and report this here accordingly). My feeling is that if this xauth bug is fixed, it should make kdesudo work. More updates during next week ! Best regards, OdyX -- Didier Raboud, proud Debian user. CH-1802 Corseaux did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#525292: [Debian #525292] Fix pending
# Pending by commit 15457 in pkg-kde svn repository
# http://svn.debian.org/wsvn/pkg-kde/kde-extras/kdesudo/trunk/?rev=15457
tag 525292 patch pending
thanks
# Launchpad commands
status inprogress
tag patch
done
Hi all,
I finally found time, motivation and skills (cough) to fix this RC bug. It was
painfully complicated to understand, but the patch (attached) is finally very
small.
This will be uploaded very soon to Debian.
Best regards,
OdyX
--
Didier Raboud, proud Debian user.
CH-1802 Corseaux
did...@raboud.com
Description: Xauth: Use a list-and-add scheme instead of the generate command.
The xauth generate command doesn't work in environments where the SECURITY X
extension is disabled (like in Debian).
.
This is obviously an ugly hack, but works-here™
Origin: vendor
Bug: http://bugs.debian.org/525292
Forwarded: https://bugs.launchpad.net/kdesudo/+bug/365956
Author: Didier Raboud did...@raboud.com
Last-Update: 2009-08-03
Index: kdesudo-3.4.1/kdesudo/kdesudo.cpp
===
--- kdesudo-3.4.1.orig/kdesudo/kdesudo.cpp 2009-08-03 10:21:39.0 +0200
+++ kdesudo-3.4.1/kdesudo/kdesudo.cpp 2009-08-03 10:22:15.0 +0200
@@ -163,8 +163,10 @@
QByteArray disp = m_pCookie-display();
- QString c = /usr/bin/xauth -q -f + m_tmpName + generate
- + QString::fromLocal8Bit(disp) + . trusted timeout 60 /dev/null 21;
+QString c = xauth_token=`/usr/bin/xauth -q list + QString::fromLocal8Bit(disp)
+ + | head -n 1 | awk '{ print $3; }'`
+ + /usr/bin/xauth -q -f + m_tmpName + add :0 . $xauth_token 2/dev/null
+ + echo + m_tmpName;
blockSigChild();
if (!(f = popen(QFile::encodeName(c), r))) {
signature.asc
Description: This is a digitally signed message part.
Bug#533892: rules for Option iCON 225 HSDPA maybe wrong
Le dimanche 21 juin 2009 13:10:50 W. Martin Borgert, vous avez écrit : Package: usb-modeswitch Version: 0.9.7-1 Severity: normal Hi Martin, and thanks for your bugreport, first of all, a new 1.0.2-1 upstream release landed in unstable (and migrated to testing). You might be interested to try it. If I remember correctly, the rules for your device changed a little bit. Secondly, a mega-sorry for the delay, I have had tons of other things to do in the meanwhile. I have on Option UMTS modem with the USB id 0af0:6971 (output of lsusb -v attached) plugged in. When I run the command: # /usr/sbin/usb_modeswitch --DefaultVendor 0x0af0 --DefaultProduct 0x6971 --MessageEndpoint 0x05 --MessageContent 55534243785634120100860100 (as written in /etc/udev/rules.d/usb_modeswitch.rules) I get error messages: (…) Prepare switching, accessing device 007 on bus 003 ... Looking for active driver ... No driver found. Either detached before or never attached This seems to imply that your device was not correctly plugged in… This does not look like the right behaviour to me. What does error -2 mean? When I comment out the respective lines in /etc/usb_modeswitch.conf, and do not use udev, but run the command: # usb_modeswitch without arguments, I get: (…) All devices in target class mode. Nothing to do. Bye! This seems to imply that your device was _already_ switched before you launched usb_modeswitch. Is the device really supported? Are there maybe wrong parameters? Esp. I cannot find the MessageContent documented somewhere in the package, so it's hard to tell, whether there might be an error. The MessageContent is some sort of BlackMagic hexa stream pushed to the USB device. This is at least what I understood of it. Could you please give me your /var/log/syslog lines concerning the plugging of your device ? These indicate pretty clearly what happens : a) recognised as zeroconf usb-storage b) disconnected by usb-modeswitch c) recognised as modem d) appearance of /dev/ttyUSB* devices. Also notes that some devices begin to _not_ need usb-modeswitch anymore with newer kernel versions. (Minor point, which does not justify a bug report: In both /etc/udev/rules.d/usb_modeswitch.rules and /etc/usb_modeswitch.conf, the names of the contributors Bernd Holzmüller, Flávio Moringa, and Jérôme Oufella are encoded in ISO-8859-1. I believe, this should be UTF-8, right?) About this minor point, it's an easy fix, so I committed a patch already. Thanks for that ! Best regards, OdyX -- Didier Raboud, proud Debian user. CH-1802 Corseaux did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#514345: gtk-qt-engine-kde4: removal of package doesn't remove automatic startup config in kde4
package gtk-qt-engine tag 514245 wontfix thanks Le vendredi 6 février 2009 15:12:00 Xavier Brochard, vous avez écrit : Package: gtk-qt-engine-kde4 Version: 1.1+svn145-1 Severity: normal After removal of the gtk-qt-engine-kde4 package, the script ~/.kde4/env/gtk-qt-engine.rc.sh is still here and is still activated on startup: it is setup in system config / advanced / automatic startup regards xavier Hi Xavier, unfortunately, once a file has been written to any $HOME, systemwide packages can_not_ remove them. It is simply against policy. Best regards, OdyX -- Didier Raboud, proud Debian user. CH-1802 Corseaux did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#475518: Still the case with latest version ?
tag 475518 +moreinfo thanks Hi Torquil, could you try to reproduce your bug with an up-to-date testing or sid ? Best regards, Odyx -- Didier Raboud, proud Debian user. CH-1802 Corseaux did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#435908: Retry this now ?
package gtk-qt-engine tags 435908 moreinfo thanks Hi, could you please try to reproduce this bug with an uptodate Sid or Testing ? Best regards, OdyX -- Didier Raboud, proud Debian user. CH-1802 Corseaux did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#512782: gtk-qt-engine test version with your patch
Hi Guido, could you please test the package I prepared with your patch there: http://alioth.debian.org/~odyx-guest/packages/gtk-qt-engine/ and report back to the bug if it does (or not) fix your issue ? Thanks in advance, best regards, OdyX -- Didier Raboud, proud Debian user. CH-1802 Corseaux did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#539947: grub-invaders: Uses deprecated update-grub_lib
Package: grub-invaders Version: 1.0.0-8 Severity: normal Tags: patch Hi Fabian and Debian Games Team, actually, grub-invaders uses the deprecated /usr/lib/update-grub_lib (deprecated since grub2 [1.96+20081108-1], now in unstable [1.96+20090725-1]). The fix is rather simple, you'll find a patch attached. Best regards, OdyX -- Didier Raboud, proud Debian user. CH-1802 Corseaux did...@raboud.com diff -Naur invaders-1.0.0-8/debian/changelog invaders-1.0.0/debian/changelog --- invaders-1.0.0-8/debian/changelog 2009-08-04 18:40:25.0 +0200 +++ invaders-1.0.0/debian/changelog 2009-08-04 18:58:54.0 +0200 @@ -1,3 +1,11 @@ +invaders (1.0.0-8.1) unstable; urgency=low + + * Non-maintainer upload. + * Fixes Warning: update-grub_lib is deprecated, use grub-mkconfig_lib +instead (Closes: #xx) + + -- Didier Raboud did...@raboud.com Tue, 04 Aug 2009 18:57:55 +0200 + invaders (1.0.0-8) unstable; urgency=low * debian/control: diff -Naur invaders-1.0.0-8/debian/scripts/grub invaders-1.0.0/debian/scripts/grub --- invaders-1.0.0-8/debian/scripts/grub 2009-08-04 18:40:25.0 +0200 +++ invaders-1.0.0/debian/scripts/grub 2009-08-04 18:42:12.0 +0200 @@ -1,7 +1,7 @@ #!/bin/bash -e if test -e /boot/invaders ; then - source /usr/lib/grub/update-grub_lib + source /usr/lib/grub/grub-mkconfig_lib INVADERSPATH=$( make_system_path_relative_to_its_root /boot/invaders ) echo Found GRUB Invaders image: /boot/invaders 2 cat EOF signature.asc Description: This is a digitally signed message part.
Bug#568126: lm-sensors: Fails to read my sensors
Le jeudi 4 février 2010 19:58:32 Aurelien Jarno, vous avez écrit : Hi, since the 2010-01-30, sensors fails to read my sensors. Do you mean it was working before? Hi again, Yes. I have a munin instance running that stopped reporting values on that day, after a reboot (I guess). No sensors found! Make sure you loaded all the kernel drivers you need. Try sensors-detect to find out which these are. I haven't changed anything related to my modules or the sensors program itself, but it fails for a reason I can't find. Did you upgrade your kernel recently? It might be interesting to apt/aptitude log to see what has changed. I don't remember having done so, but it might be possible. I attached the aptitude.1.gz with the updates around that date. From the kernel log, I get things like that, which I don't fully get. [ 3659.067814] smsc47m1: Found SMSC LPC47M15x/LPC47M192/LPC47M997 [ 3659.067910] ACPI: I/O resource smsc47m1 [0x680-0x6ff] conflicts with ACPI region RTIO [0x680-0x6ff] [ 3659.067971] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver You should try to unload acpi before trying to load smsc47m192. After fresh reboot: $ lsmod | grep acpi $ lsmod | grep sm smsc47m192 9264 0 hwmon_vid 1828 1 smsc47m192 psmouse49521 0 i2c_core 15584 / 2 smsc47m192,i2c_i801 $ ls /sys/class/hwmon/ $ Don't hesitate to ask for details. I also noted that it might be a duplicate of #524038 (same module) or #566184 (It also fails to set the defaults, obviously). I really doubt, it is related. In the first one, the sensors works, it's just they don't correspond correctly to the machine (the formulas to compute the values may change from motherboard to motherboard), and the second one is problem setting the default value. lm-sensors is actually just a program that read raw values from /sys/classes/hwmon and display it in a nice way. Could you check in this directory if your smsc47m192 device is present or not. As mentioned above, I have nothing in /sys/class/hwmon (es too much I guessed). Maybe I wrecked the havoc (hardware failure) ? Regards, OdyX -- Didier Raboud, proud Debian user. CH-1020 Renens did...@raboud.com aptitude.1.gz Description: GNU Zip compressed data
Bug#568126: lm-sensors: Fails to read my sensors
Le jeudi 4 février 2010 21:08:55 Didier 'OdyX' Raboud, vous avez écrit : Le jeudi 4 février 2010 19:58:32 Aurelien Jarno, vous avez écrit : Hi, since the 2010-01-30, sensors fails to read my sensors. Do you mean it was working before? Hi again, Yes. I have a munin instance running that stopped reporting values on that day, after a reboot (I guess). No sensors found! Make sure you loaded all the kernel drivers you need. Try sensors-detect to find out which these are. I haven't changed anything related to my modules or the sensors program itself, but it fails for a reason I can't find. Did you upgrade your kernel recently? It might be interesting to apt/aptitude log to see what has changed. I don't remember having done so, but it might be possible. I attached the aptitude.1.gz with the updates around that date. Hi again, you were right… I just rebooted under 2.6.32-1 (instead of .33-trunk) and it works. So I'll have to check with the latest kernel in unstable (or wait for it to enter Squeeze. Wait stays is that it fails with .33-trunk. Regards, OdyX -- Didier Raboud, proud Debian user. CH-1020 Renens did...@raboud.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#568126: lm-sensors: Fails to read my sensors
Le jeudi 4 février 2010 22:25:09, vous avez écrit : lm-sensors is actually just a program that read raw values from /sys/classes/hwmon and display it in a nice way. Could you check in this directory if your smsc47m192 device is present or not. As mentioned above, I have nothing in /sys/class/hwmon (es too much I guessed). Sorry you are right, I meant /sys/classes/hwmon. From where does your kernel come? Are your sure CONFIG_THERMAL_HWMON is enabled in it? As wrongly (all numbers mixed) mentioned in http://bugs.debian.org/568126#20 , it works (I have a symlink in /sys/class/hwmon/) with 2.6.30-2 but doesn't with 2.6.32-trunk. Both kernels have been once in squeeze (2.6.30-2 is still in security squeeze/updates/main). -- Didier Raboud, proud Debian user. CH-1020 Renens did...@raboud.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#569321: cmake-data: FindPython{Interp, Libs}.cmake should take the desired python version as argument
tags 569321 +patch
thanks
Hi,
Here are the two patches that do this in a backwards-compatible way (tested
here).
Best regards,
OdyX
--
Didier Raboud, proud Debian user.
CH-1020 Renens
did...@raboud.com
--- /usr/share/cmake-2.8/Modules/FindPythonLibs.cmake 2009-11-13 19:32:52.0 +0100
+++ FindPythonLibs.cmake 2010-02-11 14:53:01.0 +0100
@@ -27,7 +27,14 @@
# Search for the python framework on Apple.
CMAKE_FIND_FRAMEWORKS(Python)
-FOREACH(_CURRENT_VERSION 2.6 2.5 2.4 2.3 2.2 2.1 2.0 1.6 1.5)
+# Allows to choose your python version by setting CMAKE_PYTHON_VERSION to e.g. 2.6
+if (CMAKE_PYTHON_VERSION)
+ SET(CMAKE_PYTHON_VERSIONS ${CMAKE_PYTHON_VERSION})
+else (CMAKE_PYTHON_VERSION)
+ SET(CMAKE_PYTHON_VERSIONS 2.6 2.5 2.4 2.3 2.2 2.1 2.0 1.6 1.5)
+endif (CMAKE_PYTHON_VERSION)
+
+FOREACH(_CURRENT_VERSION ${CMAKE_PYTHON_VERSIONS})
STRING(REPLACE . _CURRENT_VERSION_NO_DOTS ${_CURRENT_VERSION})
IF(WIN32)
FIND_LIBRARY(PYTHON_DEBUG_LIBRARY
--- /usr/share/cmake-2.8/Modules/FindPythonInterp.cmake 2009-11-13 19:32:52.0 +0100
+++ FindPythonInterp.cmake 2010-02-11 14:53:01.0 +0100
@@ -19,19 +19,20 @@
# (To distributed this file outside of CMake, substitute the full
# License text for the above reference.)
-FIND_PROGRAM(PYTHON_EXECUTABLE
- NAMES python2.6 python2.5 python2.4 python2.3 python2.2 python2.1 python2.0 python1.6 python1.5 python
+# Allows to choose your python version by setting CMAKE_PYTHON_VERSION to e.g. 2.6
+if (CMAKE_PYTHON_VERSION)
+ SET(CMAKE_PYTHON_VERSIONS ${CMAKE_PYTHON_VERSION})
+else (CMAKE_PYTHON_VERSION)
+ SET(CMAKE_PYTHON_VERSIONS 2.6 2.5 2.4 2.3 2.2 2.1 2.0 1.6 1.5)
+endif (CMAKE_PYTHON_VERSION)
+
+FOREACH(_CURRENT_VERSION ${CMAKE_PYTHON_VERSIONS})
+ FIND_PROGRAM(PYTHON_EXECUTABLE
+NAMES python${_CURRENT_VERSION}
PATHS
- [HKEY_LOCAL_MACHINE\\SOFTWARE\\Python\\PythonCore\\2.6\\InstallPath]
- [HKEY_LOCAL_MACHINE\\SOFTWARE\\Python\\PythonCore\\2.5\\InstallPath]
- [HKEY_LOCAL_MACHINE\\SOFTWARE\\Python\\PythonCore\\2.4\\InstallPath]
- [HKEY_LOCAL_MACHINE\\SOFTWARE\\Python\\PythonCore\\2.3\\InstallPath]
- [HKEY_LOCAL_MACHINE\\SOFTWARE\\Python\\PythonCore\\2.2\\InstallPath]
- [HKEY_LOCAL_MACHINE\\SOFTWARE\\Python\\PythonCore\\2.1\\InstallPath]
- [HKEY_LOCAL_MACHINE\\SOFTWARE\\Python\\PythonCore\\2.0\\InstallPath]
- [HKEY_LOCAL_MACHINE\\SOFTWARE\\Python\\PythonCore\\1.6\\InstallPath]
- [HKEY_LOCAL_MACHINE\\SOFTWARE\\Python\\PythonCore\\1.5\\InstallPath]
+ [HKEY_LOCAL_MACHINE\\SOFTWARE\\Python\\PythonCore\\${_CURRENT_VERSION}\\InstallPath]
)
+ENDFOREACH(_CURRENT_VERSION)
# handle the QUIETLY and REQUIRED arguments and set PYTHONINTERP_FOUND to TRUE if
# all listed variables are TRUE
signature.asc
Description: This is a digitally signed message part.
Bug#569321: cmake-data: FindPython{Interp, Libs}.cmake should take the desired python version as argument
Le jeudi 11 février 2010 14:57:23 Didier 'OdyX' Raboud, vous avez écrit :
tags 569321 +patch
thanks
Hi,
Here are the two patches that do this in a backwards-compatible way (tested
here).
Best regards,
OdyX
Hi again²,
I just updated FindPythonLibs to use a different variable. It is useful because
then you can do the following to detect debug libraries (the postfix is
different):
dh_auto_configure --builddirectory=build-$*-dbg -- \
-DCMAKE_BUILDTYPE:STRING=Debug \
-DCMAKE_SKIP_RPATH=true \
-DCMAKE_PYTHON_VERSION=$*-dbg \
-DCMAKE_PYTHONLIB_VERSION=$*_d;$* \
Best regards,
OdyX
--
Didier Raboud, proud Debian user.
CH-1020 Renens
did...@raboud.com
--- /usr/share/cmake-2.8/Modules/FindPythonLibs.cmake 2009-11-13 19:32:52.0 +0100
+++ FindPythonLibs.cmake 2010-02-11 16:51:14.0 +0100
@@ -27,7 +27,14 @@
# Search for the python framework on Apple.
CMAKE_FIND_FRAMEWORKS(Python)
-FOREACH(_CURRENT_VERSION 2.6 2.5 2.4 2.3 2.2 2.1 2.0 1.6 1.5)
+# Allows to choose your python version by setting CMAKE_PYTHON_VERSION to e.g. 2.6
+if (CMAKE_PYTHONLIB_VERSION)
+ SET(CMAKE_PYTHONLIB_VERSIONS ${CMAKE_PYTHONLIB_VERSION})
+else (CMAKE_PYTHONLIB_VERSION)
+ SET(CMAKE_PYTHONLIB_VERSIONS 2.6 2.5 2.4 2.3 2.2 2.1 2.0 1.6 1.5)
+endif (CMAKE_PYTHONLIB_VERSION)
+
+FOREACH(_CURRENT_VERSION ${CMAKE_PYTHONLIB_VERSIONS})
STRING(REPLACE . _CURRENT_VERSION_NO_DOTS ${_CURRENT_VERSION})
IF(WIN32)
FIND_LIBRARY(PYTHON_DEBUG_LIBRARY
signature.asc
Description: This is a digitally signed message part.
Bug#544410: fails to autoreconnect after wifi disaccociating
Le jeudi 11 février 2010 18:52:22 David Paleino, vous avez écrit : Hello, On Thursday 11 February 2010 18:23:57, Cyril Brulebois wrote: severity 544410 serious thanks Didier Raboud did...@raboud.com (10/11/2009): I am getting this bug very very often and each time, I do have to manually reconnect (through the GUI or the -curses). Metoo. Does this happen with 1.7.0 too? The original bugreport was about 1.6.2.2 (and I haven't had the time to re-triage all the bugs yet, exams at University). David Hi David, I must admit that I had no more of this bug. I can stay connected all day long without a glitch. Thanks for the time ! Best regards, OdyX -- Didier Raboud, proud Debian user. CH-1020 Renens did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#547490: included in 1.0.7-1 ?
Hi Stefano and thanks for your update ! Le dimanche 17 janvier 2010 14:01:38 Stefano Costa, vous avez écrit : Hi, apparently the latest 1.0.7-1 (that introduced usb-modeswitch-data separate package) includes a rule for this 3G device: st...@gibreel:~$ dpkg -L usb-modeswitch-data | grep 1446 /etc/usb_modeswitch.d/12d1:1446 But I can't seem to make it work anyway. dmesg output: These lines seem to indicate the opposite : [ 3667.781390] usbcore: registered new interface driver usbserial [ 3667.781664] USB Serial support registered for generic [ 3667.781963] usbcore: registered new interface driver usbserial_generic [ 3667.781968] usbserial: USB Serial Driver core [ 3668.000918] USB Serial support registered for GSM modem (1-port) [ 3668.001378] usbcore: registered new interface driver option [ 3668.001383] option: v0.7.2:USB Driver for GSM modems After the plugging, do you get some /dev/ttyUSB* devices ? The device is not available in Network Manager, I even tried to unmount the SD storage (I trick which I have read to be working for some other 3G stick). If your answer to the question above is no, could you please modify the file /usr/share/usb_modeswitch/usb_modeswitch.tcl to put 1 at line 32 and give me the /var/log/usb_modeswitch file afterwards ? (Don't forget to revert the modification afterwards…) Ciao, steko Thanks, OdyX -- Didier Raboud, proud Debian user. CH-1020 Renens did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#543636: Update about the packaging of pyside
Hi all, I heard that some people around begin to wonder where and when pyside is planned to be uploaded to Debian, so here is a short update : It has taken me some time and work, but it is now mostly ready. My apiextractor, generatorrunner and boostpythongenerator packages where uploaded multiple times already (to track upstream releases) and successfully built. I successfully built pyside itself on amd64 some days ago, with good-looking outputted .debs (lintian clean etc.) I am now waiting on my benevolent sponsors to review pyside and hopefully upload it in the next days. So keep tuned ! Best regards, OdyX -- Didier Raboud, proud Debian user. CH-1020 Renens did...@raboud.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#540091: A little more info ?
tags 540091 +moreinfo thanks Hi Anders, and thanks for your bugreport, Could you please provide a little more info than the too short does not work anymore? That is: what happens when you launch skype, which library is missing, etc. Thanks in advance, regards, OdyX -- Didier Raboud, proud Debian user. CH-1802 Corseaux did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#540091: A little more info ?
severity 540091 important retitle 540091 Skype fails because libuuid.so.1 is missing from ia32-libs merge 540091 539746 thanks Le jeudi 6 août 2009 16:58:48 Anders Lagerås, vous avez écrit : theis happens ERROR: ld.so: object '/usr/lib32/libv4l/v4l1compat.so' from LD_PRELOAD cannot be preloaded: ignored. /usr/bin/skype.real: error while loading shared libraries: libuuid.so.1: cannot open shared object file: No such file or directory Hi again, It seems to me that this bug is a duplicate of 539746 and 540014, thus merging. By the way, make sure that you have lib32v4l-0 installed. Best regards, OdyX -- Didier Raboud, proud Debian user. CH-1802 Corseaux did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#540735: Work in progress
Hi,
I spent time on this bug to understand what and what-elses… This work resulted
in two patches fixing the cannot import name options [0] and a runtime error
I had [1].
[0]
http://svn.debian.org/wsvn/pkg-kde/trunk/packages/kdeadmin/debian/patches/01_system_config_printer_kde_cupsutils.diff
[1]
http://svn.debian.org/wsvn/pkg-kde/trunk/packages/kdeadmin/debian/patches/03_fix_runtime_fail_type_mismatch.diff
What I understood so far is that kde4.py file from python-kde4 [2] is not
loaded by the system-config-printer-kde, where it should (obviously). A
possibility was to patch s-c-p-k to get rid of what needed python-kde4, but it
is an obviously broken solution. Finally, I found the necessary trick to make
s-c-p-k work :
# ln -sf /usr/lib/pymodules/python2.5/PyQt4/uic/widget-plugins/kde4.py
/usr/share/python-qt4/widget-plugins/
# ln -sf /usr/lib/pymodules/python2.5/PyQt4/uic/widget-plugins/kde4.pyc
/usr/share/python-qt4/widget-plugins/
[2] python-kde4: /usr/share/pyshared/PyQt4/uic/widget-plugins/kde4.py
My guess is that python-qt4 has a path problem and should be able to catch
those kde4.py{,c} files where they are. Does this mean that this (RC) bug
should be reassigned to python-qt4 ?
Best regards,
OdyX
--
Didier Raboud, proud Debian user.
CH-1802 Corseaux
did...@raboud.com
signature.asc
Description: This is a digitally signed message part.
Bug#541150: New version ?
tags 505158 -experimental +upstream tags 541150 +upstream reassign 541150 gtk-qt-engine merge 541150 505158 thanks Hi Ivan, gtk-qt-engine-kde4 has been superseeded by gtk-qt-engine. Can you try with this version and report back if it still fails ? Note that I am very certain it will, see #505158… Thus tagging and merging the two bugs. Best regards, OdyX -- Didier Raboud, proud Debian user. CH-1802 Corseaux did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#540735: More Work in Progress
clone 540735 -1 retitle 540735 system-config-printer-kde broken because cannot import name options tags 540735 +pending reassign -1 python-qt4 retitle -1 python-qt4 should not install uic/widget-plugins in /u/s/python-qt4 (but should conform to upstream) severity -1 important tags -1 +patch thanks Hi all again, it took me some time to figure it all, and its not necessarily clear at first sight for everyone. Let me summarize that here : 1) The ImportError: cannot import name options error is fixed in the Debian kdeadmin svn [0] (actually, it was an update to that patch). This will be part of the next upload. 2) The ImportError: No module named kpushbutton error is due to a path mismatch between python-kde4 (src:kdebindings) and python-qt4. python-qt4 installs the uic/widget-plugins in a non-standard place (namely /usr/share/python-qt4/) . But other packages provides other widget-plugins at upstream's original place (/usr/lib/python*/*-packages/PyQt4/uic/widget-plugins ). There are two solutions to this (at least, I see those two): a) patch kdebindings to diverge from upstream and follow python-qt4 b) unpatch python-qt4 to come back to upstream defaults. I discussed this within the pkg-qt-kde team and the smarter solution for us (and not because the patch goes elsewhere) would be b), to let Debian follow upstream and other applications will avoid unnecessary patches. Therefore this bug is cloned to python-qt4 so that the details for b) can be discussed there. I prepared a NMU patch for this solution [1], but of course, I would by large prefer to have this discussed with the python-qt4 guys. Best regards, OdyX [0] http://svn.debian.org/wsvn/pkg-kde/trunk/packages/kdeadmin/debian/patches/01_system_config_printer_kde_cupsutils.diff [1] http://alioth.debian.org/~odyx-guest/packages/python-qt4/python-qt4_4.5.1-1.2.debdiff -- Didier Raboud, proud Debian user. CH-1802 Corseaux did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#527122: [Debian] Usb-modeswitch improvement proposal
Hi, (could you please keep 527...@bugs.debian.org cc'ed so that the bugreport subscribers can read us ?) Le vendredi 15 mai 2009 22:05:39, vous avez écrit : Didier Raboud schrieb: My idea was not to have a dialog initiated by a hal .rules but to have a simple wrapper which any user can launch. This wrapper could have an option like --non-interactive which could do the actual switch if the DV:DP:UUMID is unique and do nothing (return error) if not. I'm not sure I understand that fully ... How would a user know he is supposed to start the wrapper? And does he have to do it every time he plugs his device in? It would work as now, with two possible cases: 1) automatic launch by a udev rule 2) hand launch for a not-yet-recognised device or without udev rules If the device doesn't have any rule for it, the user will have to launch it by hand (as actually without my additions in the Debian package), but if the device is known to usb-modeswitch (by an appropriate file in the database), the wrapper will be launched with --non-interactive. I still like the idea of a run-once-per-device installer better; if I remember correctly, a similar approach is chosen by the SANE scanner project. I dislike it, because it transfers the burden of configuration from upstream/distribution (aka you/me) to the user, where we could make him an easier life. But I can live with it, you are upstream afterall. :) What are your plans for future releases ? Doing the split of the configuration files could be a good first step. Then, the detection-and-prompting wrapper can be written in simple bash or something similar and I can handle the auto-detection .rules file (as now). I would prefer a tcl script which is my favourite rapid development language. A tcl interpreter/shell is likely installed on most systems and is small enough to quickly add it where it's missing. The readability is better than Bash or Perl and it's an excellent tool for text parsing and glueing together common command line tools. I can live with that too. Your choice ! The USB_ModeSwitch tool should not do much more than it is doing now; I'd rather not add a lot of complexity. If the wrapper / installer mechanism proves to demand more options I would certainly implement them, but apart from that I see the further development outside of the binary. I agree. The transfer to a simple database infrastructure seems to be reasonably easy with the existing binary - further improvements seem to have to be outside of it. Cheers, Josh Regards, OdyX -- Didier Raboud, proud Debian user. CH-1802 Corseaux did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#530788: usb-modeswitch: Broken generated udev rules for Huawei devices.
package usb-modeswitch tags 530788 fixed pending thanks Le Wednesday 27 May 2009 22:24:10 Stephen Depooter, vous avez écrit : Package: usb-modeswitch Version: 0.9.6 Severity: normal The usb-modeswitch.conf file has a few entries with extra ; characters. These are copied into the udev rules and breaks the udev rule since the ; breaks the shell command. Hi Stephen, and thanks for your bugreport. I applied your patch directly to 0.9.7-1 and it will be part of next upload. The commit can be seen here: http://git.raboud.homelinux.org/?p=usb- modeswitch.git;a=commit;h=7dc6264b256f14f1d53654887d06ae5f430b213c Thanks again ! Best regards, OdyX -- Didier Raboud, proud Debian user. CH-1802 Corseaux did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#535445: usb-modeswitch: udev rule file contains incorect entry for Sony Ericsson MD400 device
# Pending thanks to commits 78ef77fc and 517ca744 to
# git://git.debian.org/collab-maint/usb-modeswitch.git
tag 535445 pending
thanks
Le jeudi 2 juillet 2009 10:57:03 Matej Zagiba, vous avez écrit :
Package: usb-modeswitch
Version: 1.0.2-1
Severity: normal
Sony Ericsson MD400 device require special sony procedure to successfully
change mode. Current entry for Sony Ericsson MD400 does not use this
special procedure.
Current (incorrect) entry:
SUBSYSTEM==usb, SYSFS{idVendor}==0fce, SYSFS{idProduct}==d0e1,
RUN+=/usr/sbin/usb_modeswitch --default-vendor 0x0fce --default-product
0xd0e1
Correct entry:
SUBSYSTEM==usb, SYSFS{idVendor}==0fce, SYSFS{idProduct}==d0e1,
RUN+=/usr/sbin/usb_modeswitch --default-vendor 0x0fce --default-product
0xd0e1 -O 1
Note: Although in version 1.0.2 usb_modeswitch --help states:
-O, --sonyModeapply a special procedure
long option does not work in this version.
Matej Zagiba
Hi Matej, and thanks for your report,
You are completely right on both your sayings. First, the long options were
badly reported both in --help and in the manpage. Second, the script that
mangles usb_modeswitch.conf (mkrules.py) was lacking support for those single
options (--sony-mode, --sierra-mode and --huawei-mode).
I commited a fix for all those in the git repository (see the top of the
mail).
These fixes will be part of next upload.
Thanks for your report again !
Best regards,
OdyX
--
Didier Raboud, proud Debian user.
CH-1802 Corseaux
did...@raboud.com
signature.asc
Description: This is a digitally signed message part.
Bug#535520: cupt: Does not support non-spaced sources.list
Package: cupt
Version: 0.2.3
Severity: normal
Tags: patch
Hi,
# cupt update
fails if anywhere in your sources.list you have used tabs instead of spaces to
separate your various fields (deb, uri, distribution, sections).
The attached patch solves this by changing the arguments to the split function
from one or more spaces to any whitespace.
Best regards,
OdyX
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (750, 'unstable'), (700, 'testing-proposed-updates'), (700,
'testing'), (90, 'experimental'), (50, 'testing-proposed-updates'), (50,
'experimental'), (50, 'unstable'), (50, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages cupt depends on:
ii libcupt-perl 0.2.3 alternative front-end for dpkg --
ii perl 5.10.0-23 Larry Wall's Practical Extraction
cupt recommends no packages.
cupt suggests no packages.
-- no debconf information
diff --git a/Cupt/Cache.pm b/Cupt/Cache.pm
index 7edc1ed..4fa2696 100644
--- a/Cupt/Cache.pm
+++ b/Cupt/Cache.pm
@@ -668,7 +668,7 @@ sub __parse_source_list {
next if m/^\s*(?:#.*)?$/;
my %entry;
- ($entry{'type'}, $entry{'uri'}, $entry{'distribution'}, my @sections) = split / +/;
+ ($entry{'type'}, $entry{'uri'}, $entry{'distribution'}, my @sections) = split ' ';
mydie(incorrect source type at file '%s', line %u, $file, $.)
if ($entry{'type'} ne 'deb' $entry{'type'} ne 'deb-src');
signature.asc
Description: This is a digitally signed message part.
Bug#563551: #563551 still valid for you ?
Hi Frederic, usb-modeswitch and usb-modeswitch-data saw big updates in the last months, so this bug is very probably fixed for you. Can you please test with the latest versions from unstable ? Thanks in advance and best regards, OdyX -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#444197: Any progress on that packaging ?
Le Vendredi 21 Décembre 2007 00:36:35 Tobias Grimm, vous avez écrit : Hello Oliver, Olivier Berger wrote: I'd be interested in that package... any news ? replex is already packaged, but not yet uploaded to Debian. You can find the binary package for Etch or Sid here: deb http://e-tobi.net/vdr-experimental sid base deb http://e-tobi.net/vdr-experimental etch base and the source package here: deb-src http://e-tobi.net/vdr-experimental sid base ( browsable via http://www.e-tobi.net/vdr-experimental/ ) Best Regards, Tobias Hi Tobias, I'd now be in need of that package. Are you willing to maintain it in Debian ? I could help you maintain it otherwise. I saw that your packaging is GPL2, so I could easily take it and push it without much changes to Debian, but I'd rather help you do it. :-) Thanks in advance for an answer, OdyX -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#444197: Any progress on that packaging ?
Le Jeudi 11 Mars 2010 16:34:20 Didier 'OdyX' Raboud, vous avez écrit : Hi Tobias, I'd now be in need of that package. Are you willing to maintain it in Debian ? I could help you maintain it otherwise. I saw that your packaging is GPL2, so I could easily take it and push it without much changes to Debian, but I'd rather help you do it. :-) Thanks in advance for an answer, OdyX By the way, sorry for my paternalism, I didn't know (yet) you are Debian Developper. Anyway, I'd be willing to help. :-) Best regards, OdyX -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#579981: usb-modeswitch-data: dpkg-old files in /etc/usb_modeswitch.d/ not ignored
reassign 579981 usb-modeswitch 1.1.2-1 affects 579981 usb-modeswitch-data tags 579981 +pending thanks Le dimanche 2 mai 2010 22:11:07 Nils Radtke, vous avez écrit : Package: usb-modeswitch-data Version: 20100418-1 Severity: normal Salut Didier, after enabling logging in modeswitch /var/log/usb_modeswitch_2-1:1.0 tells us that /etc/usb_modeswitch.d/19d2:2000.dpkg-old is used as configuration file. On a Debian system these files should be silently ignored. # head /var/log/usb_modeswitch_2-1:1.0 (…) checking config: /etc/usb_modeswitch.d/19d2:2000.dpkg-old ! matched, now switching (running command: /usr/sbin/usb_modeswitch -I -W -c /etc/usb_modeswitch.d/19d2:2000.dpkg-old) Merci, Nils Salut Nils, [CC'ing upstream for information; Hi Josh !] Thanks for the report: you are totally right. I fixed this in the usb-modeswitch packaging repository by patching the tcl searching script. This will be uploaded really soon. http://git.debian.org/?p=collab-maint/usb- modeswitch.git;a=commitdiff;h=1de91b38fb81afb11717b238b4c6bd3710b67570 Cheers, OdyX -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#513917: win32-loader: [INTL:zh_TW] Updated Traditional Chinese (zh_TW) translation
Le lundi 2 février 2009 13:59:18 Tetralet, vous avez écrit : Package: win32-loader Severity: wishlist Hi, Attached file is updated Translation Chinese translation for win32-loader package. Please consider to apply this. Thanks. Hi Tetralet, The pot file for win32-loader got updated and rendered your translation update out-of-date. Unfortunately I can't import it directly in the d-i svn. The actual zh_TW.po can be found there: http://svn.debian.org/viewsvn/d-i/trunk/win32-loader/l10n/po/zh_TW.po Thanks in advance, cheers, OdyX -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#581143: usb-modeswitch: bashism in /bin/sh script
package usb-modeswitch tags 581143 +pending +upstream thanks Le mardi 11 mai 2010 08:15:05 Raphael Geissert, vous avez écrit : Package: usb-modeswitch Severity: important Version: 1.1.2-2 User: debian-rele...@lists.debian.org Usertags: goal-dash Hello maintainer, While performing an archive wide checkbashisms (from the 'devscripts' package) check I've found your package containing a /bin/sh script making use of a bashism. checkbashisms' output: possible bashism in ./lib/udev/usb_modeswitch line 7 (should be word 21): /usr/bin/tclsh $0 $@ /dev/null \ Not using bash (or a Debian Policy compliant shell interpreter that doesn't provide such an extra feature) as /bin/sh is likely to lead to errors or unexpected behaviours. Please be aware that dash is now the default /bin/sh. Thank you, Raphael Geissert Hi Raphael, and thanks for your bug report, (Josua, upstream, CC'ed) I just committed [1] that fixes that (patch is attached). It will be part of the next upload. Cheers, OdyX [1] http://git.debian.org/?p=collab-maint/usb-modeswitch.git;a=commitdiff;h=803337c -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com Description: Fixes bashism in usb_modeswitch.tcl Author: Didier Raboud did...@raboud.com Origin: vendor Forwarded: yes (e-mail) Bugs: http://bugs.debian.org/581143 Last-Updated: 2010-05-11 Index: usb-modeswitch.git/usb_modeswitch.tcl === --- usb-modeswitch.git.orig/usb_modeswitch.tcl 2010-05-11 09:19:05.0 +0200 +++ usb-modeswitch.git/usb_modeswitch.tcl 2010-05-11 09:19:29.0 +0200 @@ -4,7 +4,7 @@ if [ ! -e /usr/bin/tclsh ]; then \ logger -p syslog.error usb_modeswitch: tcl shell not found, install tcl package!; \ fi; \ -/usr/bin/tclsh $0 $@ /dev/null \ +/usr/bin/tclsh $0 $@ /dev/null 21 \ sleep 1; \ exit
Bug#581215: [shiboken] shiboken just segfaults or does nothing
package shiboken tags 581215 +pending thanks Le mardi 11 mai 2010 19:19:36 Adrià Cereto Massagué, vous avez écrit : Package: shiboken Version: 0.3.1-1 Severity: grave --- Please enter the report below this line. --- Calling shiboken from bash does nothing, or if you're lucky, segfaults. Hi, You are correct: this happens when generatorrunner is not installed (see main.cpp from the source to get the details). I just committed r12878 to the packaging repository [0], and it will be part of the next upload (waiting to get it built (or not) on all release architectures). Thanks for your bugreport ! Cheers, OdyX [0] http://svn.debian.org/viewsvn/python-modules?view=revrevision=12878 -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#581283: boostpythongenerator: FTBFS: cppgenerator.cpp:561: error: no match for 'operator==' in 'inc.Include::type == (Include::IncludeType)0u'
Le mercredi 12 mai 2010 09:47:43 Lucas Nussbaum, vous avez écrit : Source: boostpythongenerator Version: 0.3.3-1 Severity: serious Tags: squeeze sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20100511 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Hi, boostpythongenerator will be removed from both Squeeze and Sid when the new pyside (no more B-Ding on it) will reach the archive (its packaging has to be finished, it has to go to NEW; and get out of it). Thanks four your bugreport nevertheless ! Cheers, OdyX -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#574666: #574666 duplicate of #505517 ?
Hi Russel, Isn't your #574666 a duplicate of the previous #505517 (merged to #555985 ) ? Best regards, OdyX -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#575510: kdebluetooth: Unable to install the new experimental version...
Le Vendredi 26 Mars 2010 14:17:28 mourad, vous avez écrit : Package: kdebluetooth Version: 1:0.4~rc1-1 Severity: important Tags: experimental Hi, The experimental version of kdebluetooth is not installable because af the dependency to kbluetooth which is a virtual paquage... Please could you correct that dependency, this is the only KDE4 program to interact with bluetooth ? Thanks a lot Mourad Hi Mourad, The actual version in experimental is 1:0.4.2-2 . It might be that your mirror is outdated. Please make sure your mirror contains that version and retry. It is very certainly fixed. Best regards, OdyX -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#575510: kdebluetooth: Unable to install the new experimental version...
newbeewan wrote: Le 26/03/2010 14:27, Didier 'OdyX' Raboud a écrit : Hi Mourad, The actual version in experimental is 1:0.4.2-2 . It might be that your mirror is outdated. Please make sure your mirror contains that version and retry. It is very certainly fixed. Best regards, OdyX I effectively trying to install 1:0.4.2-2 which is the version I can't install to upgrade my current version (I'm using 1:0.4~rc1-1). my report is concerning the actual version in experimental (1:0.4.2-2). Regards Mourad Hi again, what do those commands output for you ? $ LANG=C apt-cache policy kdebluetooth $ LANG=C apt-cache policy kbluetooth $ LANG=C aptitude -texperimental show kdebluetooth $ LANG=C aptitude -texperimental show kbluetooth Regards, OdyX -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#575510: kdebluetooth: Unable to install the new experimental version...
newbeewan wrote: Here the result of those commands : $ LANG=C apt-cache policy kdebluetooth kdebluetooth: Installed: 1:0.4~rc1- (…) $ LANG=C apt-cache policy kbluetooth kbluetooth: Installed: (none) Candidate: (none) (…) $ LANG=C aptitude -texperimental show kdebluetooth (…) $ LANG=C aptitude -texperimental show kbluetooth Unable to find an archive experimental for the package kbluetooth Package: kbluetooth State: not a real package Regards Mourad Oh. You are just hit by a standard experimental issue: the package is not built for your architecture (i386, right ?). https://buildd.debian.org/status/package.php?p=kbluetoothsuite=experimental I'll see what can be done to solve that, but this might be low priority as kbluetooth is supposed to be uploaded to unstable as soon as KDE 4.4 reaches unstable too. Best regards, OdyX -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#563551: usb-modeswitch: Disconnect the Huawei E220 3G USB modem
reassign 563551 linux-2.6 2.6.31-1
retitle 563551 Linux resets Huawei E220 3G USB modem as soon as the storage is
accessed
thanks
Le Vendredi 26 Mars 2010 16:54:28 Frédéric Massot, vous avez écrit :
Hi,
I tested the version 009-3 of package devicekit-disks.
There is no longer the message segfault for devkit-disks-daemon, but I
was unable to connect to the network.
The only thing I changed was the update of disks-daemon from 009-2 to
009-3. There is an kernel error for the pseudo CDROM, I'll test the
kernel 2.6.33.
Below the logs.
Regards.
Hi all,
from the bug log, it seems to me that there is no bug in usb-modeswitch{,-data},
but rather in linux-2.6, to which I am reassigning this bug.
Feel free to disagree ! ;-)
Best regards,
OdyX
--
Didier Raboud, proud Debian Maintainer (DM).
CH-1020 Renens
did...@raboud.com
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533892: #533892 still valid for you ?
Hi Martin, Usb-modeswitch and usb-modeswitch-data saw big updates in the last months, so it might very well be fixed in the latest versions. Did you gain access to your hardware to test this ? Best regards, OdyX -- Didier Raboud, proud Debian user. CH-1020 Renens did...@raboud.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#560023: #560023 still valid for you ?
Hi Werner, usb-modeswitch and usb-modeswitch-data saw big updates in the last months, so this bug is very probably fixed for you. Can you please test with the latest versions from unstable ? Thanks in advance and best regards, OdyX -- Didier Raboud, proud Debian user. CH-1020 Renens did...@raboud.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#577460: udev: Please remove option modeswitching code
Le Dimanche 11 Avril 2010 22:57:01 Marco d'Itri, vous avez écrit : On Apr 11, Didier Raboud did...@raboud.com wrote: Squeeze should really ship a udev that incorporates the upstream commit 4dd9b291354e76f34b0d6d7b5c3b28d03a624418 (post-151). The freeze is still not close, what about you wait for the next upload? In private discussion with Betavine and usb_modeswitch upstreams, it appears rather clearly that usb-modeswitch is now the tool supposed to handle the switching of those flip-flop devices: 61-mobile-action.rules conflicts with usb-modeswitch. Guess what? I had similar discussions as well. Then that's great! I intended this bugreport as notifier-reminder for you: your answer shows me that you are informed and aware of the issue, which is all I wanted to make sure of. As I can't know when udev's upstream will push new version tarballs [but you most probably know], I would have preferred to see this bug closed with the new upstream upload of udev, but I'm not in the mood for BTS ping-pong and it's your package afterall. Cheers, OdyX -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#577853: usb-modeswitch-data: Unusual chars in filenames
package usb-modeswitch-data tags 577853 +upstream severity 577853 whishlist thanks Le jeudi 15 avril 2010 09:47:22 Frank Lin PIAT, vous avez écrit : Package: usb-modeswitch-data Version: 20100322-2 Severity: normal Hello, The package usb-modeswitch-data provide the file: /etc/usb_modeswitch.d/16d8:6803:? The question-mark ? symbol is unusual on unix filesystem, and it is almost guaranteed that it is going to break various script (both provided by Debian and local admin ones). Also, I suggest to replace the column too. Thanks, Franklin Hi Franklin, and thanks for your bugreport, Although I recognise that : and ? symbols are somehow special on Unix filesystems, I don't see this as a problem, because usb-modeswitch just works with those files. Thus downgrading severity to wishlist (I am of course open to discussion). Furthermore, this is clearly an upstream issue which should be fixed there, to ensure cross-distribution compatibility, thus tagging as such. I will make sure upstream (CCed) is aware of the issue and eventually commenting on the bugreport. Is such an action schedule (non-action schedule…) fine for you? Cheers, OdyX -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#578024: usb-modeswitch-data: Avoid splitting /etc/usb_modeswitch.d/ to save space
package usb-modeswitch-data tags 578024 +upstream thanks Le vendredi 16 avril 2010 09:22:57 Frank Lin PIAT, vous avez écrit : Hello, Splitting the file in /etc/usb_modeswitch.d/ increase the _disk_ pace usage by 10 folds (400K instead of 28K). IMHO, /etc/foo.d/ directory for configuration file is useful when other packages ship files in the $foo.d/ directory. Or when a packages receives a lot of updates (through volatile...), so the user isn't asked to merge configuration file. Couldn't all the files in the .d directory be merged in a single file? (that file could be /etc/usb_modeswitch.d/upstream) Thanks, Franklin % du /etc/usb_modeswitch.d/ -h 400K /etc/usb_modeswitch.d/ % cat /etc/usb_modeswitch.d/* /tmp/all % du -h /tmp/al 28K /tmp/a Hi Franklin, and thanks again for your bugreport ! (Upstream CCed again) Historically, usb-modeswitch was shipped with one single file containing all the configurations and this file went splitted in multiple files to ease conffile transitions, additions and update. I still think that this model is very convenient for working out new devices, etc. Now I very much understand this space issue. Furthermore, providing so many configuration files somehow bloats the /etc space for things that are probably more of /usr scope. So a reasonable solution IMHO (and again, probably to be done upstream) would be to modify both usb-modeswitch and u-m-data for the following (to be done separately probably): * use configuration from two different places: /usr/share/usb-modeswitch-data would contain the upstream stable configuration files (or even all) and /etc/usb_modeswitch.d/ would contain the still to be modified (_:_:? e.g.) and the user provided ones. The /etc/* would take precedence over the /usr/* ones. * enhance usb-modeswitch to be able to understand multiple configurations per file. This would allow to ship one upstream blob in /usr/share and keep working with separate files overrides in /etc/* Josh: What do you think of all this ? I am somehow puzzled to propose yet-a-new paradigm change, but the path to technical perfection is sometimes zigzag. :-) Frank: Does this sound sensible to you ? Cheers, OdyX -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#569389: win32-loader: FTBFS: plugins/cpuid/plugin.c:18:21: error: windows.h: No such file or directory
package win32-loader tags 569389 +patch thanks Le jeudi 11 février 2010 19:48:03 Lucas Nussbaum, vous avez écrit : Source: win32-loader Version: 0.6.13 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20100211 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[1]: Entering directory `/build/user-win32-loader_0.6.13-amd64-wy87Ht/win32-loader-0.6.13' i586-mingw32msvc-gcc -Os plugins/cpuid/cpuid.c plugins/cpuid/plugin.c -Wl,--file-alignment,512 -Werror -D_WIN32_WINNT=0x0500 -L/usr/i586-mingw32msvc/lib/nsis -lpluginapi -shared -o plugins/cpuid/test64.dll plugins/cpuid/plugin.c:18:21: error: windows.h: No such file or directory In file included from The full build log is available from: http://people.debian.org/~lucas/logs/2010/02/11/win32-loader_0.6.13_lsid64 .buildlog Hi, I managed to get this RC bug fixed (not a big deal). The debdiff is attached and a compiled form is downloadable there: http://alioth.debian.org/~odyx-guest/debian/unstable/win32-loader_0.6.13+nmu1.dsc Please get this RC bug fixed: it keeps win32-loader out of squeeze. By the way, the package is in some need of love (standards, lintian, [cdbs vs dh], patches merging, etc.), which I'd be willing to give. debian-boot and Robert Millan: what are your opinions ? Cheers, OdyX -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com diff -Nru win32-loader-0.6.13/debian/changelog win32-loader-0.6.13+nmu1/debian/changelog --- win32-loader-0.6.13/debian/changelog 2009-11-30 16:39:17.0 +0100 +++ win32-loader-0.6.13+nmu1/debian/changelog 2010-04-20 16:34:21.0 +0200 @@ -1,3 +1,11 @@ +win32-loader (0.6.13+nmu1) unstable; urgency=high + + * Non-maintainer upload. + * Add mingw32-runtime to Build-Depends (Closes: #569389) +- Urgency high for RC bug. + + -- Didier Raboud did...@raboud.com Tue, 20 Apr 2010 16:34:20 +0200 + win32-loader (0.6.13) unstable; urgency=low [ Robert Millan ] diff -Nru win32-loader-0.6.13/debian/control win32-loader-0.6.13+nmu1/debian/control --- win32-loader-0.6.13/debian/control 2009-11-30 16:14:05.0 +0100 +++ win32-loader-0.6.13+nmu1/debian/control 2010-04-20 16:27:07.0 +0200 @@ -7,7 +7,7 @@ cdbs, debhelper (= 5), nsis (= 2.25), - gcc-mingw32, + gcc-mingw32, mingw32-runtime, gettext, grub-pc (= 1.97+20091130-1), loadlin (= 1.6c.really1.6c.nobin-1~), signature.asc Description: This is a digitally signed message part.
Bug#578626: /etc/usb_modeswitch.setup missing
package usb-modeswitch tags 578626 +wontfix thanks Le mercredi 21 avril 2010 13:17:14 Julien Danjou, vous avez écrit : Package: usb-modeswitch Version: 1.1.2-1 Severity: important It seems that the .setup file is missing in /etc. Specifing -c /etc/usb_modeswitch.conf stills to make it works, but well, I doubt it's specified in udev calls and therefore not sure it still works. Hi Julien, /etc/usb_modeswitch.setup is not provided on purpose and here's why : * /e/usb_modeswitch.setup is a one-file version of what usb-modeswitch-data provides in /etc/usb_modeswitch.d/ * It's existence is mainly historical, back in the days when usb-modeswitch was shipped with the switching commands. * The switching commands are now provided by usb-modeswitch-data, which can happen to be more up2date than usb-modeswitch itself (that's the point of the split), there is little meaning to provide usb-modeswitch's setup. * the usb-modeswitch + usb-modeswitch-data combination is supposedly working out-of-the-box, thanks to udev rules and wrappers. So you should really not need /etc/usb_modeswitch.setup at all: either your device's commands is shipped by usb-modeswitch-data in /etc/usb_modeswitch.d and it should just work when plugged in; or it isn't and to get it, you should create one single entry in /etc/usb_modeswitch.d and test it with usb_modeswitch, manually. Is that answer (and the +wontfix tag) OK with you ? I am of course open to discussion. Cheers, OdyX -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#559533: [buildd-tools-devel] Bug#559533: sbuild: does not support new source formats
package sbuild
tags 559533 +patch
thanks
Hi Roger and Andres,
I got hit by the same bug, while trying to compile a 3.0 (quilt) package. I
propose the attached simple patch, that just works for me.
Best regards,
OdyX
--
Didier Raboud, proud Debian Maintainer (DM).
CH-1020 Renens
did...@raboud.com
commit 06fe18978dce8ee4f9c8759f3ad5dbfbb1efdaa2
Author: Didier Raboud did...@raboud.com
Date: Wed Apr 21 15:43:33 2010 +0200
Allows .bz2 files in .dsc's
This supposedly fixes #559533.
diff --git a/lib/Sbuild/Build.pm b/lib/Sbuild/Build.pm
index 2cb5b4a..15e68e8 100644
--- a/lib/Sbuild/Build.pm
+++ b/lib/Sbuild/Build.pm
@@ -1935,7 +1935,7 @@ sub dsc_files {
# We're only interested in the name of the files in the Files field.
my $entry = ${$stanza}{'Files'};
-@files = grep(/\.tar\.gz$|\.diff\.gz$/, split(/\s/, $entry));
+@files = grep(/\.tar\.(gz|bz2)$|\.diff\.gz$/, split(/\s/, $entry));
return @files;
}
signature.asc
Description: This is a digitally signed message part.
Bug#578626: /etc/usb_modeswitch.setup missing
Le mercredi 21 avril 2010 14:29:28 Julien Danjou, vous avez écrit :
Didier 'OdyX' Raboud did...@raboud.com writes:
* /e/usb_modeswitch.setup is a one-file version of what
usb-modeswitch-data provides in /etc/usb_modeswitch.d/
* It's existence is mainly historical, back in the days when
usb-modeswitch was shipped with the switching commands.
Ok, I'm new so I did not know that. However, usb_modeswitch binary seems
to look for it, that seems wrong, isn't it?
Hmm… That's true. It is a fallback on case no configuration is pushed to it by
the udev scripts (see below).
* the usb-modeswitch + usb-modeswitch-data combination is supposedly
working out-of-the-box, thanks to udev rules and wrappers.
That's not my case currently, even if my device USB id are included in
the files provided by -data.
This is why I tried to investigate a little but and discovered that
calling usb_modeswitch fails because of that missing file.
And when I read:
ATTRS{idVendor}==19d2, ATTRS{idProduct}==2000, RUN+=usb_modeswitch
'%b/%k' (my device)
I was wondering if it really runs usb_modeswitch something/something,
because I'm not sure it'd works.
You are right that it wouldn't work; but there is a slight subtility in this
udev rules file: the usb_modeswitch called from the udev rules file is the
/lib/udev/usb_modeswitch [provided by usb-modeswitch]. This one is a wrapper
around /usr/sbin/usb_modeswtich that finds and reads the correct configuration
file.
So if you want to investigate your device, you should either build yourself a
small /etc/usb_modeswitch.d/19d2:2000 -like and run /usr/sbin/usb_modeswitch -c
~/yourfile for testing purposes. Then you could try to put it with a sensible
name under /etc/usb_modeswitch.d/.
Is it clearer now ?
Cheers,
OdyX
--
Didier Raboud, proud Debian Maintainer (DM).
CH-1020 Renens
did...@raboud.com
signature.asc
Description: This is a digitally signed message part.
Bug#464233: #464233 : Misunderstanding
package win32-loader tags 464233 +pending thanks Hi, the win32-loader.exe shipped by the win32-loader package is the one intended to be on the CDs. The next version will ship a win32-loader-standalone.exe, intended to be used from a network. Cheers, OdyX -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#578114: #578114: kdebluetooth ceased recognising dongle after upgrade
Hi envite, what Debian release are you using that you still are using KDE3.5 ? Squeeze will ship with kbluetooth 1:0.4.2-2, actually in experimental. Could you try this version ? Thanks in advance, cheers, OdyX -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#533452: foomatic-db-engine: FTBFS: Could not run foomatic-combo-xml/foomatic-perl-data!
package foomatic-db-engine
tags 533452 +patch
thanks
Le dimanche 21 février 2010 02:20:01 Slávek Banko, vous avez écrit :
Here is small workaround to fix this bug.
*** debian/rules.orig 2010-02-21 02:05:22.0 +0100
--- debian/rules2010-02-21 02:06:20.0 +0100
***
*** 80,86
--- 80,90
dh_prep
dh_installdirs
+ mv ./lib/Foomatic/Defaults.pm ./lib/Foomatic/Defaults.pm-orig
+ sed s|bindir = '/usr/bin';|bindir = '.';|
./lib/Foomatic/Defaults.pm ./lib/Foomatic/Defaults.pm-orig
PERL5LIB='$(CURDIR)/lib' python ./debian/build_ppds
$(CURDIR)/debian/foomatic-filters-ppds/usr/share/ppd/openprinting.org-gs
+ rm -f ./lib/Foomatic/Defaults.pm
+ mv ./lib/Foomatic/Defaults.pm-orig ./lib/Foomatic/Defaults.pm
dpkg-query -W -f 'ppds:Version=$${version}\n' foomatic-db
debian/foomatic-filters-ppds.substvars
dpkg-query -W -f 'gp:Version=$${version}\n' foomatic-db-gutenprint
debian/foomatic-filters-ppds.substvars
Hi Chris, hi Slávek,
I prepared an NMU to solve this RC bug, with Slávek's patch. debdiff is
attached. Chris: if you don't have time, I'll try to find somebody to upload
this as a regular NMU.
The dsc is there:
http://alioth.debian.org/~odyx-guest/debian/unstable/foomatic-db-
engine_4.0-20090509-2.1.dsc
I launched a complete build, but it takes time. I'll see with either Chris or
the NMUer if it is actually needed.
By the way, I might be interested in updating this package to latest upstream,
merge some bugs and merge back some Ubuntu patches. Chris: would you be
interested in some help (also for other printing-related packages) ?
Cheers,
OdyX
--
Didier Raboud, proud Debian Maintainer (DM).
CH-1020 Renens
did...@raboud.com
diff -u foomatic-db-engine-4.0-20090509/debian/changelog foomatic-db-engine-4.0-20090509/debian/changelog
--- foomatic-db-engine-4.0-20090509/debian/changelog
+++ foomatic-db-engine-4.0-20090509/debian/changelog
@@ -1,3 +1,11 @@
+foomatic-db-engine (4.0-20090509-2.1) unstable; urgency=high
+
+ * Non-maintainer upload.
+ * Use the built binaries to build the arch-indep ppds. Closes: #533452
+- Urgency high for RC bugfix. Thanks to Slávek Banko for the patch!
+
+ -- Didier Raboud did...@raboud.com Thu, 22 Apr 2010 13:35:26 +0200
+
foomatic-db-engine (4.0-20090509-2) unstable; urgency=low
* Fix build outside of chroot. (Closes: #532977)
diff -u foomatic-db-engine-4.0-20090509/debian/rules foomatic-db-engine-4.0-20090509/debian/rules
--- foomatic-db-engine-4.0-20090509/debian/rules
+++ foomatic-db-engine-4.0-20090509/debian/rules
@@ -80,7 +80,14 @@
dh_prep
dh_installdirs
+ # Use the binaries we just built - bug #533452
+ mv ./lib/Foomatic/Defaults.pm ./lib/Foomatic/Defaults.pm-orig
+ sed s|bindir = '/usr/bin';|bindir = '.';| ./lib/Foomatic/Defaults.pm ./lib/Foomatic/Defaults.pm-orig
+
PERL5LIB='$(CURDIR)/lib' python ./debian/build_ppds $(CURDIR)/debian/foomatic-filters-ppds/usr/share/ppd/openprinting.org-gs
+
+ # Restore
+ mv ./lib/Foomatic/Defaults.pm-orig ./lib/Foomatic/Defaults.pm
dpkg-query -W -f 'ppds:Version=$${version}\n' foomatic-db debian/foomatic-filters-ppds.substvars
dpkg-query -W -f 'gp:Version=$${version}\n' foomatic-db-gutenprint debian/foomatic-filters-ppds.substvars
signature.asc
Description: This is a digitally signed message part.
Bug#533452: foomatic-db-engine: FTBFS: Could not run foomatic-combo-xml/foomatic-perl-data!
Le jeudi 22 avril 2010 15:50:11 Didier 'OdyX' Raboud, vous avez écrit : I launched a complete build, but it takes time. I'll see with either Chris or the NMUer if it is actually needed. It got built: http://alioth.debian.org/~odyx-guest/debian/unstable/foomatic-db-engine_4.0-20090509-2.1_amd64.changes Cheers, OdyX -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#578858: [Fingerforce-devel] Bug#578858: libpam-fprint: Doesn't work with kdm
Le vendredi 23 avril 2010 14:57:08 Dererk, vous avez écrit : Hello Odyx, Can you check that your problem is not related to this Bug Report http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=469059 ? Greetings, Dererk Hi Dererk, I don't think so, because it worked in the past with KDE4's kdm. If I remember correctly, it was back when we (with experimental) had to enable it per hand. Cheers, OdyX -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533452: RFS: NMU for foomatic-db-engine RC #533452 - FTBFS: Could not run foomatic-combo-xml/foomatic-perl-data!
Hi mentors, I prepared an NMU for foomatic-db-engine's RC: #533452. The dsc's there: http://alioth.debian.org/~odyx-guest/debian/unstable/foomatic-db- engine_4.0-20090509-2.1.dsc There is also a built version there: http://alioth.debian.org/~odyx-guest/debian/unstable/foomatic-db- engine_4.0-20090509-2.1_amd64.changes It'd be great if someone could upload this. Chris I'm still interested in co-maintaining this package with you. Cheers, OdyX Le jeudi 22 avril 2010 15:50:11 Didier 'OdyX' Raboud, vous avez écrit : Hi Chris, hi Slávek, I prepared an NMU to solve this RC bug, with Slávek's patch. debdiff is attached. Chris: if you don't have time, I'll try to find somebody to upload this as a regular NMU. The dsc is there: http://alioth.debian.org/~odyx-guest/debian/unstable/foomatic-db- engine_4.0-20090509-2.1.dsc I launched a complete build, but it takes time. I'll see with either Chris or the NMUer if it is actually needed. By the way, I might be interested in updating this package to latest upstream, merge some bugs and merge back some Ubuntu patches. Chris: would you be interested in some help (also for other printing-related packages) ? Cheers, OdyX -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#579533: cpio-win32: cpio.exe changed output format, which breaks initrd.gz editing
Le mercredi 28 avril 2010 19:41:13 Clint Adams, vous avez écrit : On Wed, Apr 28, 2010 at 03:04:39PM +0200, Didier Raboud wrote: So it seems that this issue is win32-specific. Probably I made a mistake when forward-porting the win32 patches. Robert Millan seems to be out of the picture, so I'm not sure who else might want to pick this up. Hrm… I'm nowhere near familiar to win32 nor with C, but I'm interested in getting this fixed: count me as responsible for this bug: I'll hunt it down seriously. Not just now, but seriously. -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#579533: cpio-win32: cpio.exe changed output format, which breaks initrd.gz editing
Le mercredi 28 avril 2010 20:29:22 Didier 'OdyX' Raboud, vous avez écrit : Hrm… I'm nowhere near familiar to win32 nor with C, but I'm interested in getting this fixed: count me as responsible for this bug: I'll hunt it down seriously. Not just now, but seriously. Little update (from my rapid analysis): it seems that the UNIXes \n which were written as \n by cpio-win32_2.9-15 went then written as \r\n by cpio- win32_2.9.90-2. My example file had 16 lines (so 16 \n ), so that's where the 16 bytes diff came from. Now it remains to see where those \r might come from. (I just saw your update…) -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#579533: cpio-win32: cpio.exe changed output format, which breaks initrd.gz editing
tags 579533 +patch thanks Le jeudi 29 avril 2010 17:10:29 Clint Adams, vous avez écrit : On Thu, Apr 29, 2010 at 01:58:25PM +0200, Didier 'OdyX' Raboud wrote: Little update (from my rapid analysis): it seems that the UNIXes \n which were written as \n by cpio-win32_2.9-15 went then written as \r\n by cpio- win32_2.9.90-2. My example file had 16 lines (so 16 \n ), so that's where the 16 bytes diff came from. Now it remains to see where those \r might come from. (I just saw your update…) SET_BINARY_MODE() is likely your culprit. Hi again, the attached patch solves this: in fact it is just Robert's fix for #464172 that wasn't applied anymore for some reason. [By the way, I had hard time to find what was from upstream and what was part of the patches; Robert's had been lost sometime back in an upstream upgrade. Why not using quilt patches (as you already are using 3.0 (quilt))? Anyway: I can quilt'ify the patches over cpio if you want: just ask. ] Cheers, OdyX -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com Description: Fix corrupted output in -win32 build Author: Robert Millan r...@aybabtu and Didier Raboud did...@raboud.com Origin: vendor Bugs: http://bugs.debian.org/579533 http://bugs.debian.org/464172 Last-Update: 2010-04-29 Index: cpio/gnu/fcntl.in.h === --- cpio.orig/gnu/fcntl.in.h 2010-04-29 18:29:01.0 +0200 +++ cpio/gnu/fcntl.in.h 2010-04-29 18:29:31.0 +0200 @@ -234,7 +234,10 @@ # undef O_TEXT #endif -#ifndef O_BINARY +#ifdef O_BINARY +# define SET_BINARY_MODE(arc) setmode(arc, O_BINARY) +#else +# define SET_BINARY_MODE(arc) # define O_BINARY 0 # define O_TEXT 0 #endif Index: cpio/lib/system.h === --- cpio.orig/lib/system.h 2010-04-29 18:29:01.0 +0200 +++ cpio/lib/system.h 2010-04-29 18:29:09.0 +0200 @@ -109,9 +109,6 @@ # define O_TRUNC 32 /* truncate file on open */ #endif -#ifndef O_BINARY -# define O_BINARY 0 -#endif #ifndef O_DIRECTORY # define O_DIRECTORY 0 #endif @@ -462,13 +459,11 @@ #if MSDOS # include process.h -# define SET_BINARY_MODE(arc) setmode(arc, O_BINARY) # define ERRNO_IS_EACCES errno == EACCES # define mkdir(file, mode) (mkdir) (file) # define TTY_NAME con # define sys_reset_uid_gid() #else -# define SET_BINARY_MODE(arc) # define ERRNO_IS_EACCES 0 # define TTY_NAME /dev/tty # define sys_reset_uid_gid() \ signature.asc Description: This is a digitally signed message part.
Bug#573546: kbluetooth: package is empty
# Pending by http://git.debian.org/?p=pkg-kde/kde-extras/kdebluetooth4.git;a=commitdiff;h=b2e5656fde5ca0b64f1b32397f499ffb471fcf14 tag 573546 +pending thanks Le Vendredi 12 Mars 2010 10:12:56 Marcus Better, vous avez écrit : Package: kbluetooth Version: 1:0.4.2-1 Severity: serious Very little functionality in this release... Hi, Thanks for your report. It is fixed in the packaging repository, waiting for an upload. Best regards, OdyX -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#444197: Any progress on that packaging ?
Le Jeudi 11 Mars 2010 20:16:10, vous avez écrit : Hi! Didier 'OdyX' Raboud wrote: I'd now be in need of that package. Do you need it as a dependency for another package or as a standalone tool? Hi Tobias, My use case is rather simple: I use vdr on a no-screen server and I schedule recordings using Live (:8008). I want to re-encode those recordings using ffmpeg (from main). So I thought that for it to work, it would be logical to first merge the various *.vdr TS files into one PS file, but I then noticed that replex can't keep the multiple audio tracks. So I was about to use replex to demux the various media tracks into individual files, which I could then encode separately before merging them into a single matroska file for example. But I am maybe mistaken and replex is not the correct tool to do what I want. What do you think ? Are you willing to maintain it in Debian ? I could help you maintain it otherwise. The package itself requires nearly no maintenance. In order to upload it, I would just have to change the standards version, convert debian/rules to CDBS, update debian/copyright and add a README.source. There hasn't been a new upstream release for years and I don't expect any new upstream release in the future. The reason I haven't uploaded it yet, simply is, that there wasn't any need for such a tool in Debian or Ubuntu yet. But if you have another packge that requires replex, I would happily upload it and set the DM-field for you. bye, Tobias As a new vdr-* user, I might be interested in joining the vdr packaging team for simple tools like that one. Best regards, OdyX -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com signature.asc Description: This is a digitally signed message part.
Bug#548419: #548419: MySQL package split patch
tag 548419 +patch
thanks
Hi all,
I managed to prepare a split of the mysql-server-5.1 package. The patch is
attached.
It uses the same naming scheme and file repartition as Ubuntu. I also patched
the descriptions to fit tightly to what the packages really contain and I
targeted that to experimental. I tried to prepare a minimal-impact patch.
This patch is rather important for KDE, because it will allow it to only depend
on mysql-server-core and avoid forcing people to run a system database.
Please
comment !
Best regards,
OdyX
--
Didier Raboud, proud Debian Maintainer (DM).
CH-1020 Renens
did...@raboud.com
Index: debian/changelog
===
--- debian/changelog (revision 1848)
+++ debian/changelog (working copy)
@@ -1,3 +1,16 @@
+mysql-dfsg-5.1 (5.1.44-3.1) experimental; urgency=low
+
+ * Non-maintainer upload.
+ * Add mysql-server-core-5.1 package, containing the package and its manpage,
+to let packages like akonadi use the mysql binary without using system
+databases (Closes: #548419).
+Affects:
+- debian/control
+- debian/mysql-server-5.1.{files,dirs}
+- debian/mysql-server-core-5.1.{files,dirs}
+
+ -- Didier Raboud did...@raboud.com Mon, 08 Mar 2010 19:29:36 +0100
+
mysql-dfsg-5.1 (5.1.44-3) unstable; urgency=low
* Add patch that reinstates the reloading of character set data when a
Index: debian/control
===
--- debian/control (revision 1848)
+++ debian/control (working copy)
@@ -91,22 +91,37 @@
This package includes the client binaries and the additional tools
innotop and mysqlreport.
+Package: mysql-server-core-5.1
+Architecture: any
+Depends: ${shlibs:Depends}, ${misc:Depends}
+Conflicts: mysql-server-5.1 ( 5.1.44-3.1), mysql-server-5.0 ( 5.1.44-3.1)
+Provides: mysql-server-core, mysql-server-core-5.0
+Description: MySQL database server binaries
+ MySQL is a fast, stable and true multi-user, multi-threaded SQL database
+ server. SQL (Structured Query Language) is the most popular database query
+ language in the world. The main goals of MySQL are speed, robustness and
+ ease of use.
+ .
+ This package includes the server binaries but doesn't contain all the
+ infrastructure needed to setup system databases.
+
Package: mysql-server-5.1
Architecture: any
Suggests: tinyca
Recommends: mailx, libhtml-template-perl
Pre-Depends: mysql-common (= ${source:Version}), adduser (= 3.40), debconf
-Depends: mysql-client-5.1 (= ${source:Version}), libdbi-perl, perl (= 5.6), ${shlibs:Depends}, ${misc:Depends}, psmisc, passwd, lsb-base (= 3.0-10)
+Depends: mysql-client-5.1 (= ${source:Version}), libdbi-perl, perl (= 5.6), ${shlibs:Depends}, ${misc:Depends}, psmisc, passwd, lsb-base (= 3.0-10), mysql-server-core-5.1 (= ${binary:Version})
Conflicts: mysql-server ( ${source:Version}), mysql-server-4.1
Provides: mysql-server, virtual-mysql-server, mysql-server-5.0
Replaces: mysql-server ( ${source:Version}), mysql-server-5.0, libmysqlclient-dev (= 5.1.41-1)
-Description: MySQL database server binaries
+Description: MySQL database server binaries and system database setup
MySQL is a fast, stable and true multi-user, multi-threaded SQL database
server. SQL (Structured Query Language) is the most popular database query
language in the world. The main goals of MySQL are speed, robustness and
ease of use.
.
- This package includes the server binaries.
+ This package contains all the infrastructure needed to setup system
+ databases.
Package: mysql-server
Section: database
Index: debian/mysql-server-5.1.files
===
--- debian/mysql-server-5.1.files (revision 1848)
+++ debian/mysql-server-5.1.files (working copy)
@@ -24,7 +24,6 @@
usr/bin/replace
usr/bin/resolve_stack_dump
usr/bin/resolveip
-usr/sbin/mysqld
usr/share/doc/mysql-server-5.1/
usr/share/lintian/overrides/mysql-server-5.1
usr/share/man/man1/msql2mysql.1
@@ -51,5 +50,16 @@
usr/share/man/man1/innochecksum.1
usr/share/man/man1/mysqltest_embedded.1
usr/share/man/man1/mysql_tzinfo_to_sql.1
-usr/share/man/man8/mysqld.8
-usr/share/mysql/
+usr/share/mysql/debian-start.inc.sh
+usr/share/mysql/echo_stderr
+usr/share/mysql/errmsg.txt
+usr/share/mysql/fill_help_tables.sql
+usr/share/mysql/mysqld_multi.server
+usr/share/mysql/mysql_fix_privilege_tables.sql
+usr/share/mysql/mysql_system_tables.sql
+usr/share/mysql/mysql_system_tables_data.sql
+usr/share/mysql/mysql_test_data_timezone.sql
+usr/share/mysql/config.huge.ini
+usr/share/mysql/config.medium.ini
+usr/share/mysql/config.small.ini
+usr/share/mysql/ndb-config-2-node.ini
Index: debian/mysql-server-core-5.1.files
===
--- debian/mysql-server-core-5.1.files (revision 0)
+++ debian/mysql-server-core-5.1.files (revision 0)
@@ -0,0
Bug#574270: usb-modeswitch-data: MF636 not working after upgrade
Le Mercredi 17 Mars 2010 10:32:45 l...@think-future.de, vous avez écrit : Package: usb-modeswitch-data Version: 20100221-1 Severity: important Reporting this here for the draisberghof bb requires registration. It's just a bad thing to have to get registrated with dozens of boards, wikis, trac or whatever and keeping track of software. I seek to contribute but not waste effort and energy in useless regs and get humbled by 1k more of spam messages. Hi, I understand that. No problem. We'll handle your bugreport here. Having that said, here's the report: Device: - Model: MC503HSA - Type: MF636 After an usb-modeswitch-data update the modem was unusable as usb-modeswitch-data matched idVendor=19d2, idProduct=0037 in /etc/usb_modeswitch.d/19d2:2000, no ttyUSB? devices being created. I don't entirely get your bugreport… did it work with previous versions of usb- modeswitch-data ? What have you done to make your device work ? Did you delete /etc/usb_modeswitch.d/19d2\:2000 ? The changelog contains several changes about those devices (that seem to be the most problematic one): usb-modeswitch-data (20100221-1) unstable; urgency=low * New upstream release. + New devices (…) [19d2:2000] ZTE MF626 and others usb-modeswitch-data (20100203-1) unstable; urgency=low * New upstream release. × Devices updates [19d2:2000] Re-arrange target product lists Thanks in advance for your answers, OdyX -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
