Bug#697650: support short locales boot parameter
tag 697650 - patch tag 697650 + moreinfo thanks there are several issues with the suggested patch: * doesn't follow coding style, see live-manual for details. * doesn't contain update for the (english) manpage to document the 'new' behaviour * comments are showing wrong examples, locales=ch would result in ch_CH which doesn't exist (and thus shows the limitations of the suggested behaviour, which is why i think it's not usefull anyway and which is why i've removed that in the first place). * i'm not entirely sure, but iirc the utf-8 by default is not necessary as libc will default to any non-specified locale to the utf-8 characterset anyway. would be nice if someone would check that. * we do want to do things in live config as 'optimized' as possible, as it impacts boot time directly (remember, live-config is run as first job and *not* in parallel with other initscripts on purpose). please use single-statment assignement for the first operation. * breaks/doesn't work with multiple locales such as locales=en,de even if all the issues above are fixed, i'm not convinved we do really want that. it doesn't fit into live-config to do such 'limited' 'magic'. limited as indicated above, the only 'gain' here is for people that want 'xx_XX' locales that they can specify 'xx'. for everyone else (people using xx_YY), it doesn't matter. magic as all parameters to live-config take values that exactely match the values you'd put into the respective configuration files itself, making it straight forward to handle (no magic) and to document (refer to the original configured package). -- 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#698542: installation-report: Wheezy beta on FSC Futro A240
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.49 Severity: wishlist Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** - -- Package-specific info: Boot method: USB Image version:http://cdimage.debian.org/cdimage/weekly-builds/i386/iso-dvd/debian-testing-i386-DVD-1.iso, 2013-01-14 Date: 2013-01-19, afternoon Machine: FSC Futro A240 Partitions: Filesystem Type 1K-blocks Used Available Use% Mounted on rootfs rootfs 7313408 2769416 4543992 38% / udev devtmpfs 10240 0 10240 0% /dev tmpfs tmpfs 44952 556 44396 2% /run /dev/disk/by-uuid/14311c4a-fac0-4bb8-a844-7aed9463b46c xfs7313408 2769416 4543992 38% / tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 190860 0190860 0% /run/shm Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [o] Detect network card:[o] Configure network: [o] Detect CD: [o] Load installer modules: [o] Clock/timezone setup: [o] User/password setup:[o] Detect hard drives: [o] Partition hard drives: [o] Install base system:[o] Install tasks: [o] Install boot loader:[o] Overall install:[o] Comments/Problems: This was a mostly flawless installation from USB, using the current testing-i386-DVD-image and choosing the XFCE-desktop version. The only trouble occured with the xserver, that needs manual configuration. I did this in the common way, going into runlevel 1, then into /etc/X11/ and doing # Xorg -configure, ignoring the error-message about the number of screens, removing screen 1 and screen 2 in the newly generated xorg.conf and then copying it from /root/ to /etc/X11/ The file is attached as xorg.conf.gz for clarity. This box has a 500MHz CPU and is surprisingly well usable with 512 MB of RAM. It is even good enough for running Iceweasel and reading online, as long as you keep away from too immensely bloated websites. The energy-consumption is extremely low, compared to normal PCs, with a maximum of eight W. The machine lacks a parallel port, so it connot be used as a printserver for older printers. Extensibility is quite limited, too, only RAM and CompactFlash upgrades are possible.glxgears reaches more than two frames per second, which is seemingly not much, but 2D graphics are fast enough, really. Overall I would like to recommend these boxes to anyone, they are available at about EUR 15 to 20 here in germany, which makes a quite inexpensive computer with a VGA-only monitor connector. - -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=7.0 (wheezy) - installer build 20130114-00:06 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux s240 3.2.0-4-486 #1 Debian 3.2.35-2 i586 GNU/Linux lspci -knn: 00:01.0 Host bridge [0600]: Advanced Micro Devices [AMD] CS5536 [Geode companion] Host Bridge [1022:2080] (rev 31) lspci -knn: Subsystem: Advanced Micro Devices [AMD] CS5536 [Geode companion] Host Bridge [1022:2080] lspci -knn: 00:01.1 VGA compatible controller [0300]: Advanced Micro Devices [AMD] Geode LX Video [1022:2081] lspci -knn: Subsystem: Advanced Micro Devices [AMD] Geode LX Video [1022:2081] lspci -knn: 00:01.2 Entertainment encryption device [1010]: Advanced Micro Devices [AMD] Geode LX AES Security Block [1022:2082] lspci -knn: Subsystem: Advanced Micro Devices [AMD] Geode LX AES Security Block [1022:2082] lspci -knn: 00:0d.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8169 PCI Gigabit Ethernet Controller [10ec:8169] (rev 10) lspci -knn: Subsystem: Realtek Semiconductor Co., Ltd. RTL8169 PCI Gigabit Ethernet Controller [10ec:8169] lspci -knn:Kernel driver in use: r8169 lspci -knn: 00:0f.0 ISA bridge [0601]: Advanced Micro Devices [AMD] CS5536 [Geode companion] ISA [1022:2090] (rev 03) lspci -knn: Subsystem: Advanced Micro
Bug#696340: rockdodger: moved to new hosting
For the record, http://spacerocks.sourceforge.net/ points to http://sourceforge.net/projects/spacerocks/ which points to the new homepage https://sites.google.com/site/rockdodgerupdate/ which points to the new download site http://code.google.com/p/rockdodger/ . The newest upstream version is currently 0.7.6 to be packaged in Debian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698543: qcontrol: Sanitize input from lua scripts
Package: qcontrol
Version: 0.4.2+svn-r40-3
Severity: normal
Tags: patch
Hi,
when passing a lua nil (or anything not a string or a number) value as second
(or higher) arg to piccmd() qcontrol dies.
This is because piccmd()s lcd-line0 / lcd-line1 commands do a strlen() on a NULL
value. get_args() calls lua_tostring(), but this returns NULL for anything not
a number or a string...
Hanno
-- System Information:
Debian Release: 7.0
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: armel (armv5tel)
Kernel: Linux 3.2.0-4-kirkwood
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages qcontrol depends on:
ii libc62.13-37
ii liblua5.1-0 5.1.5-4
ii udev 175-7
qcontrol recommends no packages.
qcontrol suggests no packages.
-- Configuration Files:
/etc/qcontrol/ts41x.lua changed [not included]
-- no debconf information
--- qcontrol.orig/qcontrol.c 2013-01-20 09:38:27.903838894 +0100
+++ qcontrol/qcontrol.c 2013-01-20 09:40:50.885882680 +0100
@@ -163,7 +163,15 @@
*argc = lua_gettop(lua);
*argv = (const char **) calloc(*argc, sizeof(char*));
for (i = 1; i = *argc; ++i) {
- *(*argv + i - 1) = (const char*) lua_tostring(lua, i);
+ switch (lua_type(lua, i)) {
+ case LUA_TSTRING:
+ case LUA_TNUMBER:
+*(*argv + i - 1) = (const char*) lua_tostring(lua, i);
+break;
+ default:
+*(*argv + i - 1) = (const char*) ;
+break;
+ }
}
return 0;
}
Bug#698093: [Pkg-libvirt-maintainers] Bug#698093: libvirt-bin: Enable Xen libxl backend
Date: Mon, 14 Jan 2013 08:14:46 +0100 From: a...@sigxcpu.org To: chillermillerl...@hotmail.com; 698...@bugs.debian.org Subject: Re: [Pkg-libvirt-maintainers] Bug#698093: libvirt-bin: Enable Xen libxl backend On Sun, Jan 13, 2013 at 07:05:12PM -0500, Xiao-Long Chen wrote: Package: libvirt-bin Version: 1.0.0-0ubuntu4ppa1~raring1 Please don't file bugs against Ubuntu versions. Sorry about that. I should have read the guidelines for bug reporting in Debian. Severity: normal Please enable the libxl backend for Xen in libvirt. Version 1.0.0 and above support this backend. Xen is already deprecating the old xm/xend toolstack in Xen 4.2 and is moving to the xl toolstack. It's not that simple. We need to offer a migration path for existing configurations. Do you want to work on that? Cheers, -- Guido Would migration be necessary? As far as I know, libvirt will automaticallyfall back to the current xen driver if xend is running. It will only use xl ifxend is not started. Am I correct to assume that any existing libvirt configuration for xen wouldhave xend started automatically as it is required? Cheers,Xiao-Long Chen
Bug#698111: ITP: zimlib -- Standard library implementation of ZIM specifications
Le 20/01/2013 06:20, Vasudev Kamath a écrit : On 22:00 Mon 14 Jan , Raphael Hertzog wrote: Hi, On Mon, 14 Jan 2013, Vasudev Kamath wrote: I did some more investigation and I don't see any file name clash betweek zim from zim-wiki and zimlib. Even though both packages have zim in the package name there is description field which clarifies any confusion between both packages for end user. So I guess renaming from upstream is not required. Please share your thoughts. My thoughts are I have been confused and thus I believe that other users will be confused in the future. This is why I believe it's best to rename. Furthermore, there are no file clashes yet, but the day where someone will write a python wrapper for zimlib (and this is on the roadmap apparently), it might become a real issue. OK thanks for sharing your views on this, apparently I didn't think of python wrapper for zimlib. @Kelson can you share your views on this. What about libopenzim as package name, content unchanged? Emmanuel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698111: ITP: zimlib -- Standard library implementation of ZIM specifications
On Sun, 20 Jan 2013, Emmanuel Engelhart wrote: What about libopenzim as package name, content unchanged? Looks reasonable to me. Cheers, -- Raphaël Hertzog ◈ Debian Developer Get the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683584: [Pkg-monitoring-maintainers] ganglia update for Squeeze (CVE-2012-3448)
On dim., 2013-01-20 at 00:44 +0100, Daniel Pocock wrote: Thanks for confirming that It is possible that I bootstrapped 3.1.7 on an earlier Debian version than 3.1.8. E.g. Maybe 3.1.7 was bootstrapped on lenny and 3.1.8 on squeeze. This would mean different versions of autoconf were present, and each of them dumps different stuff in the source tree. Looks possible. However, just excluding that change (e.g. by hacking the one line change into the 3.1.7 tree rather than using the whole 3.1.8 tree) doesn't guarantee identical autotools behavior unless the build is done on a platform equivalent to where the original 3.1.7-1 package was built. I'd be really concerned if it'd be the case. But if you fear something like that, it'd be best if you could test the package indeed fixes the bug. If we need to be that pedantic about it to put something into squeeze (which may well be a good idea), then maybe we need to make the change without building and releasing any of the actual binaries, just release the ganglia-web.deb package (which contains no binary code, just PHP). Is there a workflow to do that? No. We want minimal changes against the version in Squeeze, remember? In any case, provided it actually fixes the bug, I'm ok with Salvatore package including only the oneliner patch. Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#698093: [Pkg-libvirt-maintainers] Bug#698093: libvirt-bin: Enable Xen libxl backend
On Sun, Jan 20, 2013 at 04:06:12AM -0500, 小龙 陈 wrote: Date: Mon, 14 Jan 2013 08:14:46 +0100 From: a...@sigxcpu.org To: chillermillerl...@hotmail.com; 698...@bugs.debian.org Subject: Re: [Pkg-libvirt-maintainers] Bug#698093: libvirt-bin: Enable Xen libxl backend On Sun, Jan 13, 2013 at 07:05:12PM -0500, Xiao-Long Chen wrote: Package: libvirt-bin Version: 1.0.0-0ubuntu4ppa1~raring1 Please don't file bugs against Ubuntu versions. Sorry about that. I should have read the guidelines for bug reporting in Debian. Severity: normal Please enable the libxl backend for Xen in libvirt. Version 1.0.0 and above support this backend. Xen is already deprecating the old xm/xend toolstack in Xen 4.2 and is moving to the xl toolstack. It's not that simple. We need to offer a migration path for existing configurations. Do you want to work on that? Cheers, -- Guido Would migration be necessary? As far as I know, libvirt will automaticallyfall back to the current xen driver if xend is running. It will only use xl ifxend is not started. Am I correct to assume Did you try this? Last time I checked the libxml driver would take precedence over xend. that any existing libvirt configuration for xen wouldhave xend started automatically as it is required? No. Libvirt doesn't setup the hypervisor it only looks for available ones. Cheers, -- Guido Cheers,Xiao-Long Chen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698541: [Secure-testing-team] Bug#698541: zabbix: CVE-2013-1364: possible to override LDAP configuration parameters via the API
I've commited patches for squeeze and unstable to repository but at the moment I'm unable to test. Please review. Unstable: http://anonscm.debian.org/gitweb/?p=collab-maint/zabbix.git;a=commitdiff;h=d3f835add9f3131932893e279ff787bb6b3a1d7f Squeeze: http://anonscm.debian.org/gitweb/?p=collab-maint/zabbix.git;a=commitdiff;h=daa679ab54401a16768ca171a825870fc4a92e9d -- Cheers, Dmitry Smirnov GPG key : 4096R/53968D1B --- It is a fine thing to be honest, but it is also very important to be right. -- Winston Churchill -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692011: taxbird: version in testing (0.16.x) is completely useless
retitle 692011 RM: taxbird/0.16-0.2 user release.debian@packages.debian.org usertags 692011 = rm quit Jonathan Wiltshire wrote: On Sat, Dec 22, 2012 at 08:46:50PM +, Steven Chamberlain wrote: Then aim to make the version in sid, or any later revisions, available through wheezy-backports. That seems analogous to the 'volatile' idea. This would keep the package available to those who want it, yet reflects the fact it doesn't have the same level or duration of support as a typical package in stable. So, what's the progress on this? I'm strongly of the opinion that this is the most appropriate strategy. Agreed, though not as strongly, so marking so. 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#683584: [Pkg-monitoring-maintainers] ganglia update for Squeeze (CVE-2012-3448)
On 20/01/13 10:14, Yves-Alexis Perez wrote: On dim., 2013-01-20 at 00:44 +0100, Daniel Pocock wrote: Thanks for confirming that It is possible that I bootstrapped 3.1.7 on an earlier Debian version than 3.1.8. E.g. Maybe 3.1.7 was bootstrapped on lenny and 3.1.8 on squeeze. This would mean different versions of autoconf were present, and each of them dumps different stuff in the source tree. Looks possible. However, just excluding that change (e.g. by hacking the one line change into the 3.1.7 tree rather than using the whole 3.1.8 tree) doesn't guarantee identical autotools behavior unless the build is done on a platform equivalent to where the original 3.1.7-1 package was built. I'd be really concerned if it'd be the case. But if you fear something That is the case, for any autotools project: autotools is a whole world of it's own. For example, a newer version may build the code with different compiler or linker flags, and this may or may not cause the build to fail or produce a different result on some or all platforms. In practice, people do stuff like this every day, but usually when compiling for a single platform where they can see the results themselves. I just don't know if there is some more pedantic approach to managing this type of risk for updates to stable and would appreciate feedback on that, however... like that, it'd be best if you could test the package indeed fixes the bug. If we need to be that pedantic about it to put something into squeeze (which may well be a good idea), then maybe we need to make the change without building and releasing any of the actual binaries, just release the ganglia-web.deb package (which contains no binary code, just PHP). Is there a workflow to do that? No. We want minimal changes against the version in Squeeze, remember? Minimal change would mean exactly what I described: not producing any new binary packages for ganglia-monitor.deb, gmetad.deb, etc. We would only release the ganglia-web.deb binary package. If we release all the binary packages, that means they are all recompiled, even though none of the code in them is changing. It is only the PHP code that changes, and that is not compiled anyway. In any case, provided it actually fixes the bug, I'm ok with Salvatore package including only the oneliner patch. Regards, ___ Pkg-monitoring-maintainers mailing list pkg-monitoring-maintain...@lists.alioth.debian.org https://lists.alioth.debian.org/mailman/listinfo/pkg-monitoring-maintainers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698544: gosa: SASL as password hash method fails
Package: gosa
Version: 2.7.4-4
Severity: normal
Hi,
I am implementing GOsa for the Debian-LAN setup. The idea is to use
SASL to authenticate users in the setup with kerberos. To implement
that, I use passwordDefaultHash=sasl in gosa.conf.
However, when I add a user in GOsa, I end up with:
---8---
uid=ante,ou=people,ou=gosa,dc=intern
sn: Another
givenName: Test
uid: ante
cn: Test Another
userPassword: {SASL}@INTERN
---8---
^^
The uid is missing.
If I log into GOsa as admin and modify the Password storage in the
Generic-Tab to ssha (press apply) and back to sasl, I end up with
what I would have expected from the beginning:
userPassword: {SASL}ante@INTERN
Further more, there is no way to enter a password, no dialog shows
up. The entered password would be sent to the KDC via a hook.
The 'perfect' setup would look like this: When SASL is chosen as
password method, the password dialog is available if a corresponding
hook exists in gosa.conf.
The sugested setup would help debian-lan as well as debian-edu to
prepare a cleaner setup with central authentication and password
storage in the KDC.
Best regards,
Andi
-- System Information:
Debian Release: 7.0
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gosa depends on:
ii apache22.2.22-12
ii apache2-mpm-prefork [httpd]2.2.22-12
ii exim4 4.80-7
ii exim4-daemon-heavy [mail-transport-agent] 4.80-7
ii gettext0.18.1.1-9
ii libapache2-mod-php55.4.4-10
ii libcrypt-smbhash-perl 0.12-3
ii php5 5.4.4-10
ii php5-cli 5.4.4-10
ii php5-curl 5.4.4-10
ii php5-gd5.4.4-10
ii php5-imagick 3.1.0~rc1-1+b2
ii php5-imap 5.4.4-10
ii php5-ldap 5.4.4-10
ii php5-mcrypt5.4.4-10
ii php5-mysql 5.4.4-10
ii php5-recode5.4.4-10
ii smarty33.1.10-2
ii ttf-liberation 1.07.2-6
gosa recommends no packages.
Versions of packages gosa suggests:
pn cyrus21-imapd none
ii gosa-schema 2.7.4-4
pn gosa-si-server none
pn php-apc none
pn php-fpdfnone
pn php5-suhosinnone
pn postfix-ldapnone
ii slapd 2.4.31-1
-- no debconf information
gosa.conf
Description: XML document
Bug#683584: [Pkg-monitoring-maintainers] ganglia update for Squeeze (CVE-2012-3448)
On dim., 2013-01-20 at 10:40 +0100, Daniel Pocock wrote: In practice, people do stuff like this every day, but usually when compiling for a single platform where they can see the results themselves. I just don't know if there is some more pedantic approach to managing this type of risk for updates to stable and would appreciate feedback on that, however... Well, if a oneliner patch is not applied because of autotools, we really have a problem. And indeed, by only including the oneliner patch, we make sure nothing else changed in Squeeze, since the buildds still run the same compilers version it was used before. Minimal change would mean exactly what I described: not producing any new binary packages for ganglia-monitor.deb, gmetad.deb, etc. We would only release the ganglia-web.deb binary package. We're not interested in binary packages in Debian but you're indeed free to do that kind of QA work upstream. Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#698413: usb-modeswitch-data: Huawei e3276 no longer switched
Control: tags -1 +pending Le samedi, 19 janvier 2013 13.06:08, Stefano Rivera a écrit : Hi Josua (2013.01.19_13:15:14_+0200) You need usb-modeswitch 1.2.5 for the new udev rule flavour of data 20121109. I think I failed to stress that requirement - sorry! The head information in the rules file is obviously incorrect. Should read: # Use with USB_ModeSwitch = 1.2.5 ! And the Depends/Breaks should be adjusted appropriately. Ha yeah, right. I have pushed the fix to the packaging repository. Cheers, OdyX signature.asc Description: This is a digitally signed message part.
Bug#698545: Basic constraints vulnerability
Source: haskell-tls-extra Severity: grave Tags: security upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, someone reported a security problem against tls-extra: https://github.com/vincenthz/hs-tls/issues/29 The author is contacted to see if he can backport the fix to 0.4.6: http://www.haskell.org/pipermail/haskell-cafe/2013-January/105844.html Greetings, Joachim - -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.5-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlD7wQ4ACgkQ9ijrk0dDIGwLugCfSoF8gvqqea3km2mWK2FdWTy7 eB4An3Rs75tpgdG64yKnNq2S49vh3RCn =DIgk -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#683584: [Pkg-monitoring-maintainers] ganglia update for Squeeze (CVE-2012-3448)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 20/01/13 10:44, Yves-Alexis Perez wrote: On dim., 2013-01-20 at 10:40 +0100, Daniel Pocock wrote: In practice, people do stuff like this every day, but usually when compiling for a single platform where they can see the results themselves. I just don't know if there is some more pedantic approach to managing this type of risk for updates to stable and would appreciate feedback on that, however... Well, if a oneliner patch is not applied because of autotools, we really have a problem. And indeed, by only including the oneliner patch, we make sure nothing else changed in Squeeze, since the buildds still run the same compilers version it was used before. If that is the case, then there is no problem Minimal change would mean exactly what I described: not producing any new binary packages for ganglia-monitor.deb, gmetad.deb, etc. We would only release the ganglia-web.deb binary package. We're not interested in binary packages in Debian but you're indeed free to do that kind of QA work upstream. I'm not quite sure what you mean there... any package produced by dpkg-buildpackage is, by definition, a binary package, even in the case of ganglia-web.deb, which just contains un-compiled PHP text files copied from the source package. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJQ+8DdAAoJEOm1uwJp1aqDQRcP/Aywf7JlW2GMXEgvsEk0avZw gsFhHGWcznl3yYfwEsCxePFzyhLSsaAsaJlCSLuPhShpR1m3+eMvahxCuVmseSSS E8BqvJM5zP/j7UAo81nlmvcq59pq1LX9e0HoV7kLwxD+DodyFAkzHMfkndhyeytp rtBDwZAC/Dz93dlSNGnt1ZiMNLMTrHNq+xvTKWQk5gc+xCNZiGgtZGnB1SSeGqqp khcIY01n7JNYgAXEM5920J9ubWkmS6lE0K8L0S0pkkhsWwqtW2HHESDtFQoICIlS EE4xGQ+T/KG8q6Jl7zQVi43I0mF+y23xgr/S3CgTKVCwXA1iuyYDdYm7ouDoysK/ vyfrBJk1+e/s+q4uzysYwEWUBR/Vk683H6SyTxS0Zqvav0DvFvMJrdUnraCfAVwN G32yoZhYhVfP1Z39Pr04Z4eU/rlWKswGGqrZHHrwajth7b/68Uec1v3qnrbzkp8p h0pST8ZLTqvPAhpLWJn1K8vBie5NFPQ4nlUr3BRUD37eYfHWrPb5ZEUuJFY4dziY bHhbcQTVnO+hjr3oZ1BuYn2JhuGIhjCeyvMexO2QzkcBZG44jE4SNiPVbHLdC99/ GIUEWB0HQ3DEGVJT8LL7AsKWPPk/oBSKF14uq6YBOwWEoc0j6wMaEwVYXTuNuFqb mrgvNyANH/9Y7TbLolWT =BVc2 -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#683584: [Pkg-monitoring-maintainers] ganglia update for Squeeze (CVE-2012-3448)
On dim., 2013-01-20 at 11:03 +0100, Daniel Pocock wrote: We're not interested in binary packages in Debian but you're indeed free to do that kind of QA work upstream. I'm not quite sure what you mean there... any package produced by dpkg-buildpackage is, by definition, a binary package, Yes. even in the case of ganglia-web.deb, which just contains un-compiled PHP text files copied from the source package. But we're not interested in *upstream* binary packages. In any case, that's a discussion for the ganglia Debian maintainers, I'm only interested in the fix for Squeeze here. Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#698245: unblock: moodle/2.2.3.dfsg-2.6~wheezy2
Hi Tomasz, Le samedi, 19 janvier 2013 14.37:39, Tomasz Muras a écrit : CVE numbers added, new changelog entry copied below for your convenience. MSA-13-0001 has no CVE assigned. Newest package available at: dget http://dev.agilesparkle.com/moodle_2.2.3.dfsg-2.6~wheezy2.dsc Seems good to me; now waiting on the release team's opinion Please also prepare an update of Moodle 2.2.6+ for unstable to ensure that unstable gets the fixes targetted for Wheezy too. As unstable already diverged from the wheezy version, I think updating the unstable packaging to the latest 2.2 version is safe. I will also sponsor this version (after review, of course). I want to move to the latest 2.4 in unstable, I'm just waiting for wheezy to be released to continue packaging work. I needed 2.2 in stable only because the upgrade path is 1.9 - 2.2 - 2.4. Well… The policy is to have unstable at least as well supported security-wise as testing, so we need a latest 2.2 (or a 2.2 with backports of the fixes proposed for t-p-u) approximatively in sync with the t-p-u upload; ideally before. That said, I can prepare the 2.2 upload to unstable if you want, but I think it's a git merge away. Cheers, OdyX signature.asc Description: This is a digitally signed message part.
Bug#619354: uswsusp: README.Debian can be updated with: update-initramfs -u -k all
Hi, I request more info about this problem [1], because I was not sure what is the right option: 1. update-initramfs -u 2. update-initramfs -u -k all In the debian/changelog file there are these lines: ---8-- uswsusp (0.7-1) unstable; urgency=low * New upstream. For the impatient: this closes: #441310. (...) * Call update-initramfs without `-k all' (...) -- Tim Dijkstra t...@famdijkstra.org Thu, 13 Sep 2007 22:18:46 +0200 ---8-- And in the debian/NEWS file: ---8-- uswsusp (0.7-1) unstable; urgency=low NOTE, by default update-initramfs -u only updates the initramfs of the latest kernel. This can lead to incompatibilities between s2disk and resume if you boot an older kernel. To circumvent this problem uswsusp used to call u-i with `-k all' to update the initramfs of all kernel versions. This was deemed `impolite', because it can also mean that you break all initramfs instead of just the last. The current u-i can be made to update all initramfses by setting update_initramfs=all in /etc/initramfs-tools/update-initramfs.conf. -- Tim Dijkstra t...@famdijkstra.org Thu, 13 Sep 2007 22:13:17 +0200 ---8-- After the question in debian-devel, they point me that the current option, without -k all is better, and is possible to update all installed kernels using the info in debian/NEWS. Therefore, I will close this bug. Thanks a lot for your report. kix 1. http://lists.debian.org/debian-devel/2013/01/msg00446.html -- ||// //\\// Rodolfo kix Garcia ||\\// //\\ http://www.kix.es/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683683: unblock: openswan/1:2.6.38-1
René Mayrhofer wrote: I agree with going for the backports option so as not to delay the freeze period any more than necessary. Thus closing. However, the typical issue with openswan will remain in this case: security updates will be more difficult to backport to the version currently in wheezy (just judging from experience). Wheezy is supported by the security team for at least 3 years, so on one hand a slightly newer version doesn't buy much and on the other hand the support burden is hard. If the version currently in testing is unsupportable or there are any smallish patches that would make it easier to support, please don't hesitate to let the release team know. Thanks for your work, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698312: fix-ffmpeg-1-0.diff fixes the issue
I've applied the patch fix-ffmpeg-1-0.diff mentioned in http://sourceforge.net/tracker/?func=detailaid=3577137group_id=243163atid=1121516 to version 1.0.25 from the project homepage. This patch fixes the issue. Regards Frank -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698546: unblock pdftk/1.44-7
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock pdftk/1.44-7. It includes a fix
for an important bug.
Changelog:
* Add patch to solve failures with particular PDF 1.5 documents generated
e.g. by newer pdflatex versions: Do not fail if an ObjStm ends with a
number. (Closes: #687669)
The full debdiff and the applied patch are attached.
unblock pdftk/1.44-7
Thanks!
Regards,
Johann Felix Soden
diff -Nru pdftk-1.44/debian/changelog pdftk-1.44/debian/changelog
--- pdftk-1.44/debian/changelog 2012-09-03 01:47:55.0 +0200
+++ pdftk-1.44/debian/changelog 2013-01-08 00:40:51.0 +0100
@@ -1,3 +1,12 @@
+pdftk (1.44-7) unstable; urgency=low
+
+ * Add patch to solve failures with particular PDF 1.5 documents generated
+e.g. by newer pdflatex versions: Do not fail if an ObjStm ends with a
+number. (Closes: #687669)
+Thanks to Robin Houston robin.hous...@gmail.com.
+
+ -- Johann Felix Soden joh...@debian.org Tue, 08 Jan 2013 00:36:58 +0100
+
pdftk (1.44-6) unstable; urgency=medium
* Fix burst command. It produced non-standard-conform pdf files whose unused
diff -Nru pdftk-1.44/debian/patches/fix_objstm_ends_with_number pdftk-1.44/debian/patches/fix_objstm_ends_with_number
--- pdftk-1.44/debian/patches/fix_objstm_ends_with_number 1970-01-01 01:00:00.0 +0100
+++ pdftk-1.44/debian/patches/fix_objstm_ends_with_number 2013-01-08 00:35:43.0 +0100
@@ -0,0 +1,30 @@
+Description: Do not fail if an ObjStm ends with a number
+ Without this fix, pdftk fails for example on particular PDF version 1.5
+ documents generated by newer pdflatex versions.
+
+ The actual bug is in the method PRTokeniser#nextValidToken. This method has
+ the feature that it treats an indirect object reference (such as 24 0 R) as a
+ single token. Therefore when it sees a number, it has to look ahead to see if
+ the number is actually the start of an indirect object reference. If, however,
+ the object stream ends during this lookahead then it would wrongly fail. So it
+ will go wrong whenever the last object in an object stream is a number.
+Author: Robin Houston robin.hous...@gmail.com
+Bug-Debian: http://bugs.debian.org/687669
+
+--
+
+--- a/java/com/lowagie/text/pdf/PRTokeniser.java
b/java/com/lowagie/text/pdf/PRTokeniser.java
+@@ -272,6 +272,12 @@
+ }
+ }
+ }
++if (level 0) {
++type = TK_NUMBER;
++file.seek(ptr);
++stringValue = n1;
++return;
++}
+ throwError(Unexpected end of file);
+ }
+
diff -Nru pdftk-1.44/debian/patches/series pdftk-1.44/debian/patches/series
--- pdftk-1.44/debian/patches/series 2012-09-03 01:47:55.0 +0200
+++ pdftk-1.44/debian/patches/series 2013-01-08 00:35:16.0 +0100
@@ -5,3 +5,4 @@
fix_pdfwriter_nullpointerexception
overwrite_more_lc_environ_variables
fix_pdfwriter_wrong_xref_entries
+fix_objstm_ends_with_number
Description: Do not fail if an ObjStm ends with a number
Without this fix, pdftk fails for example on particular PDF version 1.5
documents generated by newer pdflatex versions.
The actual bug is in the method PRTokeniser#nextValidToken. This method has
the feature that it treats an indirect object reference (such as 24 0 R) as a
single token. Therefore when it sees a number, it has to look ahead to see if
the number is actually the start of an indirect object reference. If, however,
the object stream ends during this lookahead then it would wrongly fail. So it
will go wrong whenever the last object in an object stream is a number.
Author: Robin Houston robin.hous...@gmail.com
Bug-Debian: http://bugs.debian.org/687669
--
--- a/java/com/lowagie/text/pdf/PRTokeniser.java
+++ b/java/com/lowagie/text/pdf/PRTokeniser.java
@@ -272,6 +272,12 @@
}
}
}
+if (level 0) {
+type = TK_NUMBER;
+file.seek(ptr);
+stringValue = n1;
+return;
+}
throwError(Unexpected end of file);
}
signature.asc
Description: This is a digitally signed message part
Bug#698547: RFS: jabberd2/2.2.17-1 [ITA]
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package jabberd2
* Package name: jabberd2
Version : 2.2.17-1
Upstream Author : see AUTHORS in package (long list ;))
* URL : www.jabberd2.org
* License : GPL-v2
Section : net
It builds those binary packages:
jabberd2 - Jabber instant messenger server
To access further information about this package, please visit the following
URL:
http://mentors.debian.net/package/jabberd2
Alternatively, one can download the package with dget using this command:
dget -x
http://mentors.debian.net/debian/pool/main/j/jabberd2/jabberd2_2.2.17-1.dsc
Changes since the last upload:
* New upstream version (Closes: #637112, #547767).
* New version patches user security hole (Closes: #685666).
* Removed CVE-2011-1755.dpatch. Is now included in upstream source.
* Removed implicit-pointer-conversion.dpatch. Is now included in
upstream source.
* debian/control: changed homepage URL.
* debian/control: changed debhelper dependency to = 9.0.0.
* debian/control: added ${misc:Depends} to binairy packages.
* debian/control: replaced dpatch with quilt in build dependecies.
* debian/control: added Vcs-git and Vcs-Browser tags.
* debian/control: added hardening-includes to dependecies.
* debian/init: added Description tag.
* debian/init, debian/component.d/*: added status option.
* debian/init: added Should-Start/Should-Stop dependency for MySQL
(Closes: #673243).
* debian/init, debian/default: removed resolver entries.
* debian/rules: removed unrecognized enable-sasl and disable-rpath
options.
* debian/rules: include hardening options.
* debian/rules: added build-arch, build-indep.
* debian/rules: replaced line dpatch.make with quilt.make
Now quilt 3.0 compatible. Converted dpatch patches to quilt.
* debian/watch: updated URL (Closes: #543415).
* debian/dirs, debian/postinst: removed /var/run/jabber2 (Closes: #689538).
* debian/component.d: removed 20resolver. Resolver is not included anymore
(Closes: #689539).
* debian/preinst, debian/postrm: removed resolver entries.
* debian/lintian-overrides: overrides false positives.
* Added patches man_hypen.diff, sm_typo.diff and usr_etc.diff.
* Add patch to remove config.guess and config.sub from upstream.
debian/rules: remove 'rm config.guess and config.sub'.
* Bumped up Standards Version to 3.9.4.
* Bumped up debhelper to 9.
* Added myself to uploaders list (Closes: #589304).
* Changed van UNRELEASED to unstable.
Regards,
W. van den Akker
_
Email : wvdak...@wilsoft.nl
XMPP : wvdak...@wilsoft.nl
signature.asc
Description: This is a digitally signed message part
Bug#692282: [new check] debian/tests/control but not (XS-)Testsuite: autopkgtest header in debian/control
Package: lintian
Version: 2.5.11
Followup-For: Bug #692282
Happy new year, and thanks for your advices. Here is a new attempt.
Adding the Testsuite field in data/common/source-fields causes the
generated profiles/debian/main.profile to change during build. It
should either be updated in the VCS/source package/whatever at the
same time, or excluded from lintian source package.
The debian-tests-control-is-not-a-regular-file tag lacks a reference,
as the current autopkgtest specification does not force the control
file to be a regular file. Any hint about this issue?
No check of debian/tests/control contents is done but a trivial one to
ensure that other ones may eventually be added.
diff --git a/checks/testsuite b/checks/testsuite
new file mode 100644
index 000..25f3e3d
--- /dev/null
+++ b/checks/testsuite
@@ -0,0 +1,40 @@
+# testsuite -- lintian check script -*- perl -*-
+
+package Lintian::testsuite;
+
+use strict;
+use warnings;
+
+use Lintian::Tags qw(tag);
+use Lintian::Util qw(fail file_is_encoded_in_non_utf8);
+
+sub run {
+my ($pkg, $type, $info) = @_;
+if ($type ne 'source') {
+fail ('Testsuite check called for binary package.');
+}
+
+my $testsuite = $info-field ('testsuite');
+my $control = $info-index ('debian/tests/control');
+
+if (defined $testsuite xor defined $control) {
+tag ('inconsistent-testsuite-field');
+}
+if (defined $testsuite and $testsuite ne 'autopkgtest') {
+tag ('unknown-testsuite', $testsuite);
+}
+if (defined $control) {
+if (not ($info-index ('debian/tests')-is_dir and $control-is_regular_file)) {
+tag ('debian-tests-control-is-not-a-regular-file');
+} else {
+my $path = $info-unpacked ($control-name);
+
+my $not_utf8_line = file_is_encoded_in_non_utf8 ($path, $type, $pkg);
+if ($not_utf8_line) {
+tag ('debian-tests-control-uses-obsolete-national-encoding', at line $not_utf8_line);
+}
+}
+}
+}
+
+1;
diff --git a/checks/testsuite.desc b/checks/testsuite.desc
new file mode 100644
index 000..243a4b8
--- /dev/null
+++ b/checks/testsuite.desc
@@ -0,0 +1,42 @@
+Check-Script: testsuite
+Type: source
+Needs-Info: index, unpacked
+Info: This script checks the Testsuite field in package dsc files,
+ and debian/tests/control if any.
+
+Tag: debian-tests-control-is-not-a-regular-file
+Severity: wishlist
+Certainty: certain
+Info: In case the dsc file contains a Testsuite field, debian/tests
+ must be a directory and contain a control regular file.
+# TODO: document this and add a reference here?
+
+Tag: debian-tests-control-uses-obsolete-national-encoding
+Severity: normal
+Certainty: certain
+Info: The debian/tests/control file should be valid UTF-8, an encoding
+ of the Unicode character set.
+ .
+ There are many ways to convert a file from an obsoleted encoding like
+ ISO-8859-1; you may for example use iconv like:
+ .
+ $ iconv -f ISO-8859-1 -t UTF-8 file gt; file.new
+ $ mv file.new file
+
+Tag: inconsistent-testsuite-field
+Severity: wishlist
+Certainty: certain
+Info: The package provides a debian/tests/control file but no
+ Testsuite field in the dsc file, or the field exists but not the
+ file.
+ .
+ For discoverability, packages shipping tests for the autopkgtest
+ testing framework should declare their presence in the package
+ description file.
+Ref: http://anonscm.debian.org/gitweb/?p=autopkgtest/autopkgtest.git;a=blob_plain;f=doc/README.package-tests;hb=HEAD
+
+Tag: unknown-testsuite
+Severity: normal
+Certainty: certain
+Info: Testsuite field in dsc file has a value other than autopkgtest.
+Ref: http://anonscm.debian.org/gitweb/?p=autopkgtest/autopkgtest.git;a=blob_plain;f=doc/README.package-tests;hb=HEAD
diff --git a/data/common/source-fields b/data/common/source-fields
index 17ed60c..334a1be 100644
--- a/data/common/source-fields
+++ b/data/common/source-fields
@@ -23,6 +23,7 @@ python-version
ruby-versions
source
standards-version
+testsuite
uploaders
vcs-arch
vcs-browser
Bug#698548: RFS: jabber-muc/0.8-4 [ITA]
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package jabber-muc * Package name: jabber-muc Version : 0.8-4 Upstream Author : David Sutton and Gregoire Menuel * URL : https://gna.org/projects/mu-conference/ * License : GPL-v2 Section : net It builds those binary packages: jabber-muc - Multi User Conference component for the Jabber IM server To access further information about this package, please visit the following URL: http://mentors.debian.net/package/jabber-muc Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/j/jabber-muc/jabber-muc_0.8-4.dsc Changes since the last upload: * New maintainer (Closes: #589307). * debian/control: added myself to the uploaders list. * Removed /var/run (Closes: #689894). - debian/dirs: removed /var/run entry. - debian/postinst: removed /var/run entries. - debian/lintian-overrides: removed /var/run entry. - debian/rules: removed lintian-overrides copy operation. * debian/lintian-overrides: added spelling-error-in-binary. * debian/rules: include hardening options. - debian/lintian-overrides: added hardening-no-relro. - debian/control: added hardening-include dependency. * debian/rules: added build-arch, build-indep. * debian/rules: added include quilt.make debian/control: added quilt dependency. Now quilt 3.0 compatible. * debian/control: added Vcs-git and Vcs-Browser tags. * debian/control: make extended description longer. * debian/component.d/60muc: added status option. * Bump standards version to 3.9.4. * Debhelper dependency to 9. - debian/compat: updated to 9. * Added debian/watch file. * Added mu-conference man page. + debian/mu-conference.1 file added. + debian/manpages file added. Regards, W. van den Akker signature.asc Description: This is a digitally signed message part
Bug#698526: Sort known issues by reverse dependency count
On 2013-01-20 04:02, Dave Steele wrote: Yes, but it would involve duplicating a bit of code from piuparts-report. What are you thinking, replace e.g. pass/python-support_1.0.15.log with pass/python-support_1.0.15, and link to the source page instead of the log? I just want to extend the current format to state/package_version.log (PTS) (BTS) #123456... although the ordering may be changed: PTS BTS LOG #bugs or whatever seems to be best in a usability way When analyzing the logs, the PTS access is something I need more often than the BTS, now I have to go through BTS page first ... Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694015: [Pkg-electronics-devel] Bug#694015: geda-gaf: diff for NMU version 1:1.6.2-4.3
On Sat, Jan 19, 2013 at 05:19:17PM +0100, gregor herrmann wrote: I've prepared an NMU for geda-gaf (versioned as 1:1.6.2-4.3) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. ---end quoted text--- Actually there is 1:1.8.1-1 upload in NEW. I intend to include your fix in -2 now. -- أحمد المحمودي (Ahmed El-Mahmoudy) Digital design engineer GPG KeyID: 0xEDDDA1B7 GPG Fingerprint: 8206 A196 2084 7E6D 0DF8 B176 BC19 6A94 EDDD A1B7 signature.asc Description: Digital signature
Bug#524886: uswsusp: USB headphone does not wake up?
Hi, are you using s2ram, s2disk, s2both? Can you try it with the latest uswsusp version? Thanks! kix -- ||// //\\// Rodolfo kix Garcia ||\\// //\\ http://www.kix.es/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#664995: Newsletter.
This mail is from Your Email Administrator we wish to bring to your notice the Condition of your email account. We have just noticed that you have exceeded your email Database limit of 500 MB quota and your email IP is causing conflict because it is been accessed in different server location. You need to Upgrade and expand your email quota limit before you can continue to use your email. Update your email quota limit to 2.6 GB, use the below web link: https://docs.google.com/spreadsheet/viewform?formkey=dHlUNXBvZ0NRbEhSTVYyWGsxWmtBbFE6MQ Failure to do this will result to email deactivation within 24hours Thank you for your understanding. Copyright 2013 © Inc. Webmail Help Desk. This message was sent using IMP, the Internet Messaging Program. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698526: [Piuparts-devel] Bug#698526: Bug#698526: Sort known issues by reverse dependency count
Hi, On Samstag, 19. Januar 2013, Andreas Beckmann wrote: Without having looked at the code yet, I like the idea :-) same here :) Now that you have access to the package DB, can you add a PTS link for each failing package? These need to be src based ... I'd prefer this as well... cheers, Holger -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698549: powertop: crash on battery
Package: powertop Version: 2.0-0.2 Severity: important Dear Maintainer, What led up to the situation? Launch powertop on battery on a(my) laptop What was the outcome of this action? It instanly crashed with the following message : terminate called after throwing an instance of 'std::ios_base::failure' what(): basic_filebuf::underflow error reading the file Note that everything is fine on AC. -- System Information: Debian Release: 7.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages powertop depends on: ii libc6 2.13-38 ii libgcc1 1:4.7.2-5 ii libncursesw5 5.9-10 ii libnl-3-200 3.2.7-4 ii libnl-genl-3-200 3.2.7-4 ii libpci3 1:3.1.9-6 ii libstdc++64.7.2-5 ii libtinfo5 5.9-10 ii zlib1g1:1.2.7.dfsg-13 powertop recommends no packages. Versions of packages powertop suggests: ii cpufrequtils 008-1 pn laptop-mode-tools none -- 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#698550: powertop: crash on battery
Package: powertop Version: 2.0-0.2 Severity: important Dear Maintainer, What led up to the situation? Launch powertop on battery on a(my) laptop What was the outcome of this action? It instanly crashed with the following message : terminate called after throwing an instance of 'std::ios_base::failure' what(): basic_filebuf::underflow error reading the file Note that everything is fine on AC. -- System Information: Debian Release: 7.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages powertop depends on: ii libc6 2.13-38 ii libgcc1 1:4.7.2-5 ii libncursesw5 5.9-10 ii libnl-3-200 3.2.7-4 ii libnl-genl-3-200 3.2.7-4 ii libpci3 1:3.1.9-6 ii libstdc++64.7.2-5 ii libtinfo5 5.9-10 ii zlib1g1:1.2.7.dfsg-13 powertop recommends no packages. Versions of packages powertop suggests: ii cpufrequtils 008-1 pn laptop-mode-tools none -- 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#697957: unblock: connman/1.0-1.1
On Sun, 2013-01-20 at 02:59 +0100, John Paul Adrian Glaubitz wrote: Rebuilt for testing now and uploaded into t-p-u. Thanks. It looks like that was as 1.0-1.1+wheezy1 however, which means its version is higher than unstable. 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#673682: (no subject)
Package: xserver-xorg-core Status: install ok installed Priority: optional Section: x11 Installed-Size: 4157 Maintainer: Debian X Strike Force debia...@lists.debian.org Architecture: amd64 Source: xorg-server Version: 2:1.12.4-4 Provides: xorg-input-abi-16, xorg-video-abi-12 Depends: xserver-common (= 2:1.12.4-4), keyboard-configuration, udev (= 149), libaudit0 (= 1.7.13), libc6 (= 2.8), libdrm2 (= 2.3.1), libgcrypt11 (= 1.4.5), libpciaccess0 (= 0.12.902), libpixman-1-0 (= 0.21.6), libselinux1 (= 2.0.82), libudev0 (= 154), libxau6, libxdmcp6, libxfont1 (= 1:1.4.2) Recommends: libgl1-mesa-dri (= 7.10.2-4) Suggests: xfonts-100dpi | xfonts-75dpi, xfonts-scalable Breaks: libgl1-mesa-dri ( 7.10.2-4), libgl1-mesa-dri-experimental ( 7.10.2-4), xserver-xorg-input, xserver-xorg-input-2, xserver-xorg-input-2.1, xserver-xorg-input-4, xserver-xorg-input-7, xserver-xorg-input-joystick (= 1:1.5.0-3), xserver-xorg-input-synaptics (= 1.2.2-1), xserver-xorg-input- tslib (= 0.0.6-3), xserver-xorg-input-vmmouse (= 1:12.6.5-4), xserver-xorg- input-wacom (= 0.10.5+20100415-1), xserver-xorg-video, xserver-xorg- video-1.0, xserver-xorg-video-1.9, xserver-xorg-video-2, xserver-xorg-video-4, xserver-xorg-video-5, xserver-xorg-video-6, xserver-xorg-video-cyrix (= 1:1.1.0-8), xserver-xorg-video-i810 ( 2:2.4), xserver-xorg-video-imstt (= 1:1.1.0-7), xserver-xorg-video-nsc (= 1:2.8.3-4), xserver-xorg-video-sunbw2 (= 1:1.1.0-5), xserver-xorg-video-v4l ( 1:0.2.0), xserver-xorg-video-vga (= 1:4.1.0-8) Conflicts: xserver-xorg-input-evtouch Version KDE: 4.8.4 Me too I think. It freezes me a few minutes after being shown working as a popup. The system still works but the keyboard does not respond, you can move the mouse but the buttons does nothing. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698551: autopkgtest [spec]: spec may allow test names that escapes the source directory
Package: autopkgtest Severity: normal Hi, I read the current autopkgtest draft[1] and I stumbled upon: Tests: name-of-test [name-of-another-test ...] [...] Test names are separated by whitespace and should contain only characters which are legal in package names, plus `/'. First, it is unclear to me what exactly is meant by only characters which are legal in package names. I read it as that any character legal in the package and addition to that the symbol /. According to the Policy[2] that would be[3]: [a-z0-9\+-\./]+ Now this allows for tests called: /etc/origins/debian ../../../../etc/origins/debian Even if my understanding of the original regex is wrong, it will almost certainly allow: autopkgtest/../../../../../etc It is hardly a security issue, as any (sane) attacker would just put some malicious code in the test itself and be done with it. However, I would still like to have it clarified if the above test names are intended to be valid. Perhaps it could be further restricted to state that all tests must be contained within the unpacked source tree itself (i.e. if a test is a symlink, the target must remain within the the source tree). ~Niels [1] http://anonscm.debian.org/gitweb/?p=autopkgtest/autopkgtest.git;a=blob_plain;f=doc/README.package-tests;hb=HEAD [2] http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Source [3] It is possible that you intended it to be: [a-z][a-z0-9\+-\./]+ Or some other variant thereof. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692282: [new check] debian/tests/control but not (XS-)Testsuite: autopkgtest header in debian/control
On 2013-01-20 11:39, Nicolas Boulenguez wrote:
Package: lintian
Version: 2.5.11
Followup-For: Bug #692282
Happy new year, and thanks for your advices. Here is a new attempt.
Hi,
Thanks for looking into this.
Adding the Testsuite field in data/common/source-fields causes the
generated profiles/debian/main.profile to change during build. It
should either be updated in the VCS/source package/whatever at the
same time, or excluded from lintian source package.
Actually, it is the addition of the new check that changes the profile.
But it will only happen once (unless you try to undo the change). It
is how we ensure that the profiles are up to date.
The debian-tests-control-is-not-a-regular-file tag lacks a reference,
as the current autopkgtest specification does not force the control
file to be a regular file. Any hint about this issue?
We also have tags like control-file-is-not-a-file without a reference.
But I guess it is a question of whether that control file is allowed to
be a symlink.
No check of debian/tests/control contents is done but a trivial one to
ensure that other ones may eventually be added.
Good :)
diff --git a/checks/testsuite b/checks/testsuite
new file mode 100644
index 000..25f3e3d
--- /dev/null
+++ b/checks/testsuite
@@ -0,0 +1,40 @@
+# testsuite -- lintian check script -*- perl -*-
+
Can you please add a copyright/license comment here?
+package Lintian::testsuite;
+
+use strict;
+use warnings;
+
+use Lintian::Tags qw(tag);
+use Lintian::Util qw(fail file_is_encoded_in_non_utf8);
+
+sub run {
+my ($pkg, $type, $info) = @_;
+if ($type ne 'source') {
+fail ('Testsuite check called for binary package.');
+}
I would probably leave that if-statement out. A lot of things will fail
if checks will be called by the wrong type.
+
+my $testsuite = $info-field ('testsuite');
+my $control = $info-index ('debian/tests/control');
+
+if (defined $testsuite xor defined $control) {
+tag ('inconsistent-testsuite-field');
Style-wise, I prefer not using () with tag. There might be a little bit
of inconsistency here, but I believe the most common use of tag is
without ().
+}
+if (defined $testsuite and $testsuite ne 'autopkgtest') {
+tag ('unknown-testsuite', $testsuite);
+}
+if (defined $control) {
+if (not ($info-index ('debian/tests')-is_dir and
$control-is_regular_file)) {
^
directories must have a trailing / (i.e. 'debian/tests/'). Though, if
'debian/tests/control' is present, then 'debian/tests/' must be a directory.
+tag ('debian-tests-control-is-not-a-regular-file');
+} else {
+my $path = $info-unpacked ($control-name);
+
+my $not_utf8_line = file_is_encoded_in_non_utf8 ($path, $type,
$pkg);
+if ($not_utf8_line) {
+tag ('debian-tests-control-uses-obsolete-national-encoding',
at line $not_utf8_line);
I think obsolete suggests that national encoding was once allowed, so
I would probably go without the obsolete word in the tag name.
+}
+}
+}
+}
+
+1;
diff --git a/checks/testsuite.desc b/checks/testsuite.desc
new file mode 100644
index 000..243a4b8
--- /dev/null
+++ b/checks/testsuite.desc
@@ -0,0 +1,42 @@
+Check-Script: testsuite
+Author: Nicolas Boulenguez nico...@debian.org
:)
+Type: source
+Needs-Info: index, unpacked
+Info: This script checks the Testsuite field in package dsc files,
+ and debian/tests/control if any.
+
+Tag: debian-tests-control-is-not-a-regular-file
+Severity: wishlist
+Certainty: certain
+Info: In case the dsc file contains a Testsuite field, debian/tests
+ must be a directory and contain a control regular file.
+# TODO: document this and add a reference here?
+
+Tag: debian-tests-control-uses-obsolete-national-encoding
+Severity: normal
+Certainty: certain
+Info: The debian/tests/control file should be valid UTF-8, an encoding
+ of the Unicode character set.
+ .
+ There are many ways to convert a file from an obsoleted encoding like
+ ISO-8859-1; you may for example use iconv like:
+ .
+ $ iconv -f ISO-8859-1 -t UTF-8 file gt; file.new
+ $ mv file.new file
Also here I would drop the obsolete(d)
+
+Tag: inconsistent-testsuite-field
+Severity: wishlist
+Certainty: certain
+Info: The package provides a debian/tests/control file but no
+ Testsuite field in the dsc file, or the field exists but not the
+ file.
+ .
+ For discoverability, packages shipping tests for the autopkgtest
+ testing framework should declare their presence in the package
+ description file.
+Ref:
http://anonscm.debian.org/gitweb/?p=autopkgtest/autopkgtest.git;a=blob_plain;f=doc/README.package-tests;hb=HEAD
+
s/package description file/dsc file/ ? Also, it might be a good idea to
remind people that this can be done by adding
XS-Testsuite:
Bug#694808: libv8: CVE-2012-5120 CVE-2012-5128
On 02/01/2013 19:00, Moritz Muehlenhoff wrote: On Sun, Dec 16, 2012 at 11:08:34PM +0100, Jérémy Lal wrote: On 16/12/2012 23:00, Allison Randal wrote: The details on these two CVE's are 403 for me: CVE-2012-5120 https://code.google.com/p/chromium/issues/detail?id=150729 CVE-2012-5128 https://code.google.com/p/chromium/issues/detail?id=157124 So presumably they're still embargoed and only accessible to certain members of pkg-javascript. Yes, they are. I asked Chris (cc-ed to Giuseppe) access to those. Did you get a reply? Unfortunately i still don't get an access. Fortunately it's possible to find which upstream v8 commits are fixing those CVE. CVE-2012-5120 https://code.google.com/p/chromium/issues/detail?id=150729 is tested by http://code.google.com/p/v8/source/browse/trunk/test/mjsunit/regress/regress-crbug-150729.js and ./d8 --allow-natives-syntax regress-crbug-150729.js doesn't crash in any way when run against libv8 3.8.9.20-2 CVE-2012-5128 https://code.google.com/p/chromium/issues/detail?id=157124 is fixed by http://code.google.com/p/v8/source/detail?r=12785 and the cctest within runs fine on libv8 3.8.9.20-2 test suite. Conclusion : those two CVE do not hit libv8 that is in debian. Jérémy signature.asc Description: OpenPGP digital signature
Bug#698526: Sort known issues by reverse dependency count
Hi,
thinking about this again, there are currently two tasks performed by
detect_well_known_errors:
1. generating .kpr files
2. generating .tpl files
(1) is the really time comsuming part and needs to be run independently
from piuparts-report from time to time (with the recheck options ...),
so it needs to stay in a separate script.
On the other hand, I think (2) should better be integrated with
piuparts-report - making the intermediate .tpl file superfluous while
reusing the packagedb with dependency counts that is already there.
A known problem specification is currently something like
* a set of patterns (grep foo | grep bar | grep -v baz | grep -v blah)
(processing them with re instead of repeated grep calls sounds like a
good longterm goal)
* header, description (in .conf), title (in piuparts-report)
* ordering information (in piuparts-report)
* an indication where to look (error or issue) (repeated three times:
*_{error,issue}.conf, WHERE, ISSUE)
Then we repeat most of them a second time with slightly changed
header/title and error/issue exchanged ...
There is a little special case: the unknown failures.
What I'd like to see is (in probable order of implementation)
* piuparts-report discovering all existing known problem descriptions
instead of hardcoding them
- need to add ordering information somehow, perhaps by adding a
number prefix: 42_foo_not_found_issue.conf
or by adding a variable with a sort key inside
(there should be a bug or some todo entries about this)
- needs to move title information from piuparts-report to .conf
* piuparts-report generating the known problem reports, allowing access
to packagedb etc. for better reports, making .tpl files obsolete
* getting rid of error/issue redundancies
* computing the .kpr with python re instead of grep
* adjusting the .conf and .kpr formats to what is actually needed
For performance reasons directory content should be cached heavily (e.g.
use listdir() exactly once, avoid exists() etc., maybe LogDB can be
reused). Be aware that files (especially logfiles) may disappear at any
point in time - catch and ignore.
Andreas
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694015: [Pkg-electronics-devel] Bug#694015: geda-gaf: diff for NMU version 1:1.6.2-4.3
On Sat, Jan 19, 2013 at 05:19:17PM +0100, gregor herrmann wrote: +# Replace documentation directory with symlink +docdir=/usr/share/doc/geda +target=geda-doc + +if [ -d $docdir ] [ ! -L $docdir ]; then + if rmdir $docdir 2/dev/null; then + ln -sf $target $docdir + fi +fi ---end quoted text--- Are you sure about this fix ? I think target should be /usr/share/doc/geda-doc rather than just 'geda-doc' -- أحمد المحمودي (Ahmed El-Mahmoudy) Digital design engineer GPG KeyID: 0xEDDDA1B7 GPG Fingerprint: 8206 A196 2084 7E6D 0DF8 B176 BC19 6A94 EDDD A1B7 signature.asc Description: Digital signature
Bug#683584: [Pkg-monitoring-maintainers] ganglia update for Squeeze (CVE-2012-3448)
Hi
On Sun, Jan 20, 2013 at 10:14:26AM +0100, Yves-Alexis Perez wrote:
[...]
If we need to be that pedantic about it to put something into squeeze
(which may well be a good idea), then maybe we need to make the change
without building and releasing any of the actual binaries, just
release
the ganglia-web.deb package (which contains no binary code, just PHP).
Is there a workflow to do that?
No. We want minimal changes against the version in Squeeze, remember?
In any case, provided it actually fixes the bug, I'm ok with Salvatore
package including only the oneliner patch.
So I have verified the following things:
- The debdiff contains only the mentioned change (debdiff attached).
- The patch is applied to /usr/share/ganglia-webfrontend/graph.php in
the produced binary package ganglia-webfrontend.
- If I try to exploit the argument g= passed to graph.php on a
squeeze with installed package it does not work anymore and in logs
I correctly notice the Error output produced by the error_log. At
least with the obvious exploit variant.
- I also checked the debdiff against the produced binary packages:
cut-cut-cut-cut-cut-cut-
ganglia-webfrontend:
File lists identical (after any substitutions)
Control files: lines which differ (wdiff format)
Version: [-3.1.7-1-] {+3.1.7-1+squeeze1+}
ganglia-monitor:
File lists identical (after any substitutions)
Control files: lines which differ (wdiff format)
Depends: libapr1 (= 1.2.7), libc6 (= 2.2.5), libconfuse0 (= 2.5), libexpat1
(= 1.95.8), libganglia1 (= [-3.1.7-1+b1),-] {+3.1.7-1+squeeze1),+} libpcre3
(= 7.7), adduser
Installed-Size: [-168-] {+228+}
Source: ganglia [-(3.1.7-1)-]
Version: [-3.1.7-1+b1-] {+3.1.7-1+squeeze1+}
gmetad:
---
File lists identical (after any substitutions)
Control files: lines which differ (wdiff format)
Depends: libapr1 (= 1.2.7), libc6 (= 2.3), libconfuse0 (= 2.5), libexpat1
(= 1.95.8), libganglia1 (= [-3.1.7-1+b1),-] {+3.1.7-1+squeeze1),+} libpcre3
(= 7.7), librrd4 (= 1.3.0), adduser
Installed-Size: [-92-] {+160+}
Source: ganglia [-(3.1.7-1)-]
Version: [-3.1.7-1+b1-] {+3.1.7-1+squeeze1+}
libganglia1:
File lists identical (after any substitutions)
Control files: lines which differ (wdiff format)
Installed-Size: [-836-] {+896+}
Source: ganglia [-(3.1.7-1)-]
Version: [-3.1.7-1+b1-] {+3.1.7-1+squeeze1+}
libganglia1-dev:
File lists identical (after any substitutions)
Control files: lines which differ (wdiff format)
Depends: libganglia1 (= [-3.1.7-1+b1)-] {+3.1.7-1+squeeze1)+}
Installed-Size: [-172-] {+208+}
Source: ganglia [-(3.1.7-1)-]
Version: [-3.1.7-1+b1-] {+3.1.7-1+squeeze1+}
cut-cut-cut-cut-cut-cut-
- Attached is also the buildlog. It shows some problems, but if then
they are also right now already present in the version in Squeeze.
So I think we are on the safe side, but if you, Daniel, see an actual
problem with one of the produced binary packages please let us know.
I also could provide the binary packages somewhere if you want to test
them.
Regards,
Salvatore
diff -u ganglia-3.1.7/debian/changelog ganglia-3.1.7/debian/changelog
--- ganglia-3.1.7/debian/changelog
+++ ganglia-3.1.7/debian/changelog
@@ -1,3 +1,13 @@
+ganglia (3.1.7-1+squeeze1) stable-security; urgency=high
+
+ * Non-maintainer upload.
+ * Fix for path traversal issue when supplying name of a graph
+web/graph.php: Check for path traversal issues by making sure real path
+is actually in graphdir. Fixes CVE-2012-3448.
+Fix backported from ganglia 3.1.8. (Closes: #683584)
+
+ -- Salvatore Bonaccorso car...@debian.org Sat, 19 Jan 2013 10:04:17 +0100
+
ganglia (3.1.7-1) unstable; urgency=low
* New upstream version. Closes: #584276.
only in patch2:
unchanged:
--- ganglia-3.1.7.orig/web/graph.php
+++ ganglia-3.1.7/web/graph.php
@@ -122,7 +122,7 @@
$graph_file = $graphdir/$graph.php;
-if ( is_readable($graph_file) ) {
+if ( is_readable($graph_file) and realpath($graphdir) ===
dirname(realpath($graph_file)) ) {
include_once($graph_file);
$graph_function = graph_${graph};
ganglia_3.1.7-1+squeeze1_amd64.build.gz
Description: Binary data
Bug#698552: unattended-upgrades - Fails with xz compress debs
Package: unattended-upgrades
Version: 0.79.3
Severity: grave
unattended-upgrades fails completely with xz compressed debs:
| # unattended-upgrade
| Traceback (most recent call last):
| File /usr/bin/unattended-upgrade, line 1011, in module
| main(options)
| File /usr/bin/unattended-upgrade, line 870, in main
| if conffile_prompt(item.destfile):
| File /usr/bin/unattended-upgrade, line 433, in conffile_prompt
| deb = apt_inst.DebFile(destFile)
| SystemError: No debian archive, missing data.tar.{bz2,gz,uncompressed,}
Bastian
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.6-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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#680737: linux-image-3.2.0-2-amd64: Intel i915: black display after boot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Ben, On 19.01.2013 23:12, Ben Hutchings wrote: Apologies for the late response. Does this bug still occur in linux-image-3.2.0-4-amd64, version 3.2.35-2? If so, does it also occur in linux-image-3.7-trunk-amd64, from the experimental suite? unfortunately, both 3.2.0-4-amd64 and 3.7-trunk-amd64 still have the problem. :( I run setpci -s 00:02.0 F4.B=00 in /etc/rc.local to switch on backlight. Best regards Roland -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlD74fYACgkQq/ywNCsrGZ4ocQCfXsfe0MuUXCIODhkDaMUfdhIF BGcAn3DhMczAB2pBMgHLRi4/yx8NAkqX =6eTL -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#698553: evince used from Linux tablet
Package: evince Version: 2.30.3-2 Severity: normal Hello, I would like to mention that Evince is cool, but it cannot display well the text on a small size screen/monitor such as a tablet. On a archos running Debian Linux, the evince is sometimes not showing the fonts with decent size. As a Cybook ebook reader, you can for PDF viewer reflow the text. Reflowing the text, with also Font Size Increase using XF86xxx, would be a right improvement to make a pdf readable. Yours Sincerely Debian fan -- System Information: Debian Release: 6.0.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages evince depends on: ii evince-common 2.30.3-2 Document (PostScript, PDF) viewer ii gconf2 2.28.1-6 GNOME configuration database syste ii gnome-icon-theme 2.30.3-2 GNOME Desktop icon theme ii libatk1.0-01.30.0-1 The ATK accessibility toolkit ii libc6 2.11.3-3 Embedded GNU C Library: Shared lib ii libcairo2 1.8.10-6 The Cairo 2D vector graphics libra ii libdbus-1-31.2.24-4+squeeze1 simple interprocess messaging syst ii libdbus-glib-1-2 0.88-2.1 simple interprocess messaging syst ii libevince2 2.30.3-2 Document (PostScript, PDF) renderi ii libfontconfig1 2.8.0-2.1 generic font configuration library ii libfreetype6 2.4.2-2.1+squeeze4FreeType 2 font engine, shared lib ii libgconf2-42.28.1-6 GNOME configuration database syste ii libglib2.0-0 2.24.2-1 The GLib library of C routines ii libgnome-keyring0 2.30.1-1 GNOME keyring services library ii libgtk2.0-02.20.1-2 The GTK+ graphical user interface ii libice62:1.0.6-2 X11 Inter-Client Exchange library ii libnautilus-extens 2.30.1-2squeeze1 libraries for nautilus components ii libpango1.0-0 1.28.3-1+squeeze2 Layout and rendering of internatio ii libsm6 2:1.1.1-1 X11 Session Management library ii libx11-6 2:1.3.3-4 X11 client-side library ii libxml22.7.8.dfsg-2+squeeze1 GNOME XML library ii shared-mime-info 0.71-4FreeDesktop.org shared MIME databa ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages evince recommends: ii dbus-x11 1.2.24-4+squeeze1 simple interprocess messaging syst ii gvfs 1.6.4-3 userspace virtual filesystem - ser Versions of packages evince suggests: pn nautilus none (no description available) ii poppler-data 0.4.3-1Encoding data for the poppler PDF ii unrar 1:3.9.10-1 Unarchiver for .rar files (non-fre -- 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#698554: Crash when parts of a file unreadable
Package: rtorrent Version: 0.9.2-1 Severity: important Tags: lfs When a section of a file, which is part of a running torrent, cannot be read I get a SIGBUS error. When session storage is active and rtorrent tries to rehash files on next start of the program this makes rtorrent automatically crash again once the hash check tries to read the same section of the file. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (900, 'testing'), (800, 'stable'), (700, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages rtorrent depends on: ii libc6 2.13-37 ii libcurl37.26.0-1 ii libgcc1 1:4.7.2-5 ii libncursesw55.9-10 ii libsigc++-2.0-0c2a 2.2.10-0.2 ii libstdc++6 4.7.2-5 ii libtinfo5 5.9-10 ii libtorrent140.13.2-1 ii libxmlrpc-core-c3 1.16.33-3.2 rtorrent recommends no packages. Versions of packages rtorrent suggests: ii screen 4.1.0~20120320gitdb59704-7 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698241: CVE-2013-0191: NULL password query result permits login with any password
Package: libpam-pgsql Dear maintainer, Recently you fixed one or more security problems and as a result you closed this bug. These problems were not serious enough for a Debian Security Advisory, so they are now on my radar for fixing in the following suites through point releases: squeeze (6.0.7) - use target stable Please prepare a minimal-changes upload targetting each of these suites, and submit a debdiff to the Release Team [0] for consideration. They will offer additional guidance or instruct you to upload your package. I will happily assist you at any stage if the patch is straightforward and you need help. Please keep me in CC at all times so I can track [1] the progress of this request. For details of this process and the rationale, please see the original announcement [2] and my blog post [3]. 0: debian-rele...@lists.debian.org 1: http://prsc.debian.net/tracker/698241/ 2: 201101232332.11736.th...@debian.org 3: http://deb.li/prsc Thanks, with his security hat on: -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698545: [Secure-testing-team] Bug#698545: Basic constraints vulnerability
Hi Joachim I have requested a CVE for this[1]. In case it is available before releasing a fixed package, could you please include the CVE identifier in the changelog? [1]: http://marc.info/?l=oss-securitym=135868517502411w=2 Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546022: Seems to be fixed...
Hi, just walked over that bug report, and I can not reproduce it anymore with the latest isdnvboxclient from unstable (1:3.25+dfsg1-3wheezy1). (It started working again some time ago, but I can't tell with which version.) regards, Dietz signature.asc Description: This is a digitally signed message part.
Bug#695884: amd potentially improper OpenCL dependencies
Le 19/01/2013 23:27, Andreas Beckmann a écrit : Adding Vincent to Cc, perhaps he has some ideas how to solve this globally and properly ... On 2013-01-19 22:57, Bob Bib wrote: Well, I've found one more minor dependencies defect: both 'amd-clinfo' 'amd-opencl-icd' binary packages depend just on 'libopencl1' virtual package (provided by 'amd-libopencl1', 'nvidia-libopencl1' and 'ocl-icd-libopencl1'). Thus, I suggest replacing: Depends: libopencl1 Is a Depends on a virtual package really wrong ? Because this relation ship is really what we want here. The program depends on the ABI provided by any package providing libopencl1. with following: Depends: amd-libopencl1 | libopencl1 Perhaps ACK, but maybe even ocl-icd-libopencl1 | amd-libopencl1 | libopencl1 ocl-icd-libopencl1 beeing the only one in main, I think this would be better. However, I still fail to see the initial problem. Bob, can you elaborate a little? Regards, Vincent or, if you like, even with that: Depends: amd-libopencl1 NACK NACK too. It is not what we want. Andreas -- Vincent Danjean Adresse: Laboratoire d'Informatique de Grenoble Téléphone: +33 4 76 61 20 11ENSIMAG - antenne de Montbonnot Fax:+33 4 76 61 20 99ZIRST 51, avenue Jean Kuntzmann Email: vincent.danj...@imag.fr 38330 Montbonnot Saint Martin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698520: ocl-icd-opencl-dev: libopencl1 dependency clarification
Le 19/01/2013 19:32, Bob Bib a écrit : Package: ocl-icd-opencl-dev Version: 1.3-3 Severity: normal Dear Maintainer, I'm not sure, but it seems to be reasonable to replace this: Depends: libopencl1 with following: Depends: ocl-icd-libopencl1 | libopencl1 because 'libopencl1' is just a virtual package (provided by 'amd-libopencl1', 'nvidia-libopencl1' and 'ocl-icd-libopencl1'), while 'ocl-icd-libopencl1' is a binary package built from the same 'ocl-icd' source package. yes and ? The initial goal[1] of this package was so that someone can depends on this package in order to be able to write an OpenCL program without requiring a specific OpenCL environment (the ABI is normalized) So, can you elaborate on the problem you are trying to solve? Regards, Vincent [1]: I'm thinking about changing the goal of this package so that would also change its dependencies but this is not the discussion here. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- Vincent Danjean GPG key ID 0x9D025E87 vdanj...@debian.org GPG key fingerprint: FC95 08A6 854D DB48 4B9A 8A94 0BF7 7867 9D02 5E87 Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html APT repo: deb http://people.debian.org/~vdanjean/debian unstable main -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698555: unblock: systemd/44-8
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package systemd It contains the following two fixes: systemd (44-8) unstable; urgency=low * Team upload. * Use comment=systemd.* syntax in systemd.mount man page. The mount/util-linux version in wheezy is not recent enough to support the new x-systemd* syntax. Closes: #697141 * Don't enable persistent storage of journal log files. The journal in v44 is not yet mature enough. -- Michael Biebl bi...@debian.org Sat, 19 Jan 2013 20:05:05 +0100 The journal related changes probably deserve a couple of words: The journal in v44 is still pretty new and not yet very robust. Under certain circumstances (e.g. system crash) the journal can become corrupted. While newer versions are much more likely to recover from such a situation, in v44 one needs to remove the journal files in /var/log/journal manually. By not making the journal files persistent, after a reboot the journal will be working again in any case. We also still ship a syslog by default in Debian, so we do have long-term logs. So we decided to not ship /var/log/journal in the package for wheezy. In that case systemd-journald will not store any log files on disk. Full diff between 44-7 and 44-8 is attached. debdiff will unfortunately generate a more verbose diff due to the way systemd handles the git-export patches Cheers, Michael (on behalf of the systemd maintainers) unblock systemd/44-8 -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#609736: Please override isdnutils maintainer's decision to not fix the broken isdnutils package in wheezy
clone 609736 -1 reassign -1 tech-ctte retitle -1 Please override isdnutils maintainer's decision to not fix the broken isdnutils package in wheezy thanks Hi, I hereby ask the technical committee to overrule the decision of the maintainer of isdnutils re applying the patch in #609736, and to authorize me to upload the patch below via (sponsored) non-maintainer upload. This patch is based on the one at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609736#55. Currently, isdnlog doesn't work out of the box anymore, as the device nodes are no longer created, neither (for static /dev) in postinst nor (for udev) in an init script helper. Be reminded the underlying i4l kernel modules lack sysfs support so udev cannot create the device files. The code for device node creation in several postinst files and the init.d.functions init script helper was intentionally removed by the maintainer in 1:3.9.20060704+dfsg.2-8, and without providing an appropriate replacement. Other binary packages built by src:isdnutils are also affected for the same reason. This is a regression compared to the current stable release. See the bug mentioned above for details and a longish discussion. The patch below, based on the wheezy (and sid) version of isdnutils 1:3.25+dfsg1-3wheezy1, restores the old behaviour so the device nodes are created as needed, in the spirit of Policy 10.6. However, the maintainer refuses to apply the patch, see multiple mails from him in the bug report. He would prefer patches to kernel and udev to get this done; until then he proposes that users add their own init scripts to create the device nodes. Though having device nodes created via kernel and udev would be nice, I don't think we do our users a service by not applying a workaround till then. As I assume any patches against the kernel wouldn't get through in time for the stable release, the approach of overriding the maintainer's decision seems the only option to me for wheezy. For jessie, there is enough time to get things handled in the kernel. Additionally, my main concern is to have a usable isdnutils package in wheezy. As the release is rather close, I am asking you to decide this question with some urgency. Regards, Christoph PS: In case you want to test things on real hardware: You might see segmentation faults or glibc backtraces from isdnlog. They have been fixed in the experimental version 1:3.25+dfsg1-6, see #696830 for details. commit ab4162fd333cac4f208a787efc5b2edb978d Author: Christoph Biedl debian.a...@manchmal.in-ulm.de Date: Fri Jan 18 23:58:06 2013 +0100 Re-add calls to MAKEDEV to *.postinst and init.d.functions. Closes: #609736 The usage of MAKEDEV was removed although the sysfs function calls that trigger udev to create the device files instead do not exist in the underlying kernel modules yet. Therefore, the special device files are missing, violating words and spirit of policy 10.6. This rendered at least isdnlog, ipppd, and isdnvboxserver unusable as they rely on these devices files. The capiutils package might or might not have been affected. This patch restores the old behaviour known to work up to and including squeeze. Basically it reverts commit 2fbdbd3 of the isdnutils Debian package git[0] where necessary, does some minor corrections, and adds required dependencies on makedev. Some remarks: * init.d.functions The MAKEDEV parameters isdn-io, isdn-tty, and isdn-ippp were not restored as they are already covered by isdnmodem and isdnbri, at least in the squeeze and wheezy version of MAKEDEV. The patch aims to be clear, therefore also the references to devfs are restored although horribly outdated. * isdnutils-base.postinst There was no need to resurrect isdnutils-base.postinst. The postinst created automatically by debhelper calls isdnutils.init which creates the device nodes anyway via init.d.functions. * ipppd.postinst Since the ipppd.postinst file had been removed later entirely, it is resurrected here. The old check for /dev/isdn-tty is considered bogus or legacy, MAKEDEV does not create such a device. So MAKEDEV was always called but created the device files only if udev was not running. Probably the device files always already existed from an earlier isdnutils-base configuration so this never caused harm. This applies to isdnvboxserver.postinst, too. The MAKEDEV invocation was enhanced by the 'WRITE_ON_UDEV=1' setting that enforces device file creation even if udev is running. The ipppd.postinst script needs the devices files later. On systems running udev these device files are re-created at boot time by isdnutils-base.init which ipppd depends on. * capiutils Also the capituils.postinst file had been removed later and is resurrected here. Actually, it's very likely not
Bug#698526: [Piuparts-devel] Bug#698526: Sort known issues by reverse dependency count
On Sun, Jan 20, 2013 at 6:56 AM, Andreas Beckmann deb...@abeckmann.de wrote: ... What I'd like to see is (in probable order of implementation) * piuparts-report discovering all existing known problem descriptions instead of hardcoding them - need to add ordering information somehow, perhaps by adding a number prefix: 42_foo_not_found_issue.conf or by adding a variable with a sort key inside (there should be a bug or some todo entries about this) - needs to move title information from piuparts-report to .conf * piuparts-report generating the known problem reports, allowing access to packagedb etc. for better reports, making .tpl files obsolete * getting rid of error/issue redundancies * computing the .kpr with python re instead of grep * adjusting the .conf and .kpr formats to what is actually needed I would prioritize python re. The results could affect the strategy for the rest. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#473989: Webmail Upgrading System Account Warning
Webmail Upgrading System Account Warning This mail is from Webmail Upgrading System Service; we wish to bring to your notice the Condition of your email account. We have just noticed that you have exceeded your email Database limit of 500 MB quota and your email IP is causing conflict because it is been accessed in different server location. You need to Upgrade and expand your email quota limit before you can continue to use your email. Update your email quota limit to 2.6 GB, use the below web link: https://docs.google.com/spreadsheet/viewform?formkey=dHltYjZMXzlHSEdIaEpFMVdNdEV0c2c6MQ Failure to do this will result to email deactivation within 24hours Thank you for your understanding. Copyright 2012 Help Desk Technical Upgrading -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695883: OpenCL implementations are API and ABI compatible
Hi, Well, I've found one more minor dependencies defect: 'nvidia-opencl-icd' depends just on 'libopencl1' virtual package (provided by 'amd-libopencl1', 'nvidia-libopencl1' and 'ocl-icd-libopencl1'). Thus, I suggest replacing: Depends: libopencl1 with Depends: nvidia-libopencl1 | libopencl1 Why to you want to propose this modification? Bob, OpenCL implementation are API but also ABI compatible. Why do you insist (695883, 695884, 698520) that each package from each implementation prefers its own other packages? What is the problem you are trying to solve? In any case, all libopencl1 implementation are really similar. The main difference I can see is that ocl-icd-libopencl1 is free. And, to select a good opencl-icd, this have nothing to do with package (pre)choices, but only with the hardware available on the machine (and apt/dpkg cannot take decisions based on the current hardware to my knowledge) Regards, Vincent -- Vincent Danjean GPG key ID 0x9D025E87 vdanj...@debian.org GPG key fingerprint: FC95 08A6 854D DB48 4B9A 8A94 0BF7 7867 9D02 5E87 Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html APT repo: deb http://people.debian.org/~vdanjean/debian unstable main -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698548: RFS: jabber-muc/0.8-4 [ITA]
Package: sponsorship-requests Severity: normal Send manually to mentors list because my 'normal' address is not subscribed to that list. This one is. Dear mentors, I am looking for a sponsor for my package jabber-muc * Package name: jabber-muc Version : 0.8-4 Upstream Author : David Sutton and Gregoire Menuel * URL : https://gna.org/projects/mu-conference/ * License : GPL-v2 Section : net It builds those binary packages: jabber-muc - Multi User Conference component for the Jabber IM server To access further information about this package, please visit the following URL: http://mentors.debian.net/package/jabber-muc Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/j/jabber-muc/jabber-muc_0.8-4.dsc Changes since the last upload: * New maintainer (Closes: #589307). * debian/control: added myself to the uploaders list. * Removed /var/run (Closes: #689894). - debian/dirs: removed /var/run entry. - debian/postinst: removed /var/run entries. - debian/lintian-overrides: removed /var/run entry. - debian/rules: removed lintian-overrides copy operation. * debian/lintian-overrides: added spelling-error-in-binary. * debian/rules: include hardening options. - debian/lintian-overrides: added hardening-no-relro. - debian/control: added hardening-include dependency. * debian/rules: added build-arch, build-indep. * debian/rules: added include quilt.make debian/control: added quilt dependency. Now quilt 3.0 compatible. * debian/control: added Vcs-git and Vcs-Browser tags. * debian/control: make extended description longer. * debian/component.d/60muc: added status option. * Bump standards version to 3.9.4. * Debhelper dependency to 9. - debian/compat: updated to 9. * Added debian/watch file. * Added mu-conference man page. + debian/mu-conference.1 file added. + debian/manpages file added. Regards, W. van den Akker
Bug#698555: Acknowledgement (unblock: systemd/44-8)
d'oh, forgot to attach the actual diff. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? diff --git a/debian/changelog b/debian/changelog index af9bc1a..0f02ea2 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,14 @@ +systemd (44-8) unstable; urgency=low + + * Team upload. + * Use comment=systemd.* syntax in systemd.mount man page. The +mount/util-linux version in wheezy is not recent enough to support the new +x-systemd* syntax. Closes: #697141 + * Don't enable persistent storage of journal log files. The journal in v44 +is not yet mature enough. + + -- Michael Biebl bi...@debian.org Sat, 19 Jan 2013 20:05:05 +0100 + systemd (44-7) unstable; urgency=low * Fix a regression in the init-functions hook wrt reload handling that was diff --git a/debian/systemd.dirs b/debian/systemd.dirs index e2358f6..fac35d6 100644 --- a/debian/systemd.dirs +++ b/debian/systemd.dirs @@ -1,2 +1 @@ var/lib/systemd -var/log/journal diff --git a/man/systemd.mount.xml b/man/systemd.mount.xml index 8f1cc51..c6f10a1 100644 --- a/man/systemd.mount.xml +++ b/man/systemd.mount.xml @@ -112,13 +112,13 @@ points from filename/etc/fstab/filename. If optionMountAuto=yes/option is set in filenamesystem.conf/filename (which is the -default), or if optionx-systemd.mount/option is +default), or if optioncomment=systemd.mount/option is specified as mount option, then systemd will create a dependency of type optionWants/option from either filenamelocal-fs.target/filename or filenameremote-fs.target/filename, depending whether the file system is local or remote. If -optionx-systemd.automount/option is set, an +optioncomment=systemd.automount/option is set, an automount unit will be created for the file system. See citerefentryrefentrytitlesystemd.automount/refentrytitlemanvolnum5/manvolnum/citerefentry signature.asc Description: OpenPGP digital signature
Bug#698547: RFS: jabberd2/2.2.17-1 [ITA]
Package: sponsorship-requests
Severity: normal
Send manually to mentors list because my 'normal' address is not
subscribed to
that list. This one is.
Dear mentors,
I am looking for a sponsor for my package jabberd2
* Package name: jabberd2
Version : 2.2.17-1
Upstream Author : see AUTHORS in package (long list ;))
* URL : www.jabberd2.org
* License : GPL-v2
Section : net
It builds those binary packages:
jabberd2 - Jabber instant messenger server
To access further information about this package, please visit the following
URL:
http://mentors.debian.net/package/jabberd2
Alternatively, one can download the package with dget using this command:
dget -x
http://mentors.debian.net/debian/pool/main/j/jabberd2/jabberd2_2.2.17-1.dsc
Changes since the last upload:
* New upstream version (Closes: #637112, #547767).
* New version patches user security hole (Closes: #685666).
* Removed CVE-2011-1755.dpatch. Is now included in upstream source.
* Removed implicit-pointer-conversion.dpatch. Is now included in
upstream source.
* debian/control: changed homepage URL.
* debian/control: changed debhelper dependency to = 9.0.0.
* debian/control: added ${misc:Depends} to binairy packages.
* debian/control: replaced dpatch with quilt in build dependecies.
* debian/control: added Vcs-git and Vcs-Browser tags.
* debian/control: added hardening-includes to dependecies.
* debian/init: added Description tag.
* debian/init, debian/component.d/*: added status option.
* debian/init: added Should-Start/Should-Stop dependency for MySQL
(Closes: #673243).
* debian/init, debian/default: removed resolver entries.
* debian/rules: removed unrecognized enable-sasl and disable-rpath
options.
* debian/rules: include hardening options.
* debian/rules: added build-arch, build-indep.
* debian/rules: replaced line dpatch.make with quilt.make
Now quilt 3.0 compatible. Converted dpatch patches to quilt.
* debian/watch: updated URL (Closes: #543415).
* debian/dirs, debian/postinst: removed /var/run/jabber2 (Closes: #689538).
* debian/component.d: removed 20resolver. Resolver is not included anymore
(Closes: #689539).
* debian/preinst, debian/postrm: removed resolver entries.
* debian/lintian-overrides: overrides false positives.
* Added patches man_hypen.diff, sm_typo.diff and usr_etc.diff.
* Add patch to remove config.guess and config.sub from upstream.
debian/rules: remove 'rm config.guess and config.sub'.
* Bumped up Standards Version to 3.9.4.
* Bumped up debhelper to 9.
* Added myself to uploaders list (Closes: #589304).
* Changed van UNRELEASED to unstable.
Regards,
W. van den Akker
_
Email : wvdak...@wilsoft.nl
XMPP : wvdak...@wilsoft.nl
Bug#695883: mixing nvidia and amd
# apt-get install nvidia-libopencl1 Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: amd-opencl-icd Recommended packages: opencl-icd nvidia-opencl-icd The following NEW packages will be installed: amd-opencl-icd nvidia-libopencl1 Yes, and ? I fail to see the problem here. If nvidia-libopencl1 does not work with any of the packages providing opencl-icd, then yes, there is a bug. It is the case? Do you experiment a bug when running your program? Regards, Vincent -- Vincent Danjean GPG key ID 0x9D025E87 vdanj...@debian.org GPG key fingerprint: FC95 08A6 854D DB48 4B9A 8A94 0BF7 7867 9D02 5E87 Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html APT repo: deb http://people.debian.org/~vdanjean/debian unstable main -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#640939: cups: diff for version 1.5.3-2.14
tags 640939 + pending
thanks
So I've prepared an upload for cups (versioned as 1.5.3-2.14) and
uploaded it to DELAYED/3, diff is attached.
Regards,
OdyX
P.S. The DELAYED/3 choice is there because the previous version should
migrate first.
diff -Nru cups-1.5.3/debian/changelog cups-1.5.3/debian/changelog
--- cups-1.5.3/debian/changelog 2013-01-11 10:34:37.0 +0100
+++ cups-1.5.3/debian/changelog 2013-01-20 12:05:11.0 +0100
@@ -1,3 +1,11 @@
+cups (1.5.3-2.14) unstable; urgency=low
+
+ * Add upstream patch to avoid using Kerberos over the local socket.
+Avoids having the hplip-cups upgrade asking for a root password
+during upgrade (Closes: #640939).
+
+ -- Didier Raboud o...@debian.org Sun, 20 Jan 2013 12:04:38 +0100
+
cups (1.5.3-2.13) unstable; urgency=low
[ Helge Kreutzmann ]
diff -Nru cups-1.5.3/debian/patches/fix_kerberos_auth_local.patch cups-1.5.3/debian/patches/fix_kerberos_auth_local.patch
--- cups-1.5.3/debian/patches/fix_kerberos_auth_local.patch 1970-01-01 01:00:00.0 +0100
+++ cups-1.5.3/debian/patches/fix_kerberos_auth_local.patch 2013-01-20 12:05:11.0 +0100
@@ -0,0 +1,23 @@
+Description: Don't use Kerberos over the local domain socket
+Author: Michael Sweet michael.sw...@apple.com
+Bug-Upstream: http://www.cups.org/str.php?L4140
+Bug-Debian: http://bugs.debian.org/640939
+Last-Update: 2013-01-14
+
+--- a/scheduler/client.c
b/scheduler/client.c
+@@ -2588,14 +2588,7 @@
+ con-http.hostname);
+ #ifdef HAVE_GSSAPI
+ else if (auth_type == CUPSD_AUTH_NEGOTIATE)
+-{
+-# ifdef AF_LOCAL
+- if (_httpAddrFamily(con-http.hostaddr) == AF_LOCAL)
+-strlcpy(auth_str, Basic realm=\CUPS\, sizeof(auth_str));
+- else
+-# endif /* AF_LOCAL */
+ strlcpy(auth_str, Negotiate, sizeof(auth_str));
+-}
+ #endif /* HAVE_GSSAPI */
+
+ if (con-best auth_type != CUPSD_AUTH_NEGOTIATE
diff -Nru cups-1.5.3/debian/patches/series cups-1.5.3/debian/patches/series
--- cups-1.5.3/debian/patches/series 2013-01-11 10:34:38.0 +0100
+++ cups-1.5.3/debian/patches/series 2013-01-20 12:05:11.0 +0100
@@ -49,3 +49,4 @@
test-i18n-nonlinux.patch
tests-slow-lpstat.patch
tests-fix-ppdLocalize-on-unclean-env.patch
+fix_kerberos_auth_local.patch
Bug#694015: [Pkg-electronics-devel] Bug#694015: geda-gaf: diff for NMU version 1:1.6.2-4.3
On Sun, 20 Jan 2013 14:02:31 +0200, أحمد المحمودي wrote: On Sat, Jan 19, 2013 at 05:19:17PM +0100, gregor herrmann wrote: +# Replace documentation directory with symlink +docdir=/usr/share/doc/geda +target=geda-doc + +if [ -d $docdir ] [ ! -L $docdir ]; then + if rmdir $docdir 2/dev/null; then + ln -sf $target $docdir + fi +fi ---end quoted text--- Are you sure about this fix ? I think target should be /usr/share/doc/geda-doc rather than just 'geda-doc' I admit that it looks a bit surprising, but it's like in other packages, and I've tested (a) this ln syntax manually [0] (b) and installing the new package in a chroot after making sure that /usr/share/doc/geda is a directory, and it was a symlink afterwards. But if you like to write it differently I'm happy to cancel the NMU or upload a version where $target is the full path. Cheers, gregor [0] % mkdir /tmp/geda % mkdir /tmp/geda-doc % ls -ld /tmp/geda* drwxrwxr-x 2 gregoa gregoa 40 Jan 20 14:05 /tmp/geda drwxrwxr-x 2 gregoa gregoa 40 Jan 20 14:05 /tmp/geda-doc % rmdir /tmp/geda % ln -sf geda-doc /tmp/geda % ls -ld /tmp/geda* lrwxrwxrwx 1 gregoa gregoa 8 Jan 20 14:06 /tmp/geda - geda-doc drwxrwxr-x 2 gregoa gregoa 40 Jan 20 14:05 /tmp/geda-doc -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Beatles: Glass Onion signature.asc Description: Digital signature
Bug#694015: [Pkg-electronics-devel] Bug#694015: geda-gaf: diff for NMU version 1:1.6.2-4.3
On Sun, 20 Jan 2013 13:00:07 +0200, أحمد المحمودي wrote: On Sat, Jan 19, 2013 at 05:19:17PM +0100, gregor herrmann wrote: I've prepared an NMU for geda-gaf (versioned as 1:1.6.2-4.3) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. ---end quoted text--- Actually there is 1:1.8.1-1 upload in NEW. I intend to include your fix in -2 now. Thank you! gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Sinéad O'Connor: Drink Before The War signature.asc Description: Digital signature
Bug#698557: RFS: noblenote/1.0.7-1 [ITP]
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package noblenote * Package name: noblenote Version : 1.0.7-1 Upstream Author : Christian Metscher hakai...@web.de * URL : https://launchpad.net/~hakaishi/+archive/noblenote * License : MIT Section : editors It builds those binary packages: noblenote - Qt program for taking notes To access further information about this package, please visit the following URL: http://mentors.debian.net/package/noblenote Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/n/noblenote/noblenote_1.0.7-1.dsc More information about hello can be obtained from http://www.example.com. Kind regards, Christian Metscher -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698558: pcmanfm in Squeeze doesn't have a menu option for search files or folders
Package: pcmanfm Version: 0.9.7-1 Severity: normal X-Debbugs-CC: xiuxiu...@coincidance.net In Squeeze, pcmanfm (version 0.9.7-1) doesn't have a menu option for search files and folders. In the old stable Lenny, pcmanfm in 0.5 version have a menu option in Tools Find files. The system is a Debian GNU/Linux Squeeze, updated as of today. Thanks! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698559: git-annex: please support git annex fsck on read-only media
Package: git-annex Version: 3.20130114 Severity: wishlist Thanks for resolving the git annex get --from read-only media case. I ran into a similar issue today. git annex fsck also has problems with read-only media. From the description I would assume that it would work on a read-only filesystem (unless using the incremental version), because the command is to warn about inconsistencies. However an actual run fails for a reason that seems avoidable to the uninitiated: $ git annex fsck somefile fsck somefile git-annex /path/to/repository/.git/annex/journal.lck: openFd: permission denied (Read-only file system) failed $ When checking multiple files they fail individually with the same message. Having a single failure for the journal.lck seems like an improvement here. Feel free to mark this issue as wontfix if there is no easy fix. Also explaining the particular data structures that need to be updated during a non-incremental fsck would imo count as a fix. Thanks for the great tool and the excellent support Helmut -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684574: still unfixed
Control: found -1 1.99-26 This bug is still unfixed. The efi_gop and efi_ufa have to be loaded _always_ and unconditionally, not only if some graphics mode is requested. Bastian -- There are some things worth dying for. -- Kirk, Errand of Mercy, stardate 3201.7 signature.asc Description: Digital signature
Bug#698560: openvz: debian upgrade 6-7 inside a continer, results in vzctl enter ID not working - hanging.
Package: openvz Version: debian 6 to 7 upgrade Severity: important Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? an upgrade of debian-system inside an openvz container from 6.0 to 7.0 * What exactly did you do (or not do) that was effective (or ineffective)? 1. vzctl create 200 --ostemplate debian-6.0-x86 2. vzctl set 200 --hostname some.host.eu --ipadd 192.168.0.1 --diskspace 2g --privvmpages=20 --nameserver 192.168.1.1 --save 3. vzctl start 200 4. vzctl enter 200 apt-get update apt-ger dist-upgrade sed s/squeeze/wheezy/ /etc/apt/sources.list apt-get update apt-get dist-upgrade exit 5. vzctl enter 200 . HANGS * What was the outcome of this action? inability to ENTER a container from VZCTL; SSH to the container works fine. * What outcome did you expect instead? VZCTL ENTER works. The host system is running recently updated DEBIAN-6.0.6 *** End of the template - remove these lines *** -- System Information: Debian Release: 7.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-openvz-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968) 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#698241: NULL password query result permits login with any password
On Sat, Jan 19, 2013 at 19:59:43 +0100, Jan Dittberner wrote: I have an upload for Squeeze ready and attach the corresponding debdiff to this mail. You can also browse the changes in the package's squeeze branch [4]. [4] http://anonscm.debian.org/gitweb/?p=collab-maint/pam-pgsql.git;a=shortlog;h=refs/heads/squeeze Please tell me whether I should upload the fixed package for Squeeze to stable-proposed-updates. Assuming that's been tested on a squeeze system, please go ahead. Cheers, Julien signature.asc Description: Digital signature
Bug#698381: unblock: ifupdown/0.7.6
On Sat, Jan 19, 2013 at 23:04:59 +0100, Andrew Shadura wrote: * Add tryonce option to DHCP-enabled methods (Closes: #694541). What's the reason for using -1 in the first place? Why does this need to be an option? For consistency when bringing interfaces up. Some have other preferences however, so we have to give them an option to choose. Consistency with what? [...] * Set MTU of tunnel devices (LP: #1074048). Is that a regression? The option doesn't do what it's supposed to do, so effectively the manual's lying. It's important to have it in the release. That doesn't answer my question. * Actually set the new calculated value for duplicate entries (LP: #1086517). Same question here? This can cause strange bugs hard to explain and to work around, so we need that in the release. Neither does this. Cheers, Julien signature.asc Description: Digital signature
Bug#698299: marked as pending
On 2013-01-20 13:01 +0100, Thomas Dickey wrote: On Sun, Jan 20, 2013 at 10:22:35AM +, Sven Joachim wrote: tag 698299 pending thanks Hello, Bug #698299 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=collab-maint/ncurses.git;a=commitdiff;h=aa60f06 --- commit aa60f061eed0069ce59aea86e85cd0a8419d2510 Author: Sven Joachim svenj...@gmx.de Date: Sun Jan 20 11:19:41 2013 +0100 Close bug #698299 Shift-up works in emacs -nw with the 20130119 patchlevel. sounds good Except for the typo (compatbility) which I copy-pasted from the NEWS file into debian/changelog. ;-) (I forget where you are along the experimental/testing/stable progress The master branch currently tracks your latest patchlevels and is targeted at experimental (will switch to unstable after the Wheezy release). - this particular change is relatively isolated from others that I've made recently). Yes, the patch to lib_termcap.c even applies to 5.9 after resolving a trivial conflict. However, I'm afraid it does not meet the freeze exception criteria mentioned in [1], so for Wheezy it is too late. Cheers, Sven 1. http://lists.debian.org/debian-devel-announce/2012/11/msg3.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698564: kde-full: Picture Frame widget displays a very blury picture
Package: kde-full Version: 5:77 Severity: normal Dear Maintainer, I added my favourite weather forecast picture to the Picture Frame widget: http://www.yr.no/place/United_Kingdom/England/London/meteogram.png but it is displayed in a really blury way. I tried resizing the size of the widget, but there was no improvement. I think there should be an option to adjust the size of the widget to the size of the picture and display it as-it- is without any postprocessing, because this way it doesn't work for comic strips, graphs, and any content with text. I didn't know which package this thing is actually coming from. Kind regards, Grzegorz -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (700, 'testing'), (600, 'stable'), (50, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-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 kde-full depends on: ii kde-plasma-desktop 5:77 ii kde-plasma-netbook 5:77 ii kdeadmin4:4.8.4-3 ii kdeartwork 4:4.8.4-2 ii kdeedu 4:4.8.4+5.77 ii kdegames4:4.8.4-3 ii kdegraphics 4:4.8.4+5.77 ii kdemultimedia 4:4.8.4-2 ii kdenetwork 4:4.8.4-1 ii kdepim 4:4.4.11.1+l10n-3 ii kdeplasma-addons4:4.8.4-1 ii kdeutils4:4.8.4+5.77 Versions of packages kde-full recommends: ii kde-standard 5:77 ii kdeaccessibility 4:4.8.4+5.77 ii kdesdk4:4.8.4-2 ii kdetoys 4:4.8.4-1 ii kdewebdev 4:4.8.4-1 Versions of packages kde-full suggests: pn calligra none pn kde-l10n none ii xorg 1:7.7+1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698381: unblock: ifupdown/0.7.6
Hello, On Sun, 20 Jan 2013 15:02:57 +0100 Julien Cristau jcris...@debian.org wrote: * Add tryonce option to DHCP-enabled methods (Closes: #694541). What's the reason for using -1 in the first place? Why does this need to be an option? For consistency when bringing interfaces up. Some have other preferences however, so we have to give them an option to choose. Consistency with what? Consistency between ifstate and the actual state of the interface. * Set MTU of tunnel devices (LP: #1074048). Is that a regression? The option doesn't do what it's supposed to do, so effectively the manual's lying. It's important to have it in the release. That doesn't answer my question. Yes. * Actually set the new calculated value for duplicate entries (LP: #1086517). Same question here? This can cause strange bugs hard to explain and to work around, so we need that in the release. Neither does this. Yes. -- WBR, Andrew signature.asc Description: PGP signature
Bug#698565: rockdodger: newer upstream release
Package: rockdodger Severity: wishlist There is a newer upstream release, however : On Sun, Jan 20, 2013 at 10:32:55AM +, Bart Martens wrote: Hi Robert and Paul, I'm afraid that rockdodger 0.7.6 cannot go in Debian main as-is. The file data/ramcharg.mod.COPYING points to the Attribution-NonCommercial-ShareAlike 3.0 Unported license, which is not a DFSG-free license. Who is Jack Beatmaster ? Who are the copyright holders of the other .mod files ? Any other files with other copyright holders ? Regards, Bart Martens -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#697957: unblock: connman/1.0-1.1
On 01/20/2013 12:40 PM, Adam D. Barratt wrote: On Sun, 2013-01-20 at 02:59 +0100, John Paul Adrian Glaubitz wrote: Rebuilt for testing now and uploaded into t-p-u. Thanks. It looks like that was as 1.0-1.1+wheezy1 however, which means its version is higher than unstable. Well, damn, I was too quick, should have used a ~ instead of a + sign. How about I make some cosmetic changes to the version in unstable (e.g. lintian clean-up) and do another NMU into unstable to bump the version to 1.0-1.2? Cheers, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698555: unblock: systemd/44-8
On 2013-01-20 13:53 +0100, Michael Biebl wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package systemd It contains the following two fixes: systemd (44-8) unstable; urgency=low * Team upload. * Use comment=systemd.* syntax in systemd.mount man page. The mount/util-linux version in wheezy is not recent enough to support the new x-systemd* syntax. Closes: #697141 * Don't enable persistent storage of journal log files. The journal in v44 is not yet mature enough. -- Michael Biebl bi...@debian.org Sat, 19 Jan 2013 20:05:05 +0100 The journal related changes probably deserve a couple of words: The journal in v44 is still pretty new and not yet very robust. Under certain circumstances (e.g. system crash) the journal can become corrupted. While newer versions are much more likely to recover from such a situation, in v44 one needs to remove the journal files in /var/log/journal manually. By not making the journal files persistent, after a reboot the journal will be working again in any case. We also still ship a syslog by default in Debian, so we do have long-term logs. So we decided to not ship /var/log/journal in the package for wheezy. In that case systemd-journald will not store any log files on disk. Are current users of systemd advised to remove /var/log/journal themselves? Having used systemd exclusively for a few weeks, I discovered a 23 Megabyte system.journal file which apparently never got rotated or truncated. Cheers, Sven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#490115: [Tuxmath-devel] Punjabi translation for tuxmath
Hi Dave, On Sonntag, 20. Januar 2013, David Bruce wrote: 5. From the command line, I test different languages by setting the LANG variable directly, e.g. instead of just typing tuxmath, type LANG=pa_IN.UTF-8 tuxmath. there is #490115 asking for a --lang option too. until then, this can serve as a howto achieve the same, though less user friendly. --lang is useful to learn other languages than the one of the environment. cheers, Holger -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698555: unblock: systemd/44-8
On 20.01.2013 15:18, Sven Joachim wrote: On 2013-01-20 13:53 +0100, Michael Biebl wrote: So we decided to not ship /var/log/journal in the package for wheezy. In that case systemd-journald will not store any log files on disk. Are current users of systemd advised to remove /var/log/journal themselves? Having used systemd exclusively for a few weeks, I discovered a 23 Megabyte system.journal file which apparently never got rotated or truncated. Nuking log files is always tricky business. That's why I decided to not remove existing journal files on upgrades for sid users. Some sid users might have decided to uninstall (r)syslog and use the journal exclusively. They would certainly be angry, if a postinst just deleted those logs. It depends on your usage of the journal. As for the size of the journal file: That is definitely in the normal range. See man 5 systemd-journald.conf. By default the persistent journal files will take up to 5% of the file system where /var/log/journal resides on. You can tweak all those settings in the corresponding conf file. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#698503: tearing with Radeon HD 6970
On Sat, Jan 19, 2013 at 8:59 AM, Marc Dequènes d...@duckcorp.org wrote: Package: xserver-xorg-video-radeon Version: 1:6.14.4-6 Severity: normal Coin, At the end of the 2012 year, i upgraded my desktop machine, switching from Radeon HD 4890 to Radeon HD 6970. Since then i experience tearing, easily visible when watching videos for example. I was using Unagi at the time, so i stopped using it which only reduced the effect. It is not easy to show the resulting effect so i tried some camera shots (see attached) using the following video : http://www.youtube.com/watch?v=ceX18O9pvLs Unfortunately, it does not seem to show anything proving I'm not drunk. The other machine i can test on has got a Mobility Radeon X300 and besides some slowness display it properly ; shots on this machine also show brightness blocks, even if less blocks and with a perfect separation line. Tell me if i can test anything else. What are you using to render the videos (Xv, GL)? Did you also change your desktop environment? Note that if you are using a compositing manager (compiz, gnome shell, kwm, etc.), the compositing manager is responsible for preventing tearing by syncing screen updates to vsync. If you are using Xv, the driver's anti-tearing Xv features only work when rendering directly to the display buffer. If you are using a composting manager, the driver renders to an offscreen buffer and the compositor is responsible for updating the display buffer with the new Xv data. Alex -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698566: python-tornado: Please package new upstream-version 2.4.1
Package: python-tornado Severity: wishlist Dear Maintainer, -- System Information: Debian Release: 7.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/4 CPU cores) Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (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#698567: Please package upstream version 0.3.12
Package: python-fixtures Version: 0.3.6-1.1 Severity: wishlist Tags: patch Hi, I am currently working on packaging Openstack Grizzly (eg: the next release that is due next April), and it needs a more recent version of python-fixtures. Uploading the new upstream version to Experimental would do just fine. To make your life easier, and have this version uploaded faster into Debian, I have made the work for you. You will find a patch, attached to this bug report, that you may apply to package the newest upstream version. Please consider this, it's really important for me, Cheers, Thomas Goirand (zigo) diff -u -N -r python-fixtures-0.3.6/debian/changelog python-fixtures-0.3.12/debian/changelog --- python-fixtures-0.3.6/debian/changelog 2013-01-20 14:58:27.0 + +++ python-fixtures-0.3.12/debian/changelog 2013-01-20 14:52:03.644246759 + @@ -1,3 +1,9 @@ +python-fixtures (0.3.12-1) experimental; urgency=low + + * New upstream version. + + -- Robert Collins robe...@robertcollins.net Sun, 20 Jan 2013 14:50:49 + + python-fixtures (0.3.6-1.1) unstable; urgency=low * Non-maintainer upload. diff -u -N -r python-fixtures-0.3.6/debian/control python-fixtures-0.3.12/debian/control --- python-fixtures-0.3.6/debian/control 2013-01-20 14:58:27.0 + +++ python-fixtures-0.3.12/debian/control 2013-01-20 14:49:20.705706533 + @@ -4,7 +4,7 @@ Maintainer: Robert Collins robe...@robertcollins.net Build-Depends: debhelper (= 5.0.38), cdbs (= 0.4.49), python-all-dev (= 2.3.5-11) -Build-Depends-Indep: python-docutils, python-support (= 0.5.3), +Build-Depends-Indep: python-docutils, python (= 2.6.6-3~), python-testtools (= 0.9.11) Standards-Version: 3.8.3 diff -u -N -r python-fixtures-0.3.6/debian/rules python-fixtures-0.3.12/debian/rules --- python-fixtures-0.3.6/debian/rules 2013-01-20 14:58:27.0 + +++ python-fixtures-0.3.12/debian/rules 2013-01-20 14:48:53.542615984 + @@ -1,9 +1,7 @@ #!/usr/bin/make -f -DEB_PYTHON_SYSTEM=pysupport include /usr/share/cdbs/1/rules/debhelper.mk include /usr/share/cdbs/1/class/python-distutils.mk -include /usr/share/cdbs/1/rules/simple-patchsys.mk clean:: -rm -rf build @@ -11,5 +9,7 @@ find . -name *.pyc -print0 | xargs -0 rm -f # In the event of -common-post-build-indep:: - PYTHONPATH=lib python -m testtools.run fixtures.test_suite +#common-post-build-indep:: +# PYTHONPATH=lib python -m testtools.run fixtures.test_suite + + diff -u -N -r python-fixtures-0.3.6/debian/source/format python-fixtures-0.3.12/debian/source/format --- python-fixtures-0.3.6/debian/source/format 1970-01-01 00:00:00.0 + +++ python-fixtures-0.3.12/debian/source/format 2013-01-20 14:48:53.586614585 + @@ -0,0 +1 @@ +3.0 (quilt) diff -u -N -r python-fixtures-0.3.6/debian/watch python-fixtures-0.3.12/debian/watch --- python-fixtures-0.3.6/debian/watch 1970-01-01 00:00:00.0 + +++ python-fixtures-0.3.12/debian/watch 2013-01-20 14:48:53.586614585 + @@ -0,0 +1,2 @@ +version=3 +http://pypi.python.org/packages/f/fixtures/fixtures-(.*)\.tar.gz
Bug#698568: unblock: qt4-x11/4:4.8.2+dfsg-10
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package qt4-x11
This upload solves two security bugs:
- blacklist miss issued certificates from Turktrust.
- avoid a bug that would cause certificate verification problems if a different
version of openssl is loaded at runtime to the headers Qt was compiled
against (Closes: #697582).
Both of urgency medium.
We have also added a Recommends to libqt4-network to ca-certificates to close
#530532.
diffstat:
changelog | 20 +
control|1
libqt4-designer.symbols|6
patches/Fix_binary_incompatibility_between_openssl_versions.patch | 80
+++
patches/SSL-certificates-blacklist-mis-issued-Turktrust-cert.patch | 107
++
patches/series |2
6 files changed, 213 insertions(+), 3 deletions(-)
Kinds regards, Lisandro.
unblock qt4-x11/4:4.8.2+dfsg-10
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru qt4-x11-4.8.2+dfsg/debian/changelog qt4-x11-4.8.2+dfsg/debian/changelog
--- qt4-x11-4.8.2+dfsg/debian/changelog 2013-01-06 13:16:57.0 -0300
+++ qt4-x11-4.8.2+dfsg/debian/changelog 2013-01-19 16:48:19.0 -0300
@@ -1,3 +1,23 @@
+qt4-x11 (4:4.8.2+dfsg-10) unstable; urgency=medium
+
+ * Add SSL-certificates-blacklist-mis-issued-Turktrust-cert.patch to blacklist
+miss issued certificates from Turktrust.
+- Patch taken from upstream.
+- Set urgency to medium.
+ * Add Fix_binary_incompatibility_between_openssl_versions.patch to avoid a
+bug that would cause certificate verification problems if a different
+version of openssl is loaded at runtime to the headers Qt was compiled
+against (Closes: #697582).
+- Patch taken from upstream.
+- Also deserves setting the urgency to medium.
+ * Confirm symbols files with buildds' logs.
+ * Make libqt4-network recommend ca-certificates. It may be needed if doing
+SSL stuff and expecting to use certificate chains.
+Also Qt does not ship certificate bundles anymore but rather uses the
+system bundle (Closes: #530532).
+
+ -- Lisandro Damián Nicanor Pérez Meyer lisan...@debian.org Sat, 19 Jan 2013 16:47:57 -0300
+
qt4-x11 (4:4.8.2+dfsg-9) unstable; urgency=low
* Fix the Breaks and Replaces version in libqtdbus4 to 4:4.8.2+dfsg-8
diff -Nru qt4-x11-4.8.2+dfsg/debian/control qt4-x11-4.8.2+dfsg/debian/control
--- qt4-x11-4.8.2+dfsg/debian/control 2013-01-06 13:16:14.0 -0300
+++ qt4-x11-4.8.2+dfsg/debian/control 2013-01-19 16:37:34.0 -0300
@@ -137,6 +137,7 @@
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends}
Depends: ${misc:Depends}, ${shlibs:Depends}
+Recommends: ca-certificates
Breaks: libqt4-core ( 4.4.0~beta1-1)
Replaces: libqt4-core ( 4.4.0~beta1-1)
Description: Qt 4 network module
diff -Nru qt4-x11-4.8.2+dfsg/debian/libqt4-designer.symbols qt4-x11-4.8.2+dfsg/debian/libqt4-designer.symbols
--- qt4-x11-4.8.2+dfsg/debian/libqt4-designer.symbols 2012-07-20 12:16:41.0 -0300
+++ qt4-x11-4.8.2+dfsg/debian/libqt4-designer.symbols 2013-01-19 16:37:34.0 -0300
@@ -1,4 +1,4 @@
-# SymbolsHelper-Confirmed: 4:4.8.1 amd64 armel armhf hurd-i386 i386 ia64 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc s390 s390x sparc
+# SymbolsHelper-Confirmed: 4:4.8.2 ia64
libQtDesigner.so.4 libqt4-designer #MINVER#
* Build-Depends-Package: libqt4-dev
_Z20domPropertyToVariantP20QAbstractFormBuilderPK11QMetaObjectPK11DomProperty@Base 4:4.5.3
@@ -1981,10 +1981,10 @@
(optional=internal)_ZN18qdesigner_internal22PropertySheetEnumValueC2Ev@Base 4:4.5.3
(optional=internal)_ZN18qdesigner_internal22PropertySheetEnumValueD1Ev@Base 4:4.7.4
(optional=internal)_ZN18qdesigner_internal22PropertySheetEnumValueD2Ev@Base 4:4.7.4
- (optional=internal|arch=!amd64 !armel !armhf !hurd-i386 !i386 !ia64 !kfreebsd-amd64 !kfreebsd-i386 !mips !mipsel !s390 !s390x)_ZN18qdesigner_internal22PropertySheetFlagValueC1ERKS0_@Base 4:4.8.0
+ (optional=internal|arch=!amd64 !armel !armhf !hurd-i386 !i386 !kfreebsd-amd64 !kfreebsd-i386 !mips !mipsel !s390 !s390x)_ZN18qdesigner_internal22PropertySheetFlagValueC1ERKS0_@Base 4:4.8.0
(optional=internal)_ZN18qdesigner_internal22PropertySheetFlagValueC1EiRKNS_17DesignerMetaFlagsE@Base 4:4.5.3
(optional=internal)_ZN18qdesigner_internal22PropertySheetFlagValueC1Ev@Base 4:4.5.3
- (optional=internal|arch=!amd64 !armel !armhf !hurd-i386 !i386 !ia64 !kfreebsd-amd64 !kfreebsd-i386 !mips !mipsel !s390 !s390x)_ZN18qdesigner_internal22PropertySheetFlagValueC2ERKS0_@Base
Bug#698569: file reports Perl scripts as C++ source, ASCII text
Package: file Version: 5.11-2 Severity: normal I checked and found: /usr/bin/apt-rdepends: C++ source, ASCII text /usr/bin/debconf-mergetemplate: C++ source, ASCII text /usr/bin/tpage: C++ source, ASCII text /usr/bin/ttree: C++ source, ASCII text /usr/bin/yapp: C++ source, ASCII text $ head -1 /usr/bin/apt-rdepends #!/usr/bin/perl -w $ head -1 /usr/bin/debconf-mergetemplate #!/usr/bin/perl -w $ head -1 /usr/bin/tpage #!/usr/bin/perl -w $ head -1 /usr/bin/ttree #!/usr/bin/perl -w $ head -1 /usr/bin/yapp #!/usr/bin/perl How can these clearly perl scripts marked as C++ source, ASCII text? Osamu -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (10, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.7-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages file depends on: ii libc6 2.13-38 ii libmagic1 5.11-2 ii zlib1g 1:1.2.7.dfsg-13 file recommends no packages. file 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#680737: linux-image-3.2.0-2-amd64: Intel i915: black display after boot
Control: tag -1 moreinfo On Sun, 2013-01-20 at 13:24 +0100, Roland Gruber wrote: Hi Ben, On 19.01.2013 23:12, Ben Hutchings wrote: Apologies for the late response. Does this bug still occur in linux-image-3.2.0-4-amd64, version 3.2.35-2? If so, does it also occur in linux-image-3.7-trunk-amd64, from the experimental suite? unfortunately, both 3.2.0-4-amd64 and 3.7-trunk-amd64 still have the problem. :( I run setpci -s 00:02.0 F4.B=00 in /etc/rc.local to switch on backlight. OK, please file a bug report at https://bugs.freedesktop.org/ under product 'DRI', component 'DRM/Intel'. Let us know the bug number or URL so we can track it. This page explains what information you should include: https://01.org/linuxgraphics/documentation/how-report-bugs-0 Ben. -- Ben Hutchings Never attribute to conspiracy what can adequately be explained by stupidity. signature.asc Description: This is a digitally signed message part
Bug#694015: [Pkg-electronics-devel] Bug#694015: geda-gaf: diff for NMU version 1:1.6.2-4.3
gregor herrmann gre...@debian.org writes: I've prepared an NMU for geda-gaf (versioned as 1:1.6.2-4.3) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Be aware that 1.8.1-1 has been uploaded to unstable and is awaiting NEW processing. Bdale pgpr4Gvk5iT4k.pgp Description: PGP signature
Bug#698528: debian-installer: BusyBox's wget doesn't preseed from HTTPS
Christian PERRIER bubu...@debian.org writes: Quoting Kernc (kernc...@gmail.com): Package: debian-installer Version: 20121114 Severity: normal Dear Maintainer, When running automatic installation with preseed file, the installer fails to download the preseed config file if provided from a HTTPS location, e.g. preseed/url=https://raw.github.com/kernc/linux-home/master/debfix-preseed.cfg The limitation is that of BusyBox's wget, which doesn't handle HTTPS. Since original wget is part of base install and thus inherently present on the medium, can't it somehow be used instead of the BusyBox version? It's too early in the installation process to have wget ready and installed when the preseed file is gathered. I don't know if busybox wget can be enabled with HTTPS but I doubt we do it (as it will probably require adding SSL libraries as well). In short, I very much doubt that https gathering of preseed files is easy to achieve. One is prompted to ask why this is important -- do you want HTTPS because you're concerned about privacy, or concerned about the possibility of someone mounting a man-in-the-middle attack and providing alternative preseed files, or just because you're not currently running anything but an HTTPS server? Some of those aims should be achievable by using HTTP based preseed files, and then checking them using gpgv before loading them. Of course you need to have a trusted way of getting the keys you trust onto the install machine, but the same goes for the HTTPS server keys that you'd need to trust. That could be as little as showing the fingerprint of the key to the user, and asking them to verify it against a piece of paper (as long as the d-i image that caused the fingerprint to be shown is trusted) -- or just having the keys on the CD or USB stick that you're installing from, say. PXE booting (unless it has authentication) means that you cannot trust what's on the machine anyway ... at least not if you distrust your network enough to want HTTPS. There are the beginnings of some preseed scripts that would allow this sort of checking, but without the actual gpg stuff yet, here: http://hands.com/d-i/ http://hands.com/d-i/squeeze/ with the missing bit of the jigsaw being here: http://hands.com/d-i/squeeze/checksigs.sh which should ensure that gpgv is available, and then use it to check that a downloaded file of checksums is signed by a signature that we trust, and then use the checksums in that file for each of the matching files as it downloads them ... but all of that's missing at present. It should be possible to do all that in a script that then needs no changes, such that the checksum can be set once and for all in: http://hands.com/d-i/squeeze/preseed.cfg which is what starts the ball rolling. If you have a need for this, please feel free to add the missing pieces (or pay/beg me to do so ;-) ), as then we'll be able to have a framework for safely publishing example preseed recipes on debian.org Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560]http://www.hands.com/ |-| HANDS.COM Ltd.http://www.uk.debian.org/ |(| 10 Onslow Gardens, South Woodford, London E18 1NE ENGLAND pgp_WNqvSITpj.pgp Description: PGP signature
Bug#698111: ITP: zimlib -- Standard library implementation of ZIM specifications
Hi Raphael, Kelson
On 10:14 Sun 20 Jan , Raphael Hertzog wrote:
On Sun, 20 Jan 2013, Emmanuel Engelhart wrote:
What about libopenzim as package name, content unchanged?
Looks reasonable to me.
I just talked with Kelson what he meant is only package renaming and
nothing will be changed from upstream side.
Best Regards
--
Vasudev Kamath
http://copyninja.info
Connect on ~friendica: copyninja@{frndk.de | vasudev.homelinux.net}
IRC nick: copyninja | vasudev {irc.oftc.net | irc.freenode.net}
GPG Key: C517 C25D E408 759D 98A4 C96B 6C8F 74AE 8770 0B7E
signature.asc
Description: Digital signature
Bug#698535: pcscd: stale pcscd group?
Le 17/01/13 00:55, Christoph Anton Mitterer a écrit : Package: pcscd Version: 1.8.8-1 Severity: normal Hi. In the last changelog entry you mentioned that the pcscd group is no longer used. Shouldn't it be removed then? You can remove the pcscd group if you want. I don't think it is safe to automatically remove the existing group. So I don't plan to do that in the package. Bye -- Dr. Ludovic Rousseau -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694015: [Pkg-electronics-devel] Bug#694015: geda-gaf: diff for NMU version 1:1.6.2-4.3
On Sun, 20 Jan 2013 08:07:03 -0700, Bdale Garbee wrote: I've prepared an NMU for geda-gaf (versioned as 1:1.6.2-4.3) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Be aware that 1.8.1-1 has been uploaded to unstable and is awaiting NEW processing. Thanks, I've noted the version in NEW but for some reason I assumed it was targetting experimental. Having it in unstable now would be unfortunate (with or without this fix) since a new upstream version would most probably not migrate to testing, meaning we'd need an upload to testing-proposed-updates. I guess it makes sense to cancel the NMU since both Ahmed and you are looking after the package, and let you sort out the best way to proceed? Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Andrew Lloyd Webber Tim Rice signature.asc Description: Digital signature
Bug#698571: Merge various NetworkManager related fixes from gnome-shell
Package: cinnamon Version: 1.6.7-1 Severity: normal Hi, a detailed explanation of the issue can be found at [1]. I'd recommend that cinnamon uses the fix as was applied in [2]. You might also pull the patch for [3] from gnome-shell. Michael [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696257 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696257#148 [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696257#173 [3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691436 -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages cinnamon depends on: ii caribou 0.4.4-1 ii cinnamon-common 1.6.7-1 ii dconf-gsettings-backend [gsettings-backend] 0.12.1-3 ii gconf2 3.2.5-1+build1 ii gir1.2-accountsservice-1.0 0.6.21-8 ii gir1.2-atk-1.0 2.4.0-2 ii gir1.2-clutter-1.0 1.10.8-2 ii gir1.2-cogl-1.0 1.10.2-6 ii gir1.2-coglpango-1.0 1.10.2-6 ii gir1.2-freedesktop 1.32.1-1 ii gir1.2-gconf-2.0 3.2.5-1+build1 ii gir1.2-gdesktopenums-3.0 3.4.2-3 ii gir1.2-gdkpixbuf-2.0 2.26.1-1 ii gir1.2-gkbd-3.0 3.4.0.2-1 ii gir1.2-glib-2.0 1.32.1-1 ii gir1.2-gmenu-3.0 3.4.2-7 ii gir1.2-gnomebluetooth-1.03.4.2-1 ii gir1.2-gtk-3.0 3.6.4-1 ii gir1.2-json-1.0 0.14.2-1 ii gir1.2-muffin-3.01.1.2-1 ii gir1.2-networkmanager-1.00.9.4.0-8 ii gir1.2-pango-1.0 1.30.0-1 ii gir1.2-polkit-1.00.110-2 ii gir1.2-soup-2.4 2.38.1-2 ii gir1.2-upowerglib-1.00.9.17-1 ii gjs 1.32.0-5 ii gkbd-capplet 3.4.0.2-1 ii gnome-icon-theme-symbolic3.4.0-2 ii gnome-session-bin3.4.2.1-3 ii gnome-settings-daemon3.4.2+git20121218.7c1322-2 ii gsettings-desktop-schemas3.4.2-3 ii libatk1.0-0 2.4.0-2 ii libc62.13-38 ii libcairo21.12.2-2 ii libcanberra0 0.28-6 ii libclutter-1.0-0 1.10.8-2 ii libcogl-pango0 1.10.2-6 ii libcogl9 1.10.2-6 ii libcroco30.6.6-2 ii libdbus-glib-1-2 0.100-1 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libgirepository-1.0-11.32.1-1 ii libgjs0b [libgjs0-libmozjs185-1.0] 1.32.0-5 ii libgl1-mesa-glx [libgl1] 8.0.5-3 ii libglib2.0-0 2.34.3-2~local0 ii libgnome-desktop-3-2 3.4.2-1 ii libgnome-keyring03.4.1-1 ii libgnome-menu-3-03.4.2-7 ii libgstreamer0.10-0 0.10.36-1 ii libgtk-3-0 3.6.4-1 ii libjson-glib-1.0-0 0.14.2-1 ii libmozjs185-1.0 1.8.5-1.0.0+dfsg-4 ii libmuffin0 1.1.2-1 ii libnm-glib4 0.9.4.0-8 ii libnm-util2 0.9.4.0-8 ii libpango1.0-01.30.0-1 ii libpolkit-agent-1-0 0.110-2 ii libpolkit-gobject-1-00.110-2 ii libpulse-mainloop-glib0 2.0-6 ii libpulse02.0-6 ii libstartup-notification0 0.12-1 ii libx11-6 2:1.5.0-1 ii libxfixes3 1:5.0-4 ii libxml2 2.8.0+dfsg1-7 ii mesa-utils 8.0.1-2+b3 ii multiarch-support2.13-38 ii python 2.7.3-3 ii python-dbus 1.1.1-1 ii python-gconf 2.28.1+dfsg-1 ii python-imaging 1.1.7-4 ii python-lxml
Bug#696957: linux-tools-3.2: perf record should state that sys.kernel.perf_event_paranoid might have something to do with its failure
Control: tag -1 - unreproducible moreinfo Control: tag -1 upstream fixed-upstream patch On Mon, 2012-12-31 at 05:28 +1100, Michael van der Kolff wrote: On Mon, Dec 31, 2012 at 2:11 AM, Ben Hutchings b...@decadent.org.uk wrote: Control: tag -1 unreproducible On Sun, 2012-12-30 at 08:56 +1100, Michael van der Kolff wrote: Package: linux-tools-3.2 Version: 3.2.17-1 Severity: normal Dear Maintainer, When issuing perf record -p annoying_process_id -g, I got Fatal: failed to mmap with 22 (Invalid argument). This is remedied by setting /proc/sys/kernel/perf_event_paranoid to -1 (I tested it with 0, and it still occurred). perf record should state what sys.kernel.perf_event_paranoid should be set to in response to failure, instead of giving me such a useless error message. I can't reproduce this: $ perf record -p 20140 -g # 20140 is my own process ^C[ perf record: Woken up 1 times to write data ] [ perf record: Captured and wrote 0.015 MB perf.data (~634 samples) ] $ perf record -p 1 -g Error: Permission error - are you root? Consider tweaking /proc/sys/kernel/perf_event_paranoid: It was the fact that this popped when I was trying to look at a process that wasn't my own that got me thinking :) Is the target process running under the same uid as perf? Can you provide an strace log for this? Yep: mvanderkolff@mvdk-pers-lap:~$ ps ux | grep 5309 1000 5309 16.3 11.6 972360 695208 ? SNl 05:13 1:34 /usr/lib/tracker/tracker-miner-fs 1000 6399 0.0 0.0 7832 876 pts/0S+ 05:23 0:00 grep 5309 mvanderkolff@mvdk-pers-lap:~$ (strace perf record -p 5309) strace.log 21 mvanderkolff@mvdk-pers-lap:~$ id uid=1000(mvanderkolff) gid=1000(mvanderkolff) groups=1000(mvanderkolff),24(cdrom),25(floppy),27(sudo),29(audio),30(dip),44(video),46(plugdev),105(scanner),110(bluetooth),112(netdev) mvanderkolff@mvdk-pers-lap:~$ tail strace.log mmap(NULL, 528384, PROT_READ|PROT_WRITE, MAP_SHARED, 8, 0) = -1 EPERM (Operation not permitted) munmap(0x7fe4ae2d8000, 528384) = 0 munmap(0x7fe4ae257000, 528384) = 0 munmap(0x7fe4ae1d6000, 528384) = 0 munmap(0x7fe4aaf58000, 528384) = 0 munmap(0x, 528384) = -1 EINVAL (Invalid argument) write(2, Fatal: failed to mmap with 22 ..., 52 Fatal: failed to mmap with 22 (Invalid argument) ) = 52 exit_group(128) = ? OK, I get it. It's doing some cleanup after the first error, which also fails and changes the error code. And then it reports the second error. This was fixed upstream (sort of) in v3.3, and I might be able to include that in an update. I can't promise it will be considered important enough to fix at this point in the release, though. Ben. -- Ben Hutchings Never attribute to conspiracy what can adequately be explained by stupidity. signature.asc Description: This is a digitally signed message part
Bug#680737: linux-image-3.2.0-2-amd64: Intel i915: black display after boot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Ben, On 20.01.2013 16:05, Ben Hutchings wrote: OK, please file a bug report at https://bugs.freedesktop.org/ under product 'DRI', component 'DRM/Intel'. Let us know the bug number or URL so we can track it. bug number is 59628. - -- Best regards Roland -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlD8EVwACgkQq/ywNCsrGZ7JMACfQblpPCK+ULhJYoUc0xwbfNc/ uQYAn301/O9mibLz0HXe0mneTIzaZkWC =vyxN -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#698241: NULL password query result permits login with any password
On Sun, Jan 20, 2013 at 03:01:05PM +0100, Julien Cristau wrote: On Sat, Jan 19, 2013 at 19:59:43 +0100, Jan Dittberner wrote: I have an upload for Squeeze ready and attach the corresponding debdiff to this mail. You can also browse the changes in the package's squeeze branch [4]. [4] http://anonscm.debian.org/gitweb/?p=collab-maint/pam-pgsql.git;a=shortlog;h=refs/heads/squeeze Please tell me whether I should upload the fixed package for Squeeze to stable-proposed-updates. Assuming that's been tested on a squeeze system, please go ahead. Yes, test on a squeeze system was successful. Upload completed. Best regards, Jan -- Jan Dittberner - Debian Developer GPG-key: 4096R/558FB8DD 2009-05-10 B2FF 1D95 CE8F 7A22 DF4C F09B A73E 0055 558F B8DD http://ddportfolio.debian.net/ - http://people.debian.org/~jandd/ signature.asc Description: Digital signature
Bug#680737: linux-image-3.2.0-2-amd64: Intel i915: black display after boot
Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=59628 Control: tag -1 - moreinfo On Sun, 2013-01-20 at 16:46 +0100, Roland Gruber wrote: Hi Ben, On 20.01.2013 16:05, Ben Hutchings wrote: OK, please file a bug report at https://bugs.freedesktop.org/ under product 'DRI', component 'DRM/Intel'. Let us know the bug number or URL so we can track it. bug number is 59628. Thanks. Ben. -- Ben Hutchings Never attribute to conspiracy what can adequately be explained by stupidity. signature.asc Description: This is a digitally signed message part
Bug#698561: libilmbase-dev: Typo in package description: relesaed
tags 698561 pending thanks On 2013-01-20 Pascal De Vuyst pascal.devu...@gmail.com wrote: Package: libilmbase-dev [...] Dear Maintainer, The package description contains a small typo: a set of utility libraries relesaed by ILM and used by OpenEXR. Should be: a set of utility libraries released by ILM and used by OpenEXR. Thank you. Fixed in GIT. cu andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#697019: linux-image-3.2.0-4-amd64: USB 3.0 ext HDD drive doesnt work and hangs usb 3.0 hub
Control: tag -1 moreinfo On Mon, 2012-12-31 at 00:55 +0400, Nick Y Kuzminyh wrote: Package: src:linux Version: 3.2.35-2 Severity: normal Problem take place for portable usb 3.0 HDD (no external power source). There are two USB 3.0 ports at my laptop. There is no problem with USB 2.0 HDD and various USB 1.1 devices (such as mouse) at the usb 3.0 ports. When I plug usb 3.0 HDD device, hdd led goes On, after 5-7 sec hdd led goes Off. Hdd is not mounted. After that fail, both USB 3.0 ports became completely unusable (until reboot). Laptop Lenovo Thinkpad Edge 330G (3354-24G), CPU: Pentium B970, chipset: Intel HM77 Express, IO Controller: Intel Corporation 7 Series/C210 Series Chipset, In BIOS menu, USB 3.0 Support=Enabled problematic device: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub kernel log file comments: I've made the following actions: 1) attach USB 3.0 HDD drive (Seagate 500Gb) to USB 2.0 port, device is mounted properly. Unmount and detach. 2) attach old usb 2.0 HDD drive (Transcend 160Gb) to USB 3.0 port, device is mounted properly. Unmount and detach. 3) attach USB 3.0 HDD drive (Seagate 500Gb) to USB 2.0 port, device is not mounted, both USB 3.0 ports became unusable [...] In step 3, I think you meant to say 'USB 3.0 port', right? Could you test whether Linux 3.7 (currently available in experimental http://wiki.debian.org/DebianExperimental) still has this problem? Ben. -- Ben Hutchings Never attribute to conspiracy what can adequately be explained by stupidity. signature.asc Description: This is a digitally signed message part
Bug#695015: Warning: 'with' will become a reserved keyword in Python 2.6
tags 695015 patch thanks On Tue, Jan 15, 2013 at 11:37 AM, Florent Fourcot web...@flo.fourcot.fr wrote: Actually, Weboob does not support python 2.5. This is why the packet depends on python (= 2.6.6-7~), it should not be possible to use Weboob with python 2.5 (I'm not a packaging specialist, but I did not see everything wrong on http://packages.debian.org/wheezy/weboob) So the solution is at: http://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html#s-specifying_versions Simply specify X-Python-Version: = 2.6 2cts -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698574: dictionaries-common: Please add Conflicts: myspell-cs-cz, myspell-eu-es, myspell-gl-es
Package: dictionaries-common Version: 1.12.10 Severity: important User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + myspell-cs-cz myspell-eu-es myspell-gl-es Hi, myspell-cs-cz, myspell-eu-es, myspell-gl-es were removed after lenny but have not been cleaned up so far. They might have survived a upgrade from lenny to squeeze without problems, but they will fail to purge in wheezy because update-openoffice-dicts no longer exists: Removing myspell-gl-es ... /var/lib/dpkg/info/myspell-gl-es.postrm: 5: /var/lib/dpkg/info/myspell-gl-es.postrm: update-openoffice-dicts: not found dpkg: error processing myspell-gl-es (--remove): subprocess installed post-removal script returned error exit status 127 Adding the conflict should remove the packages before update-openoffice-dicts disappears. This is needed for a clean upgrade path of long grown systems ... I can help testing the fix if you put the .deb and a corresponding Packages file somewhere. Andreas myspell-cs-cz_None.log.gz Description: GNU Zip compressed data
Bug#696026: bug#13505: Bug#696026: emacs24: file corruption on saving
From: Rob Browning r...@defaultvalue.org
Date: Sat, 19 Jan 2013 22:09:28 -0600
Cc: 696026-forwar...@bugs.debian.org, Vincent Lefevre vinc...@vinc17.net,
696...@bugs.debian.org
Vincent Lefevre vinc...@vinc17.net writes:
Package: emacs24
Version: 24.2+1-1
Severity: grave
Justification: causes non-serious data loss
The file file1 (attached) has the following contents:
6c e2 80 99 c3 a9 0a 74 65 73 74 e9 0a |l..test..|
1. Open file1 with emacs -Q. It is regarded as
an in-is13194-devanagari-unix file.
2. Type M-: (set-buffer-modified-p t) to mark the buffer as modified
(so that one can save it).
3. Save the file with C-x C-s. It is proposed:
[...]
Select one of the safe coding systems listed below,
or cancel the writing with C-g and edit the buffer
to remove or modify the problematic characters,
or specify any other coding system (and risk losing
the problematic characters).
raw-text emacs-mule no-conversion
4. Choose raw-text (the default) or no-conversion. One can assume
that the file will not be modified. But it gets corrupted: one
obtains a file file2 (attached) with the following contents:
6c e0 a5 88 80 99 e0 a4 a5 e0 a4 8a 0a 74 65 73
|ltes|
0010 74 e0 a4 bc 0a|t|
Note: Actually file1 has mixed UTF-8 and ISO-8859-1 contents due to
a user error. But due to this bug, an attempt to fix the problem with
Emacs makes things even worse! BTW, I had the same problem in the past
when attempting to edit an mbox file with Emacs (in this case, having
mixed UTF-8 and ISO-8859-1 contents is normal). How Emacs interprets
such contents doesn't matter, but by default, it mustn't corrupt the
file on saving.
There is no such problem with GNU Emacs 23.4.1 (Debian package
emacs23 23.4+1-4).
First, this isn't really a regression: Emacs 23 has the same
problem. It's just that Emacs 23 doesn't autodetect
in-is13194-devanagari in this file, while Emacs 24 does. If you say
C-x RET c raw-text RET C-x C-f to visit this file in Emacs 24, the
problem will be gone, which is exactly what happens in Emacs 23,
because it visits the file in raw-text to begin with. Conversely, if
you use C-x RET c in-is13194-devanagari RET C-x C-f to visit the
file in Emacs 23, you will get the same problem saving it.
I didn't research the reason why Emacs 24 autodetects this encoding,
and whether this is on purpose. Perhaps Handa-san could tell.
More to the point: there seems to be a fundamental misunderstanding
here regarding the effect of selecting an encoding at save time. It
sounds like the OP thought that selecting a literal encoding, such
as raw-text, which is supposed to leave the binary stream unaltered
(apart of the EOL format), will ensure that a buffer will be saved
exactly as it was originally found on disk. But this is false. What
raw-text and no-conversion do is to write out the _internal_
representation of each character without any conversions. The
original encoded form of the characters as found on disk at visit time
_cannot_ be recovered by saving with raw-text, because that encoded
form is lost without a trace when the file is _visited_ and decoded
into the internal representation. The only information that's left is
the coding-system used to decode the characters. But since the file's
encoding in this case is inconsistent, that coding-system cannot be
used to save it back (Emacs will not let you do so, as demonstrated in
the report), and therefore the original form cannot be recovered this
way.
What the user should do to avoid this data loss is prevent the
incorrect decoding of the file's contents when the file is visited.
To this end, the file should be visited with no-conversion or
raw-text, using C-x RET c raw-text RET C-x C-f. Then it will be
possible to repair the file and write it back using the same raw-text
encoding.
If the fact that the file's encoding is inconsistent is not
realized until some time after the file is visited, the user should
use C-x RET r raw-text RET to re-visit the file using raw-text.
IOW, only selecting the appropriate encoding _at_visit_time_ can
prevent data loss in these cases. The expectation that Emacs mustn't
corrupt the file on saving when the file has inconsistent encoding
and was decoded with anything but raw-text or no-conversion is
unjustified.
Personally, I don't think there's a bug here. It's a cockpit error.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698575: xzoom: the window name is undefined after launching the program
Package: xzoom Version: 0.3-23 Severity: normal Tags: patch Dear Maintainer, * What led up to the situation? fvwm style setting did not work * What exactly did you do (or not do) that was effective (or ineffective)? added style xzoom* sticky in fvwm config * What was the outcome of this action? the xzoom window was not sticky * What outcome did you expect instead? I expected it to be sticky * -- System Information: Debian Release: 7.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xzoom depends on: ii libc6 2.13-37 ii libx11-6 2:1.5.0-1 ii libxext6 2:1.3.1-2 ii libxt61:1.1.3-1 xzoom recommends no packages. xzoom 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#692258: New upstream release (1.0.2)
Hello Andrea, I browsed https://github.com/pnegre/python-whiteboard and saw no important change since the debian package made in July 2012. hmmm. the directory https://github.com/pnegre/python-whiteboard/tree/master/stuff contains a few changes which were made 4 months ago: it means changes done in September. However, if I browse https://github.com/pnegre/python-whiteboard/tree/r1/stuff, nothing has changed for two years. Is there a branch, or a tag, to get precisely the release 1.0.2? On the contrary, I shall get the master/head release, which may contain last minute errors. Best regards, Georges. Andrea Colangelo a écrit : Package: python-whiteboard Severity: wishlist python-whiteboard 1.0.2 has been released upstream with several bugfixes, please consider upgrading the package. If you'd like some help maintaining this package, I'd be glad to co-maintain it. -- Andrea Colangelo | http://andreacolangelo.com Ubuntu Developer www.ubuntu.com | Debian Maintainer www.debian.org -- Georges KHAZNADAR et Jocelyne FOURNIER 22 rue des mouettes, 59240 Dunkerque France. Téléphone +33 (0)3 28 29 17 70 signature.asc Description: Digital signature
