Bug#771758: unblock (pre-approval): serf/1.3.8-1
Control: tags -1 + confirmed moreinfo On 2014-12-02 3:38, James McCoy wrote: Please unblock package serf The upstream 1.3.8 release is a minor bug fix release. One of the three functional changes is to disable use of SSLv2/SSLv3. I'd like to include all the changes, but the SSL changes seem most relevant, so if needed I can instead backport just that patch. Please go ahead, and remove the moreinfo tag once the package has been accepted. 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#771995: Move autopsy to forensics-devel
Package: autopsy Lorenzo Martignoni martignlo has retired and orphaned his packages. It would make sense to move autopsy under the forensics-devel umbrella project. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771993: Versions of packages feh depends on
Versions of packages feh depends on: ii libcurl3 7.38.0-3 Can't even do feh --help. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771964: unblock: torbrowser-launcher/0.1.7-1 (pre-approval)
Control: tags -1 - moreinfo On Mittwoch, 3. Dezember 2014, Jonathan Wiltshire wrote: Please go ahead, and remove the moreinfo tag when it's ready. thanks, uploaded, accepted and build everywhere! cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#770627: dbus: Please (consider) switch(ing) to no-await triggers
On 04/12/14 07:00, Niels Thykier wrote: On 2014-11-30 02:52, Guillem Jover wrote: If this cannot be fixed in apt proper (due to requiring it to self-upgrade), then it should be fixable by switching dbus to noawaiting trigger directives (which I think would be correct regardless). So these triggers are: whenever a new D-Bus system service is installed in /usr/share/dbus-1/system-services or new security policies are installed in /etc/dbus-1/system.d, we tell the system dbus-daemon to reload, and block until it has done so. deb-triggers(5) says we should -noawait when the functionality provided by the trigger is not crucial. My question is, crucial for who? If dbus-daemon has not yet reloaded, then dbus-daemon will continue to work fine (it's in a consistent state either way), but the package that shipped the system service or security policy (in #771417 it's systemd) won't necessarily work properly until dbus-daemon has had a chance to reload. From reading deb-triggers(5) and /usr/share/doc/dpkg-dev/triggers.txt.gz it seems that the difference is that when systemd triggers dbus, with an interest trigger, systemd does not satisfy other packages' dependencies until dbus' trigger has run, forcing the trigger to be run before other packages try to use systemd's D-Bus API; but with an interest-noawait trigger, systemd is assumed to be fully working and satisfies dependencies, potentially resulting in failed calls to its D-Bus API because dbus-daemon's security policy does not allow them yet. Am I correct? If I am correct in my interpretation, then it seems to me that normal interest triggers are right here. However, if there is consensus that using the wrong trigger is a less severe bug than #771417, I can switch to interest-noawait and open a bug for should go back to ordinary triggers post-jessie... as long as that new bug is not *also* going to be considered RC. S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771996: Split dicomscope package
Package: dicomscope Version: 3.6.0-11 Severity: important Control: submitter -1 Markus Koschany a...@gambaru.de [...] 4. I think Mathieu is right and dicomscope should install the native libraries into specific *-jni packages. The Java policy should be changed to say must be shipped in a separate package instead of should. In any case dicomscope:amd64 and dicomscope:i386 are currently not co-installable, so the whole discussion about the java -d32|64 hack is rather academic at the moment. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771969: s3ql: mount.s3ql throws exception and hangs file system
On Wed, 3 Dec 2014, Nikolaus Rath wrote: severity 771969 important thanks Thanks for the report! I'll set the severity to important for now, because the package still works nicely for many other users. Not sure why it's making so much trouble for you.. Because computers hate me :-) I actually have yet another problem with an sshfs mounted s3ql file system but was trying to get the issues with my S3 mount resolved first. but I notice that (like the last bug you found) this seems related to the handling of unreliable network connections. In this case there seems to be a temporary problem with your DNS server which S3QL has trouble coping with. From a high level perspective, the connection (generally) is pretty reliable, but I wouldn't notice momentary network issues. The raw_streamXXX files are from the patch that you applied to the debug the previous issue. I'd recommend to purge and reinstall both the s3ql and python3-dugong packages to make sure that you're in vanilla state again. I forgot about the dugong patch, so I reinstalled both packages, using the Debian-unstable version for s3ql If the file system still hangs (or the next time it hangs), could you follow the instructions at https://bitbucket.org/nikratio/s3ql/wiki/Providing%20Debugging%20Info to obtain a Python stacktrace, and attach it to this issue? This time the file system didn't hang until I attempted to unmount it. Attached are two log files with the mount and stack trace information. Shannon C. Dealy | DeaTech Research Inc. de...@deatech.com |- Custom Software Development - USA Phone: +1 800-467-5820 |- Natural Building Instruction - numbers : +1 541-929-4089 |www.deatech.com2014-12-04 07:28:56.413 31144:MainThread (name)s.excepthook: Mountpoint does not exist. 2014-12-04 07:39:43.743 609:MainThread (name)s.determine_threads: Using 8 upload threads. 2014-12-04 07:39:43.746 609:MainThread (name)s.main: Autodetected 4040 file descriptors available for cache entries 2014-12-04 07:39:56.730 609:MainThread (name)s.get_metadata: Using cached metadata. 2014-12-04 07:39:56.734 609:MainThread (name)s.main: Mounting filesystem... 2014-12-04 07:39:56.821 626:MainThread (name)s.detach_process_context: Daemonizing, new PID is 630 2014-12-04 07:42:45.765 630:MainThread (name)s.main: FUSE main loop terminated. 2014-12-04 07:42:45.786 630:MainThread (name)s.unmount: Unmounting file system... 2014-12-04 07:42:46.272 630:MainThread (name)s.main: File system unchanged, not uploading metadata. 2014-12-04 07:42:46.309 630:MainThread (name)s.main: Cleaning up local metadata... 2014-12-04 07:42:51.966 630:MainThread (name)s.main: All done. 2014-12-04 07:42:58.936 3663:MainThread (name)s.determine_threads: Using 8 upload threads. 2014-12-04 07:42:58.938 3663:MainThread (name)s.main: Autodetected 4040 file descriptors available for cache entries 2014-12-04 07:43:05.572 3663:MainThread (name)s.get_metadata: Using cached metadata. 2014-12-04 07:43:05.582 3663:MainThread (name)s.main: Mounting filesystem... 2014-12-04 07:43:05.602 3669:MainThread (name)s.detach_process_context: Daemonizing, new PID is 3671 2014-12-04 07:43:12.769 3671:Dummy-22 (name)s.stacktrace: # ThreadID: 140042022409984 pyapi.py:504, in stacktrace for filename, lineno, name, line in traceback.extract_stack(frame): # ThreadID: 140042039195392 threading.py:888, in _bootstrap self._bootstrap_inner() threading.py:920, in _bootstrap_inner self.run() mount.py:66, in run_with_except_hook run_old(*args, **kw) threading.py:868, in run self._target(*self._args, **self._kwargs) queue.py:167, in get self.not_empty.wait() threading.py:290, in wait waiter.acquire() # ThreadID: 140043138082560 threading.py:888, in _bootstrap self._bootstrap_inner() threading.py:920, in _bootstrap_inner self.run() mount.py:66, in run_with_except_hook run_old(*args, **kw) threading.py:868, in run self._target(*self._args, **self._kwargs) block_cache.py:677, in _removal_loop tmp = self.to_remove.get(block=len(ids)==0) queue.py:167, in get self.not_empty.wait() threading.py:290, in wait waiter.acquire() # ThreadID: 140042576066304 threading.py:888, in _bootstrap self._bootstrap_inner() threading.py:920, in _bootstrap_inner self.run() mount.py:66, in run_with_except_hook run_old(*args, **kw) threading.py:868, in run self._target(*self._args, **self._kwargs) block_cache.py:677, in _removal_loop tmp = self.to_remove.get(block=len(ids)==0) queue.py:167, in get self.not_empty.wait() threading.py:290, in wait waiter.acquire() # ThreadID: 140043154867968 threading.py:888, in _bootstrap self._bootstrap_inner() threading.py:920, in _bootstrap_inner self.run() mount.py:66, in run_with_except_hook run_old(*args, **kw) threading.py:868, in run self._target(*self._args, **self._kwargs) block_cache.py:677, in _removal_loop tmp =
Bug#771922: keyboard handling broken with jessie's gnome-settings-daemon
Hi,
On Wed, 3 Dec 2014 21:04:54 +0200, Faidon Liambotis wrote:
You may say that gnome-panel should be removed as well, but please do not
forget that there are 8 other source packages depending on it, so they should
get removed as well in that case.
Yeah, that's a good point. This affects the Flashback mode as a whole...
Another possibility will be to drop gnome-session-f{lash,all}back packages from
gnome-panel source. This way we won’t need to remove stuff that depends on
gnome-panel (though I still do not like this, see below).
I think the best solution will be to leave things as-is. But if you convince
the Release Team that removing 10 packages (or backporting 800 lines of code
to add keyboard grabber) is a good idea, I will be fine with that.
I don't think this is fit for release as-is.
Are you referring to the two patches I posted? If so, I wish it was that
simple; those a) are a hack, since they provide org.gnome.Shell, b) only
fix media keys custom keybindings, not layout switching/input sources,
c) even for media keys, there is no OSD, for e.g. volume.
Yes, I am referring to the two patches you posted.
Note that gnome-flashback already owns org.gnome.Shell to show end session
dialogs.
In any case, though, let's agree on the problem first. This is currently
a severity: grave bug, i.e. release critical.
I agree that this is a problem. However, GNOME Flashback can still be
usable in most cases:
- To switch keyboard layouts one can use good old xkb (I do that when I use
GNOME Flashback session).
- Other keybindings are not so critical. To lock screen / power off / etc
one can use the user menu.
Thus I still think this bug should be downgraded to important or ignored for
Jessie.
This mail is written from gnome-flashback session on Jessie, btw.
--
Dmitry Shachnev
signature.asc
Description: OpenPGP digital signature
Bug#770461: upowerd become crazy after plug in my laptop
Le 04/12/2014 00:26, Tomas Pospisek a écrit : Hello, you wrote: After standby cycle, using the laptop, and plugged it to power, upowerd become crazy and start to consume more and more memory and 100% of a cpu ! I think this might have been fixed in 0.99.1-3.1 : http://metadata.ftp-master.debian.org/changelogs//main/u/upower/upower_0.99.1-3.1_changelog Could you please try out that version and report back here, if it fixes the problem? *t Yes, I also think so... It never happened since the last update and I heavly using standby mode. Regards Mourad -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768657: [Pkg-sysvinit-devel] Bug#768657: sysvinit: Please provide xen virtual console in inittab
On Wed, 2014-12-03 at 23:12 +0100, Samuel Thibault wrote: I'm not sure to understand what the original bug report is about precisely. AIUI, it is about the following scenario: 1) install debian in a Xen domU, ending up with systemd installed by default 2) install sysvinit-core to switch back to sysvinit boot 3) end up having to fix this and that to get sysvinit work properly I am not very surprised that it does not work. The various tuning that d-i does usually only work on what gets installed during d-i, not on what gets installed later on. That's particularly the case for software which doesn't provide nice hooks for d-i to use them. I'm just wondering one thing: between steps 1) and 2), does the installed system (using systemd) properly have a login banner on hvc0? I believe it will, systemd probes for suitable console devices and spawns getty's for them. I'm sure I've seen this in Debian guests using systemd, although I've not gone and checked my recollection. It would make sense, but I'm not sure we can manage to write something that both sysvinit and systemd can understand easily. include support could be added to sysvinit, and /etc/inittab made to include the d-i-generate bits, but it'd still be in inittab format, which AIUI systemd wouldn't grok. So it would be something else, but then we would have to make sysvinit aware of what a serial login is, which it has never been made to, for flexibility reasons. Something which might be helpful is http://lists.xen.org/archives/html/xen-devel/2013-12/msg00805.html which was posted on the xen-devel but redirected to the appropriate upstream, since it isn't Xen specific. I wonder how that got on. Anyway, it would allow all the various initsystems to just spawn one of these smart gettys and get a getty on the console device, whatever that may be. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#601345: are you still experiencing the reported bug?
Hi Tomas, Thanks for cleaning up :-) I am no longer in possesion of the laptop describe. I also don't use the Ubuntu version mentions. You can consider the problem solved for me. Oz On Thu, Dec 4, 2014 at 12:36 AM, Tomas Pospisek t...@sourcepole.ch wrote: Hello Oz and Akira, you reported bug http://bugs.debian.org/601345 against a version of upower older than the one currently found in Debian jessie. However Christophe TROESTLER wrote on 02 Jun 2011 on the same bug: With version 0.9.11-1+b1 (currently in unstable), the percentage level seems to be reported fine In case you are running the latest upower version from Debian jessie, could you please test if you still experience the problem? It would be nice if you could test and reply, so this bug could be marked as fixed in jessie and closed. Thanks, *t PS: If I may, then I'd like to suggest to look through the list of open bugs reported by yourself and close the ones that are not valid any more: https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist= unstable;submitter=nahumoz%40gmail.com
Bug#771997: swp on armv8 (Was: Haskell on arm needs help)
Source: linux Version: 3.16.7-2 Severity: important X-Debbugs-CC: debian-...@lists.debian.org On Thu, 2014-12-04 at 08:38 +, Ian Campbell wrote: On Wed, 2014-12-03 at 23:23 +, peter green wrote: I vaugely remember something a while back about some deprecated 32-bit arm instructions needing kernel emulation on armv8 and that emulation not being implemented yet. That's correct, and IIRC swp is one of those instructions. AIUI swp is already handled through kernel emulation on armv7 multiprocessor systems. There seem to be patches to port that emulation to arm64 but it doesn't appear they are in the kernel tree debian is using. Having 32-bit binaries break on armv8 systems due to lack of the swp instruction does not seem like a good thing so IMO we really want this in our kernels before release. If those patches have gone into a later upstream kernel than we have in Jessie (v3.16) then we should certainly backport them. IIRC they were controversial though, so if they haven't hit mainline I'd be *very* reluctant to fork the v8 userspace ABI. They are in the arm64 maintainer's for-next/core branch but not in Linus' tree (yet): $ git log --oneline v3.16..origin/master -- arch/arm64/kernel/armv8_deprecated.c $ git log --oneline v3.16..arm64/for-next/core -- arch/arm64/kernel/armv8_deprecated.c 9096339 arm64: fix return code check when changing emulation handler d784e29 arm64: Trace emulation of AArch32 legacy instructions c852f32 arm64: Emulate CP15 Barrier instructions bd35a4a arm64: Port SWP/SWPB emulation support from arm 587064b arm64: Add framework for legacy instruction emulation I've bcc'd submit@ on this mail to create a bug for tracking. I think I'm happy to backport now (FSVO now depending on when I get a moment), since these are clearly en route to Linus. Note that after these patches SWP is still undef by default, this just adds the option to emulate (via a sysctl toggle). I don't propose to deviate from upstream here, since they have good reasons to prefer the current defaults. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771945: tor: abstractions/nameservice is unnecessary in AppArmor profile
Control: tag -1 + moreinfo Hi, Henrik Ahlgren wrote (03 Dec 2014 18:04:27 GMT) : Please consider removing the line #include abstractions/nameservice from /etc/apparmor.d/abstractions/tor. In my testing tor seems to function just fine without it; I haven't seen any errors reported to audit.log or tor's own log. The nameserver abstraction grants access to e.g. /etc/passwd that could reveal the identity of the owner of the machine. If I remove that line, then the system Tor daemon fails to start here with: [notice] Tor v0.2.5.10 (git-43a5f3d91e726291) running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.1j and Zlib 1. [notice] Read configuration file /usr/share/tor/tor-service-defaults-torrc. [notice] Read configuration file /etc/tor/torrc. [warn] Error setting configured user: debian-tor not found [warn] Failed to parse/validate config: Problem with User value. See logs for details. Did you test this usecase? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771974: gcc-4.9: FTBFS on hppa after r218208
Control: forwarded -1 https://gcc.gnu.org/PR64167 Control: tags -1 + upstream On 12/04/2014 01:41 AM, John David Anglin wrote: Package: gcc-4.9 Version: 4.9.2-5 Severity: normal gcc-4.9 4.9.2-5 fails to build from source on hppa. See: http://buildd.debian-ports.org/status/fetch.php?pkg=gcc-4.9arch=hppaver=4.9.2-5stamp=1417599336 r218208 introduced a number of problems including this PR: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64167 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771998: plasma-nm: Plasma-NM gets partially dysfunctional after systemd upgrade
Package: plasma-nm Version: 0.9.3.4-2 Severity: normal Dear Maintainer, after upgrading systemd, die KDE NM applet gets partially dysfunctional. Steps to reproduce: - disable WiFi in the Plasma NM $ sudo aptitude reinstall systemd $ sudo systemctl restart NetworkManager.service - click the WiFi checkbox in Plasma NM Expectid behavior: WiFi should be enabled again. Actual behavior: It is not - nothing happens. However, I can run sudo nmcli radio wifi on to enable radio again, and Plasma NM notices that. It even connects to the WiFi, but the checkbox remains dysfunctional - I cannot control radio anymore. It also happened once to me that I cannot use Plasma NM to control the WiFi connections, but I could not reproduce that. Not even restarting Plasma fixes the checkbox. Additional information: This may be related to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771122 (to work around the issue described there, I do a restart of NM). Kind regards, Ralf -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.17.0+ (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages plasma-nm depends on: ii kde-runtime 4:4.14.2-1 ii libc6 2.19-13 ii libgcc1 1:4.9.1-19 ii libkdecore5 4:4.14.2-3 ii libkdeui5 4:4.14.2-3 ii libkio5 4:4.14.2-3 ii libknotifyconfig4 4:4.14.2-3 ii libmodemmanagerqt1 1.0.1-2 ii libnetworkmanagerqt10.9.8.2-1 ii libopenconnect3 6.00-1+b1 ii libplasma3 4:4.14.2-3 ii libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-declarative 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-network 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-svg 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-xml 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libsolid4 4:4.14.2-3 ii libstdc++6 4.9.1-19 ii mobile-broadband-provider-info 20140317-1 ii network-manager 0.9.10.0-3 Versions of packages plasma-nm recommends: ii kwalletmanager 4:4.14.2-1 ii network-manager-openvpn 0.9.10.0-1 ii network-manager-pptp 0.9.10.0-1 ii network-manager-vpnc 0.9.10.0-1 Versions of packages plasma-nm suggests: ii kde-workspace-bin4:4.11.13-2 ii network-manager-openconnect 0.9.10.0-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768127: Fails to build the index when invalid UTF-8 is met
Package: dhelp Version: 0.6.21+nmu5 Followup-For: Bug #768127 I don't know if it helps, but I got a similar error from the weekly cron task. LANG=C sudo /etc/cron.weekly/dhelp ArgumentError: invalid byte sequence in US-ASCII (/usr/lib/ruby/vendor_ruby/dhelp.rb:185:in `===' /usr/lib/ruby/vendor_ruby/dhelp.rb:185:in `block in initialize' /usr/lib/ruby/vendor_ruby/dhelp.rb:183:in `each' /usr/lib/ruby/vendor_ruby/dhelp.rb:183:in `initialize' /usr/lib/ruby/vendor_ruby/dhelp.rb:309:in `new' /usr/lib/ruby/vendor_ruby/dhelp.rb:309:in `block (2 levels) in each' /usr/lib/ruby/vendor_ruby/dhelp.rb:306:in `each' /usr/lib/ruby/vendor_ruby/dhelp.rb:306:in `block in each' /usr/lib/ruby/vendor_ruby/dhelp.rb:305:in `each' /usr/lib/ruby/vendor_ruby/dhelp.rb:305:in `each' /usr/lib/ruby/vendor_ruby/dhelp.rb:456:in `_register_docs' /usr/lib/ruby/vendor_ruby/dhelp.rb:387:in `rebuild' /usr/sbin/dhelp_parse:204:in `main' /usr/sbin/dhelp_parse:216:in `main') It seems to work fine with my default locale: LANG=es_CO.utf8 sudo /etc/cron.weekly/dhelp I added a puts @path in /usr/lib/ruby/vendor_ruby/dhelp.rb:184 and it shows this: ... /var/lib/doc-base/documents/bogofilter-bogotune-faq /var/lib/doc-base/documents/developers-reference /var/lib/doc-base/documents/developers-reference /var/lib/doc-base/documents/developers-reference /var/lib/doc-base/documents/developers-reference ArgumentError: invalid byte sequence in US-ASCII (/usr/lib/ruby/vendor_ruby/dhelp.rb:186:in `===' /usr/lib/ruby/vendor_ruby/dhelp.rb:186:in `block in initialize' /usr/lib/ruby/vendor_ruby/dhelp.rb:183:in `each' ... The problem rises when it parses the fourth line in developers-reference: Author: Adam Di Carlo, Josip Rodin, Raphaël Hertzog, et al It doesn't complain when I use fr_FR.UTF-8 ! (which is not consisent :P) Cheers, Santiago -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=es_CO.utf8, LC_CTYPE=es_CO.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dhelp depends on: ii doc-base 0.10.6 ii libdata-page-perl 2.02-1 ii libhtml-parser-perl 3.71-1+b3 ii liblocale-gettext-perl1.05-8+b1 ii libtemplate-perl 2.24-1.2+b1 ii liburi-perl 1.64-1 ii perl-modules 5.20.1-3 ii poppler-utils 0.26.5-2 ii pstotext 1.9-6+b1 ii ruby 1:2.1.0.4 ii ruby-bdb 0.6.6-1+b2 ii ruby-debian 0.3.9 ii ruby-gettext 3.1.2-1 ii ruby1.8 [ruby-interpreter]1.8.7.358-7.1+deb7u1 ii ruby1.9.1 [ruby-interpreter] 1.9.3.194-8.1+deb7u2 ii ruby2.1 [ruby-interpreter]2.1.5-1 ii swish++ 6.1.5-2.2 ii ucf 3.0030 Versions of packages dhelp recommends: ii chromium [www-browser] 38.0.2125.101-3 ii html2text1.3.2a-18 ii iceweasel [www-browser] 31.2.0esr-3 ii opera [www-browser] 12.16.1860 ii w3m [www-browser]0.5.3-19 Versions of packages dhelp suggests: ii apache2 [httpd-cgi] 2.4.10-8 ii apache2-mpm-prefork [httpd-cgi] 2.4.10-8 pn catdvi none pn info2www none pn man2html none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771991: confirmed
Hi, the effect of this bug can also be seen at https://jenkins.debian.net/job/chroot-installation_sid_install_gnome/760/console and https://jenkins.debian.net/job/chroot-installation_sid_install_kde/694/ as well as with other jobs... IOW: it will also be easy for us to see when this is fixed. Thanks to Josselin Mouette who tracked down the failures in the jenkins jobs to be caused by this bug. cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#761815: wow, huh
Control: severity -1 serious Control: tags -1 +patch [CCing Ansgar as the original bug submitter] Just to give some context: This bug is about adding entries for USB mass storage devices to /etc/fstab on installation. Olliver Schinagl oli...@schinagl.nl writes: I just got bitten by this bug myself. As a long time gentoo + ubuntu user, I was baffled after getting the solution to this problem. I have worked through several different kind of fstab files, but this was a serious wtf. Why wasn't removable storage working for me? I just couldn't figure it out, everything 'looked' normal. I'd increase the severity of this report, as it is far far from obvious. I just had a look at the relevant code in partman-target finish.d/fstab_removable_media_entries. As far as I understand it (no testing done) these entries are added if a USB device is currently plugged in. The code is from 2004 (commit af81206d02f8d668dab382e5ec8483ccbc90a506) when this probably made sense. Does it make any sense anymore to keep this code? IMO the fstab entries should at least not be added when udisks is installed. I attached a patch (not yet tested) which does this. My patch currently only prohibits adding of USB device entries. Should this be extended to floppies and CD-ROMs? What about kfreebsd and hurd? IMO this should be fixed before the release as it causes unexpected and inconsistent behavior. For example udisks will just mount the usb device as normal if it does not have the same device node as the one used during installation, but devices that happen to get the same device node won't be accessible and mounted on a different path. This will lead to things like one device being accessible and the other not if you plug in two usb mass storage devices. I raised the severity of the bug to serious as I think this should be RC, but if members more involved with d-i than I am currently disagree, feel free to downgrade again. Gaudenz From ec9b2cc840412863499c10854926f7328d6c9cc0 Mon Sep 17 00:00:00 2001 From: Gaudenz Steinlin gaud...@debian.org Date: Thu, 4 Dec 2014 10:22:32 +0100 Subject: [PATCH] Only add USB entries to fstab if udisks is not installed In combination with udisks these entries cause USB mass storage devices to be mounted with options that prohibit the current user from accessing the data. The also change the mount point to always be /media/usb0. The fstab entries also only work if the USB device has the same device node as the device that was used on installation. Which is not guaranteed at all. --- finish.d/fstab_removable_media_entries | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/finish.d/fstab_removable_media_entries b/finish.d/fstab_removable_media_entries index 813873d..5e209b5 100755 --- a/finish.d/fstab_removable_media_entries +++ b/finish.d/fstab_removable_media_entries @@ -159,7 +159,10 @@ done case `udpkg --print-os` in linux) - populate_media usb auto rw,user,noauto $USBDEVICES + # Only add USB entries if udisks or udisks2 are not installed + if ! in-target sh -c dpkg-query -s udisks udisks2 2/dev/null | grep -q '^Status: install ok installed' ; then + populate_media usb auto rw,user,noauto $USBDEVICES + fi ;; kfreebsd) populate_media usb auto rw,noauto $USBDEVICES -- 2.1.3 signature.asc Description: PGP signature
Bug#771184: unblock: postgresql-9.4/9.4~rc1-1.pgdg+1
Re: Adam D. Barratt 2014-12-04 7207dce6eff7baea931384c5f1fdf...@mail.adsl.funky-badger.org On 2014-11-27 11:51, Christoph Berg wrote: Please unblock package postgresql-9.4. This is now finally an RC version of the 9.4 series. The PostgreSQL people were planning to release 9.4.0 next week, but this hasn't been finalized yet, so it might well be a bit later. Have there been any updates on that? There's been some pondering if some minor API change warrants an RC2 version or if that change should just be reverted [1] - afaict RC2 won't happen, so 9.4.0 should be there soonish. Usually the packagers learn about this one or two weeks in advance, so there's still chances to make it happen before Christmas. (Afaict the chances for that are rather good.) [1] http://www.postgresql.org/message-id/28190.1417288...@sss.pgh.pa.us I've unblocked ~rc1-1; thanks. Thanks! Mit freundlichen Grüßen, Christoph Berg -- Senior Berater, Tel.: +49 (0)21 61 / 46 43-187 credativ GmbH, HRB Mönchengladbach 12080, USt-ID-Nummer: DE204566209 Hohenzollernstr. 133, 41061 Mönchengladbach Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer pgp fingerprint: 5C48 FE61 57F4 9179 5970 87C6 4C5A 6BAB 12D2 A7AE -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771999: jxrlib does not support large file
Package: jxrlib
Version: 1.1-5
Severity: important
Tags: lfs
By default jxrlib uses the old 32bits API to read from file, eg:
[...]
ERR SetPosWS_File(struct WMPStream* pWS, size_t offPos)
{
ERR err = WMP_errSuccess;
FailIf(0 != fseek(pWS-state.file.pFile, (long)offPos, SEEK_SET),
WMP_errFileIO);
Cleanup:
return err;
}
ERR GetPosWS_File(struct WMPStream* pWS, size_t* poffPos)
{
ERR err = WMP_errSuccess;
long lOff = 0;
FailIf(-1 == (lOff = ftell(pWS-state.file.pFile)), WMP_errFileIO);
*poffPos = (size_t)lOff;
Cleanup:
return err;
}
[...]
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755475: gnome-shell-common: since 3.12 components entered testing, gnome-shell breaks GDM
Hi Tomas, Tomas Pospisek t...@sourcepole.ch wrote: Would it be a good idea to set thighter package interdependencies or, at least, put a Breaks: gdm ( 3.12) to upower? Agreed. Reassigning. Seeing that gdm3 in wheezy was 3.4.1-8 and that everybody is going to update to gdm3 = 3.14.1-3 for jessie or the versions in jessie anyway I'm not sure this is required? Is there some specific scenario where users would be running with unreleased, older gdm3's? Well, partial upgrades are not “supported” per se, but they are expected not to leave your system in an unusable state, so when there’s a lockstep upgrade we should match it in the dependencies. -- Joss -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770706: [PKG-Openstack-devel] Bug#770706: keystone.service does not start, /var/run/keystone not created
Mikaël Cluseau mclus...@isi.nc writes: On 12/04/2014 03:52 AM, Thomas Goirand wrote: Let's see what the release team says. Thanks Thomas. Aside from this, I took a look at how they did in Fedora. Here is their unit file: [Unit] Description=OpenStack Identity Service (code-named Keystone) After=syslog.target network.target [Service] Type=notify Restart=always User=keystone ExecStart=/usr/bin/keystone-all --config-file /usr/share/keystone/keystone-dist.conf --config-file /etc/keystone/keystone.conf [Install] WantedBy=multi-user.target So, we can use multiple config files, this allows the same granularity as the /etc/default/* way. They also use the Type=notify clause. Their keystone-dist.conf has the following DEFAULT section: [DEFAULT] log_file = /var/log/keystone/keystone.log onready = keystone.common.systemd Cool, didn't know that keystone supports the systemd notification protocol. We should definitely use that post jessie then. Do you know if all the openstack daemons support this and configure it in the same way? To mimic the current genericity of our init-script, we could use something like ExecStart=... --config-file /usr/share/keystone/keystone-systemd.conf --config-file /etc/openstack.conf --config-file /etc/keystone/keystone.conf with the same global section in /usr/share/keystone/keystone-systemd.conf. One can then use /etc/openstack.conf to switch back to syslog or stdout or stderr or whatever she wants globally. That looks like a good solution to me to get rid of the /etc/default files without loosing any functionality. This would avoid duplicating configuration settings in configuration files and /etc/default files. Looks like the best solution to me, but ovviously post jessie. Gaudenz signature.asc Description: PGP signature
Bug#772000: openvpn cannot start with systemd
package: openvpn version: 2.3.4-5 severity: grave justification: autostarting of openvpn does not work I have tested both server and client with systemd on sid. Configuration is correct as manually running openvpn via 'openvpn server.conf' and 'openvpn client.conf' works. Same configuration is working with upstart on Ubuntu 12.04 signature.asc Description: OpenPGP digital signature
Bug#772001: ITP: ruby-rails-assets-perfect-scrollbar -- Tiny but perfect jQuery scrollbar plugin
package: perfect-scrollbar Severity: wishlist Owner: 'syam' syamg...@gmail.com *Package Name : perfect-scrollbar Version : 2.1.2 Upstream Author : Hyunje Alex Jun (Author name/s of the Gem). *URL : https://github.com/noraesae/perfect-scrollbar (Link to the git repo of the Gem) *License : MIT *Description : Tiny but perfect jQuery scrollbar plugin I am packaging perfect-scrollbar as it is a dependency of rails-assets (#691181) which is a dependency of diaspora (#597093) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772002: unblock: geki2/2.0.3-9
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package geki2. The 2.0.3-9 upload fixes a bug with priority important that is present in jessie - #770055, one of Guillem Jover's obsolete absolute path to dpkg-statoverride. geki2 (2.0.3-9) unstable; urgency=medium * Team upload. * Do not use the obsolete and incorrect full path to dpkg-statoverride. Closes: #770055 -- Peter Pentchev r...@ringlet.net Sat, 29 Nov 2014 03:02:01 +0200 Full debdiff attached. Thanks in advance! unblock geki2/2.0.3-9 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -u geki2-2.0.3/debian/postinst geki2-2.0.3/debian/postinst --- geki2-2.0.3/debian/postinst +++ geki2-2.0.3/debian/postinst @@ -9,15 +9,13 @@ # Cancel my old stupid use of dpkg-statoverride if [ $1 = configure ] [ $2 != ] dpkg --compare-versions $2 le 2.0.3-4 - [ -x /usr/sbin/dpkg-statoverride ] dpkg-statoverride --list $PROG /dev/null then dpkg-statoverride --remove $PROG fi # Properly use statoverride -if ! [ -x /usr/sbin/dpkg-statoverride ] || \ -! dpkg-statoverride --list $PROG /dev/null ; then +if ! dpkg-statoverride --list $PROG /dev/null ; then chown root:games $PROG chmod 2755 $PROG fi diff -u geki2-2.0.3/debian/changelog geki2-2.0.3/debian/changelog --- geki2-2.0.3/debian/changelog +++ geki2-2.0.3/debian/changelog @@ -1,3 +1,11 @@ +geki2 (2.0.3-9) unstable; urgency=medium + + * Team upload. + * Do not use the obsolete and incorrect full path to dpkg-statoverride. +Closes: #770055 + + -- Peter Pentchev r...@ringlet.net Sat, 29 Nov 2014 03:02:01 +0200 + geki2 (2.0.3-8) unstable; urgency=low [ Barry deFreese ] signature.asc Description: Digital signature
Bug#771978: Patch: apparmor profile for ps
Hi pkg apparmor team, On Wed, Dec 03, 2014 at 08:48:08PM -0600, Pat Parson wrote: /bin/ps does not have an apparmor profile. I have attached an apparmor profile to patch the package. Except for a basic concept, I'm not familiar with apparmour and Debian. The Debian wiki is not too helpful with it either. Is it just a matter of sticking this patch file into /etc/apparmor.d/bin.ps and then that's it? It would be really useful if the Wiki had a what happens if you get one of these profiles page. For someone who understands how it works it should be a pretty quick page to write. A debhelper dh_* tool would even be better. - Craig -- Craig Small (@smallsees) http://enc.com.au/ csmall at : enc.com.au Debian GNU/Linux http://www.debian.org/ csmall at : debian.org GPG fingerprint:5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772003: unblock: geki3/1.0.3-8
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package geki3. The 1.0.3-8 upload fixes a bug with priority important that is present in jessie - #770056, one of Guillem Jover's obsolete absolute path to dpkg-statoverride. geki3 (1.0.3-8) unstable; urgency=medium * Team upload. * Do not use the obsolete and incorrect full path to dpkg-statoverride. Closes: #770056 -- Peter Pentchev r...@ringlet.net Sat, 29 Nov 2014 02:50:27 +0200 Full debdiff attached. Thanks in advance! unblock geki3/1.0.3-8 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -u geki3-1.0.3/debian/postinst geki3-1.0.3/debian/postinst --- geki3-1.0.3/debian/postinst +++ geki3-1.0.3/debian/postinst @@ -7,15 +7,13 @@ # Cancel my old stupid use of dpkg-statoverride if [ $1 = configure ] [ $2 != ] dpkg --compare-versions $2 le 1.0.3-4 - [ -x /usr/sbin/dpkg-statoverride ] dpkg-statoverride --list $PROG /dev/null then dpkg-statoverride --remove $PROG fi # Properly use statoverride -if ! [ -x /usr/sbin/dpkg-statoverride ] || \ -! dpkg-statoverride --list $PROG /dev/null ; then +if ! dpkg-statoverride --list $PROG /dev/null ; then chown root:games $PROG chmod 2755 $PROG fi diff -u geki3-1.0.3/debian/changelog geki3-1.0.3/debian/changelog --- geki3-1.0.3/debian/changelog +++ geki3-1.0.3/debian/changelog @@ -1,3 +1,11 @@ +geki3 (1.0.3-8) unstable; urgency=medium + + * Team upload. + * Do not use the obsolete and incorrect full path to dpkg-statoverride. +Closes: #770056 + + -- Peter Pentchev r...@ringlet.net Sat, 29 Nov 2014 02:50:27 +0200 + geki3 (1.0.3-7) unstable; urgency=low * Moved packaging to the Debian Games Team. signature.asc Description: Digital signature
Bug#768657: [Pkg-sysvinit-devel] Bug#768657: sysvinit: Please provide xen virtual console in inittab
Samuel Thibault sthiba...@debian.org writes: What is new here is that sysvinit-core can now get initially installed not from d-i. And thus the tuning usually done by d-i can't work. Also, we probably have to think about ping-pong scenarii: install sysvinit-core, then switch back to systemd, purge sysvinit-core, and drop /etc/inittab. Change one's mind again, reinstall sysvinit-core. We still want to have a console on /dev/hvc0. We're far from d-i, so it'd rather be sysvinit-core which does the job of adding the console to inittab. Can't some of the logic in finish-install's 90console simply moved to sysvinit-core's postinst? From my POV as an infrequent d-i contributor: For the reasons above and because having an /etc/inittab which does not do anything on systemd is confusing I think moving this to sysvinit-core is the best solution. Not reassing the bug right now to let others comment first. Gaudenz signature.asc Description: PGP signature
Bug#767936: Marked for autoremoval on 05 December
Hi, mcollective will be auto-removed from Jessie *tomorrow*. Being just a DM I can do nothing about this, but it would be great if an updated package could make it in to sid today to avoid mcollective going missing from Jessie completely. Once it has been removed it will be that much harder to get back in again. Best regards, Chris -- Chris Boot deb...@bootc.net GPG: 8467 53CB 1921 3142 C56D C918 F5C8 3C05 D9CE -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772000: openvpn cannot start with systemd
On Thu, Dec 04, 2014 at 03:16:11PM +0530, Pirate Praveen wrote: package: openvpn version: 2.3.4-5 severity: grave justification: autostarting of openvpn does not work I have tested both server and client with systemd on sid. Configuration is correct as manually running openvpn via 'openvpn server.conf' and 'openvpn client.conf' works. Same configuration is working with upstart on Ubuntu 12.04 Could you provide your /etc/default/openvpn, and the ouput of: systemctl status openvpn -- Alberto Gonzalez Iniesta| Formación, consultoría y soporte técnico mailto/sip: a...@inittab.org | en GNU/Linux y software libre Encrypted mail preferred| http://inittab.com Key fingerprint = 5347 CBD8 3E30 A9EB 4D7D 4BF2 009B 3375 6B9A AA55 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772004: RFS: openldap/2.4.40-3.1 NMU -- smooth upgrade for partial replicas
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package openldap Package name: openldap Version : 2.4.40-3.1 Upstream Author : The OpenLDAP Project URL : http://www.openldap.org/ License : OpenLDAP Public License Section : net It builds those binary packages: ldap-utils - OpenLDAP utilities libldap-2.4-2 - OpenLDAP libraries libldap-2.4-2-dbg - Debugging information for OpenLDAP libraries libldap2-dev - OpenLDAP development libraries slapd - OpenLDAP server (slapd) slapd-dbg - Debugging information for the OpenLDAP server (slapd) slapd-smbk5pwd - Keeps Samba and Kerberos passwords in sync within slapd. To access further information about this package, please visit the following URL: http://mentors.debian.net/package/openldap Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/o/openldap/openldap_2.4.40-3.1.dsc Changes since the last upload: openldap (2.4.40-3.1) unstable; urgency=medium . * Non-maintainer upload. * Disable schema checking for reloading the dumped data during upgrades, to avoid interrupting the upgrade procedure of partial replicas. (Closes: #614569). Though technically it's an NMU, please don't delay the upload too much, as the unblock pre-approval expires on Monday the 8th of December (#771962). The issue and the various options for fixing it have been discussed on the BTS, and this seems like the best solution for now. Regards, Ferenc Wágner -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771562: Pre-approval for libetpan/1.6-1
Control: tags -1 - moreinfo Hi Ivo, On Wed, Dec 03, 2014 at 07:39:14PM +0100, Ivo De Decker wrote: Control: tags -1 moreinfo Hi, On Sun, Nov 30, 2014 at 08:04:47PM +0100, Ricardo Mones wrote: Libetpan's upstream has made a new release¹ targetted to fix POODLE breakage (CVE-2014-3566) and some other bugfixes, albeit one feature was added, hence the pre-approval request. Unfortunately it also includes a large ammount of fixed source file copyright/license headers which were missing, but now causes some noise. These were excluded from the filtered diff, but only when there were on other changes in the file, so still some there. Appart from that, most of changes not related to the above bugfixes are type or typecast fixes (which cause also a lot of noise, but still there). Diffstat summary is: 104 files changed, 1778 insertions(+), 1109 deletions(-) No soname bump, and only added symbols, which is the good part. The diff quite big, and includes a number of changes which don't comply with the freeze policy. https://release.debian.org/jessie/freeze_policy.html Yep, but the changes are mostly type fixes. New functions added won't be called by any of the library dependencies in jessie, so I don't see how they could cause trouble. A targeted fix (as a patch on top of the current version in testing, so without the new upstream) might be acceptable, but keep in mind that the deadline for fixes for important bugs is Dec 5th. I'm sorry but I have not time for preparing that for tomorrow. Unfortunately it already took a lot of time to prepare and test this one. If somebody else is willing and able to do such, I'm open and happy to accept NMUs or even give the package away. Best regards, -- Ricardo Mones ~ RTFM - Read The Manual (The 'F' is silent). Usually a very good idea. Bjarne Stroustrup signature.asc Description: Digital signature
Bug#772005: libdevice-cdio-perl: Debian patch causes Perl crashes in Device::Cdio::ISO9660::IFS's readdir: Error in `/usr/bin/perl': realloc(): invalid next size: 0x0000000001f05850
Package: libdevice-cdio-perl
Version: 0.3.0-2+b2
Severity: serious
X-Debbugs-Cc: tin...@debian.org
Hi,
(Tentatively flagging as RC as this regression breaks Tails software
that worked just fine on Wheezy. If other team members disagree, then
feel free to downgrade severity.)
The reproducer script that follows, when passed the path to Tails'
1.2.1 ISO
(http://dl.amnesia.boum.org/tails/stable/tails-i386-1.2.1/tails-i386-1.2.1.iso),
reliably crashes the interpreter with:
before readdir EFI
after readdir EFI
before readdir live
after readdir live
before readdir syslinux
after readdir syslinux
before readdir tails
after readdir tails
before readdir utils
after readdir utils
before readdir isolinux
*** Error in `/usr/bin/perl': realloc(): invalid next size:
0x01f05850 ***
Same with debian-7.2.0-amd64-i386-netinst.iso and
debian-jessie-DI-b1-amd64-netinst.iso.
If I drop 04_wrong_handling_of_output_parameters.patch, then it works
fine for me. That patch was introduced in 2007 by Tincho. I suspect
the upstream bugs it was meant to fix have been fixed in other ways
since then. Tincho, thoughts? Do you have reproducers for these bugs?
script
#!/usr/bin/perl
use strict;
use warnings FATAL = 'all';
use 5.10.1;
use Device::Cdio::ISO9660;
use Device::Cdio::ISO9660::IFS;
my $iso_obj = Device::Cdio::ISO9660::IFS-new(-source = shift);
for my $dir (qw{EFI live syslinux tails utils isolinux}) {
say STDERR before readdir $dir;
my @readdir = $iso_obj-readdir($dir);
say STDERR after readdir $dir;
my @content = map {
Device::Cdio::ISO9660::name_translate($_-{filename});
} @readdir;
}
/script
-- System Information:
Debian Release: 8.0
APT prefers unstable
APT policy: (990, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages libdevice-cdio-perl depends on:
ii libc6 2.19-13
ii libcdio13 0.83-4.2
ii libiso9660-80.83-4.2
ii perl5.20.1-3
ii perl-base [perlapi-5.20.0] 5.20.1-3
libdevice-cdio-perl recommends no packages.
libdevice-cdio-perl suggests no packages.
-- no debconf information
--
intrigeri
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769129: What's next?
On Wednesday 03 December 2014 22:02:15 Michael Tokarev wrote: Since #769129 [1] has been closed, I opened #771208 Ok, thanks. I'll follow that bug then. Cheers, Diederik -- GPG: 0x138E41915C7EFED6 signature.asc Description: This is a digitally signed message part.
Bug#708982: release-notes: keycapl/keycap is difficult to distinguish from I or | (at least in the html version)
On Jo, 04 dec 14, 06:50:48, Niels Thykier wrote: Do you have a suggestion for the .css file to fix this? CSS is not one of my strong suits, so I am hoping for suggestions. :) Same here :) Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Bug#771944: Following FusionForge 5.3 stable branch
Hi, On Wed, Dec 03, 2014 at 11:03:59PM +, Jonathan Wiltshire wrote: On Wed, Dec 03, 2014 at 06:52:26PM +0100, b...@debian.org wrote: We're (upstream-ly) maintaining a stable branch for FusionForge, called 5.3, which the Debian package currently follows. (incidentally Lolando and I are both upstream and debian devs) We're currently pushing only bugfixes to this branch (some of them qualify as RC, some don't), because it's deployed at several large client installs already and we want to make sure we don't break anything. It makes sense that users benefit from the quality of this branch, so we'd like to know to what extent following this branch is compatible with the Freeze. The compatibility benchmark you need to meet is the freeze policy, which you can find at https://release.debian.org/jessie/freeze_policy.html. If there are exceptional circumstances it's worth asking on a case-by-case basis. I already read the policy, and since it sounds sensible to follow the upstream Stable branch for the debian Stable release, I'm asking. So, I take it we need to maintain a branch off the upstream stable branch, that will not include most user-related bugfixes (but include the piupart-related nitpicks ;))? (Btw, by all means I suggest you improve your communication. This no_greetings+RTFM answer you just gave is as close to my support team's initial auto-reply as one can be :/) Cheers! Sylvain -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772001: ITP: ruby-rails-assets-perfect-scrollbar -- Tiny but perfect jQuery scrollbar plugin
Control: reassign -1 wnpp On Jo, 04 dec 14, 15:16:30, Syam G Krishnan wrote: package: perfect-scrollbar Severity: wishlist Owner: 'syam' syamg...@gmail.com *Package Name : perfect-scrollbar Version : 2.1.2 Upstream Author : Hyunje Alex Jun (Author name/s of the Gem). *URL : https://github.com/noraesae/perfect-scrollbar (Link to the git repo of the Gem) *License : MIT *Description : Tiny but perfect jQuery scrollbar plugin I am packaging perfect-scrollbar as it is a dependency of rails-assets (#691181) which is a dependency of diaspora (#597093) -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Bug#614569: [Pkg-openldap-devel] Bug#614569: RFS: Bug#614569: slapd fails to dump/reload partial replica -- NMU sponsor needed
On Wednesday 03 December 2014 18:21:08 Ryan Tandy wrote: On Wed, Dec 03, 2014 at 11:40:24PM +0100, Ferenc Wagner wrote: I got pre-approval on #771962: the upload will be unblocked, provided it's in unstable by Monday the 8th of December. People with upload rights, if you can spare a minute please review the above change and consider sponsoring the upload! Actually, review is welcome from anybody. :) Thanks very much for working on this, and the debdiff looks fine (but I haven't actually built or tested it). I hope you can find a sponsor in time. Luca, are you reading? I was following the discussion, and I have to say that I am not too comfortable in uploading this NMU at this point of the release cycle. So NACK on my side. My main concerns are: * I am not sure that I grok all the implications of that. I suspect that most of our (overly) complex pre/postinst scripts makes some assumption on schema/db consistency, at least implicitly. * We are changing the default behavior to fix a single-case situation, by removing a safety check. Mmmh... * This bug has been open since some time, never marked as RC, put on low-priority by the maintainer and upstream discouraged dropping the -s. * This is not even the proper solution, just a quick-hack patch. Moreover, I don't consider myself an LDAP expert, but I have some comments on the issue: * I would say that requiring/checking schema integrity across upgrade is a good general measure, and we should NOT work around that. Fail early, fail loudly. * IIRC disabling schemachecking is heavily discouraged. We don't offer that option in debconf. I assume the admin are really aware of the setup, and know its quirk. * Workarounds for the specific corner case exists, but maybe are a bit undocumented. So my alternative suggestion is: let's make it explicit that we value schema integrity, and we rely on it across upgrades; let's put a point in the release notes to document how to workaround this partial replica scenario; let's try to address this better in the next point release. Cheers, Luca -- .''`. ** Debian GNU/Linux ** | Luca Bruno (kaeso) : :' : The Universal O.S.| lucab (AT) debian.org `. `'` | GPG Key ID: 0x4F3BBEBF `- http://www.debian.org | Debian GNU/Linux Developer signature.asc Description: This is a digitally signed message part.
Bug#722611: mutt: segfaults when sending with SMTP
Matteo, I did miss this bugreport since it doesn't notify the new maintainer when the bug is reassigned. Did you or could you please report this to the upstream bugzilla? I have a little free time right now, so that would be very helpful. Cheers, Ondrej On Mon, Nov 24, 2014, at 23:36, Matteo Cypriani wrote: Hi there, On Wed, 11 Jun 2014 16:56:07 -0400, Matteo Cypriani m...@lm7.fr wrote: After all it *looks* indeed like it's a bug in libsasl. The bug occurs when trying to send an email with mutt via SMTP and the DIGEST-MD5 authentication, because free_rc4() (from plugins/digestmd5.c) is called twice: once when mutt calls sasl_client_step(), and once when it calls sasl_dispose(). I'm attaching a file with the most important steps of my gdb session (this time I rebuilt mutt and libsasl with nostrip to have all the symbols). I'm also attaching a patch that fixes the problem for me, but please don't blindly apply it: I really don't know what I'm doing! Maybe the pointers should be set to NULL elsewhere, or maybe free_rc4() shouldn't be called twice in the first place, I'm not familiar enough with the code to tell. Did anybody have time to look into this? I would very much like to see this problem fixed in jessie. I think it would be possible to obtain an unblock exception if the upload is prepared soon. Cheers, Matteo ___ Pkg-cyrus-sasl2-debian-devel mailing list pkg-cyrus-sasl2-debian-de...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-cyrus-sasl2-debian-devel Email had 1 attachment: + Attachment1.2 1k (application/pgp-signature) -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772006: python-clang-3.6: wrong library version in cindex.py
Package: python-clang-3.6 Version: 1:3.6~svn218612-1 Severity: important Tags: patch Dear Maintainer, The current version of this package try to use 'libclang-3.5.so' but in this version of the libclang library the symbol 'clang_Cursor_getMangling' does not exists. This cause an exception at the import time of the module cindex. I see two way's to fix this problem. 1. remove the 'clang_Cursor_GetMangling' function from the functionlist in cindex.py to avoid accessing the symbol. 2. change the library to 'libclang-3.6.so' where the symbol is defined. I prefer the latter one, this works fine for me. -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python-clang-3.6 depends on: ii python 2.7.8-2 python-clang-3.6 recommends no packages. python-clang-3.6 suggests no packages. -- no debconf information --- cindex.py 2014-12-03 22:36:52.0 +0100 +++ /usr/lib/python2.7/dist-packages/clang/cindex.py 2014-12-02 11:33:45.819870140 +0100 @@ -3457,7 +3457,7 @@ elif name == 'Windows': file = 'libclang.dll' else: -file = 'libclang-3.5.so' +file = 'libclang-3.6.so' if Config.library_path: file = Config.library_path + '/' + file signature.asc Description: Digital signature
Bug#712838: RFP: gnss-sdr -- An Open Source Global Navigation Satellite System Software Defined Receiver
Update: * Package name : gnss-sdr Version : 0.0.5 Upstream Author : Carles Fernandez carles.fernan...@cttc.es * URL :http://gnss-sdr.org/ * License : GPL Programming Lang: C++ Description : Global Navigation Satellite Systems Software Defined Receiver The source code is available at git://github.com/gnss-sdr/gnss-sdr -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771619: fusionforge: plugin postinst script uses 'service' instead of invoke-rc.d
Hi, I'm going to fix the bug but... by all means, can you postpone these piuparts tests? I appreciate the effort you put into this, but doing them during the freeze make them very ill-suited for a proper (upstream) fix, especially considering we revamped the buildinstall system completely for the next version. Also getting a RC bug with copy/paste first thing on Monday morning, for something no human user ever reported, just makes me want to stop my Debian packaging work. Regards, Sylvain -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772007: unblock: apt-cacher-ng/0.8.0-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package apt-cacher-ng
there is a trivial but nasty bug in the Debian packaging. No upstream
changes and source-only upload; no build trouble anywhere (except for a
bogus warning on armhf only which I consider a compiler bug, and it has
existed before).
The bug was not reported as serious but I tend to consider it a such one
since it impacts the log rotation and might cause hidden disk space
consumption and probably loss of log data.
debdiff:
File lists identical (after any substitutions)
Control files: lines which differ (wdiff format)
Version: [-0.8.0-1-] {+0.8.0-3+}
And git diff debian/0.8.0-1 debian/0.8.0-3 :
diff --git a/debian/apt-cacher-ng.logrotate b/debian/apt-cacher-ng.logrotate
index 1122f8f..1adf759 100644
--- a/debian/apt-cacher-ng.logrotate
+++ b/debian/apt-cacher-ng.logrotate
@@ -8,7 +8,9 @@
notifempty
create
postrotate
-if [ -s /var/run/apt-cacher-ng/pid ] ; then
+if [ -e /run/systemd/system ] ; then
+systemctl is-active apt-cacher-ng systemctl kill
--signal=USR1 apt-cacher-ng
+elif [ -s /var/run/apt-cacher-ng/pid ] ; then
kill -s USR1 $(cat /var/run/apt-cacher-ng/pid)
fi
endscript
@@ -24,7 +26,9 @@
notifempty
create
postrotate
-if [ -s /var/run/apt-cacher-ng/pid ] ; then
+if [ -e /run/systemd/system ] ; then
+systemctl is-active apt-cacher-ng systemctl kill
--signal=USR1 apt-cacher-ng
+elif [ -s /var/run/apt-cacher-ng/pid ] ; then
kill -s USR1 $(cat /var/run/apt-cacher-ng/pid)
fi
endscript
diff --git a/debian/changelog b/debian/changelog
index afc3766..bddd009 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,18 @@
+apt-cacher-ng (0.8.0-3) unstable; urgency=medium
+
+ * Restored build-dependency on libsystemd-daemond-dev since upstream source
+didn't cope with that change (yet)
+
+ -- Eduard Bloch bl...@debian.org Fri, 28 Nov 2014 21:05:16 +0100
+
+apt-cacher-ng (0.8.0-2) unstable; urgency=medium
+
+ * Send SIGUSR1 properly to reopen the logs when controlled by systemd
+(closes: Bug#77)
+ * replace build-dependency on transitional package libsystemd-daemond-dev
+
+ -- Eduard Bloch bl...@debian.org Fri, 28 Nov 2014 08:14:54 +0100
+
apt-cacher-ng (0.8.0-1) unstable; urgency=medium
* New upstream version
unblock apt-cacher-ng/0.8.0-2
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.12.31+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--
Angela Merkel zitiere ich ja am liebsten wörtlich. Ich hab noch keine
bessere Möglichkeit gefunden, diese Frau zu beleidigen.
-- Volker Pispers
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771902: claws-mail: Printing with default settings results in unreadable printouts probably due to monospace
Control: tags -1 moreinfo unreproducible Hi, On Wed, Dec 03, 2014 at 12:21:59PM +0100, bugreporter wrote: Package: claws-mail Version: 3.11.1-2 Severity: normal Dear Maintainer, we have to print out any of our mails. Currently the printouts were noti in a good shape (Text partly missing, unintended linefeeds). This happens on Virtual-PDF Printers an physical attached HP Officejet Pro 8600 Just tested here printing to PDF and they're printed as seen on Claws Mail message view, nothing strange. Without an actual example I can't say more. After fiddling around for a while i found a way to correct this problem. Setting an other type than monospace in the Settings for View/Printout e.g. to Arial solves the problem. Is that a Claws Mail configuration setting or something else? Try to launch it with an english locale to get the exact names, e.g.: Run “env LC_MESSAGES=C /usr/bin/claws-mail” in a terminal. I canÂt figure out if this problem ist related only to claws-mal, or even to cups or anything else. The problem is reproducable here on two machines. Maybe anyone else can reproduce it? Well, I can't, so I'd say is some misconfiguration of your printing subsystem, not a Claws Mail issue. regards, -- Ricardo Mones ~ Physics is like sex: sure, it may give some practical results, but that's not why we do it.Richard Feynman signature.asc Description: Digital signature
Bug#770461: upowerd become crazy after plug in my laptop
I've experienced the same problem (I believe) as Mourad. My computer became totally unresponsive, however after a few minutes I managed to launch iotop and saw that upowerd was swapping like crazy - I deduce that it was a symptom of a memory leak. Just the thing that was fixed in 0.99.1-3.1: upower (0.99.1-3.1) unstable; urgency=medium * Non-maintainer upload. * debian/patches/git-fix-memleak.patch - Memleak fix. Taken from upstream git head, commit 4221835f (Closes: #766762). -- Michael Banck mbanck@d.o Fri, 28 Nov 2014 16:24:34 +0100 After upgrading to 0.99.1-3.1, just as with Mourad, my laptop has remained quiet and well. I think it'd be good to ask the release managers to let 0.99.1-3.1 propagate to jessie. Has anybody asked them yet to let 0.99.1-3.1 propagate to jessie? Otherwise I'd ask them to do so. ? *t PS: thank you Michael for finding and patching the problem! On Thu, 4 Dec 2014, newbee...@nativobject.net wrote: Le 04/12/2014 00:26, Tomas Pospisek a écrit : Hello, you wrote: After standby cycle, using the laptop, and plugged it to power, upowerd become crazy and start to consume more and more memory and 100% of a cpu ! I think this might have been fixed in 0.99.1-3.1 : http://metadata.ftp-master.debian.org/changelogs//main/u/upower/upower_0.99.1-3.1_changelog Could you please try out that version and report back here, if it fixes the problem? *t Yes, I also think so... It never happened since the last update and I heavly using standby mode. Regards Mourad
Bug#772008: libmpfr4: buffer overflow in mpfr_strtofr
Package: libmpfr4 Version: 3.1.2-1+b1 Severity: grave Tags: security Justification: user security hole A buffer overflow may occur in mpfr_strtofr. This bug was actually discovered a year ago, and was a consequence of incorrect GMP documentation. For details, see the discussion: https://gmplib.org/list-archives/gmp-bugs/2013-December/003267.html A short description of the bug and a patch (which just increases the buffer size according to the new GMP documentation) is available at: http://www.mpfr.org/mpfr-3.1.2/#bugs The effects of this bug may be those of a buffer overflow. I don't know whether it can be exploitable to execute random code (I'd say that this is unlikely, but I'm not sure). I just know that a crash is possible (memory corruption detected by the glibc?) with the 32-bit ABI when alloca is disabled (alloca is not disabled by default, but note that alloca is not used in large precisions). -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages libmpfr4:amd64 depends on: ii libc6 2.19-13 ii libgmp10 2:6.0.0+dfsg-6 ii multiarch-support 2.19-13 libmpfr4:amd64 recommends no packages. libmpfr4:amd64 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#772009: acpi: Laptop Lid status (/proc/acpi/button/lid/LID0/state) on Surface Pro remains closed after first use
Package: acpi Version: 1.7-1 Severity: normal Dear Maintainer, I'am using a MS Surface Pro with Debian Jessie on it. ;-) At start a status of /proc/acpi/button/lid/LID0/state is open, but after first use it changes to closed and remains on this status until reboot. I have tested it with Debian Wheezy, Debian Jessie, Fedora 20, Fedora 21 and Ubuntu 14.10. All of them have the same behaviour. /proc/acpi/button/lid/LID0/state remains on closed. Wheezy and F20 have no reaction on closing lid, I think because of Gnome 3.10 with Energy Saving Bug. But Jessie and F21 reacts well and believes that lid stays closed. The most annoying thing is, that the notebook suspends after ca. 20 seconds after wake up. Just reboot helps. My suggestion is: A bug in button mod. It recognize a closing of lid but not the opening. But how can i disable the reaktion on lid until bug in button mod will be fixed? I have also reported in on bugzilla.kernel.org Bug:89211 Thanks for your attention -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.17.4 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages acpi depends on: ii libc6 2.19-13 acpi recommends no packages. acpi suggests no packages. -- no debconf information [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-13) ) #1 SMP Debian 3.16.7-2 (2014-11-06) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=901c317a-7e1d-4e00-a38e-88987e96261c ro quiet [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009dfff] usable [0.00] BIOS-e820: [mem 0x0009e000-0x0009] reserved [0.00] BIOS-e820: [mem 0x0010-0x1fff] usable [0.00] BIOS-e820: [mem 0x2000-0x201f] reserved [0.00] BIOS-e820: [mem 0x2020-0x40003fff] usable [0.00] BIOS-e820: [mem 0x40004000-0x40004fff] reserved [0.00] BIOS-e820: [mem 0x40005000-0xd917] usable [0.00] BIOS-e820: [mem 0xd918-0xd95f8fff] reserved [0.00] BIOS-e820: [mem 0xd95f9000-0xd9608fff] ACPI data [0.00] BIOS-e820: [mem 0xd9609000-0xda1d6fff] ACPI NVS [0.00] BIOS-e820: [mem 0xda1d7000-0xda5f3fff] reserved [0.00] BIOS-e820: [mem 0xda5f4000-0xda685fff] type 20 [0.00] BIOS-e820: [mem 0xda686000-0xda686fff] usable [0.00] BIOS-e820: [mem 0xda687000-0xda6c9fff] ACPI NVS [0.00] BIOS-e820: [mem 0xda6ca000-0xdad54fff] usable [0.00] BIOS-e820: [mem 0xdad55000-0xdaff1fff] reserved [0.00] BIOS-e820: [mem 0xdaff2000-0xdaff] usable [0.00] BIOS-e820: [mem 0xdb80-0xdf9f] reserved [0.00] BIOS-e820: [mem 0xf800-0xfbff] reserved [0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved [0.00] BIOS-e820: [mem 0xfed0-0xfed03fff] reserved [0.00] BIOS-e820: [mem 0xfed1c000-0xfed1] reserved [0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved [0.00] BIOS-e820: [mem 0xff00-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x00011f5f] usable [0.00] NX (Execute Disable) protection: active [0.00] efi: EFI v2.31 by American Megatrends [0.00] efi: ACPI=0xd95fe000 ACPI 2.0=0xd95fe000 SMBIOS=0xda5f2198 [0.00] efi: mem00: type=7, attr=0xf, range=[0x-0x00058000) (0MB) [0.00] efi: mem01: type=4, attr=0xf, range=[0x00058000-0x00059000) (0MB) [0.00] efi: mem02: type=7, attr=0xf, range=[0x00059000-0x0009e000) (0MB) [0.00] efi: mem03: type=0, attr=0xf, range=[0x0009e000-0x000a) (0MB) [0.00] efi: mem04: type=7, attr=0xf, range=[0x0010-0x0100) (15MB) [0.00] efi: mem05: type=2, attr=0xf, range=[0x0100-0x02016000) (16MB) [0.00] efi: mem06: type=7, attr=0xf, range=[0x02016000-0x2000) (479MB) [0.00] efi: mem07: type=0, attr=0xf, range=[0x2000-0x2020) (2MB) [0.00] efi: mem08: type=7, attr=0xf, range=[0x2020-0x36428000) (354MB) [0.00] efi: mem09: type=2, attr=0xf,
Bug#772010: libini4j-java: Java 8 compatibility patch does not seem correct
Package: libini4j-java
Version: 0.5.2-SNAPSHOT-4
Severity: important
I noticed that 01-java8-compatibility.patch seems wrong to me. And not only me,
please have a look at https://bugzilla.redhat.com/show_bug.cgi?id=1087526#c2
Code used in RedHat patch seems more correct to me.
https://kojipkgs.fedoraproject.org//packages/ini4j/0.5.1/12.fc21/src/ini4j-0.5.1-12.fc21.src.rpm
-return (sec == null) ? null : sec.remove(optionName);
+if (sec == null) {
+return false;
+}
+if (sec.containsKey(optionName)) {
+sec.remove(optionName);
+return true;
+}
+return false;
Regards,
Tomas
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772011: ITP: kafkacat -- generic producer and consumer for Apache Kafka
Package: wnpp Severity: wishlist Owner: Vincent Bernat ber...@debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 * Package name: kafkacat Version : 1.0.0 Upstream Author : Magnus Edenhill mag...@edenhill.se * URL : https://github.com/edenhill/kafkacat * License : BSD Programming Lang: C Description : generic producer and consumer for Apache Kafka kafkacat is a generic non-JVM producer and consumer for Apache Kafka 0.8, think of it as a netcat for Kafka. In producer mode kafkacat reads messages from stdin, delimited with a configurable delimeter and produces them to the provided Kafka cluster, topic and partition. In consumer mode kafkacat reads messages from a topic and partition and prints them to stdout using the configured message delimiter. kafkacat also features a Metadata list mode to display the current state of the Kafka cluster and its topics and partitions. -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUgD4eAAoJEJWkL+g1NSX5eA8P/i9LyGFu9YcztDLP3OGwF7wC wtEZdSEtbiCusukoSsfbcqR0fMqD5WHt7fe6kDYcxMUkP5nr2RVfuAVf8fLXLxPx ADzvG7T0C5b8/TTFaIJLjj6HY6D5bHVm+9g+6sF04mWwfIc1Ypfd/utd4fiPpwJP oT779du25cEqiIkcTBHVIm2opiAJ4t7RGh4DFHW43JV47V+RjbihEUOVfdgoM+LM twDJBK3sxHIq6i9cMazP03BYVvuvUvGJi3iyX5BZTcI/uODmic7A/Mmwppa5eGF0 CO+D7tReKlIEkI0IlxLwNSr+ltqHrY1CM6MtfMv4mbJTHE4LcnmS9tI40EEHVdOm v5zgWkB0Qy7HPmAsvYQWuyfmB3Bkotzz6UPudpT7SgE7HkbzibpMrcamE0WdfcHm dY5LhgveN+IrE+EV8cKdWNKMSXiX5AXF1zfq0civh2j7qHDqiUQ5b00kpQqjwTCY z3l7A3IYwzetChOvKzL+TQOVvGKYu/GsYwWoH6GfAmt0e5OexYL7Ygvrk25YyRG4 8LTybcRSsOYeWUdr19M0WGWXyPeC9c3sEOSlsk+6l32K2s0MOo+xo9Jhg5RQ1kIo q3mXLaJ489zSHBsV++cAP2bnFg4H4hlYFTPDa1xuNWt1wPZ0fhZ3l+dD1wf+742l nGNXR6pu55cSy1P2dfvK =Zd5p -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#770461: upowerd become crazy after plug in my laptop
Hi, On Thu, Dec 04, 2014 at 11:37:48AM +0100, Tomas Pospisek wrote: Has anybody asked them yet to let 0.99.1-3.1 propagate to jessie? Well, I had a look at it the other day but then noticed that our awesome-as-usual release team had already put an unblock request into place, see https://packages.qa.debian.org/u/upower.html Ignoring block request by freeze, due to unblock request by jcristau. So it should hit testing tomorrow or the day after. Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771208: unblock: busybox/1:1.22.0-14
On Thu, 27 Nov 2014 17:00:03 +0100 Cyril Brulebois k...@debian.org wrote: (Putting on my d-i RM fedora.) #768876 is tagged jessie-ignore so I'm really unconvinced by the debian/rules changes. At this stage, I'd rather see the security fix only. Wouldn't that entail that #769190 would NOT be fixed for jessie? I realize that important != RC, but a not properly working busybox-static in jessie would be a real bummer (imo). Cheers, Diederik -- GPG: 0x138E41915C7EFED6 signature.asc Description: This is a digitally signed message part.
Bug#771825: release-notes: Update information on non-systemd Jessie upgrades and installations
On Wed, 2014-12-03 at 22:07 +0100, Niels Thykier wrote: On 2014-12-03 11:56, Svante Signell wrote: On Tue, 2014-12-02 at 23:01 +0100, Svante Signell wrote: [...] Index: en/issues.dbk === --- en/issues.dbk (revision 10513) +++ en/issues.dbk (working copy) @@ -183,7 +183,7 @@ role=packagesysvinit-core/systemitem or systemitem role=packageupstart/systemitem, it is recommended to setup APT pinning prior to the upgrade. As an example, to prevent -systemitem role=packagesystemd/systemitem from being +systemitem role=packagesystemd-sysv/systemitem from being Indeed, the package name is systemd-sysv. Though perhaps we should change it to systemd without marking it as a package. I presume that the user/admin is less interested in the actual package name and more in the name of the init system. Problem is: Does the pinning work if it is on systemd instead of systemd-sysv? The the pin would be about any systemd component? installed during the upgrade, you can create a file called filename/etc/apt/preferences.d/local-pin-init/filename with the following contents: @@ -193,12 +193,16 @@ Pin: release o=Debian Pin-Priority: -1 /screen - caution -para - Be advised that some packages may have degraded behaviour or - may be lacking features under a non-default init system. -/para - /caution I am not too happy with pushing the caution down. To be honest, I have been considering to push it up. Pushed up, as you wish. + note I am not entirely convinced this should be a note rather than a para. Fixed by using itemizedlist instead! +It is also good to install It is also a good idea to install ...? Fixed! +systemitem role=package sysvinit-core, sysvint and sysvinit-utils +/systemitem as the first packages when upgrading. In case +you want an emphasisas-systemd-free-as-possible/emphasis Not sure why the emphasis here. To be honest, the sentence strikes me as a bit odd (and possibly a bit long). Maybe just add it to the list above or simply just: If you have a desktop environment installed, it is also recommended to install systemd-shim to assist apt or/and aptitude with the upgrade path. Rewritten! +desktop environment, it is also recommended to install systemitem +role=packagesystemd-shim/systemitem in order to +help apt and aptitude to avoid installing systemd-sysv and +other *systemd* components, unintentionally. ^ Fixed! Why the *X*? We got emphasis if you want to highlight. Then again, see my previous remark about the entire sentence. New patch attached. Better now? Note the comment about the CTTE decision today (hopefully) about default init system on upgrades! Index: en/issues.dbk === --- en/issues.dbk (revision 10513) +++ en/issues.dbk (working copy) @@ -178,12 +178,16 @@ para Jessie ships with systemitem role=packagesystemd-sysv/systemitem as -emphasisdefault/emphasis init system. If you have a -preference for another init such as systemitem +emphasisdefault/emphasis init system. +This package is installed automatically on upgrades +emphasis(pending the CTTE decision today)/emphasis. + /para + para +If you have a preference for another init such as systemitem role=packagesysvinit-core/systemitem or systemitem role=packageupstart/systemitem, it is recommended to setup APT pinning prior to the upgrade. As an example, to prevent -systemitem role=packagesystemd/systemitem from being +systemitem role=packagesystemd-sysv/systemitem from being installed during the upgrade, you can create a file called filename/etc/apt/preferences.d/local-pin-init/filename with the following contents: @@ -193,6 +197,11 @@ Pin: release o=Debian Pin-Priority: -1 /screen + para +Please note that the upgrade may install packages containing +systemd in their name even with APT pinning. These alone do +emphasisnot/emphasis change your init system. + /para caution para Be advised that some packages may have degraded behaviour or @@ -199,14 +208,32 @@ may be lacking features under a non-default init system. /para /caution + itemizedlist + listitem para -Please note that the upgrade may install packages containing -systemd in their name even with APT pinning. These alone do -emphasisnot/emphasis change your init system. To use -systemd as your init system, the systemitem -role=packagesystemd-sysv/systemitem package must be -installed first. +It is also a good idea to install +systemitem role=package sysvinit-core, sysvint and sysvinit-utils +/systemitem as the first packages when upgrading. /para + /listitem + listitem
Bug#766670: RC bug in stable and oldstable for getmail4
Hi Osamu, On Fri, 28 Nov 2014, Osamu Aoki wrote: Although I am not comfortable to package this way if I do it again (I inherited it and did not touch it back then.), I should do the same strange packaging style again considering oldstable update if I do. Not really, if you switch to a new upstream version, it's certainly fine to start with the latest packaging and just fix up things so that they work in squeeze. Neither python-support nor dh_python2 are a strong requirement. Sure the debdiff will mean nothing but as long as you tested that an upgrade works, and that the package still runs, it's good enough IMO. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772012: ltsp-server-standalone: Screen saver (dim screen) does not work anymore
Package: ltsp-server-standalone Version: 5.5.4-1 Severity: normal Since the upgrade to jessie the screen does not automatically switch off/dim when inactive, even though this is enabled in the power settings of gnome 3.14. This setting worked in wheezy and works in jessie without ltsp, but not in our ltsp fat client configuration. This is bad for the environment! (and therefore serious) :-) thanks Florian -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772013: unblock (pre-approval): debian-edu-artwork/0.52-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please consider unblocking of package to-be-uploaded debian-edu-artwork The Debian Edu team would like to bring an upgraded debian-edu-artwork version to jessie. Gains of this new version are: o Debian Edu's login background (spacefun theme) has been re-rendered and greatly improved. This is important for people that use the Debian Edu spacefun theme on machines running Debian jessie with LightDM as login manager. o We managed to greatly reduce the src:package size and the bin:package size of debian-edu-artwork-spacefun. See below. File sizes in 0.51-1 -rw-r--r-- 1 mike mike23430 Dez 4 11:43 debian-edu-artwork_0.51-1_all.deb -rw-r--r-- 1 mike mike18516 Dez 4 11:33 debian-edu-artwork_0.51-1.debian.tar.xz -rw-r--r-- 1 mike mike 1605 Dez 4 11:33 debian-edu-artwork_0.51-1.dsc -rw-r--r-- 1 mike mike 54718108 Dez 4 11:31 debian-edu-artwork_0.51.orig.tar.xz -rw-r--r-- 1 mike mike 7443962 Dez 4 11:43 debian-edu-artwork-joy_0.51-1_all.deb -rw-r--r-- 1 mike mike 3182928 Dez 4 11:43 debian-edu-artwork-lines_0.51-1_all.deb -rw-r--r-- 1 mike mike 43285974 Dez 4 11:43 debian-edu-artwork-spacefun_0.51-1_all.deb File sizes in 0.52-1 -rw-rw-r-- 1 mike mike 18264 Dez 4 11:20 debian-edu-artwork_0.52-1_all.deb -rw-rw-r-- 1 mike mike 3243 Dez 4 11:20 debian-edu-artwork_0.52-1_amd64.changes -rw-rw-r-- 1 mike mike 18668 Dez 4 11:10 debian-edu-artwork_0.52-1.debian.tar.xz -rw-rw-r-- 1 mike mike 1605 Dez 4 11:10 debian-edu-artwork_0.52-1.dsc -rw-rw-r-- 1 mike mike 31329888 Dez 4 11:10 debian-edu-artwork_0.52.orig.tar.xz -rw-rw-r-- 1 mike mike7439340 Dez 4 11:20 debian-edu-artwork-joy_0.52-1_all.deb -rw-rw-r-- 1 mike mike3178104 Dez 4 11:20 debian-edu-artwork-lines_0.52-1_all.deb -rw-rw-r-- 1 mike mike 13654584 Dez 4 11:20 debian-edu-artwork-spacefun_0.52-1_all.deb A filtered .debdiff (filtered to reduce patch size from 10mb) has been attached to this mail. The filter command that has been used is shown below: $ cat debian-edu-artwork_0.51-1_0.52-1.debdiff | filterdiff -x *.svg -x *.png unblock debian-edu-artwork/0.52-1 -- System Information: Debian Release: jessie/sid APT prefers stable APT policy: (990, 'stable'), (500, 'testing-updates'), (500, 'testing-proposed-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-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 Binärdateien /tmp/7MSedjAtR1/debian-edu-artwork-0.51/art-lines/splash/debian-edu-lines-splash.png und /tmp/dYni8EIh_r/debian-edu-artwork-0.52/art-lines/splash/debian-edu-lines-splash.png sind verschieden. Binärdateien /tmp/7MSedjAtR1/debian-edu-artwork-0.51/art-spacefun/kde/1280x1024.png und /tmp/dYni8EIh_r/debian-edu-artwork-0.52/art-spacefun/kde/1280x1024.png sind verschieden. Binärdateien /tmp/7MSedjAtR1/debian-edu-artwork-0.51/art-spacefun/kde/1600x1200.png und /tmp/dYni8EIh_r/debian-edu-artwork-0.52/art-spacefun/kde/1600x1200.png sind verschieden. Binärdateien /tmp/7MSedjAtR1/debian-edu-artwork-0.51/art-spacefun/kde/1920x1080.png und /tmp/dYni8EIh_r/debian-edu-artwork-0.52/art-spacefun/kde/1920x1080.png sind verschieden. Binärdateien /tmp/7MSedjAtR1/debian-edu-artwork-0.51/art-spacefun/kde/1920x1200.png und /tmp/dYni8EIh_r/debian-edu-artwork-0.52/art-spacefun/kde/1920x1200.png sind verschieden. Binärdateien /tmp/7MSedjAtR1/debian-edu-artwork-0.51/art-spacefun/kde/800x600.png und /tmp/dYni8EIh_r/debian-edu-artwork-0.52/art-spacefun/kde/800x600.png sind verschieden. Binärdateien /tmp/7MSedjAtR1/debian-edu-artwork-0.51/art-spacefun/kde/debian-edu-spacefun-wallpaper01_1280x1024.png und /tmp/dYni8EIh_r/debian-edu-artwork-0.52/art-spacefun/kde/debian-edu-spacefun-wallpaper01_1280x1024.png sind verschieden. diff -Nru debian-edu-artwork-0.51/art-spacefun/kde/debian-edu-spacefun-wallpaper01_1280x1024.svg debian-edu-artwork-0.52/art-spacefun/kde/debian-edu-spacefun-wallpaper01_1280x1024.svg Binärdateien /tmp/7MSedjAtR1/debian-edu-artwork-0.51/art-spacefun/kde/debian-edu-spacefun-wallpaper01_1600x1200.png und /tmp/dYni8EIh_r/debian-edu-artwork-0.52/art-spacefun/kde/debian-edu-spacefun-wallpaper01_1600x1200.png sind verschieden. diff -Nru debian-edu-artwork-0.51/art-spacefun/kde/debian-edu-spacefun-wallpaper01_1600x1200.svg debian-edu-artwork-0.52/art-spacefun/kde/debian-edu-spacefun-wallpaper01_1600x1200.svg Binärdateien /tmp/7MSedjAtR1/debian-edu-artwork-0.51/art-spacefun/kde/debian-edu-spacefun-wallpaper01_1920x1080.png und /tmp/dYni8EIh_r/debian-edu-artwork-0.52/art-spacefun/kde/debian-edu-spacefun-wallpaper01_1920x1080.png sind verschieden. diff -Nru debian-edu-artwork-0.51/art-spacefun/kde/debian-edu-spacefun-wallpaper01_1920x1080.svg
Bug#771908: unblock: phamm/0.6.2-1.1
Control: tags -1 + moreinfo Control: retitle -1 unblock: phamm/0.6.2-1.2 Version 0.6.2-1.2 of phamm was just uploaded with the change you request. I'll remove the moreinfo tag and post the new diff when it's in the archive. signature.asc Description: OpenPGP digital signature
Bug#772014: atril cannot open multiple files
Package: atril Severity: important Version: 1.8.1+dfsg1-2 Tag: upstream patch Quoting initial post on https://github.com/mate-desktop/atril/issues/86: When I open multiple files (select 2-3 documents, right click and Open with Document Viewer) The first document opens but the second (third, ...) document does not open. Here is what it looks like - https://cdn.mediacru.sh/qqPfryh7AzpS.png At first I though there must be a work around, but someone pointed out that its a bug. Hope this helps to fix the problem. This issue is present in Debian jessie and fixed by upstream. Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgp58OBcLV14a.pgp Description: Digitale PGP-Signatur
Bug#586751: are you still experiencing the reported bug?
I don't know whether this bug should be closed, but at this moment we are unable to verify whether this problem still persists. *t -- Forwarded message -- Date: Thu, 04 Dec 2014 11:10:43 +0100 From: Joost Yervante Damad Subject: Re: are you still experiencing the reported bug? On 14-12-04 at 07:34AM +0100, Joost Yervante Damad wrote: Hey Tomas, I don't really know. Joost On 12/04/2014 12:49 AM, Tomas Pospisek wrote: Hello Joost, you reported bug http://bugs.debian.org/586751 against a version of upower older than the one currently found in Debian jessie. In case you are running the latest upower version from Debian jessie, could you please test if you still experience the problem? It would be nice if you could test and reply, so this bug could be marked as fixed in jessie and closed. Btw. did you report this upstream? It looked like upstream was very responsive, so he might have fixed this quickly? Thanks, On 12/04/2014 11:05 AM, Tomas Pospisek wrote: Hello Joost, I suppose you do not have access to HW in question any more, right? Yup. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762194: Summary:Re: Bug#762194: Proposal for upgrades to jessie
On Fri, 2014-11-28 at 12:56 +0100, Svante Signell wrote: Hello, In summary: a) Upgrades should _not_ change init: whatever is installed should be kept. b) New installs should get systemd-sysv as default init with a debconf message about alternative init systems. More detailed: 1) Fix debootstrap bugs 2) Add a (non-aborting) debconf message referring to release-notes on how to install sysvinit-core when installing from scratch. 3) Add information in release-notes on how to: - Upgrade from stable/testing/sid to jessie to avoid getting systemd-sysv installed (this should not strictly be needed if the ctte chooses to decide that upgrades will _not_ switch init) - Install sysvinit-core after installation and reboot after getting systemd-sysv as default. 3.1) I'll file a bug against release-notes as written above. Hopefully the ctte will make a decision on init system for upgrades to Jessie today! FYI: Bugs for release-notes on upgrades, #771825, and installation-guide (and perhaps debian wiki) on new installs (pending), are in the pipe! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772010: libini4j-java: Java 8 compatibility patch does not seem correct
Hi Tomas, Thank you very much for forwarding this issue, it could have been easily detected if the tests weren't disabled. I'll upload a new version shortly. Emmanuel Bourg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#586751: are you still experiencing the reported bug? (fwd)
Hello Richard, is there anything we can do about this? See also these: http://bugs.debian.org/586751 http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=34;bug=586751 *t -- Forwarded message -- Date: Thu, 4 Dec 2014 12:20:45 +0100 (CET) From: Tomas Pospisek To: 586...@bugs.debian.org Subject: Re: are you still experiencing the reported bug? I don't know whether this bug should be closed, but at this moment we are unable to verify whether this problem still persists. *t -- Forwarded message -- Date: Thu, 04 Dec 2014 11:10:43 +0100 From: Joost Yervante Damad Subject: Re: are you still experiencing the reported bug? On 14-12-04 at 07:34AM +0100, Joost Yervante Damad wrote: Hey Tomas, I don't really know. Joost On 12/04/2014 12:49 AM, Tomas Pospisek wrote: Hello Joost, you reported bug http://bugs.debian.org/586751 against a version of upower older than the one currently found in Debian jessie. In case you are running the latest upower version from Debian jessie, could you please test if you still experience the problem? It would be nice if you could test and reply, so this bug could be marked as fixed in jessie and closed. Btw. did you report this upstream? It looked like upstream was very responsive, so he might have fixed this quickly? Thanks, On 12/04/2014 11:05 AM, Tomas Pospisek wrote: Hello Joost, I suppose you do not have access to HW in question any more, right? Yup. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732209: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.
Hi, BTW, this only happens with GNOME sessions. With other window managers (e.g. LXDE, Openbox) it does *not*. Therefore, I do not think it's a systemd bug, rather it's related to GNOME. Do you agree to reassign this bug against either the 'gnome-session' or the 'gnome-shell' package? No, I don't agree. I can reproduce it 100% in MATE desktop environment and also in Cinnamon, see [1]. I'm actually thinking of merging that bug report with this one. Please read the comments from Linas Vepstas there, they confirm that it's not a desktop environment or a text editor itself that causes it. Also, systemd had been messing up the ownership of /run/user/1000/dconf/user in the past, see [2]. [1] https://bugs.debian.org/766464 [2] https://bugs.debian.org/731300
Bug#755475: gnome-shell-common: since 3.12 components entered testing, gnome-shell breaks GDM
On Thu, 4 Dec 2014, Josselin Mouette wrote: Hi Tomas, Tomas Pospisek t...@sourcepole.ch wrote: Would it be a good idea to set thighter package interdependencies or, at least, put a Breaks: gdm ( 3.12) to upower? Agreed. Reassigning. Seeing that gdm3 in wheezy was 3.4.1-8 and that everybody is going to update to gdm3 = 3.14.1-3 for jessie or the versions in jessie anyway I'm not sure this is required? Is there some specific scenario where users would be running with unreleased, older gdm3's? Well, partial upgrades are not “supported” per se, but they are expected not to leave your system in an unusable state, so when there’s a lockstep upgrade we should match it in the dependencies. Agreed. But I do not think the release team will allow a new version of upower to migrate to jessie because it fixes such a (IMHO) minor issue? Do you think they will? And once jessie is released then really I can't see much sense of adding that information either because by then you'll allready be running upower and gdm3 from jessie and so this becomes a non-issue? I.e. it becomes a pure formality without any real impact or effect. ? *t
Bug#772015: unblock: atril/1.8.1+dfsg1-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package atril
Atril 1.8.1+dsfg1-3 fixes #772014. When selecting multiple document files
in Caja (filebrowser) you can now open them all by right-click - Open in
Document Viewer. In previous versions of atril, only the first document
got opened.
unblock atril/1.8.1+dfsg1-3
-- System Information:
Debian Release: jessie/sid
APT prefers stable
APT policy: (990, 'stable'), (500, 'testing-updates'), (500,
'testing-proposed-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-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
diff -Nru atril-1.8.1+dfsg1/debian/changelog atril-1.8.1+dfsg1/debian/changelog
--- atril-1.8.1+dfsg1/debian/changelog 2014-10-25 18:45:13.0 +0200
+++ atril-1.8.1+dfsg1/debian/changelog 2014-12-04 12:32:40.0 +0100
@@ -1,3 +1,11 @@
+atril (1.8.1+dfsg1-3) unstable; urgency=medium
+
+ * debian/patches:
++ Add 0001_open-multiple-files.patch. Allow selecting multiple files
+ and opening them in Atril. (Closes: #772014).
+
+ -- Mike Gabriel sunwea...@debian.org Thu, 04 Dec 2014 12:32:18 +0100
+
atril (1.8.1+dfsg1-2) unstable; urgency=medium
[ Vangelis Mouhtsis ]
diff -Nru atril-1.8.1+dfsg1/debian/patches/0001_open-multiple-files.patch atril-1.8.1+dfsg1/debian/patches/0001_open-multiple-files.patch
--- atril-1.8.1+dfsg1/debian/patches/0001_open-multiple-files.patch 1970-01-01 01:00:00.0 +0100
+++ atril-1.8.1+dfsg1/debian/patches/0001_open-multiple-files.patch 2014-12-04 12:26:34.0 +0100
@@ -0,0 +1,48 @@
+From cee6caa16804a4c4b539518b37d81c1470ca9270 Mon Sep 17 00:00:00 2001
+From: Stefano Karapetsas stef...@karapetsas.com
+Date: Mon, 13 Oct 2014 16:20:51 +0200
+Subject: [PATCH] Uses g_app_info_launch_uris instead of g_app_info_launch to
+ spawn other sessions
+
+Closes https://github.com/mate-desktop/atril/issues/86
+
+Solution comes from evince code
+---
+ shell/ev-application.c | 12 +---
+ 1 file changed, 9 insertions(+), 3 deletions(-)
+
+diff --git a/shell/ev-application.c b/shell/ev-application.c
+index 220519d..da6366f 100644
+--- a/shell/ev-application.c
b/shell/ev-application.c
+@@ -282,12 +282,13 @@ ev_spawn (const char *uri,
+ break;
+ }
+
+- g_string_append_printf (cmd, %s, uri);
+-
+ cmdline = g_string_free (cmd, FALSE);
+ app = g_app_info_create_from_commandline (cmdline, NULL, 0, error);
+
+ if (app != NULL) {
++ GList uri_list;
++ GList *uris = NULL;
++
+ #if GTK_CHECK_VERSION (3, 0, 0)
+ ctx = gdk_display_get_app_launch_context (gdk_screen_get_display (screen));
+ #else
+@@ -297,7 +298,12 @@ ev_spawn (const char *uri,
+ gdk_app_launch_context_set_screen (ctx, screen);
+ gdk_app_launch_context_set_timestamp (ctx, timestamp);
+
+- g_app_info_launch (app, NULL, G_APP_LAUNCH_CONTEXT (ctx), error);
++ if (uri) {
++ uri_list.data = (gchar *)uri;
++ uri_list.prev = uri_list.next = NULL;
++ uris = uri_list;
++ }
++ g_app_info_launch_uris (app, uris, G_APP_LAUNCH_CONTEXT (ctx), error);
+
+ g_object_unref (app);
+ g_object_unref (ctx);
+
diff -Nru atril-1.8.1+dfsg1/debian/patches/series atril-1.8.1+dfsg1/debian/patches/series
--- atril-1.8.1+dfsg1/debian/patches/series 2014-10-04 00:47:47.0 +0200
+++ atril-1.8.1+dfsg1/debian/patches/series 2014-12-04 12:26:34.0 +0100
@@ -1 +1,2 @@
+0001_open-multiple-files.patch
2001_omit-gfdl-licensed-help-files.patch
Bug#772016: sqlitebrowser: When i install sqlitebrowser from apt-get i get the error: segmentation fault
Package: sqlitebrowser Version: 3.2.0-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.17-4.towo-siduction-amd64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages sqlitebrowser depends on: ii libc62.19-13 ii libgcc1 1:4.9.2-5 ii libqcustomplot1.21.2.1-3 ii libqt5core5a 5.3.2+dfsg-4+b1 ii libqt5gui5 5.3.2+dfsg-4+b1 ii libqt5network5 5.3.2+dfsg-4+b1 ii libqt5printsupport5 5.3.2+dfsg-4+b1 ii libqt5test5 5.3.2+dfsg-4+b1 ii libqt5widgets5 5.3.2+dfsg-4+b1 ii libsqlite3-0 3.8.7.2-1 ii libstdc++6 4.9.2-5 sqlitebrowser recommends no packages. sqlitebrowser 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#772017: unblock: ruby-libxml/2.7.0-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package ruby-libxml
This version fixes building against the newer libxml2 in unstable. If
that version of libxml2 gets into jessie (it was supposed to),
ruby-libxml will instanty become RC-buggy. This version will build in
both jessie and unstable.
The debdiff against the package in testing is attached.
unblock ruby-libxml/2.7.0-3
-- System Information:
Debian Release: 8.0
APT prefers buildd-unstable
APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'),
(1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--
Antonio Terceiro terce...@debian.org
diff -Nru ruby-libxml-2.7.0/debian/changelog ruby-libxml-2.7.0/debian/changelog
--- ruby-libxml-2.7.0/debian/changelog 2013-12-23 18:21:44.0 -0200
+++ ruby-libxml-2.7.0/debian/changelog 2014-12-03 21:15:18.0 -0200
@@ -1,3 +1,11 @@
+ruby-libxml (2.7.0-3) unstable; urgency=medium
+
+ * Team upload.
+ * debian/patches/libxml2-2.9.2.patch: fix tests when running against libxml2
+2.9.2 (Closes: #771217). Thanks to Colin Watson cjwat...@ubuntu.com.
+
+ -- Antonio Terceiro terce...@debian.org Wed, 03 Dec 2014 20:30:48 -0200
+
ruby-libxml (2.7.0-2) unstable; urgency=medium
* Team upload.
diff -Nru ruby-libxml-2.7.0/debian/patches/0100_run_builtin_shell_command_ulimit_in_tests.patch ruby-libxml-2.7.0/debian/patches/0100_run_builtin_shell_command_ulimit_in_tests.patch
--- ruby-libxml-2.7.0/debian/patches/0100_run_builtin_shell_command_ulimit_in_tests.patch 2013-08-29 16:17:28.0 -0300
+++ ruby-libxml-2.7.0/debian/patches/0100_run_builtin_shell_command_ulimit_in_tests.patch 2014-12-03 20:42:25.0 -0200
@@ -7,7 +7,7 @@
--- a/test/tc_parser.rb
+++ b/test/tc_parser.rb
-@@ -246,7 +246,7 @@
+@@ -246,7 +246,7 @@ class TestParser Test::Unit::TestCase
max_fd = if RUBY_PLATFORM.match(/mswin32|mingw/i)
500
else
diff -Nru ruby-libxml-2.7.0/debian/patches/libxml2-2.9.2.patch ruby-libxml-2.7.0/debian/patches/libxml2-2.9.2.patch
--- ruby-libxml-2.7.0/debian/patches/libxml2-2.9.2.patch 1969-12-31 21:00:00.0 -0300
+++ ruby-libxml-2.7.0/debian/patches/libxml2-2.9.2.patch 2014-12-03 20:40:52.0 -0200
@@ -0,0 +1,43 @@
+--- a/test/tc_parser.rb
b/test/tc_parser.rb
+@@ -302,7 +302,12 @@ class TestParser Test::Unit::TestCase
+ assert_nil(error.str2)
+ assert_nil(error.str3)
+ assert_equal(0, error.int1)
+-assert_equal(20, error.int2)
++# Versions of libxml2 before 2.9.2 calculated wrong error columns.
++if Gem::Version.new(XML::LIBXML_VERSION) Gem::Version.new('2.9.2')
++ assert_equal(20, error.int2)
++else
++ assert_equal(34, error.int2)
++end
+ assert_nil(error.node)
+ end
+
+--- a/test/tc_html_parser_context.rb
b/test/tc_html_parser_context.rb
+@@ -6,19 +6,22 @@ require 'test/unit'
+
+ class TestHtmlParserContext Test::Unit::TestCase
+ def test_default_options
++XML.default_keep_blanks = true
+ context = XML::HTMLParser::Context.new
+ assert_equal(0, context.options)
+ end
+
+ def test_no_options
++XML.default_keep_blanks = true
+ context = XML::HTMLParser::Context.new
+ context.options = 0
+ assert_equal(0, context.options)
+ end
+
+ def test_options
++XML.default_keep_blanks = true
+ context = XML::HTMLParser::Context.new
+ context.options = XML::HTMLParser::Options::NOERROR
+ assert_equal(XML::HTMLParser::Options::NOERROR, context.options)
+ end
+-end
+\ No newline at end of file
++end
diff -Nru ruby-libxml-2.7.0/debian/patches/series ruby-libxml-2.7.0/debian/patches/series
--- ruby-libxml-2.7.0/debian/patches/series 2013-08-29 16:17:28.0 -0300
+++ ruby-libxml-2.7.0/debian/patches/series 2014-12-03 20:27:46.0 -0200
@@ -1,3 +1,4 @@
0100_run_builtin_shell_command_ulimit_in_tests.patch
#fix_test_under_1.9.1
0200_do_not_overwrite_LDFLAGS.patch
+libxml2-2.9.2.patch
signature.asc
Description: Digital signature
Bug#772018: pylint: Please backport extension-pkg-whitelist support
Package: pylint Version: 1.3.1-1 Severity: important Dear Maintainer, Since the upload of python-astroid 1.2.1-2, pylint is unusable on projects using C extensions. Since this affects a number of commonly used 3rd party modules (numpy, PyQT, python-gtk, etc.) this will severely restricts the usablity of pylint in jessie. This is fixed in pylint 1.4 and astroid 1.3.2 with the following patches: https://bitbucket.org/logilab/astroid/commits/afea46c03809 https://bitbucket.org/logilab/pylint/commits/5733254372ed This issue has already previously mentioned in #591676 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591676#60 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pylint depends on: ii python 2.7.8-2 ii python-astroid 1.2.1-2 ii python-logilab-common 0.62.0-1 pn python:any none Versions of packages pylint recommends: ii python-tk 2.7.8-2+b1 pylint 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#771991: libldb1: New version 1.1.18-1 break other package (samba-libs)
Hi, Christian Marillat wrote: Why a new version has been uploaded during the freeze ? I wondered about that, too, and I suspect it was an accident. If you look at the dates in https://packages.qa.debian.org/l/ldb/news/20141202T232257Z.html the changelog entry (Date header of the changes file) is dated Sat, 05 Jul 2014 23:32:23 +0200, but the mail itself is from Tue, 02 Dec 2014 23:22:57 +. It looks as if the package was uploaded to some queue which held the package for several months and then passing it on to the next hop. Is it possible to upload packages by (e-)mail? Or maybe built in pbuilder in July, but never uploaded. And when 1.1.17-2 was about to be uploaded, the tab-completion for dput unexpectedly caught the older build in /var/cache/pbuilder/result/ first or such. But then again, the GnuPG signature is recent: gpg: Signature made Wed 03 Dec 2014 00:07:33 CET using RSA key ID D729A457. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770706: [PKG-Openstack-devel] Bug#770706: Bug#770706: keystone.service does not start, /var/run/keystone not created
On 12/04/2014 05:42 PM, Gaudenz Steinlin wrote: with the same global section in /usr/share/keystone/keystone-systemd.conf. One can then use /etc/openstack.conf to switch back to syslog or stdout or stderr or whatever she wants globally. That looks like a good solution to me to get rid of the /etc/default files without loosing any functionality. This would avoid duplicating configuration settings in configuration files and /etc/default files. Looks like the best solution to me, but ovviously post jessie. Gaudenz I not sure this is a good solution. The only correct way is to configure it on the command line, with the init system, as we need a per-daemon configuration to keep previous functionality. I'm not even sure that with a non-existent /etc/default/openstack.conf, the daemons would all continue to run without complaining. I very much prefer the current state of things with (shell) configuration files in /etc/default, and I don't see any valid reason why we would stop using that. Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735160: installation-report: installation successfull - no encrypted disk possible
On Donnerstag, 4. Dezember 2014, Stephan Heidinger wrote: can be closed thanks for your feedback, Stephan! signature.asc Description: This is a digitally signed message part.
Bug#772019: ITP: python-proliantutils -- client lib interfacing various devices in HP Proliant Servers
Package: wnpp Severity: wishlist Owner: Thomas Goirand z...@debian.org * Package name: python-proliantutils Version : 0.1.1 Upstream Author : Nisha Agarwal agarwalnisha1...@gmail.com * URL : https://github.com/hpproliant/proliantutils * License : Apache-2.0 Programming Lang: Python Description : client lib interfacing various devices in HP Proliant Servers Proliant Management Tools provides python libraries for interfacing and managing various devices(like iLO) present in HP Proliant Servers. Currently, this module offers a library to interface to iLO4 using RIBCL. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771951: ITP: haskell-bool-extras -- Fold function for Bool type
* Joachim Breitner nome...@debian.org [2014-12-03 23:44:40+0100] due to the triviality of packaging a single Haskell library, but the intricacies of maintaining the whole bunch of them, we usually maintain all haskell libraries in the Debian Haskell Group (https://wiki.debian.org/Haskell). You are invited to join us to get haskell-bool-extras packaged, but you are also free to simply tell us „I need this packaged as a dependency for something I want to maintain“, and let us do the work – that’s what we are for, after all. Well, I already packaged bool-extras and sent it on mentors. What would it mean for me join DHG? -- Best regards, Dmitry Bogatov kact...@gnu.org, Free Software supporter, esperantisto and netiquette guardian. GPG: 54B7F00D pgpPwiRtsj4mw.pgp Description: PGP signature
Bug#770194: [DRE-maint] Bug#770194: please confirm the version of ruby-i18n
On Thu, Nov 27, 2014 at 10:37:09AM +0100, Cédric Boutillier wrote: Control: tags -1 + moreinfo Hi, This bug looks very much like #765124 [1], which is triggered by a version of ruby-i18n not compatible with the version of ruby-stringex in Jessie. Could you please ensure that you can reproduce the bug with ruby-i18n set to version 0.6.9-2? 1: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765124 If the bug is not reproducible with the version of ruby-i18n in Jessie, then I'll probably add a version 0.6.11~ for ruby-i18n in the dependency line of ruby-stringex. please don't, the right fix for this is to make stringex compatible with the new i18n. dependencies will always come back to bite you in the future. -- Antonio Terceiro terce...@debian.org signature.asc Description: Digital signature
Bug#715440: ipsec-tools-0.8.0: Mobile Clients Phase 1 Negotiation timeout during NAT-T
Hi Christian, i just tried to backport the 0.8.2 from jessie to wheezy, but the build failed with a message configure.ac:10: option 'serial-tests' not recognized Seems i have to install a newer automake, but i don't have the time to dig into this right now... You don't have a prebuilt binary package for powerpc-wheezy by hazard ;-) On Sat, 28 Jun 2014 18:25:30 +0200 Christian Hofstaedtler z...@debian.org wrote: Thomas, I've a nicely working setup with ipsec-tools 0.8.2 and various clients, including iOS 7. Could you try again with 0.8.2? Thanks, -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- -- Thomas Kempf fon + 49 7321 969845 fax + 49 7321 969890 tke...@hueper.de http://www.hueper.de Werbeagentur Hüper GmbH Im Brühl 1 89520 Heidenheim an der Brenz Registergericht Amtsgericht Heidenheim an der Brenz HRB 720441 Geschäftsführer Peter Hüper Bernd Weser -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#718596: [Pkg-bluetooth-maintainers] Bug#718596: (no subject)
On 03/12/14 08:47, Habib Seifzadeh wrote: Dear Nobuhiro, Thanks a lot, Bluez-obexd solved the problem. Both send and receive works perfectly, Cheers, Habib On 12/03/2014 04:19 AM, Nobuhiro Iwamatsu wrote: Hi, obexd is already obsolete. Also different because API can not be used in GNOME, KDE and other. Please use the bluez-obexd instead. Best regards, Nobuhiro Hi guys, I confirm that today, after upgrade of my packages, I can transfer files from/to my phone using gnome-bluetooth. It means, I guess, that you can close (or maybe donwgrade) this bug. Thanks Tomasz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771951: ITP: haskell-bool-extras -- Fold function for Bool type
Hi, Am Donnerstag, den 04.12.2014, 15:40 +0300 schrieb Dmitry Bogatov: * Joachim Breitner nome...@debian.org [2014-12-03 23:44:40+0100] due to the triviality of packaging a single Haskell library, but the intricacies of maintaining the whole bunch of them, we usually maintain all haskell libraries in the Debian Haskell Group (https://wiki.debian.org/Haskell). You are invited to join us to get haskell-bool-extras packaged, but you are also free to simply tell us „I need this packaged as a dependency for something I want to maintain“, and let us do the work – that’s what we are for, after all. Well, I already packaged bool-extras and sent it on mentors. What would it mean for me join DHG? you’d read through https://wiki.debian.org/Haskell, including the secion on how we use Darcs to manage the packaging, subscribe to the mailing lists d-haskell and pkg-haskell-*, request membership via alioth. When that has been enabled, you’d upload your packaging to the darcs repo and get feedback and/or sponsorship from there. Greetings, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Bug#771980: systemd: /var/run/log/journal is not readable by the adm group
Hi, On 4 Dec 2014 02:16, Michael Biebl bi...@debian.org wrote: Am 04.12.2014 um 04:38 schrieb Felipe Sateler: Package: systemd Version: 215-7 Severity: minor The tmpfiles snippets set the /run/log/journal directory owned to root:systemd-journal, but it does not add a read acl for the adm group as README.Debian suggests. I'm not sure tmpfiles can add ACLs, if so, debian should probably add that ACL. Are you talking about /var/log/journal or /run/log/journal? Keep in mind, that we don't not create /var/log/journal in the package and if you do so, you should follow the instructions in the README.Debian to set the permissions/ACLs accordingly. I'm sorry I was unclear. The instructions in README.Debian are perfectly fine. The problem is when persistent logging is not enabled, as /run/log/journal does not have the adm ACL set. A jessie system by default will not have logs in `systemctl status` and require root for journalctl. I do not understsand the purpose of the systemd-journal group; if it is safe to replace with adm everywhere I think that in Debian it should be, as the adm group is the one for reading logs. That is probably too intrusive for jessie, though. Once we ship /var/log/journal in the package, we'll also set the ACLs accordingly. I'm not quite sure what this bug report is about though and what we are supposed to fix? I hope I was clearer this time. -- Saludos, Felipe Sateler -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772020: wget: Please compile with PCRE support
Package: wget Version: 1.16-1 Severity: wishlist Dear Maintainer, Newer versions of Wget support various types of regular expressions for --accept-regex and --reject-regex options. -- --regex-type regextype Specify the regular expression type. Possible types are posix or pcre. Note that to be able to use pcre type, wget has to be compiled with libpcre support. -- Please consider enabling pcre support in Wget binaries. Best Regards, Mert Dirik -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (2, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages wget depends on: ii libc6 2.19-13 ii libgnutls-deb0-28 3.3.8-5 ii libidn11 1.29-1+b1 ii libnettle4 2.7.1-3 ii libpsl00.5.1-1 ii libuuid1 2.25.2-3 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages wget recommends: ii ca-certificates 20141019 wget 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#772021: unblock: redmine/3.0~20140825-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package redmine
This fixes an important bug where Redmine will crash at every request
under some specific issue management configurations.
Attached you will find:
- redmine-full.diff: full diff between testing and unstable
- redmine.diff: diff between previously unblocked version (#771611) and
this new one.
unblock redmine/3.0~20140825-3
-- System Information:
Debian Release: 8.0
APT prefers buildd-unstable
APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'),
(1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--
Antonio Terceiro terce...@debian.org
diff -Nru redmine-3.0~20140825/debian/changelog redmine-3.0~20140825/debian/changelog
--- redmine-3.0~20140825/debian/changelog 2014-11-30 21:20:48.0 -0200
+++ redmine-3.0~20140825/debian/changelog 2014-12-04 09:44:34.0 -0200
@@ -1,3 +1,10 @@
+redmine (3.0~20140825-3) unstable; urgency=medium
+
+ * debian/patches/avoid-crash-on-issues.diff: apply upstream patch to avoid
+crashes in some issue management configurations (Closes: #771849)
+
+ -- Antonio Terceiro terce...@debian.org Thu, 04 Dec 2014 09:41:50 -0200
+
redmine (3.0~20140825-2) unstable; urgency=medium
* README.Debian: update instructions to run redmine without a webserver
diff -Nru redmine-3.0~20140825/debian/patches/avoid-crash-on-issues.diff redmine-3.0~20140825/debian/patches/avoid-crash-on-issues.diff
--- redmine-3.0~20140825/debian/patches/avoid-crash-on-issues.diff 1969-12-31 21:00:00.0 -0300
+++ redmine-3.0~20140825/debian/patches/avoid-crash-on-issues.diff 2014-12-04 09:44:34.0 -0200
@@ -0,0 +1,48 @@
+Description: fix crashes in some issue management configurations
+Author: Jean-Philippe Lang jp_l...@yahoo.fr
+Origin: upstream
+Bug: http://www.redmine.org/issues/18275
+Bug-Debian: https://bugs.debian.org/771849
+Reviewed-by: Antonio Terceiro terce...@debian.org
+Last-Update: 2014-11-04
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/test/functional/repositories_controller_test.rb
b/test/functional/repositories_controller_test.rb
+@@ -166,6 +166,18 @@ class RepositoriesControllerTest Actio
+ assert_equal 1, assigns(:changeset).revision
+ end
+
++ def test_revision_should_show_add_related_issue_form
++Role.find(1).add_permission! :manage_related_issues
++@request.session[:user_id] = 2
++
++get :revision, :id = 1, :rev = 1
++assert_response :success
++
++assert_select 'form[action=?]', '/projects/ecookbook/repository/revisions/1/issues' do
++ assert_select 'input[name=?]', 'issue_id'
++end
++ end
++
+ def test_revision_should_not_change_the_project_menu_link
+ get :revision, :id = 1, :rev = 1
+ assert_response :success
+--- a/app/views/repositories/_related_issues.html.erb
b/app/views/repositories/_related_issues.html.erb
+@@ -24,12 +24,12 @@
+ /ul
+
+ % if manage_allowed %
+- %= form_for(@issue, :as = :issue, :remote = true,
+- :url = {:controller = 'repositories', :action = 'add_related_issue',
++ %= form_tag({:controller = 'repositories', :action = 'add_related_issue',
+ :id = @project, :repository_id = @repository.identifier_param,
+ :rev = @changeset.identifier},
++ :remote = true,
+:method = :post,
+- :html = {:id = 'new-relation-form', :style = (@issue ? '' : 'display: none;')}) do |f| %
++ :id = 'new-relation-form', :style = (@issue ? '' : 'display: none;')) do |f| %
+ %= l(:label_issue) % #%= text_field_tag 'issue_id', '', :size = 10 %
+ %= submit_tag l(:button_add) %
+ %= toggle_link l(:button_cancel), 'new-relation-form'%
diff -Nru redmine-3.0~20140825/debian/patches/series redmine-3.0~20140825/debian/patches/series
--- redmine-3.0~20140825/debian/patches/series 2014-11-30 21:20:48.0 -0200
+++ redmine-3.0~20140825/debian/patches/series 2014-12-04 09:44:34.0 -0200
@@ -9,3 +9,4 @@
gemfile-adjustments.patch
drop-update_all.patch
invalidate-language-cache-from-older-versions.diff
+avoid-crash-on-issues.diff
diff -Nru redmine-3.0~20140825/debian/changelog redmine-3.0~20140825/debian/changelog
--- redmine-3.0~20140825/debian/changelog 2014-09-30 18:40:43.0 -0300
+++ redmine-3.0~20140825/debian/changelog 2014-12-04 09:44:34.0 -0200
@@ -1,3 +1,29 @@
+redmine (3.0~20140825-3) unstable; urgency=medium
+
+ * debian/patches/avoid-crash-on-issues.diff: apply upstream patch to avoid
+crashes in some issue management configurations (Closes: #771849)
+
+ -- Antonio Terceiro terce...@debian.org Thu, 04 Dec 2014 09:41:50 -0200
+
+redmine (3.0~20140825-2) unstable; urgency=medium
+
+ * README.Debian: update instructions
Bug#614569: [Pkg-openldap-devel] Bug#614569: RFS: Bug#614569: slapd fails to dump/reload partial replica -- NMU sponsor needed
Luca Bruno lu...@debian.org writes: On Wednesday 03 December 2014 18:21:08 Ryan Tandy wrote: On Wed, Dec 03, 2014 at 11:40:24PM +0100, Ferenc Wagner wrote: I got pre-approval on #771962: the upload will be unblocked, provided it's in unstable by Monday the 8th of December. People with upload rights, if you can spare a minute please review the above change and consider sponsoring the upload! Actually, review is welcome from anybody. :) Thanks very much for working on this, and the debdiff looks fine (but I haven't actually built or tested it). I hope you can find a sponsor in time. Luca, are you reading? I was following the discussion, and I have to say that I am not too comfortable in uploading this NMU at this point of the release cycle. So NACK on my side. My main concerns are: * I am not sure that I grok all the implications of that. I suspect that most of our (overly) complex pre/postinst scripts makes some assumption on schema/db consistency, at least implicitly. I went through all the maintainer scripts in the package, and did not find any dependency on DB consistency, apart from the config DB itself, which we touch on the filesystem (which is unsupported). And of course apart from the current issue, which is assuming that slapadd will work on the result of slapcat. This is false without the -s option. * We are changing the default behavior to fix a single-case situation, by removing a safety check. Mmmh... As you point out below, debconf does not offer switching off schema checking. Just like it does not offer configuring replication. Thus if a database is not schema-correct, that must be the result of manual configuration, not some default behavior. From this point of view, we do not change the default behavior, we extend it to other cases. If the database was schema-correct, it will stay so. If the admin uses a config where it wasn't, then it will stay so as well. * This bug has been open since some time, never marked as RC, put on low-priority by the maintainer I don't understand why. This bug breaks upgrades, and the only workaround I know of is manually editing the postinst script. and upstream discouraged dropping the -s. (I guess you mean using). Yes, but I think their reasoning about importing invalid databases does not apply in our case, see above and below. * This is not even the proper solution, just a quick-hack patch. The proper solution would require separate dump/restore decisions for each database, and we haven't yet got the infrastructure for that. And it would only achieve not using the -s flag when it wouldn't have any effect anyway (maybe apart from slowing down the import). After all, we're loading dumps we ourselves made a couple of moments earlier, not some synthetic data. Moreover, I don't consider myself an LDAP expert, but I have some comments on the issue: * I would say that requiring/checking schema integrity across upgrade is a good general measure, and we should NOT work around that. Fail early, fail loudly. My point here is that schema-correctness has nothing to do with the upgrade, as the schema is just a part of the local configuration, which is not changed by the upgrade. * IIRC disabling schemachecking is heavily discouraged. We don't offer that option in debconf. I assume the admin are really aware of the setup, and know its quirk. As far as I know, it's not only discouraged, but is actually impossible for some time now. The only way to switch off schema checking is using replication, making your database a read-only shadow. * Workarounds for the specific corner case exists, but maybe are a bit undocumented. I don't consider editing the postinst script a viable workaround. Maybe I miss something here? Disabling dumping does not cut it, see #770827 and #771823. So my alternative suggestion is: let's make it explicit that we value schema integrity, and we rely on it across upgrades OpenLDAP also values schema-correctness (see above), and that's why artifically relying on it does not really help, only needlessly breaks upgrades on partial replicas. let's put a point in the release notes to document how to workaround this partial replica scenario; let's try to address this better in the next point release. I honestly don't think there's much to gain in that direction. Unless there really is a good workaround (not involving hand-editing maintainer scripts during the upgrade), I find it an unneeded burden on the user. -- Regards, Feri. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770283: xfburn crashes when adding Data Composition files
Hi, Sorry I took so long. Debian's bugtracker didn't forward me the emails, so I just saw this yesterday. Here's the contents of /tmp/valgrind_messages: ==2799== Memcheck, a memory error detector ==2799== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==2799== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info ==2799== Command: /usr/bin/xfburn ==2799== ** Message: No existing settings file, using default settings ** Message: Using UDEV ** (xfburn:2799): WARNING **: A pipeline element could not be created ==2799== Conditional jump or move depends on uninitialised value(s) ==2799==at 0x7201FC8: ??? (in /usr/lib/powerpc-linux-gnu/gtk-2.0/2.10.0/engines/libmurrine.so) ==2799==by 0x72060D3: ??? (in /usr/lib/powerpc-linux-gnu/gtk-2.0/2.10.0/engines/libmurrine.so) ==2799==by 0x71FB7DB: ??? (in /usr/lib/powerpc-linux-gnu/gtk-2.0/2.10.0/engines/libmurrine.so) ==2799==by 0x4D03F87: gtk_paint_box (in /usr/lib/powerpc-linux-gnu/libgtk-x11-2.0.so.0.2400.25) ==2799==by 0x4B717AB: ??? (in /usr/lib/powerpc-linux-gnu/libgtk-x11-2.0.so.0.2400.25) ==2799==by 0x4B71A83: ??? (in /usr/lib/powerpc-linux-gnu/libgtk-x11-2.0.so.0.2400.25) ==2799==by 0x4C53393: ??? (in /usr/lib/powerpc-linux-gnu/libgtk-x11-2.0.so.0.2400.25) ==2799==by 0x53D3C17: ??? (in /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0.4200.0) ==2799==by 0x53D592B: g_closure_invoke (in /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0.4200.0) ==2799==by 0x53EE01B: ??? (in /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0.4200.0) ==2799==by 0x53F7337: g_signal_emit_valist (in /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0.4200.0) ==2799==by 0x53F79D7: g_signal_emit (in /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0.4200.0) ==2799== ==2799== Conditional jump or move depends on uninitialised value(s) ==2799==at 0x7202030: ??? (in /usr/lib/powerpc-linux-gnu/gtk-2.0/2.10.0/engines/libmurrine.so) ==2799==by 0x72060D3: ??? (in /usr/lib/powerpc-linux-gnu/gtk-2.0/2.10.0/engines/libmurrine.so) ==2799==by 0x71FB7DB: ??? (in /usr/lib/powerpc-linux-gnu/gtk-2.0/2.10.0/engines/libmurrine.so) ==2799==by 0x4D03F87: gtk_paint_box (in /usr/lib/powerpc-linux-gnu/libgtk-x11-2.0.so.0.2400.25) ==2799==by 0x4B717AB: ??? (in /usr/lib/powerpc-linux-gnu/libgtk-x11-2.0.so.0.2400.25) ==2799==by 0x4B71A83: ??? (in /usr/lib/powerpc-linux-gnu/libgtk-x11-2.0.so.0.2400.25) ==2799==by 0x4C53393: ??? (in /usr/lib/powerpc-linux-gnu/libgtk-x11-2.0.so.0.2400.25) ==2799==by 0x53D3C17: ??? (in /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0.4200.0) ==2799==by 0x53D592B: g_closure_invoke (in /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0.4200.0) ==2799==by 0x53EE01B: ??? (in /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0.4200.0) ==2799==by 0x53F7337: g_signal_emit_valist (in /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0.4200.0) ==2799==by 0x53F79D7: g_signal_emit (in /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0.4200.0) ==2799== ==2799== Conditional jump or move depends on uninitialised value(s) ==2799==at 0x7202038: ??? (in /usr/lib/powerpc-linux-gnu/gtk-2.0/2.10.0/engines/libmurrine.so) ==2799==by 0x72060D3: ??? (in /usr/lib/powerpc-linux-gnu/gtk-2.0/2.10.0/engines/libmurrine.so) ==2799==by 0x71FB7DB: ??? (in /usr/lib/powerpc-linux-gnu/gtk-2.0/2.10.0/engines/libmurrine.so) ==2799==by 0x4D03F87: gtk_paint_box (in /usr/lib/powerpc-linux-gnu/libgtk-x11-2.0.so.0.2400.25) ==2799==by 0x4B717AB: ??? (in /usr/lib/powerpc-linux-gnu/libgtk-x11-2.0.so.0.2400.25) ==2799==by 0x4B71A83: ??? (in /usr/lib/powerpc-linux-gnu/libgtk-x11-2.0.so.0.2400.25) ==2799==by 0x4C53393: ??? (in /usr/lib/powerpc-linux-gnu/libgtk-x11-2.0.so.0.2400.25) ==2799==by 0x53D3C17: ??? (in /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0.4200.0) ==2799==by 0x53D592B: g_closure_invoke (in /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0.4200.0) ==2799==by 0x53EE01B: ??? (in /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0.4200.0) ==2799==by 0x53F7337: g_signal_emit_valist (in /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0.4200.0) ==2799==by 0x53F79D7: g_signal_emit (in /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0.4200.0) ==2799== ==2799== Invalid read of size 4 ==2799==at 0x53EDD90: ??? (in /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0.4200.0) ==2799==by 0x53F77C7: g_signal_emit_valist (in /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0.4200.0) ==2799==by 0x53F79D7: g_signal_emit (in /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0.4200.0) ==2799==by 0x4C86EEB: ??? (in /usr/lib/powerpc-linux-gnu/libgtk-x11-2.0.so.0.2400.25) ==2799==by 0x4DD09DB: ??? (in /usr/lib/powerpc-linux-gnu/libgtk-x11-2.0.so.0.2400.25) ==2799==by 0x4DDE593: ??? (in /usr/lib/powerpc-linux-gnu/libgtk-x11-2.0.so.0.2400.25) ==2799==by 0x53DEF77: g_object_run_dispose (in /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0.4200.0) ==2799==
Bug#772022: unblock: ini4j/0.5.2-SNAPSHOT-5
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package ini4j. The package was patched last June to compile with Java 8, but the patch broke a major functionality of the library (removing an element from the ini configuration no longer work). The version 0.5.2-SNAPSHOT-5 fixes this issue and enables the unit tests to ensure the Java 8 compatibility patch doesn't break the expected behavior of the library. Thank you unblock ini4j/0.5.2-SNAPSHOT-5 diff -Nru ini4j-0.5.2-SNAPSHOT/debian/changelog ini4j-0.5.2-SNAPSHOT/debian/changelog --- ini4j-0.5.2-SNAPSHOT/debian/changelog 2014-04-15 15:20:57.0 +0200 +++ ini4j-0.5.2-SNAPSHOT/debian/changelog 2014-12-04 13:53:54.0 +0100 @@ -1,3 +1,12 @@ +ini4j (0.5.2-SNAPSHOT-5) unstable; urgency=medium + + * Team upload. + * Fixed the Java 8 compatibility patch (Closes: #772010) + * Enabled the unit tests + * Standards-Version updated to 3.9.6 (no changes) + + -- Emmanuel Bourg ebo...@apache.org Thu, 04 Dec 2014 13:53:51 +0100 + ini4j (0.5.2-SNAPSHOT-4) unstable; urgency=medium * Team upload. diff -Nru ini4j-0.5.2-SNAPSHOT/debian/control ini4j-0.5.2-SNAPSHOT/debian/control --- ini4j-0.5.2-SNAPSHOT/debian/control 2014-04-15 15:20:57.0 +0200 +++ ini4j-0.5.2-SNAPSHOT/debian/control 2014-12-04 13:50:47.0 +0100 @@ -3,8 +3,8 @@ Priority: optional Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Uploaders: Marek Slama marek.sl...@sun.com, Andres Mejia ame...@debian.org -Build-Depends: cdbs, debhelper (= 9), maven-debian-helper, default-jdk, libmaven-javadoc-plugin-java -Standards-Version: 3.9.5 +Build-Depends: cdbs, debhelper (= 9), maven-debian-helper, default-jdk, libmaven-javadoc-plugin-java, junit4, libbsh-java, libeasymock-java +Standards-Version: 3.9.6 Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-java/ini4j.git Vcs-Git: git://anonscm.debian.org/pkg-java/ini4j.git Homepage: http://www.ini4j.org diff -Nru ini4j-0.5.2-SNAPSHOT/debian/maven.cleanIgnoreRules ini4j-0.5.2-SNAPSHOT/debian/maven.cleanIgnoreRules --- ini4j-0.5.2-SNAPSHOT/debian/maven.cleanIgnoreRules 2014-04-15 15:39:43.0 +0200 +++ ini4j-0.5.2-SNAPSHOT/debian/maven.cleanIgnoreRules 1970-01-01 01:00:00.0 +0100 @@ -1 +0,0 @@ - diff -Nru ini4j-0.5.2-SNAPSHOT/debian/maven.ignoreRules ini4j-0.5.2-SNAPSHOT/debian/maven.ignoreRules --- ini4j-0.5.2-SNAPSHOT/debian/maven.ignoreRules 2014-04-15 15:39:43.0 +0200 +++ ini4j-0.5.2-SNAPSHOT/debian/maven.ignoreRules 2014-12-04 13:49:43.0 +0100 @@ -1,7 +1,6 @@ com.google.code.maven-license-plugin maven-license-plugin * * * * jetty jetty * * * * -junit junit * * * * net.sf.retrotranslator retrotranslator-runtime * * * * org.apache.maven.plugins maven-antrun-plugin * * * * org.apache.maven.plugins maven-assembly-plugin * * * * @@ -14,11 +13,8 @@ org.apache.maven.plugins maven-project-info-reports-plugin * * * * org.apache.maven.plugins maven-site-plugin * * * * org.apache.maven.plugins maven-source-plugin * * * * -org.apache.maven.plugins maven-surefire-plugin * * * * -org.beanshell bsh * * * * org.codehaus.mojo cobertura-maven-plugin * * * * org.codehaus.mojo retrotranslator-maven-plugin * * * * org.codehaus.mojo taglist-maven-plugin * * * * org.codehaus.mojo wagon-maven-plugin * * * * -org.easymock easymock * * * * org.easymock easymockclassextension * * * * diff -Nru ini4j-0.5.2-SNAPSHOT/debian/maven.properties ini4j-0.5.2-SNAPSHOT/debian/maven.properties --- ini4j-0.5.2-SNAPSHOT/debian/maven.properties2014-04-15 15:20:57.0 +0200 +++ ini4j-0.5.2-SNAPSHOT/debian/maven.properties2014-12-04 13:40:17.0 +0100 @@ -2,5 +2,4 @@ # For example: # maven.test.skip=true -maven.test.skip=true project.build.sourceEncoding=UTF-8 diff -Nru ini4j-0.5.2-SNAPSHOT/debian/maven.publishedRules ini4j-0.5.2-SNAPSHOT/debian/maven.publishedRules --- ini4j-0.5.2-SNAPSHOT/debian/maven.publishedRules2014-04-15 15:39:43.0 +0200 +++ ini4j-0.5.2-SNAPSHOT/debian/maven.publishedRules1970-01-01 01:00:00.0 +0100 @@ -1 +0,0 @@ - diff -Nru ini4j-0.5.2-SNAPSHOT/debian/maven.rules ini4j-0.5.2-SNAPSHOT/debian/maven.rules --- ini4j-0.5.2-SNAPSHOT/debian/maven.rules 2014-04-15 15:39:43.0 +0200 +++ ini4j-0.5.2-SNAPSHOT/debian/maven.rules 2014-12-04 13:51:27.0 +0100 @@ -1 +1,3 @@ +junit junit jar s/4\..*/4.x/ * * + diff -Nru ini4j-0.5.2-SNAPSHOT/debian/patches/01-java8-compatibility.patch ini4j-0.5.2-SNAPSHOT/debian/patches/01-java8-compatibility.patch --- ini4j-0.5.2-SNAPSHOT/debian/patches/01-java8-compatibility.patch 2014-04-15 15:20:57.0 +0200 +++ ini4j-0.5.2-SNAPSHOT/debian/patches/01-java8-compatibility.patch 2014-12-04 13:48:04.0 +0100 @@ -1,7 +1,7 @@ Description: Changes the return type of the org.ini4j.Profile.remove(Object, Object) method to fix a
Bug#771918: Possible fix
On 4 December 2014 at 14:36, miniupnp miniu...@free.fr wrote: Le 03/12/2014 14:42, Tristan Seligmann a écrit : It looks like setting V6SOCKETS_ARE_V6ONLY in the config fixes this. There is some detection using sysctl (which is a bit broken since the settings on the build system may not match the settings on the target system) for this on *BSD, but nothing to set this flag for Linux. https://github.com/miniupnp/miniupnp/commit/3b717664937c5e4c23b5211031ec3f2eba2ab034 Does it do the job ? Yes, that patch seems to work, thanks! (albeit with the caveat of build vs. runtime systems mentioned previously) -- mithrandi, i Ainil en-Balandor, a faer Ambar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755475: gnome-shell-common: since 3.12 components entered testing, gnome-shell breaks GDM
Tomas Pospisek t...@sourcepole.ch wrote: But I do not think the release team will allow a new version of upower to migrate to jessie because it fixes such a (IMHO) minor issue? Do you think they will? Fixing incorrect dependencies is certainly among the things the release team will allow to migrate. And once jessie is released then really I can't see much sense of adding that information either because by then you'll allready be running upower and gdm3 from jessie and so this becomes a non-issue? I agree that after jessie this becomes a non-issue.0 -- Joss -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772023: nodejs: Upstream version 0.10.33 available
Package: nodejs Version: 0.10.29~dfsg-1 Severity: important Tags: security Hello, Please package the latest upstream version. Severity important because according the changelog [1] multiple CVEs are fixed in this release. Thanks, George [1] https://raw.githubusercontent.com/joyent/node/v0.10.33/ChangeLog -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nodejs depends on: ii libc-ares21.10.0-2 ii libc6 2.19-10 ii libgcc1 1:4.9.1-9 ii libssl1.0.0 1.0.1i-2 ii libstdc++64.9.1-9 ii libv8-3.14.5 3.14.5.8-8 ii zlib1g1:1.2.8.dfsg-2 nodejs recommends no packages. nodejs 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#771918: Possible fix
Le 03/12/2014 14:42, Tristan Seligmann a écrit : It looks like setting V6SOCKETS_ARE_V6ONLY in the config fixes this. There is some detection using sysctl (which is a bit broken since the settings on the build system may not match the settings on the target system) for this on *BSD, but nothing to set this flag for Linux. https://github.com/miniupnp/miniupnp/commit/3b717664937c5e4c23b5211031ec3f2eba2ab034 Does it do the job ? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772025: CVE-2014-8106: cirrus: insufficient blit region checks
Package: qemu-system, qemu-kvm Version: 1.1.2+dfsg-1 Severity: critical Tags: security patch upstream fixed-upstream There's a CVE-2014-8106 reported against qemu. The prob exists in earlier versions of qemu too, affecting stable (wheezy) release as well. /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772024: unblock: gnome-flashback/2.10.0-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi, I'm filing this bug to discuss possible ways forward for #771922. After reading the bug report and chatting to the maintainer, I believe the most sensible fix would be to allow a backport of the keygrabber code into jessie. The code that would be backported is: https://git.gnome.org/browse/gnome-flashback/commit/?id=cfce8742780e8be335cf19dd49a993cc0ea63b13 https://git.gnome.org/browse/gnome-flashback/commit/?id=670c310e8eaf89e895da96e62edc2a724c4ec068 These two commits would bring back the key grabbing functionality and would partially fix #771922. I've been in touch with the maintainer (Cc'd), and he thinks this should be a good improvement. unblock gnome-flashback/2.10.0-2 -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#511464: xserver-xorg-input-synaptics: After some time strange behavior with appletouch touchpad
Hello, I no longer use this device and I am unable to test this issue. Please close the bug. Thank you, Tomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770695: Dovecot-core unable to finish its installation
On Thu, 4 Dec 2014, Jaldhar H. Vyas wrote: 1. Which version were you originally upgrading from? 2. Did you edit /etc/dovecot/conf.d/10-ssl.conf at all (from any version.) 3. Would you mind sending me the contents of that file? 4. During the upgrade do you remember seeing any message about updating that file? 5. This is a long shot but...do you have the ucf package installed? Sorry, one more question. Do the files /etc/dovecot/dovecot.pem and /etc/dovecot/private/dovecot.pem exist? -- Jaldhar H. Vyas jald...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770995: unblock: xboard/4.8.0-2
Hi, Jonathan Wiltshire j...@debian.org writes: On Tue, Nov 25, 2014 at 02:24:06PM -0500, Vincent Legout wrote: xboard 4.8.0-1 still uses the old xaw interface and I'd like to upload a new version 4.8.0-2 to use the new gtk interface. This change has been requested by upstream because of several bugs with the old interface, for example some input fields do not work (I don't have any bug report, sorry). This only just came to light?? It's a pretty big change, though I see the usability aspects of it. You'd better upload to sid and let it age for as long as possible, and if nothing else comes up between now and 4th December I imagine we could be persuaded then. xboard 4.8.0-2 has been in unstable for 7 days and no bug has been reported. Could you please consider unblocking it? Thanks, Vincent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771102: upstream license violation
Control: tag -1 + confirmed
Hi,
Ned T. Crigler wrote:
abduco is derived from dtach,
According to the abduco upstream web page, it is only in many ways
very similar, but not derived. I checked the initial import of abduco
(commit 89cbbb3aa6aea7ca7410096aeacc3316a3532344) against dtach 0.8.
I first checked it with
dwdiff -c dtach-0.8/main.c abduco/abduco.c
dwdiff -c dtach-0.8/attach.c abduco/client.c
dwdiff -c dtach-0.8/master.c abduco/server.c
dwdiff -c dtach-0.8/main.c abduco/server.c
dwdiff -c dtach-0.8/master.c abduco/abduco.c
and didn't find any similarities. Also the file listing does not look
very similar:
ls -l dtach-0.8 abduco
abduco:
total 52
-rw-r--r-- 1 abe abe 1574 Dec 4 13:55 abduco.1
-rw-r--r-- 1 abe abe 10121 Dec 4 13:55 abduco.c
-rw-r--r-- 1 abe abe 3168 Dec 4 13:55 client.c
-rw-r--r-- 1 abe abe72 Dec 4 13:55 config.def.h
-rw-r--r-- 1 abe abe 364 Dec 4 13:55 config.mk
-rw-r--r-- 1 abe abe 1780 Dec 4 13:55 debug.c
-rw-r--r-- 1 abe abe 765 Dec 4 13:54 LICENSE
-rw-r--r-- 1 abe abe 1544 Dec 4 13:55 Makefile
-rw-r--r-- 1 abe abe 271 Dec 4 13:55 README
-rw-r--r-- 1 abe abe 6661 Dec 4 13:55 server.c
dtach-0.8:
total 244
-rw-r--r-- 1 abe abe 5963 Jan 31 2008 attach.c
-rw-r--r-- 1 abe abe 3513 Jan 31 2008 config.h.in
-rwxr-xr-x 1 abe abe 155943 Jan 31 2008 configure*
-rw-r--r-- 1 abe abe903 Jan 31 2008 configure.ac
-rw-r--r-- 1 abe abe 17992 Jan 31 2008 COPYING
-rw-r--r-- 1 abe abe 5204 Jan 31 2008 dtach.1
-rw-r--r-- 1 abe abe 2864 Jan 31 2008 dtach.h
-rw-r--r-- 1 abe abe 3510 Jan 31 2008 dtach.spec
-rw-r--r-- 1 abe abe 6692 Jan 31 2008 main.c
-rw-r--r-- 1 abe abe953 Jan 31 2008 Makefile.in
-rw-r--r-- 1 abe abe 14174 Jan 31 2008 master.c
-rw-r--r-- 1 abe abe 7891 Jan 31 2008 README
While abduco may be considered a rewrite of dtach that just has
similar looking portions of code left in it,
I then took similarity-tester (from Wheezy) and ran it as follows:
→ sim_c dtach-0.8/*.c / abduco/*.c
File dtach-0.8/attach.c: 988 tokens
File dtach-0.8/main.c: 844 tokens
File dtach-0.8/master.c: 2600 tokens
File /: separator
File abduco/abduco.c: 2028 tokens
File abduco/client.c: 774 tokens
File abduco/debug.c: 394 tokens
File abduco/server.c: 1554 tokens
Total: 9182 tokens
dtach-0.8/attach.c: line 45-62 |dtach-0.8/master.c: line 178-195 [76]
fflush(stdout); | kill(-pty-pid, sig);
} |}
|
/* Connects to a unix domain socket */ |/* Creates a new unix domain socket. *
static int |static int
connect_socket(char *name) |create_socket(char *name)
{ |{
int s;| int s;
struct sockaddr_un sockun;| struct sockaddr_un sockun;
|
s = socket(PF_UNIX, SOCK_STREAM, 0); | s = socket(PF_UNIX, SOCK_STREAM, 0);
if (s 0)| if (s 0)
return -1; | return -1;
sockun.sun_family = AF_UNIX; | sockun.sun_family = AF_UNIX;
strcpy(sockun.sun_path, name);| strcpy(sockun.sun_path, name);
if (connect(s, (struct sockaddr*)soc | if (bind(s, (struct sockaddr*)sockun
{ | {
close(s);| close(s);
dtach-0.8/attach.c: line 179-184 |abduco/abduco.c: line 316-321 [54]
cur_term.c_iflag = ~(IXON|IXOFF);| cur_term.c_iflag = ~(IGNBRK|BRKINT|P
cur_term.c_oflag = ~(OPOST); | cur_term.c_oflag = ~(OPOST);
cur_term.c_lflag = ~(ECHO|ECHONL|ICA | cur_term.c_lflag = ~(ECHO|ECHONL|ICA
cur_term.c_cflag = ~(CSIZE|PARENB); | cur_term.c_cflag = ~(CSIZE|PARENB);
cur_term.c_cflag |= CS8; | cur_term.c_cflag |= CS8;
cur_term.c_cc[VLNEXT] = VDISABLE; | cur_term.c_cc[VLNEXT] = _POSIX_VDISAB
dtach-0.8/attach.c: line 166-175 |dtach-0.8/master.c: line 420-429 [46]
atexit(restore_term); | atexit(unlink_socket);
|
/* Set some signals. */ | /* Set up some signals. */
signal(SIGPIPE, SIG_IGN); | signal(SIGPIPE, SIG_IGN);
signal(SIGXFSZ, SIG_IGN); | signal(SIGXFSZ, SIG_IGN);
signal(SIGHUP, die); | signal(SIGHUP, SIG_IGN);
signal(SIGTERM, die); | signal(SIGTTIN, SIG_IGN);
signal(SIGINT, die); | signal(SIGTTOU, SIG_IGN);
signal(SIGQUIT, die); | signal(SIGINT, die);
signal(SIGWINCH, win_change); | signal(SIGTERM, die);
dtach-0.8/main.c: line 142-153 |dtach-0.8/main.c: line 164-175[42]
else if (*p == 'e') | else if (*p == 'r')
{ | {
++argv; --argc;|++argv; --argc;
if (argc 1) |if (argc 1)
{ |{
Bug#771930: RFS: sane-frontends/1.0.14-10 [ITA]
Hello Stephen, first thanks for your review. Am Donnerstag, den 04.12.2014, 00:00 +0100 schrieb Stephen Kitt: Control: owner -1 ! Hi Jörg, On Wed, 03 Dec 2014 17:20:22 +0100, Jörg Frings-Fürst deb...@jff-webhosting.net wrote: I am looking for a sponsor for my package sane-frontends Excellent, thanks for taking care of this. Your packaging updates look good, in particular the debian/copyright overhaul! Regarding the latter, you've listed src/preferences.c twice ;-). Removed. Is the dh_builddeb override in debian/rules necessary? No it's not. That was part of my build testing. The removed last line was cp xy xy to run into a error hook. Now the override is also removed. Since you're adding a bunch of .install files, it should be possible to install the XPM using them too, thereby simplifying debian/rules even further. Ok. I thought the source / destination tuples are not allowed at install files. Thanks for your hint. Done debian/watch mentions sane-backends which I guess is a copy-and-paste error! Yes it was a copy-and-past error. :-( Typo corrected. Packeage is uploaded to mentors[1] again. Regards, Stephen CU Jörg [1] http://mentors.debian.net/debian/pool/main/s/sane-frontends/sane-frontends_1.0.14-10.dsc -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG Key: 8CA1D25D CAcert Key S/N: 0E:D4:56 Old (will be revoked after 2014-12-31): pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8 EBCB 422B 44B0 BE58 1B6E pgp Key: BE581B6E Jörg Frings-Fürst D-54526 Niederkail Threema: SYR8SJXB IRC: j_...@freenode.net j_...@oftc.net signature.asc Description: This is a digitally signed message part
Bug#772027: ITP: blogliterately -- Tool for posting Haskelly articles to blogs
Package: wnpp Severity: wishlist Owner: Dmitry Bogatov kact...@gnu.org * Package name: blogliterately Version : 0.7.1.7 Upstream Author : Brent Yorgey byor...@cis.upenn.edu * URL : http://byorgey.wordpress.com/blogliterately/ * License : GPL3+ Programming Lang: Haskell Description : Tool for posting Haskelly articles to blogs Upstream description: This package provides development internals of BlogLiterately tool, allowing you write blog posts in Markdown format, then use it to do syntax highlighting, format ghci sessions, and upload to any blog supporting the metaWeblog API (such as Wordpress) This package is made avaliliable to make customization possible, in particular, to create your own executable which adds extra custom transformations. In short: it is awesome utility(imho), that allows to publish articles from console, without browser and javascript at all. It also can highlight code and interact with ghci. As far, as I know, it is the only of its kind, I use and plan to maintain it. I will need a sponsor to upload it. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772026: plm: It seems PLM sends data to a remote host... which should be advertizes to the users
Package: plm Version: 2.4.11+repack-2 Severity: normal Hi. AFAIU, PLM sends traces (anonymized) to a remote host when it is run (haven't checked, but trust what upstream author just said in a presentation ;-). I'm not sure this is something that is optimal in the general Debian user context. I think that it should at least be documented in a sufficient way. Hope this makes sense. Best regards, P.S.: thanks for packaging this :-) -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing-proposed-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages plm depends on: ii java-wrappers0.1.28 ii jython 2.5.3-3 ii libgettext-commons-java 0.9.6-2 ii libhttpclient-java 4.3.5-2 ii libhttpcore-java 4.3.3-1 ii libhttpmime-java 4.3.5-2 ii libjgit-java 3.4.0-2 ii libjson-simple-java 1.1.1-2 ii libmiglayout-java4.2-1 ii librsyntaxtextarea-java 2.5.0-1 plm recommends no packages. plm 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#772028: quantlib-swig FTBFS on testing for mips/mipsel
Package: quantlib-swig Version: 1.4-1 Tags: sid patch Severity: important Justification: FTBFS User: debian-m...@lists.debian.org Usertags: mips-patch Package quantlib-swig FTBFS on mips/mipsel with an error: g++ -shared -Wl,-z,relro -O0 -g0 build/temp.linux-mips64-2.7/QuantLib/quantlib_wrap.o -lQuantLib -o build/lib.linux-mips64-2.7/QuantLib/_QuantLib.so build/temp.linux-mips64-2.7/QuantLib/quantlib_wrap.o: In function `SWIG_PackDataName': quantlib_wrap.cpp:(.text+0x10b0): relocation truncated to fit: R_MIPS_CALL16 against `strncpy@@GLIBC_2.0' build/temp.linux-mips64-2.7/QuantLib/quantlib_wrap.o: In function `SWIG_Python_ErrorType(int)': quantlib_wrap.cpp:(.text+0x137c): relocation truncated to fit: R_MIPS_GOT16 against `PyExc_ValueError' build/temp.linux-mips64-2.7/QuantLib/quantlib_wrap.o: In function `SWIG_Python_AddErrorMsg(char const*)': quantlib_wrap.cpp:(.text+0x1410): relocation truncated to fit: R_MIPS_CALL16 against `PyErr_Occurred' quantlib_wrap.cpp:(.text+0x1488): relocation truncated to fit: R_MIPS_CALL16 against `PyErr_Clear' quantlib_wrap.cpp:(.text+0x14f0): relocation truncated to fit: R_MIPS_CALL16 against `PyErr_Format' build/temp.linux-mips64-2.7/QuantLib/quantlib_wrap.o: In function `SWIG_Python_AppendOutput(_object*, _object*)': quantlib_wrap.cpp:(.text+0x18c4): relocation truncated to fit: R_MIPS_CALL16 against `PyList_SetItem' build/temp.linux-mips64-2.7/QuantLib/quantlib_wrap.o: In function `SWIG_Python_UnpackTuple(_object*, char const*, int, int, _object**)': quantlib_wrap.cpp:(.text+0x1a0c): relocation truncated to fit: R_MIPS_CALL16 against `PyErr_Format' quantlib_wrap.cpp:(.text+0x1b48): relocation truncated to fit: R_MIPS_CALL16 against `PyErr_Format' quantlib_wrap.cpp:(.text+0x1bc4): relocation truncated to fit: R_MIPS_CALL16 against `PyErr_Format' build/temp.linux-mips64-2.7/QuantLib/quantlib_wrap.o: In function `SwigPyClientData_New': quantlib_wrap.cpp:(.text+0x1f24): relocation truncated to fit: R_MIPS_CALL16 against `PyErr_Occurred' quantlib_wrap.cpp:(.text+0x1f48): additional relocation overflows omitted from the output collect2: error: ld returned 1 exit status error: command 'g++' failed with exit status 1 https://buildd.debian.org/status/fetch.php?pkg=quantlib-swigarch=mipselver=1.4-1stamp=1405951271 Using mxgot flag for mips/mipsel solves this issue for me. Patch that contains this fix for mips/mipsel is attached. With this patch I was able to successfully build quantlib-swig for both mips and mipsel. Could you please consider including this patch. Regards, Dejandiff -uNr quantlib-swig-1.4.orig/debian/rules quantlib-swig-1.4/debian/rules --- quantlib-swig-1.4.orig/debian/rules 2014-11-28 18:26:04.0 +0100 +++ quantlib-swig-1.4/debian/rules 2014-11-28 18:27:49.0 +0100 @@ -49,7 +49,7 @@ ## edd 26 Jun 2007 use cpu test, not arch test -- thanks to Riku via #430709 ## edd 26 Oct 2007 s390+powerpc also die, so add'em (and remove mips(el), see next item) ## edd 27 May 2012 added mips/mipsel/armel/armhf here too -ifneq $(findstring $(cpu), m68k arm armeb s390 powerpc armel armhf mips mipsel) +ifneq $(findstring $(cpu), m68k arm armeb s390 powerpc armel armhf) compilerflags = -O0 -g0 endif @@ -59,6 +59,9 @@ #compilerflags = -O2 -g0 #endif +ifneq $(findstring $(cpu), mipsel mips) +compilerflags = -O0 -g0 -mxgot +endif ## edd 25 Dec 2002 g++-3.2 for s390
Bug#711829: gphoto2
Hi, do you still want to adopt the package ? i want to adopt the package. i will wait your response until 2014-12-20 regards, -- Herbert Parentes Fortes Neto (hpfn) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768600: Bug#769557: education-common: package fails to upgrade properly from wheezy
reopen 768600 found 768600 2:1.5.6-5.2 reassign 769557 readahea-fedora forcemerge 768600 769557 affect 768600 education-desktop-lxde affect 768600 education-desktop-sugar affect 768600 education-common affect 768600 education-desktop-xfce thanks On Sonntag, 23. November 2014, Petter Reinholdtsen wrote: I suspect this metapackage upgrade problem was triggered by bug #768600 fixed in readahead-fedora version 2:1.5.6-5.2. If I got it right, it was a problem exposed/triggered by a new dpkg version changing how triggers were handled, and not really something we can fix in education-common. https://jenkins.debian.net/job/chroot-installation_wheezy_install_education-common_upgrade_to_jessie/6/consoleFull which was done a few minutes ago uses readahead-fedora version 2:1.5.6-5.2 and still shows exactly the same problem, thus reopening the bug. cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#771918: Possible fix
On 12/04/2014 09:12 PM, Tristan Seligmann wrote: On 4 December 2014 at 14:36, miniupnp miniu...@free.fr wrote: Le 03/12/2014 14:42, Tristan Seligmann a écrit : It looks like setting V6SOCKETS_ARE_V6ONLY in the config fixes this. There is some detection using sysctl (which is a bit broken since the settings on the build system may not match the settings on the target system) for this on *BSD, but nothing to set this flag for Linux. https://github.com/miniupnp/miniupnp/commit/3b717664937c5e4c23b5211031ec3f2eba2ab034 Does it do the job ? Yes, that patch seems to work, thanks! (albeit with the caveat of build vs. runtime systems mentioned previously) Do you guys think I should try to get this patch in Jessie? Or is it not worth bothering the Debian release team? Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770283: xfburn crashes when adding Data Composition files
Hi, Debian's bugtracker didn't forward me the emails, This has happened to me, too. But today it worked for me. ==2799== Conditional jump or move depends on uninitialised value(s) ==2799==at 0x7201FC8: ??? (in /usr/lib/powerpc-linux-gnu/gtk-2.0/2.10.0/engines/libmurrine.so) Hard to say whether this is a true bug. Google libmurrine ... Murrine GTK2 cairo theme. Maybe one can choose a different theme and avoid the library in order to see whether xfburn still crashes. ==2799== Invalid read of size 4 ==2799==at 0x53EDD90: ??? (in /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0.4200.0) [... no xfburn code to see ...] ==2799==by 0x53F712B: g_signal_emit_valist (in /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0.4200.0) ==2799== Address 0x4 is not stack'd, malloc'd or (recently) free'd Well, this seems to be the immediate cause of the SIGSEGV. Like with the i386-Ubuntu occasion half a year ago, we see no accusations against the xfburn code before this happens. The normal ways how an application can spoil a library are supposed to get detected by valgrind. Do i get it right that this is 32 bit code ? Something seems to be wrong with xfburn and XFCE+GTK on 32 bit systems. But what ? And why rather rarely ? Is everybody else on 64 bit ? Have a nice day :) Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
