Bug#661127: [Pkg-cups-devel] Bug#661127: cups-filters: please build depend on libfontconfig1-dev
Hello Pino, Pino Toscano [2012-02-24 12:51 +0100]: Unfortunately this change breaks, other than cups-filters, 5 more sources (all reported yesterday and today by me); given the so close timing with your Ubuntu release, I suggest you adding back the libfontconfig1-dev dependency in libpoppler-dev in Ubuntu. Regarding Debian, I will put it back too when starting the poppler 0.18 transition and uploading it to unstable, in case not all of the reported bugs have been fixed yet. Thanks for pointing this out, this makes sense. I uploaded a new version to put it back again (will land after beta-1 freeze). Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#661430: bugfix:octave-epstk: invisible axis ruins plot line
Package: octave-epstk Version: 2.3-2 Severity: normal There was a clipping bug in eplot.m. The bugfix is in the attachment. %%NAME %% eplot - make linear plot %% %%SYNOPSIS %% eplot ([xData,[yData,[legendText,[dash,[color[,width]]) %% %%PARAMETER(S) %% xData vector of x-data %% or matrix(2xn) of x0,x1-data to plot lines %% yData vector of y-data %% or matrix(2xn) of y0,y1-data to plot lines %% legendText text of legend, if empty string then no legend %% dash if a scalar and %% dash=0 solid plot line, %% dash0 dash length %% dash0 fill plot line with color %%default: dash=eLineDash %%if a vector with size 1xn, then dash describes %% a dash combination [space lineLength1 lineLength2 ...] %%if a string then dash is a name of symbol %%if a matrix and color=-1 %% dash is the image of plot %% and filled with RGB values %% (value=R*2^16+G*2^8+B and R,G,B are integer of 0:255) %%if a matrix and color is a colormap %% dash is the image of plot %% and filled with indices of colormap %%if a string dash is filename of a JPEG-file %% color if dash=0 vector of plot color ([r g b]) %%if dash0 vector of background color %%if dash a matrix then colormap of image or -1 %%default: dash=eLineColor %% width width of plot line %% %% Important: eplot without parameters closes the current plot explicit. %%it's useful for several plot on one page %% %%GLOBAL PARAMETER(S) %% ePlotAreaPos %% ePlotAreaWidth %% ePlotAreaHeight %% eXAxisSouthScale %% eYAxisWestScale %% ePlotAreaXValueStart %% ePlotAreaXValueEnd %% ePlotAreaYValueStart %% ePlotAreaYValueEnd %% ePlotLineInterpolation %% ePlotLineWidth %% ePlotLineColor; %% ePlotLineDash; %% ePlotLegendPos; %% ePlotLegendTextFont %% ePlotLegendTextColor %% ePlotLegendFontSize %% ePlotLegendDistance %% eAxesColor % written by stefan.muel...@fhr.fraunhofer.de (C) 2010 function eplot(xData,yData,legendText,dash,color,width) if nargin6 eusage('eplot([xData,[yData,[legendText,[dash,[color[,width]])'); end eglobpar; if (nargin==0) %finish plotting % write title etitle; %value range if eXAxisSouthScale(1)~=eXAxisSouthScale(3) %fix scale ePlotAreaXValueStart=eXAxisSouthScale(1); ePlotAreaXValueEnd=eXAxisSouthScale(3); else if eXAxisSouthScaleType==2 if (ePlotAreaXValueStart0)(ePlotAreaXValueEnd0) ePlotAreaXValueStart=log10(ePlotAreaXValueStart); ePlotAreaXValueEnd=log10(ePlotAreaXValueEnd); else error('xValues=0 for log scale'); end end end if eYAxisWestScale(1)~=eYAxisWestScale(3) %fix scale ePlotAreaYValueStart=eYAxisWestScale(1); ePlotAreaYValueEnd=eYAxisWestScale(3); else if eYAxisWestScaleType==2 if (ePlotAreaYValueStart0)(ePlotAreaYValueEnd0) ePlotAreaYValueStart=log10(ePlotAreaYValueStart); ePlotAreaYValueEnd=log10(ePlotAreaYValueEnd); else error('yValues=0 for log scale'); end end end if (eXAxisSouthScale(1)==eXAxisSouthScale(3))eAxesCrossOrigin xRange=ePlotAreaXValueEnd-ePlotAreaXValueStart; ePlotAreaXValueStart=ePlotAreaXValueStart-0.05*xRange; ePlotAreaXValueEnd=ePlotAreaXValueEnd+0.05*xRange; end if eYAxisWestScale(1)==eYAxisWestScale(3) yRange=ePlotAreaYValueEnd-ePlotAreaYValueStart; ePlotAreaYValueStart=ePlotAreaYValueStart-0.05*yRange; ePlotAreaYValueEnd=ePlotAreaYValueEnd+0.05*yRange; end egrid; % plot line and write legend if ePlotAreaXValueEnd==ePlotAreaXValueStart ePlotAreaXValueStart=ePlotAreaXValueStart-1; ePlotAreaXValueEnd=ePlotAreaXValueEnd+1 end if ePlotAreaYValueEnd==ePlotAreaYValueStart ePlotAreaYValueStart=ePlotAreaYValueStart-1; ePlotAreaYValueEnd=ePlotAreaYValueEnd+1 end ePlotAreaXFac=ePlotAreaWidth*eFac/... (ePlotAreaXValueEnd-ePlotAreaXValueStart); ePlotAreaYFac=ePlotAreaHeight*eFac/... (ePlotAreaYValueEnd-ePlotAreaYValueStart); legendPos=ePlotLegendPos; for i=1:ePlotLineNo parameter=sprintf('global ePlotLineWidth%d;',i); eval(parameter); parameter=sprintf('width=ePlotLineWidth%d;',i); eval(parameter); parameter=sprintf('global ePlotLineColor%d;',i); eval(parameter); parameter=sprintf('color=ePlotLineColor%d;',i); eval(parameter); parameter=sprintf('global ePlotLineDash%d;',i); eval(parameter); parameter=sprintf('dash=ePlotLineDash%d;',i); eval(parameter); parameter=sprintf('global
Bug#606482: no headphone output on ASUS M4A785T-D motherboard
* Jonathan Nieder [2012-02-25 21:19:43 -0600]: Sergio Gelato wrote: The problem turned out to be due to an inappropriate BIOS configuration setting. The Front Panel Select setting needed (for my specific case) to be set to AC97 instead of HD Audio. Found thanks to some comments in https://bugtrack.alsa-project.org/alsa-bug/view.php?id=5309 (especially note 23449). No kernel changes needed. That sounds like a workaround rather than a fix. I don't see it that way: my front panel is in fact of the older AC97 type, so the earlier BIOS setting was incorrect and changing it was the proper thing to do. When I installed this motherboard I wasn't sure whether I had HDA or AC97, so I decided to try one setting and see if it worked. The fact that the Ubuntu 10.04 kernel appeared to work even with the setting I tried first actually made it harder for me to correctly diagnose the problem. If it is possible to get the headphone jack working in HDA mode as well as AC97, we would like to do that, to avoid new users having to learn what BIOS knob to change. That way lies madness. Maybe in this particular instance one can get away with it, but in general this approach will add complexity to the software. It's already bad enough to have to work around hardware bugs. My impression so far is that the newer HDA front panels allow better power management and that the driver change that apparently broke headphone sound for me was actually an enhancement to make better use of the capabilities of HDA. So of course one can revert to the older approach, but then one probably loses some benefits of the newer one. One could add a kernel (module) option to control this, but then the user needs to figure out what setting is needed and it's just as easy to find out about the BIOS switch instead. My preferred approach would be to add this to the troubleshooting guides: if your audio front panel is misbehaving, check that it is of the right type for your motherboard. (Probably with some additional words about AC97 vs. HDA and/or a link to an external reference.) Now, if there was a way for the kernel to detect a misconfigured front panel and issue a warning in dmesg that would be great. I have no idea whether that is feasible. Based on the upstream report you mentioned it seems that 2.6.39 might fix this; could you try 3.2.y from wheezy or unstable? (The only packages needed from outside squeeze for this test are the kernel image itself, linux-base, and initramfs-tools.) The reason I revisited this bug now is that I tried 3.2.0-0.bpo.1 (for other reasons) and found that the headphone functionality was still broken. That prompted me to make a new search through the ALSA knowledge base, which yielded the hint about the two types of front panel. The report I found the hint in ended up addressing some other issue. Thanks for the update, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661431: override: ttf-sinhala-lklug:oldlibs/extra
Package: ftp.debian.org Severity: normal This package is now a transition package, so its priority should be extra. signature.asc Description: Digital signature
Bug#661432: override: ttf-junicode:oldlibs/extra
Package: ftp.debian.org Severity: normal This package is now a transition package, so its priority should be extra. signature.asc Description: Digital signature
Bug#542221: [Pkg-fonts-devel] Bug#542221: closed by Christian PERRIER bubu...@debian.org (No 0.6 version of the LKLUG Sinhala font seems to be easily available...)
reopen 542221 thanks Quoting Harshula (harsh...@debian.org): Version 0.6: http://sinhala.sourceforge.net/files/lklug.ttf I assume you want a tar.gz instead? I've created one for you: http://sinhala.sourceforge.net/files/ttf-sinhala-lklug-0.6.tar.gz I suspected that, but wasn't sure. Having a tarball also makes it learer that this is a new version...:). I'll then package this new version ASAP. Does the font exist as source code, too? I don't know how it is designed but if this is done with fontforge, publishing the .sfd file could be a good idea, too. signature.asc Description: Digital signature
Bug#661433: override: ttf-sil-abyssinica:oldlibs/extra
Package: ftp.debian.org Severity: normal This package is now a transition package, so its priority should be extra. signature.asc Description: Digital signature
Bug#661434: override: libgconf2-4:oldlibs/optional
package: ftp.debian.org Hi, Le dimanche 26 février 2012 à 13:33 +, Debian FTP Masters a écrit : There are disparities between your recently accepted upload and the override file for the following file(s): libgconf2-4_3.2.3-2_amd64.deb: package says section is oldlibs, override says libs. This package is now an empty, transition package to libgconf-2-4. See the changelog for the (multiarch-related) reason. Please move it to section oldlibs. Thanks, -- .''`. Josselin Mouette : :' : `. `' `- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660842: ITP: python-gnupg -- python wrapper for the gnupg command
On 2012-02-26 at 00:26:14 +0100, Evgeni Golov wrote: What's wrong with [...] What are the benefits of python-gnupg? The homepage doesnt tell any, neither does the description :) Mostly the documentation: python-gnupg's interface is fully documented with docstrings (with examples checked in the test suite) and it has an in-depth manual/tutorial[1]. among the other python interfaces to gnupg functionality, python-gnupginterface seems to be the one documented best in the module, but the last release was in 2002 and the homepage[2] features broken links both to the mailing list and documentation. The docstrings for both python-gpgme and python-pyme are both poor, and in the case of pyme the homepage just refers to the pgpme docs, which are complete, but of course based on the slighty different conventions of the C library. [1] http://packages.python.org/python-gnupg/ [2] http://py-gnupg.sourceforge.net/ -- Elena ``of Valhalla'' -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660842: ITP: python-gnupg -- python wrapper for the gnupg command
On Mon, Feb 27, 2012 at 09:06:51AM +0100, Elena ``of Valhalla'' wrote: On 2012-02-26 at 00:26:14 +0100, Evgeni Golov wrote: What's wrong with [...] What are the benefits of python-gnupg? The homepage doesnt tell any, neither does the description :) Mostly the documentation: python-gnupg's interface is fully documented with docstrings (with examples checked in the test suite) and it has an in-depth manual/tutorial[1]. among the other python interfaces to gnupg functionality, python-gnupginterface seems to be the one documented best in the module, but the last release was in 2002 and the homepage[2] features broken links both to the mailing list and documentation. The docstrings for both python-gpgme and python-pyme are both poor, and in the case of pyme the homepage just refers to the pgpme docs, which are complete, but of course based on the slighty different conventions of the C library. Hm, okay. I must admit I have used both pyme and pygpgme with great success, but relying on the gpgme docs, as these are quite complete and apply quite well to the Python versions. Another question I would like to raise is the performance -- python-gnupg seems to be a command line wrapper around gnupg, thus having to fork() heavily -- does it affect processing of data? regards Evgeni -- Bruce Schneier can read and understand Perl programs. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661435: mc: lynx-like motion forgotten during upgrade to 4.8.1
Package: mc Version: 3:4.8.1-1 Severity: normal I had Lynx-like motion enabled in mc 3:4.7.0.9-2. Upgrading to mc 3:4.8.1-1 auto-migrated config files, but my customization to enable Lynx-like motion was lost. Moreover, this config option was moved to Panel options which took some time to figure out (including close-reading upstream changelog which did not mention this change (in a way that caught my attention). At a minimum, I recommend documenting in a NEWS entry which options are not migrated but reset to defaults at upgrade. Preferrably this issue is passed upstream and handled more elegantly. - Jonas -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages mc depends on: ii e2fslibs 1.42.1-2 ii libc6 2.13-27 ii libcomerr21.42.1-2 ii libglib2.0-0 2.30.2-6 ii libgpm2 1.20.4-4 ii libslang2 2.2.4-6 ii mc-data 3:4.8.1-1 Versions of packages mc recommends: ii mime-support 3.52-1 Versions of packages mc suggests: ii arj none ii bzip21.0.6-1 ii catdvi none ii dbview none ii djvulibre-binnone ii epdfview [pdf-viewer]0.1.8-1+b1 ii evince-gtk [pdf-viewer] 3.2.1-1 ii file 5.10-1 ii graphicsmagick-imagemagick-compat [imagemagick] 1.3.12-1.1 ii gv none ii links2.5-1 ii odt2txt 0.4+git20100620-1+b1 ii perl 5.14.2-7 ii python 2.7.2-10 ii python-boto none ii python-tz2011h-1 ii unzip6.0-5 ii w3m 0.5.3-5 ii zip 3.0-4 -- Configuration Files: /etc/mc/mc.menu changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660266: Fwd: Bug#660266: Failed to download 1rott13.zip
Am 25.02.2012 14:12, schrieb Ansgar Burchardt: fab...@greffrath.com writes: +SHAREURL3=http://pkg-games.alioth.debian.org; could you move them to a subdirectory (maybe game-data or game-data-packager)? I would prefer not having random shareware archives in the team's webroot. I have done so (called the directory game-data, since the stuff it contains is independent of g-d-p) and updated g-d-p in GIT. However, I have left two symlinks in place until the updated g-d-p is uploaded and migrated. - Fabian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661436: upower: general protection with ipheth
Package: upower Version: 0.9.15-2 Severity: normal Hi, when I connect my iphone via USB upowerd crashes repeatedly, as a consequence I cannot use the network interface provided by the ipheth kernel driver. The syslog contains many lines: [ 2619.013161] upowerd[7538] general protection ip:7ff5f1de555b sp:7fff32f192c0 error:0 in libplist.so.1.1.8[7ff5f1ddc000+c000] Please let me know what else you need to know. Best Norbert -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (501, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.3.0-rc5+ (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages upower depends on: ii dbus 1.4.18-1 ii libc6 2.13-26 ii libdbus-1-31.4.18-1 ii libdbus-glib-1-2 0.98-1 ii libglib2.0-0 2.30.2-6 ii libgudev-1.0-0 175-3.1 ii libimobiledevice2 1.1.1-3 ii libplist1 1.8-1 ii libpolkit-gobject-1-0 0.104-2 ii libupower-glib10.9.15-2 ii libusb-1.0-0 2:1.0.9~rc3-3 ii pm-utils 1.4.1-9 ii udev 175-3.1 Versions of packages upower recommends: ii policykit-1 0.104-2 upower suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#659541: Please enable autobuild for upx-nrv
Robert Luberda rob...@debian.org writes: Ansgar Burchardt wrote: Robert Luberda rob...@debian.org writes: The package is upx-nrv, and it's license allow redistributing or modifying the program under GNU GPL with a special exception granted for compressed executables. If it's licensed under the GPL: where is the source? The source for upx itself is provided on the upstream website (and upx-ucl package is built from it), source for NRV is not available. http://www.gnu.org/licenses/gpl-faq.html#UnchangedJustBinary http://www.gnu.org/licenses/gpl-faq.html#GPLIncompatibleLibs And how can you link it against a non-free library and distribute the resulting binary? NRV library is written by the same authors, so I assume they can link their upx binaries with their library. Sure, but nobody else can redistribute the resulting binaries unless they do get special permission (the GPL doesn't allow this, see above). Regards, Ansgar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661437: [l10n] Updated Czech translation of lilo debconf messages
Package: lilo Severity: wishlist Tags: l10n, patch Hi, in attachement there is updated Czech (cs.po) translation of lilo debconf messages. Please include it with the package. Thanks -- Miroslav Kure # Translation of Lilo debconf templates to Czech # This file is distributed under the same license as the Lilo package. # # Translators: # Miroslav Kure ku...@debian.cz, 2008-2012 # msgid msgstr Project-Id-Version: lilo 1:23.1-2\n Report-Msgid-Bugs-To: l...@packages.debian.org\n POT-Creation-Date: 2011-03-14 15:48+0100\n PO-Revision-Date: 2012-02-27 09:35+0100\n Last-Translator: Miroslav Kure ku...@debian.cz\n Language-Team: Czech debian-l10n-cz...@lists.debian.org\n Language: cs\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n #. Type: note #. Description #: ../lilo.templates:1001 msgid LILO configuration msgstr Konfigurace zavaděče LILO #. Type: note #. Description #: ../lilo.templates:1001 msgid It seems to be your first LILO installation. It is absolutely necessary to run liloconfig(8) when you complete this process and execute /sbin/lilo after this. msgstr Zdá se, že to je první instalace LILA. Je nezbytné, abyste po skončení tohoto procesu a spustili liloconfig(8) a poté /sbin/lilo. #. Type: note #. Description #: ../lilo.templates:1001 msgid LILO won't work if you don't do this. msgstr Pokud to neuděláte, LILO nebude fungovat. #. Type: boolean #. Description #: ../lilo.templates:2001 msgid Do you want to add the large-memory option? msgstr Přidat volbu large-memory? #. Type: boolean #. Description #: ../lilo.templates:2001 msgid Usually LILO loads the initrd file into the first 15MB of memory to avoid a BIOS limitation with older systems (earlier than 2001 and few systems until 2004). msgstr LILO obvykle zavádí initrd do prvních 15MB paměti, aby tak obešlo omezení BIOSu starších systémů (před rokem 2001 a s několika výjimkami do roku 2004). #. Type: boolean #. Description #: ../lilo.templates:2001 msgid With newer kernels the combination of kernel and initrd may not fit into the first 15MB of memory. LILO compute the needed size of memory and will automatically use the memory above 15MB, too, if there is enough physical memory. msgstr U novějších jader se však nemusí kombinace jádra a initrd vlézt do prvních 15MB paměti. LILO si spočítá velikost potřebné paměti a pokud existuje dostatek fyzické paměti, automaticky použije i paměť nad 15MB. #. Type: boolean #. Description #: ../lilo.templates:2001 msgid If this machine has a recent BIOS without a 15MB limitation and you want to use memory above 15MB for all kernels, set the 'large-memory' option. msgstr Pokud počítač obsahuje aktuální BIOS bez omezení na 15MB a chcete u všech \n jader použít paměť nad 15MB, nastavte volbu „large-memory“. #. Type: boolean #. Description #: ../lilo.templates:3001 msgid Do you want to run /sbin/lilo now? msgstr Chcete nyní spustit /sbin/lilo? #. Type: boolean #. Description #: ../lilo.templates:3001 msgid It was detected that it's necessary to run /sbin/lilo in order to activate the new LILO configuration. msgstr Bylo zjištěno, že pro použití nové konfigurace LILA je nutné spustit /sbin/ lilo. #. Type: boolean #. Description #: ../lilo.templates:3001 msgid WARNING: This procedure will write data in your MBR and may overwrite some data there. If you skip this step, you must run /sbin/lilo before rebooting your computer, or your system may not boot again. msgstr VAROVÁNÍ: Tento postup zapíše data do MBR a tím přepíše data tam umístěná. Pokud tento krok přeskočíte, musíte spustit /sbin/lilo ještě před restartem počítače, protože jinak by systém nemusel nastartovat. #. Type: boolean #. Description #: ../lilo.templates:4001 msgid Do you want to convert boot and root options? msgstr Přidat volbu large-memory? #. Type: boolean #. Description #: ../lilo.templates:4001 msgid Since kernel using the newer disk interface 'libata' you need the newer DiskID and/or UUID in your /etc/lilo.conf for the boot and root options. For the most modern systems you should use this conversion and then run '/sbin/ lilo'. msgstr Na jádrech používajících novější diskové rozhraní „libata“, budete pro volby boot a root v /etc/lilo.conf potřebovat nové DiskID a/nebo UUID. Na většině moderních systémů byste měli tento převod povolit a potom spustit „/sbin/lilo“.
Bug#661438: approx: [INTL:nl] Dutch translation of debconf templates
Package: approx Severity: wishlist Tags: patch l10n Hello, Attached is the Dutch translation of the approx debconf templates. Please include it in your next upload. Regards, -- Jeroen Schot # Dutch translation of approx debconf templates. # Copyright (C) 2012 THE PACKAGE'S COPYRIGHT HOLDER # This file is distributed under the same license as the approx package. # Jeroen Schot sc...@a-eskwadraat.nl, 2012. # msgid msgstr Project-Id-Version: approx 5.1-1\n Report-Msgid-Bugs-To: app...@packages.debian.org\n POT-Creation-Date: 2009-04-09 07:33+0200\n PO-Revision-Date: 2012-02-27 09:48+0100\n Last-Translator: Jeroen Schot sc...@a-eskwadraat.nl\n Language-Team: Debian l10n Dutch debian-l10n-du...@lists.debian.org\n Language: nl\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n #. Type: string #. Description #: ../approx.templates:2001 msgid TCP port for approx service: msgstr TCP-poort voor de approx-dienst: #. Type: string #. Description #: ../approx.templates:2001 msgid Please enter the TCP port on which approx should listen for requests. The default is the value used by apt-proxy, for compatibility with its clients' / etc/apt/sources.list files. msgstr Op welke TCP-poort moet approx naar aanvragen luisteren? De standaard is hetzelfde als die van apt-proxy, vanwege compatibiliteit met de /etc/apt/ sources.list-bestanden van diens clients.
Bug#661439: drivel: French debconf templates translation
Package: drivel Version: N/A Severity: wishlist Tags: patch l10n *** /home/julien/traductions/po-debconf/patch-translate.txt Please find attached the french debconf templates translation, proofread by the debian-l10n-french mailing list contributors. This file should be put as debian/po/fr.po in your package build tree. -- System Information: Debian Release: 6.0.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash # French translation of drivel. # Copyright (C) 2004-2006 The GNOME Foundation. # This file is distributed under the same license as the drivel package. # # Gareth Owen gowe...@yahoo.com 2004. # David Lodge d...@cirt.net, 2004. # Jeff Coquery jcoqu...@gmail.com, 2006. # Jonathan Ernst jonat...@ernstfamily.ch, 2006. # Claude Paroz cla...@2xlibre.net, 2007. # Julien Patriarca patriar...@gmail.com, 2012. msgid msgstr Project-Id-Version: drivel\n Report-Msgid-Bugs-To: \n POT-Creation-Date: 2011-05-07 15:59+0100\n PO-Revision-Date: 2012-02-20 13:12+0100\n Last-Translator: Julien Patriarca patriar...@gmail.com\n Language-Team: French debian-l10n-fre...@lists.debian.org\n Language: fr\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n #: ../data/drivel.schemas.in.h:1 msgid A list of every journal username previously used on this machine. msgstr Liste de tous les identifiants de journaux précédemment utilisés sur cette machine. #: ../data/drivel.schemas.in.h:2 msgid A list of moods for the drivel menu. msgstr Une liste des humeurs pour le menu drivel #: ../data/drivel.schemas.in.h:3 msgid The currently logged-in user. msgstr L'utilisateur connecté en ce moment. #: ../data/drivel.schemas.in.h:4 msgid The number of moods stored locally. msgstr Le nombre d'humeurs stockées localement. #: ../data/gnome-drivel.desktop.in.h:1 ../src/about.c:98 msgid Drivel Journal Editor msgstr Éditeur de journal Drivel #: ../data/gnome-drivel.desktop.in.h:2 msgid Journal Editor msgstr Éditeur de journal #: ../data/gnome-drivel.desktop.in.h:3 msgid Update and manage your online journal msgstr Gérez et mettez à jour votre journal en ligne #: ../data/mime/drivel.xml.in.h:1 msgid Draft journal entry msgstr Brouillon de billet de journal #. #. * Translators should localize the following string #. * which will give them credit in the About box. #. * E.g. Fulano de Tal ful...@detal.com #: ../src/about.c:68 msgid translator-credits msgstr Gareth Owen gowe...@yahoo.com\n David Lodge d...@cirt.net\n Coquery Jeff jcoqu...@gmail.com\n Jonathan Ernst jonat...@ernstfamily.ch\n Claude Paroz cla...@2xlibre.net #: ../src/about.c:85 msgid With help from: msgstr Avec l'aide de : #: ../src/about.c:90 msgid And many others--thank you, all! msgstr Et beaucoup d'autres, merci à tout le monde ! #: ../src/about.c:102 msgid A journal client for the GNOME desktop. msgstr Un client de journal pour le bureau GNOME. #: ../src/about.c:108 msgid Homepage: msgstr Page d'accueil : #: ../src/blog_atom.c:301 ../src/network.c:315 ../src/network.c:321 #: ../src/network.c:365 msgid Server error msgstr Erreur serveur #: ../src/blog_atom.c:302 msgid The server did not return a valid Atom response. msgstr Le serveur n'a pas retourné de réponse Atom valide. #: ../src/blog_atom.c:408 msgid Unknown error msgstr Erreur inconnue #: ../src/blog_atom.c:411 msgid Error Posting Entry msgstr Erreur lors de la publication d'un billet #: ../src/blog_lj.c:290 msgid default msgstr par défaut #: ../src/blog_mt.c:140 ../src/insert_poll_dialog.c:175 ../src/main.c:632 #: ../src/main.c:634 msgid None msgstr Aucun #: ../src/blog_offline.c:41 msgid Offline msgstr Hors-ligne #: ../src/dialogs.c:319 ../src/dialogs.c:714 msgid [No journal entries] msgstr [Aucun billet de journal] #. Context: Spell check dictionary #: ../src/dialogs.c:394 msgid System default msgstr Celui du système #: ../src/dialogs.c:426 msgid Missing username msgstr Nom d'utilisateur manquant #: ../src/dialogs.c:427 msgid Please enter a username to add. msgstr Veuillez saisir un nom d'utilisateur à ajouter. #: ../src/dialogs.c:650 ../src/main.c:349 ../src/utils.c:520 msgid Public msgstr Public #: ../src/dialogs.c:655 ../src/main.c:353 ../src/utils.c:514 msgid Private msgstr Privé #: ../src/dialogs.c:809 msgid Community msgstr Communauté #: ../src/dialogs.c:811 msgid Syndicated Feed msgstr Flux syndiqué #: ../src/dialogs.c:813 msgid User msgstr Utilisateur #: ../src/dialogs.c:867 msgid Add Friend msgstr Ajouter un ami #: ../src/dialogs.c:895 msgid _Friend's username: msgstr _Nom de l'ami : #: ../src/dialogs.c:914 msgid _Text color: msgstr Couleur du _texte : #: ../src/dialogs.c:929
Bug#659541: Please enable autobuild for upx-nrv
Robert, am Sun, Feb 26, 2012 at 11:26:31PM +0100 hast du folgendes geschrieben: NRV library is written by the same authors, so I assume they can link their upx binaries with their library. true, and they can distribute it. But we can't distribute it under the GPL then. Kind regards, Philipp Kern -- .''`. Philipp KernDebian Developer : :' : http://philkern.de Stable Release Manager `. `' xmpp:p...@0x539.de Wanna-Build Admin `-finger pkern/k...@db.debian.org signature.asc Description: Digital signature
Bug#660266: Fwd: Bug#660266: Failed to download 1rott13.zip
notfound 660936 1.1.1-4 thanks Am 25.02.2012 14:09, schrieb Cyril Brulebois: Please update the bug to reflect that it doesn't apply to unstable, then. Done. Double # for the Closes. Fixed, thanks. Looks sane to me otherwise, feel free to upload unless you hear otherwise from others. Will do so, thank you. Please find the final debdiff attached. Am 25.02.2012 14:12, schrieb Ansgar Burchardt: could you move them to a subdirectory (maybe game-data or game-data-packager)? I would prefer not having random shareware archives in the team's webroot. I have done so (called the directory game-data, since the stuff it contains is independent of g-d-p) and updated g-d-p in GIT. However, I have left two symlinks in place until the updated g-d-p is uploaded and migrated. - Fabian diff --git a/debian/changelog b/debian/changelog index a854bda..246d693 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +rott (1.1.1-3.1+squeeze1) squeeze; urgency=low + + * As a last resort, try to download the shareware data files +from pkg-games.alioth.debian.org (Closes: #660266). + * Update Vcs-* fields in debian/control. + + -- Fabian Greffrath fabian+deb...@greffrath.com Mon, 27 Feb 2012 10:00:12 +0100 + rott (1.1.1-3.1) unstable; urgency=low * Non-maintainer upload. diff --git a/debian/control b/debian/control index d9e9333..d553898 100644 --- a/debian/control +++ b/debian/control @@ -7,8 +7,8 @@ Uploaders: Fabian Greffrath fabian+deb...@greffrath.com, Build-Depends: debhelper (= 7.3), libsdl1.2-dev, libsdl-mixer1.2-dev Standards-Version: 3.8.3 Homepage: http://icculus.org/rott/ -Vcs-Svn: svn://svn.debian.org/svn/pkg-games/packages/trunk/rott/ -Vcs-Browser: http://svn.debian.org/wsvn/pkg-games/packages/trunk/rott/ +Vcs-Git: git://anonscm.debian.org/pkg-games/rott.git +Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-games/rott.git Package: rott Architecture: any diff --git a/debian/rott.postinst b/debian/rott.postinst index 81a9097..f5166dc 100644 --- a/debian/rott.postinst +++ b/debian/rott.postinst @@ -8,6 +8,7 @@ SHAREDIR=/usr/share/games/rott SHAREZIP=1rott13.zip SHAREURL1=ftp://ftp.3drealms.com/share; SHAREURL2=ftp://ftp.3drealms.com/pub/share; +SHAREURL3=http://pkg-games.alioth.debian.org/game-data; SHAREMD5=0fafd6b629eab80278fc726e31f9cf41 DOCDIR=/usr/share/doc/rott @@ -45,6 +46,7 @@ case $1 in if [ ! -e ${SHAREDIR}/${SHAREZIP} ]; then wget --progress=dot --directory-prefix ${SHAREDIR} -c ${SHAREURL1}/${SHAREZIP} || \ wget --progress=dot --directory-prefix ${SHAREDIR} -c ${SHAREURL2}/${SHAREZIP} || \ + wget --progress=dot --directory-prefix ${SHAREDIR} -c ${SHAREURL3}/${SHAREZIP} || \ echo rott: Download of shareware data files failed! 2 fi
Bug#661436: upower: general protection with ipheth
On Mo, 27 Feb 2012, Norbert Preining wrote: when I connect my iphone via USB upowerd crashes repeatedly, as a consequence I cannot use the network interface provided by the ipheth kernel driver. The syslog contains many lines: And even more inconvenient, the gnome mbattery monitor simply stops working, it shows the value of the battery charge when I plugged in the iphone and remains there forever, which is very inconvenient ;-) Best wishes Norbert Norbert Preiningpreining@{jaist.ac.jp, logic.at, debian.org} JAIST, Japan TeX Live Debian Developer DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 FROSSES (pl.n.) The lecherous looks exchanged between sixteen-year-olds at a party given by someone's parents. --- Douglas Adams, The Meaning of Liff -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#633297: funguloids: FTBFS everywhere: error: reference to 'map' is ambiguous
On Sat, 2012-02-25 at 12:23 +, peter green wrote: IMO if you have made reasonable attempts to contact upstream and have seen no signs of life then forking (and announcing your fork to other distro packagers) is the corect thing to do. Upstream has finally gotten back to me, forking it will not be needed since he is going to give me admin access to the project. -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#661422: myodbc: New release 5.1.10 available
On Mon, Feb 27, 2012 at 03:22:54AM +0100, Leo Iannacone wrote: Package: myodbc Severity: important Dear maintainer, a new release of odbc is available (5.1.0). This fixes some problems of compatibility with mysql 5.5. Can you please consider to package it? Here's the result of trying to build myodbc 5.1.10 against version 5.5.20-1 of mysql-5.5, taken from the mysql team's svn repo: libtool: link: gcc -O3 -DDBUG_OFF -I/usr/include/mysql -DBIG_JOINS=1 -fno-strict-aliasing -g -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wl,-z -Wl,relro -o .libs/my_basics my_basics.o ../driver/.libs/libmyodbc5.so -L/usr/lib/x86_64-linux-gnu -lmysqlclient_r -lpthread -lm -lrt -ldl -lz -L/usr/lib -lodbcinst ../driver/.libs/libmyodbc5.so: undefined reference to `dynstr_append_mem' ../driver/.libs/libmyodbc5.so: undefined reference to `dynstr_append' ../driver/.libs/libmyodbc5.so: undefined reference to `dynstr_free' ../driver/.libs/libmyodbc5.so: undefined reference to `dynstr_realloc' ../driver/.libs/libmyodbc5.so: undefined reference to `strfill' ../driver/.libs/libmyodbc5.so: undefined reference to `init_dynamic_string' ../driver/.libs/libmyodbc5.so: undefined reference to `dynstr_append_os_quoted' collect2: ld returned 1 exit status make[2]: *** [my_basics] Error 1 So I would not say this has fixed the problems of compatibility with mysql 5.5 given that the test suite won't compile. (Patches welcome.) -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Bug#660266: Failed to download 1rott13.zip
Hi Paul, Am 26.02.2012 01:03, schrieb Paul Wise: If the rott data is distributable by Debian, why isn't it being packaged in non-free? If the rott data is not distributable in non-free, what makes it distributable from alioth? I believe this is due to the absurd shareware license that applies for the shareware zip file. Citing the first two paragraphs from the accompanying VENDOR.DOC file: ---8--- [*] If you want to distribute it in a retail location (such as on a rack), or as part of a hardware or software bundle, or on CD-ROM you must get PRIOR signed written permission from Apogee. Apogee reserves its right to withhold permission. [*] Everyone can -- and is encouraged! -- to copy, upload and generally pass around this Program without charging for it. ---8--- So if you consider the Debian distribution as a software bundle then it is not OK to include it, but is it OK to upload it anywhere at will. :/ Since I am not going to discuss this interpretation with my lawyer, I think we should play safe and it is reasonable to only host the zip file (which is explicitely allowed) and let the users do the rest themselves on their computers. ;) Remember, this is from 1998 and ROTT is a DOS game. The concept of Linux distributions wasn't that popular back then. ;) Cheers, Fabian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#490604: debian-policy: please don't state that scripts working under dash are 'probably' policy-compliant
Russ Allbery wrote: --- a/policy.sgml +++ b/policy.sgml @@ -7968,10 +7968,12 @@ fname () { [...] - as its interpreter. If your script works with prgndash/prgn - (originally called prgnash/prgn), it probably complies with - the above requirements, but if you are in doubt, use - file/bin/bash/file. + as its interpreter. Checking your script + with prgncheckbashisms/prgn from + the packagedevscripts/package package or running your script + with prgnposh/prgn may help uncover violations of the above + requirements. If in doubt whether a script complies with these + requirements, use file/bin/bash/file. I tend to find checking syntax ($shell -n) and running with bash, dash, mksh, and ksh93 more useful than posh for checking that a script is portable to the main POSIX-style shells in common use. I want posh to work for this kind of thing, but in some cases it is not different enough from bash to catch problems. Some scripting portability pitfalls, taken from the git commit log: - 'test $foo == $bar' (Checkbashisms and posh catch it) - brace expansion (Checkbashisms and posh catch it) - ++i in arithmetic expansion (Checkbashisms catches it. Posh doesn't) - 'echo $var', var='foo\bar' (Posh catches it. Checkbashisms doesn't) - printf '\xc3\xa4\n' (Neither posh nor checkbashisms catches it) - 'local var=$val', val='foo bar' (Posh catches it; checkbashisms doesn't) - It is not predictable when starting a new command in the shell will start a new process. Scripts notice this by using $!, $PPID, kill, and so on. (Testing as many different shells as possible helps a lot --- bash, dash, ksh93, and mksh behaviors are all different.) - 'var=newval function_call; echo $var' (Neither posh nor checkbashisms catches it). Yes, the dash/ksh93 behavior is explicitly permitted in POSIX. - 'var=$((echo hi) | head)' (Neither posh nor checkbashisms catches it) Hope that helps, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#624782: mirror submission for mirrors.coreix.net
On 27/02/12 02:59, Raphael Geissert wrote: Hi, Please accept our apologies for responding until now. On Sunday 29 May 2011 16:43:02 Coreix Mirrors wrote: Hello, Is there a problem? If yes, which exactly? We sync from umu.se via rsync. As documented on the Debian Mirrors website, rsync alone isn't enough. Some files need to be synced in a specific order to avoid user disruption during the sync process. ftpsync is the name of a script that, despite what its name may suggest, uses rsync in the right way to create and sync a Debian mirror. It takes care of creating a trace file which is needed for proper monitoring, among other things. You can find the latest version of ftpsync in the project/ftpsync/ directory of your mirror. Could you please address the issue and get back to us? Thanks in advance. P.S. the archive is updated four times a day nowadays, please consider updating more often. Kind regards, Hello and thanks for the reply, Raphael. I'll try to set up anonftpsync. Could you recommend a good rsync server to sync from the UK? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661440: libexplain FTBFS on Alpha: linux/ac/sys/types.h: No such file or directory
Source: libexplain Version: 0.51.D001-1 Severity: normal User: debian-al...@lists.debian.org Usertags: alpha X-Debbugs-CC: debian-al...@lists.debian.org libexplain FTBFS on Alpha with the following: libtool: compile: gcc -Wall -g -O2 -Wall -Wextra -Wl,--as-needed -I. -c libexplain/buffer/eio.c -fPIC -DPIC -o libexplain/buffer/.libs/eio.o In file included from libexplain/buffer/eio.c:22:0: ./libexplain/ac/fcntl.h:35:32: fatal error: linux/ac/sys/types.h: No such file or directory Full build log is available at: http://buildd.debian-ports.org/status/fetch.php?pkg=libexplainarch=alphaver=0.51.D001-1stamp=1329468418 The compilation fails because of some trickery in the file libexplain/ac/fcntl.h, namely: #if defined(__alpha__) defined(HAVE_LINUX_FCNTL_H) #include libexplain/ac/linux/types.h /* Ubuntu Hardy needs this first */ /* This is very strange, but numerous tests fail if we use fcntl.h because is appears to have several incorrect macro definitions */ #include linux/ac/sys/types.h #include linux/fcntl.h #else I'm not sure why a compilation path unique to Alpha is present but I found the following in the libexplain changelog which seems relevant: libexplain (0.35.D006-1) unstable; urgency=low * A build problem concerning fcntl.h has been fixed: it turns out that on Liunux [sic] alpha fcntl.h has the wrong values for O_LARGEFILE and O_DIRECTORY, and you must use linux/fcntl.h instead. I find that comment somewhat mystifying as O_LARGEFILE is defined to be 0, which I believe to be correct as _all_ files are by default and by design O_LARGEFILE, and O_DIRECTORY is defined to be 010 which is the same as is in the linux kernel source. (They may not be the same as x86 which is not a problem.) I ran a test build where I had commented out the Alpha specific code in libexplain/ac/fcntl.h so it would use the standard code that every other architecture uses and the compilation passed that point and went on for a lot further until it failed with: libtool: compile: gcc -Wall -g -O2 -Wall -Wextra -Wl,--as-needed -I. -c libexplain/iocontrol/tiocgetp.c -fPIC -DPIC -o libexplain/iocontrol/.libs/tiocgetp.o libexplain/iocontrol/tiocgetp.c:31:5: error: invalid application of 'sizeof' to incomplete type 'struct sgttyb' That is due to use of the TIOCGETP macro. It appears that termios.h only declares 'struct sgttyb' but does not define it so the sizeof operator on struct sgttyb fails. Struct sgttyb is defined in: /usr/include/alpha-linux-gnu/asm/termios.h but I haven't been able to work out why that is not being included. It's getting late so I am filing the bug report at this stage. Cheers Michael. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#542221: [Pkg-fonts-devel] Bug#542221: closed by Christian PERRIER bubu...@debian.org (No 0.6 version of the LKLUG Sinhala font seems to be easily available...)
On Mon, 2012-02-27 at 06:38 +0100, Christian PERRIER wrote: I suspected that, but wasn't sure. Having a tarball also makes it learer that this is a new version...:). I'll then package this new version ASAP. Thanks. Does the font exist as source code, too? I don't know how it is designed but if this is done with fontforge, publishing the .sfd file could be a good idea, too. The tarball should contain the SFD file. The CVS version is in SFD format. cya, # -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652745: Some packaging tests
Hi, I have tried to build packages based on the ppa ones: * sid - amd64 : Seems to work ok apart from minor lintian warnings. * squeeze - x86 : In order to build policykit integration the libpolkit-qt-1-dev package doesn't have two cmake files that sid package has. If you try to build it with these two files copied manually into the system it doesn't build at all. There's a C++ build error. If you remove the install file for policykit-agent then it works (without policykit integration of course). Next weekend (or the next one) I'll try to make more tests, improve my own packages and maybe try to search a mentor. adrian15 -- Support free software. Donate to Super Grub Disk. Apoya el software libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#638060: debian-policy: §9.1.1: FHS should also be a must for generated files
Russ Allbery wrote: --- a/policy.sgml +++ b/policy.sgml @@ -6169,11 +6169,11 @@ install -m644 debian/shlibs.varpackage/var debian/varpackage/var/DEBIAN/ headingFile System Structure/heading p - The location of all installed files and directories must - comply with the Filesystem Hierarchy Standard (FHS), This is a clear and unfortunately too narrow restriction on the package. I agree with you that if we could easily make it match the intent that we all know in broad strokes, that would be worth doing without much fuss. [...] + The location of all files and directories must comply with the + Filesystem Hierarchy Standard (FHS) Unfortunately, I don't think that matches the old intent. This sounds like a restriction on the admin. I'm particularly worried that people could use this as justification for packages assuming that all files and directories comply with the FHS, instead of coping with the real world --- for example, we have traditionally treated files placed by admins as worth keeping, even when put in areas outside /usr/local, /var/local, /home, and /opt, like /usr/share/doc/package alongside the shipped docs. So for what it's worth, without debugging I don't think this is a non-normative change. Hope that helps, and sorry for the lack of clarity before. Sincerely, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661441: src:genshi: tests fail under python2.7, but failure is ignored
Package: src:genshi Version: 0.6-2 Severity: serious Justification: Policy 4.6 == FAIL: test_sanitize_remove_src_javascript (genshi.filters.tests.html.HTMLSanitizerTestCase) -- Traceback (most recent call last): File /«PKGBUILDDIR»/genshi/filters/tests/html.py, line 442, in test_sanitize_remove_src_javascript 'IMG SRC=`javascript:alert(RSnake says, \'foo\')`') AssertionError: ParseError not raised -- Ran 828 tests in 1.198s FAILED (failures=1) Yet, the build continues... SR -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661442: mingw-w64-dev: Error when including ddraw.h
Package: mingw-w64-dev Version: 2.0.1+svn4784-2 Severity: normal Hi Stephen, Including ddshow.h leads to a compilation error: snoopy:~$ cat b.cpp #include dshow.h int main (void) { return 0; } snoopy:~$ i686-w64-mingw32-g++ b.cpp In file included from /usr/lib/gcc/i686-w64-mingw32/4.6/../../../../i686-w64-min gw32/include/dshow.h:41:0, from b.cpp:1: /usr/lib/gcc/i686-w64-mingw32/4.6/../../../../i686-w64-mingw32/include/strmif.h: 6824:17: error: conflicting declaration ‘typedef void* IDirectDraw’ /usr/lib/gcc/i686-w64-mingw32/4.6/../../../../i686-w64-mingw32/include/ddraw.h:1 338:1: error: ‘struct IDirectDraw’ has a previous declaration as ‘struct IDirect Draw’ /usr/lib/gcc/i686-w64-mingw32/4.6/../../../../i686-w64-mingw32/include/strmif.h: 6825:17: error: conflicting declaration ‘typedef void* IDirectDrawSurface’ /usr/lib/gcc/i686-w64-mingw32/4.6/../../../../i686-w64-mingw32/include/ddraw.h:1 873:1: error: ‘struct IDirectDrawSurface’ has a previous declaration as ‘struct IDirectDrawSurface’ /usr/lib/gcc/i686-w64-mingw32/4.6/../../../../i686-w64-mingw32/include/strmif.h: 6826:17: error: conflicting declaration ‘typedef void* LPDIRECTDRAWSURFACE7’ [...] Thank you! Eugen -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593508: kadu: some strange libqtcore error
Please see if the problem still occurs in version 0.11.0-1, or higher. -- Patryk Cisek -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660265: Heads-Up
On Sun, Feb 26, 2012 at 03:55:38PM +, Ben Hutchings wrote: These will be in the next upload. I haven't added the patch to make use Great! Thanks a lot! of the various modes configurable, but I think all you really wanted was to be able to enable RC6 without RC6+ and that's what you will get. So I'm considering these changes to close the bug. Yes, you're absolutely correct. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org Jabber: michael.meskes at googlemail dot com VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661443: FTBFS
Package: dozzaqueux Version: 3.21-1 Severity: serious Your package fails to build from source: dpkg-source: info: using source format `3.0 (quilt)' dpkg-source: info: building dozzaqueux using existing ./dozzaqueux_3.21.orig.tar.gz dpkg-source: warning: ignoring deletion of file dozzzaqueux.lpi dpkg-source: info: building dozzaqueux in dozzaqueux_3.21-1.debian.tar.gz dpkg-source: info: building dozzaqueux in dozzaqueux_3.21-1.dsc debian/rules build dh build dh_testdir dh_auto_configure dh_auto_build make[1]: Entering directory `/root/dozzaqueux-3.21' fpc -B -MObjFPC -Scgi -O1 -gl -WG -vewnhi -l -Fi/ -Fu/usr/lib/lazarus/0.9.30.2/lcl/units/x86_64-linux/ -Fu/usr/lib/lazarus/0.9.30.2/lcl/units/x86_64-linux/gtk2/ -Fu/usr/lib/lazarus/0.9.30.2/packager/units/x86_64-linux/ -Fu/usr/lib/lazarus/0.9.30.2/components/printers/lib/x86_64-linux/gtk2/ -Fu/usr/lib/lazarus/0.9.30.2/components/synedit/units/x86_64-linux/ -Fu. -dLCL -dLCLgtk2 -TLINUX -odozzaqueux dozzzaqueux.lpr Hint: Start of reading config file /etc/fpc.cfg Hint: End of reading config file /etc/fpc.cfg Error: Illegal parameter: -WG Hint: -? writes help pages Error: /usr/bin/ppcx64 returned an error exitcode (normal if you did not specify a source file to be compiled) make[1]: *** [dozzaqueux] Error 1 make[1]: Leaving directory `/root/dozzaqueux-3.21' dh_auto_build: make -j1 returned exit code 2 make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661427: Compilation failures with : Exiting with 4 jobserver tokens available; should be 3!
forcemerge 622863 661427 quit Hi Julien, Julien Puydt wrote: I get a lot of compilation failures with : make[1]: INTERNAL: Exiting with 4 jobserver tokens available; should be 3! (running make -j 3 -l 2) Even though Vincent was using strace and I suspect you are not, I'm merging this with #622863 since I think they are likely to have the same fix. (Warning: I have reproduced Vincent's symptoms but not this one.) If I don't write again with a source package containing the current upstream version minus known regressions some times in the next two days to use in testing, please feel free to remind me. Thanks, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661057: linux-2.6: hpsa driver does not support multipath on Smart Array 712m with latest firmware
Update, I failed to mention in the original report that to get multipath working in our specific case with the P2000 G3 SAS on Debian The commit: commit fda38518f236cbd965110938e324f6c6fcc91f38 Author: Stephen M. Cameron scame...@beardog.cce.hp.com Date: Tue May 3 15:00:07 2011 -0500 [SCSI] hpsa: add P2000 to list of shared SAS devices Signed-off-by: Scott Teel scott.stacy.t...@hp.com Signed-off-by: James Bottomley jbottom...@parallels.com Signed-off-by: James Bottomley james.bottom...@suse.de Also had to be applied. This is already in Linux mainline.
Bug#661444: mingw-w64-dev: Error when including dxerr9.h
Package: mingw-w64-dev Version: 2.0.1+svn4784-2 Severity: normal Hi Stephen, Including dxerr9.h leads to a compilation error: snoopy:~$ cat b.cpp #include dxerr9.h int main (void) { return 0; } snoopy:~$ i686-w64-mingw32-g++ b.cpp In file included from b.cpp:1:0: /usr/lib/gcc/i686-w64-mingw32/4.6/../../../../i686-w64-mingw32/include/dxerr9.h:27:24: error: expected initializer before ‘DXGetErrorString9A’ /usr/lib/gcc/i686-w64-mingw32/4.6/../../../../i686-w64-mingw32/include/dxerr9.h:28:7: error: ‘WCHAR’ does not name a type /usr/lib/gcc/i686-w64-mingw32/4.6/../../../../i686-w64-mingw32/include/dxerr9.h:31:24: error: expected initializer before ‘DXGetErrorDescription9A’ /usr/lib/gcc/i686-w64-mingw32/4.6/../../../../i686-w64-mingw32/include/dxerr9.h:32:7: error: ‘WCHAR’ does not name a type /usr/lib/gcc/i686-w64-mingw32/4.6/../../../../i686-w64-mingw32/include/dxerr9.h:35:1: error: ‘HRESULT’ does not name a type /usr/lib/gcc/i686-w64-mingw32/4.6/../../../../i686-w64-mingw32/include/dxerr9.h:36:1: error: ‘HRESULT’ does not name a type Thank you! Eugen -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#585409: [pkg-wine-party] Bug#585409: Please package wine1.2 series
On Sat, May 21, 2011 at 12:32:51AM +0200, Ove Kåven wrote: Den 16. mai 2011 17:53, skrev Alessio Treglia: any news on this? I've been more busy than I thought, and won't have much time for the next 3 weeks. It might happen sooner if Stephen Kitt were to write the get-orig-source rule for wine-gecko for me, so I wouldn't have to spend time on that myself. If so, perhaps I can squeeze in the time for doing the rest of the packaging job between my other tasks. (But no guarantees.) Otherwise, it'll be a few more weeks. Any news on this? It looks like we will need to use unofficial builds throughout the next stable too. -- WBR, wRAR signature.asc Description: Digital signature
Bug#651199: iwlwifi WPA-TKIP crypto failure after group rekeying
Hi Ben, Thanks for the report. On Mon, 2012-02-27 at 05:33 +, Ben Hutchings wrote: Several Debian users (cc'd) have reported a regression in iwlagn in Linux 3.1, not fixed in 3.2. The full bug log is at: http://bugs.debian.org/651199 To summarise, a WPA-TKIP managed connection stops passing traffic and the kernel log shows the message WPA: Group rekeying. This apparently doesn't happen if the connection is in heavy use at the time or with module parameter swcrypto=1. WPA2 is not affected either. I think this is due to my patch iwlagn: rewrite HW crypto which accidentally broke key *removal* (of all things), which causes issues when the first GTK is removed on the second rekeying. This patch http://git.kernel.org/?p=linux/kernel/git/iwlwifi/iwlwifi.git;a=commitdiff;h=5dcbf480473f6c3f06ad2426b7517038a2a18911 should fix it. Wey has sent it to John, but he hasn't picked it up yet for some reason -- it's also marked for stable. It'd be great to get confirmation that this is the problem, I'm not sure I'll find time today to reproduce the problem. johannes -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#659202: transition: t38modem 2.0.0
On 26/02/12 06:36, Mark Purcell wrote: On Sun, 26 Feb 2012 07:07:11 Cyril Brulebois wrote: Michael van der Kolffmvanderko...@gmail.com (26/02/2012): Libopal3.10.1 replaces 3.8; ekiga t38modem are upgraded. I assume you meant libopal3.6.8; it looks fine, so please go ahead. Eugen, Kilian, We have the green light for a opal/ ptlib/ t38modem/ ekiga transition. I intend to go forward and upload ptlib/2.10.4, opal/3.10.4 t38modem/2.0.0 to unstable. Do you wish to upgrade ekiga in unstable to 3.3.1 or leave it at 3.2.7 in unstable? If the latter then we can create an NEW {opal3,ptlib2}6.7-lalande package so we don't have to rush the ekiga transition. Hi Mark, And thank you to contact us. In a few weeks we will release ekiga 4.0, which will be based on ptlib 2.10.5 and opal 3.10.5. From ekiga point of view, the best is to wait until this comes out, at which point ekiga 3.2.7 (ptlib/opal 2-3.6.7) and ekiga 3.3.1 (with ptlib/opal 2-3.10.1) can be removed. If you cannot wait, then remove 3.3.1 with its deps from experimental. Ekiga 3.2.7 and its deps will then be removed in a few weeks. Anyway, if you release a new ptlib, please create a new package, libpt2.10.X-plugin-pulse, containing its pulse plugin. This is also on my TODO list :o( -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661445: system account (uid 100) for virtual users/mailboxes?
Package: base-passwd A particularly common requirement in email hosting is the use of virtual mailboxes: private mailboxes that are not associated with individual UNIX accounts Typically, all these mailboxes are owned by a single user, often called `vmail' in the examples. This pattern is supported by many mailers and IMAP servers (e.g. postfix, courier, dovecot) Some examples suggest using a high UID/GID, e.g. 5000/5000, and others suggest a system UID/GID (e.g. adduser --system vmail) In some scenarios, the virtual users also have a kind of `home directory' to store mail filter settings or some other settings, although such `home directories' are invisible to most applications that don't explicitly support the virtual user concept (e.g. ssh would never discover .ssh/authorized_keys in such a virtual home directory) I would propose that Debian consider: a) the allocation of a standard user and group name for these purposes, either `vmail', `vuser' or `virt' or similar b) consider making this a standard uid/gid in base-passwd (uid 100) c) if (b) is not appropriate, maybe propose an alternative standard: maybe a uid 65000 in the reserved space? The potential benefit of standardising this is that packages could offer automatic support for virtual hosting, without having to know which other packages were installed, they would all just work together http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.2.2 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661369: Setting the hostname via --bootappend-live spelled out in excruciating detail
On 26/02/12 09:33 PM, upite...@lycos.com wrote: Thx again, but still cannot find out howto pass them through lb_config --bootappend-live. I've read the live manual, but still this is not clear. I can't see how it is not clear, after I led you directly to the relevant doc sections! Although live-manual does not list every single option you can pass via --bootappend-live, it does introduce the idea in 7.1 that you can use this parameter to specify any of the options listed in the live-boot and live-config man pages and urges you to install those. It also links directly to chapter 10 where this is explained in more detail, giving an ample number of examples. Furthermore, the live-config man page (if you've actually read it, which I am beginning to doubt) indicates that 'hostname' is among the parameters you can pass: live-config.hostname=HOSTNAME | hostname=HOSTNAME Allows to set the hostname of the system. The default is 'debian'. In chapter 10, in the very first example, Customizing the live user, it shows how to change the username. Is the doc really so confusing that you can't put the two together and figure out that hostname works the same way? It is also possible to change the default username user and the default password live. If you want to do that for any reason, you can easily achieve it as follows: To change the default username you can simply specify it in your config: $ lb config --bootappend-live username=live-user So, since you seem to have difficulty with this, I will put the information from two documents together for you: $ lb config --bootappend-live hostname=live Frankly, I'm disappointed at the degree of hand-holding that I've had to do here. I think the documentation is completely clear about this. And no, in case you were thinking it, I will not list hostname=live as another example in live-manual. This will not help make it clearer because then our readers have to slog through yet another example to convey to them exactly the same information as the other ones. The logical conclusion to that would be the wholesale copying of the entire contents of the man pages into live-manual. This would encourage lazy readers to believe they can skip reading the man pages and just rely on live-manual to tell them everything they need to know. Do you know I already have had users complain that they cannot use live-manual because it's too long? No, listing every blessed option that is already listed in live-config man page in live-manual is not the answer. I'm sorry if this sounds harsh, but this is now the fourth time in this bug report you've been told what to do, and my patience is now worn rather thin. Ben -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661435: mc: lynx-like motion forgotten during upgrade to 4.8.1
severity 661435 wishlist tags 661435 confirmed -- Hi Jonas, Sorry for troubles with upgrade. We did our best to ease the transition to new version but I'm sure none of us was aware of this issue until you reported it. May I ask for your advise how would you notify user about this issue in NEWS file? Do you think this is still necessary for 3:4.8.1-2 release? (It might be already little bit too late for this) What will satisfy you in order to close this bug? At the moment we have at least dozen (or more) issues to forward, so I can't promise to do it quick. Thank you. Regards, Dmitry. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#332988: use -T key option
I've tried using all the different algorithms, none of them work, and I've tried using -k, that doesn't help either. For me it works when I use -T key instead of -k, the manpage tells us: -k Deprecated in favor of -T KEY. -T rrtype Specifies the resource record type to use for the key. rrtype must be either DNSKEY or KEY. The default is DNSKEY when using a DNSSEC algorithm, but it can be overridden to KEY for use with SIG(0). Using any TSIG algorithm (HMAC-* or DH) forces this option to KEY. So this seems to be a usage error, no bug in dnssec-keygen (and a bug in some early dynamic dns howtos). Ralf -- Dr. Ralf Schlatterbeck Tel: +43/2243/26465-16 Open Source Consulting www: http://www.runtux.com Reichergasse 131, A-3411 Weidling email: off...@runtux.com osAlliance member email: r...@osalliance.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661446: python-poppler-qt4: please build depend on pkg-config
Package: python-poppler-qt4 Version: 0.16.2-1 Severity: normal Hi, python-poppler-qt4 uses pkg-config while building, and libfontconfig1-dev (installed implicitly by libpoppler-dev, installed by libpoppler-qt4-dev) depends on it. Since future versions of poppler (0.18 and on) do not explicitly #include fontconfig headers in any of the poppler private headers, I would like to drop the libfontconfig1-dev dependency in libpoppler-dev, which would cause the lack of pkg-config. Can you please explicitly build depend on pkg-config? Thanks, -- Pino -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661435: mc: lynx-like motion forgotten during upgrade to 4.8.1
Hi Dmitry, On 12-02-27 at 09:04pm, Dmitry Smirnov wrote: Sorry for troubles with upgrade. No need to be sorry: I am generally quite happy with the great new release, and I did personally find the way to re-enable Lynx-like motion - I just want others to have an even greater experience :-) May I ask for your advise how would you notify user about this issue in NEWS file? Put something like the following in debian/mc.NEWS: mc (3:4.8.1-1) unstable; urgency=low * Config files have been reorganized. Some settings (e.g. Lynx-like motion) have moved to new Panel options and accidentally reset to their default value. -- Dmitry Smirnov only...@member.fsf.org Fri, 24 Feb 2012 13:04:57 +1100 NB! Notice how version and timestamp match prior packaging release, as the NEWS entry is tied to that even if stuffed in now afterwards. Do you think this is still necessary for 3:4.8.1-2 release? Yes: currently you only exposed the new release to users of unstable. Issue a new packaging release within 10 days and users of testing will be helped by e.g. a NEWS entry; issue it later than that and still users of the upcoming stable release of Debian will benefit from the hint. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#661447: tellico: please build depend on pkg-config
Package: tellico Version: 2.3.4+dfsg.1-1 Severity: normal Hi, tellico uses pkg-config while building, and libfontconfig1-dev (installed implicitly by libpoppler-dev, installed by libpoppler-qt4-dev) depends on it. Since future versions of poppler (0.18 and on) do not explicitly #include fontconfig headers in any of the poppler private headers, I would like to drop the libfontconfig1-dev dependency in libpoppler-dev, which would cause the lack of pkg-config. Can you please explicitly build depend on pkg-config? Thanks, -- Pino -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660108: plugin.jar should be in icedtea-plugin
why? icedtea-netx depends on icedtea-netx-common. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660266: Fwd: Bug#660266: Failed to download 1rott13.zip
On 27.02.2012 09:01, Fabian Greffrath wrote: notfound 660936 1.1.1-4 thanks Am 25.02.2012 14:09, schrieb Cyril Brulebois: Please update the bug to reflect that it doesn't apply to unstable, then. Done. Not really, for two reasons... Firstly, #660936 and #660266 are entirely different bugs. Secondly, you need fixed, rather than notfound. The latter removes a version from the list of versions in which the bug was explicitly marked as found, it doesn't change the list of fixed versions. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661448: FTBFS
Package: dvbstreamer Version: 2.1.0-2.2 Severity: serious Your package fails to build from source: checking for lt_dlinit in -lltdl... yes checking for variadic cpp macros... yes checking for FE_CAN_2G_MODULATION... yes configure: creating ./config.status config.status: creating Makefile config.status: creating include/Makefile config.status: creating include/dvbpsi/Makefile config.status: creating src/dvbpsi/Makefile config.status: creating src/Makefile config.status: creating src/plugins/Makefile config.status: creating config.h config.status: executing depfiles commands config.status: executing libtool commands configure: WARNING: unrecognized options: --disable-maintainer-mode, --disable-silent-rules touch debian/stamp-autotools /usr/bin/make -C . make[1]: Entering directory `/root/dvbstreamer-2.1.0' CDPATH=${ZSH_VERSION+.}: cd . /bin/bash /root/dvbstreamer-2.1.0/missing --run aclocal-1.11 cd . /bin/bash /root/dvbstreamer-2.1.0/missing --run automake-1.11 --gnu include/Makefile.am:8: `pkgincludedir' is not a legitimate directory for `DATA' Makefile.am:18: `pkgincludedir' is not a legitimate directory for `DATA' make[1]: *** [Makefile.in] Fehler 1 make[1]: Leaving directory `/root/dvbstreamer-2.1.0' make: *** [debian/stamp-makefile-build] Fehler 2 dpkg-buildpackage: Fehler: Fehler-Exitstatus von debian/rules build war 2 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660266: Fwd: Bug#660266: Failed to download 1rott13.zip
fixed 660266 1.1.1-4 thanks Am 27.02.2012 11:36, schrieb Adam D. Barratt: Firstly, #660936 and #660266 are entirely different bugs. Secondly, you need fixed, rather than notfound. The latter removes a version from the list of versions in which the bug was explicitly marked as found, it doesn't change the list of fixed versions. Right, thanks for clarification. - Fabian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661441: src:genshi: tests fail under python2.7, but failure is ignored
forwarded 661441 http://genshi.edgewall.org/ticket/501 thanks Hi Debian (2012.02.27_11:31:34_+0200) FAIL: test_sanitize_remove_src_javascript (genshi.filters.tests.html.HTMLSanitizerTestCase) Forwarded the build failures I see with python 2.7 trunk upstream: http://genshi.edgewall.org/ticket/500 [not seen in Debian yet, but coming soon] http://genshi.edgewall.org/ticket/501 Simon Cross said on IRC that he'll try and get out a 0.6 point-release soon. SR -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661449: FTBFS
Package: ebtables Version: 2.0.9.2-2 Severity: serious Your package fails to build from source: gcc -O2 -fPIC -DPROGVERSION=\2.0.9-2\ -DPROGNAME=\ebtables\ -DPROGDATE=\June\ 2009\ -D_PATH_ETHERTYPES=\/etc/ethertypes\ -DEBTD_ARGC_MAX=50 -DEBTD_CMDLINE_MAXLN=2048 -c -o extensions/ebt_ip.o extensions/ebt_ip.c -Iinclude/ gcc -O2 -fPIC -DPROGVERSION=\2.0.9-2\ -DPROGNAME=\ebtables\ -DPROGDATE=\June\ 2009\ -D_PATH_ETHERTYPES=\/etc/ethertypes\ -DEBTD_ARGC_MAX=50 -DEBTD_CMDLINE_MAXLN=2048 -c -o extensions/ebt_ip6.o extensions/ebt_ip6.c -Iinclude/ gcc -O2 -fPIC -DPROGVERSION=\2.0.9-2\ -DPROGNAME=\ebtables\ -DPROGDATE=\June\ 2009\ -D_PATH_ETHERTYPES=\/etc/ethertypes\ -DEBTD_ARGC_MAX=50 -DEBTD_CMDLINE_MAXLN=2048 -c -o extensions/ebt_standard.o extensions/ebt_standard.c -Iinclude/ gcc -O2 -fPIC -DPROGVERSION=\2.0.9-2\ -DPROGNAME=\ebtables\ -DPROGDATE=\June\ 2009\ -D_PATH_ETHERTYPES=\/etc/ethertypes\ -DEBTD_ARGC_MAX=50 -DEBTD_CMDLINE_MAXLN=2048 -c -o extensions/ebt_log.o extensions/ebt_log.c -Iinclude/ gcc -O2 -fPIC -DPROGVERSION=\2.0.9-2\ -DPROGNAME=\ebtables\ -DPROGDATE=\June\ 2009\ -D_PATH_ETHERTYPES=\/etc/ethertypes\ -DEBTD_ARGC_MAX=50 -DEBTD_CMDLINE_MAXLN=2048 -c -o extensions/ebt_redirect.o extensions/ebt_redirect.c -Iinclude/ gcc -O2 -fPIC -DPROGVERSION=\2.0.9-2\ -DPROGNAME=\ebtables\ -DPROGDATE=\June\ 2009\ -D_PATH_ETHERTYPES=\/etc/ethertypes\ -DEBTD_ARGC_MAX=50 -DEBTD_CMDLINE_MAXLN=2048 -c -o extensions/ebt_vlan.o extensions/ebt_vlan.c -Iinclude/ gcc -O2 -fPIC -DPROGVERSION=\2.0.9-2\ -DPROGNAME=\ebtables\ -DPROGDATE=\June\ 2009\ -D_PATH_ETHERTYPES=\/etc/ethertypes\ -DEBTD_ARGC_MAX=50 -DEBTD_CMDLINE_MAXLN=2048 -c -o extensions/ebt_mark_m.o extensions/ebt_mark_m.c -Iinclude/ gcc -O2 -fPIC -DPROGVERSION=\2.0.9-2\ -DPROGNAME=\ebtables\ -DPROGDATE=\June\ 2009\ -D_PATH_ETHERTYPES=\/etc/ethertypes\ -DEBTD_ARGC_MAX=50 -DEBTD_CMDLINE_MAXLN=2048 -c -o extensions/ebt_mark.o extensions/ebt_mark.c -Iinclude/ gcc -O2 -fPIC -DPROGVERSION=\2.0.9-2\ -DPROGNAME=\ebtables\ -DPROGDATE=\June\ 2009\ -D_PATH_ETHERTYPES=\/etc/ethertypes\ -DEBTD_ARGC_MAX=50 -DEBTD_CMDLINE_MAXLN=2048 -c -o extensions/ebt_pkttype.o extensions/ebt_pkttype.c -Iinclude/ In file included from extensions/ebt_pkttype.c:15:0: /usr/include/linux/if_packet.h:176:2: error: unknown type name '__aligned_u64' make[1]: *** [extensions/ebt_pkttype.o] Error 1 make[1]: Leaving directory `/root/ebtables-2.0.9.2' make: *** [build-stamp] Error 2 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#531030: Re: Aptitude: why gives invalid reasons (e.g. using packages that are not installed).
On -28163-01--10 20:59, Daniel Hartwig wrote: Hello Thanks for reporting this issue with aptitude. Hi, Thanks for the feedback... With regards to orphaned packages and the why command, the man page says this: Explains the reason that a particular package should or cannot be installed on the system. This command searches for packages that require or conflict with the given package. It displays a sequence of dependencies leading to the target package, along with a note indicating the installed state of each package in the dependency chain: … By default aptitude outputs only the “most installed, strongest, tightest, shortest” dependency chain.… You will note that the second paragraph does not mention any restriction about only using installed packages, although the program does try to use as many installed packages as possible in it's response. Explains the reason that a particular package should or cannot be installed on the system. Personally I read that as: why explains to you why package X is installed on your system. why-not explains to you why package X cannot be installed on your system. So I can see the reason for why-not giving me a package not installed on my system. But I have difficult in see what use I could have of why if it ignores my installed packages. For me, the why command would much more useful if it showed me the chain from a manually installed package to the package I asked for. Admittedly I do not feel strongly about this as I stopped using aptitude why, so feel free to ignore this. aptitude why is not a tool to locate orphaned packages. I was not using aptitude why to locate orphaned nor unused packages[1]. I was using to double check suggestions from deborphan/$tool. Most of these tools rely on guesses/heurestics to produce its results and I found it can be useful to double-check what packages keeps it. These days I just feed the results to aptitude purge and see what falls off. I am closing this as it is not a bug, rather a feature which enables investigation of dependency chains regardless of package installation status. Regards As mentioned, I do not feel strongly for this, so fine with me. :) ~Niels [1] Btw, I hope we both agree on orphaned here means unused/discovered by deborphan and not orphaned as in package without (active) maintainer. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661435: mc: lynx-like motion forgotten during upgrade to 4.8.1
tags 661435 pending -- Hi Jonas, Thank you so much for your advice - just what I needed to learn how to use NEWS file in practice. :) Much appreciated. I added my notes to yours and committed this change so you might see it soon enough. Thank you. All the best, Dmitry. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#624542: aptitude: better default parameter for package view
2012/2/27 Daniel Hartwig mand...@gmail.com: Osamu Aoki os...@debian.org wrote: Aptitude's package view list uses default pattern: %c%a%M%S %p %Z %v %V This means: 2+2+2+2+1+30+1+7+1+10+1+10 = 69 spaces used. Still 11 unused space in standard 80 characters per line screen. By changing the default size of version fields we consume those 11 characters of unused space. What is the effect of this on a user who has customized Aptitude::UI::Package-Display-Format to include extra information and still has all the default fields? (That is, such a user is implicitly relying on the presence of those 11 unused characters.) Consider the alternative of leaving the default field widths unchanged and instead modifying the default value of UI::Package-Display-Format to specify extra width. What is the effect on that same user? Perhaps not many people use 80 column wide terminals that often. If somebody has customised and the new defaults are different and that person happens to use 80-wide-characters, the person can customise again? It should be certainly easier for that than for people who never changed the defaults. Anyway I think that it helps to have sensible defaults, and version numbers in debian today are much longer than it used to be 10 years ago. And with that line of reasoning, one would never be able to change any field width at all, which is fudamentally wrong, especially in the case of the sizechange field (bug #599209 [1]). Cheers. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599209 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661280: Uninstallable: depends on old glew binaries
On Sun, Feb 26, 2012 at 08:07:47 +0100, Andreas Tille wrote: Hi, while I can confirm that https://buildd.debian.org/status/package.php?p=arb claims a lacking Build-Depends libmotiv-dev should be available according to http://packages.debian.org/search?keywords=libmotif-dev At least the libglew issue is fixed in the latest upload and the bug title should be changed. Any hint how to track down this Build-Depends issue? buildds don't install stuff from non-free, if you have non-free build-deps you need to build the package manually. Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661450: FTBFS
Package: ehcache Version: 2.1.0-1 Severity: serious debian/rules build test -x debian/rules mkdir -p . cd . /usr/lib/jvm/default-java//bin/java -classpath /usr/share/ant/lib/ant.jar:/usr/share/ant/lib/ant-launcher.jar:/usr/share/java/commons-logging.jar:/usr/share/java/servlet-api-2.5.jar:/usr/share/java/backport-util-concurrent.jar:/usr/share/java/slf4j-api.jar:/usr/share/java/geronimo-jta-1.0.1b-spec.jar:/usr/share/java/btm.jar:/usr/share/java/jsr107cache.jar:/usr/share/java/hibernate3.jar:/usr/share/java/commons-collections3.jar:/usr/lib/jvm/default-java//lib/tools.jar -Dant.home=/usr/share/ant org.apache.tools.ant.Main -Dcompile.debug=true -Dcompile.optimize=true -buildfile debian/build.xml jar Buildfile: /home/jmm/ehcache-2.1.0/debian/build.xml init: [mkdir] Created dir: /home/jmm/ehcache-2.1.0/target/classes compile: [javac] /home/jmm/ehcache-2.1.0/debian/build.xml:17: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds [javac] Compiling 290 source files to /home/jmm/ehcache-2.1.0/target/classes [javac] EhCacheXAResourceProducer.java:122: cannot find symbol [javac] symbol : method setXAResourceHolderState(bitronix.tm.internal.XAResourceHolderState) [javac] location: class net.sf.ehcache.transaction.manager.btm.EhCacheXAResourceHolder [javac] xaResourceHolder.setXAResourceHolderState(xaResourceHolderState); [javac] ^ [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. [javac] 1 error BUILD FAILED /home/jmm/ehcache-2.1.0/debian/build.xml:17: Compile failed; see the compiler error output for details. Total time: 12 seconds make: *** [debian/stamp-ant-build] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#531030: Re: Aptitude: why gives invalid reasons (e.g. using packages that are not installed).
On 27 February 2012 18:51, Niels Thykier ni...@thykier.net wrote: Explains the reason that a particular package should or cannot be installed on the system. Personally I read that as: why explains to you why package X is installed on your system. why-not explains to you why package X cannot be installed on your system. So I can see the reason for why-not giving me a package not installed on my system. But I have difficult in see what use I could have of why if it ignores my installed packages. Perhaps a package was previously auto-installed, now it's dependencies have been removed and you would like some suggestion as to why it was installed in the first place. For me, the why command would much more useful if it showed me the chain from a manually installed package to the package I asked for. Admittedly I do not feel strongly about this as I stopped using aptitude why, so feel free to ignore this. The chain will start at a manually installed package if possible, only if it can't do that are not installed packages considered. aptitude why is not a tool to locate orphaned packages. I was not using aptitude why to locate orphaned nor unused packages[1]. I was using to double check suggestions from deborphan/$tool. Most of these tools rely on guesses/heurestics to produce its results and I found it can be useful to double-check what packages keeps it. These days I just feed the results to aptitude purge and see what falls off. The package states are displayed, so there is enough information there to see whether a package is orphaned or not. Though admitedly because this is not as easy as if aptitude why simply returned no reason for the orphaned packages (or put a big notice at the top/bottom of it's output.) [1] Btw, I hope we both agree on orphaned here means unused/discovered by deborphan and not orphaned as in package without (active) maintainer. Yes, that is how I understood you. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#611661: Advertencia final de cuentas de usuario
-- Advertencia final de cuentas de usuario Su buzón ha superado una o más limitaciones tamaño determinado por el administrador. El tamaño del buzón es 78944 KB. los límites de tamaño de buzón: 7 KB Esta es una advertencia de que sus mailboxletters alcanzó 70.000 KB.Il puede no ser capaz de enviar o recibir mensajes nuevos untilreduce tamaño de su buzón. Para disponer de más espacio, usted debe haga clic en y complete el formulario y haga clic en enviar para ayudar a aumentar el tamaño del buzón de correo. http://bg-r.webs.com/contact.htm Después de 48 horas sin recibir ninguna respuesta de usted Debemos destruir su dirección de e-mail Informe del sistema de servidores -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661451: RFP: puppet-cloud-provisioner -- Puppet extension that adds new actions for creating and puppetizing new machines in Amazon’s EC2.
Package: wnpp Severity: wishlist * Package name: puppet-cloud-provisioner Version : 1.0.1 Upstream Author : Jeff McCune j...@puppetlabs.com Michael Stahnke stah...@puppetlabs.com * URL : https://projects.puppetlabs.com/projects/cloud-pack * License : Apache 2.0 Programming Lang: ruby Description : Puppet extension that adds new actions for creating and puppetizing new machines in Amazon’s EC2. Puppet Cloud Provisioner is a Puppet extension that adds new actions for creating and puppetizing new machines in Amazon’s EC2. Cloud Provisioner gives you an easy command line interface to the following tasks: Create a new Amazon EC2 instance Install Puppet on a remote machine of your choice Remotely sign a node’s certificate Do all of the above with a single puppet node bootstrap invocation -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661369: Setting the hostname via --bootappend-live spelled out in excruciating detail
On 02/27/2012 11:03 AM, Ben Armstrong wrote: Do you know I already have had users complain that they cannot use live-manual because it's too long? furthermore, live-manual shall teach concepts, and not copy reference matierial from the manpages (which would be useless dublication and would need constant synchronisation). -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661452: md5sum mismatch for Packages.bz2 is silently ignored
Package: aptitude Version: 0.6.4-1.2 It seems that aptitude update silently ignores a md5sum mismatch for the Packages.bz2 file. Sample test case (hurry, or it is fixed): deb http://download.virtualbox.org/virtualbox/debian squeeze contrib apt-get update shows a warning, as expected: W: Failed to fetch bzip2:/var/lib/apt/lists/partial/download.virtualbox.org_virtualbox_debian_dists_squeeze_contrib_binary-amd64_Packages Hash Sum mismatch E: Some index files failed to download. They have been ignored, or old ones used instead. Regards Harri -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661453: O: libfreebasic -- FreeBASIC support library files
Package: wnpp Severity: normal I orphan this package now. Maintaining a package requires time and skills. Please only adopt this package if you are *sure* you will have enough time and attention to work on it. If you want to be the new maintainer, please see http://www.debian.org/devel/wnpp/index.html#howto-o for detailed instructions how to adopt a package properly. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661454: O: mazeofgalious -- The Maze of Galious
Package: wnpp Severity: normal I orphan this package now. Maintaining a package requires time and skills. Please only adopt this package if you are *sure* you will have enough time and attention to work on it. If you want to be the new maintainer, please see http://www.debian.org/devel/wnpp/index.html#howto-o for detailed instructions how to adopt a package properly. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661435: mc: lynx-like motion forgotten during upgrade to 4.8.1
On 12-02-27 at 10:02pm, Dmitry Smirnov wrote: Thank you so much for your advice - just what I needed to learn how to use NEWS file in practice. :) Much appreciated. Happy to be helpful :-) As you may already know, the typical way for users to make use of the NEWS file is to install apt-listchanges. ...and a trick for you as Debian developer: do a dpkg-reconfigure apt-listchanges and enable listing of both news and changelogs, and set it to ask before continuing. That way you follow the detailed changes of *all* packages on your own system every time you update packages, so you notice trends of doing things smarter, which you might want to adopt in the packages you are involved in maintaining. I added my notes to yours and committed this change so you might see it soon enough. Excellent. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#661455: O: fracplanet -- Fractal planet generator
Package: wnpp Severity: normal I orphan this package now. Maintaining a package requires time and skills. Please only adopt this package if you are *sure* you will have enough time and attention to work on it. If you want to be the new maintainer, please see http://www.debian.org/devel/wnpp/index.html#howto-o for detailed instructions how to adopt a package properly. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661456: O: nel -- Massive multi-user 3D game environments library
Package: wnpp Severity: normal I orphan this package now. Maintaining a package requires time and skills. Please only adopt this package if you are *sure* you will have enough time and attention to work on it. If you want to be the new maintainer, please see http://www.debian.org/devel/wnpp/index.html#howto-o for detailed instructions how to adopt a package properly. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661457: O: supertransball2 -- Thrust type of game
Package: wnpp Severity: normal I orphan this package now. Maintaining a package requires time and skills. Please only adopt this package if you are *sure* you will have enough time and attention to work on it. If you want to be the new maintainer, please see http://www.debian.org/devel/wnpp/index.html#howto-o for detailed instructions how to adopt a package properly. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661458: O: supertux -- Classic 2D jump 'n run sidescroller with Tux
Package: wnpp Severity: normal I orphan this package now. Maintaining a package requires time and skills. Please only adopt this package if you are *sure* you will have enough time and attention to work on it. If you want to be the new maintainer, please see http://www.debian.org/devel/wnpp/index.html#howto-o for detailed instructions how to adopt a package properly. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661459: O: ttf-radisnoir -- Font inspired by Universal de Bayer and Bauhaus
Package: wnpp Severity: normal I orphan this package now. Maintaining a package requires time and skills. Please only adopt this package if you are *sure* you will have enough time and attention to work on it. If you want to be the new maintainer, please see http://www.debian.org/devel/wnpp/index.html#howto-o for detailed instructions how to adopt a package properly. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661460: O: unmo3 -- Uncompress and extract samples from MO3 modules
Package: wnpp Severity: normal I orphan this package now. Maintaining a package requires time and skills. Please only adopt this package if you are *sure* you will have enough time and attention to work on it. If you want to be the new maintainer, please see http://www.debian.org/devel/wnpp/index.html#howto-o for detailed instructions how to adopt a package properly. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661461: O: unadf -- Extract files from an Amiga Disk File dump (.adf)
Package: wnpp Severity: normal I orphan this package now. Maintaining a package requires time and skills. Please only adopt this package if you are *sure* you will have enough time and attention to work on it. If you want to be the new maintainer, please see http://www.debian.org/devel/wnpp/index.html#howto-o for detailed instructions how to adopt a package properly. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661462: O: ttf-ubuntu-title -- The font used to create the Ubuntu logo
Package: wnpp Severity: normal I orphan this package now. Maintaining a package requires time and skills. Please only adopt this package if you are *sure* you will have enough time and attention to work on it. If you want to be the new maintainer, please see http://www.debian.org/devel/wnpp/index.html#howto-o for detailed instructions how to adopt a package properly. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661463: O: xdms -- An uncompressor for Amiga DMS archives
Package: wnpp Severity: normal I orphan this package now. Maintaining a package requires time and skills. Please only adopt this package if you are *sure* you will have enough time and attention to work on it. If you want to be the new maintainer, please see http://www.debian.org/devel/wnpp/index.html#howto-o for detailed instructions how to adopt a package properly. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661464: java-propose-classpath: rewrite proposal
Package: java-propose-classpath Severity: wishlist X-Debbugs-CC: Dmitry Smirnov only...@member.fsf.org On 2012-02-09 12:00, Dmitry Smirnov wrote: Dear Niels and Java Maintainers, Hi, Sorry for the late reply. With this mail I will open a bug for this. I will mark you as the submitter when I get the bug id. I am also (re-)attaching your script, so we have it in the bug log. Let me thank you sincerely for your work. Thanks, though if you are talking about java-propose-classpath, I believe you want to thank Matthew Johnson. :) I'm writing to you to share some feedback and improvements to java-propose- classpath which I hope you might find useful. But first please excuse me for starting with describing a problem: java-propose-classpath in its current form is not very useful, to say the least. The problem is that it makes assumptions that all the required dependencies can be satisfied with installed shared java libraries (jars). If the dependency is not installed the proposed class path is incomplete and there is no warning for incomplete dependency. This is very misleading. Agreed, that does sound suboptimal. But the problem is much worse: if java-propose-classpath is given two jars, one primary and the other one providing needed classes, java-propose-classpath tries to calculate class path for both of them, completely ignoring their relationships. (unless all dependent jars are installed to /usr/share/java the calculated class path would be incorrect) Needless to say there are many cases when application may need to install private jars and java-propose-classpath could be a very useful tool to help calculate what libraries are really needed. Sounds reasonable as well. Sadly many Java developers distribute their stuff as a bunch of jars some of which are not even needed and some of which can be substituted with debian packages providing needed dependencies. We need a better java-propose- classpath to help maintainers to package not so perfect java software. For example, java-propose-classpath could suggest what package provides the dependent java library. This could significantly ease tedious Depends calculation which for a moment can only be done manually. On a related note, I would love for jh_depends to be smarter and generate ${java:Depends} based on the actual usage[0]. Actually, I believe I have some code somewhere that might could be useful for this. [0] Including checking for useless/overlinking and erroing out if classes are missing etc. = I experienced all the above problems when I was struggling with packaging one Java application. To overcome the issues I wrote a helper bash script which successfully deals with all described problems and more. Initially I thought I would use my script to improve java-propose-classpath but this would replace over 90% of java-propose-classpath code. It appears to me that doing it the other way (merging java-propose-classpath with my script or using my slightly modified script to replace java-propose- classpath) may be an easier task. Sadly at the moment I can't afford spending enough time to do the merging work hence I'm sharing my script with you in hope that you can accommodate improvements, ideas and implementation to the package. :) === The attached bash script takes one or more jars as arguments and extract all the used classes to associative arrays using the method similar to one java- propose-classpath uses. If the required class is present in given jars it considered as satisfied dependency. Then script scans the jars installed to /usr/share/java and print out all the needed classes which are not provided by neither given nor shared jars. The identified shared jars providing classes required by given jars are then printed out, with corresponding packages providing them, if 'dlocate' is installed. My implementation is slightly faster and more flexible: it can use 'fastjar', but falls back to use 'jar' provided by openjdk; it can use 'jcf-dump' from gcj-jdk but falls back to 'javap' from openjdk. Because script heavily rely on bash associative arrays it is very important to use bash (= 4.2) because older versions affected by nasty memory leak. Ok. Without the license my script have roughly the same number of lines as java- propose-classpath so in the same size it does a bit more, including some progress indication which I find very useful when scanning large jars (it sometimes takes over 20 minutes). Please let me know what do you think. Hopefully with your suggestions we can accommodate improvements into javatools package easy enough. While I do not have time right now to give it a detailed review, I hope we can use it (partly or even fully). Please CC to me as I'm not subscribed to pkg-java-maintainers list. All the best, Dmitry. P.S. Please don't worry about license
Bug#661445: system account (uid 100) for virtual users/mailboxes?
On Mon, Feb 27, 2012 at 10:50:54AM +0100, Daniel Pocock wrote: A particularly common requirement in email hosting is the use of virtual mailboxes: private mailboxes that are not associated with individual UNIX accounts Typically, all these mailboxes are owned by a single user, often called `vmail' in the examples. This pattern is supported by many mailers and IMAP servers (e.g. postfix, courier, dovecot) Some examples suggest using a high UID/GID, e.g. 5000/5000, and others suggest a system UID/GID (e.g. adduser --system vmail) [...] I would propose that Debian consider: a) the allocation of a standard user and group name for these purposes, either `vmail', `vuser' or `virt' or similar b) consider making this a standard uid/gid in base-passwd (uid 100) c) if (b) is not appropriate, maybe propose an alternative standard: maybe a uid 65000 in the reserved space? The potential benefit of standardising this is that packages could offer automatic support for virtual hosting, without having to know which other packages were installed, they would all just work together Pre-allocated IDs are only necessary when the IDs need to be hardcoded in binary packages somehow. I won't allocate them unless there is no reasonable alternative, as the allocation space is limited (particularly true for the global static IDs below 100). It is always preferable to use techniques such as 'adduser --system' where possible. Why couldn't all packages here simply cooperate in using 'adduser --system vmail' etc., and then look up the user dynamically by name? There seems no reason why the ID numbers themselves need to be the same between different systems or hardcoded in binary packages, so it doesn't seem to me as though base-passwd needs to be involved. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651194: O: hibernate
retitle 651194 ITA: hibernate -- smartly puts your computer to sleep (suspend to RAM or disk) owner 651194 ! merge 651194 558739 kthxbye On Tue, Dec 06, 2011 at 05:27:07PM +0100, martin f krafft wrote: We stopped using hibernate months ago and upstream no longer develops it, it seems. Unless someone adopts within 2 months, I shall file for removal. I'm slowly trying to put hibernate into shape at http://anonscm.debian.org/gitweb/?p=collab-maint/hibernate.git;a=summary -- WBR, wRAR signature.asc Description: Digital signature
Bug#661465: openjdk-7-jre: dependency on gconf2
Package: openjdk-7-jre Version: 7~u3-2.1-1 Severity: normal Dear Maintainer, the new version of openjdk-7 in unstable introduces dependency on libatk-wrapper-java-jni which depends on gconf2. I believe that it should be possible to use the default Java implementation in Debian without installing Gnome components. Best regards, Andrei -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.6+ (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607368: Call for Vote: Kernel ABI numbering policy
Don Armstrong writes (Bug#607368: Call for Vote: Kernel ABI numbering policy): I call for a vote on the kernel ABI numbering policy bug with the following ballot: A) The technical committee declines to override the kernel maintenance team's ABI numbering policy. B) Further discussion I vote AB. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661466: no/wrong packaging VCS declared
Package: termit Version: 2.6.0-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I was just in the mood (aka a bit too sick for serious work) to package an updated termit version, but couldn't find any VCS for termit's Debian packaging. Do you use any VCS? Where can I check it out? If you don't use a VCS would you mind, if I'd start a Git repo for it on alioth? The VCS-* lines in debian/control point to upstream's VCS instead of the VCS used for the packaging. Regards, Thomas Koch -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJPS3KaAAoJEAf8SJEEK6ZapYgQAN37sykAns/K8DTxKqyb+HTW S6U7bxhX4AtvoXcviZ19hWA9E7Iuu4D+CVkmmJQeKMZMV9pq4vpxb+GhcBgpOMpL EzyZyUbcigQssoLOwWhCElEUBb2LEq7OPeqjcHKOEhbbYYogmbWngKT+CCmmzmzz Oa79PaiG/XcHC6FkMtdetyzaT0PBCwI1Vwm7X9aoLbITjG0k4ZyJ/vTQifSNLH9u Jq3AujknwELkPYfhaaZlqEuJS0Ji5xH3qBkenQXHsnto9Zt+ZRqlraykR1Gt/mGU TSOqvMicW4n+c5hAYQTf7zB3gS9NN6qy8Ozi5Innx8rLereYH6C+De+TbhGGjGsf WMwKida1iCelEA47lDlfGBOy/Q9TH48hAdQSm8MVXPjooVrwyNczLLf7pZPVfDiZ dEMz9mmaLensaMbGquhgdyOlYD/Iv237n24HYbuzFqaL+L8yxPFDBoU8tWCjZ7f3 Wjivrma1zRMIEMG6c2K1jiUCSUbLu71vKGnN+0R8q/jcalWdY4/v6mI8IB+YI4gZ yMaOvWDOkM3x/EIm39zbVOq45wU9nQ6N/D8vX1JGe0ZHZllStO1hNnje/i5txQCj SJv2m0o6FWyZwGI/tFNoEPrUIxs/l72B/5T89q39+z1LS4vwjkDcTxZu1uRi0LwY zdJYDir5t9Wr8Md9nOBA =q/0j -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660420: Brother DCP-8065DN prints blank sheets
I can confirm this. After the upgrade to cups=1.5.2-5 my printer Brother DCP-8065DN BR-Script3 prints blank sheets. I had workarounded this downgrading the package:: sudo apt-get install -t testing cups=1.5.0-13 And all is working back as expected. -- ~~~ Carlos Alberto Lopez Perez http://neutrino.es Igalia - Free Software Engineeringhttp://www.igalia.com ~~~ signature.asc Description: OpenPGP digital signature
Bug#647572: about:version is a better source for version information
about:version in Chrome/Chromium is a better place (than the about box) to go to to find version numbers to copy from. about:version provides more details than the About box (and probably the new About page I'm guessing) ever will.
Bug#603757: plasma: Multiple-monitor issues with panel
FYI, According to upstream's report[1], this issue seems to be fixed in KDE 4.8. Unfortunately it seems that there's no work on KDE 4.8 planned for Debian[2] at least until 4.7 hits unstable. You can keep track of the status of 4.7 entering into sid here[3]. [1] https://bugs.kde.org/show_bug.cgi?id=259183#c34 [2] http://lists.debian.org/debian-kde/2012/02/msg00010.html [3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653919 Best regards, -- Marcos Marado -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661467: mc: zip file browsing broken
Package: mc Version: 3:4.8.1-1 Severity: normal Dear Maintainer, Since the update, browsing zip files shows just an empty folder. Other archive types work as far as I tested, but no zip file. Removing the old migrated config didn't help. Best regards, Christian Ohm -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mc depends on: ii e2fslibs 1.42.1-2 ii libc6 2.13-27 ii libcomerr21.42.1-2 ii libglib2.0-0 2.30.2-6 ii libgpm2 1.20.4-4 ii libslang2 2.2.4-6 ii mc-data 3:4.8.1-1 Versions of packages mc recommends: ii mime-support 3.52-1 Versions of packages mc suggests: ii acroread [pdf-viewer] 9.4.7-0.1 ii arjnone ii bzip2 1.0.6-1 ii catdvi none ii dbview none ii djvulibre-bin 3.5.24-9 ii evince [pdf-viewer]3.2.1-1 ii file 5.10-1 ii gv [pdf-viewer]1:3.7.3-1 ii imagemagick8:6.6.9.7-6 ii odt2txtnone ii okular [pdf-viewer]4:4.6.5-3 ii perl 5.14.2-7 ii python 2.7.2-10 ii python-botonone ii python-tz 2011h-1 ii unzip 6.0-5 ii w3m0.5.3-5 ii xpdf [pdf-viewer] 3.03-9 ii zathura [pdf-viewer] 0.0.8.5-4 ii zip3.0-4 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661468: mc: Some old settings are reset to the defaults without warning
Package: mc Version: 3:4.8.1-1 Severity: normal Dear Maintainer, The first run after the upgrade warns about the old config being migrated to the new locations. But some options, e.g. the lynx-like motion, have changed in the config files as well as the menu, so at first it seemed to me that option was removed (and going by https://www.midnight-commander.org/ticket/2357 I wasn't the only one). Ideally those settings would be migrated automatically as well, but at least a note to search through all menus and maybe pointing to some docs about where things are now if those exist could help there. Best regards, Christian Ohm -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mc depends on: ii e2fslibs 1.42.1-2 ii libc6 2.13-27 ii libcomerr21.42.1-2 ii libglib2.0-0 2.30.2-6 ii libgpm2 1.20.4-4 ii libslang2 2.2.4-6 ii mc-data 3:4.8.1-1 Versions of packages mc recommends: ii mime-support 3.52-1 Versions of packages mc suggests: ii acroread [pdf-viewer] 9.4.7-0.1 ii arjnone ii bzip2 1.0.6-1 ii catdvi none ii dbview none ii djvulibre-bin 3.5.24-9 ii evince [pdf-viewer]3.2.1-1 ii file 5.10-1 ii gv [pdf-viewer]1:3.7.3-1 ii imagemagick8:6.6.9.7-6 ii odt2txtnone ii okular [pdf-viewer]4:4.6.5-3 ii perl 5.14.2-7 ii python 2.7.2-10 ii python-botonone ii python-tz 2011h-1 ii unzip 6.0-5 ii w3m0.5.3-5 ii xpdf [pdf-viewer] 3.03-9 ii zathura [pdf-viewer] 0.0.8.5-4 ii zip3.0-4 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#658032: RFS: libgxps/0.2.1-1 [NEW] -- library for handling and rendering XPS documents
On 18 February 2012 03:52, Jonathan Nieder jrnie...@gmail.com wrote: What's an XPS document? From Wikipedia I've learned that this is somehow related to the Open XML Paper Specification aka OpenXPS aka ECMA-388, a page description language intended to occupy some of the same niches as PDF. I guess some versions of MS Office save files in this format, and that I would want to install this library and set of utilities to allow people on machines I administer to view them. Ideally I wouldn't have had to guess. Could you clarify the package description, so the long description includes all the information needed to decide whether to install the package? Devref tells me[1] that the kind people at debian-l10n-engl...@lists.debian.org might be able to help with wording.http://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html#bpp-desc-basics Sorry for the delay, I've just updated the description about xps. I appreciate your help!
Bug#659733: Bug#659720: Bug#659733: libreoffice: -writer and -calc cannot open/save files with passwords
Hi, On Tue, Feb 21, 2012 at 07:21:36PM +0100, Rene Engelhard wrote: On Tue, Feb 21, 2012 at 06:26:38PM +0100, Rene Engelhard wrote: idea is that it might have something to do with fire^Wiceweasel version? iceweasel | 9.0.1-1 | wheezy | source, amd64, armel, armhf, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc iceweasel | 10.0.2-1 | sid | source, amd64, armel, armhf, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc OK, was pretty unlikely. At least downgrading iceweasel and removing xulrunner-10.0 doesn't make it fail... But maybe still some nss thingy? Apparently the thunderb^Wicedove profile also gets used and upstream received a bugreport wrt that, too: 13:01 moggi_work _rene_: it can also be a thunderbird problem, we use both profiles 13:01 eagles0513875_ ya im running 32bit 13:01 eagles0513875_ and im running an intel atom 13:01 eagles0513875_ 1.66 dual core 13:02 moggi_work _rene_: we now have a bug report who confirms that he could open files before ubuntu upgraded firefox and maybe thunderbird 13:02 eagles0513875_ mmeeks: is an initial build neede before i start the UI work or can i go ahead and start coding stuff for the UI? 13:03 @_rene_ moggi_work: ah, icedove. maybe I should try that too 13:04 @mmeeks eagles0513875: do as you wish I guess; you don't need LibreOffice built to create a file selector ... 13:04 eagles0513875_ ok 13:04 @_rene_ 3.1.16 vs 8.0 13:04 @_rene_ yeah, that sounds sufficienty different ;) 13:05 * _rene_ will follow-up on his question wrt iceweasel with a question about icedove icedove | 3.1.16-1 | wheezy| source, amd64, armel, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc icedove | 3.1.16-1 | sid | source, mips, mipsel, sparc icedove | 8.0-2 | sid | source icedove | 8.0-2+b1 | sid | amd64, armel, armhf, i386, ia Does upgrading icedove to sid make it work? Looks like some new vss vs. old icedove-problem then for me? Regards, Rene -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661445: system account (uid 100) for virtual users/mailboxes?
On Mon, Feb 27, 2012 at 01:16:25PM +0100, Daniel Pocock wrote: Colin Watson wrote: Pre-allocated IDs are only necessary when the IDs need to be hardcoded in binary packages somehow. I won't allocate them unless there is no reasonable alternative, as the allocation space is limited (particularly true for the global static IDs below 100). It is always preferable to use techniques such as 'adduser --system' where possible. I definitely haven't seen this type of thing hard coded, so it would not pass that criteria The reason I raise this, however, is that the pattern is becoming more widespread, and it is possible with quite a few packages now Have you raised this with any of the maintainers of the packages in question, or do you maintain any of those packages yourself? I mean, I'm not trying to restrict who gets to report bugs or anything, but normally it's best for this sort of request for ID allocation to be made by maintainers of the affected packages; there's no point in me allocating things that no maintainer is actually planning to use. Why couldn't all packages here simply cooperate in using 'adduser --system vmail' etc., and then look up the user dynamically by name? There seems no reason why the ID numbers themselves need to be the same between different systems or hardcoded in binary packages, so it doesn't seem to me as though base-passwd needs to be involved. It would be useful to have a standard username. Right, certainly. But this is the kind of thing that maintainers of the affected packages should just arrange among themselves, in a mail mini-policy or whatever (or even an amendment to policy - whatever suits best). It wouldn't add anything to have it recorded in base-passwd; in fact in many ways that would be less likely to be noticed than a mail mini-policy, and base-passwd is not in a good position to record things like the precise ways in which packages should co-operate in their use of the user in question, what files are permitted to be owned by that user, and so on, which are likely to be important security properties. Having a standard numeric ID isn't so important, but it would be useful to have some guidance on whether this type of ID would be in the system range (up to 999) or potentially qualify for one of the reserved ranges ( 6) It would belong in the dynamic system range, 100-999. As indicated by policy, the 6-64999 range is only for static allocation; and I only allocate static IDs when dynamic ones won't do. Cheers, -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636974: ITP: root-system -- CERN's ROOT Data Analysis Framework
Hi, JFYI: Lifeng Sun wrote: [...] Antonio Salvucci continues to maintain a non-official package in CERN [1]. My packaging will be based on their work. [1] http://lcg-heppkg.web.cern.ch/lcg-heppkg/debian/pool/hep/r/root-system/ Currently these packages won't build inside a pbuilder properly: build/unix/installXrootd.sh /tmp/buildd/root-system-5.32.00 Version: 3.1.0 Installing in: /tmp/buildd/root-system-5.32.00/xrootd-3.1.0 Retrieving source from tarball http://xrootd.slac.stanford.edu/download/v3.1.0/xrootd-3.1.0.tar.gz Build dir: /tmp/xrootd-3.1.0-25272 build/unix/installXrootd.sh: line 243: wget: command not found Tarball retrieval failed! make: *** [config.status] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 E: Failed autobuilding of package Downloading source tar balls during build is very suspicious and won't work anyway on Debian's build daemons as some of them may not have network access during build-time. It actually FTBFS due to a missing build-dependency on wget. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661188: [Aptitude-devel] Bug#661188: aptitude purge package recursively REMOVES BUT DOES NOT PURGE the unneeded dependencies of package
I too have been bitten by this in the past and do think what Daniel has given as an answer is okish (although there should be some sort of better way.) For my exchange see [0] . One of the things which I didn't know to figure out how to produce a listing of such packages using aptitude [1] which was shared by Daniel as well. As I have removed all the packages which were removed haven't been able to test out if dpkg -L works on such packages as well or not. George if you have some packages whose configuration files are still it would be nice if you could produce a listing of what you get. If you do get the location of those files then a user could attempt at least to know what they contain and perhaps judge (or not) whether it could be useful now or latter. Another point to be kept at back of mind as well is over a period of time a package could merge other packages in it or be split in one or more packages, in the former the config files remaining the same (while binary is removed) while at the latter more config files would perhaps be added. I have a very vague sense of how aptitude does things so I might be right (or not). I do hope however that my $0.02 does prove to be useful to you otherwise simply disregard it. 0 - http://lists.alioth.debian.org/pipermail/aptitude-devel/2012-February/001945.html 1 - aptitude search ?config-files 2 - dpkg -L = -L|--listfiles package ... List files `owned' by package(s). A healthy package displays something like this , a random e.g. :- $ dpkg -L fonts-gubbi /. /etc /etc/fonts /etc/fonts/conf.avail /etc/fonts/conf.avail/65-0-fonts-gubbi.conf /etc/fonts/conf.d /usr /usr/share /usr/share/doc /usr/share/doc/fonts-gubbi /usr/share/doc/fonts-gubbi/changelog.gz /usr/share/doc/fonts-gubbi/changelog.Debian.gz /usr/share/doc/fonts-gubbi/copyright /usr/share/fonts /usr/share/fonts/truetype /usr/share/fonts/truetype/Gubbi /usr/share/fonts/truetype/Gubbi/Gubbi.ttf /etc/fonts/conf.d/65-0-fonts-gubbi.conf Sorry for the noise :) -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661469: x11-common: template parse error choices-sr
Package: x11-common Version: 1:7.6+11 Severity: important Setting up x11-common (1:7.6+11) ... Template parse error near `choices...@latin.utf-8: Samo glavni korisnik, Samo za korisnike konzole, Svako', in stanza #1 of /var/lib/dpkg/info/x11-common.templates dpkg: error processing x11-common (--configure): -- System Information: Debian Release: squeeze/sid APT prefers oldstable APT policy: (500, 'oldstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages x11-common depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii debianutils 4.2.1 Miscellaneous utilities specific t ii lsb-base 3.2-28.1 Linux Standard Base 3.2 init scrip x11-common recommends no packages. x11-common suggests no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652631: www.debian.org: please clarify the distinction between 'events@d.o' and 'debian-events-*@lists.d.o'
[partly reformatted] begin quotation from Francesca Ciceri (in 20120221135142.gh8...@zouish.org): sorry for the late reply on this important discussion: lately I was really really busy (in real life) and I just did Debian work if cruelly pinged ;). Same for me. On Mon, Dec 26, 2011 at 01:30:10AM +0100, Bernd Zeimetz wrote: On 12/25/2011 11:11 PM, Arne Wichmann wrote: [...] b) at least for those who have access to Debian machines nothing is happening behind the scene, given that 'events@d.o' is archived on master [8]. [8] http://anonscm.debian.org/viewvc/webwml/webwml/english/events/README?revision=1.8view=markup Hm. Where is the archive? I have not. Am I the only one to which this applies? No. we often have people organizing stuff which are not DDs. Not-DDs can be added to @debian.org alias: at least I was added at events@d.o when I wasn't a DD yet, and the same happened for cdvend...@debian.org. Wrt organization: wiki is really useful for organizing stuff. And is also quite easy to follow the organization process *if* you're aware of the existence of the wikipage. Yep, this is one of the points. On Mon, Dec 26, 2011 at 01:30:10AM +0100, Bernd Zeimetz wrote: May be the events team should - instead of founding itself - talk to those people who are known to provide merch and booth material if they want to join and what they can provide? [...] Even better: the even team should consist of people from each d-events-$(locale) list (probably those who are organizing a lot of stuff). Oh!! Finally! To make a long story short: I have no experience of organizing events, for instance, and I'm in the events team just to do the promoting/www part. It's quite a while that me and Luca are talking about enlarge the team, to include at least 1 person from each part-of-the-world where events are more regularly organized. This person need to be one who often organizes events/booths, so someone with experience and who knows practical things about events. Now, we usually have a lot of events in Europe mostly in the German-speaking area, but also in France and UK. Then we have few events in the US, some in Hispano America and Brazil and a *lot* of events in India (thanks to the Debian India group) and some in Taiwan. I've thought about a couple of names for some of these areas (please fill the list of possible candidates for this area, or propose yourself!), to be part of the events team: German-speaking area: Annette Kalbow, Arne Wichmann, Axel Beckert, Franziska Lichtblau I, at least, am not opposed to the idea. France-speaking area: Carl Chenet, Sylvestre Ledru UK: ... US: ... Hispano America: Fernando Estrada, Gunnar Wolf Brazil: Ana Caroll Comandulli, Marcelo Santana India: Praveen Arimbrathodiyil Taiwan: Andrew Lee -nl had a quite active community when I last looked at it... [...] If you all agree on this part, I'd really like to start to send some invitation to the events team. ;) Do. ;) begin quotation from Franziska Lichtblau (in 20120223082519.ga31...@old-forest.org): Hey, On Tue, Feb 21, 2012 at 02:51:42PM +0100, Francesca Ciceri wrote: [...] First of all, just a correction: On Mon, Dec 26, 2011 at 01:30:10AM +0100, Bernd Zeimetz wrote: On 12/25/2011 11:11 PM, Arne Wichmann wrote: [...] b) at least for those who have access to Debian machines nothing is happening behind the scene, given that 'events@d.o' is archived on master [8]. [8] http://anonscm.debian.org/viewvc/webwml/webwml/english/events/README?revision=1.8view=markup I have not. Am I the only one to which this applies? No. we often have people organizing stuff which are not DDs. Not-DDs can be added to @debian.org alias: at least I was added at events@d.o when I wasn't a DD yet, and the same happened for cdvend...@debian.org. Arne, Axel and me talked about this to Luka at Fosdem - this problems seems to be solved. Hm. What was the solution? I remember, at least for me it was mainly a clarification of the workflow, as Rhalina wrote below. Wrt organization: wiki is really useful for organizing stuff. And is also quite easy to follow the organization process *if* you're aware of the existence of the wikipage. Same thing applies here: There seems to be just a misunderstanding. So the workflow as I understood it is: Find an event, create a Wikipage, send event-+wikilink to events@d.o and everything is fine. From there on the event will be promoted and the organisation can happen in the wiki or via mailinglist etc. And this should be documented prominently - the workflow of event organization. In my view it should be the following: - If you find an event in which Debien could possibly take part, mail to debian-events-region. - If you want to organize an event create a wiki page for it (documentation how to do that
Bug#661471: gnome-themes-standard: removal of gnome-themes-standard makes files disappear from gnome-accessibility-themes
Package: gnome-themes-standard Version: Severity: serious User: debian...@lists.debian.org Usertags: piuparts replaces-without-breaks Hi, during a test with piuparts and EDOS tools I noticed your package causes removal of files that also belong to another package. This is caused by using Replaces without corresponding Breaks. The installation sequence to reproduce this problem is apt-get install gnome-accessibility-themes # (1) apt-get install gnome-themes-standard apt-get remove gnome-themes-standard # (2) The list of installed files at points (1) and (2) should be identical, but the following files have disappeared: /usr/share/icons/HighContrast/index.theme /usr/share/icons/HighContrastInverse/index.theme /usr/share/themes/HighContrast/gtk-2.0/gtkrc /usr/share/themes/HighContrast/index.theme /usr/share/themes/HighContrastInverse/gtk-2.0/gtkrc /usr/share/themes/HighContrastInverse/index.theme /usr/share/themes/LowContrast/gtk-2.0/gtkrc /usr/share/themes/LowContrast/index.theme This is a serious bug violating policy 7.6, see http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces and also see the footnote that describes this incorrect behavior http://www.debian.org/doc/debian-policy/footnotes.html#f53 The gnome-themes-standard package has the following relationships with gnome-accessibility-themes: Conflicts: n/a Breaks:n/a Replaces: gnome-accessibility-themes ( 3.0) gnome-accessibility-themes is only available as 2.30.2-1 in squeeze, wheezy, and sid. From the attached log (scroll to the bottom...): 0m40.0s ERROR: FAIL: After purging files have disappeared: /usr/share/icons/HighContrast/index.theme owned by: gnome-themes-standard /usr/share/icons/HighContrastInverse/index.theme owned by: gnome-themes-standard /usr/share/themes/HighContrast/gtk-2.0/gtkrc owned by: gnome-themes-standard /usr/share/themes/HighContrast/index.theme owned by: gnome-themes-standard /usr/share/themes/HighContrastInverse/gtk-2.0/gtkrcowned by: gnome-themes-standard /usr/share/themes/HighContrastInverse/index.theme owned by: gnome-themes-standard /usr/share/themes/LowContrast/gtk-2.0/gtkrcowned by: gnome-themes-standard /usr/share/themes/LowContrast/index.theme owned by: gnome-themes-standard 0m40.0s ERROR: FAIL: After purging files have been modified: /var/lib/dpkg/info/gnome-accessibility-themes.list not owned cheers, Andreas REPL_gnome-accessibility-themes_gnome-themes-standard.log.gz Description: GNU Zip compressed data
Bug#611292: insserv treats corekeeper as invalid file name, inconsistent with manual's *.core unaccepted filename.
The proposed patch is wrong: as written it arranges to reject filenames that begin with .core, rather than those that end with .core. Files whose names end .core are already rejected by cfgfile_filter(), and files whose names begin .core are rejected by the general rejection of filenames beginning with .. I think the original test is intended to trap old-style core dumps, which are always called simply core. This could be correctly achieved by: --- insserv.c.orig 2010-02-19 13:08:04.0 + +++ insserv.c 2012-02-27 12:10:01.0 + @@ -2764,7 +2764,7 @@ continue; } - if (!strncmp(d-d_name, core, strlen(core))) { + if (!strcmp(d-d_name, core)) { if (isarg) warn(script name %s is not valid, skipped!\n, d-d_name); continue; -- Ben Harris, University of Cambridge Computing Service. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660022: [Pkg-opt-media-team] Bug#660403: cdparanoia (Re: transition status)
On 25.02.2012 16:03, Rogério Brito wrote: Hi there. On Feb 25 2012, Robert Millan wrote: El 25 de febrer de 2012 13:46, Adam D. Barratt a...@adam-barratt.org.uk ha escrit: On Sat, 2012-02-25 at 12:20 +, Robert Millan wrote: 660403: cdparanoia: FTFBS on kfreebsd-* - Unless there's further activity I recommend removing of kfreebsd-* binaries from testing. See http://bugs.debian.org./cgi-bin/bugreport.cgi?bug=660403#12 That doesn't work. The choices would be removing the kfreebsd-* binaries from unstable, and letting that propagate, or removing the entire package from testing. Is an upload needed in first case? Is there anything that I can do helping with this? Well, I sent a patch... :) I must admit to not being able to check whether it works, but it at least makes the package build on kfreebsd-amd64 again on the porter-box. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661445: system account (uid 100) for virtual users/mailboxes?
Pre-allocated IDs are only necessary when the IDs need to be hardcoded in binary packages somehow. I won't allocate them unless there is no reasonable alternative, as the allocation space is limited (particularly true for the global static IDs below 100). It is always preferable to use techniques such as 'adduser --system' where possible. I definitely haven't seen this type of thing hard coded, so it would not pass that criteria The reason I raise this, however, is that the pattern is becoming more widespread, and it is possible with quite a few packages now Why couldn't all packages here simply cooperate in using 'adduser --system vmail' etc., and then look up the user dynamically by name? There seems no reason why the ID numbers themselves need to be the same between different systems or hardcoded in binary packages, so it doesn't seem to me as though base-passwd needs to be involved. It would be useful to have a standard username. Having a standard numeric ID isn't so important, but it would be useful to have some guidance on whether this type of ID would be in the system range (up to 999) or potentially qualify for one of the reserved ranges ( 6) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661188: [Aptitude-devel] Bug#661188: aptitude purge package recursively REMOVES BUT DOES NOT PURGE the unneeded dependencies of package
some additions :- 2012/2/27 shirish शिरीष shirisha...@gmail.com: I too have been bitten by this in the past and do think what Daniel has given as an answer is okish (although there should be some sort of better way.) For my exchange see [0] . One of the things which I didn't know to figure out how to produce a listing of such packages using aptitude [1] which was shared by Daniel as well. As I have purged all the packages which were removed haven't been able to test out if dpkg -L (2) works on such packages as well or not. George if you have some packages whose configuration files are still it would be nice if you could produce a listing of what you get. If you do get the location of those files then a user could attempt at least to know what they contain and perhaps judge (or not) whether it could be useful now or latter. Another point to be kept at back of mind as well is over a period of time a package could merge other packages in it or be split in one or more packages, in the former the config files remaining the same (while binary is removed) while at the latter more config files would perhaps be added. I have a very vague sense of how aptitude does things so I might be right (or not). I do hope however that my $0.02 does prove to be useful to you otherwise simply disregard it. 0 - http://lists.alioth.debian.org/pipermail/aptitude-devel/2012-February/001945.html 1 - aptitude search ?config-files 2 - dpkg -L = -L|--listfiles package ... List files `owned' by package(s). A healthy package displays something like this , a random e.g. :- $ dpkg -L fonts-gubbi /. /etc /etc/fonts /etc/fonts/conf.avail /etc/fonts/conf.avail/65-0-fonts-gubbi.conf /etc/fonts/conf.d /usr /usr/share /usr/share/doc /usr/share/doc/fonts-gubbi /usr/share/doc/fonts-gubbi/changelog.gz /usr/share/doc/fonts-gubbi/changelog.Debian.gz /usr/share/doc/fonts-gubbi/copyright /usr/share/fonts /usr/share/fonts/truetype /usr/share/fonts/truetype/Gubbi /usr/share/fonts/truetype/Gubbi/Gubbi.ttf /etc/fonts/conf.d/65-0-fonts-gubbi.conf I did try it just now with a library which I know is no longer needed (although aptitude hasn't removed/purged it). This is on a Debian sid machine. $ aptitude search libgs? p libgs-dev - interpreter for the PostScript language and for PDF - Develop v libgs-esp-dev - i libgs8 - The Ghostscript PostScript/PDF interpreter Library i A libgs9 - interpreter for the PostScript language and for PDF - Library i A libgs9-common - interpreter for the PostScript language and for PDF - common Just extracted partial listing. It seems aptitude doesn't respect the wildcard '?' as it produces a whole listing but that I guess is another issue. See libgs8 :- $ aptitude show libgs8 Package: libgs8 State: installed Version: 8.71~dfsg2-9 Priority: optional Section: libs Maintainer: Debian Printing Team debian-print...@lists.debian.org Uncompressed Size: 16.2 M Depends: libc6 (= 2.7), libcomerr2 (= 1.01), libcups2 (= 1.4.0), libcupsimage2 (= 1.4.0), libfontconfig1 (= 2.8.0), libgcrypt11 (= 1.4.2), libgnutls26 (= 2.7.14-0), libgssapi-krb5-2 (= 1.6.dfsg.2), libjasper1 (= 1.900.1), libjbig2dec0, libjpeg62 (= 6b1), libk5crypto3 (= 1.6.dfsg.2), libkrb5-3 (= 1.6.dfsg.2), libpaper1, libpng12-0 (= 1.2.13-4), libstdc++6 (= 4.1.1), libtiff4, zlib1g (= 1:1.1.4) Breaks: ghostscript ( 8.71~dfsg2-7) Replaces: ghostscript ( 8.71~dfsg2-7) Description: The Ghostscript PostScript/PDF interpreter Library Ghostscript is used for PostScript/PDF preview and printing. Usually as a back-end to a program such as ghostview, it can display PostScript and PDF documents in an X11 environment. This package provides the Ghostscript library which makes the facilities of Ghostscript available to applications. Homepage: http://www.ghostscript.com/ Tags: implemented-in::c, role::shared-lib, use::printing, use::viewing, works-with-format::pdf, works-with-format::postscript Looking at libgs9 now :- $ aptitude show libgs9 Package: libgs9 State: installed Automatically installed: yes Version: 9.05~dfsg-2 Priority: optional Section: libs Maintainer: Debian Printing Team debian-print...@lists.debian.org Uncompressed Size: 10.4 M Depends: libc6 (= 2.7), libcomerr2 (= 1.01), libcups2 (= 1.4.0), libcupsimage2 (= 1.4.0), libfontconfig1 (= 2.8.0), libfreetype6 (= 2.2.1), libgcrypt11 (= 1.4.5), libgnutls26 (= 2.12.6.1-0), libgssapi-krb5-2 (= 1.6.dfsg.2), libidn11 (= 1.13), libijs-0.35 (= 0.35), libjasper1, libjbig2dec0, libjpeg8 (= 8c), libk5crypto3 (= 1.6.dfsg.2), libkrb5-3 (= 1.6.dfsg.2), liblcms2-2, libpaper1, libpng12-0 (= 1.2.13-4), libstdc++6 (= 4.1.1), libtiff4, zlib1g (= 1:1.1.4), gs-cjk-resource, libgs9-common (=
Bug#658415: [BTS#658415] templates://golang-weekly/{golang-weekly-tools.templates} : Final update for English review
On Sun, Feb 26, 2012 at 13:11, Justin B Rye j...@edlug.org.uk wrote: Jonathan Nieder wrote: Christian PERRIER wrote: -Description: Experimental Go programming language compiler +Description: Go programming language compiler Shouldn't this say Go programming language compiler (weekly snapshot) or something similar to distinguish it from the main golang package? That's what I thought until I discovered that the only golang packages available for the golang metapackage to pull in are the -weekly ones. No. packages.qa.debian.org/g/golang.html At present, warning people to use that instead seems rather futile. [...] - Go is an experiment. We hope adventurous users will give it a try and - see if they enjoy it. Not every programmer will, but we hope enough - will find satisfaction in the approach it offers to justify further - development. The language can (and still does) change between weekly - releases, check http://golang.org/doc/devel/weekly.html before - upgrading this package. + This package provides an assembler, a compiler, and a linker for the + Go programming language. This is Google's implementation of the Go + tool chain. The warning about lack of stability seems relevant to someone considering whether to install the package. Maybe something like this, to give the same hints more briefly: This package provides an assembler, a compiler, and a linker for the Go programming language. This is Google's implementation of the Go tool chain. . Go is young. There are still language changes between weekly releases, described at http://golang.org/doc/devel/weekly.html. Or maybe, stealing text from that page: This package provides an assembler, a compiler, and a linker for the Go programming language. This is Google's implementation of the Go tool chain. . Weekly snapshots occur often and may not be stable. If stability of API and code is more important than having the latest features, use the official releases from the golang package instead. Bear in mind that these packages are already in Testing; if the idea is that some particular individual weekly snapshot is going to end up as the only version of golang released with Wheezy, the text above won't make much sense. No, they are not in the Testing: http://packages.qa.debian.org/g/golang-weekly.html By the way, why is this a separate source package instead of being called golang in experimental? Or to put it another way, if the upstream versions of the last three golang-weekly releases are 2011.09.07, 2011.09.21, and 2012.01.27, why is it called -weekly? Because upstream do weekly releases, but I upload -weekly release when I have a time. I need to automatize the process, but it goes back to when I have a time. O. -- Ondřej Surý ond...@sury.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661464: java-propose-classpath: rewrite proposal
Hi Niels, Good to hear from you. Thank you for your reply. On Monday 27 February 2012 22:37:36 Niels Thykier wrote: Thanks, though if you are talking about java-propose-classpath, I believe you want to thank Matthew Johnson. :) Thanks! :) On a related note, I would love for jh_depends to be smarter and generate ${java:Depends} based on the actual usage[0]. Actually, I believe I have some code somewhere that might could be useful for this. [0] Including checking for useless/overlinking and erroing out if classes are missing etc. I like this idea. :) While I do not have time right now to give it a detailed review, I hope we can use it (partly or even fully). Either way would be fine, I will be happy if you manage to use any part. P.S. Please don't worry about license compatibility because for javatools I give permission to use GPL-2+ license. I appreciate the gesture, but I cannot accept it[1]. It is possible that we could bump the license of the existing javatools code to GPL-2+ or alternatively, I can also accept an unconditional GPL-2+ license on your code. My bad, I overlooked this paragraph in social contract - sorry. Of course unconditional GPL-2+ is fine: I hereby grant permission to use this code under GPL-2+ license. I reckon it will be better to attach the script with updated license to avoid any doubts. [attached] All the best, Dmitry. listdeps-jar.sh Description: application/shellscript signature.asc Description: This is a digitally signed message part.