Bug#700768: samba4: Error upgrade to version 4.0.3
Package: samba4
Version: 4.0.3+dfsg1-0.1
Severity: important
Dear Maintainer,
During update I get this messages:
Setting up samba4 (4.0.3+dfsg1-0.1) ...
Checking 208 objects
Not fixing nTSecurityDescriptor on CN=Cert
Publishers,CN=Users,DC=localdomain
Not fixing nTSecurityDescriptor on
CN=3c784009-1f57-4e2a-9b04-6915c9e71961,CN=Operations,CN=DomainUpdates,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on CN=Performance Monitor
Users,CN=Builtin,DC=localdomain
Not fixing nTSecurityDescriptor on
CN=ipsecNFA{6A1F5C6F-72B7-11D2-ACF0-0060B0ECCA17},CN=IP
Security,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on
CN=6bcd568b-8314-11d6-977b-00c04f613221,CN=Operations,CN=DomainUpdates,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on
CN=6bcd567b-8314-11d6-977b-00c04f613221,CN=Operations,CN=DomainUpdates,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on
DC=h.root-servers.net,DC=RootDNSServers,CN=MicrosoftDNS,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on
CN=6bcd5679-8314-11d6-977b-00c04f613221,CN=Operations,CN=DomainUpdates,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on
CN=ebad865a-d649-416f-9922-456b53bbb5b8,CN=Operations,CN=DomainUpdates,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on
CN=ipsecNFA{7238523E-70FA-11D1-864C-14A3},CN=IP
Security,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on
DC=a.root-servers.net,DC=RootDNSServers,CN=MicrosoftDNS,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on
CN=3e4f4182-ac5d-4378-b760-0eab2de593e2,CN=Operations,CN=DomainUpdates,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on CN=Users,DC=localdomain
Not fixing nTSecurityDescriptor on CN=Event Log
Readers,CN=Builtin,DC=localdomain
Not fixing nTSecurityDescriptor on
CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on CN=Default Domain
Policy,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on
DC=j.root-servers.net,DC=RootDNSServers,CN=MicrosoftDNS,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on
CN=13d15cf0-e6c8-11d6-9793-00c04f613221,CN=Operations,CN=DomainUpdates,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on CN=AppCategories,CN=Default Domain
Policy,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on
CN=c4f17608-e611-11d6-9793-00c04f613221,CN=Operations,CN=DomainUpdates,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on CN=Content,CN=Domain System
Volume,CN=DFSR-GlobalSettings,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on
DC=c.root-servers.net,DC=RootDNSServers,CN=MicrosoftDNS,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on
CN=User,CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on CN=RID Manager$,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on
CN=8437C3D8-7689-4200-BF38-79E4AC33DFA0,CN=Operations,CN=DomainUpdates,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on
DC=l.root-servers.net,DC=RootDNSServers,CN=MicrosoftDNS,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on
CN=f58300d1-b71a-4DB6-88a1-a8b9538beaca,CN=Operations,CN=DomainUpdates,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on
CN=ipsecNegotiationPolicy{7238523B-70FA-11D1-864C-14A3},CN=IP
Security,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on
DC=e.root-servers.net,DC=RootDNSServers,CN=MicrosoftDNS,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on
DC=RootDNSServers,CN=MicrosoftDNS,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on CN=Pre-Windows 2000 Compatible
Access,CN=Builtin,DC=localdomain
Not fixing nTSecurityDescriptor on CN=FileLinks,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on CN=Builtin,DC=localdomain
Not fixing nTSecurityDescriptor on
CN=Operations,CN=DomainUpdates,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on
CN=d85c0bfd-094f-4cad-a2b5-82ac9268475d,CN=Operations,CN=DomainUpdates,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on
DC=g.root-servers.net,DC=RootDNSServers,CN=MicrosoftDNS,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on
CN=VolumeTable,CN=FileLinks,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on CN=Domain Guests,CN=Users,DC=localdomain
Not fixing nTSecurityDescriptor on
CN=6ada9ff7-c9df-45c1-908e-9fef2fab008a,CN=Operations,CN=DomainUpdates,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on CN=ComPartitions,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on CN=Meetings,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on CN=Policies,CN=System,DC=localdomain
Not fixing nTSecurityDescriptor on CN=Denied RODC Password Replication
Group,CN=Users,DC=localdomain
Not fixing nTSecurityDescriptor on CN=Guests,CN=Builtin,DC=localdomain
Not fixing nTSecurityDescriptor on
CN=f607fd87-80cf-45e2-890b-6cf97e
Bug#700696: [Pkg-acpi-devel] Bug#700696: acpi-support: race in sleep script delays screen locking to after resume
On Sat, Feb 16, 2013 at 11:43:21AM +0100, Tormod Volden wrote: > http://anonscm.debian.org/gitweb/?p=pkg-acpi/acpi-support.git;a=commitdiff;h=9fb9c28886b4002306428ac2b7ff04779bd0e0cb > changed the xscreensaver-command -lock invocation to be run in > background. This results in /etc/acpi/sleep_suspend.sh calling > pm-suspend before the locking has been done. This is not true, this commit only merges some patches. The real commit was d2d1c0a283de8695f3681fb211e49633f11cba18. You can see its history on http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593303. > Upon resuming from sleep, the screen is displayed for a second before > the screensaver fades the screen and locks it. Some users consider this > a security issue. I tend to agree, although a second seems to be stretching it. > Simply removing the backgrounding &'s fixes the issue. But re-open #593303. Surely security is mor eimportant than speed, but maybe we can find a way to satisfy both. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org Jabber: michael.meskes at gmail dot com VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700642: index files are not updated
When looked again in the target, directory I found the sources.list is clean ie, does not have any repository configured but the indexes are not cleaned (missed running an apt-get update after changing sources.list). apt-cache policy grub-pc shows a network repository grub-pc: Installed: (none) Candidate: 1.99-26 Version table: 1.99-26 0 500 cdrom://[Debian GNU/Linux 7.0~b4 _Wheezy_ - Official Snapshot amd64 LIVE/INSTALL Binary 20130120-20:35]/ wheezy/main amd64 Packages 500 http://ftp.debian.org/debian/ sid/main amd64 Packages Now there is also another problem as it should take cdrom:// as first priority, but it somehow can't find it, probably, as it is live USB and apt is expecting a traditional cdrom. This issue was reproduced in a VirtualBox VM so it is not hardware specific (as I guessed in the beginning). -- പ്രവീണ് അരിമ്പ്രത്തൊടിയില് You have to keep reminding your government that you don't get your rights from them; you give them permission to rule, only so long as they follow the rules: laws and constitution. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#630532: xorg hangs in screensaver (radeon chipset)
Dear Michel, I filed a bug against libgl1-mesa-dri. Thank you very much for your response. Sincerely, Adrian Immanuel KIESS On Mon, 2013-02-11 at 18:13 +0100, Michel Dänzer wrote: > On Mon, 2013-02-11 at 17:42 +0100, Adrian Immanuel Kiess wrote: > > Package: xserver-xorg-video-radeon > > Version: 1:6.14.4-6 > > Followup-For: Bug #630532 > > Unless you get the same kernel messages as reported in #630532, it's > probably not the same bug. Please file your own against libgl1-mesa-dri. > > -- With greetings from Leipzig, Germany. Adrian Immanuel Kieß Administrator & programmer UNIX / Perl / LaTeX -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700642: installer is not expecting a network source
In the traditional install method the installer is not expecting a network source when it asks if the users wants a network mirror so it doesn't refresh pkgcache when 'No' is selected for network mirror. In case of live installer should refresh the pkgcache even if the user selects 'No' when choosing a network mirror to clear the existing network source in the pkgcache. -- പ്രവീണ് അരിമ്പ്രത്തൊടിയില് You have to keep reminding your government that you don't get your rights from them; you give them permission to rule, only so long as they follow the rules: laws and constitution. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#695182: [RFC] Reproducible OOM with just a few sleeps
On 01/14/2013 11:00 PM, Dave Hansen wrote: On 01/11/2013 07:31 PM, paul.sz...@sydney.edu.au wrote: Seems that any i386 PAE machine will go OOM just by running a few processes. To reproduce: sh -c 'n=0; while [ $n -lt 1 ]; do sleep 600 & ((n=n+1)); done' My machine has 64GB RAM. With previous OOM episodes, it seemed that running (booting) it with mem=32G might avoid OOM; but an OOM was obtained just the same, and also with lower memory: Memorysleeps to OOM free shows total (mem=64G) 5300 64447796 mem=32G 10200 31155512 mem=16G 13400 14509364 mem=8G14200 6186296 mem=6G15200 4105532 mem=4G16400 2041364 The machine does not run out of highmem, nor does it use any swap. I think what you're seeing here is that, as the amount of total memory increases, the amount of lowmem available _decreases_ due to inflation of mem_map[] (and a few other more minor things). The number of sleeps So if he config sparse memory, the issue can be solved I think. you can do is bound by the number of processes, as you noticed from ulimit. Creating processes that don't use much memory eats a relatively large amount of low memory. This is a sad (and counterintuitive) fact: more RAM actually *CREATES* RAM bottlenecks on 32-bit systems. On my large machine, 'free' fails to show about 2GB memory, e.g. with mem=16G it shows: root@zeno:~# free -l total used free sharedbuffers cached Mem: 14509364 435440 14073924 0 4068 111328 Low:769044 120232 648812 High: 13740320 315208 13425112 -/+ buffers/cache: 320044 14189320 Swap:134217724 0 134217724 You probably have a memory hole. mem=16G means "give me all the memory below the physical address at 16GB". It does *NOT* mean, "give me enough memory such that 'free' will show ~16G available." If you have a 1.5GB hole below 16GB, and you do mem=16G, you'll end up with ~14.5GB available. The e820 map (during early boot in dmesg) or /proc/iomem will let you locate your memory holes. Dear Dave, two questions here: 1) e820 map is read from BIOS, correct? So if all kinds of ranges dump from /proc/iomem are setup by BIOS? 2) only "System RAM" range dump from /proc/iomem can be treated as real memory, all other ranges can be treated as holes, correct? -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majord...@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: mailto:"d...@kvack.org";> em...@kvack.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700770: security-tracker: DSA-2624-1 vs. tracker
Package: security-tracker Severity: normal Hello, DSA-2624-1 [1] states that a number of vulnerabilities have been fixed for squeeze in ffmpeg/4:0.5.10-1 . The tracker seems to agree on its corresponding DSA page [2] and on *some* of the corresponding CVE pages. However, three vulnerabilities [3][4][5] seem to be still considered unfixed for squeeze (security). Is the DSA wrong? Or is the tracker wrong? Please clarify, and, in the latter case, please fix the tracker data. Thanks for your time! [1] https://lists.debian.org/debian-security-announce/2013/msg00029.html [2] https://security-tracker.debian.org/tracker/DSA-2624-1 [3] https://security-tracker.debian.org/tracker/CVE-2012-2784 [4] https://security-tracker.debian.org/tracker/CVE-2012-2788 [5] https://security-tracker.debian.org/tracker/CVE-2012-2801 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700737: binutils-gold: produces different symbols for webkit
tags 700737 + moreinfo quit Hi Michael, Michael Gilbert wrote: > - > (optional|c++)"WebCore::TextIterator::getLocationAndLengthFromRange(WebCore::Element*, > WebCore::Range const*, unsigned int&, unsigned int&)@Base" 1.7.4 > +#MISSING: 1.8.1-3.3# > (optional|c++)"WebCore::TextIterator::getLocationAndLengthFromRange(WebCore::Element*, > WebCore::Range const*, unsigned int&, unsigned int&)@Base" 1.7.4 >From the dpkg-gensymbols(1) manpage: optional A symbol marked as optional can disappear from the library at any time and that will never cause dpkg-gensymbols to fail. [...] > @@ -213,6 +213,7 @@ > _NPN_SetException@Base 1.3.10 > _NPN_SetProperty@Base 1.3.10 > _NPN_UTF8FromIdentifier@Base 1.3.10 > + _ZdlPv@Base 1.8.1-3.3 c++filt tells me this is operator delete(void*). So presumably an entry (optional|c++)"operator delete(void*)" would suppress the build failure. Can you say a little more about whether this is a gold bug? Do binaries built against versions of libwebkit built with gold rely on this symbol and fail when run against libwebkit built with ld.bfd? In C++, different lists of exported symbols based on the phase of moon are completely normal, for example when template instantiation is involved. So more details would be welcome. 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#700770: security-tracker: DSA-2624-1 vs. tracker
On Sun, Feb 17, 2013 at 11:06:15AM +0100, Francesco Poli (wintermute) wrote: > Package: security-tracker > Severity: normal > > Hello, > DSA-2624-1 [1] states that a number of vulnerabilities have been fixed > for squeeze in ffmpeg/4:0.5.10-1 . > The tracker seems to agree on its corresponding DSA page [2] and > on *some* of the corresponding CVE pages. > However, three vulnerabilities [3][4][5] seem to be still considered > unfixed for squeeze (security). > > Is the DSA wrong? > Or is the tracker wrong? > > Please clarify, and, in the latter case, please fix the tracker data. > > Thanks for your time! All entries seem fixed now, I guess it only needed some time to get the data processed. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700608: CVE-2013-0296 also in squeeze
Control: found -1 2.1.6-1 Hi, This issue also exists in squeeze. Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700771: RFS: seafile-client/1.4.5-1 [ITP] -- online file storage and collaboration tool - client
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "seafile-client" * Package name: seafile-client Version : 1.4.5-1 Upstream Author : Lingtao Pan * URL : https://github.com/haiwen/seafile * License : GPL-3+ with OpenSSL exception Section : net It builds those binary packages: seafile-client - online file storage and collaboration tool - client To access further information about this package, please visit the following URL: http://mentors.debian.net/package/seafile-client Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/s/seafile-client/seafile-client_1.4.5-1.dsc More information about seafile-client can be obtained from https://github.com/haiwen/seafile. Changes since the last upload: * Initial release (Closes: #698681) Regards, Shuai Lin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#699405: Summary: [journal.bookmarks transaction recovery error on multi-committer repos ]
On Thu, Jan 31, 2013 at 03:27:38PM +1100, Peter Chubb wrote: > Package: mercurial > Version: 2.2.2-1~bpo60+1 > Severity: normal > > We keep being hit by bug http://bz/selenic.com/show_bug/?id=3318 --- That bug was fixed in mercurial 2.1.2 and you are using mercurial 2.2.2 which shouldn't have it. > can a more recent version of mercurial be added to stable, please? Right now we are in a freeze so the only uploads going to stable are ones that fix bugs that are >= important. New versions of mercurial are currently only uploaded to experimental. Once we release wheezy, wheezy-backports will get a more recent mercurial. Cheers, Javi signature.asc Description: Digital signature
Bug#700771: RFS: seafile-client/1.4.5-1 [ITP] -- online file storage and collaboration tool - client
On 17/02/2013 11:43, Shuai Lin wrote: > Package: sponsorship-requests > Severity: wishlist > > Dear mentors, > > I am looking for a sponsor for my package "seafile-client" Hello, sponsors, i've helped Shuai Lin review his package. He has done a great job at fixing the problems i pointed out. I'm willing to sponsor him - but i am only DM, so i'll continue reviewing his package until another DD step in. Hi Shuai, could you have a look at lintian pedantic/experimental warnings ? You can quickly see them at your package page on mentors.d.n, or reproduce using lintian --pedantic -E seafile-client_1.4.5-1_amd64.changes Mind that they could be false positives, in which case you can ignore them. (Or better, report a bug to lintian package, having made sure it hasn't already been reported before). Regards Jérémy. signature.asc Description: OpenPGP digital signature
Bug#478605: Fixed in 2.9.1
feh v2.9.1 fixes this issue. signature.asc Description: Digital signature
Bug#700563: pu: package fglrx-driver/10-9-3squeeze1
On 2013-02-17 00:50, Adam D. Barratt wrote:
> [Why the CC to debian-release? That's where mail for release.d.o bugs
> goes anyway...]
I trimmed down the recipients to only the bug, but didn't switch that
from Cc: to To:
[same in this mail, but now with To: 700563@]
> Ah. In that case, you just need patience. :)
All right, everything is here by now.
> The buildds only find out
> about new packages in {t,}pu at dinstall. My acceptance of the upload
> was after the 19:52 dinstall, so it'll need to wait for the 01:52.
I never looked at the timings in detail ... I just wanted to ensure I
didn't miss something and that could cause trouble with the point
release. :-)
Andreas
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700277: pu: package kfreebsd-8/8.1+dfsg-8+squeeze4
Control: tags -1 + pending On Sat, 2013-02-16 at 19:07 -0800, Christoph Egger wrote: > Steven Chamberlain writes: > > Yes please! I was just about to ask if anyone is available to do this. [...] > Should be uploaded Flagged for acceptance in to p-u; thanks. 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#700772: josm: Menus do not stay open when JOSM is maximised
Package: josm Version: 0.0.svn5608+dfsg1-2 Severity: important Most of the time, when I maximise JOSM, the menus and other UI elements break. They work again if the window is un-maximised. This problem appears to be present using the Gnome Shell (currently using 3.6), but not with other window managers. -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.5-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages josm depends on: ii ant 1.8.2-4 ii libcommons-codec-java1.6-1 ii libgettext-commons-java 0.9.6-2 ii libmetadata-extractor-java 2.3.1+dfsg-2 ii liboauth-signpost-java 1.2.1.2-1 ii libsvgsalamander-java0~svn95-1 ii openjdk-6-jre6b27-1.12.1-2 ii openjdk-7-jre7u3-2.1.4-1 ii openstreetmap-map-icons-classic 1:0.0.svn28731-1 Versions of packages josm recommends: ii josm-l10n 0.0.svn5608+dfsg1-2 ii josm-plugins 0.0.svn29007+ds1-1 ii webkit-image-gtk 0.0.svn25399-3 josm 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#698748: wicd-daemon: 'man wicd' typo: "Everthing"
tags 698748 confirmed upstream fixed-upstream thanks Hello, On Tue, 22 Jan 2013 23:40:40 -0500, A. Costa wrote: > Dear Maintainer, > > Found a typo in '/usr/share/man/man8/wicd.8.gz', see attached '.diff'. Committed upstream. Thanks, David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature
Bug#700773: DDPO: does not show PU NMUs
Package: qa.debian.org Severity: normal Looking at my overview page http://qa.debian.org/developer.php?login=anbe%40debian.org+pkg-nvidia-devel%40lists.alioth.debian.org+pkg-fglrx-devel%40lists.alioth.debian.org&comaint=yes&reset=yes I don't see my NMUs to PU listed there. The packages were listed while they were still in the DELAYED queue. The fglrx-driver PU upload is shown (there I'm uploader). The PU NMUs, e.g. gmime2.2, bugzilla, sdic are currently missing. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700774: Homepage do not exist anymore
Package: xli Version: 1.17.0+20061110-4 Severity: normal When I give a command "dpkg --status xli" it also gives URL of homepage of this software. Unfortunately that homepage do not exist anymore. -- System Information: Debian Release: 7.0 APT prefers stable APT policy: (990, 'stable'), (500, 'testing-proposed-updates'), (500, 'stable-updates'), (500, 'proposed-updates'), (102, 'testing'), (101, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xli depends on: ii libc6 2.13-38 ii libjpeg88d-1 ii libpng12-0 1.2.49-3 ii libx11-62:1.5.0-1 ii libxext62:1.3.1-2 ii zlib1g 1:1.2.7.dfsg-13 xli recommends no packages. xli suggests no packages. -- no debconf information -- Juhapekka "naula" Tolvanen * http colon slash slash iki dot fi slash juhtolv "Quidquid Latine dictum sit altum videtur." -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700718: python-numpy: fails to upgrade from squeeze: prerm: 6: update-python-modules: not found
Hi, I have now observed this behavior also while upgrading the following packages from squeeze -> sid (and verified that these upgrades fail on squeeze -> wheezy(+new numpy) in the same way). python-netcdf python-scientific Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700775: Not installable from experimental
Package: gnome-documents Version: 3.6.2-1 Severity: grave Hi, gnome-documents currently isn't installable from experimental as it depends on libgnome-desktop-3-2 (>= 3.2) which is available from sid in 3.4.2-1 and depends on gnome-desktop3-data in _exactly_ that version. However gnome-control-center and other packages in experimental depend on gnome-desktop3-data in a version (>= 3.6) so libgnome-desktop-3-2's dependency can't be fulfilled. Cheers, -- Guido P.S.: Thanks for making gnome 3.6 available via unstale -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-documents depends on: ii dconf-gsettings-backend [gsettings-backend] 0.12.1-3 ii gir1.2-atk-1.0 2.6.0-1 ii gir1.2-clutter-1.0 1.12.0-1 ii gir1.2-evince-3.03.4.0-3.1 ii gir1.2-freedesktop 1.34.2-1 ii gir1.2-gdata-0.0 0.12.0-1 ii gir1.2-gdkpixbuf-2.0 2.26.4-2 ii gir1.2-glib-2.0 1.34.2-1 ii gir1.2-goa-1.0 3.4.2-1 ii gir1.2-gtk-3.0 3.6.4-1 ii gir1.2-gtkclutter-1.01.4.0-1 ii gir1.2-pango-1.0 1.30.1-1 ii gir1.2-soup-2.4 2.40.1-1 ii gir1.2-tracker-0.14 0.14.1-3 ii gjs 1.34.0-1 ii libc62.13-37 ii libcairo21.12.6-1 ii libevdocument3-4 3.4.0-3.1 ii libevview3-3 3.4.0-3.1 ii libgdata13 0.12.0-1 ii libgdk-pixbuf2.0-0 2.26.4-2 ii libglib2.0-0 2.34.3-1 ii libgnome-desktop-3-2 3.4.2-1 ii libgoa-1.0-0 3.6.1-1 ii libgtk-3-0 3.6.4-1 ii liboauth00.9.4-3.1 ii libpango1.0-01.30.1-1 ii libsoup2.4-1 2.40.1-1 ii libtracker-sparql-0.14-0 0.14.1-3 ii tracker 0.14.1-3 Versions of packages gnome-documents recommends: ii unoconv 0.5-1 gnome-documents 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#700776: libexosip2-dev: Dependency on lobosip-dev most likely needs to be versioned
Package: libexosip2-dev Version: 4.0.0-2 Severity: important libexosip2-dev depends unversioned against libosip-dev. Not sure, but it is highly likely that dependency should be versioned at least against major version of osip API, like this: Build-depends: libosip2-dev (>= 4) Regards, - Jonas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700762: System fails to shutdown due to iscsid being terminated.
Ritesh Raj Sarraf wrote: > Hello Wakko > > On Sun, Feb 17, 2013 at 8:13 AM, Wakko Warner wrote: > > I have a test system that boots over iSCSI. If iscsid is killed and the > > kernel decides to sync the scsi caches, the iSCSI connection fails. > > How is iscsid being killed here? > > I still can't see whey the connection would fail. I tested it on one of my systems and it works. iscsid is killed during shutdown by sendsigs. I don't know why either, but once iscsid is dead, the kernel will sync the scsi cache and then the iscsi driver cannot connect anymore. > > I change the init script to drop a link to the PID file for iscsid to the > > /run/sendsigs.omit.d and it shuts down properly now. > > > > I've attached the patch, it's only adds 2 lines. > > > > I looked but have no clue at what it does. It places a link to the pid file so that send sigs will not kill it. -- Microsoft has beaten Volkswagen's world record. Volkswagen only created 22 million bugs. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700678: Please reenable the DDTP email interface
On 16 February 2013 02:45, Martin Eberhard Schauer wrote: > Package: debian-i18n > Severity: normal > X-Debbugs-CC: debian-l10n-de...@lists.alioth.debian.org > > > Dear Masters of Infrastructure, > > please reenable the DDTP email interface. I'm convinced that this will help > DDTP translation teams with little manpower (all except the Italian and > Danish > ones). What makes you think it's disabled? I just sent a message to it and it responded normally. > What can be read on the web regarding DDTP (1) seems not to be true at > present. > > Copied from (1): Can you indicate which bits specifically aren't true? You might need to write the script yourself, but other than that it should work... Have a nice day, -- Martijn van Oosterhout http://svana.org/kleptog/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#670963: lintian: Warn (or at least inform) of non-LFS-enabled binaries
On 2013-01-23 11:45, Guillem Jover wrote:
> On Wed, 2013-01-23 at 09:37:59 +0100, Niels Thykier wrote:
>> On 2013-01-23 02:47, Guillem Jover wrote:
>>> * Handles partially enabled LFS binaries, so that if an object which
>>> is part of the binary has been correctly compiled with LFS but not
>>> another part it will trigger. Add a regression test for this.
>>>
>>
>> It was my understanding that "you" (i.e. the programmer) could
>> deliberately support both 32 and 64 bit interfaces by using
>> -D_LARGEFILE64_SOURCE. But I suppose it is unlikely that anyone would
>> bother having both interfaces around.
>
> Ah, right. I can think of two cases where a binary might kind of
> “ligitimately” mix LFS and non-LFS enabled objects.
>
> [...]
>
> In any case this should be overridable so “legitimate” cases can be
> ignored, but I'd expect those to be few.
>
Right, I think we will go with emitting the tag unless there is complete
LFS support. We can always undo it later. BTW, the previous code has
been running on lintian.d.o for a while - so far at least 300 packages
have triggered (at least once). Though it is hard to tell how much of
the archive is affected from this.
http://lintian.debian.org/tags/binary-file-built-without-LFS-support.html
>>> Also something to note is that some of the functions will most
>>> probably not match as they get renamed to something else, for example
>>> stat(2) will end up as __xstat on the binary's symbol table. There's
>>> probably others like that.
>>
>> Really? Because I looked at the include files and saw loads of:
>>
>> #define symbol symbol64
>>
>> But yeah, stat appears to be "__extern_inline"'d, so that would fail
>> detection.
>
> I didn't check if there's any other, so just wanted to bring it up
> here so this does not get missed. Maybe a more resistant way to handle
> this could be to add a generator program in lintian that looks for
> foo/foo64 symbol variants from libc at build time?
>
Given that are now flagging any known "bad" LFS usage, we do not need to
know what the "safe" variant is called. I have replaced {,f,l}stat
functions with the __{,f,l}xstat variants.
>>> Of course feel free to squash them into a single patch if that's your
>>> preferred form.
>>
>> """
>> +/* Name function so that it comes last in the symbol table, to make
>> + * sure the presence of an LFS function does not mark the whole binary
>> + * as LFS-enabled. */
>> """
>>
>> This comment (from the test in patch 3) does not seem to be accurate
>> (any longer). Regardless of which order they appear in the check should
>> be produce the same result (as we would no longer whitelist any binary
>> with LFS-enabled code).
>
> Right sorry, I added that case as a regression check, and the explanation
> seemed fitting to explain why the function name, it might need to be
> clarified to explain just that, or do you want that removed, do you want
> me to resend?
>
> Thanks,
> Guillem
>
>
Nah, I just ammended your patch to exclude the comment. All 3 are
committed (note that I also ammended the 0002 to break the pargraph into
smaller ones).
~Niels
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700777: Add Bash completion for /etc/crypttab targets to cryptdisks_{start,stop}
Package: cryptsetup
Version: 2:1.4.3-4
Severity: wishlist
Dear Maintainer(s),
it would be nice if cryptsetup shipped a Bash completion snippet for
cryptdisks_{start,stop} to allow for easy autocompletion of possibly
long (or rarely used) names in /etc/crypttab.
The following, placed in /etc/bash_completion.d/cryptdisks, works for
me, but I am sure there are ways one can improve it. :-)
-- /etc/bash_completion.d/cryptdisks
# cryptdisks_{start,stop} completion by first row of crypttab
#
# Copyright 2013 Claudius Hubig , 2-clause BSD
_cryptdisks() {
local tf;
tf=${TABFILE-"/etc/crypttab"};
COMPREPLY=($(egrep -v "^[[:space:]]*(#|$)" "${tf}" | egrep -o
"^${COMP_WORDS[COMP_CWORD]}[^[:space:]]*"));
return 0;
}
complete -F _cryptdisks cryptdisks_start;
complete -F _cryptdisks cryptdisks_stop;
Thank you very much for considering this and your work for Debian,
Claudius
-- Package-specific info:
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'),
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.7.1.a2017.3 (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
Versions of packages cryptsetup depends on:
ii cryptsetup-bin 2:1.4.3-4
ii debconf [debconf-2.0] 1.5.49
ii dmsetup2:1.02.74-4
ii libc6 2.13-37
Versions of packages cryptsetup recommends:
ii busybox 1:1.20.0-7
ii console-setup 1.88
ii initramfs-tools [linux-initramfs-tool] 0.109
ii kbd 1.15.3-9
Versions of packages cryptsetup suggests:
ii dosfstools 3.0.13-1
ii liblocale-gettext-perl 1.05-7+b1
-- debconf information:
cryptsetup/prerm_active_mappings: true
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700772: [Pkg-osm-maint] Bug#700772: josm: Menus do not stay open when JOSM is maximised
Chris writes: > Most of the time, when I maximise JOSM, the menus and other UI elements break. > They work again if the window is un-maximised. This problem appears to be > present using the Gnome Shell (currently using 3.6), but not with other window > managers. Does this affect other applications written in Java? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700353: libwmf-dev, libwmf-doc: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Followup-For: Bug #700353
Control: tag -1 patch
Hi,
a patch that adds the two preinst scripts to clean up the symlinks is
attached. Install and upgrade paths verified.
I intend to NMU libwmf with this patch in a few days.
Andreas
diffstat for libwmf-0.2.8.4 libwmf-0.2.8.4
changelog |8
libwmf-dev.preinst |8
libwmf-doc.preinst |8
3 files changed, 24 insertions(+)
diff -Nru libwmf-0.2.8.4/debian/changelog libwmf-0.2.8.4/debian/changelog
--- libwmf-0.2.8.4/debian/changelog 2012-11-29 18:58:00.0 +0100
+++ libwmf-0.2.8.4/debian/changelog 2013-02-17 14:23:41.0 +0100
@@ -1,3 +1,11 @@
+libwmf (0.2.8.4-10.3) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * libwmf-{dev,doc}.preinst: Delete /usr/share/doc/$PKG if it is a symlink
+because this is now shipped as a regular directory. (Closes: #700353)
+
+ -- Andreas Beckmann Sun, 17 Feb 2013 14:23:41 +0100
+
libwmf (0.2.8.4-10.2) unstable; urgency=low
* Non-maintainer upload.
diff -Nru libwmf-0.2.8.4/debian/libwmf-dev.preinst libwmf-0.2.8.4/debian/libwmf-dev.preinst
--- libwmf-0.2.8.4/debian/libwmf-dev.preinst 1970-01-01 01:00:00.0 +0100
+++ libwmf-0.2.8.4/debian/libwmf-dev.preinst 2013-02-17 14:20:31.0 +0100
@@ -0,0 +1,8 @@
+#!/bin/sh
+set -e
+
+# #700353
+DOCDIR=/usr/share/doc/libwmf-dev
+test ! -L $DOCDIR || rm $DOCDIR
+
+#DEBHELPER#
diff -Nru libwmf-0.2.8.4/debian/libwmf-doc.preinst libwmf-0.2.8.4/debian/libwmf-doc.preinst
--- libwmf-0.2.8.4/debian/libwmf-doc.preinst 1970-01-01 01:00:00.0 +0100
+++ libwmf-0.2.8.4/debian/libwmf-doc.preinst 2013-02-17 14:21:04.0 +0100
@@ -0,0 +1,8 @@
+#!/bin/sh
+set -e
+
+# #700353
+DOCDIR=/usr/share/doc/libwmf-doc
+test ! -L $DOCDIR || rm $DOCDIR
+
+#DEBHELPER#
Bug#700778: python-crypto-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Package: python-crypto-dbg Version: 2.6-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: squeeze -> wheezy For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase For switching from a symlink to a directory, the *preinst* script should do something like this: DOCDIR=/usr/share/doc/@@PACKAGE@@ if [ -L $DOCDIR ] ; then rm $DOCDIR fi >From the attached log (usually somewhere in the middle...): 0m59.9s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/python-crypto-dbg/changelog.Debian.gz (python-crypto-dbg) != /usr/share/doc/python-crypto/changelog.Debian.gz (python-crypto) /usr/share/doc/python-crypto-dbg/changelog.gz (python-crypto-dbg) != /usr/share/doc/python-crypto/changelog.gz (python-crypto) /usr/share/doc/python-crypto-dbg/copyright (python-crypto-dbg) != /usr/share/doc/python-crypto/copyright (python-crypto) cheers, Andreas python-crypto-dbg_2.6-3.log.gz Description: GNU Zip compressed data
Bug#700779: python-gobject-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Package: python-gobject-dbg Version: 3.2.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: squeeze -> wheezy For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase For switching from a symlink to a directory, the *preinst* script should do something like this: DOCDIR=/usr/share/doc/@@PACKAGE@@ if [ -L $DOCDIR ] ; then rm $DOCDIR fi >From the attached log (usually somewhere in the middle...): 0m58.6s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/python-gobject-dbg/changelog.Debian.gz (python-gobject-dbg) != /usr/share/doc/python-gobject/changelog.Debian.gz (python-gobject) /usr/share/doc/python-gobject-dbg/changelog.gz (python-gobject-dbg) != /usr/share/doc/python-gobject/changelog.gz (python-gobject) /usr/share/doc/python-gobject-dbg/copyright (python-gobject-dbg) != /usr/share/doc/python-gobject/copyright (python-gobject) cheers, Andreas python-gobject-dbg_3.2.2-1.log.gz Description: GNU Zip compressed data
Bug#700780: python-gpgme-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Package: python-gpgme-dbg Version: 0.2-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: squeeze -> wheezy For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase For switching from a symlink to a directory, the *preinst* script should do something like this: DOCDIR=/usr/share/doc/@@PACKAGE@@ if [ -L $DOCDIR ] ; then rm $DOCDIR fi >From the attached log (usually somewhere in the middle...): 0m57.9s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/python-gpgme-dbg/changelog.Debian.gz (python-gpgme-dbg) != /usr/share/doc/python-gpgme/changelog.Debian.gz (python-gpgme) /usr/share/doc/python-gpgme-dbg/copyright (python-gpgme-dbg) != /usr/share/doc/python-gpgme/copyright (python-gpgme) cheers, Andreas python-gpgme-dbg_0.2-2.log.gz Description: GNU Zip compressed data
Bug#696671: tpu: isc-dhcp/4.2.2.dfsg.1-5+deb70u3
Control: tag -1 confirmed
Hi,
On Sat, Feb 16, 2013 at 04:20:45PM -0500, Michael Gilbert wrote:
> On Sat, Feb 16, 2013 at 4:18 PM, Michael Gilbert wrote:
> >> I've attached an updated proposed patch, which also fixes #698582 (and
> >> consequentially #700363).
> > File attached.
> Really attached this time ...
thanks. Please go ahead. One tiny remark, though:
+ if [ -e /etc/dhcp/dhclient.conf ] && \
+ [ "`md5sum /etc/dhcp/dhclient.conf | awk '{print $1;}'`" =
6e3910d75cd5cde0042ecb6d48492ae9 ]; then
+ sed -i -e
's/rfc3442-classless-static-routes;/rfc3442-classless-static-routes,
ntp-servers;/' /etc/dhcp/dhclient.conf
+ fi
Please don't do things with awk that can be realized with cut,
especially in a preinst. But since awk is still pseudo-essential
(pre-depends of base-files) in wheezy, it doesn't make a difference.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
Bug#700781: python-newt-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Package: python-newt-dbg Version: 0.52.14-10 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: squeeze -> wheezy For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase For switching from a symlink to a directory, the *preinst* script should do something like this: DOCDIR=/usr/share/doc/@@PACKAGE@@ if [ -L $DOCDIR ]; then rm $DOCDIR fi >From the attached log (usually somewhere in the middle...): 0m57.3s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/python-newt-dbg/changelog.Debian.gz (python-newt-dbg) != /usr/share/doc/python-newt/changelog.Debian.gz (python-newt) /usr/share/doc/python-newt-dbg/changelog.gz (python-newt-dbg) != /usr/share/doc/python-newt/changelog.gz (python-newt) /usr/share/doc/python-newt-dbg/copyright (python-newt-dbg) != /usr/share/doc/python-newt/copyright (python-newt) cheers, Andreas python-newt-dbg_0.52.14-10.log.gz Description: GNU Zip compressed data
Bug#646934: alacarte: properties menu does not work
I appear to have the same problem... the properties button does not function Running alacarte from the command line yields the following results when pressing the properties button... Traceback (most recent call last): File "/usr/share/alacarte/Alacarte/MainWindow.py", line 470, in on_properties_button_clicked self.on_edit_properties_activate(None) File "/usr/share/alacarte/Alacarte/MainWindow.py", line 339, in on_edit_properties_activate process = subprocess.Popen(['gnome-desktop-item-edit', file_path], env=os.environ) File "/usr/lib/python2.7/subprocess.py", line 679, in __init__ errread, errwrite) File "/usr/lib/python2.7/subprocess.py", line 1259, in _execute_child raise child_exception OSError: [Errno 2] No such file or directory I hope this is of some use. alacarte version is 3.5.3-1 running debian testing/unstable on amd64 kernel 3.7.8-1-experimental Regards Harry signature.asc Description: This is a digitally signed message part
Bug#699615: CVE-2013-0250 - corosync: Remote DoS due improper HMAC initialization
Hi Luciano and Moritz On Sat, Feb 02, 2013 at 01:54:32PM +0100, Luciano Bello wrote: > Package: corosync > Severity: important > Tags: security patch > Justification: user security hole > > Hi there, > Please, take a look to this thread: > http://seclists.org/oss-sec/2013/q1/212 > The patch is included there too. Disclaimer: Did not made a throughout analysis, but upstream mentions in [1], which could help here: [1]: http://www.openwall.com/lists/oss-security/2013/02/01/2 cut-cut-cut-cut-cut-cut- No, this version is not correct. corosync >= 2.0 to < 2.3 are affected. corosync 2.3 and higher have the fix. Also, the DoS reason is not correct. The junk filter part is a consequence on how libnss work and should be dropped. Subject should be: "CVE Request -- Corosync (2.0 <= X < 2.3): Remote DoS due improper HMAC initialization" cut-cut-cut-cut-cut-cut- But this might still need some checking and/or confirmation with upstream. 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#700669: Allow pyrad 1.2-1+deb7u1 into wheezy
On Sun, Feb 17, 2013 at 08:06:36AM +0100, Salvatore Bonaccorso wrote: > I was involved reporting the problem: I noticed now a possible problem > about the versioning: > > Current situation: > > pyrad | 1.2-1| squeeze| source > pyrad | 1.2-1| wheezy | source > pyrad | 1.2-1+deb7u1 | wheezy-p-u | source > pyrad | 2.0-2| sid| source > > Assuming there will be also either a DSA or a pu for pyrad, how should > that be versioned? Traditionally for Squeeze it was +squeeze1, but: > > 1.2-1 <= 1.2-1+deb7u1 > > but > > 1.2-1+squeeze1 is not smaller than 1.2-1 or 1.2-1+deb7u1. Once 1.2-1+deb7u1 reaches wheezy (next 24 hours) we will be able to use 1.2-1+deb6u1 for any hypothetical DSA to slot in between squeeze and wheezy. -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 i have six years of solaris sysadmin experience, from 8->10. i am well qualified to say it is made from bonghits layered on top of bonghits signature.asc Description: Digital signature
Bug#700669: Allow pyrad 1.2-1+deb7u1 into wheezy
On Sun, Feb 17, 2013 at 08:36:24AM +0100, Jeremy Lainé wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 02/17/2013 01:19 AM, Jonathan Wiltshire wrote: > > It's traditional to seek approval *before* uploading; more so in this case > > since adding a > patch system is a no-no. The change itself is fine, please upload with this > only. You will > have to bump the version number IIRC. > > OK, attached is the resulting debdiff. Approved, thanks. -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 i have six years of solaris sysadmin experience, from 8->10. i am well qualified to say it is made from bonghits layered on top of bonghits signature.asc Description: Digital signature
Bug#700782: python3-cxx-dev: unhandled symlink to directory conversion: /usr/include/python3.2
Package: python3-cxx-dev Version: 6.2.4-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: squeeze -> wheezy For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase For switching from a symlink to a directory, the *preinst* script should do something like this: DOCDIR=/usr/share/doc/@@PACKAGE@@ if [ -L $DOCDIR ]; then rm $DOCDIR fi >From the attached log (usually somewhere in the middle...): 0m54.2s INFO: dirname part contains a symlink: /usr/include/python3.2/CXX (python3-cxx-dev) != /usr/include/python3.2mu/CXX (?) /usr/include/python3.2/CXX/Config.hxx (python3-cxx-dev) != /usr/include/python3.2mu/CXX/Config.hxx (?) /usr/include/python3.2/CXX/Exception.hxx (python3-cxx-dev) != /usr/include/python3.2mu/CXX/Exception.hxx (?) /usr/include/python3.2/CXX/Extensions.hxx (python3-cxx-dev) != /usr/include/python3.2mu/CXX/Extensions.hxx (?) /usr/include/python3.2/CXX/IndirectPythonInterface.hxx (python3-cxx-dev) != /usr/include/python3.2mu/CXX/IndirectPythonInterface.hxx (?) /usr/include/python3.2/CXX/Objects.hxx (python3-cxx-dev) != /usr/include/python3.2mu/CXX/Objects.hxx (?) /usr/include/python3.2/CXX/Python3 (python3-cxx-dev) != /usr/include/python3.2mu/CXX/Python3 (?) /usr/include/python3.2/CXX/Python3/Config.hxx (python3-cxx-dev) != /usr/include/python3.2mu/CXX/Python3/Config.hxx (?) /usr/include/python3.2/CXX/Python3/CxxDebug.hxx (python3-cxx-dev) != /usr/include/python3.2mu/CXX/Python3/CxxDebug.hxx (?) /usr/include/python3.2/CXX/Python3/Exception.hxx (python3-cxx-dev) != /usr/include/python3.2mu/CXX/Python3/Exception.hxx (?) /usr/include/python3.2/CXX/Python3/ExtensionModule.hxx (python3-cxx-dev) != /usr/include/python3.2mu/CXX/Python3/ExtensionModule.hxx (?) /usr/include/python3.2/CXX/Python3/ExtensionOldType.hxx (python3-cxx-dev) != /usr/include/python3.2mu/CXX/Python3/ExtensionOldType.hxx (?) /usr/include/python3.2/CXX/Python3/ExtensionType.hxx (python3-cxx-dev) != /usr/include/python3.2mu/CXX/Python3/ExtensionType.hxx (?) /usr/include/python3.2/CXX/Python3/ExtensionTypeBase.hxx (python3-cxx-dev) != /usr/include/python3.2mu/CXX/Python3/ExtensionTypeBase.hxx (?) /usr/include/python3.2/CXX/Python3/Extensions.hxx (python3-cxx-dev) != /usr/include/python3.2mu/CXX/Python3/Extensions.hxx (?) /usr/include/python3.2/CXX/Python3/IndirectPythonInterface.hxx (python3-cxx-dev) != /usr/include/python3.2mu/CXX/Python3/IndirectPythonInterface.hxx (?) /usr/include/python3.2/CXX/Python3/Objects.hxx (python3-cxx-dev) != /usr/include/python3.2mu/CXX/Python3/Objects.hxx (?) /usr/include/python3.2/CXX/Python3/PythonType.hxx (python3-cxx-dev) != /usr/include/python3.2mu/CXX/Python3/PythonType.hxx (?) /usr/include/python3.2/CXX/Version.hxx (python3-cxx-dev) != /usr/include/python3.2mu/CXX/Version.hxx (?) /usr/include/python3.2/CXX/WrapPython.h (python3-cxx-dev) != /usr/include/python3.2mu/CXX/WrapPython.h (?) This could be a change in a python package, not python3-cxx-dev itself, please investigate and maybe reassign or adjust your install location. cheers, Andreas python3-cxx-dev_6.2.4-2.log.gz Description: GNU Zip compressed data
Bug#700783: ITP: lua-discount -- lua bindings for discount
Package: wnpp Severity: wishlist * Package name: lua-discount * Version: 1.2.10.1 * Homepage: http://asbradbury.org/projects/lua-discount/ * Licence: BSD * Short description: lua bindigs for discount * Description: A binding to Discount, a fast C implementation of the Markdown text to HTML markup system which passes the Markdown testsuite. With best regards, Julian Wollrath -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700786: libsidutils-dev: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Package: libsidutils-dev Version: 2.1.1-13 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: squeeze -> wheezy For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase For switching from a symlink to a directory, the *preinst* script should do something like this: DOCDIR=/usr/share/doc/@@PACKAGE@@ if [ -L $DOCDIR ]; then rm $DOCDIR fi >From the attached log (usually somewhere in the middle...): 0m51.3s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/libsidutils-dev/changelog.Debian.gz (libsidutils-dev) != /usr/share/doc/libsidutils0/changelog.Debian.gz (libsidutils0) /usr/share/doc/libsidutils-dev/copyright (libsidutils-dev) != /usr/share/doc/libsidutils0/copyright (libsidutils0) cheers, Andreas libsidutils-dev_2.1.1-13.log.gz Description: GNU Zip compressed data
Bug#700786: libsidutils-dev: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Followup-For: Bug #700786 Control: reassign -1 libsidutils-dev,libresid-builder-dev 2.1.1-13 Hi, same problem in libresid-builder-dev, maybe other binary packages from the same source, too. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700788: libavc1394-dev: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Package: libavc1394-dev Version: 0.5.4-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: squeeze -> wheezy For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase For switching from a symlink to a directory, the *preinst* script should do something like this: DOCDIR=/usr/share/doc/@@PACKAGE@@ if [ -L $DOCDIR ]; then rm $DOCDIR fi >From the attached log (usually somewhere in the middle...): 0m49.5s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/libavc1394-dev/changelog.Debian.gz (libavc1394-dev:amd64) != /usr/share/doc/libavc1394-0/changelog.Debian.gz (libavc1394-0:amd64) /usr/share/doc/libavc1394-dev/changelog.gz (libavc1394-dev:amd64) != /usr/share/doc/libavc1394-0/changelog.gz (libavc1394-0:amd64) /usr/share/doc/libavc1394-dev/copyright (libavc1394-dev:amd64) != /usr/share/doc/libavc1394-0/copyright (libavc1394-0:amd64) cheers, Andreas libavc1394-dev_0.5.4-1.log.gz Description: GNU Zip compressed data
Bug#700789: autoconf-archive: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Package: autoconf-archive Version: 20111221-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: squeeze -> wheezy For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase For switching from a symlink to a directory, the *preinst* script should do something like this: DOCDIR=/usr/share/doc/@@PACKAGE@@ if [ -L $DOCDIR ]; then rm $DOCDIR fi >From the attached log (usually somewhere in the middle...): 0m49.6s INFO: dirname part contains a symlink: /usr/share/doc/autoconf-archive/html/Downloads.html (autoconf-archive) != /usr/share/autoconf-archive/html/Downloads.html (?) /usr/share/doc/autoconf-archive/html/GNU-Free-Documentation-License.html (autoconf-archive) != /usr/share/autoconf-archive/html/GNU-Free-Documentation-License.html (?) /usr/share/doc/autoconf-archive/html/How-to-contribute.html (autoconf-archive) != /usr/share/autoconf-archive/html/How-to-contribute.html (?) /usr/share/doc/autoconf-archive/html/Introduction.html (autoconf-archive) != /usr/share/autoconf-archive/html/Introduction.html (?) /usr/share/doc/autoconf-archive/html/The-Macros.html (autoconf-archive) != /usr/share/autoconf-archive/html/The-Macros.html (?) /usr/share/doc/autoconf-archive/html/ax_005fabsolute_005fheader.html (autoconf-archive) != /usr/share/autoconf-archive/html/ax_005fabsolute_005fheader.html (?) /usr/share/doc/autoconf-archive/html/ax_005fac_005fappend_005fto_005ffile.html (autoconf-archive) != /usr/share/autoconf-archive/html/ax_005fac_005fappend_005fto_005ffile.html (?) /usr/share/doc/autoconf-archive/html/ax_005fac_005fprint_005fto_005ffile.html (autoconf-archive) != /usr/share/autoconf-archive/html/ax_005fac_005fprint_005fto_005ffile.html (?) /usr/share/doc/autoconf-archive/html/ax_005fadd_005fam_005fmacro.html (autoconf-archive) != /usr/share/autoconf-archive/html/ax_005fadd_005fam_005fmacro.html (?) /usr/share/doc/autoconf-archive/html/ax_005fadd_005fam_005fmacro_005fstatic.html (autoconf-archive) != /usr/share/autoconf-archive/html/ax_005fadd_005fam_005fmacro_005fstatic.html (?) /usr/share/doc/autoconf-archive/html/ax_005fadd_005fam_005ftrilinos_005fmakefile_005fexport.html (autoconf-archive) != /usr/share/autoconf-archive/html/ax_005fadd_005fam_005ftrilinos_005fmakefile_005fexport.html (?) /usr/share/doc/autoconf-archive/html/ax_005fadd_005frecursive_005fam_005fmacro.html (autoconf-archive) != /usr/share/autoconf-archive/html/ax_005fadd_005frecursive_005fam_005fmacro.html (?) /usr/share/doc/autoconf-archive/html/ax_005fadd_005frecursive_005fam_005fmacro_005fstatic.html (autoconf-archive) != /usr/share/autoconf-archive/html/ax_005fadd_005frecursive_005fam_005fmacro_005fstatic.html (?) /usr/share/doc/autoconf-archive/html/ax_005fafs.html (autoconf-archive) != /usr/share/autoconf-archive/html/ax_005fafs.html (?) [...] I have no idea how to properly clean up currently messed up installations ... cheers, Andreas autoconf-archive_20111221-1.log.gz Description: GNU Zip compressed data
Bug#670942: Please, remove the FAQ
Hi Javier, > > Currently, the Securing Debian Manual [1] ships the security FAQ [2], > > duplicating an (outdated) information already available in 9 languages. > Hi. I think I implemented this already in SVN. I will check later tomorrow. It's currently still present in svn, so please remove it as it contains information that's currently false. I can also submit a patch to correct all false information, if removing the FAQ from the manual isn't an option in the short term. In any case I'd like to get this fixed soon. Thanks, Thijs signature.asc Description: This is a digitally signed message part.
Bug#700790: gtkmm-documentation: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Package: gtkmm-documentation Version: 3.4.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: squeeze -> wheezy For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase For switching from a symlink to a directory, the *preinst* script should do something like this: DOCDIR=/usr/share/doc/@@PACKAGE@@ if [ -L $DOCDIR ]; then rm $DOCDIR fi >From the attached log (usually somewhere in the middle...): 0m55.2s INFO: dirname part contains a symlink: /usr/share/doc/gtkmm-3.0/tutorial (gtkmm-documentation) != /usr/share/doc/libgtkmm-3.0-doc/tutorial (?) Hmm, looks like gtkmm-documentation installs something in the documentation directory of another package, but that has changed to a symlink inbetween ... cheers, Andreas gtkmm-documentation_3.4.0-1.log.gz Description: GNU Zip compressed data
Bug#476284: progress with bullet engine ?
at bottom :- On Sun, Feb 17, 2013 at 7:45 PM, Markus Koschany wrote: > On 17.02.2013 08:45, shirish शिरीष wrote: >> Hi Markus, >> Just wanted to know how closer you are to release bullet engine ? >> >> I did see you did some changes some days ago, looking forward to learn more. >> >> http://anonscm.debian.org/gitweb/?p=pkg-games/bullet.git;a=log;h=refs/heads/master >> >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476284 (for reference). >> >> Looking forward to know more from you. > > > Hi shirish, > > the greatest blocker is, there must be a need for the library. I will > talk to the maintainers of Blender and ask for their opinions. It > depends on their feedback whether it is really necessary to package all > extras or just the core of bullet. > > Otherwise i will check whether it is feasible to maintain FreeOrion, the > only other game at the moment which would benefit from Bullet. Of course > i also need a sponsor. > > The package is usable, please feel free to make use of it as you see fit. > > Regards, > > Markus Hi Markus, I could do that but am hoping we do get support. One of the games which I have wanted to try is lips of suna (http://lipsofsuna.org/) which as the site describes it a tongue-in-cheek dungeon crawling rpg but it also needs libbullet-dev to function. Looking forward to some progress on the above. Till l8er. -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700791: php-xml-serializer: unhandled symlink to directory conversion: /usr/share/php/tests/XML_Serializer/tests
Package: php-xml-serializer Version: 0.20.2-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: squeeze -> wheezy For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase For switching from a symlink to a directory, the *preinst* script should do something like this: DOCDIR=/usr/share/doc/@@PACKAGE@@ if [ -L $DOCDIR ]; then rm $DOCDIR fi >From the attached log (usually somewhere in the middle...): 0m48.0s INFO: dirname part contains a symlink: /usr/share/php/tests/XML_Serializer/tests/AllTests.php (php-xml-serializer) != /usr/share/doc/php-xml-serializer/tests/AllTests.php (?) /usr/share/php/tests/XML_Serializer/tests/Serializer_Arrays_TestCase.php (php-xml-serializer) != /usr/share/doc/php-xml-serializer/tests/Serializer_Arrays_TestCase.php (?) /usr/share/php/tests/XML_Serializer/tests/Serializer_Objects_TestCase.php (php-xml-serializer) != /usr/share/doc/php-xml-serializer/tests/Serializer_Objects_TestCase.php (?) /usr/share/php/tests/XML_Serializer/tests/Serializer_Option_AttributesContent_TestCase.php (php-xml-serializer) != /usr/share/doc/php-xml-serializer/tests/Serializer_Option_AttributesContent_TestCase.php (?) /usr/share/php/tests/XML_Serializer/tests/Serializer_Option_CDataSections_TestCase.php (php-xml-serializer) != /usr/share/doc/php-xml-serializer/tests/Serializer_Option_CDataSections_TestCase.php (?) /usr/share/php/tests/XML_Serializer/tests/Serializer_Option_ClassName_TestCase.php (php-xml-serializer) != /usr/share/doc/php-xml-serializer/tests/Serializer_Option_ClassName_TestCase.php (?) /usr/share/php/tests/XML_Serializer/tests/Serializer_Option_Comment_TestCase.php (php-xml-serializer) != /usr/share/doc/php-xml-serializer/tests/Serializer_Option_Comment_TestCase.php (?) /usr/share/php/tests/XML_Serializer/tests/Serializer_Option_DefaultTag_TestCase.php (php-xml-serializer) != /usr/share/doc/php-xml-serializer/tests/Serializer_Option_DefaultTag_TestCase.php (?) /usr/share/php/tests/XML_Serializer/tests/Serializer_Option_DocType_TestCase.php (php-xml-serializer) != /usr/share/doc/php-xml-serializer/tests/Serializer_Option_DocType_TestCase.php (?) /usr/share/php/tests/XML_Serializer/tests/Serializer_Option_EncodeFunc_TestCase.php (php-xml-serializer) != /usr/share/doc/php-xml-serializer/tests/Serializer_Option_EncodeFunc_TestCase.php (?) /usr/share/php/tests/XML_Serializer/tests/Serializer_Option_IgnoreNull_TestCase.php (php-xml-serializer) != /usr/share/doc/php-xml-serializer/tests/Serializer_Option_IgnoreNull_TestCase.php (?) /usr/share/php/tests/XML_Serializer/tests/Serializer_Option_Indent_TestCase.php (php-xml-serializer) != /usr/share/doc/php-xml-serializer/tests/Serializer_Option_Indent_TestCase.php (?) /usr/share/php/tests/XML_Serializer/tests/Serializer_Option_Linebreaks_TestCase.php (php-xml-serializer) != /usr/share/doc/php-xml-serializer/tests/Serializer_Option_Linebreaks_TestCase.php (?) /usr/share/php/tests/XML_Serializer/tests/Serializer_Option_Mode_TestCase.php (php-xml-serializer) != /usr/share/doc/php-xml-serializer/tests/Serializer_Option_Mode_TestCase.php (?) /usr/share/php/tests/XML_Serializer/tests/Serializer_Option_Namespace_TestCase.php (php-xml-serializer) != /usr/share/doc/php-xml-serializer/tests/Serializer_Option_Namespace_TestCase.php (?) /usr/share/php/tests/XML_Serializer/tests/Serializer_Option_ReturnResult_TestCase.php (php-xml-serializer) != /usr/share/doc/php-xml-serializer/tests/Serializer_Option_ReturnResult_TestCase.php (?) /usr/share/php/tests/XML_Serializer/tests/Serializer_Option_RootAttributes_TestCase.php (php-xml-serializer) != /usr/share/doc/php-xml-serializer/tests/Serializer_Option_RootAttributes_TestCase.php (?) /usr/share/php/tests/XML_Serializer/tests/Serializer_Option_RootName_TestCase.php (php-xml-serializer) != /us
Bug#700792: libavifile-0.7-dev: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Package: libavifile-0.7-dev Version: 1:0.7.48~20090503.ds-12 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: squeeze -> wheezy For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase For switching from a symlink to a directory, the *preinst* script should do something like this: DOCDIR=/usr/share/doc/@@PACKAGE@@ if [ -L $DOCDIR ]; then rm $DOCDIR fi >From the attached log (usually somewhere in the middle...): 0m52.8s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/libavifile-0.7-dev/changelog.Debian.gz (libavifile-0.7-dev) != /usr/share/doc/libavifile-0.7c2/changelog.Debian.gz (libavifile-0.7c2:amd64) /usr/share/doc/libavifile-0.7-dev/changelog.gz (libavifile-0.7-dev) != /usr/share/doc/libavifile-0.7c2/changelog.gz (libavifile-0.7c2:amd64) /usr/share/doc/libavifile-0.7-dev/copyright (libavifile-0.7-dev) != /usr/share/doc/libavifile-0.7c2/copyright (libavifile-0.7c2:amd64) cheers, Andreas libavifile-0.7-dev_1:0.7.48~20090503.ds-12.log.gz Description: GNU Zip compressed data
Bug#697970: cups: printing gets wrong after some pages on Epson Stylus Photo 750
Hi OdyX Le 15/02/2013 09:14, Didier 'OdyX' Raboud a écrit : Control: reopen -1 Control: found -1 1.6.1-2 Le vendredi, 15 février 2013 08.53:10, Denis Prost a écrit : I was just facing the problem when you wrote to me ! I don't know why it appeared again, maybe the lpadmin settings above where lost for some reason. Anyway it let me try the new experimental cups release and notice that it did not solve the problem. I reapplied the lpadmin commands above and the problem was gone. Re-opening this bug then. Damn… Cheers, OdyX I faced the problem again today with the experimental package and, this time, reapplying : lpadmin -p Epson_Stylus_Photo_750 -R usb-unidir-default lpadmin -p Epson_Stylus_Photo_750 -o usb-no-reattach-default=true did not solve it. So I tried lpadmin -p Epson_Stylus_Photo_750 -R usb-no-reattach-default and it worked ! But this behaviour is so strange that I'm not sure the problem won't reappear. So I suggest to keep the bug open and I'll let you know if it appears again. Regards, Denis
Bug#700649: Please update libeatmydata
Hello, On Friday 15 February 2013 14:49:39 Phillip Susi wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Package: libeatmydata > > It has been two years since this package has been updated, and > upstream has had several releases. Please package the new release. I will do best but IMHO back in 28 upstream went the wrong way with complicating the build of a single *.c file with hundreds of build system support files (iirc, pandora-build) which afaik, require python for any more serious modification (!). At one point I even tried to fork build system stuff but obviously ran out of steam with this effort. Anyway, I will have a look at new upsteam as-it-is again but with fresh mind this time. Hopefully, it is going to work out better now. signature.asc Description: This is a digitally signed message part.
Bug#700482: [Pkg-utopia-maintainers] Bug#700482: network-manager: NetworkManager lists several Mobile Broadband connections
On Wed, Feb 13, 2013 at 09:26:18AM +0100, Michael Biebl wrote: > can you run a diff on those different connection files in > /etc/NetworkManager/system-connections to see in what aspect hey are > defferent. I have run diffs. There is one connection named by its own name and then several others with the same name and the uuid appended. I have joined you a diff file. Most of the time it occurs after the laptop has rebooted. When it comes back from suspend, it has lost the connections and I have to go through the wizard again. Cheers, --- Bouygues Telecom Contrat Pro Data Illimité 2012-12-28 16:36:31.415789907 +0100 +++ Bouygues Telecom Contrat Pro Data Illimité-1dc9669d-3f39-433f-abfb-59cd3f371038 2013-02-15 18:08:30.343336376 +0100 @@ -1,20 +1,21 @@ [connection] id=Bouygues Telecom Contrat Pro Data Illimité -uuid=8c351354-555d-4312-a46a-616c388ba2a2 +uuid=1dc9669d-3f39-433f-abfb-59cd3f371038 type=gsm +permissions=user:julien:; autoconnect=false +[gsm] +number=*99# +password-flags=1 +apn=a2bouygtel.com + [ppp] lcp-echo-failure=5 lcp-echo-interval=30 -[ipv4] -method=auto - [serial] baud=115200 -[gsm] -number=*99# -apn=a2bouygtel.com -pin= +[ipv4] +method=auto signature.asc Description: Digital signature
Bug#699586: closed by vin...@gmail.com (Vincent W. Chen) (Bug#699586: fixed in fvwm 1:2.6.5.ds-2)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/17/13 00:38, Vincent W. Chen wrote: > > When you say "rebuilding fvwm without deprecated.patch", what steps did you > take? Since the patches are the same, it means that when you tested the new > patch with the previous version (1:2.6.5.ds-1), the bug wasn't fixed. I'd > like to know how you go about rebuilding fvwm. > Using your new patch I had created a new source package (I edited patch/series to kick out "deprecated.patch" and to append "deprecated.new.patch"). Looking at "quilt push -a" I verified that the new patch is in. The binary package was built using pbuilder. I still have the source and binary packages of the test build. If I install the test binary today, then the problem is still in, so I would guess I had made a mistake at install time. Please accept my apologies. Of course I still would be glad if I could help to get this problem fixed. Regards Harri -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlEg8egACgkQUTlbRTxpHjcDqQCfTCJZQ/KHJ97BrWVe/xK2iRlU BF8Aniv1oEfaR/kgchNDiBpnwn6xpLTk =xh9a -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#700793: [sweethome3d] stair design
Package: sweethome3d Version: 3.7+dfsg-2 Severity: wishlist Hi, A stair is very important to design the interior of a house. Unfortunately, sweethome3d is very limited on stairs. There is only a few models available. For instance stairs like these are not available, but very common in real houses : http://www.lapeyre.fr/amenagements/escaliers/droits-et-quart-tournant/bois-exotique/escalier-1-qt-maestro-tauari-h-275-cm-ri-291-cm.html http://www.lapeyre.fr/amenagements/escaliers/droits-et-quart-tournant/bois-exotique/escalier-1-qt-tenor-tauari-h-275-cm-rd-279-cm.html It could be very interesting to have a way to define stairs in sweethome3D : quart-tournant haut ou bas, trois quart tournant, colimaçon (sorry I don't know the english words, just the french…). Another way could be to have more stair models, especially the very common ones. Adrien --- System information. --- Architecture: amd64 Kernel: Linux 3.7-trunk-amd64 Debian Release: 7.0 900 testing security.debian.org 900 testing ftp.fr.debian.org 800 unstableftp.fr.debian.org 700 experimentalftp.fr.debian.org 100 experimental-snapshots qt-kde.debian.net --- Package information. --- Depends(Version) | Installed -+-== icedtea-netx-common | 1.3.1-2 OR sun-java6-bin| java-wrappers| 0.1.25 java3ds-fileloader | 1.2+dfsg-1 libfreehep-graphicsio-svg-java | 2.1.1-3 libitext-java| 2.1.7-3+deb7u1 libjava3d-java | 1.5.2+dfsg-8 libsunflow-java(>= 0.07.2.svn396+dfsg-9) | 0.07.2.svn396+dfsg-9 libbatik-java| 1.7+dfsg-3 default-jre | 1:1.6-47 OR java6-runtime| Recommends (Version) | Installed -+-=== sweethome3d-furniture| 1.2.1-1 Package's Suggests field is empty. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700794: CVE-2012-6128: stack-based buffer overflow in OpenConnect
Package: openconnect Version: 3.20-2 Severity: critical CVE-2012-6128 concerns a stack-based buffer overflow that can be triggered by data read from a remote host, either a man-in-the-middle or a malicious VPN. The issue has been fixed in squeeze with 2.25-0.1+squeeze2. It should be easy to apply the same patch to 3.20 to fix this in wheezy and sid. I have recently uploaded 4.99-1 to experimental which already contains the fix upstream. -- mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700482: [Pkg-utopia-maintainers] Bug#700482: Bug#700482: network-manager: NetworkManager lists several Mobile Broadband connections
On 17.02.2013 15:53, Julien Patriarca wrote: > On Wed, Feb 13, 2013 at 09:26:18AM +0100, Michael Biebl wrote: >> can you run a diff on those different connection files in >> /etc/NetworkManager/system-connections to see in what aspect hey are >> defferent. > > I have run diffs. There is one connection named by its own name and then > several others with the same name and the uuid appended. > I have joined you a diff file. > Most of the time it occurs after the laptop has rebooted. When it comes > back from suspend, it has lost the connections and I have to go through > the wizard again. NM should not automatically create any new connections. But as you said, after resume, you have to go through the wizard again, to create a new connection. That's most likely where your duplicates come from. I suspect, that after resume, your device is not properly initialized and the wizard somehow triggers that. Could you remove all duplicate connection files, create a fresh one, then after resume, when the connection is not shown, rmmod the driver and modprobe it again. If that doesn't help restart NM 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#700795: webkit: FTBFS on x32: Tries and fails to build x86_64 JIT compiler
Source: webkit Version: 1.8.1-3.3 Severity: wishlist Tags: patch User: debian-...@lists.debian.org Usertags: port-x32 ftbfs-x32 The webkit source package is getting this build failure on the unofficial Debian x32 port: http://buildd.debian-ports.org/status/fetch.php?pkg=webkit&arch=x32&ver=1.8.1-3.3&stamp=1360860558>: ... ./doltlibtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. -DBUILDING_WEBKIT -DPACKAGE_LOCALE_DIR=\"/usr/share/locale\" -DDATA_DIR=\"/usr/share\" -I../Source/WebCore/bindings -I../Source/WebCore/bindings/gobject -I../Source/WebKit/gtk -I../Source/WebKit/gtk/WebCoreSupport -I../Source/WebKit/gtk/webkit -I./DerivedSources/webkit -ISource/WebKit/gtk/webkit -Wall -W -Wcast-align -Wchar-subscripts -Wreturn-type -Wformat -Wformat-security -Wno-format-y2k -Wundef -Wmissing-format-attribute -Wpointer-arith -Wwrite-strings -Wno-unused-parameter -Wno-parentheses -fno-exceptions -DENABLE_GLIB_SUPPORT=1 -DBUILDING_CAIRO__=1 -DBUILDING_GTK__=1 -DWTF_CHANGES -DXP_UNIX -DWTF_USE_ICU_UNICODE=1 -DWTF_USE_GSTREAMER=1 -DGTK_API_VERSION_2=1 -DNDEBUG -I../Source/ThirdParty/ANGLE/src -I../Source/ThirdParty/ANGLE/include -I../Source/ThirdParty/ANGLE/include/GLSLANG -I../Source/WebCore -I../Source/WebCore/accessibility -I../Source/WebCore/bindings -I../Source/WebCore/bindings/generic -I../Source/WebCore/bindings/js -I../Source/WebCore/bindings/js/specialization -I../Source/WebCore/bridge -I../Source/WebCore/bridge/c -I../Source/WebCore/bridge/jni/jsc -I../Source/WebCore/bridge/jsc -I../Source/WebCore/css -I../Source/WebCore/dom -I../Source/WebCore/dom/default -I../Source/WebCore/editing -I../Source/WebCore/fileapi -I../Source/WebCore/history -I../Source/WebCore/html -I../Source/WebCore/html/canvas -I../Source/WebCore/html/parser -I../Source/WebCore/html/shadow -I../Source/WebCore/html/track -I../Source/WebCore/inspector -I../Source/WebCore/loader -I../Source/WebCore/loader/appcache -I../Source/WebCore/loader/archive -I../Source/WebCore/loader/cache -I../Source/WebCore/loader/icon -I../Source/WebCore/mathml -I../Source/WebCore/mediastream -I../Source/WebCore/notifications -I../Source/WebCore/page -I../Source/WebCore/page/animation -I../Source/WebCore/page/scrolling -I../Source/WebCore/platform -I../Source/WebCore/platform/animation -I../Source/WebCore/platform/audio -I../Source/WebCore/platform/graphics -I../Source/WebCore/platform/graphics/filters -I../Source/WebCore/platform/graphics/filters/arm -I../Source/WebCore/platform/graphics/gpu -I../Source/WebCore/platform/graphics/opengl -I../Source/WebCore/platform/graphics/opentype -I../Source/WebCore/platform/graphics/transforms -I../Source/WebCore/platform/image-decoders -I../Source/WebCore/platform/image-decoders/bmp -I../Source/WebCore/platform/image-decoders/gif -I../Source/WebCore/platform/image-decoders/ico -I../Source/WebCore/platform/image-decoders/jpeg -I../Source/WebCore/platform/image-decoders/webp -I../Source/WebCore/platform/image-decoders/png -I../Source/WebCore/platform/leveldb -I../Source/WebCore/platform/mediastream -I../Source/WebCore/platform/mock -I../Source/WebCore/platform/network -I../Source/WebCore/platform/sql -I../Source/WebCore/platform/text -I../Source/WebCore/platform/text/transcoder -I../Source/WebCore/platform/win -I../Source/WebCore/plugins -I../Source/WebCore/plugins/win -I../Source/WebCore/rendering -I../Source/WebCore/rendering/mathml -I../Source/WebCore/rendering/style -I../Source/WebCore/rendering/svg -I../Source/WebCore/storage -I../Source/WebCore/svg -I../Source/WebCore/svg/animation -I../Source/WebCore/svg/graphics -I../Source/WebCore/svg/graphics/filters -I../Source/WebCore/svg/properties -I../Source/WebCore/testing -I../Source/WebCore/testing/js -I../Source/WebCore/webaudio -I../Source/WebCore/websockets -I../Source/WebCore/workers -I../Source/WebCore/xml -I../Source/WebCore/xml/parser -I./WebCore/bindings/js -I./DerivedSources/WebCore -I./DerivedSources -I./DerivedSources/JavaScriptCore -DDATA_DIR=\"/usr/share\" -DENABLE_CHANNEL_MESSAGING=1 -DENABLE_METER_TAG=1 -DENABLE_PROGRESS_TAG=1 -DENABLE_JAVASCRIPT_DEBUGGER=1 -DENABLE_GAMEPAD=0 -DENABLE_SQL_DATABASE=1 -DENABLE_DATALIST=1 -DENABLE_DIRECTORY_UPLOAD=0 -DENABLE_TOUCH_ICON_LOADING=0 -DENABLE_INPUT_COLOR=0 -DENABLE_INPUT_SPEECH=0 -DENABLE_ICONDATABASE=1 -DENABLE_VIDEO=1 -DENABLE_MEDIA_SOURCE=0 -DENABLE_MEDIA_STATISTICS=0 -DENABLE_FULLSCREEN_API=1 -DENABLE_VIDEO_TRACK=0 -DENABLE_MEDIA_STREAM=0 -DENABLE_XSLT=1 -DENABLE_WORKERS=1 -DENABLE_SHADOW_DOM=1 -DENABLE_SHARED_WORKERS=1 -DENABLE_FILTERS=1 -DENABLE_GEOLOCATION=1 -DENABLE_CLIENT_BASED_GEOLOCATION=1 -DENABLE_MATHML=1 -DENABLE_SVG=1 -DENABLE_SVG_FONTS=1 -DENABLE_WEB_SOCKETS=1 -DENABLE_BLOB=1 -DENABLE_REQUEST_ANIMATION_FRAME=1 -DENABLE_WEBGL=1 -DWEBKITGTK_API_VERSION_STRING=\"1.0\" -DWTF_USE_SOUP=1 -I../Source/WebCore/accessibility/gtk -I../Source/WebCore/loader/gtk -I../Source/WebCore/page/gtk -I../Source/WebCore/platform/cairo -I../Source/WebCore/platform/audio/gstreamer -I../Source/We
Bug#700790: gtkmm-documentation: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
On 17.02.2013 15:26, Andreas Beckmann wrote: > Package: gtkmm-documentation > Version: 3.4.0-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > an upgrade test with piuparts revealed that your package installs files > over existing symlinks and possibly overwrites files owned by other > packages. This usually means an old version of the package shipped a > symlink but that was later replaced by a real (and non-empty) > directory. This kind of overwriting another package's files cannot be > detected by dpkg. > > This was observed on the following upgrade paths: > > squeeze -> wheezy > > For /usr/share/doc/PACKAGE this may not be problematic as long as both > packages are installed, ship byte-for-byte identical files and are > upgraded in lockstep. But once one of the involved packages gets > removed, the other one will lose its documentation files, too, > including the copyright file, which is a violation of Policy 12.5: > http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile > > For other overwritten locations anything interesting may happen. > > Note that dpkg intentionally does not replace directories with symlinks > and vice versa, you need the maintainer scripts to do this. > See in particular the end of point 4 in > http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase > > For switching from a symlink to a directory, the *preinst* script > should do something like this: > > DOCDIR=/usr/share/doc/@@PACKAGE@@ > > if [ -L $DOCDIR ]; then > rm $DOCDIR > fi > > >>From the attached log (usually somewhere in the middle...): > > 0m55.2s INFO: dirname part contains a symlink: > /usr/share/doc/gtkmm-3.0/tutorial (gtkmm-documentation) != > /usr/share/doc/libgtkmm-3.0-doc/tutorial (?) > > Hmm, looks like gtkmm-documentation installs something in the documentation > directory of another package, but that has changed to a symlink inbetween ... This symlink didn't exist in squeeze, so I'm unsure which directory was converted to a symlink At least /usr/share/doc/gtkmm-3.0/tutorial never existed as an actual directory afaics, or can you be move specific from which versions of which packages you upgraded. 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#700779: python-gobject-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
On 17.02.2013 14:44, Andreas Beckmann wrote: >>From the attached log (usually somewhere in the middle...): > > 0m58.6s ERROR: FAIL: silently overwrites files via directory symlinks: > /usr/share/doc/python-gobject-dbg/changelog.Debian.gz (python-gobject-dbg) > != /usr/share/doc/python-gobject/changelog.Debian.gz (python-gobject) > /usr/share/doc/python-gobject-dbg/changelog.gz (python-gobject-dbg) != > /usr/share/doc/python-gobject/changelog.gz (python-gobject) > /usr/share/doc/python-gobject-dbg/copyright (python-gobject-dbg) != > /usr/share/doc/python-gobject/copyright (python-gobject) Argh, those damn doc symlinks, I know why I hate them. In squeeze, python-gobject-dbg was an actual package where /usr/share/doc/python-gobject-dbg/ was symlinked to /usr/share/doc/python-gobject/ In squeeze that symlink dance was updated for the new binary package name: The relevant bits from squeeze's debian/rules: rm -rf debian/python-gobject-dbg/usr/share/doc/python-gobject-dbg ln -sf python-gobject debian/python-gobject-dbg/usr/share/doc/python-gobject-dbg This was changed to rm -rf debian/python-gi-dbg/usr/share/doc/python-gi-dbg ln -sf python-gi debian/python-gi-dbg/usr/share/doc/python-gi-dbg python-gobject-dbg is now a transitional package only which pulls in python-gi-dbg and python-gobject-2-dbg. Let's drop those stupid doc symlinks altogether. 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#700798: unblock: live-tools/3.0.18-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package live-tools
The version in wheezy had some issues (see #685752 which this request
supercedes and I will now close) with upgradability that, while not
typical use cases (live-tools would normally only be installed on a live
system and subsequently not upgraded) were nevertheless show-stoppers
for the wheezy release. Those issues have have since been resolved. We
consider this release to be the only supportable version for the
lifetime of wheezy.
I have attached a cleaned up diff which lists at the top the specific
cleanups performed to make review easier.
unblock live-tools/3.0.18-1
-- System Information:
Debian Release: 7.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.7-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
This is a diff 3.0.3-1..3.0.18-1:
* without manpage translation changes
* with filenames adjusted to account for file renames providing a minimal diff
diff -Naurp live-tools.orig/bin/live-persistence live-tools/bin/live-persistence
--- live-tools.orig/bin/live-persistence 1970-01-01 01:00:00.0 +0100
+++ live-tools/bin/live-persistence 2013-02-15 10:42:34.619868805 +0100
@@ -0,0 +1,482 @@
+#!/bin/sh
+
+## live-tools(7) - System Support Scripts
+##
+## This program comes with ABSOLUTELY NO WARRANTY; for details see COPYING.
+## This is free software, and you are welcome to redistribute it
+## under certain conditions; see COPYING for details.
+
+
+set -e
+
+# We're gonna mess with stderr's file descriptor below, so we save a
+# reference to it in fd 3 if we want to print to stderr
+exec 3>&2
+
+error ()
+{
+ echo "error: ${@}" >&3
+ exit 1
+}
+
+# Exit if user is unprivileged
+if [ "$(id -u)" -ne 0 ]
+then
+ echo "E: need root privileges" >&3
+
+ exit 1
+fi
+
+# Exit if live-boot is not installed
+if [ ! -e /lib/live/boot ]
+then
+ echo "E: live-boot not installed" >&3
+
+ exit 1
+fi
+
+# import Cmdline_old()
+. /lib/live/boot/9990-cmdline-old || error 'Could not source /lib/live/boot/9990-cmdline-old'
+
+# Set variable names needed by get_custom_mounts() etc.,
+# and now initialized by live-boot in a file that we certainly
+# don't want to source.
+persistence_list="persistence.conf"
+old_persistence_list="live-persistence.conf"
+custom_overlay_label="persistence"
+export persistence_list old_persistence_list custom_overlay_label
+
+# This will import the following functions and variables used below:
+# activate_custom_mounts()
+# get_custom_mounts()
+# open_luks_device()
+# probe_for_gpt_name()
+# removable_dev()
+# removable_usb_dev()
+# storage_devices()
+# where_is_mounted()
+. /lib/live/boot/9990-misc-helpers.sh || error 'Could not source /lib/live/boot/9990-misc-helpers.sh'
+
+usage ()
+{
+ echo "Usage: live-persistence [OPTION]... list [LABEL]...
+List (on stdout) all partitions with names among LABEL(s) that are compatible
+with live-boot's overlay persistence, and that are adhering to live-boot's
+persistence filters (e.g. persistence-media). If no LABEL is given the default
+in live-boot is used ('${custom_overlay_label}').
+ or: live-persistence [OPTION]... activate VOLUME...
+Activates persistence on the given VOLUME(s) (specified via block device).
+Successes and failures are written to stdout. There are no checks for whether
+the given volumes adhere to live-boot's options.
+ or: live-persistence [OPTION]... close VOLUME...
+Deactivates persistence on the given VOLUME(s) (specified via block device).
+
+Note: The 'activate' and 'stop' actions only support partition-backed volumes
+(e.g. /dev/sda2), not file-backed persistent volumes.
+
+Kernel command-line options are parsed just like in live-boot and have the same
+effect (see live-boot(7) for more information).
+
+Most options correspond to the persistence-* options of live-boot, and will
+override the corresponging options parsed from the kernel command-line.
+
+General options:
+ -h, --helpdisplay this help and exit
+ -l, --log-file=FILE log the execution trace to FILE
+
+Options affecting the 'list' action:
+ -e, --encryption=LIST override 'persistence-encryption'
+ -m, --media=VALUE override 'persistence-media'
+ -g, --gpt-onlyonly list GPT partitions
+
+Options affecting the 'activate' action:
+ -r, --read-only enable 'persistence-read-only'
+ -w, --read-write disable 'persistence-read-only'
+ -u, --union=VALUE override 'union'"
+}
+
+warning ()
+{
+ echo "warning: ${@}" >&3
+}
+
+dbus_udisks_get_attribute ()
+{
+ dev="${1}"
+ attribute="${2}"
+ re='^[[:space:]]*variant[[:space:]]\+string[[:space:]]\+"\(.*\)"$'
+
+ dbus-send --system --print-reply --dest=org.freedesktop.UDisks \
+ /org/freedesktop/UDisks/devices/$(basename ${
Bug#700482: [Pkg-utopia-maintainers] Bug#700482: Bug#700482: network-manager: NetworkManager lists several Mobile Broadband connections
On Sun, Feb 17, 2013 at 04:53:04PM +0100, Michael Biebl wrote: > > I have run diffs. There is one connection named by its own name and then > > several others with the same name and the uuid appended. > > I have joined you a diff file. > > Most of the time it occurs after the laptop has rebooted. When it comes > > back from suspend, it has lost the connections and I have to go through > > the wizard again. > > NM should not automatically create any new connections. But as you said, > after resume, you have to go through the wizard again, to create a new > connection. That's most likely where your duplicates come from. > I suspect, that after resume, your device is not properly initialized > and the wizard somehow triggers that. > > Could you remove all duplicate connection files, create a fresh one, > then after resume, when the connection is not shown, rmmod the driver > and modprobe it again. If that doesn't help restart NM The rmmod and modprobe does nothing. But the restart of Network-Manager fixes it. Thanks ;-) signature.asc Description: Digital signature
Bug#698066: dot crash
I have also gotten a memory corruption with the given input file, and with
'digraph g {v [label="fmnosyy cemnnoopt definr\Einoprx\Eeionprssx aceert"]}'
as input. The directory names are sorted versions of those in N44 of the
original input, and the backslashes and newlines have been space-ified.
If I shorten this by one character I get an assertion error in malloc.c:3096.
If I remove one of the '\E's or replace it by anything else I've come up with
(trying '\e', 'ee', 'E' and 'EE' for a start), I get normal output.
If I run dot with -v, the crash happens right after
'loadimage : (lib) eps gd gd2 gif jpe jpeg jpg png ps svg'
though it is now a segfault rather than a memory corruption.
The same thing happens with neato, fdp, circo and twopi, also if I tweak the
output format parameter (tested: -Tpng, -Tsvg, -Tpdf). Perhaps that not
surprising, since that 'loadimage' comes before the layout algorithm begins in
the -v logorrhea ;-)
Looking at upstream (hg clone http://hg.research.att.com/graphviz), revision
9118 (most recent at the time of writing) didn't crash on the shrunk input,
nor the original.
8833 claims to have fixed a memory/free issue, but it didn't build for me. I
did a hg bisect -c 'make -j' which spat out rev 9084, "start 2.31 development
series". It compiled, and ran on the two input files without a hiccup.
I hope this helps figure out what's going on :-)
Cheerio,
JK
signature.asc
Description: Digital signature
Bug#699591: exim4 upload to stable (dovecot stability / and optionally spf quoting)
Hi, Apologies for the delay in getting back to you about this. On Sat, 2013-02-02 at 09:34 +0100, Andreas Metzler wrote: > | Dovecot: robustness; better msg on missing mech. [...] > This fixes an exim segfault when accessing a malicious dovecot AUTH > server. I have already talked with the security team, Moritz agrees > that this should be fixed in a point release. Testing already has the > fix since 4.80-6. The patch includes "TESTED: works against Dovecot 2.1.10", but stable has 1.2.15. Do we know if the patch has been tested against stable? > On top of this I would like to discuss whether it is acceptable to fix > http://bugs.debian.org/697057 in stable, too. [ I definitily want o > get the fix into testing - #697444.] The Debian configuration > optionally allows to use spfquery to run SPF-checks on incoming mail. > Due to insufficient quoting it is possible to pass on arbitrary > arguments to spfquery and therefore bypass SPF checks. The fix is not > invasive, but it changes dpkg conffiles. I've been arguing with myself a little over this one. Is it worth a comment preceding the new version of the changes to make it more obvious to anyone looking at the diff during an upgrade why the quoting was added? Presumably anyone performing a non-interactive upgrade won't get the changes, but that doesn't seem so bad in this case. 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#700801: cyrus-imapd-2.4: Cyrus imapd crashes when fetching message partrs
Package: cyrus-imapd-2.4 Version: 2.4.16-2 Severity: important Tags: upstream Dear Maintainer, When using cyrus imapd as a backend for Horde ActiveSync it crashes consistently. Doing queries like: UID FETCH 287574 (BINARY.PEEK[1] BINARY.SIZE[1]) consistently crashes Cyrus with the following messages in the logs: Jul 11 22:31:13 neo cyrus/master[23396]: process 10684 exited, signaled to death by 6 Jul 11 22:31:13 neo cyrus/master[23396]: service imap pid 10684 in BUSY state: terminated abnormally This bug is filed with the cyrus team and fixed in 2.4.17 already. Would be great to get this backported to Debian (or the package upgraded) https://bugzilla.cyrusimap.org/show_bug.cgi?id=3718 -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages cyrus-imapd-2.4 depends on: ii cyrus-common-2.4 2.4.16-2 ii libc6 2.13-35 ii libcomerr21.42.5-1 ii libdb5.1 5.1.29-5 ii libsasl2-22.1.25.dfsg1-5 ii libssl1.0.0 1.0.1c-4 ii libwrap0 7.6.q-24 ii zlib1g1:1.2.7.dfsg-13 cyrus-imapd-2.4 recommends no packages. cyrus-imapd-2.4 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#700801: cyrus-imapd-2.4: Cyrus imapd crashes when fetching message partrs
I think this can be included in wheezy update since it's a remote crasher. I will update the package during next week. Thanks for reporting, Ondrej On Sun, Feb 17, 2013 at 5:36 PM, Richard Braun wrote: > Package: cyrus-imapd-2.4 > Version: 2.4.16-2 > Severity: important > Tags: upstream > > Dear Maintainer, > When using cyrus imapd as a backend for Horde ActiveSync it crashes > consistently. > Doing queries like: > > UID FETCH 287574 (BINARY.PEEK[1] BINARY.SIZE[1]) > > consistently crashes Cyrus with the following messages in the logs: > > Jul 11 22:31:13 neo cyrus/master[23396]: process 10684 exited, signaled to > death by 6 > Jul 11 22:31:13 neo cyrus/master[23396]: service imap pid 10684 in BUSY state: > terminated abnormally > > This bug is filed with the cyrus team and fixed in 2.4.17 already. Would be > great to get this backported to Debian (or the package upgraded) > https://bugzilla.cyrusimap.org/show_bug.cgi?id=3718 > > > > > -- System Information: > Debian Release: 7.0 > APT prefers testing > APT policy: (500, 'testing') > Architecture: amd64 (x86_64) > > Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > > Versions of packages cyrus-imapd-2.4 depends on: > ii cyrus-common-2.4 2.4.16-2 > ii libc6 2.13-35 > ii libcomerr21.42.5-1 > ii libdb5.1 5.1.29-5 > ii libsasl2-22.1.25.dfsg1-5 > ii libssl1.0.0 1.0.1c-4 > ii libwrap0 7.6.q-24 > ii zlib1g1:1.2.7.dfsg-13 > > cyrus-imapd-2.4 recommends no packages. > > cyrus-imapd-2.4 suggests no packages. > > -- no debconf information > > ___ > Pkg-Cyrus-imapd-Debian-devel mailing list > pkg-cyrus-imapd-debian-de...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-cyrus-imapd-debian-devel -- Ondřej Surý -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#683360: [Pkg-xfce-devel] Bug#683360: xfce4 4.10/experimental, metapackages depends on unavailable packages
Control: reopen -1 Hi Yves-Alexis, On Thu, Sep 20, 2012 at 07:46:51PM +0200, Yves-Alexis Perez wrote: > On jeu., 2012-09-20 at 11:19 +0200, Thomas Martitz wrote: > > How is this not fixed yet? It means xfce 4.10 cannot be installed, and > > thus cannot receive proper testing. > > Actually it's fixed. I don't see any fix for this in the archive. This is still present in experimental. I ran into that today and was very surprised to find this issue as archived and hence morenot present on http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=xfce4 (I hence unarchived it and am herewith reopening this issue.) Could you please explain what you mean with "Actually it's fixed" (or where the fix should be available)? Regards, Axel -- ,''`. | Axel Beckert , http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#698837: Bug#695774 cloned and reopened to #698837
severity 698837 important thanks On 05/02/2013 11:39, Thorsten Glaser wrote: > If the steps (install redmine and redmine-pgsql but > not postgresql server, say yes to configure the DB, > then it fails, then install postgresql and let redmine > configure the DB, then upgrade redmine) work for you, > I guess the issue is closed. I'd rather lower severity for now, because i really do not reproduce the bug with this scenario, and keep it open for a while. Jérémy. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700802: awesome: Uninstallable on sid (depends on unavailable libc6 version)
Package: awesome Version: 3.4.15-1 Severity: serious Hi! The new version 3.4.15-1 has a depends on libc6 (>= 2.14) We have libc6 2.13-38 on sid and 2.17-0experimental2 on experimental (thus making it uninstallable on sid as it is now). binNMU? Thank you! Best regards, Nelson -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.7-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages awesome depends on: ii dbus-x11 1.6.8-1 ii libc6 2.13-38 ii libcairo2 1.12.2-3 ii libdbus-1-3 1.6.8-1 ii libev41:4.11-1 ii libglib2.0-0 2.33.12+really2.32.4-5 ii libimlib2 1.4.5-1 ii liblua5.1-0 5.1.5-4 ii libpango1.0-0 1.30.0-1 ii libstartup-notification0 0.12-1 ii libx11-6 2:1.5.0-1 ii libx11-xcb1 2:1.5.0-1 ii libxcb-icccm4 0.3.9-2 ii libxcb-image0 0.3.9-1 ii libxcb-keysyms1 0.3.9-1 ii libxcb-randr0 1.8.1-2 ii libxcb-render01.8.1-2 ii libxcb-shape0 1.8.1-2 ii libxcb-shm0 1.8.1-2 ii libxcb-util0 0.3.8-2 ii libxcb-xinerama0 1.8.1-2 ii libxcb-xtest0 1.8.1-2 ii libxcb1 1.8.1-2 ii libxcursor1 1:1.1.13-1 ii libxdg-basedir1 1.1.1-2 ii menu 2.1.46 Versions of packages awesome recommends: ii feh2.6.3-1 pn rlwrap ii x11-xserver-utils 7.7~3 awesome 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#700801: cyrus-imapd-2.4: Cyrus imapd crashes when fetching message partrs
On Sun, Feb 17, 2013 at 2:01 PM, Ondřej Surý wrote: > I think this can be included in wheezy update since it's a remote > crasher. I will update the package during next week. > > Thanks for reporting, > Ondrej Please if at all possible also fix #675812 (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675812) It isn't of remote crash severity but trivial to confirm and fix. Thanks! -- Ramiro Morales @ramiromorales -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700803: awesome: package released to unstable but depends on libraries in experimental
Package: awesome Version: 3.4.15-1 Severity: grave Justification: renders package unusable awesome 3.4.15-1 is released to unstable but depends on libc6 (>= 2.14) only available in experimental. - Jonas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700804: Audacious fails to play files if caharacter encoding is not recognised
Package: audacious Version: 3.2.4-1 Hi, Audacious 3.4.2-1 currently in testing (?) fails to open files if it does not recognise the character encoding with error message "Cannot convert filename to system locale". This works with 2.3-2 and with the original XMMS (!). I know the character encoding the file names use is not utf8 (it's latin1) but I don't think that should be a reason to refuse playing them. -- Kind regards, Sakari Ailus sakari.ai...@iki.fi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#683360: [Pkg-xfce-devel] Bug#683360: Bug#683360: xfce4 4.10/experimental, metapackages depends on unavailable packages
On dim., 2013-02-17 at 18:05 +0100, Axel Beckert wrote: > Control: reopen -1 > > Hi Yves-Alexis, > > On Thu, Sep 20, 2012 at 07:46:51PM +0200, Yves-Alexis Perez wrote: > > On jeu., 2012-09-20 at 11:19 +0200, Thomas Martitz wrote: > > > How is this not fixed yet? It means xfce 4.10 cannot be installed, and > > > thus cannot receive proper testing. > > > > Actually it's fixed. > > I don't see any fix for this in the archive. This is still present in > experimental. I ran into that today and was very surprised to find > this issue as archived and hence morenot present on > http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=xfce4 (I hence > unarchived it and am herewith reopening this issue.) > > Could you please explain what you mean with "Actually it's fixed" (or > where the fix should be available)? Could you start by explaining which packages you can't install on which architecture? -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#700805: openconnect: Fix for CVE-2012-6128 causes memory leak on error
Package: openconnect
Version: 3.20-3
Severity: normal
++
++static void buf_append(struct oc_text_buf *buf, const char *fmt, ...)
++{
++ va_list ap;
[...]
++
++ buf->data = realloc(buf->data, new_buf_len);
^
++ if (!buf->data) {
++ buf->error = -ENOMEM;
++ break;
++ }
++ buf->buf_len = new_buf_len;
If realloc fails, it will return NULL but without freeing the original
buffer. This means the marked code will leak the (old) buf->data on
error.
~Niels
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#683360: [Pkg-xfce-devel] Bug#683360: Bug#683360: xfce4 4.10/experimental, metapackages depends on unavailable packages
Yves-Alexis Perez wrote: > > Could you please explain what you mean with "Actually it's fixed" (or > > where the fix should be available)? > > Could you start by explaining which packages you can't install on which Same issue as reported by the original reporter: xfce4 in Experimental depends on orage and on xfce4-panel (>= 4.10.0), but orage from Sid depends on xfce4-panel (<< 4.9). And since there's no orage from Experimental, xfce4 from Experimental is uninstallable due to insatisfiable dependencies. I can reproduce it on amd64 (as with the original reporter) as well as on i386 (where I ran into it first). Regards, Axel -- ,''`. | Axel Beckert , http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#581999: still occurs, reopening
reopen 581999 found 581999 rinputd/1.0.5-2 thanks Hi, I can still reproduce this problem. During installation: Extracting templates from packages: 100% Preconfiguring packages ... /tmp/rinputd.config.92027: 5: [: =: unexpected operator Configuring rinputd --- Invalid username or password Neither the remote input username nor the password can be empty. Please correct them. Invalid username or password Neither the remote input username nor the password can be empty. Please correct them. Invalid username or password Neither the remote input username nor the password can be empty. Please correct them. Invalid username or password [...] line 5 is: [ `echo $DEBIAN_FRONTEND | tr '[:upper:]' '[:lower:]'` = "noninteractive" ] && exit 0 DEBIAN_FRONTEND is not set. However, # debconf-show debconf says: debconf-apt-progress/preparing: debconf-apt-progress/info: * debconf/frontend: Noninteractive * debconf/priority: critical debconf-apt-progress/media-change: debconf-apt-progress/title Lucas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700806: unblock: openconnect/3.20-3 (Fixes CVE-2012-6128)
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Dear Release Team,
Please unblock package openconnect, version 3.20-3 already uploaded to
unstable. This upload fixes RC bug #700794 (CVE-2012-6128), a
stack-based buffer overflow vulnerability.
The fix was made upstream and this change is a backport of that patch to
version 3.20. The debdiff is included below. Thanks in advance.
diffstat for openconnect-3.20 openconnect-3.20
changelog |7 +
patches/02_CVE-2012-6128.patch | 281 +
patches/series |1
3 files changed, 289 insertions(+)
diff -Nru openconnect-3.20/debian/changelog openconnect-3.20/debian/changelog
--- openconnect-3.20/debian/changelog 2012-06-06 08:54:48.0 -0400
+++ openconnect-3.20/debian/changelog 2013-02-17 12:25:52.0 -0500
@@ -1,3 +1,10 @@
+openconnect (3.20-3) unstable; urgency=low
+
+ * debian/patches/02_CVE-2012-6128.patch: Backport patch from upstream to fix
+buffer overflow (CVE-2012-6128). (Closes: #700794)
+
+ -- Mike Miller Sun, 17 Feb 2013 11:56:35 -0500
+
openconnect (3.20-2) unstable; urgency=low
* Depend on vpnc-scripts for routing and DNS configuration. (Closes:
diff -Nru openconnect-3.20/debian/patches/02_CVE-2012-6128.patch
openconnect-3.20/debian/patches/02_CVE-2012-6128.patch
--- openconnect-3.20/debian/patches/02_CVE-2012-6128.patch 1969-12-31
19:00:00.0 -0500
+++ openconnect-3.20/debian/patches/02_CVE-2012-6128.patch 2013-02-17
12:25:52.0 -0500
@@ -0,0 +1,281 @@
+Origin: upstream,
http://git.infradead.org/users/dwmw2/openconnect.git/commitdiff/26f752c3dbf69227679fc6bebb4ae071aecec491
+From: Kevin Cernekee
+Subject: http: Fix overflow on HTTP request buffers
+
+A malicious VPN gateway can send a very long hostname/path (for redirects)
+or cookie list (in general), which OpenConnect will attempt to sprintf()
+into a fixed length buffer. Each HTTP server response line can add
+roughly MAX_BUF_LEN (131072) bytes to the next OpenConnect HTTP request,
+but the request buffer (buf) is capped at MAX_BUF_LEN bytes and is
+allocated on the stack.
+
+The result of passing a long "Location:" header looks like:
+
+Attempting to connect to server 127.0.0.1:443
+SSL negotiation with localhost
+Server certificate verify failed: self signed certificate in certificate
chain
+Connected to HTTPS on localhost
+GET https://localhost/
+Got HTTP response: HTTP/1.0 301 Moved
+Ignoring unknown HTTP response line 'aa'
+SSL negotiation with localhost
+Server certificate verify failed: self signed certificate in certificate
chain
+Connected to HTTPS on localhost
+*** buffer overflow detected ***: /scr/openconnect2/.libs/lt-openconnect
terminated
+=== Backtrace: =
+/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x5c)[0x7fd62729b82c]
+/lib/x86_64-linux-gnu/libc.so.6(+0x109700)[0x7fd62729a700]
+/lib/x86_64-linux-gnu/libc.so.6(+0x108b69)[0x7fd627299b69]
+/lib/x86_64-linux-gnu/libc.so.6(_IO_default_xsputn+0xdd)[0x7fd62720d13d]
+/lib/x86_64-linux-gnu/libc.so.6(_IO_vfprintf+0x1ae7)[0x7fd6271db4a7]
+/lib/x86_64-linux-gnu/libc.so.6(__vsprintf_chk+0x94)[0x7fd627299c04]
+/lib/x86_64-linux-gnu/libc.so.6(__sprintf_chk+0x7d)[0x7fd627299b4d]
+
/scr/openconnect2/.libs/libopenconnect.so.2(openconnect_obtain_cookie+0xc0)[0x7fd62832d210]
+/scr/openconnect2/.libs/lt-openconnect[0x40413f]
+/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7fd6271b276d]
+/scr/openconnect2/.libs/lt-openconnect[0x404579]
+
+The proposed fix is to use dynamically allocated buffers with overflow
+checking.
+
+--- a/http.c
b/http.c
+@@ -32,6 +32,7 @@
+ #include
+ #include
+ #include
++#include
+
+ #include
+ #include
+@@ -45,6 +46,85 @@ static int proxy_read(struct openconnect
+ unsigned char *buf, size_t len);
+
+ #define MAX_BUF_LEN 131072
++#define BUF_CHUNK_SIZE 4096
++
++struct oc_text_buf {
++ char *data;
++ int pos;
++ int buf_len;
++ int error;
++};
++
++static struct oc_text_buf *buf_alloc(void)
++{
++ return calloc(1, sizeof(struct oc_text_buf));
++}
++
++static void buf_append(struct oc_text_buf *buf, const char *fmt, ...)
++{
++ va_list ap;
++
++ if (!buf || buf->error)
++ return;
++
++ if (!buf->data) {
++ buf->data = malloc(BUF_CHUNK_SIZE);
++ if (!buf->data) {
++ buf->error = -ENOMEM;
++ return;
++ }
++ buf->buf_len = BUF_CHUNK_SIZE;
++ }
++
++ while (1) {
++ int max_len = buf->buf_len - buf->pos, ret;
++
++ va_start(ap, fmt);
++ ret = vsnprintf(buf->data + buf->pos, max_len, fmt, ap);
++ va_end(ap);
++ if (ret < 0) {
++
Bug#683360: [Pkg-xfce-devel] Bug#683360: Bug#683360: Bug#683360: xfce4 4.10/experimental, metapackages depends on unavailable packages
On dim., 2013-02-17 at 18:57 +0100, Axel Beckert wrote: > Yves-Alexis Perez wrote: > > > Could you please explain what you mean with "Actually it's fixed" (or > > > where the fix should be available)? > > > > Could you start by explaining which packages you can't install on which > > Same issue as reported by the original reporter: > > xfce4 in Experimental depends on orage and on xfce4-panel (>= 4.10.0), > but orage from Sid depends on xfce4-panel (<< 4.9). And since there's > no orage from Experimental, xfce4 from Experimental is uninstallable > due to insatisfiable dependencies. Actually there was an orage in experimental, but the latest uploaded to unstable made it disappear. Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#697970: cups: printing gets wrong after some pages on Epson Stylus Photo 750
Hi Denis, Le dimanche, 17 février 2013 15.38:30, Denis Prost a écrit : > I faced the problem again today with the experimental package and, this > time, reapplying : > > lpadmin -p Epson_Stylus_Photo_750 -R usb-unidir-default > lpadmin -p Epson_Stylus_Photo_750 -o usb-no-reattach-default=true > > did not solve it. > > So I tried > > lpadmin -p Epson_Stylus_Photo_750 -R usb-no-reattach-default > > and it worked ! > But this behaviour is so strange that I'm not sure the problem won't > reappear. Can you please do the following procedure and tell me after which step you can print several documents without issues. Make sure to turn your printer off and back on before trying to print documents. a) Disable all printer-specific optimisations lpadmin -p Epson_Stylus_Photo_750 -R usb-no-reattach-default lpadmin -p Epson_Stylus_Photo_750 -R usb-unidir-default b) Try 'usb-no-reattach-default' lpadmin -p Epson_Stylus_Photo_750 -o usb-no-reattach-default=true c) Try both 'usb-no-reattach-default' and 'usb-unidir-default' lpadmin -p Epson_Stylus_Photo_750 -o usb-unidir-default=true d) Try 'usb-unidir-default' lpadmin -p Epson_Stylus_Photo_750 -R usb-no-reattach-default Note that the fix deployed to cups experimental is "d)", as far as I understand that code. Also note that "-R " disables a specific option, and "-o =default" enables it. Thanks in advance, cheers, OdyX -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700807: tpu: package unbound/1.4.17-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: tpu i'd like to upload unbound 1.4.17-3 with an updated D.ROOT-SERVERS.NET hint to testing/testing-proposed-updates to fix #697351. unstable has a newer upstream release (1.4.19-1) so the update will need to go via tpu. debdiff is attached. -- Robert Edmonds edmo...@debian.org diff -Nru unbound-1.4.17/debian/changelog unbound-1.4.17/debian/changelog --- unbound-1.4.17/debian/changelog 2012-05-28 14:36:18.0 -0400 +++ unbound-1.4.17/debian/changelog 2013-02-17 12:35:34.0 -0500 @@ -1,3 +1,9 @@ +unbound (1.4.17-3) testing; urgency=low + + * Update IPv4 address hint for D.ROOT-SERVERS.NET. + + -- Robert S. Edmonds Sun, 17 Feb 2013 12:34:39 -0500 + unbound (1.4.17-2) unstable; urgency=low * Build-depend on libldns-dev (>= 1.6.13~) for ECDSA support. diff -Nru unbound-1.4.17/debian/patches/debian-changes unbound-1.4.17/debian/patches/debian-changes --- unbound-1.4.17/debian/patches/debian-changes2012-05-28 14:41:58.0 -0400 +++ unbound-1.4.17/debian/patches/debian-changes2013-02-17 12:54:32.0 -0500 @@ -5,9 +5,9 @@ information below has been extracted from the changelog. Adjust it or drop it. . - unbound (1.4.17-2) unstable; urgency=low + unbound (1.4.17-3) testing; urgency=low . - * Build-depend on libldns-dev (>= 1.6.13~) for ECDSA support. + * Update IPv4 address hint for D.ROOT-SERVERS.NET. Author: Robert S. Edmonds --- @@ -54,6 +54,17 @@ AC_C_INLINE ACX_CHECK_FORMAT_ATTRIBUTE +--- unbound-1.4.17.orig/iterator/iter_hints.c unbound-1.4.17/iterator/iter_hints.c +@@ -129,7 +129,7 @@ compile_time_root_prime(int do_ip4, int + if(!ah(dp, "A.ROOT-SERVERS.NET.", "198.41.0.4"))return 0; + if(!ah(dp, "B.ROOT-SERVERS.NET.", "192.228.79.201")) return 0; + if(!ah(dp, "C.ROOT-SERVERS.NET.", "192.33.4.12")) return 0; +- if(!ah(dp, "D.ROOT-SERVERS.NET.", "128.8.10.90")) return 0; ++ if(!ah(dp, "D.ROOT-SERVERS.NET.", "199.7.91.13")) return 0; + if(!ah(dp, "E.ROOT-SERVERS.NET.", "192.203.230.10")) return 0; + if(!ah(dp, "F.ROOT-SERVERS.NET.", "192.5.5.241")) return 0; + if(!ah(dp, "G.ROOT-SERVERS.NET.", "192.112.36.4")) return 0; --- unbound-1.4.17.orig/daemon/unbound.c +++ unbound-1.4.17/daemon/unbound.c @@ -266,8 +266,6 @@ checkrlimits(struct config_file* cfg) signature.asc Description: Digital signature
Bug#670942: Please, remove the FAQ
On 17 February 2013 15:25, Thijs Kinkhorst wrote: > Hi Javier, > >> > Currently, the Securing Debian Manual [1] ships the security FAQ [2], >> > duplicating an (outdated) information already available in 9 languages. > >> Hi. I think I implemented this already in SVN. I will check later tomorrow. > > It's currently still present in svn, so please remove it as it contains > information that's currently false. Ok. Will do when I recover my development computer (currently broken, replacement is being shipped). > I can also submit a patch to correct all false information, if removing the > FAQ from the manual isn't an option in the short term. In any case I'd like to > get this fixed soon Feel free to send a patch t othe bug report. You can also ask the Debian documentation project list for somebody to apply the patch to the SVN if you need it fixed sooner. Best regards Javier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700808: emacs: editing text file containing korean quickly results in 100% cpu usage
Package: emacs Version: 45.0 Severity: important Dear Maintainer, I use emacs for editing all my text files, it is awesome. However when editing files with Korean in them it suddenly becomes extremely laggy and top shows a very high CPU usage. This occurs as son as I have opened the file, even before I have started hangul mode to type Korean. An example Korean file that gives this problem is here: http://www.kitamura-studios.com/ko-index.shtml I don't get this problem editing Chinese files. I am working around this problem by using libreoffice to edit files that contain Korean at the moment. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/12 CPU cores) Locale: LANG=en_HK.UTF-8, LC_CTYPE=en_HK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages emacs depends on: ii emacs23 23.4+1-4 emacs recommends no packages. emacs 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#700672: pu: package libzorpll/3.3.0.12-4+squeeze1
Control: tags -1 + pending On Sat, 2013-02-16 at 11:22 +, Adam D. Barratt wrote: > On Sat, 2013-02-16 at 12:19 +0100, Andreas Beckmann wrote: > > On 2013-02-16 11:10, Adam D. Barratt wrote: > > > On Sat, 2013-02-16 at 00:02 +0100, Andreas Beckmann wrote: > > >> An unversioned Breaks/Replaces should fix this, libzorp2-dev is not > > >> used as a virtual package. > > > > > > The patch looks okay; thanks. Has it been tested? > > > > Yes, I can confirm that there is now a clean upgrade path from lenny. > > And libzorpll* still installs in squeeze and upgrades from lenny without > > issues. > > Thanks for the confirmation. Please go ahead. Flagged for acceptance. 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#683360: [Pkg-xfce-devel] Bug#683360: Bug#683360: Bug#683360: xfce4 4.10/experimental, metapackages depends on unavailable packages
Hi Yves-Alexis, Yves-Alexis Perez wrote: > > xfce4 in Experimental depends on orage and on xfce4-panel (>= 4.10.0), > > but orage from Sid depends on xfce4-panel (<< 4.9). And since there's > > no orage from Experimental, xfce4 from Experimental is uninstallable > > due to insatisfiable dependencies. > > Actually there was an orage in experimental, but the latest uploaded to > unstable made it disappear. Oh, I missed that, sorry. The upload to experimental is visible on http://packages.qa.debian.org/o/orage.html, but the removal isn't -- probably because it was an auto-removal. So this issue was indeed fixed for some time, but now shows up again. Sorry for the (implicit) accusation that the bug illicitly has been marked as fixed. That definitely wasn't the case. Regards, Axel -- ,''`. | Axel Beckert , http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700523: pu: package nautilus/2.30.1-2squeeze2
Control: tags -1 + pending On Fri, 2013-02-15 at 18:14 +, Adam D. Barratt wrote: > On Wed, 2013-02-13 at 22:12 +0100, Andreas Beckmann wrote: > > * libnautilus-extension1: Add Breaks: samba-common (<< 2:3.5) to fix an > > upgrade path from lenny involving nautilus-share where lenny's apt would > > fail with "Error, pkgProblemResolver::Resolve generated breaks, this may > > be caused by held packages.". (Closes: #698775) > > Please go ahead. Flagged for acceptance in to p-u. 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#700809: python2.7: renders python2.7-dbg (<< 2.7.3.1) unusable, causes FTBFS
Package: python2.7
Version: 2.7.3-2
Severity: serious
The following change in 2.7.3-2 break python2.7-dbg 2.7.3-1 and
earlier versions:
python2.7 (2.7.3-2) unstable; urgency=low
...
* Backport issue #13150: sysconfig no longer parses the Makefile and config.h
files when imported, instead doing it at build time. This makes importing
sysconfig faster and reduces Python startup time by 20%.
...
python2.7-dbg doesn't have _sysconfigdata_d so running
python2.7-dbg fails with:
Traceback (most recent call last):
File "/usr/lib/python2.7/site.py", line 562, in
main()
File "/usr/lib/python2.7/site.py", line 544, in main
known_paths = addusersitepackages(known_paths)
File "/usr/lib/python2.7/site.py", line 271, in addusersitepackages
user_site = getusersitepackages()
File "/usr/lib/python2.7/site.py", line 246, in getusersitepackages
user_base = getuserbase() # this will also set USER_BASE
File "/usr/lib/python2.7/site.py", line 236, in getuserbase
USER_BASE = get_config_var('userbase')
File "/usr/lib/python2.7/sysconfig.py", line 591, in get_config_var
return get_config_vars().get(name)
File "/usr/lib/python2.7/sysconfig.py", line 490, in get_config_vars
_init_posix(_CONFIG_VARS)
File "/usr/lib/python2.7/sysconfig.py", line 374, in _init_posix
from _sysconfigdata import build_time_vars
File "/usr/lib/python2.7/_sysconfigdata.py", line 4, in
from _sysconfigdata_d import *
ImportError: No module named _sysconfigdata_d
Since python2.7-dbg 2.7.3-1 depends on python2.7 (>= 2.7.3-1), python2.7
should have a Breaks on python2.7-dbg (<< 2.7.3-2) so that python2.7-dbg
isn't rendered unusable by upgrading python2.7 without upgrading
python2.7-dbg to a version >= 2.7.3-2.
It might be also a good idea to change python2.7-dbg's dependency on
python2.7 to (= ${binary:Version}) as it's already done in experimental.
(I've observed this issue because of the build failure of python-crypto
2.6-4 on the ia64 buildd which has python2.7 2.7.3-5 and python2.7-dbg
2.7.3-1 installed [1])
Regards
[1]
https://buildd.debian.org/status/fetch.php?pkg=python-crypto&arch=ia64&ver=2.6-4&stamp=1361116491
--
Sebastian Ramacher
signature.asc
Description: Digital signature
Bug#700804: Audacious fails to play files if caharacter encoding is not recognised
tags 700804 upstream thanks Hi, On Sun, Feb 17, 2013 at 5:36 PM, Sakari Ailus wrote: > Audacious 3.4.2-1 currently in testing (?) fails to open files if it > does not recognise the character encoding with error message "Cannot > convert filename to system locale". This works with 2.3-2 and with the > original XMMS (!). could you try to reproduce the bug with audacious 3.3.4-1 presently available in experimental? Cheers. -- Alessio Treglia | www.alessiotreglia.com Debian Developer | ales...@debian.org Ubuntu Core Developer| quadris...@ubuntu.com 0416 0004 A827 6E40 BB98 90FB E8A4 8AE5 311D 765A -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700810: app-install-data: a typo in spout.desktop
Package: app-install-data Version: 2012.06.16.1 Severity: normal Tags: patch Hi, I hope that my patch is fine! ;-) -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.7-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- no debconf information --- /usr/share/app-install/desktop/spout.desktop 2012-08-06 15:43:28.0 +0200 +++ spout.desktop 2013-02-17 19:55:27.827614593 +0100 @@ -11,4 +11,4 @@ Icon=spout.xpm Exec=/usr/games/spout Terminal=false -Categories:Application:Game:ArcadeGame +Categories=Application:Game:ArcadeGame
Bug#700812: picard: New upstream version
Package: picard Severity: wishlist Hi, A new upstream version 1.1 is available. Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700811: interface comes up even if a script in /etc/network/if-pre-up.d/ fails
Package: ifupdown Version: 0.75 If there is a script inside /etc/network/if-pre-up.d/ which fails (exit 1), interfaces still come up. In comparison when using /etc/network/interfaces and pre-up, the network doesn't come up, which is much better. The if-pre-up.d could contain a firewall script and if the firewall fails, the network shouldn't come up. Please don't bring up any interfaces, if a script inside /etc/network/if-pre-up.d/ fails. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700806: unblock: openconnect/3.20-3 (Fixes CVE-2012-6128)
Control: tags -1 moreinfo
On 2013-02-17 19:12, Mike Miller wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
>
> Dear Release Team,
>
Hi,
> Please unblock package openconnect, version 3.20-3 already uploaded to
> unstable. This upload fixes RC bug #700794 (CVE-2012-6128), a
> stack-based buffer overflow vulnerability.
>
> The fix was made upstream and this change is a backport of that patch to
> version 3.20. The debdiff is included below. Thanks in advance.
>
>
> [...]
> ++
> ++static void buf_append(struct oc_text_buf *buf, const char *fmt, ...)
> ++{
> [...]
> ++buf->data = realloc(buf->data, new_buf_len);
As mentioned in #700805, this line introduces a memory leak if realloc
fails for any reason.
[...]
I believe this bug also affects the version uploaded to proposed-updates
(i.e. 2.25-0.1+squeeze2).
~Niels
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#700813: dot abort()s on valid input where neato, fdp, circo, twopi don't
Package: graphviz
Version: 2.26.3-12
Severity: important
Hi. Here's a graph which makes dot fail with
[1]32214 abort dot /tmp/crash.dot
Here it is:
// dot crash.dot # crashes
digraph g {
rankdir="LR" // RL is bad too, but TB/BT are fine
// A // insert this line...
B -> C // ... and swap this
C -> B // with this: then the crash goes away
B -> E
E -> F // but only if A -> E below, not if A -> C
A -> D
subgraph {rank="same"; B; C}
subgraph {rank="same"; A -> C} // or A -> E
subgraph {rank="same"; F -> D}
}
It doesn't make neato, fdp, circo or twopi fail.
If you run `dot -v9001', the last line of output is
'network simplex: 11 nodes 12 edges 2 iter 0.00 sec'
As I understand it, `network simplex' is part of the dot-specific graph layout
algorithm, so it makes sense that it crashes *there*, and not e.g. after
'loadimage' (see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698066)
Possibly related bugs, beyond that one, might be
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=292385
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=383261
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505436
In revision 9118:7dac23a1c3a9 from http://hg.research.att.com/graphviz the
problem doesn't exist.
Cheerio,
JK
PS. Let me know if I have more information I can usefully add to this.
-- System Information:
Debian Release: 7.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages graphviz depends on:
ii libc6 2.13-37
ii libcdt4 2.26.3-12
ii libcgraph5 2.26.3-12
ii libexpat1 2.1.0-1
ii libgd2-xpm 2.0.36~rc1~dfsg-6.1
ii libgraph4 2.26.3-12
ii libgvc5 2.26.3-12
ii libgvpr12.26.3-12
ii libx11-62:1.5.0-1
ii libxaw7 2:1.0.10-2
ii libxmu6 2:1.1.1-1
ii libxt6 1:1.1.3-1
Versions of packages graphviz recommends:
pn ttf-liberation
Versions of packages graphviz suggests:
pn graphviz-doc
ii gsfonts 1:8.11+urwcyr1.0.7~pre44-4.2
-- no debconf information
--
Med venlig hilsen
Jonas Kölker(+45) 30 95 49 40
Software-konstruktør, IT-handyman, data-mekaniker :-)
signature.asc
Description: Digital signature
Bug#700724: pu: package ttf-ipafont/00203-16+squeeze1
Control: tags -1 + pending On Sat, 2013-02-16 at 17:09 +, Adam D. Barratt wrote: > On Sat, 2013-02-16 at 18:01 +0100, Andreas Beckmann wrote: > > This leads to the following errors if ttf-ipafont is installed, removed > > and installed again: > > > > 0m16.5s ERROR: FAIL: After purging files have disappeared: > > I'm not sure how common doing so really is... In any case, the patch > looks sane enough, so please go ahead. Flagged for acceptance. 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#700811: interface comes up even if a script in /etc/network/if-pre-up.d/ fails
Control: found -1 0.7.5 Control: forcemerge 547587 -1 Hello, On Sun, 17 Feb 2013 18:59:36 + adrelanos wrote: > If there is a script inside /etc/network/if-pre-up.d/ which fails > (exit 1), interfaces still come up. > In comparison when using /etc/network/interfaces and pre-up, the > network doesn't come up, which is much better. > The if-pre-up.d could contain a firewall script and if the firewall > fails, the network shouldn't come up. > Please don't bring up any interfaces, if a script inside > /etc/network/if-pre-up.d/ fails. It's a known issue. Consider it a feature till wheezy+1 ;) -- WBR, Andrew signature.asc Description: PGP signature
Bug#606993: Patch for this bug
Hi, I've sent a patch fixing this grave issue and created a NMU [0] a bit over 3 months ago, please review it and upload to unstable. This bug caused the removal of subdownloader from testing, which is too bad... Please let us know if this package is not maintained anymore, as a user of it I'll gladly take care of the Debian packaging Thanks, +Emilien [0] http://mentors.debian.net/package/subdownloader 2012/11/23 Emilien Klein : > Hi Python Applications Packaging Team and Marco Rodrigues, > > Please have a look at the patch I sent to fix this "Severity: grave" > bug which caused the removal of SubDownloader from the archive. > As mentioned in my previous mail, I've prepared a NMU [0] for this, it > would be nice if you could check it. > > Thanks, > +Emilien > > [0] http://mentors.debian.net/package/subdownloader -- +Emilien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#696369: Bug#700675: pu: package fusionforge/5.0.2-5+squeeze1
Andreas Beckmann, 2013-02-16 12:03:01 +0100 : [...] > The fusionforge packages are not really in a good shape for automated > testing (e.g. #678025, #662897) ... and I never used fusionforge > myself, so I don't know how to properly test it manually. Therefore > I'm a bit reluctant to NMU fusionforge without having a positive > comment on the patch by the maintainer. Thank you for looking into this; I must confess I'm slacking in my duty as a maintainer of the fusionforge packages these days. The patch looks good to me, and I'd appreciate the NMU, please. > Could the new version suffix "+squeeze1" break something? I don't think so; there's a bit of code that handles Debian version numbers, but it takes care to delegate version comparison to dpkg, so we should be safe. > But after having run piuparts install and upgrade tests on the patched > packages (that takes some time for fusionforge ...) I can now confirm that > * there are no previously unseen installation or upgrade errors > * the file conflict is solved by unpacking gforge-common before > gforge-web-apache2 Thanks again! Roland. -- Roland Mas La tradition orale, c'est comme un vieux fromage [...] -- Le Blaire -- Signatures à collectionner, série n°2, partie 1/3. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#677880: Cuenta última advertencia
Su buzón se ha superado el límite de almacenamiento según lo establecido por el administrador, Y Usted no será capaz de recibir correos nuevos hasta que se volverá a validar. De revalidar - por favor HAGA CLICK AQUÍ http://www.form2go.com/publish/publish_form/73403 Administrador del sistema. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#697970: cups: printing gets wrong after some pages on Epson Stylus Photo 750
Hi OdyX Le 17/02/2013 19:15, Didier 'OdyX' Raboud a écrit : Hi Denis, Can you please do the following procedure and tell me after which step you can print several documents without issues. Make sure to turn your printer off and back on before trying to print documents. a) Disable all printer-specific optimisations lpadmin -p Epson_Stylus_Photo_750 -R usb-no-reattach-default lpadmin -p Epson_Stylus_Photo_750 -R usb-unidir-default b) Try 'usb-no-reattach-default' lpadmin -p Epson_Stylus_Photo_750 -o usb-no-reattach-default=true c) Try both 'usb-no-reattach-default' and 'usb-unidir-default' lpadmin -p Epson_Stylus_Photo_750 -o usb-unidir-default=true d) Try 'usb-unidir-default' lpadmin -p Epson_Stylus_Photo_750 -R usb-no-reattach-default Note that the fix deployed to cups experimental is "d)", as far as I understand that code. Also note that "-R" disables a specific option, and "-o=default" enables it. Thanks in advance, cheers, OdyX I'll do it as soon as possible, but can't promise when (I'm quite busy these days). Regards, Denis
Bug#700530: qt frames remain empty in kfreebsd since -10 to -11 update
If anyone runs into this issue: Setting the environment variable QT_X11_NO_MITSHM to a number != 0 might be a workaround to again have working qt applications. Bernhard R. Link -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#574947: Any update?
Hi, The latest version is 6.2.7 which has significant changes from 5.7.1. Even global's upstream webpage complains ``Debian's package is too old''. Hope the new version can be packaged. Thank you very much. Best, Hongzheng
Bug#700805: openconnect: Fix for CVE-2012-6128 causes memory leak on error
forwarded 700805 http://lists.infradead.org/pipermail/openconnect-devel/2013-February/000838.html tags 700805 + upstream thanks On Sun, Feb 17, 2013 at 12:56 PM, Niels Thykier wrote: > If realloc fails, it will return NULL but without freeing the original > buffer. This means the marked code will leak the (old) buf->data on > error. Thanks for reviewing and reporting this. It does look like there is at least a small chance of a memory leak. I have not traced all the paths, but at present I think the risk is quite low. I've emailed upstream to discuss. -- mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
