Bug#778617: grub-install often breaks in UEFI mode
On Tue, Feb 17, 2015 at 09:32:56AM -0500, Phillip Susi wrote: Package: grub-installer Version: 1.110 I'm forwarding this patch from Ubuntu: https://launchpad.net/bugs/1303790 On EFI, the boot disk argument given to grub-install is a dummy and is often the wrong disk or a non existent disk. Grub is still installed to the correct place since it goes through the filesystem to /boot/EFI, but the function make_active_partition tries to look at the partition table on the dummy disk and throws an error. Hence, I wrote the attached patch to disable the function on EFI. Hi Phillip, The logic looks ok, I guess, but I'd check more explicitly for grub-efi-* instead of !grub-pc. There's several other architectures that may use grub, and I'm not sure if/how they may need special handling for active partitions... -- Steve McIntyre, Cambridge, UK.st...@einval.com Armed with Valor: Centurion represents quality of Discipline, Honor, Integrity and Loyalty. Now you don't have to be a Caesar to concord the digital world while feeling safe and proud. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778654: FTBFS on various architectures, test-sigbus and test-utf8 failures
Source: systemd Version: 219-1 Severity: serious The latest upstream versions FTBFS on various architectures due to failures in the test-suite: armhf: FAIL: test-sigbus i386:FAIL: test-sigbus mips:FAIL: test-utf8 powerpc: FAIL: test-utf8, FAIL: test-sigbus s390x: FAIL: test-utf8 sparc: various failures (no release arch though, has been failing for quite some time) https://buildd.debian.org/status/package.php?p=systemdsuite=experimental -- Package-specific info: -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- 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#762723: pastebinit: [INTL:de] updated German po file translation
On 18.02.2015 02:44, Helge Kreutzmann wrote: I do not intend to introduce a delta for this in Debian. In this case it would be great if you could pull the (latest) de.po from upstream / launchpad Helge, in principle I agree, but as you can see above I already said I will not introduce a delta to upstream only for this. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778660: ITP: r-cran-gridextra -- GNU R package with extensions for the grid package
Package: wnpp Owner: Dirk Eddelbuettel e...@debian.org Severity: wishlist * Package name: r-cran-gridextra Version : 0.9-1-1 Upstream Author : Baptiste Auguie * URL or Web page : http://cran.r-project.org/web/packages/gridExtra/index.html * License : GPL-2 Description : GNU R extensions to grid graphics This package is a new Build-Depends for the r-cran-rms package which has been in Debian for many years. Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@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#778653: unblock: procmail/3.22-24
On Tue, Feb 17, 2015 at 11:40:48PM +0100, Moritz Muehlenhoff wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package procmail. It fixes several heap overflows and memory corruptions spotted in recent fuzzing attempts (one has been assigned CVE-2014-9681). FWIW, CVE-2014-9681 is cp error, the bugs fixed here don't have a CVE ID. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771701: (pre-approval) unblock: bareos/14.2.1+20141017gitc6c5b56-4
Le 2014-12-03 13:13, Ivo De Decker a écrit : Control: tags -1 moreinfo Hi, On Tue, Dec 02, 2014 at 11:16:57AM +0100, Evgeni Golov wrote: % ssh coccia.debian.org dak ls bareos bareos | 14.2.1+20141017gitc6c5b56-4 | accepted| source, amd64 bareos | 14.2.1+20141017gitc6c5b56-4 | buildd-unstable | source, amd64 bareos | 14.2.1+20141017gitc6c5b56-4 | unstable| source, amd64 Still building on the other archs, but I do not expect anything surprising. As you noticed, a new RC bug showed up in this version (#771870). Evgeni, can you please tell how do you plan to fix #771870? TBH, at this stage, the simpler solution as far as Jessie is concerned would be to remove the package from Jessie for now... and work on a backport as soon as Jessie is released. What do you think? Regards, -- Mehdi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772727: unblock: netplug/1.2.9.2-2
Le 2015-02-18 00:35, Mehdi Dogguy a écrit :
Le 2014-12-10 16:19, Adam D. Barratt a écrit :
Control: tags -1 + moreinfo
On 2014-12-10 14:34, Pali Rohár wrote:
Please unblock package netplug
New version of netplug package (1.2.9.2-2) which is on
http://mentors.debian.org/package/netplug fix more bugs reported to
Debian.
Ner version is not from upstream, but contains only new patches
which
fixing bugs reported in Debian.
Please attach a debdiff, as requested by
https://release.debian.org/jessie/freeze_policy.html (and I believe
by
reportbug).
The debdiff is attached. There are no bug fixes for issues that can be
considered as RC. Based on that, I am closing this bugreport. The
submitter can still re-open the bug-report if he has more information
to share.
Forgot to attach the debdiff. :) Now done.
Regards,diff -Nru netplug-1.2.9.2/debian/changelog netplug-1.2.9.2/debian/changelog
--- netplug-1.2.9.2/debian/changelog2010-08-07 17:07:58.0 +0200
+++ netplug-1.2.9.2/debian/changelog2014-12-26 14:56:56.0 +0100
@@ -1,3 +1,19 @@
+netplug (1.2.9.2-2) unstable; urgency=low
+
+ * debian/control:
+- New maintainer (Closes: #730573)
+- Depend on iproute2 instead of transitional iproute (Closes: #753747)
+- Add info about difference between netplugd and ifplugd packages
+ to package long description (Closes: #690129)
+- Fix Standards-Version
+ * debian/rules:
+- Fix missing recommended target
+- Fix dpkg-buildflags missing
+ * Handle ST_DOWNANDOUT state (Closes: #652418)
+ * Allow to specify custom script file via new param '-s' (Closes: #702495)
+
+ -- Pali Rohár pali.ro...@gmail.com Sat, 29 Nov 2014 00:34:05 +0100
+
netplug (1.2.9.2-1) unstable; urgency=low
* New upstream version:
diff -Nru netplug-1.2.9.2/debian/control netplug-1.2.9.2/debian/control
--- netplug-1.2.9.2/debian/control 2010-08-07 16:33:11.0 +0200
+++ netplug-1.2.9.2/debian/control 2014-12-26 14:56:56.0 +0100
@@ -1,20 +1,21 @@
Source: netplug
Section: net
Priority: optional
-Maintainer: Philipp Matthias Hahn pmh...@debian.org
+Maintainer: Pali Rohár pali.ro...@gmail.com
Build-Depends: debhelper ( 7)
-Standards-Version: 3.9.1
+Standards-Version: 3.9.6
Homepage: http://www.red-bean.com/~bos/
Package: netplug
Architecture: any
Depends: ${shlibs:Depends},
${misc:Depends},
- iproute
+ iproute2 | iproute
Description: network link monitor daemon
This daemon monitors the link status of network cards and configures
the network on plug- and un-plug-events.
.
It's similar to ifplugd, but uses NETLINK instead of regularly polling
the link status. This improves power-consumption with laptops, but does
- not work with all network card.
+ not work with all network card. And it can't be configured to ignore short
+ unplugged or plugged periods like ifplugd.
diff -Nru netplug-1.2.9.2/debian/patches/50downoutstate.patch
netplug-1.2.9.2/debian/patches/50downoutstate.patch
--- netplug-1.2.9.2/debian/patches/50downoutstate.patch 1970-01-01
01:00:00.0 +0100
+++ netplug-1.2.9.2/debian/patches/50downoutstate.patch 2014-11-29
12:52:37.0 +0100
@@ -0,0 +1,11 @@
+Handle ST_DOWNANDOUT state (Bug #652418)
+--- a/if_info.c
b/if_info.c
+@@ -186,6 +186,7 @@
+ if (newflags IFF_UP) {
+ switch(info-state) {
+ case ST_DOWN:
++case ST_DOWNANDOUT:
+ info-state = ST_INACTIVE;
+ break;
+
diff -Nru netplug-1.2.9.2/debian/patches/60custom-script.patch
netplug-1.2.9.2/debian/patches/60custom-script.patch
--- netplug-1.2.9.2/debian/patches/60custom-script.patch1970-01-01
01:00:00.0 +0100
+++ netplug-1.2.9.2/debian/patches/60custom-script.patch2014-11-29
12:52:37.0 +0100
@@ -0,0 +1,113 @@
+Allow to specify custom script file via new param '-s' (Bug #702495)
+diff --git a/lib.c b/lib.c
+index 5507daf..46de348 100644
+--- a/lib.c
b/lib.c
+@@ -29,6 +29,7 @@
+
+ #include netplug.h
+
++const char *script_file = NP_SCRIPT_DIR /netplug;
+
+ void
+ do_log(int pri, const char *fmt, ...)
+@@ -109,11 +110,11 @@ run_netplug_bg(char *ifname, char *action)
+ setpgrp(); /* become group leader */
+
+ do_log(LOG_INFO, %s %s %s - pid %d,
+- NP_SCRIPT, ifname, action, getpid());
++ script_file, ifname, action, getpid());
+
+-execl(NP_SCRIPT, NP_SCRIPT, ifname, action, NULL);
++execl(script_file, script_file, ifname, action, NULL);
+
+-do_log(LOG_ERR, NP_SCRIPT : %m);
++do_log(LOG_ERR, %s: %m, script_file);
+ exit(1);
+ }
+
+diff --git a/main.c b/main.c
+index fe949a9..a3cdf63 100644
+--- a/main.c
b/main.c
+@@ -91,7 +91,7 @@ handle_interface(struct nlmsghdr *hdr, void *arg)
+ static void
+ usage(char *progname, int exitcode)
+ {
+-fprintf(stderr, Usage: %s [-DFP] [-c config-file] [-i interface] [-p
pid-file]\n,
++fprintf(stderr, Usage: %s [-DFP] [-c config-file]
Bug#759001: [systemd-devel] sysv-generator: doesn't handle /etc/insserv/overrides or /etc/chkconfig.d
Hi, Christian Seiler christ...@iwakd.de writes: I've implemented both of these and attached a modified version of the patch. Do you have any objections? If not, I'll ask for pre- approval by the release team. The load_sysv function also has a heuristic to guess whether the init script support the release action or not: /* Try to figure out whether this init script supports * the reload operation. This heuristic looks for * Usage lines which include the reload option. */ As far as I can see this will no longer work with the proposed changes when an override file is present: load_sysv will only process the override file and never see the usage line used in the heuristic. Ansgar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778239: Strange GRE packet forwarding slowness in 3.16.7-ckt2-1~bpo70+1
On Thu, 12 Feb 2015 16:33:09 +0100 Sven Hartge s...@svenhartge.de wrote: I have encountered a strange slowness on a router/packetfilter system (Wheezy 7.8 with backported kernel 3.16.7-ckt2-1~bpo70+1) of mine while forwarding GRE packets. Could this be the fix for this bug: https://lists.ubuntu.com/archives/kernel-team/2014-December/052158.html gre: Set inner mac header in gro complete I cannot confirm this myself right now, as the only systems affected are in production and I am not able to set up a lab installation right now. Grüße, Sven. signature.asc Description: OpenPGP digital signature
Bug#776172: vlc: crash (segmentation fault) on a webm file
On 2015-02-18 01:26:37, Sebastian Ramacher wrote: On 2015-02-18 01:15:04, Vincent Lefevre wrote: On 2015-02-17 18:51:05 +0100, Sebastian Ramacher wrote: I just wanted to make sure that you test against a clean install. The missing libraries made me a bit suspicious. Anyway, we still need a sample. I can reproduce the crash by doing: head -c 20 Nosferatu_a_Venezia_-_Pelicula_Completa_audio_espa_ol.webm sample.webm then doing vlc sample.webm, setting the speed to 3x, then doing a sequence of stop/play. This doesn't always yield a crash. I sometimes need to do Ctrl-C and try again several times. Please attach the file to the bug report. Or send the file to me. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#759001: [systemd-devel] sysv-generator: doesn't handle /etc/insserv/overrides or /etc/chkconfig.d
Am 17.02.2015 um 23:43 schrieb Christian Seiler: Am 17.02.2015 um 13:04 schrieb Christian Seiler: Thinking about it, perhaps we could use Documentation=? Just add a Documentation=file:///etc/insserv/overrides/$NAME? Then at least systemctl status will show the information. Not perfect, but probably better than nothing... Somehow I think we should make clear though, that this is a transitional measure and parsing of insserv overrides is not going to be supported forever. Then perhaps write out a INFO priority log message (the lowest one that's still higher than DEBUG), saying that the override was used but is deprecated? And add a logcheck-ignore rule for this message, since this is something the administrator should see when looking at the logs, but not be reminded of every time systemctl daemon-reload is executed. Thoughts? I've implemented both of these and attached a modified version of the patch. Do you have any objections? If not, I'll ask for pre- approval by the release team. Sorry for not replying earlier. Both ideas sounds fine to me, thanks! -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#776172: vlc: crash (segmentation fault) on a webm file
On 2015-02-18 01:15:04, Vincent Lefevre wrote: On 2015-02-17 18:51:05 +0100, Sebastian Ramacher wrote: I just wanted to make sure that you test against a clean install. The missing libraries made me a bit suspicious. Anyway, we still need a sample. I can reproduce the crash by doing: head -c 20 Nosferatu_a_Venezia_-_Pelicula_Completa_audio_espa_ol.webm sample.webm then doing vlc sample.webm, setting the speed to 3x, then doing a sequence of stop/play. This doesn't always yield a crash. I sometimes need to do Ctrl-C and try again several times. Please attach the file to the bug report. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#777264: Could not connect to ftp.tw.debian.org:80 (140.112.8.139). - connect (110: Connection timed out)
Hi all, I think current master official mirror in Taiwan is not stable and reliable enough(for many times, its data is old even when it's alive), I'll respectfully suggest DSA team to temporarily change our mirror to another site, and maybe decide to choose a site to be the new mirror. FYI, http://free.nchc.org.tw/debian may be a good choice for this, and you may want to contact with the manager Steven with the issue about being Taiwan official local mirror, his eamil address ste...@nchc.org.tw, but they didn't provide rsync, debian.nctu.edu.tw will provide rsync protocol, just let you know! Best regards, Peter
Bug#778608: Acknowledgement (systemd: please consider backporting logind CAP_SYS_ADMIN fixes)
Hmpf, great, I just noticed I forgot to actually attach the
patch. :(
Here it is.
Sorry about the confusion,
Christian
Description: logind: handle runtime dir without CAP_SYS_ADMIN
In (e.g. LXC) containers without CAP_SYS_ADMIN, logind fails to mount
a tmpfs over /run/user/$UID (lacking mount permissions).
.
Now, logind will resort to chown+chmod of the directory instead. This
allows logind to still work in those environments, although without
the guarantees it provides (i.e. users not being able to DoS /run or
other users' /run/user/$UID space) when CAP_SYS_ADMIN is available.
Author: Christian Seiler christ...@iwakd.de
Origin: backport
Applied-Upstream: 4d858e7d9f39038713f760d7acc64acf7bba2aa7, 11c6476a08af7a8a9ae6a2d0f8370587f7b31663
Last-Update: 2015-02-17
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/src/login/logind-user.c
+++ b/src/login/logind-user.c
@@ -340,8 +340,21 @@ static int user_mkdir_runtime_path(User
r = mount(tmpfs, p, tmpfs, MS_NODEV|MS_NOSUID, t);
if (r 0) {
-log_error(Failed to mount per-user tmpfs directory %s: %s, p, strerror(-r));
-goto fail;
+r = -errno;
+if (r != -EPERM) {
+log_error(Failed to mount per-user tmpfs directory %s: %m, p);
+goto fail;
+}
+
+/* Lacking permissions, maybe
+ * CAP_SYS_ADMIN-less container? In this case,
+ * just use a normal director. */
+
+r = chmod_and_chown(p, 0700, u-uid, u-gid);
+if (r 0) {
+log_error(Failed to change runtime directory ownership and mode: %s, strerror(-r));
+goto fail;
+}
}
}
@@ -349,7 +362,11 @@ static int user_mkdir_runtime_path(User
return 0;
fail:
-free(p);
+if (p) {
+/* Try to clean up, but ignore errors */
+(void) rmdir(p);
+free(p);
+}
u-runtime_path = NULL;
return r;
}
Bug#778653: unblock: procmail/3.22-24
On Tue, Feb 17, 2015 at 11:40:48PM +0100, Moritz Muehlenhoff wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package procmail. It fixes several heap overflows and memory corruptions spotted in recent fuzzing attempts (one has been assigned CVE-2014-9681). unblock procmail/3.22-24 Thanks for submitting the report. Yes, 3.22-24 is intended for jessie. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777546: Please don't grant localhost unconditional access to mod_status
On Monday 09 February 2015 16:34:02, Jean-Michel Nirgal Vourgère wrote: What is your opinion on that problem? That's a valid feature request. But for after jessie. Do you see a more generic way to restrict tor incoming connections so that it doesn't match require local filter? I don't have the perfect idea right now. One could configure an additional localhost address like 127.0.0.2, make the tor hidden service forward to that ip, and change mod_status' config to explicitly require 127.0.0.1. But one still needs to change the config because require local matches 127.0.0.0/8. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772107: unblock: bind-dyndb-ldap/6.0-4
From the diff, I see that there might be a missing dependency on bind9, cache directory not writable, default keytab file non-existent. There are other changes but didn't read them carefully, tbh. The changelog also seems in contradiction with the scripts since : + * rules, postinst: Create /var/cache/bind/dyndb-ldap owned by bind user. but +chown root:bind /var/cache/bind/dyndb-ldap Maybe the package is still broken? Since it is a new package (not present in past stable releases) and didn't get enough users yet. I have to admit I am not very excited at the idea of providing a half-broken package to Jessie users (remember that -4 didn't migrate to Jessie). Thus, I am considering removing it from Jessie. The good news is that you will be able to apply all changes you want. You will also be able to provide a package for Jessie through backports. What do you think? Regards, -- Mehdi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775892: [Python-modules-team] Bug#775892: unblock (pre-approval): python-django/1.7.3-1
Le 2015-02-17 23:46, Brian May a écrit : On 18 February 2015 at 07:31, Mehdi Dogguy me...@dogguy.org wrote: Note that this not mean that we will accept (let's say) 1.7.5 next time. I assume you mean that when 1.7.5 comes out, we should make another unblock request? Yes. The idea is to not assume that a new minor release will be accepted at this stage. So, as usual, if you feel an update to the package is needed, please file a bug report and talk to us explaining your plan before taking actions. Regards, -- Mehdi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778658: gcc-snapshot: FTBFS on hppa -- switch to g++ breaks hppa64 cross
Package: gcc-snapshot
Version: 20150211-1
Severity: normal
From build log:
checking for libvtv support... no
checking for hppa-linux-gnu-gcc...
/home/dave/debian/gcc-snapshot/gcc-snapshot-20150211/build/gcc/xg++
-B/home/dave/debian/gcc-snapshot/gcc-snapshot-20150211/build/gcc/
checking for C compiler default output file name...
configure: error: in
`/home/dave/debian/gcc-snapshot/gcc-snapshot-20150211/build-hppa64':
configure: error: C compiler cannot create executables
See `config.log' for more details.
debian/rules2:1283: recipe for target 'stamps/04-configure-hppa64-stamp' failed
make[1]: *** [stamps/04-configure-hppa64-stamp] Error 77
make[1]: Leaving directory
'/home/dave/debian/gcc-snapshot/gcc-snapshot-20150211'
debian/rules:35: recipe for target 'stamps/04-configure-hppa64-stamp' failed
make: *** [stamps/04-configure-hppa64-stamp] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
From config.log:
configure:4345: checking for C compiler default output file name
configure:4367: /home/dave/debian/gcc-snapshot/gcc-snapshot-20150211/build/gcc/x
g++ -B/home/dave/debian/gcc-snapshot/gcc-snapshot-20150211/build/gcc/conftes
t.c 5
/usr/bin/ld.bfd.real: cannot find -lstdc++
collect2: error: ld returned 1 exit status
configure:4371: $? = 1
configure:4408: result:
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME
| #define PACKAGE_TARNAME
| #define PACKAGE_VERSION
| #define PACKAGE_STRING
| #define PACKAGE_BUGREPORT
| #define PACKAGE_URL | /* end confdefs.h. */
| | int
| main ()
| {
|
| ;
| return 0;
| }
configure:4414: error: in
`/home/dave/debian/gcc-snapshot/gcc-snapshot-20150211/build-hppa64':
configure:4418: error: C compiler cannot create executables
-- System Information:
Debian Release: 8.0
APT prefers unreleased
APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: hppa (parisc64)
Kernel: Linux 3.17.8+ (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_CA.utf8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772963: release-notes: cellphone friendly CSS
2015-02-17 8:53 GMT+01:00 Niels Thykier ni...@thykier.net: By all means, please do make a clone/branch on git.debian.org or github if that will facilitate your work, so you do not stall on me. In case it's easier to apply my patches, I setted up a repository on GitHub: https://github.com/sblondon/release-notes/tree/cellphone-css It's a clone of Niels's git repository. The files are added into the cellphone-css branch. With this last patch, I think the main needs are filled but I remember the warning from Google test suite about the use on small screen. I will probably check that during the week or next week-end. -- Stéphane -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778657: gnupg-agent: Test for existing gpg-agent in /etc/X11/Xsession.d/90gpg-agent is always true
Package: gnupg-agent
Version: 2.0.26-4
Severity: important
Tags: patch
Dear Maintainer,
The gpg-agent Xsession.d script looks as if it wants to test for an existing,
usable gpg-agent. It looks as if it is supposed to skip starting a new one for
the X session if it finds an existing gpg-agent process.
I wanted to use this functionality to run gpg-agent as a user service under
systemd as the sole gpg-agent process for all my sessions. I set up and enabled
the service. systemd starts all enabled user services on the first user login.
I logged in on a virtual console and verified that gpg-agent was running and I
could connect to
it. Then I logged in to an X session and noticed that X had still started its
own gpg-agent.
The code that looks like it should check for gpg-agent is here:
/etc/X11/Xsession.d/90gpg-agent:
6: if grep -qs '^[[:space:]]*use-agent' $GNUPGHOME/gpg.conf
$GNUPGHOME/options
7:test -x $GPGAGENT
8:{ test -z $GPG_AGENT_INFO || ! $GPGAGENT 2/dev/null; }; then
GPGAGENT=/usr/bin/gpg-agent
When run without arguments, gpg-agent's exit status will be 0 if it can connect
to an existing gpg-agent process, a positive value if it cannot. Regardless of
exit status, gpg-agent run without arguments writes all output to stderr.
So, the second part of the expression in line 8 is alwys true. The output of
'$GPAGENT 2/dev/null' is always an empty string because gpg-agent sends all
output to stderr. [ ! ] is true.
So, the entire expression on line 8 is always true. But in my testing, I also
couldn't configure X so that it passed environment variables to the X session.
I wrote a .xsession file like this:
#!/bin/sh
export MYTESTVAR=test
eval startxfce4
and then added 'echo $MYTESTVAR /tmp/mytestvar' to 90gpg-agent. But the
corresponding echo-to-file statement in 90gpg-agent never wrote anything. Am I
missing an obvious method of passing $GPG_AGENT_INFO to 90gpg-agent?
If the intent of line 8 is to keep each X session from starting its own
gpg-agent if another gpg-agent is running and connectable, then the script
should test the return value of gpg-agent without arguments, not the output. If
there are no ways to pass environment to startx or startxfce4, then 90gpg-agent
will also have to attempt to load $HOME/.gpg-agent-info.
I made those changes my 90gpg-agent file, inline. I also attached the changes
as a patch to gnupg2/debian/gnupg-agent.xsession.
Thanks,
Brian
-- System Information:
Debian Release: 8.0
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (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
Init: systemd (via /run/systemd/system)
Versions of packages gnupg-agent depends on:
ii libassuan02.1.2-2
ii libc6 2.19-13
ii libgcrypt20 1.6.2-4+b1
ii libgpg-error0 1.17-3
ii libpth20 2.0.7-20
ii libreadline6 6.3-8+b3
ii pinentry-gtk2 [pinentry] 0.8.3-2
Versions of packages gnupg-agent recommends:
ii gnupg 1.4.18-6
ii gnupg2 2.0.26-4
gnupg-agent suggests no packages.
-- Configuration Files:
/etc/X11/Xsession.d/90gpg-agent changed:
: ${GNUPGHOME=$HOME/.gnupg}
GPGAGENT=/usr/bin/gpg-agent
PID_FILE=$GNUPGHOME/gpg-agent-info-$(hostname)
INFO_FILE=$HOME/.gpg-agent-info
if test -f $INFO_FILE; then
eval $(cat $INFO_FILE)
# Exports GPG_AGENT_INFO, SSH_AUTH_SOCK, etc.
eval $(cut -d= -f 1 $INFO_FILE | xargs echo export)
fi
if test -x $GPGAGENT; then
# Invoking gpg-agent with no arguments exits successfully if the agent
# is already running as pointed by $GPG_AGENT_INFO
$GPGAGENT 2/dev/null
GPGAGENT_RUNNING=$?
else
GPGAGENT_RUNNING=1
fi
if grep -qs '^[[:space:]]*use-agent' $GNUPGHOME/gpg.conf $GNUPGHOME/options
( test -z $GPG_AGENT_INFO || $GPGAGENT_RUNNING -gt 0 ); then
if [ -r $PID_FILE ]; then
. $PID_FILE
fi
STARTUP=$GPGAGENT --daemon --sh --write-env-file=$PID_FILE $STARTUP
fi
-- no debconf information
diff --git a/debian/gnupg-agent.xsession b/debian/gnupg-agent.xsession
index eb8c5847..7ecaefe2 100644
--- a/debian/gnupg-agent.xsession
+++ b/debian/gnupg-agent.xsession
@@ -2,18 +2,29 @@
GPGAGENT=/usr/bin/gpg-agent
PID_FILE=$GNUPGHOME/gpg-agent-info-$(hostname)
+INFO_FILE=$HOME/.gpg-agent-info
+
+if test -f $INFO_FILE; then
+ eval $(cat $INFO_FILE)
+ # Exports GPG_AGENT_INFO, SSH_AUTH_SOCK, etc.
+ eval $(cut -d= -f 1 $INFO_FILE | xargs echo export)
+fi
+
+if test -x $GPGAGENT; then
+ # Invoking gpg-agent with no arguments exits successfully if the agent
+ # is already running as pointed by $GPG_AGENT_INFO
+ $GPGAGENT 2/dev/null
+ GPGAGENT_RUNNING=$?
+else
+ GPGAGENT_RUNNING=1
+fi
if grep -qs '^[[:space:]]*use-agent' $GNUPGHOME/gpg.conf $GNUPGHOME/options
- test -x $GPGAGENT
- { test -z $GPG_AGENT_INFO
Bug#778659: cppcheck: check for double evaluation when using macros
Package: cppcheck
Severity: wishlist
The article at [1] reports about an issue with the MIN and MAX macros
that cause double evaluation by default. I think the more general issue
is worth checking for, please add a check for double evaluation when
using macros. Here is a test case from [1], the warning should trigger
on the second use of the min macro but not the first.
#include stdio.h
#define min(a, b) ((a) (b)) ? (a) : (b)
int main() {
int a = 1, b = 2;
printf (%d\n, min (a, b));
printf (a=%d, b=%d\n\n, a, b);
printf (%d\n, min (a++, b++));
printf (a=%d, b=%d\n\n, a, b);
}
1. http://dustri.org/b/min-and-max-macro-considered-harmful.html
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
Bug#776611: [Pkg-gnupg-maint] Bug#776611: [dirmngr] segfaults
Hi, stat /var/cache/dirmngr/crls.d/DIR.txt device 65024 inode 330320 mode33184 nlink 1 uid 126 gid 133 rdev0 size0 atime 1424002234 mtime 1351168424 ctime 1422569978 blksize 4096 blocks 0 link ls -l /var/cache/dirmngr/crls.d/DIR.txt -rw-r- 1 dirmngr dirmngr 0 Oct 25 2012 /var/cache/dirmngr/crls.d/DIR.txt yes its empty. And no i don't know how it got in that state. Its a notebook i daily use, i use XFS which is known to behave not always nice if the power is cut. And i never cared about dirmngr, even now i don't know why its running. so it looks like, it broken for a long time.. greetings, and thanks for the fix On 02/17/2015 12:24 AM, Daniel Kahn Gillmor wrote: Control: tags 776611 - moreinfo unreproducible Hi Florian-- Sorry for taking a little while to get to this... On Thu 2015-02-05 02:59:28 -0500, Florian Reitmeir wrote: cat /var/log/dirmngr/dirmngr.log 2015-02-02 06:36:34 dirmngr[3324.0] permanently loaded certificates: 0 2015-02-02 06:36:34 dirmngr[3324.0] runtime cached certificates: 0 2015-02-02 16:02:48 dirmngr[2517.0] permanently loaded certificates: 0 2015-02-02 16:02:48 dirmngr[2517.0] runtime cached certificates: 0 2015-02-03 22:48:20 dirmngr[2384.0] permanently loaded certificates: 0 2015-02-03 22:48:20 dirmngr[2384.0] runtime cached certificates: 0 [...] attached is a stack trace, .. Thanks for this information! It looks to me like the errors are related to loading the CRL cache. (in particular, in open_dir() in src/crlcache.c). I think i'm now able to reproduce this. I suspect you have a zero-length file in /var/cache/dirmngr/crls.d/DIR.txt, is that correct? can you show me the output of: stat /var/cache/dirmngr/crls.d/DIR.txt If you move that file out of the way, can you start dirmngr without it crashing? mv /var/cache/dirmngr/crls.d/DIR.txt /var/cache/dirmngr/crls.d/DIR.txt.bak If this works, do you have any idea how dirmngr's crlcache got into this state? I'm working on a patch now. --dkg -- Dipl.-Inf. Univ. Florian Reitmeir E-Mail: n...@multi24.com Tel: +43 650 2661660 Fax: +43 650 2661660 HP: http://net.multi24.com Amraserstr 23 6020 Innsbruck / Austria -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776172: vlc: crash (segmentation fault) on a webm file
On 2015-02-17 18:51:05 +0100, Sebastian Ramacher wrote: I just wanted to make sure that you test against a clean install. The missing libraries made me a bit suspicious. Anyway, we still need a sample. I can reproduce the crash by doing: head -c 20 Nosferatu_a_Venezia_-_Pelicula_Completa_audio_espa_ol.webm sample.webm then doing vlc sample.webm, setting the speed to 3x, then doing a sequence of stop/play. This doesn't always yield a crash. I sometimes need to do Ctrl-C and try again several times. -- Vincent Lefèvre vinc...@vinc17.net - Web: https://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: https://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778581: systemd install breaks chroot jail and compromises guest system
Hello, Michael Biebl Am Dienstag, 17. Februar 2015 10:39:45 schrieben Sie: So I think systemd got installed accidentially by breaking the chroot. What you describe sounds highly unlikely. Merely installing systemd in a chroot will not break the chroot. To me it looks like you accidentally installed systemd on the host system yourself, or it was already installed. Of course, this is the first explanation that came to my mind, too. However, I had reconfigured the bash prompt of the chroot to take care of this risk. Am Dienstag, 17. Februar 2015 18:42:11 schrieben Sie: Since the given information is not sufficient to diagnose your issue, it would be great if you can provide step-by-step instructions how to reproduce the problem and a more detail log of the events that happened. hm ... I understand your desire, but this not so easy from a system that crashed. Il try to collect some of my copy/pastes from a database where I'm collecting my notes and merge it with my memory: ---8- dracut module 'systemd' will not be installed, because command '/lib/systemd/systemd' could not be found! CHR#root@blade-001:~# apt-get install systemd W: Not using locking for read only lock file /var/lib/dpkg/lock E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. root@cruncher:/cluster/node_roots/wheezy-dbstr-2015_02_10/mp-aufs-admin# chroot /cluster/node_roots/wheezy-dbstr-2015_02_10/mp-aufs-admin dpkg --configure -a -8- This CHR#root@blade-001:~# is the chrooted prompt This root@cruncher:/cluster/node_roots/wheezy-dbstr-2015_02_10/mp-aufs-admin# is the host system prompt So, as it looks, you are half way right: I did call the dpkg configure -a command from the host, however, chrooting it. But shouldn't this be the same??? And even if I called dpkg --configure -a from the host - it is not supposed to screw the machine, is it? Or may be, that something else was in the dpkg configuration pipeline, that screwed the box - completely unrelated to the chrooted systemd? Hm, well, this could be I'll include the dpkg.log Does this tell anything to you? reproduce the problem setting up systems just to screw them? Well, if this is the only option, I'd prefer to keep the issue for the archives. If this never and nowhere happened before and after - fine for everybody. Wolfgang Rosner 2015-02-03 20:02:41 startup archives unpack 2015-02-03 20:02:41 install libfindbin-libs-perl:all keine 1.64-1 2015-02-03 20:02:41 status half-installed libfindbin-libs-perl:all 1.64-1 2015-02-03 20:02:42 status triggers-pending man-db:amd64 2.7.0.2-5 2015-02-03 20:02:42 status unpacked libfindbin-libs-perl:all 1.64-1 2015-02-03 20:02:42 status unpacked libfindbin-libs-perl:all 1.64-1 2015-02-03 20:02:42 trigproc man-db:amd64 2.7.0.2-5 keine 2015-02-03 20:02:42 status half-configured man-db:amd64 2.7.0.2-5 2015-02-03 20:02:44 status installed man-db:amd64 2.7.0.2-5 2015-02-03 20:02:45 startup packages configure 2015-02-03 20:02:45 configure libfindbin-libs-perl:all 1.64-1 keine 2015-02-03 20:02:45 status unpacked libfindbin-libs-perl:all 1.64-1 2015-02-03 20:02:45 status half-configured libfindbin-libs-perl:all 1.64-1 2015-02-03 20:02:45 status installed libfindbin-libs-perl:all 1.64-1 2015-02-03 20:02:45 startup packages configure 2015-02-03 20:04:33 startup archives unpack 2015-02-03 20:04:33 install libdir-self-perl:all keine 0.10-1 2015-02-03 20:04:33 status half-installed libdir-self-perl:all 0.10-1 2015-02-03 20:04:33 status triggers-pending man-db:amd64 2.7.0.2-5 2015-02-03 20:04:33 status unpacked libdir-self-perl:all 0.10-1 2015-02-03 20:04:33 status unpacked libdir-self-perl:all 0.10-1 2015-02-03 20:04:33 trigproc man-db:amd64 2.7.0.2-5 keine 2015-02-03 20:04:33 status half-configured man-db:amd64 2.7.0.2-5 2015-02-03 20:04:36 status installed man-db:amd64 2.7.0.2-5 2015-02-03 20:04:36 startup packages configure 2015-02-03 20:04:36 configure libdir-self-perl:all 0.10-1 keine 2015-02-03 20:04:36 status unpacked libdir-self-perl:all 0.10-1 2015-02-03 20:04:36 status half-configured libdir-self-perl:all 0.10-1 2015-02-03 20:04:36 status installed libdir-self-perl:all 0.10-1 2015-02-03 20:04:36 startup packages configure 2015-02-05 20:54:35 startup archives unpack 2015-02-05 20:54:38 install firmware-qlogic:all keine 0.43 2015-02-05 20:54:38 status half-installed firmware-qlogic:all 0.43 2015-02-05 20:54:39 status unpacked firmware-qlogic:all 0.43 2015-02-05 20:54:39 status unpacked firmware-qlogic:all 0.43 2015-02-05 20:54:39 startup packages configure 2015-02-05 20:54:39 configure firmware-qlogic:all 0.43 keine 2015-02-05 20:54:39 status unpacked firmware-qlogic:all 0.43 2015-02-05 20:54:39 status half-configured firmware-qlogic:all 0.43 2015-02-05 20:54:39 status installed
Bug#778656: Malformed access ACL
Package: systemd Version: 219-1 Severity: important I do have persistent logging enabled. After the update to 219-1, I get the following messages on dpkg-reconfigure -a systemd # dpkg-reconfigure systemd setfacl: /var/log/journal/567a68a5c2672114bcf5192d0008: Malformed access ACL `user::rwx,group::r-x,group:adm:r-x,group:adm:r-x,mask::r-x,other::r-x': Duplicate entries at entry 4 setfacl: /var/log/journal/567a68a5c2672114bcf5192d0008/system@718656154e1546fcb5d438a9edf3155f-0026448b-00050de41b746eac.journal: Malformed access ACL `user::rw-,group::r-x,group:adm:r-x,group:adm:r-x,mask::r-x,other::---': Duplicate entries at entry 4 setfacl: /var/log/journal/567a68a5c2672114bcf5192d0008/user-65534@8ebf0fb523894a288a10e73985268fd3-00210822-00050b7271af4e5f.journal: Malformed access ACL `user::rw-,user:nobody:r--,group::r-x,group:adm:r-x,group:adm:r-x,mask::r-x,other::---': Duplicate entries at entry 5 setfacl: /var/log/journal/567a68a5c2672114bcf5192d0008/user-109.journal: Malformed access ACL `user::rw-,user:Debian-gdm:r--,group::r-x,group:adm:r-x,group:adm:r-x,mask::r-x,other::r--': Duplicate entries at entry 5 setfacl: /var/log/journal/567a68a5c2672114bcf5192d0008/user-1000@00050e6501bfa725-1728cb2f60eede7c.journal~: Malformed access ACL `user::rw-,user:michael:r--,group::r-x,group:adm:r-x,group:adm:r-x,mask::r-x,other::---': Duplicate entries at entry 5 setfacl: /var/log/journal/567a68a5c2672114bcf5192d0008/user-1001.journal: Malformed access ACL `user::rw-,user:test:r--,group::r-x,group:adm:r-x,group:adm:r-x,mask::r-x,other::---': Duplicate entries at entry 5 setfacl: /var/log/journal/567a68a5c2672114bcf5192d0008/user-1000@690216233b624f11a2201e9f98176515-0021f2f2-00050c4b51fd09dc.journal: Malformed access ACL `user::rw-,user:michael:r--,group::r-x,group:adm:r-x,group:adm:r-x,mask::r-x,other::---': Duplicate entries at entry 5 setfacl: /var/log/journal/567a68a5c2672114bcf5192d0008/system@00050e650144ab12-15158e9a9df4f071.journal~: Malformed access ACL `user::rw-,group::r-x,group:adm:r-x,group:adm:r-x,mask::r-x,other::---': Duplicate entries at entry 4 setfacl: /var/log/journal/567a68a5c2672114bcf5192d0008/system@718656154e1546fcb5d438a9edf3155f-0001-00050c4b51788fe4.journal: Malformed access ACL `user::rw-,group::r-x,group:adm:r-x,group:adm:r-x,mask::r-x,other::---': Duplicate entries at entry 4 setfacl: /var/log/journal/567a68a5c2672114bcf5192d0008/user-65534.journal: Malformed access ACL `user::rw-,user:nobody:r--,group::r-x,group:adm:r-x,group:adm:r-x,mask::r-x,other::---': Duplicate entries at entry 5 setfacl: /var/log/journal/567a68a5c2672114bcf5192d0008/system.journal: Malformed access ACL `user::rw-,group::r-x,group:adm:r-x,group:adm:r-x,mask::r-x,other::---': Duplicate entries at entry 4 setfacl: /var/log/journal/567a68a5c2672114bcf5192d0008/user-1000.journal: Malformed access ACL `user::rw-,user:michael:r--,group::r-x,group:adm:r-x,group:adm:r-x,mask::r-x,other::---': Duplicate entries at entry 5 root@pluto:~# ls -la /var/log/journal/ total 32 drwxr-sr-x+ 3 root systemd-journal 4096 Feb 18 00:37 . drwxr-xr-x. 22 root root12288 Feb 17 23:08 .. drwxr-sr-x+ 2 root systemd-journal 12288 Feb 6 06:51 567a68a5c2672114bcf5192d0008 root@pluto:~# ls -la /var/log/journal/567a68a5c2672114bcf5192d0008/ total 426072 drwxr-sr-x+ 2 root systemd-journal 12288 Feb 6 06:51 . drwxr-sr-x+ 3 root systemd-journal 4096 Feb 18 00:37 .. -rw-r-x---+ 1 root systemd-journal 67108864 Feb 18 00:38 system.journal -rw-r-x---+ 1 root systemd-journal 25165824 Feb 6 06:50 system@00050e650144ab12-15158e9a9df4f071.journal~ -rw-r-x---+ 1 root systemd-journal 134217728 Jan 30 21:04 system@718656154e1546fcb5d438a9edf3155f-0001-00050c4b51788fe4.journal -rw-r-x---+ 1 root systemd-journal 33554432 Feb 5 16:08 system@718656154e1546fcb5d438a9edf3155f-0026448b-00050de41b746eac.journal -rw-r-x---+ 1 root systemd-journal 41943040 Feb 18 00:37 user-1000.journal -rw-r-x---+ 1 root systemd-journal 8388608 Feb 6 06:51 user-1000@00050e6501bfa725-1728cb2f60eede7c.journal~ -rw-r-x---+ 1 root systemd-journal 92274688 Feb 5 16:08 user-1000@690216233b624f11a2201e9f98176515-0021f2f2-00050c4b51fd09dc.journal -rw-r-x---+ 1 root systemd-journal 8388608 Feb 16 17:31 user-1001.journal -rw-r-xr--+ 1 root systemd-journal 8388608 Sep 13 02:27 user-109.journal -rw-r-x---+ 1 root systemd-journal 8388608 Feb 17 23:13 user-65534.journal -rw-r-x---+ 1 root systemd-journal 8388608 Feb 5 16:08 user-65534@8ebf0fb523894a288a10e73985268fd3-00210822-00050b7271af4e5f.journal root@pluto:~# getfacl /var/log/journal/567a68a5c2672114bcf5192d0008/system.journal getfacl: Removing leading '/' from absolute path names # file: var/log/journal/567a68a5c2672114bcf5192d0008/system.journal # owner: root # group: systemd-journal user::rw- group::r-x group:adm:r-x group:adm:r-x mask::r-x other::---
Bug#778239: Strange GRE packet forwarding slowness in 3.16.7-ckt2-1~bpo70+1
On Wed, 2015-02-18 at 00:14 +0100, Sven Hartge wrote: On Thu, 12 Feb 2015 16:33:09 +0100 Sven Hartge s...@svenhartge.de wrote: I have encountered a strange slowness on a router/packetfilter system (Wheezy 7.8 with backported kernel 3.16.7-ckt2-1~bpo70+1) of mine while forwarding GRE packets. Could this be the fix for this bug: https://lists.ubuntu.com/archives/kernel-team/2014-December/052158.html gre: Set inner mac header in gro complete I don't know. I cannot confirm this myself right now, as the only systems affected are in production and I am not able to set up a lab installation right now. As that went into 3.16.7-ckt3, it is therefore included in the current packages in testing/unstable. Ben. -- Ben Hutchings To err is human; to really foul things up requires a computer. signature.asc Description: This is a digitally signed message part
Bug#778239: Strange GRE packet forwarding slowness in 3.16.7-ckt2-1~bpo70+1
On Wed, 2015-02-18 at 01:25 +, Ben Hutchings wrote: On Wed, 2015-02-18 at 00:14 +0100, Sven Hartge wrote: On Thu, 12 Feb 2015 16:33:09 +0100 Sven Hartge s...@svenhartge.de wrote: I have encountered a strange slowness on a router/packetfilter system (Wheezy 7.8 with backported kernel 3.16.7-ckt2-1~bpo70+1) of mine while forwarding GRE packets. Could this be the fix for this bug: https://lists.ubuntu.com/archives/kernel-team/2014-December/052158.html gre: Set inner mac header in gro complete I don't know. I cannot confirm this myself right now, as the only systems affected are in production and I am not able to set up a lab installation right now. As that went into 3.16.7-ckt3, it is therefore included in the current packages in testing/unstable. ...and wheezy-backports. Ben. -- Ben Hutchings To err is human; to really foul things up requires a computer. signature.asc Description: This is a digitally signed message part
Bug#775506: unblock: tbb/4.2~20140122-4
Hi, arm64 should be building in -5, so shouldn't the arm64 reverse dependancies be unaffected? Under mips, mipsel, and s390x tbb fails to build unit tests due to missing/incorrect gcc atomics. I have very little confidence in the functional correctness of the reverse dependencies, so I would be inclined to remove them to be safe. Mathieu, please shout if I've missed something. Thank you for looking at this and apologies again for me messing things up before the freeze. Steve On 18/02/2015, Mehdi Dogguy me...@dogguy.org wrote: Hi all, Le 2015-01-16 23:37, Jonathan Wiltshire a écrit : Control: tag -1 moreinfo On Fri, Jan 16, 2015 at 03:03:08PM +0100, Mathieu Malaterre wrote: Please unblock package tbb It fixes two grave bugs: #756233 #762656 It also fixes a longer term issue, as depicted in comment: #775263#17 So I understand the debdiff may be a little long, but unblocking current tbb from sid into testing would solve the issue for the long term. Comments welcome Not until the maintainer's objections to this upload are resolved. I'd like to get this request sorted out. We also want to make sure that there is no misunderstanding between you two on the technical decisions implemented in tbb up to -5. Besides, it seems that the list of architectures for this package has been reduced to: amd64, arm64, armhf, hppa, i386, powerpc and ppc64el. It appears that some reverse dependencies should have their binary packages removed from those packages before getting tbb migrated. Before proceeding, we want to be sure that this is what you want and that the list will not change once again in a near future. $ dak rm -s testing -nR -a mips,mipsel,arm64,s390x tbb W: -a/--architecture implies -p/--partial. Will remove the following packages from testing: libtbb-dev | 4.2~20140122-1.1 | mips, mipsel, s390x libtbb-dev | 4.2~20140122-1.1+b1 | arm64 libtbb2 | 4.2~20140122-1.1 | mips, mipsel, s390x libtbb2 | 4.2~20140122-1.1+b1 | arm64 libtbb2-dbg | 4.2~20140122-1.1 | mips, mipsel, s390x libtbb2-dbg | 4.2~20140122-1.1+b1 | arm64 tbb | 4.2~20140122-1.1 | source --- Reason --- Checking reverse dependencies... # Broken Depends: deal.ii: libdeal.ii-8.1.0 [arm64 mipsel] libdeal.ii-dev [arm64 mipsel] flexbar: flexbar [arm64 mips mipsel] mia: libmia-2.2-0 [arm64 mips mipsel] libmia-2.2-dev [arm64 mips mipsel] mia-tools [arm64 mips mipsel] # Broken Build-Depends: clasp: libtbb-dev (= 4.0+r233) deal.ii: libtbb-dev feel++: libtbb-dev flexbar: libtbb-dev gringo: libtbb-dev (= 4.0+r233) mia: libtbb-dev (= 3.0) opencv: libtbb-dev openturns: libtbb-dev openvdb: libtbb-dev Regards, -- Mehdi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778655: doxygen: Doxygen should not enable markdown by default
Package: doxygen Version: 1.8.8-5 Severity: serious Justification: Creates broken documentation in many packages Hi, So doxygen 1.8 added support for interpreting markdown, and it does this in all normal comment blocks before applying the normal doxygen formatting. Unfortunately, they also chose to enable this by default, so any package that is building docs against this version, which didn't update the doxyconf configuration using this version, to see that this option exists and to turn it off if it breaks the generated documentation, is going to run a fairly high chance of generating fairly horribly broken docs. A quick canary for the extent of this problem is to search for: 'warning: unexpected command endcode' Which went by uncommented on (or I assume inspected) in logs such as was posted to https://bugs.debian.org/680896 and many other places. This is just one fairly common way this fails horribly, resulting in all the comments *above* a @code section being treated as code, and the code section itself being dumped literally to the output - but there are quite a few other ways this will generate awful unreadable documentation when markdown syntax is inadvertently applied to an existing codebase. Unless we want to ship with a lot of fairly useless -doc packages, it seems like this should probably be disabled by default, until people have become more aware of the problem and have taken steps to avoid it in their own source. I found a lot of build logs that show people having this problem, but no discussion of the cause, the impact, or the fix. I suspect a lot of people who build -doc packages rarely or never actually read them themselves ... Fixing the ones that are already broken is probably going to be something of a major operation in its own right, but the mood in #d-d seemed to be that we should start by limiting the damage here and then tackle that part separately. Ron -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778581: systemd install breaks chroot jail and compromises guest system
Am 17.02.2015 um 23:34 schrieb Wolfgang Rosner: Am Dienstag, 17. Februar 2015 10:39:45 schrieben Sie: reproduce the problem setting up systems just to screw them? That's what VMs are for :-) -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#628659: [php-maint] Bug#628659: please support IPv6 connections
On Tue, 31 May 2011 12:51:49 +0200 martin f krafft madd...@debian.org wrote: forwarded 628659 http://pear.php.net/bugs/bug.php?id=18575 tags 628659 upstream thanks also sprach Thomas Goirand tho...@goirand.fr [2011.05.31.1105 +0200]: While I'm ok to maintain the *package* for php-net-smtp (as being part of the pkg-php team), but I wont do any new code on it (just eventually fixing issues), especially new features. So best might be to send a bug report upstream (there's also a bug tracker at pear.php.net), or send a patch (here and upstream). Done. The problem was in Net::Socket which is a Net::SMTP dependency. Anyway the problem was fixed on version 1.0.13 since 2013-05-22 (and Debian has now 1.0.14 and i've tested the smtp connection with php-net-smtp which is ok with this version). I'll reassign this bug to php-net-socket and mark it fixed in corresponding version. FYI, Net::Socket use php fsockopen() and it first connect to IPv6 when available (not sure how it is managed in the php source code). -- .''`. martin f. krafft madduck@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems in diving to the bottom of pleasure we bring up more gravel than pearls. -- honoré de balzac signature.asc Description: This is a digitally signed message part
Bug#759001: [systemd-devel] sysv-generator: doesn't handle /etc/insserv/overrides or /etc/chkconfig.d
Am 18.02.2015 um 00:38 schrieb Ansgar Burchardt:
I've implemented both of these and attached a modified version of
the patch. Do you have any objections? If not, I'll ask for pre-
approval by the release team.
The load_sysv function also has a heuristic to guess whether the init
script support the release action or not:
/* Try to figure out whether this init script supports
* the reload operation. This heuristic looks for
* Usage lines which include the reload option. */
As far as I can see this will no longer work with the proposed changes
when an override file is present: load_sysv will only process the
override file and never see the usage line used in the heuristic.
Oh, nice catch, thanks!
I've changed the logic slightly and tested it in all four possible
combinations (w/ or w/o reload support, w/ or w/o override), it now
works as expected. I also looked at the function to see if there
were some other surprises in there, but the the rest just parses
headers.
I've attached an updated patch. Any objections to that?
Christian
From: Christian Seiler christ...@iwakd.de
Date: Tue, 17 Feb 2015 00:27:21 +0100
Subject: sysv-generator: add support for /etc/insserv/overrides
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759001
---
src/sysv-generator/sysv-generator.c | 33 +++--
1 file changed, 23 insertions(+), 10 deletions(-)
--- a/src/sysv-generator/sysv-generator.c
+++ b/src/sysv-generator/sysv-generator.c
@@ -41,6 +41,8 @@
#include fileio.h
#include hashmap.h
+#define SYSV_OVERRIDE_PATH/etc/insserv/overrides/
+
typedef enum RunlevelType {
RUNLEVEL_SYSINIT,
RUNLEVEL_UP,
@@ -76,6 +78,7 @@ static const struct {
typedef struct SysvStub {
char *name;
char *path;
+char *override_path;
char *description;
bool sysinit;
int sysv_start_priority;
@@ -207,6 +210,12 @@ static int generate_unit_file(SysvStub *
if (!isempty(conflicts))
fprintf(f, Conflicts=%s\n, conflicts);
+/* make systemctl status show the information that the headers
+ * were overridden; not the most elegant way, but SourcePath=
+ * only accepts a single entry */
+if (s-override_path)
+fprintf(f, Documentation=file://%s\n, s-override_path);
+
fprintf(f,
\n[Service]\n
Type=forking\n
@@ -351,7 +360,7 @@ finish:
return 1;
}
-static int load_sysv(SysvStub *s) {
+static int load_sysv(SysvStub *s, const char *fpath, bool check_for_usage_only) {
_cleanup_fclose_ FILE *f;
unsigned line = 0;
int r;
@@ -368,7 +377,7 @@ static int load_sysv(SysvStub *s) {
assert(s);
-f = fopen(s-path, re);
+f = fopen(fpath, re);
if (!f)
return errno == ENOENT ? 0 : -errno;
@@ -381,7 +390,7 @@ static int load_sysv(SysvStub *s) {
log_error_unit(s-name,
Failed to read configuration file '%s': %m,
- s-path);
+ fpath);
return -errno;
}
@@ -406,6 +415,11 @@ static int load_sysv(SysvStub *s) {
continue;
}
+/* If this is just the run to determine whether the init
+ * script supports reload. */
+if (check_for_usage_only)
+continue;
+
if (state == NORMAL streq(t, ### BEGIN INIT INFO)) {
state = LSB;
s-has_lsb = true;
@@ -456,7 +470,7 @@ static int load_sysv(SysvStub *s) {
if (!path_is_absolute(fn)) {
log_error_unit(s-name,
[%s:%u] PID file not absolute. Ignoring.,
- s-path, line);
+ fpath, line);
continue;
}
@@ -547,7 +561,7 @@ static int load_sysv(SysvStub *s) {
if (r 0)
log_error_unit(s-name,
[%s:%u] Failed to add LSB Provides name %s, ignoring: %s,
- s-path, line, m, strerror(-r));
+ fpath, line, m, strerror(-r));
}
} else if (startswith_no_case(t, Required-Start:) ||
@@ -571,7 +585,7 @@ static int load_sysv(SysvStub *s) {
Bug#778648: devscripts: hitting ctrl-c while an editor is open should terminate bts, but instead it goes ahead
On Tue, Feb 17, 2015 at 04:29:29PM -0500, Daniel Kahn Gillmor wrote: it looks like if you send emacs a SIGINT, it will clean up nicely and terminate with a return code of 0. That seems like suboptimal behavior. Exiting due to a signal doesn't seem like a successful exit. It seems emacs isn't very consistent about this. Running emacsclient to connect to an existing daemon means that frame exits with an exit code of 130, as expected. Running a standalone “emacs -nw”, SIGINT gets caught and doesn't exit. Running a standalone X emacs frame does exit cleanly as you describe. if i run a bts command that drops me into my editor in an X11 environment, emacs spawns as a separate window, while my shell is blocked by the bts invocation (as it should be). if i hit ctrl-C in the shell, though, apparently bts passes the SIGINT through to my editor, and then proceeds to use the contents of the message as prepared. Yes, Perl ignores SIGINT/SIGQUIT while running the external process, so that process gets the signal. I'll adjust bts to inspect the exit code of the process so it doesn't treat a non-zero exit code as success. However, emacs will need to be fixed to not exit with a zero when killed. As an alternative, you can tell bts to cancel by saving an empty file. Cheers, -- James GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy james...@debian.org signature.asc Description: Digital signature
Bug#778546: RFS: miceamaze/4.2-1 -- video game with mice in a maze
On Tue, Feb 17, 2015 at 10:09 PM, Raphaël Champeimont wrote: I have (I hope) addressed the blocking issue and some of your recommendations also. You have addressed the blocking issue, uploaded to Debian. I'm not sure I can fix this, because all I do is ask for SDL to setup a full-screen OpenGL display, but don't think it is possible to specify the behavior on multi-screen. It sounds like SDL2 might have better support for this. Yes. Actually I had checked this list and noticed nothing applied for miceamaze. I have added the changelog entry. BTW, since that entry isn't related to the new upstream release there was no need to indent it under that item in debian/changelog. Did I do that? The only thing I changed is experimental instead of unstable. Is it what you are talking about? I'm talking about the change from Priority optional to extra in debian/control, which you mentioned in the debian/changelog entry for 1.8-2. Last time I checked, SDL2 was not shipped with most linux distributions (in stable releases) so I wanted to wait. Fair enough. I'm surprised because gcc never complained about missing includes. I will look into that later (this is not fixed in this release). The includes aren't completely missing so gcc would not complain, the include-what-you-use tool complains about indirectly including headers via other headers instead of directly including them, when you directly use their functions/macros/classes. The reason is that doing only direct includes reduces the amount of code the compiler has to parse, which speeds things up. It also helps with the other goal of include-what-you-use, which is to remove headers that are no longer used. At least this is how I interpret it. I agress this might have been another option, but actually I did not make this change myself and the other developped preferred to do like this. I see. It is probably too late to change since the images are already combined and can't be un-combined unless the other developer has a copy of the original images? Perhaps you could discuss the idea with them? That's true but I cannot provide anything better because I just downloaded it like this and did not change anything. I see. It is a bit sad you can't change the music in the same ways as the original person did, but that is your choice I guess. So if I want to fix that, I should build two packages: miceamaze with the binary file and miceamaze-data with the rest? Indeed, some info about that on the wiki. https://wiki.debian.org/PkgSplit -- bye, pabs https://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759001: [systemd-devel] sysv-generator: doesn't handle /etc/insserv/overrides or /etc/chkconfig.d
Am 17.02.2015 um 13:04 schrieb Christian Seiler:
Thinking about it, perhaps we could use Documentation=? Just add a
Documentation=file:///etc/insserv/overrides/$NAME? Then at least
systemctl status will show the information. Not perfect, but
probably better than nothing...
Somehow I think we should make clear though, that this is a
transitional
measure and parsing of insserv overrides is not going to be supported
forever.
Then perhaps write out a INFO priority log message (the lowest one
that's still higher than DEBUG), saying that the override was used
but is deprecated? And add a logcheck-ignore rule for this message,
since this is something the administrator should see when looking
at the logs, but not be reminded of every time systemctl
daemon-reload is executed.
Thoughts?
I've implemented both of these and attached a modified version of
the patch. Do you have any objections? If not, I'll ask for pre-
approval by the release team.
Christian
From: Christian Seiler christ...@iwakd.de
Date: Tue, 17 Feb 2015 00:27:21 +0100
Subject: sysv-generator: add support for /etc/insserv/overrides
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759001
---
src/sysv-generator/sysv-generator.c | 33 +++--
1 file changed, 23 insertions(+), 10 deletions(-)
--- a/src/sysv-generator/sysv-generator.c
+++ b/src/sysv-generator/sysv-generator.c
@@ -41,6 +41,8 @@
#include fileio.h
#include hashmap.h
+#define SYSV_OVERRIDE_PATH/etc/insserv/overrides/
+
typedef enum RunlevelType {
RUNLEVEL_SYSINIT,
RUNLEVEL_UP,
@@ -76,6 +78,7 @@ static const struct {
typedef struct SysvStub {
char *name;
char *path;
+char *override_path;
char *description;
bool sysinit;
int sysv_start_priority;
@@ -207,6 +210,12 @@ static int generate_unit_file(SysvStub *
if (!isempty(conflicts))
fprintf(f, Conflicts=%s\n, conflicts);
+/* make systemctl status show the information that the headers
+ * were overridden; not the most elegant way, but SourcePath=
+ * only accepts a single entry */
+if (s-override_path)
+fprintf(f, Documentation=file://%s\n, s-override_path);
+
fprintf(f,
\n[Service]\n
Type=forking\n
@@ -351,7 +360,7 @@ finish:
return 1;
}
-static int load_sysv(SysvStub *s) {
+static int load_sysv(SysvStub *s, const char *lsb_header_path) {
_cleanup_fclose_ FILE *f;
unsigned line = 0;
int r;
@@ -368,7 +377,7 @@ static int load_sysv(SysvStub *s) {
assert(s);
-f = fopen(s-path, re);
+f = fopen(lsb_header_path, re);
if (!f)
return errno == ENOENT ? 0 : -errno;
@@ -381,7 +390,7 @@ static int load_sysv(SysvStub *s) {
log_error_unit(s-name,
Failed to read configuration file '%s': %m,
- s-path);
+ lsb_header_path);
return -errno;
}
@@ -456,7 +465,7 @@ static int load_sysv(SysvStub *s) {
if (!path_is_absolute(fn)) {
log_error_unit(s-name,
[%s:%u] PID file not absolute. Ignoring.,
- s-path, line);
+ lsb_header_path, line);
continue;
}
@@ -547,7 +556,7 @@ static int load_sysv(SysvStub *s) {
if (r 0)
log_error_unit(s-name,
[%s:%u] Failed to add LSB Provides name %s, ignoring: %s,
- s-path, line, m, strerror(-r));
+ lsb_header_path, line, m, strerror(-r));
}
} else if (startswith_no_case(t, Required-Start:) ||
@@ -571,7 +580,7 @@ static int load_sysv(SysvStub *s) {
if (r 0) {
log_error_unit(s-name,
[%s:%u] Failed to translate LSB dependency %s, ignoring: %s,
- s-path, line, n, strerror(-r));
+ lsb_header_path, line, n, strerror(-r));
continue;
}
@@ -605,7 +614,7 @@ static int load_sysv(SysvStub *s) {
Bug#778653: unblock: procmail/3.22-24
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package procmail. It fixes several heap overflows
and memory corruptions spotted in recent fuzzing attempts (one
has been assigned CVE-2014-9681).
unblock procmail/3.22-24
Cheers,
Moritz
debdiff:
diff -Nru procmail-3.22/debian/changelog procmail-3.22/debian/changelog
--- procmail-3.22/debian/changelog 2014-09-04 12:08:43.0 +0200
+++ procmail-3.22/debian/changelog 2015-02-11 16:44:51.0 +0100
@@ -1,3 +1,23 @@
+procmail (3.22-24) unstable; urgency=medium
+
+ * Fix two memory corruption problems in formail. Closes: #769937.
+Reported by Jakub Wilk. Patch by Jan Darmochwal. Thanks a lot.
+The problems are the following:
+ - Off-by-one heap overflow when parsing addresses that have left angle
+bracket, then a comma, but no right angle bracket: m...@example.com,
+ - Off-by-one heap overflow when parsing addresses that end with
+backslash: m...@example.com\
+
+ -- Santiago Vila sanv...@debian.org Wed, 11 Feb 2015 16:41:40 +0100
+
+procmail (3.22-23) unstable; urgency=medium
+
+ * Fixed heap overflow in procmail that made it to segfault on
+some unusual (but legit) .procmailrc files. Closes: #771958.
+Thanks a lot to Tero Marttila.
+
+ -- Santiago Vila sanv...@debian.org Wed, 03 Dec 2014 23:51:52 +0100
+
procmail (3.22-22) unstable; urgency=high
* Fixed heap overflow in formail that made it to crash on messages
diff -Nru procmail-3.22/debian/patches/28 procmail-3.22/debian/patches/28
--- procmail-3.22/debian/patches/28 1970-01-01 01:00:00.0 +0100
+++ procmail-3.22/debian/patches/28 2014-12-03 23:47:51.0 +0100
@@ -0,0 +1,23 @@
+From: Tero Marttila te...@fixme.fi
+Subject: Fix off-by-one error that makes procmail to segfault on certain
.procmailrc files
+
+--- a/src/cstdio.c
b/src/cstdio.c
+@@ -144,7 +144,7 @@
+ { case '\n':case EOF:*q='\0';
+ return overflow?-1:p!=q; /* did we read anything at all? */
+ }
+- if(q==end) /* check here so that a trailing backslash won't be
lost */
++ if(q=end) /* check here so that a trailing backslash won't be
lost */
+ q=p,overflow=1;
+ *q++=i;
+}
+@@ -199,7 +199,7 @@
+ if(*(target=strchr(target,'\0')-1)=='\\')
+ { if(chp2!=target)/* non-empty line? */
+target++;/* then preserve the backslash */
+-if(targetend-2)/* space enough for getbl? */
++if(target=end-2) /* space enough for getbl? */
+target=end-linebuf,overflow=1; /* toss what we have */
+ continue;
+ }
diff -Nru procmail-3.22/debian/patches/29 procmail-3.22/debian/patches/29
--- procmail-3.22/debian/patches/29 1970-01-01 01:00:00.0 +0100
+++ procmail-3.22/debian/patches/29 2015-02-11 16:19:46.0 +0100
@@ -0,0 +1,25 @@
+From: Jan Darmochwal jdarmoch...@gmx.de
+Subject: formail memory corruption fixes
+
+--- a/src/formail.c
b/src/formail.c
+@@ -219,7 +219,7 @@
+ if(i=0(i!=maxindex(sest)||fldp==rdheader)) /* found
anything? */
+{ char*saddr;char*tmp; /* determine the weight */
+
nowm=areplyheadreply?headreply==1?sest[i].wrepl:sest[i].wrrepl:i;chp+=j;
+- tmp=malloc(j=fldp-Tot_len-j);tmemmove(tmp,chp,j);(chp=tmp)[j-1]='\0';
++ tmp=malloc((j=fldp-Tot_len-j) +
1);tmemmove(tmp,chp,j);(chp=tmp)[j-1]='\0';
+ if(sest[i].head==From_)
+ { char*pastad;
+ if(strchr(saddr=chp,'\n')) /* multiple From_ lines */
+--- a/src/formisc.c
b/src/formisc.c
+@@ -66,7 +66,7 @@
+ retz: *target='\0';
+ ret:return start;
+ }
+- if(*start=='\\')
++ if(*start=='\\' *(start + 1))
+ *target++='\\',start++;
+ hitspc=2;
+ goto normal; /* normal word */
diff -Nru procmail-3.22/debian/patches/series
procmail-3.22/debian/patches/series
--- procmail-3.22/debian/patches/series 2014-09-04 12:00:00.0 +0200
+++ procmail-3.22/debian/patches/series 2015-02-11 16:19:45.0 +0100
@@ -26,3 +26,5 @@
25
26
27
+28
+29
-- System Information:
Debian Release: 8.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
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#778667: xoscope: Please package new upstream version 2.1 for Jessie
Package: xoscope Version: 2.0-3.2 Severity: important Tags: upstream Dear Maintainer, New veriosn 2.1 released 11th Feb adds alsa support. Using the soundcard via aoss or padsp has been broken on 64-bit systems for some time, this would fix #710880 -- System Information: Debian Release: 8.0 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 Init: sysvinit (via /sbin/init) Versions of packages xoscope depends on: ii libatk1.0-0 2.14.0-1 ii libc6 2.19-13 ii libcairo2 1.14.0-2.1 ii libcomedi0 0.10.2-2 ii libfontconfig1 2.11.0-6.3 ii libfreetype62.5.2-2 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-02.42.1-1 ii libgtk2.0-0 2.24.25-1 ii libpango1.0-0 1.36.8-3 xoscope recommends no packages. xoscope 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#778594: git-import-orig fails to merge into packaging branch
On Tue, Feb 17, 2015 at 10:09:16PM +0200, Markus Lehtonen wrote: Hi, On 17/02/15 20:05, Guido Günther a...@sigxcpu.org wrote: retitle 778594 gbp import-orig: allow to ignore changes outside of debian/ severity 778594 wishlist thanks On Tue, Feb 17, 2015 at 11:39:34AM +0100, Martin Pitt wrote: Hello again, Martin Pitt [2015-02-17 9:55 +0100]: Ah indeed, most upstream updates have a Merge tag 'upstream/XXX' into experimental after Imported Upstream version XXX, but 217 doesn't. Probably I already had some trouble with this in 218, as curiously the 218 update has two identically-looking commits 99af89298 and f47781d88. So I suppose something went wrong with importing 217. Mystery resolved. This happens when you git-import-orig a new release, then hack on the branch to port patches, resolve regressions, update packaging etc., and do a git rebase -i origin to clean up your work before pushing. That drops the above Merge tag ... into ... commits, and thus they disappear from the history. Yeah, see the footnote in my initial reply. Since the commit message looked fine I assumed that this was caused by a rebase. Thanks for confirming. Nevertheless a gbp import-orig --force-overwrite that produces the new upstream tree + the debian/ tree as new content of the packaging branch should be added therefore let's move this to wishlist. How about an (additional) mode where no source is present in the packaging branch? That is, only have the content of the debian/ directory. No difficulties with merges and cleaner git history overall. We this kind of support in the still unmerged buildpackage-rpm tool. This mode might have the limitation of requiring a build in a separate build area (with --git-export-dir), or then some clever tricks could be done in the Git work tree to allow build in-place. There were two things I didn't like about the svn workflow for Debian packages. debian/ and upstream source not in one tree (so I can not build with a patched package easily to try fixes) and having to use an export dir (slowing down the build and not giving me a single source tree to grep through). It seems that having the packaging separate brings back these two things some I'm opposed but maybe there are good arguments in favour of just omitting the merge and putting debian/ into the upstream tree? If we create a fake merge commit it's even easy to see where the upstream source came from. Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778633: dh_python3: how to use .pydist file?
On Feb 17 2015, Nikolaus Rath nikol...@rath.org wrote:
On Feb 17 2015, Piotr Ożarowski pi...@debian.org wrote:
[Ben Finney, 2015-02-17]
The question remains, though: where should that fact (and many others
like it) be documented so newcomers don't have to keep asking?
I guess dependencies section in dh.python{2,3} manpage should be more
clear that README.PyDist is about .pydist and pydist-overrides files.
Patches are welcome.
Already done after your first response (#778633) :-).
Here's a revised patch that also documents the format of the
py3dist-overrides file:
diff --git a/dh_python3.rst b/dh_python3.rst
--- a/dh_python3.rst
+++ b/dh_python3.rst
@@ -38,14 +38,38 @@
dependencies
-dh_python3 tries to translate Python dependencies from requires.txt file to
-Debian dependencies. Use debian/py3dist-overrides or --no-guessing-deps option
-to override it if the guess is incorrect. If you want dh_python3 to generate
-more strict dependencies (f.e. to avoid ABI problems) create
-debian/python3-foo.pydist file. See /usr/share/doc/dh-python/README.PyDist
-for more information. If the pydist file contains PEP386 flag or set of (uscan
-like) rules, dh_python3 will make the depedency versioned (version requirements
-are ignored by default).
+
+dh_python3 tries to translate Python dependencies from the
+`requires.txt` file to Debian dependencies. In many cases, this works
+without any additional configuration because dh_python3 comes with a
+build-in mapping of Python module names to Debian packages that is
+periodically regenerated from the Debian archive. By default, the
+version information in the Python dependencies is discarded. If you
+want dh_python3 to generate more strict dependencies (e.g. to avoid
+ABI problems), or if the automatic mapping does not work correctly for
+your package, you have to provide dh_python3 with additional rules for
+the translation of Python module to Debian package dependencies.
+
+For a package *python3-foo* that depends on a package *python3-bar*,
+there are two files that may provide such rules:
+
+#. If the *python3-foo* source package ships with a
+ `debian/py3dist-overrides` file, this file is used by dh_python3
+ during the build of *python3-foo*.
+
+#. If the *python3-bar* source package ships with a
+ `debian/python3-bar.pydist` file (and uses dh_python3), this file
+ will be included in the binary package as
+ `/usr/share/dh-python/dist/cpython3/python3-bar`. During the build
+ of *python3-foo*, dh_python3 will then find and use the file.
+
+Both files have the same format described in
+`/usr/share/doc/dh-python/README.PyDist`. If all you want is to
+generate versioned dependencies (and assuming that the *python3-bar*
+package provides the *pybar* Python module), in most cases it will be
+sufficient to put the line ``pybar python3-bar; PEP386`` into either
+of the above files.
+
private dirs
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
Bug#778374: [php-maint] Bug#778374: [pkg-horde] Bug#778374: php5 5.6.5 fully breaks Horde packages in Debian jessie
On Di 17 Feb 2015 13:37:18 CET, Ondřej Surý wrote: On Tue, Feb 17, 2015, at 10:36, Mike Gabriel wrote: For Debian jessie, I can do this. I don't have a Horde installation on wheezy, but the one I use personally is on jessie and it has to work with latest PHP5 releases / hotfixes. So please, yes, add me to the list for Debian jessie (and probably jessie+1 when it comes to the next freeze). Thanks, I'll keep it mind. JFTR there's 5.6.5-2 in unstable right now with your patch applied. It would be great if you could confirm it really fixes this issue. Looks good here with Horde from jessie and php5 5.6.5-2. :-) Mike (who is happy again!) -- 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 pgpkNi3uDOeIT.pgp Description: Digitale PGP-Signatur
Bug#778620: systemd: Add less to suggests or recommends
Hello Floris, floris [2015-02-17 15:47 +0100]: from man journalctl: The output is paged through less by default, and long lines are truncated to screen width. The hidden part can be viewed by using the left-arrow and right- arrow keys. In particular it's $PAGER, and it defaults to less. But I'm not sure whether we should add a suggests to it -- it rather seems like if you really have a minimal system without any pager, then you probably have a good reason for it. Also, systemd is installed by default, so chances are high that a user would never actually see the suggestion. So I'm inclined to wontfix and/or close this. But this isn't a strong opinion, adding a Suggests: less is fairly harmless after all. Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.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#771701: (pre-approval) unblock: bareos/14.2.1+20141017gitc6c5b56-4
Hi Mehdi, On 02/18/2015 12:20 AM, Mehdi Dogguy wrote: Evgeni, can you please tell how do you plan to fix #771870? TBH, at this stage, the simpler solution as far as Jessie is concerned would be to remove the package from Jessie for now... and work on a backport as soon as Jessie is released. What do you think? well, as far as I can see, #771870 does not affect the version in Jessie. And while -4 contains fixes for two important bugs, those do not prevent Bareos in Jessie from working. From the short discussion on -release@ (548194b0.70...@debian.org, 20141205192725.gk2...@betterave.cristau.org, 548209b0.4090...@debian.org) which did not get CCed to this unblock request, I got the impression the RT does not want any additional fixes. That said, I'd (from a maintainer PoV) would go for -3 in Jessie and fix the remaining bugs in Sid and provide a backport at some point. Greets Evgeni -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778654: FTBFS on various architectures, test-sigbus and test-utf8 failures
Control: tag -1 upstream confirmed Michael Biebl [2015-02-17 23:53 +0100]: The latest upstream versions FTBFS on various architectures due to failures in the test-suite: armhf: FAIL: test-sigbus i386:FAIL: test-sigbus mips:FAIL: test-utf8 powerpc: FAIL: test-utf8, FAIL: test-sigbus s390x: FAIL: test-utf8 test-utf8 looks like a problem on big-endian. I can reproduce it on partch (powerpc porter box), looking into it. The new test-sigbus is a case for Disable-tests-which-fail-on-buildds.patch, I'm afraid. Many buildds run old kernels (like 3.2 or even older) which don't satisfy systemd's requirement (= 3.7). Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.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#778661: RFS: ecere-sdk/0.44.11-1 -- Please sponsor this bug fix release to the Ecere SDK
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for this bug fixes release to my package ecere- sdk. I am hoping this can be included in Debian Jessie (as well as Ubuntu Vivid Vervet) as it solves a segmentation fault on initial launch of the IDE if a configuration file doesn't already exist. * Package name: ecere-sdk Version : 0.44.11-1 Upstream Author : Ecere Corporation jer...@ecere.com * URL : http://ecere.org * License : BSD-3 clauses Section : Development It builds those binary packages: ecere-dev - Ecere SDK Development Tools ecere-extras - Extras for the Ecere SDK ecere-samples - Project samples for the Ecere SDK ecere-sdk - Ecere cross-platform SDK libecc0 - eC Compiler Library libecere0 - Ecere Runtime Library libecereaudio0 - Ecere Audio libecerecom0 - eC Core Runtime Library libeda0 - Ecere Data Access libedasqlite0 - EDA SQLite Driver To access further information about this package, please visit the following URL: http://mentors.debian.net/package/ecere-sdk Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/e/ecere-sdk/ecere -sdk_0.44.11-1.dsc More information about the Ecere SDK can be obtained from http://ecere.org Changes since the last upload: ecere-sdk (0.44.11-1) unstable; urgency=low * Packaged Ecere SDK 0.44.11 (Bug fix release) * Fixed crash on writing initial config file on Linux -- Jerome St-Louis jerstlo...@gmail.com Mon, 16 Feb 2015 19:33:00 -0500 Regards, Jerome St-Louis
Bug#778665: unblock: logol/1.7.0-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-CC: debian-...@lists.debian.org
Please unblock package logol
Logol package is affected by gridengine RC bug and removal request from
Jessie (gridengine is RC buggy and effectively unmaintained , see the
discussion
in #776131).
This patch release removes the dependency on libdrmaa-java waiting for
reintroduction in backports of gridengine. At this time, logol will put
back support and will follow in backports.
There is no other modification.
Debidiff is attached to mail.
diff -Nru logol-1.7.0/debian/changelog logol-1.7.0/debian/changelog
--- logol-1.7.0/debian/changelog2014-05-21 21:26:35.0 +0200
+++ logol-1.7.0/debian/changelog2015-02-05 15:24:35.0 +0100
@@ -1,3 +1,12 @@
+logol (1.7.0-2) unstable; urgency=medium
+
+ * d/control,d/patches/remove_drmaa_support: Remove libdrmaa-java dependency
+due to gridengine removal from Jessie (#776131).
+d/series: remove drmaa patch
+d/README.Debian: explain non drmaa support of this release
+
+ -- Olivier Sallou osal...@debian.org Sun, 01 Feb 2015 08:56:52 +0100
+
logol (1.7.0-1.1) unstable; urgency=high
* Non-maintainer upload.
diff -Nru logol-1.7.0/debian/control logol-1.7.0/debian/control
--- logol-1.7.0/debian/control 2014-04-18 13:38:41.0 +0200
+++ logol-1.7.0/debian/control 2015-02-01 09:00:22.0 +0100
@@ -7,13 +7,14 @@
Vcs-Browser: http://anonscm.debian.org/viewvc/debian-med/trunk/packages/logol/
Build-Depends: debhelper (= 8.0.0),default-jdk (= 1:1.6),ant,ruby,
gawk, swi-prolog (=6.4.1-3),
- libbiojava-java, libdrmaa-java, antlr3, libcommons-cli-java,
+ libbiojava-java, antlr3, libcommons-cli-java,
libcommons-collections3-java, libcommons-configuration-java,
libcommons-lang-java, libcommons-logging-java, libxalan2-java,
libxerces2-java, junit4, libgnumail-java,
liblog4j1.2-java,texlive, texlive-latex-extra, tex4ht,
libncursesw5-dev, ant-optional,
cassiopee, ruby-cassiopee
+#libdrmaa-java removed from Jessie, to be reintroduced.
Standards-Version: 3.9.5
Homepage: http://logol.genouest.org
@@ -21,11 +22,12 @@
Architecture: all
Depends: ${shlibs:Depends}, ${misc:Depends}, default-jre | java7-runtime,
ruby, gawk,
- libbiojava-java, libdrmaa-java, antlr3, libcommons-cli-java,
+ libbiojava-java, antlr3, libcommons-cli-java,
libcommons-collections3-java, libcommons-configuration-java,
libcommons-lang-java, libcommons-logging-java, libxalan2-java,
libxerces2-java, libgnumail-java, liblog4j1.2-java,
cassiopee, logol-bin
+#libdrmaa-java removed from Jessie, to be reintroduced.
Suggests: ruby-cassiopee (=0.1.12)
Description: Pattern matching tool using Logol language
Logol is a pattern matching tool using the Logol language.
diff -Nru logol-1.7.0/debian/patches/remove_drmaa_support
logol-1.7.0/debian/patches/remove_drmaa_support
--- logol-1.7.0/debian/patches/remove_drmaa_support 1970-01-01
01:00:00.0 +0100
+++ logol-1.7.0/debian/patches/remove_drmaa_support 2015-02-01
09:10:24.0 +0100
@@ -0,0 +1,166 @@
+Subject: libdrmaa-java removed from Debian (gridengine)
+Description: DRMAA job submission needs a Java drmaa library.
+ libdrmaa-java has been removed from Debian, bug: 776131.
+ This patch removes DRMAA related code waiting for library
+ reintroduction.
+ Logol will work on local mode only.
+Author: Olivier Sallou osal...@debian.org
+Last-Updated: 2015-02-01
+--- a/src/org/irisa/genouest/logol/dispatcher/Dispatch.java
b/src/org/irisa/genouest/logol/dispatcher/Dispatch.java
+@@ -230,7 +230,6 @@
+options.addOption(h,false,get usage);
+
+options.addOption(s, true, sequence database);
+- options.addOption(sge, false, use SGE);
+options.addOption(local, false, use local system);
+options.addOption(dna, false, analyse dna, is default);
+options.addOption(rna, false, analyse rna);
+@@ -290,7 +289,6 @@
+ usageOptions.addOption(s, true, sequence
database);
+ usageOptions.addOption(g, true, grammar file
to analyse);
+ usageOptions.addOption(m, true, model file
to analyse);
+- usageOptions.addOption(sge, false, use SGE);
+ usageOptions.addOption(local, false, use
local system);
+ usageOptions.addOption(dna, false, analyse
dna, is default);
+ usageOptions.addOption(rna, false, analyse
rna);
+@@ -355,11 +353,6 @@
+ type=LOCAL;
+ jobmngr = (JobManager) new LocalJobManager();
+}
+- if( cmd.hasOption( sge ) ) {
+- logger.info(Using sge system);
+- type=SGE;
+-
Bug#778663: guake: please package guake 0.5.2 for experimental
Package: guake Version: 0.4.4-1 Severity: wishlist Dear Maintainer, Guake has the 0.5.x releases happening for quite a while. 0.5.2 was released around 3 months back . See https://github.com/Guake/guake/releases/tag/0.5.2 and https://github.com/Guake/guake/archive/0.5.2.tar.gz Hoping the new release will make it way either to experimental or unstable for jessie+1. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (600, 'testing'), (500, 'testing-updates'), (1, 'experimental'), (1, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages guake depends on: ii gconf2 3.2.6-3 ii libatk1.0-0 2.14.0-1 ii libc6 2.19-13 ii libcairo2 1.14.0-2.1 ii libfontconfig1 2.11.0-6.3 ii libfreetype62.5.2-2 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-02.42.1-1 ii libgtk2.0-0 2.24.25-1 ii libpango1.0-0 1.36.8-3 ii libpython2.72.7.8-11 ii libx11-62:1.6.2-3 ii mate-notification-daemon [notification-daemon] 1.8.1-2 ii notification-daemon 0.7.6-2 ii plasma-widgets-workspace [notification-daemon] 4:4.11.13-2 ii python 2.7.8-3 ii python-dbus 1.2.0-2+b3 ii python-gconf2.28.1+dfsg-1.1 ii python-glade2 2.24.0-4 ii python-notify 0.1.1-4 ii python-vte 1:0.28.2-5 ii python-xdg 0.25-4 ii xfce4-notifyd [notification-daemon] 0.2.4-3 guake recommends no packages. guake suggests no packages. -- no debconf information -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778664: pam_tty_audit: Cannot make/remove an entry for the specified session
Package: libpam-modules Version: 1.1.8-3.1 Severity: normal Dear Maintainer, I tried to configure the pam_tty_audit module. I edited the /etc/pam.d/common-session file and at the end of it added the following line as per the the pam_tty_audit(8) man page: session required pam_tty_audit.so disable=* enable=root After doing that, I try to gain root access by running 'su -' and I'm presented with an error and the su fails: $ su - Password: su: Cannot make/remove an entry for the specified session $ In the /var/logl/auth.log file are the corresponding errors: Feb 18 13:55:54 dwper-ansible su[41264]: Successful su for root by jimb Feb 18 13:55:54 dwper-ansible su[41264]: + /dev/pts/0 jimb:root Feb 18 13:55:54 dwper-ansible su[41264]: pam_unix(su:session): session opened for user root by jimb(uid=1000) Feb 18 13:55:54 dwper-ansible su[41264]: pam_tty_audit(su:session): error setting current audit status: Invalid argument Feb 18 13:55:54 dwper-ansible su[41264]: pam_open_session: Cannot make/remove an entry for the specified session Removing the line from the /etc/pam.d/common-session file allows the su command to work again. The host is running the Debian testing distribution with all current updates installed. Regards, Jim Barber -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages libpam-modules depends on: ii debconf [debconf-2.0] 1.5.55 ii libaudit1 1:2.4-1+b1 ii libc6 2.19-13 ii libdb5.3 5.3.28-7~deb8u1 ii libpam-modules-bin 1.1.8-3.1 ii libpam0g 1.1.8-3.1 ii libselinux12.3-2 libpam-modules recommends no packages. libpam-modules suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778656: Malformed access ACL
Control: tag -1 unreproducible moreinfo Hey Michael, I tried to reproduce this in various ways. I created a persistant journal under 215-12, rebooted, upgraded to 219-1, dpkg-reconfigured, apt-get install --reinstall'ed, etc., but I can't get this to happen. Michael Biebl [2015-02-18 0:40 +0100]: # dpkg-reconfigure systemd setfacl: /var/log/journal/567a68a5c2672114bcf5192d0008: Malformed access ACL I'm quite sure this comes from our postinst: | if [ -d /var/log/journal ]; then | # Grant read access to /var/log/journal for members of the adm group | # via a filesystem ACL. This makes them able to read the journal. | # Failure is ignored since there might be file systems mounted without | # ACL support. | setfacl -R -nm g:adm:rx,d:g:adm:rx /var/log/journal || true | fi Can you confirm this? I. e. do you still get this error if you reconfigure/reinstall again? Does dropping this postinst snippet fix it? We can drop it now, as tmpfiles.d/systemd.conf now automatically adds an adm ACL to /var/log/journal and /run/log/journal/. I just updated README.Debian in git accordingly. But I'd like you to confirm that this indeed fixes the clutter, or whether that's coming from systemd-tmpfiles itself. getfacl: Removing leading '/' from absolute path names # file: var/log/journal/567a68a5c2672114bcf5192d0008/system.journal # owner: root # group: systemd-journal user::rw- group::r-x group:adm:r-x group:adm:r-x ^ That's the bit that I can't reproduce. If I call setfacl, or let tmpfiles.d do its thing, I never get this duplicate ACL. Do you still remember how you managed to get this? Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#778666: gnome-themes-extras: recommends package missing in the archive (gnome-themes-more)
Package: gnome-themes-extras Version: 2.22.0-3 Severity: minor Dear Maintainer, As gnome-themes-extras was installed on jessie, I noticed that gnome-themes- extras recommends package that is not present in the archive (gnome-themes- more). The same is for wheezy. Gnome-themes-more exists only for squeeze. Maybe it would be useful to remove it from recommendations, if it's not supported anymore. -- System Information: Debian Release: 7.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.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 Versions of packages gnome-themes-extras depends on: ii gtk2-engines 1:2.20.2-2 ii librsvg2-common 2.36.1-2 Versions of packages gnome-themes-extras recommends: pn gnome-themes-more none gnome-themes-extras 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#778623: rancid: RANCID 3.0 changes router.db delimiter in an incompatible way
Package: rancid Version: 3.1-1 Severity: important Hi, RANCID 3.0 (incorporated in current experimental's 3.1) introduces the following backward incompatible change | router.db,rancid.types.*: change field separator to ';' (semi-colon) to | allow for IPv6 addresses in router.db and avoid conflict with :s in | device commands and perl module names If you don't know that and do not change router.db after the upgrade it will - output weird error messages about hosts being added and removed - remove all configuration already collected (not fatal since it is in VCS, but still) - fail to collect without any usable error message Please either switch router.db in postinst or at least add NEWS.Debian for that change. Best Regards, Bernhard -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778629: golang-goprotobuf: Please upgrade to a more recent commit
Source: golang-goprotobuf Severity: wishlist Hi, This version of goprotobuf is based on a git snapshot from 2013. It has been a lot of activity in the repo, although sadly upstream does not seem to be interested in making releases. Could you consider updating this? It seems that newer versions output nicer code. Thanks. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing'), (100, 'unstable'), (50, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.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#778630: ucspi-unix: unixserver says options -d and -D are invalid
Package: ucspi-unix Version: 0.36-4 Severity: normal Dear Maintainer, $ unixserver -d unixserver: invalid option -- 'd' $ unixserver -D unixserver: invalid option -- 'D' usage: unixserver [options] socket program [..] -d Do not delete the socket file on exit. -D (default) Delete the socket file on exit. Richard. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') 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: sysvinit (via /sbin/init) Versions of packages ucspi-unix depends on: ii libc6 2.19-13 ucspi-unix recommends no packages. ucspi-unix 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#778366: unblock: kfreebsd-10/10.1~svn274115-2
Control: tag -1 confirmed Hi, Steven Chamberlain ste...@pyro.eu.org (2015-02-14): Michael Gilbert wrote: Please consider unblocking kfreebsd-10. It fixes 2 security issues: https://security-tracker.debian.org/kfreebsd-10 When I saw this request come in, I meant to ask one of the maintainers to confirm they were happy with getting this into testing… A debdiff is attached. The other change is to limit the arch-dep packages to kfreebsd-any (which was forgotten in the previous upload). … which seems to be the case, so no objections from a d-i point of view. Mraw, KiBi. signature.asc Description: Digital signature
Bug#778610: fourier.sty is incompatible with fontspec.sty under xelatex (Command `\hbar' already defined)
Package: texlive-fonts-extra
Version: 2014.20141024-1
Under xelatex,
\usepackage{fontspec}
\usepackage{fourier}
fails while reading fourier.sty with
! LaTeX Error: Command `\hbar' already defined.
whereas the inverse inclusion order works.
smime.p7s
Description: S/MIME Cryptographic Signature
Bug#778546: RFS: miceamaze/4.2-1 -- video game with mice in a maze
Hello,
Thank you for answering and reviewing the package so fast.
I have (I hope) adressed the blocking issue and some of
your recommendations also.
The new files are there: http://www.miceamaze.org/debian/
See below for my answers:
2015-02-17 6:12 GMT+01:00 Paul Wise p...@debian.org:
Control: tags -1 + moreinfo
On Mon, Feb 16, 2015 at 10:38 PM, Raphaël Champeimont wrote:
miceamaze - video game with mice in a maze
There is one issue that need to be fixed before I will upload the package:
The debian/copyright file needs to be updated for the new copyright
year. It also needs updating for the new files that are under
different licenses or have different copyright holders (data/music/
and data/mazes/maze13.txt). Please note that a full copy of the CC-BY
3.0 license needs to be added to debian/copyright, so offline users
can read the license.
She agrees to release the maze to the public domain.
I also release the ones I have made to the public domain,
so I have added an entry to say all mazes are in the public domain.
OK I added entries for the music files with CC-BY.
Other thoughts:
On a system with two screens (laptop + external screen), full-screen
mode crosses the two screens which makes the menu hard to read and
cuts part of it off.
I'm not sure I can fix this, because all I do is ask for SDL to setup a
full-screen OpenGL display, but don't think it is possible to specify
the behavior on multi-screen.
In chromium-bsu I was able to get nice anti-aliased text by passing
GLC_TEXTURE to glcRenderStyle, but for some reason that only produces
white squares in miceamaze.
Perhaps it is because I use display lists in which I put some text
rendering,
and it may not work well with the texture-based rendering (just a guess).
You might want to mention the Standards-Version in debian/changelog.
If you have gone through the upgrading checklist and there aren't any
changes that apply to miceamaze, you can say just Bump
Standards-Version, no changes needed.
http://www.debian.org/doc/debian-policy/upgrading-checklist
Yes. Actually I had checked this list and noticed nothing applied for
miceamaze.
I have added the changelog entry.
You might want to mention the reason for the Priority change in
debian/changelog.
Did I do that? The only thing I changed is experimental instead of
unstable.
Is it what you are talking about?
I would have indented the second debian/changelog item like this:
* New upstram release 4.2 (Closes: #766820)
- Removed creation timestamp in PNG generation (Closes: #778491)
ok fixed
ttf-dejavu-core is a transitional dummy package, you could depend on
fonts-dejavu-core | ttf-dejavu-core instead.
fixed
You may want to work on porting the code to SDL2. chromium-bsu is an
example of a game that supports SDL and SDL2 (in upstream git only).
Last time I checked, SDL2 was not shipped with most linux distributions
(in stable releases) so I wanted to wait. Hopefully with jessie release,
SDL2
will be available, so I might do the swith eventually (I think I will
permanently
switch and drop SDL 1.2 compatibility completely when I do that).
The debian/patches directory is empty and could be removed.
ok
There are two spelling errors:
$ codespell --quiet-level=3
./src/Functions.h:149: occured == occurred
./src/AIVertex.h:33: colum == column
thanks. corrected
The include-what-you-use tool (from the iwyu Debian package) suggests
a lot of files that are missing headers for the variables and
functions that they use. I ran this command:
$ find -type f \( -iname '*.c' -o -iname '*.cc' -o -iname '*.cxx' -o
-iname '*.cpp' -o -iname '*.h' -o -iname '*.hh' -o -iname '*.hxx' -o
-iname '*.hpp' \) -exec include-what-you-use {} \;
I'm surprised because gcc never complained about missing includes.
I will look into that later (this is not fixed in this release).
I would suggest renaming the upstream README.txt file to INSTALL.txt.
ok done
The upstream LICENSE.txt still contains details about the
Bitstream/DejaVu license even though that was removed from the source
tarball.
True. I removed this part.
The upstream LICENSE.txt is missing copyright/license info for
maze13.txt, which appears to have been contributed by someone else?
Ok I added information about that.
This is a better URL for the Ogg file from ccmixter, I found it in the
metadata of the Ogg file:
http://ccmixter.org/files/George_Ellinas/14073-
Thanks. I added the URL.
The upstream ChangeLog.txt is missing information about versions from
2.1 to 4.2.
Yes I tend to forget about this file and only update the website.
But this is now fixed.
You've changed the mouse image and introduced 2 modified copies of it.
This could be problematic if you want to tweak the mouse image or use
different modifications in the future. Personally I would have done it
like this: mouse.png containing the normal mouse image, helmet.png
Bug#716237: [PATCH] rt-migrate-test: exit early if nr_runs is non-positive
Sorry, PROGRESS_CHARS macro is used correctly, but INTERVAL and
RUN_INTERVAL not. In my opinion, they should be defined and used once in
static variable assigning, and nowhere else.
On 02/17/2015 08:30 PM, Boris Egorov wrote:
Looks like this patch is not applied yet.
I can move value check to parse_options and send another version of
patch. As for macros - yes, I already mentioned them in debian bug
report thread. There are three of them (INTERVAL, RUN_INTERVAL,
PROGRESS_CHARS) which are improperly (IMO) used instead of corresponding
lowercase variables. I thought these changes should go to another patch.
On 02/17/2015 08:08 PM, Sebastian Andrzej Siewior wrote:
* Boris Egorov | 2014-11-27 16:20:34 [+0600]:
Program will crash if nr_runs is 0 due to dividing by it in
print_results(). Let's exit early instead.
Fixes: http://bugs.debian.org/716237
Has this been dealt with? I can't see this applied. I would prefer
doing the value check in parse_options() itself. And looking at it, it
seems that run_interval is interval ignored. Or is there macro magic
invovled?
Signed-off-by: Boris Egorov ego...@linux.com
---
src/rt-migrate-test/rt-migrate-test.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/src/rt-migrate-test/rt-migrate-test.c
b/src/rt-migrate-test/rt-migrate-test.c
index e3c7a09..876a122 100644
--- a/src/rt-migrate-test/rt-migrate-test.c
+++ b/src/rt-migrate-test/rt-migrate-test.c
@@ -465,6 +465,11 @@ int main (int argc, char **argv)
parse_options(argc, argv);
+ if (nr_runs = 0) {
+ fprintf(stderr, Warning, --loops argument is non-positive.
Exiting.\n);
+ exit(-1);
+ }
+
signal(SIGINT, stop_log);
if (argc = (optind + 1))
--
2.1.3
Sebastian
--
Best regards,
Boris Egorov
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778600: torus-trooper-pure: Requires version of torus-trooper-data older than current
Control: tags -1 moreinfo On Tue, 17. Feb 11:15 eingousef eingou...@gmail.com wrote: Package: torus-trooper-pure Version: 0.22.dfsg1-8 Severity: important Dear Maintainer, torus-trooper-pure 0.22.dfsg1-8 (current) needs torus-trooper-data 0.22.dfsg1-8 to be installed, but the current version of torus-trooper-data in testing is 0.22.dfsg1-9. Hello, torus-trooper-pure is has been removed from Debian. There is no version for amd64 in testing. I presume you still use an old package from wheezy. What does apt-cache policy torus-trooper-pure report? Regards, Markus signature.asc Description: Digital signature
Bug#778617: grub-install often breaks in UEFI mode
Package: grub-installer
Version: 1.110
I'm forwarding this patch from Ubuntu:
https://launchpad.net/bugs/1303790
On EFI, the boot disk argument given to grub-install is a dummy and is
often the wrong disk or a non existent disk. Grub is still installed to
the correct place since it goes through the filesystem to /boot/EFI, but
the function make_active_partition tries to look at the partition table
on the dummy disk and throws an error. Hence, I wrote the attached
patch to disable the function on EFI.
revno: 121
committer: Phillip Susi ps...@ubuntu.com
branch nick: grub-installer
timestamp: Tue 2015-02-17 09:15:44 -0500
message:
Don't try to mark a partition as active, except on grub-pc.
This was causing failures for grub-efi (LP: #1303790).
diff:
=== modified file 'debian/changelog'
--- debian/changelog2014-10-06 18:29:15 +
+++ debian/changelog2015-02-17 14:15:44 +
@@ -1,3 +1,10 @@
+grub-installer (1.78ubuntu24) vivid; urgency=medium
+
+ * Don't try to mark a partition as active, except on grub-pc.
+This was causing failures for grub-efi (LP: #1303790).
+
+ -- Phillip Susi ps...@ubuntu.com Tue, 27 Jan 2015 15:51:09 -0500
+
grub-installer (1.78ubuntu23) utopic; urgency=medium
* On ppc64el, wipe the PReP partition before installing grub-ieee1275,
=== modified file 'grub-installer'
--- grub-installer 2014-10-06 18:29:15 +
+++ grub-installer 2015-02-17 14:15:44 +
@@ -1006,6 +1006,12 @@
}
make_active_partition () {
+ if [ $grub_package != grub-pc ]; then
+ # only do this for grub-pc since on EFI $bootdev is a dummy argument
+ # and looking for a partition table on the wrong or non existing disk
+ # crashes the installer LP:#1303790
+ return
+ fi
bootdisk=
bootpart=
case $bootdev in
signature.asc
Description: OpenPGP digital signature
Bug#578663: libapache2-mod-gnutls: GnuTLSClientVerify require is ignored.
Package: libapache2-mod-gnutls
Version: 0.5.10-1.1
Followup-For: Bug #578663
This bug still exists in current stable and unstable packages. I have
analyzed the problem and found that the authentication hook
(mgs_hook_authz) failed to consider the server's client verify mode,
even if the verify mode was unset in the directory configuration. As a
result, invalid certificates were ignored and clients could connect and
receive data as long as they presented any certificate whatsoever. The
logs show that the certificate was recognized as invalid, but the
request is still served.
[debug] gnutls_hooks.c(1181): [client 127.0.0.1] GnuTLS: A Chain of 1
certificate(s) was provided for validation
[debug] gnutls_hooks.c(1236): [client 127.0.0.1] GnuTLS: Verifying list
of 1 certificate(s)
[info] [client 127.0.0.1] GnuTLS: Could not find Signer for Peer Certificate
[info] [client 127.0.0.1] GnuTLS: Peer Certificate is invalid.
The attached patch applies to the version in stable, commit
5a8a32bbfb8a83fe6358c5c31c443325a7775fc2 in my git repository [1] should
work for the unstable version. Functionally, they are identical, but
apparently indentation changed between the two versions.
Since this bug makes required TLS client auth effectively worthless, I
consider it a security issue.
[1]
https://github.com/airtower-luna/mod_gnutls/commit/5a8a32bbfb8a83fe6358c5c31c443325a7775fc2
-- System Information:
Debian Release: 7.8
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libapache2-mod-gnutls depends on:
ii libapr-memcache0 0.7.0-1
ii libc6 2.13-38+deb7u7
ii libgnutls26 2.12.20-8+deb7u2
libapache2-mod-gnutls recommends no packages.
libapache2-mod-gnutls suggests no packages.
-- Configuration Files:
/etc/apache2/sites-available/default-tls changed [not included]
-- no debconf information
From 5a8a32bbfb8a83fe6358c5c31c443325a7775fc2 Mon Sep 17 00:00:00 2001
From: Thomas Klute thomas2.kl...@uni-dortmund.de
Date: Thu, 5 Feb 2015 14:48:45 +0100
Subject: [PATCH] TLS Client auth: Check server verify mode if unset for dir
The authentication hook (mgs_hook_authz) failed to consider the server's
client verify mode, even if the verify mode was unset in the directory
configuration. As a result, invalid certificates were ignored and
clients could connect and receive data as long as they presented any
certificate whatsoever. Logs showed that authorization was granted
despite the certificate being invalid (timestamps removed for
readability):
[:debug] [pid 10806:tid 140242057148160] gnutls_hooks.c(1198): [client ::1:40992] GnuTLS: Verifying list of 1 certificate(s) via method 'cartel'
[:info] [pid 10806:tid 140242057148160] [client ::1:40992] GnuTLS: Could not find Signer for Peer Certificate
[:info] [pid 10806:tid 140242057148160] [client ::1:40992] GnuTLS: Peer Certificate is invalid.
[authz_core:debug] [pid 10806:tid 140242057148160] mod_authz_core.c(835): [client ::1:40992] AH01628: authorization result: granted (no directives)
This commit adds a check for undefined verify mode in the directory
configuration and applies the server wide configuration in that case.
---
src/gnutls_hooks.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
Index: mod-gnutls-0.5.10/src/gnutls_hooks.c
===
--- mod-gnutls-0.5.10.orig/src/gnutls_hooks.c 2011-07-08 23:29:46.0 +0200
+++ mod-gnutls-0.5.10/src/gnutls_hooks.c 2015-02-17 15:37:15.173845398 +0100
@@ -909,9 +909,12 @@
return DECLINED;
}
rv = mgs_cert_verify(r, ctxt);
- if (rv != DECLINED
- (rv != HTTP_FORBIDDEN ||
- dc-client_verify_mode == GNUTLS_CERT_REQUIRE)) {
+ if (rv != DECLINED
+ (rv != HTTP_FORBIDDEN
+ || dc-client_verify_mode == GNUTLS_CERT_REQUIRE
+ || (dc-client_verify_mode == -1
+ ctxt-sc-client_verify_mode == GNUTLS_CERT_REQUIRE)))
+ {
return rv;
}
}
Bug#778622: wheezy-pu: package vigor/0.016-19+deb7u1
Package: release.debian.org Severity: normal Tags: wheezy User: release.debian@packages.debian.org Usertags: pu I'd like to upload the following patch to stable-proposed-updates to fix #778409, which the security team doesn't think warrants a DSA (and honestly I'd have to agree). Would this be OK? It matches 0.016-24 in unstable. diff --git a/debian/changelog b/debian/changelog index 6cf06c7..0d2ae40 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +vigor (0.016-19+deb7u1) stable; urgency=medium + + * Use libc's regex routines rather than the bundled ones, to avoid needing +to apply security patches independently (closes: #778409). + + -- Colin Watson cjwat...@debian.org Sat, 14 Feb 2015 22:06:36 + + vigor (0.016-19) unstable; urgency=low * Drop manual and not-very-useful 'debian/rules configure' target. diff --git a/debian/rules b/debian/rules index 28c3dda..eb30d7f 100755 --- a/debian/rules +++ b/debian/rules @@ -6,7 +6,7 @@ export DEB_CPPFLAGS_MAINT_APPEND := -I/usr/include/tcl8.5 dh $@ --sourcedirectory=build override_dh_auto_configure: - dh_auto_configure -- --with-x --enable-db --enable-re + dh_auto_configure -- --with-x --enable-db override_dh_clean: # This is in the upstream tarball, so shouldn't be removed. Thanks, -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778626: broadcom-sta-dkms: Module build ... was skipped
Package: broadcom-sta-dkms Version: 6.30.223.248-3 Severity: serious Justification: fails to build from source Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Updating my system removed several packets (not your department) and disabled my wlan (that should be yours). Reinstalling the driver didn't work. * What exactly did you do (or not do) that was effective (or ineffective)? Installing broadcom-sta-dkms * What was the outcome of this action? # aptitude install broadcom-sta-dkms Die folgenden NEUEN Pakete werden zusätzlich installiert: broadcom-sta-dkms 0 Pakete aktualisiert, 1 zusätzlich installiert, 0 werden entfernt und 0 nicht aktualisiert. 0 B/2.170 kB an Archiven müssen heruntergeladen werden. Nach dem Entpacken werden 14,4 MB zusätzlich belegt sein. Vormals nicht ausgewähltes Paket broadcom-sta-dkms wird gewählt. (Lese Datenbank ... 373155 Dateien und Verzeichnisse sind derzeit installiert.) Vorbereitung zum Entpacken von .../broadcom-sta-dkms_6.30.223.248-3_all.deb ... Entpacken von broadcom-sta-dkms (6.30.223.248-3) ... broadcom-sta-dkms (6.30.223.248-3) wird eingerichtet ... Loading new broadcom-sta-6.30.223.248 DKMS files... First Installation: checking all kernels... Building only for 3.16.0-4-amd64 Module build for the currently running kernel was skipped since the kernel source for this kernel does not seem to be installed. --- My running kernelversion is: # uname -a Linux debian 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt4-3 (2015-02-03) x86_64 GNU/Linux Some installed packages and their versions: # dpkg -l|grep linux-image ii linux-image-3.16.0-4-amd643.16.7-ckt4-3 amd64Linux 3.16 for 64-bit PCs ii linux-image-amd64 3.16+63 amd64Linux for 64-bit PCs (meta-package) # dpkg -l|grep linux-headers ii linux-headers-3.16.0-4-amd64 3.16.7-ckt4-3 amd64Header files for Linux 3.16.0-4-amd64 ii linux-headers-3.16.0-4-common 3.16.7-ckt4-3 amd64Common header files for Linux 3.16.0-4 ii linux-headers-amd64 3.16+63 amd64Header files for Linux amd64 configuration (meta-package) # dpkg -l|grep linux-source ii linux-source 3.16+63 all Linux kernel source (meta-package) ii linux-source-3.16 3.16.7-ckt4-3 all Linux kernel source for version 3.16 with Debian patches # dpkg -l|grep dkms ii broadcom-sta-dkms 6.30.223.248-3 all dkms source for the Broadcom STA Wireless driver ii dkms 2.2.0.3-2 all Dynamic Kernel Module Support Framework # dpkg -l|grep build-ess ii build-essential 11.7 amd64Informational list of build-essential packages # dpkg -l|grep kbuild ii linux-kbuild-3.16 3.16-3 amd64Kbuild infrastructure for Linux 3.16 # dpkg -l|grep wireless-t ii wireless-tools30~pre9-8 amd64Tools for manipulating Linux Wireless Extensions The source package was lying in /usr/src/ as a tar.xz. I unxz-ed and untar-ed it, but that didn't help neither. * What outcome did you expect instead? Compiling of the modules -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages broadcom-sta-dkms depends on: ii dkms 2.2.0.3-2 Versions of packages broadcom-sta-dkms recommends: ii wireless-tools 30~pre9-8 broadcom-sta-dkms 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#777196: activemq: CVE-2014-8110 CVE-2014-3612 CVE-2014-3600
On Fri, Feb 06, 2015 at 01:56:35PM +0100, Emmanuel Bourg wrote: For CVE-2014-3600: https://github.com/apache/activemq/commit/b9696ac8 https://issues.apache.org/jira/browse/AMQ-5333 Could you please upload a fixed package for CVE-2014-3612 and CVE-2014-3600? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774135: mc: segfault for SFTP VFS
tags 774135 - unreproducible thanks It works fine on my sid amd64 config. After further analysis, I can reconfirm this bug exists in Debian/x32 sid, but not in Debian/i386 sid or Debian/amd64 sid. I’ll track this down further. bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778627: live-build: syslinux mbr.bin file not found (again)
Package: live-build
Version: 4.0.5-1
Severity: normal
Hello,
it seems mbr.bin has moved to a subdirectory which causes hdd build
failure in Jessie.
Attaching a patch.
I applied some reformatting to better conform to the coding style so
hope it still works.
Thanks
Michal
-- Package-specific info:
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (910, 'testing'), (900, 'stable'), (410, 'unstable'), (400,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.18.0-trunk-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/bash
Init: systemd (via /run/systemd/system)
Versions of packages live-build depends on:
ii debootstrap 1.0.66
Versions of packages live-build recommends:
ii cpio2.11+dfsg-4
ii live-boot-doc 4.0.1-1
ii live-config-doc 4.0.2-1
pn live-manual-html | live-manual none
live-build suggests no packages.
-- no debconf information
commit 5720a9d88db781251145c41ce3ce39b8b6763ee7
Author: Michal Suchanek hramr...@gmail.com
Date: Tue Feb 17 13:01:40 2015 +0100
Fixing binary hdd build.
Signed-off-by: Michal Suchanek hramr...@gmail.com
diff --git a/scripts/build/binary_hdd b/scripts/build/binary_hdd
index 90cd3e9..f290bf2 100755
--- a/scripts/build/binary_hdd
+++ b/scripts/build/binary_hdd
@@ -182,6 +182,18 @@ case ${LB_BINARY_FILESYSTEM} in
;;
esac
+Find_mbrbin() {
+ for _MBR in chroot/usr/lib/${_BOOTLOADER}/mbr/mbr.bin chroot/usr/lib/${_BOOTLOADER}/mbr.bin ; do
+ if [ -f ${_MBR} ]
+ then
+ echo ${_MBR}
+ return 0
+ fi
+ done
+ Echo_error Cannot find mbr.bin. 2
+ exit 1
+}
+
case ${LB_BUILD_WITH_CHROOT} in
true)
Chroot chroot parted -s ${FREELO} mklabel ${PARTITION_TABLE_TYPE} || true
@@ -191,7 +203,7 @@ case ${LB_BUILD_WITH_CHROOT} in
if [ ${LB_BOOTLOADER} = syslinux ]
then
- dd if=chroot/usr/lib/${_BOOTLOADER}/mbr.bin of=${FREELO} bs=440 count=1
+ dd if=$(Find_mbrbin) of=${FREELO} bs=440 count=1
fi
;;
@@ -203,7 +215,7 @@ case ${LB_BUILD_WITH_CHROOT} in
if [ ${LB_BOOTLOADER} = syslinux ]
then
- dd if=/usr/lib/${_BOOTLOADER}/mbr.bin of=${FREELO} bs=440 count=1
+ dd if=$(Find_mbrbin) of=${FREELO} bs=440 count=1
fi
;;
esac
Bug#777579: krb5-admin-server: kadmind reports Insufficient access to lock database
control: tags -1 moreinfo I took the following steps: 1) create a new sid chroot. 2) apt-get update 3) apt-get install krb5-user As part of 3 krb5-config got installed and because of my DNS I was prompted to configure my krb5.conf. I entered the realm I was going to create (EXAMPLE.COM) but specified no kerberos or admin servers when prompted. 4) apt-get install krb5-admin-server 5) krb5_newrealm I then looked and confirmed that the database was in /var/lib/krb5kdc so, at least for me, the software works as intended. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778571: sbuild: predictible build location for reproducible builds
On 2015-02-17, Benjamin Drung wrote: Am Montag, den 16.02.2015, 12:37 -0800 schrieb Vagrant Cascadian: This patch is really only a small step forward, making the build dir consistent only when building with sbuild. Ideally, the build dir should be set to /usr/src/debian/PACKAGE-VERSION (or some other widely agreed upon dir) so that builds would be reproducible if built with other tools such as pbuilder using the same build dir. Why not going directly to use /usr/src/debian/PACKAGE-VERSION or is there anything speaking against this path? Only requires someone to write a better patch; it needs a more complete patch, as /build is hardcoded in several places. live well, vagrant signature.asc Description: PGP signature
Bug#511441: 511441 Error message when sqlite is not available could be more detailed
On Sat, 13 Jun 2009 15:24:05 +0100 Dominic Hargreaves d...@earth.li wrote:
reassign 511441 dbconfig-common
severity 511441 minor
retitle 511441 Error message when sqlite is not available could be more
detailed
Having reviewed your bug, the error message dbconfig-common produces
behalf of movabletype-opensource does say specifically that you should
install the sqlite package.
It's possible that the message could explain in more detail why this is
needed, so I am lowering the severity of this bug and moving it to the
dbconfig-common package.
Do you have a proposal? The current message is (with $1 is the client
name depending on the database type):
dbc_error=No $1 client to execute. (have you installed the
${dbc_dbclientpackage:-$1} package?)
I don't think this error message should be much longer, but I am open to
improvements. I assume you have something like the following in mind?
dbc_error=No $1 client to execute the maintainer scripts for the
requested database type. (have you installed the
${dbc_dbclientpackage:-$1} package?)
By the way, it seems that the original bug was really about missing
dependencies in movabletype-opensource of that version. But later
versions had it correct and it is now removed anyways.
Paul
signature.asc
Description: OpenPGP digital signature
Bug#778368: unblock: ltsp/5.5.4-3
Adam D. Barratt a...@adam-barratt.org.uk (2015-02-14): Control: tags -1 + confirmed d-i On Fri, 2015-02-13 at 21:41 -0800, Vagrant Cascadian wrote: ltsp 5.5.4-3 fixes an RC bug in ltsp removing obsolete config files from pre-wheezy versions of ltsp. It also removes an ugly, hackish workaround no longer required due to fixing an RC bug in LDM. Unblocked, thanks. No objections. It does ship a .udeb, but there are no changes to anything that would impact the .udeb, and the .udeb isn't used in debian-installer by default. It still needs an ack, I'm afraid. I'm wondering whether it should move away from the block-udeb list. Letting ltsp people do their stuff on their own looks like a good idea (until/unless some tighter integration into d-i happens, which isn't a current topic as far as I'm aware of). Mraw, KiBi. signature.asc Description: Digital signature
Bug#778351: unblock: isc-dhcp/4.3.1-6
Adam D. Barratt a...@adam-barratt.org.uk (2015-02-14): Control: tags -1 + confirmed d-i Do I double-confirm it then? ;) On Fri, 2015-02-13 at 16:54 -0500, Michael Gilbert wrote: Please consider unblocking isc-dhcp. It fixes a regression in init script error handling (bug #755834, unfortunate bug # typo in the changelog). Done. There are no changes to the udebs. Nevertheless, it still needs an ack. No objections, thanks. Mraw, KiBi. signature.asc Description: Digital signature
Bug#778577: CVE-2015-1606 CVE-2015-1607 -- multiple issues found in GnuPG
On Tue 2015-02-17 00:27:20 -0500, Salvatore Bonaccorso wrote: Control: fixed -1 2.1.2-1 Hi Daniel, On Mon, Feb 16, 2015 at 06:09:18PM -0500, Daniel Kahn Gillmor wrote: Several coding errors were discovered in GnuPG 2.0 lately by Hanno Böck as part of the Fuzzing Project: Have you checked if gnupg 1.4.x is also affected by both of these CVEs? We have marked gnupg as undetermined so far in the security-tracker. Yes, gpg 1.4.x is also affected. In particular, CVE-2015-1606 is known to affect it. The demonstration vector we have for CVE-2015-1607 is a keybox file, which is not supported by gpg 1.4.x, but the underlying fix (normalizing bitshift operations) seems like it should apply to 1.4.x as well. I'm not sure how to represent this in the BTS; should i clone this and reassign it to the gnupg package, or is there a way to make this bug report apply to both gnupg and gnupg2? I'm working today on getting patches for both the 2.0.x and 1.4.x branches. --dkg signature.asc Description: PGP signature
Bug#778624: qemu-user-static: add binfmt for mips64 and mips64el
Package: qemu-user-static Version: 1:2.1+dfsg-11 Severity: wishlist Hi, Since qemu ships with qemu-mips64el-static, it would be good if there was a binfmt setup so I could run mips64el executables on my amd64 machine. Copying the mipsel binfmt and replacing the start with \x7fELF\x02 seems to work. I would have thought that doing the same with mips and mips64 should also work. Start of a mips64el executable I have: 7f 45 4c 46 02 01 01 00 00 00 00 00 00 00 00 00 |.ELF| 0010 02 00 08 00 01 00 00 00 00 1c 00 20 01 00 00 00 |... | 0020 40 00 00 00 00 00 00 00 f8 7d 00 00 00 00 00 00 |@}..| 0030 07 00 00 60 40 00 38 00 0a 00 40 00 1e 00 1d 00 |...`@.8...@.| Thanks, James -- 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=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) qemu-user-static depends on no packages. Versions of packages qemu-user-static recommends: ii binfmt-support 2.1.5-1 Versions of packages qemu-user-static suggests: ii sudo 1.8.11p2-1.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#778527: ITP: libfile-mktemp-perl -- Make temporary filename from template
Raoul Gunnar Borenius dijo [Mon, Feb 16, 2015 at 11:30:24AM +0100]: File::MkTemp and File::MkTempO provides functions to create unique strings for use as file/directory names based on an user specified template. The package would be very useful for Nagios/Icinga-Installations using the optional Kerberos-Check-Plugin from http://exchange.nagios.org/directory/Plugins/Security/check_krb5/details This plugin is implemented in Perl and needs File::MkTemp which is not in Debian yet. Umh, what does it provide beyond what File::Temp (which is in the standard library) already does? $ perl -e 'use File::Temp; $f=File::Temp-new(TEMPLATE=FooBar, DIR=/tmp, SUFFIX=.foo); print $f-filename,\n;' /tmp/FooBarM1Xo.foo File::Temp not only creates unique strings, but also automatically handles the file or directory creation and remotion. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#716237: [PATCH] rt-migrate-test: exit early if nr_runs is non-positive
On Tue, 17 Feb 2015 09:40:11 -0600 Clark Williams
clark.willi...@gmail.com wrote:
On Tue, 17 Feb 2015 15:08:38 +0100 Sebastian Andrzej Siewior
bige...@linutronix.de wrote:
* Boris Egorov | 2014-11-27 16:20:34 [+0600]:
Program will crash if nr_runs is 0 due to dividing by it in
print_results(). Let's exit early instead.
Fixes: http://bugs.debian.org/716237
Has this been dealt with? I can't see this applied. I would prefer
doing the value check in parse_options() itself. And looking at it, it
seems that run_interval is interval ignored. Or is there macro magic
invovled?
It looks to me like interval is being ignored in favor of INTERVAL,
which is a macro defined as:
#define INTERVAL ms2nano(100ULL)
I think the fix is to change the lines that initialize intv in main()
to use interval rather than INTERVAL.
Clark
What do you guys think of this patch (moved the check to the bottom of
parse_options()):
diff --git a/src/rt-migrate-test/rt-migrate-test.c
b/src/rt-migrate-test/rt-migrate-test.c index
e3c7a0991ac5..3e4e19e1aec9 100644 ---
a/src/rt-migrate-test/rt-migrate-test.c +++
b/src/rt-migrate-test/rt-migrate-test.c @@ -227,6 +227,16 @@ static
void parse_options (int argc, char *argv[]) }
}
+ /* sanity check the options */
+ if (nr_runs = 0) {
+ fprintf(stderr, Error: --loops argument is non-positive.
Exiting.\n);
+ exit(-1);
+ }
+
+ if (prio_start 1 || prio_start 99) {
+ fprintf(stderr, Error: invalid value for --prio option: %d
(valid: 1-99)\n, prio_start);
+ exit(-1);
+ }
}
static unsigned long long get_time(void)
pgpo4dS03oxTF.pgp
Description: OpenPGP digital signature
Bug#743014: unwanted space in gnuplot tab autocomplete
I have exactly the same problem and, so far, was unable to find a solution. I would add that this bug is extremely annoying. Additional information G N U P L O T Version 4.6 patchlevel 4last modified 2013-10-02 Build System: Linux x86_64 Ubuntu 14.04 x86_64, kernel 3.17.0-031700 Best, Guido Avvisati On Sat, 29 Mar 2014 19:35:22 -0500 N Laszlo Frazer las...@laszlofrazer.com wrote: Package: gnuplot Version: 4.6.4-2 Linux 3.11-2-amd64 #1 SMP Debian 3.11.10-1 (2013-12-04) x86_64 GNU/Linux G N U P L O T Version 4.6 patchlevel 4 last modified 2013-10-02 When typing file names in gnuplot, one can press tab to auto-complete the file name. This is a very nice feature. However, since an upgrade (not particularly recent), the file name is automatically followed by a space. Gnuplot requires that the file name be followed by a quotation mark. So the user must remove the space for every single file. Reverting to the previous behavior (no automatic space after file name) would be a big improvement. Even better would be if auto-completion automatically inserted a quotation mark followed by a space after the file name. This bug may be readline related. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778614: D-I: Unable to load firmware from NTFS formated usb stick
Hi Andrey, and thanks for your report. Andrey Tataranovich tataranov...@gmail.com (2015-02-17): Package: debian-installer Version: 8.0 beta Severity: important Tags: d-i Dear Maintainer, A few days ago I tried to install Debian Jessie using Debian GNU/Linux testing Jessie - Official Snapshot amd64 NETINST Binary-1 20150209-06:32 disk. Network card require non-free firmware to work (d-i unable to detect network hardware without it) so I inserted NTFS formated usb stick with needed firmware (/firmware). But seems NTFS is not supported so I was unable to proceed. Why not to add support for NTFS for loading missing firmware? As I know kernel already have support for reading NTFS volumes. https://www.debian.org/releases/stable/amd64/ch06s04.html.en contains, under 6.4.1. Preparing a medium: The recommended file system to use is FAT as that is most certain to be supported during the early stages of the installation. Keeping this bug report at wishlist severity (as set by Ben) for later consideration looks like the way to go. Mraw, KiBi. signature.asc Description: Digital signature
Bug#778628: duplicity: Crashes when --progress and --exclude-filelist given
Package: duplicity Version: 0.7.01-1 Severity: normal Dear Maintainer, * What led up to the situation? I wanted to use duplicity and see the progress, i.e. --progress * What exactly did you do (or not do) that was effective (or ineffective)? duplicity --progress --exclude-filelist FILE /home/myhome rsync://HOST/backup * What was the outcome of this action? A crash: ... files M .some_file M .some_file2 M foobar8 Reading filelist FILE Traceback (most recent call last): File /usr/bin/duplicity, line 1507, in module with_tempdir(main) File /usr/bin/duplicity, line 1501, in with_tempdir fn() File /usr/bin/duplicity, line 1350, in main do_backup(action) File /usr/bin/duplicity, line 1483, in do_backup incremental_backup(sig_chain) File /usr/bin/duplicity, line 623, in incremental_backup commandline.set_selection() File /usr/lib/python2.7/dist-packages/duplicity/commandline.py, line 911, in set_selection sel.ParseArgs(select_opts, select_files) File /usr/lib/python2.7/dist-packages/duplicity/selection.py, line 238, in ParseArgs filelists[filelists_index], 0, arg)) File /usr/lib/python2.7/dist-packages/duplicity/selection.py, line 316, in filelist_get_sf self.filelist_read(filelist_fp, inc_default, filelist_name) File /usr/lib/python2.7/dist-packages/duplicity/selection.py, line 352, in filelist_read for line in filelist_fp.read().split(separator): ValueError: I/O operation on closed file * What outcome did you expect instead? I expected to make a backup and see progress. The problem is that when --progress is given, duplicity first does a dry-run. It opens FILE to see the list, after the dry-run, it tries to access this FILE again but it is already closed. Hence the exception. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (500, 'testing-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages duplicity depends on: ii libc62.19-13 ii librsync10.9.7-10 ii python 2.7.8-3 ii python-lockfile 1:0.8-2 Versions of packages duplicity recommends: pn python-oauthlib none ii python-paramiko 1.15.1-1 ii python-urllib3 1.9.1-3 ii rsync3.1.1-2+b1 Versions of packages duplicity suggests: pn lftpnone pn ncftp none pn python-boto none pn python-cloudfiles none ii python-gdata2.0.18+dfsg1-2 pn python-swiftclient none pn tahoe-lafs none -- no debconf information -- Dariusz Dwornikowski, Institute of Computing Science, Poznań University of Technology www.cs.put.poznan.pl/ddwornikowski/ room 1.6.2 BTiCW | tel. +48 61 665 23 71 signature.asc Description: Digital signature
Bug#778623: rancid: RANCID 3.0 changes router.db delimiter in an incompatible way
Hi Bernhard! Bernhard Schmidt schrieb am Dienstag, den 17. Februar 2015: RANCID 3.0 (incorporated in current experimental's 3.1) introduces the following backward incompatible change | router.db,rancid.types.*: change field separator to ';' (semi-colon) to | allow for IPv6 addresses in router.db and avoid conflict with :s in | device commands and perl module names If you don't know that and do not change router.db after the upgrade it will - output weird error messages about hosts being added and removed - remove all configuration already collected (not fatal since it is in VCS, but still) - fail to collect without any usable error message Please either switch router.db in postinst or at least add NEWS.Debian for that change. You're fully right. I already added such a comment to a NEWS.Debian file, but didn't notice that it wasn't installed, since it must be named NEWS (not NEWS.Debian) to be automatically installed by debhelper :-( I'll upload a 3.1-2 soon, which fixes this. Changing the router.db in postinst isn't a good solution since a rancid installation can have multiple router.db files at various places, so only the administrator knows where to find them all... Tscho Roland -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775749: fails to load comments
On Sun, Feb 15, 2015 at 12:21:13PM +0200, Evgeny Stambulchik wrote: FYI, 5.1.25 was released tonight with a fix. Sorry about a slow response. Thanks very much! Lu - I'll upload a new Debian package shortly, but it won't make it into testing or the next stable release, due to the freeze. However, if that's what you're running, the package should still install (manually) without any problems. - Nicholas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777713: unblock: xorg-server/2:1.16.4-1
Control: tag -1 confirmed Julien Cristau jcris...@debian.org (2015-02-11): Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-debbugs-cc: k...@debian.org Please unblock package xorg-server. New upstream stable release with a few bugfixes including a CVE and a regression from the last batch of CVEs. Nothing udeb-relevant in these changes. I failed to allocate some time to perform a quick test just in case, so going to trust you with this. (It's not like any regressions would be hard to pinpoint after the fact anyway, given the massive changes…) And sorry for the lag. Mraw, KiBi. signature.asc Description: Digital signature
Bug#778565: 215-12 does not set correct rights for hidraw devices (and others) anymore
Hi Martin, thanks for your answer. Am Di den 17. Feb 2015 um 14:34 schrieb Martin Pitt: Klaus Ethgen [2015-02-16 23:02 +0100]: The udev rules shipped by the udev package do not use the plugdev group *at all*. I fail to see why an update of udev should have changed anything in that regard. Well, it is in fact. Installing version 215-11 fixes the bug. Which particular binary packages did you downgrade? Just udev (and libudev), or systemd as well? Only udev and libudev. I have no systemd in use. Also, what exactly are the permissions with 215-11, and 215-12? Can you please give us the output of getfacl /dev/input/...? You mean with 215-11 installed? In /dev/input all devices writable by group input; no acl defined. /dev/hidraw0 owned by root:plugdev and mode 0660. Also no acl defined beside common unix rights. The point where I seen that directly is using solaar to look/configure my logitech mouse. There is a special rule that comes with it, /lib/udev/rules.d/60-solaar.rules, that is not working after the update. Please also attach or copy/paste that udev rule, as that seems relevant. I'll attach the file to this mail. And even more. There was many desktop notifications about late detected devices. It was too many to see all of them. I believe that there is something really strange happen with this update. It is indeed. Like Michael said, the only difference in udev 215-12 was for mmcblk devices with RPMB functionality which are not very widespread (and even then, this wouldn't affect input devices). So I'm afraid we need a lot more information here, like the udevadm test input/... output from both a working and a failing situation. Ask for everything you need. I will provide them if I can. Here is the output for /dev/hidraw (Still version 215-11): ~ udevadm test /dev/hidraw0 calling: test version 215 This program is for debugging only, it does not run any program specified by a RUN key. It may show incorrect results, because some values may be different, or not available at a simulation run. load module index Network interface NamePolicy= disabled on kernel commandline, ignoring. Created link configuration context. timestamp of '/etc/udev/rules.d' changed timestamp of '/lib/udev/rules.d' changed read rules file: /lib/udev/rules.d/39-usbmuxd.rules read rules file: /lib/udev/rules.d/40-tlp.rules read rules file: /lib/udev/rules.d/40-usb_modeswitch.rules read rules file: /lib/udev/rules.d/42-usb-hid-pm.rules read rules file: /etc/udev/rules.d/45-hpdjconsole.rules read rules file: /lib/udev/rules.d/50-bluetooth-hci-auto-poweron.rules read rules file: /lib/udev/rules.d/50-firmware.rules read rules file: /lib/udev/rules.d/50-udev-default.rules read rules file: /lib/udev/rules.d/55-Argyll.rules read rules file: /lib/udev/rules.d/55-dm.rules read rules file: /lib/udev/rules.d/56-lvm.rules read rules file: /lib/udev/rules.d/60-bridge-network-interface.rules read rules file: /lib/udev/rules.d/60-cdrom_id.rules read rules file: /lib/udev/rules.d/60-crda.rules read rules file: /lib/udev/rules.d/60-drm.rules read rules file: /lib/udev/rules.d/60-flashrom.rules read rules file: /lib/udev/rules.d/60-fuse.rules read rules file: /lib/udev/rules.d/60-garmin-forerunner-tools.rules read rules file: /lib/udev/rules.d/60-gnupg.rules read rules file: /lib/udev/rules.d/60-heimdall-flash.rules read rules file: /lib/udev/rules.d/60-inputattach.rules read rules file: /lib/udev/rules.d/60-joystick.rules read rules file: /lib/udev/rules.d/60-keyboard.rules read rules file: /lib/udev/rules.d/60-libgphoto2-6.rules read rules file: /lib/udev/rules.d/60-libpisock9.rules read rules file: /lib/udev/rules.d/60-libsane.rules read rules file: /lib/udev/rules.d/60-persistent-alsa.rules read rules file: /lib/udev/rules.d/60-persistent-input.rules read rules file: /lib/udev/rules.d/60-persistent-serial.rules read rules file: /lib/udev/rules.d/60-persistent-storage-dm.rules read rules file: /lib/udev/rules.d/60-persistent-storage-tape.rules read rules file: /lib/udev/rules.d/60-persistent-storage.rules read rules file: /lib/udev/rules.d/60-persistent-v4l.rules read rules file: /lib/udev/rules.d/60-solaar.rules read rules file: /lib/udev/rules.d/61-accelerometer.rules read rules file: /lib/udev/rules.d/64-btrfs.rules read rules file: /lib/udev/rules.d/64-xorg-xkb.rules read rules file: /lib/udev/rules.d/69-libmtp.rules read rules file: /lib/udev/rules.d/69-lvm-metad.rules read rules file: /lib/udev/rules.d/70-android-tools-adb.rules read rules file: /lib/udev/rules.d/70-android-tools-fastboot.rules read rules file: /lib/udev/rules.d/70-btrfs.rules read rules file: /etc/udev/rules.d/70-persistent-cd.rules read rules file: /etc/udev/rules.d/70-persistent-net.rules read rules file: /lib/udev/rules.d/70-power-switch.rules read
Bug#774135: mc: segfault for SFTP VFS
severity 774135 important
thanks
Dixi quod…
I’ll track this down further.
OK, we have a honest code bug (typescript first, analysis below):
tglase@tglase:~ $ gdb /usr/bin/mc.distrib ~/core
GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type show copying
and show warranty for details.
This GDB was configured as x86_64-linux-gnux32.
Type show configuration for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type help.
Type apropos word to search for commands related to word...
Reading symbols from /usr/bin/mc.distrib...done.
BFD: Warning: /home/tglase/core is truncated: expected core file size =
1744896, found: 1736704.
[New LWP 22766]
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnux32/libthread_db.so.1.
Core was generated by `/usr/bin/mc -d'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0xf77a0513 in sftpfs_cb_open_connection (super=optimized out,
vpath=optimized out,
vpath_element=optimized out) at vfs_subclass.c:114
114 vpath_element-class-verrno = mcerror-code;
(gdb) bt
#0 0xf77a0513 in sftpfs_cb_open_connection (super=optimized out,
vpath=optimized out,
vpath_element=optimized out) at vfs_subclass.c:114
#1 0xf775e839 in vfs_s_get_path (vpath=vpath@entry=0xf97ae880,
archive=archive@entry=0xff95bec8,
flags=flags@entry=0) at direntry.c:1147
#2 0xf775ecfb in vfs_s_inode_from_path (vpath=vpath@entry=0xf97ae880,
flags=flags@entry=5)
at direntry.c:380
#3 0xf775eeb1 in vfs_s_opendir (vpath=optimized out) at direntry.c:409
#4 0xf775ef18 in vfs_s_chdir (vpath=optimized out) at direntry.c:477
#5 0xf7728ac1 in mc_chdir (vpath=vpath@entry=0xf9797f90) at interface.c:685
#6 0xf7735f53 in _do_panel_cd (panel=optimized out,
new_dir_vpath=0xf9797f90, cd_type=optimized out)
at panel.c:3179
#7 0xf7736afc in do_panel_cd (panel=optimized out, new_dir_vpath=optimized
out,
cd_type=optimized out) at panel.c:4535
#8 0xf77380bd in do_cd (new_dir_vpath=new_dir_vpath@entry=0xf9797f90,
exact=exact@entry=cd_parse_command)
at panel.c:4934
#9 0xf77181bb in do_cd_command (orig_cmd=optimized out) at command.c:445
#10 0xf771865f in enter (lc_cmdline=optimized out) at command.c:263
#11 command_callback (w=optimized out, sender=optimized out, msg=optimized
out,
parm=optimized out, data=optimized out) at command.c:355
#12 0xf7731e2c in send_message (data=0x0, parm=10, msg=MSG_KEY, sender=0x0,
w=optimized out)
at ../../lib/widget/widget-common.h:167
#13 midnight_callback (w=optimized out, sender=optimized out,
msg=optimized out,
parm=optimized out, data=optimized out) at midnight.c:1469
#14 0xf7719eeb in send_message (data=0x0, parm=10, msg=MSG_KEY, sender=0x0,
w=0xf9797fc0)
at ../../lib/widget/widget-common.h:167
#15 dlg_key_event (d_key=10, h=optimized out) at dialog.c:504
#16 dlg_process_event (h=optimized out, key=10, event=optimized out) at
dialog.c:1235
#17 0xf771a581 in frontend_dlg_run (h=0xf9797fc0) at dialog.c:569
#18 dlg_run (h=optimized out) at dialog.c:1266
#19 0xf7732ccd in create_panels_and_run_mc () at midnight.c:960
#20 do_nc () at midnight.c:1753
#21 0xf770d147 in main (argc=1, argv=0xff95c394) at main.c:414
(gdb) print mcerror
$1 = (GError *) 0x0
(gdb) list sftpfs_cb_open_connection
87 */
88
89 static int
90 sftpfs_cb_open_connection (struct vfs_s_super *super,
91 const vfs_path_t * vpath, const
vfs_path_element_t * vpath_element)
92 {
93 GError *mcerror = NULL;
94 sftpfs_super_data_t *sftpfs_super_data;
95 int ret_value;
96
(gdb)
97 (void) vpath;
98
99 if (vpath_element-host == NULL || *vpath_element-host == '\0')
100 {
101 vfs_print_message (_(sftp: Invalid host name.));
102 vpath_element-class-verrno = EPERM;
103 return -1;
104 }
105
106 sftpfs_super_data = g_new0 (sftpfs_super_data_t, 1);
(gdb)
107 sftpfs_super_data-original_connection_info =
vfs_path_element_clone (vpath_element);
108 super-data = sftpfs_super_data;
109 super-path_element = vfs_path_element_clone (vpath_element);
110
111 sftpfs_fill_connection_data_from_config (super, mcerror);
112 if (mc_error_message (mcerror))
113 {
114 vpath_element-class-verrno = mcerror-code;
115 return -1;
116 }
The thing is: mc_error_message free()s mcerror afterwards,
so this is a genuine use-after-free bug.
bye,
//mirabilos
--
Sometimes they [people] care too much: pretty
Bug#778281: unblock (pre-approval): freerdp/1.1.0~git20140921.1.440916e+dfsg1-3
On Fri, Feb 13, 2015 at 06:07:56AM +0100, Mike Gabriel sunwea...@debian.org wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please consider unblocking planned upload of package freerdp. Did you raise the severity to grave only to have out attention? Regards, -- Mehdi Dogguy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778625: ITP: libjs-term.js -- full xterm clone written in javascript
Package: wnpp Severity: wishlist Owner: Thomas Goirand z...@debian.org * Package name: libjs-term.js Version : 0.0.4 Upstream Author : Christopher Jeffrey chjjeff...@gmail.com * URL : https://github.com/chjj/term.js * License : Expat Programming Lang: Javascript Description : full xterm clone written in javascript Term.js is a full xterm clone written in javascript. It is a fork from the original work of Fabrice Bellard's javascript vt100 for jslinux (with the author's permission. The original design remains. The terminal itself has been extended to include xterm CSI codes, among other features. This is a new dependency of the OpenStack dashboard, Horizon. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762843: lookup_sss.so missing - fixed in the unreleased 5.0.8-2 version
Hello. The last changes (10 months ago) to autofs.git, preliminarily becoming 5.0.8-2, seems to fix the missing lookup_sss.so. Tested on Jessie on x86_64 as of today, 2015-02-17, with HEAD from http://anonscm.debian.org/cgit/collab-maint/autofs.git as of today. I would vote on getting this version pushed into Jessie or Jessie-updates, as this fixes autofs+sss. The fix in Ubuntu (pushed into 14.04) fixes the same problem in a slightly different way (specifying sssldir instead of helping AF_CHECK_SSS_LIB find things), but both seem to work. /Tomas -- Tomas Forsman, st...@cs.umu.se, http://www.cs.umu.se/~stric/ `- SysAdmin at Computing Science, University of Umeå -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778281: unblock (pre-approval): freerdp/1.1.0~git20140921.1.440916e+dfsg1-3
Hi Mehdi, no, the severity was set by the bug submitter IIRC. I recently downgraded the severity to important to avoid removal from testing and because of the malformed command line the bug submitter used. Nonetheless, segfaults should not happen and the provided patch fixes that. Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976148 GnuPG Key ID 0x25771B13 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de - Original message - On Fri, Feb 13, 2015 at 06:07:56AM +0100, Mike Gabriel sunwea...@debian.org wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please consider unblocking planned upload of package freerdp. Did you raise the severity to grave only to have out attention? Regards, -- Mehdi Dogguy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#716237: [PATCH] rt-migrate-test: exit early if nr_runs is non-positive
On Tue, 17 Feb 2015, Boris Egorov wrote:
Sorry, PROGRESS_CHARS macro is used correctly, but INTERVAL and
RUN_INTERVAL not. In my opinion, they should be defined and used once in
static variable assigning, and nowhere else.
On 02/17/2015 08:30 PM, Boris Egorov wrote:
Looks like this patch is not applied yet.
I can move value check to parse_options and send another version of
patch. As for macros - yes, I already mentioned them in debian bug
report thread. There are three of them (INTERVAL, RUN_INTERVAL,
PROGRESS_CHARS) which are improperly (IMO) used instead of corresponding
lowercase variables. I thought these changes should go to another patch.
On 02/17/2015 08:08 PM, Sebastian Andrzej Siewior wrote:
* Boris Egorov | 2014-11-27 16:20:34 [+0600]:
Program will crash if nr_runs is 0 due to dividing by it in
print_results(). Let's exit early instead.
Fixes: http://bugs.debian.org/716237
Has this been dealt with? I can't see this applied. I would prefer
doing the value check in parse_options() itself. And looking at it, it
seems that run_interval is interval ignored. Or is there macro magic
invovled?
Signed-off-by: Boris Egorov ego...@linux.com
---
src/rt-migrate-test/rt-migrate-test.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/src/rt-migrate-test/rt-migrate-test.c
b/src/rt-migrate-test/rt-migrate-test.c
index e3c7a09..876a122 100644
--- a/src/rt-migrate-test/rt-migrate-test.c
+++ b/src/rt-migrate-test/rt-migrate-test.c
@@ -465,6 +465,11 @@ int main (int argc, char **argv)
parse_options(argc, argv);
+ if (nr_runs = 0) {
+ fprintf(stderr, Warning, --loops argument is non-positive.
Exiting.\n);
+ exit(-1);
+ }
+
signal(SIGINT, stop_log);
if (argc = (optind + 1))
--
2.1.3
Sebastian
--
Best regards,
Boris Egorov
--
Awaiting your respin on these patches.
Thanks
John
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778626: broadcom-sta-dkms: Module build ... was skipped
Le mardi 17 février 2015, 16:56:44 Rainer a écrit : Hi, First Installation: checking all kernels... Building only for 3.16.0-4-amd64 Module build for the currently running kernel was skipped since the kernel source for this kernel does not seem to be installed. Could you please check that the following links are present in /lib/modules/3.16.0-4-amd64/: build - /usr/src/linux-headers-3.16.0-4-amd64/ source - /usr/src/linux-headers-3.16.0-4-common/ And check that target directories are ok. For your information linux-source is not required to build the module, installing linux-headers-3.16.0-4-amd64 should be enough. Regards, Cyril Lacoux -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767413: Workaround
A simple workaround is to erase the file kileuirc and at next start kile goes back to a normal behavior. Maybe it was just a sid update that broke it. I am not sure if it should actually be considered as a kile bug,... cheers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778616: cdimage.debian.org: Misnamed jigdo template prevents jigdo from downloading
Package: cdimage.debian.org Severity: grave Justification: renders package unusable Dear Maintainer, This bug report concerns the jigdo file at http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including- firmware/jessie_di_rc1/amd64/jigdo-cd/ The jigdo file references a template file that does not exist. As a result, jigdo-lite gets a 404 when it looks to download it. There is, however, a template file on the web page referenced above. Downloading this file manually and then renaming that file so it has a capital J in Jesse lets jigdo find it. The error makes the jigdo file unusable and the fix is simple. After renaming, everything works as expected. Jigdo downloads the iso with no problems and the install worked fine. Thanks. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.13-1-686-pae (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: sysvinit (via /sbin/init) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#567363: evince cannot correctly save some pdf forms
I just encountered this in a more serious form -- evince now attempts to save filled in data in forms, but doesn't it doesn't always work. I was also filling in my tax information to an IRS form, tested to make sure saving the form data worked before I got started, and then started filling things out -- when I saved partway through, I got a corrupt file and lost all my information. I'm having difficulty reproducing the bug, but I do have the saved corrupt files (two different kinds: one was just a 0-byte file, the other seemed to include the filled in form data but none of the data from the original PDF, and is not a valid PDF). To me this seems like it should have severity serious, since it leads to data loss in its current form -- no? This is with evince 3.14.1-1; here's my dependency information: -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8.11 (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 Init: unable to detect Versions of packages evince depends on: ii evince-common 3.14.1-1 ii gnome-icon-theme-symbolic 3.12.0-1 ii libatk1.0-02.14.0-1 ii libc6 2.19-13 ii libcairo-gobject2 1.14.0-2.1 ii libcairo2 1.14.0-2.1 ii libevdocument3-4 3.14.1-1 ii libevview3-3 3.14.1-1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgtk-3-0 3.14.5-1 ii libnautilus-extension1a3.14.1-2 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-01.36.8-3 ii libsecret-1-0 0.18-1+b1 ii libxml22.9.1+dfsg1-4 ii shared-mime-info 1.3-1 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages evince recommends: ii dbus-x11 1.8.12-3 ii gvfs 1.22.2-1 Versions of packages evince suggests: ii nautilus 3.14.1-2 ii poppler-data 0.4.7-1 pn unrar 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#778621: (no subject)
Subject: exit: Unable to access system settings after applying updates Package: exit Version: system settings Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** -- System Information: Debian Release: 7.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778619: ITP: python-kafka -- client for Apache Kafka
Package: wnpp Severity: wishlist Owner: Thomas Goirand z...@debian.org * Package name: python-kafka Version : 0.9.3 Upstream Author : David Arthur mum...@gmail.com * URL : https://github.com/mumrah/kafka-python * License : Apache-2.0 Programming Lang: Python Description : client for Apache Kafka This module provides low-level protocol support for Apache Kafka as well as high-level consumer and producer classes. Request batching is supported by the protocol as well as broker-aware request routing. Gzip and Snappy compression is also supported for message sets. This is a new dependency for OpenStack kilo. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778612: live-boot: please remove obsolete unionmount support
Source: live-boot Severity: minor Hello, unionmount is obsolete and requires specially patched kernel and mount binary. It is superseded by overlayfs which is in turn superseded by overlay. I think there is no point keeping support for this union type and traces of it in the live scripts can only confuse users. Thanks Michal -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (910, 'testing'), (900, 'stable'), (410, 'unstable'), (400, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.18.0-trunk-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/bash 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#778620: systemd: Add less to suggests or recommends
Package: systemd Version: 218-10 Severity: minor Dear Maintainer, from man journalctl: The output is paged through less by default, and long lines are truncated to screen width. The hidden part can be viewed by using the left-arrow and right- arrow keys. But less is not a recommendation or suggestion of systemd thanks, floris -- Package-specific info: -- 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=nl_NL.utf8, LC_CTYPE=nl_NL.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd depends on: ii acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-58 ii libacl1 2.2.52-2 ii libapparmor12.9.0-3+exp1 ii libaudit1 1:2.4-1+b1 ii libblkid1 2.25.2-5 ii libc6 2.19-15 ii libcap2 1:2.24-6 ii libcap2-bin 1:2.24-6 ii libcryptsetup4 2:1.6.6-5 ii libgcrypt20 1.6.2-4+b1 ii libkmod218-3 ii liblzma55.1.1alpha+20120614-2+b3 ii libmount1 2.25.2-5 ii libpam0g1.1.8-3.1 ii libselinux1 2.3-2 ii libsystemd0 218-10 ii mount 2.25.2-5 ii sysv-rc 2.88dsf-58 ii udev218-10 ii util-linux 2.25.2-5 Versions of packages systemd recommends: ii dbus1.8.16-1 ii libpam-systemd 218-10 Versions of packages systemd suggests: pn systemd-ui 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#778611: donations: fix listing of paypal for Debian France
Package: www.debian.org Severity: normal Tags: patch Hi, The patch below fixes the listing of paypal for Debian France (so that it's mentioned in the top table, rather than 'other'). See also https://lists.debian.org/debian-www/2014/11/msg00067.html for the context of this change. Lucas Index: donations.wml === RCS file: /cvs/webwml/webwml/english/donations.wml,v retrieving revision 1.82 diff -u -r1.82 donations.wml --- donations.wml 18 Jan 2015 14:25:13 - 1.82 +++ donations.wml 17 Feb 2015 13:34:35 - @@ -72,7 +72,7 @@ tda href=#debianfranceDebian France/a/td td a href=#debianfrance-bankwire transfer/a, - a href=#debianfrance-otherother/a + a href=#debianfrance-paypalPayPal/a /td tdFrance, tax-exempt non-profit/td /tr @@ -208,7 +208,7 @@ a href=mailto:c...@france.debian.net;c...@france.debian.net/a. /p -h4 id=debianfrance-otherPayPal/h4 +h4 id=debianfrance-paypalPayPal/h4 p Donations can be sent via the a href=https://france.debian.net/galette/plugins/galette-plugin-paypal/paypal_form.php?pref_lang=en_US;Debian France PayPal page/a. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778565: 215-12 does not set correct rights for hidraw devices (and others) anymore
Control: tag -1 unreproducible moreinfo Hello Klaus, Klaus Ethgen [2015-02-16 23:02 +0100]: The udev rules shipped by the udev package do not use the plugdev group *at all*. I fail to see why an update of udev should have changed anything in that regard. Well, it is in fact. Installing version 215-11 fixes the bug. Which particular binary packages did you downgrade? Just udev (and libudev), or systemd as well? Also, what exactly are the permissions with 215-11, and 215-12? Can you please give us the output of getfacl /dev/input/...? The point where I seen that directly is using solaar to look/configure my logitech mouse. There is a special rule that comes with it, /lib/udev/rules.d/60-solaar.rules, that is not working after the update. Please also attach or copy/paste that udev rule, as that seems relevant. And even more. There was many desktop notifications about late detected devices. It was too many to see all of them. I believe that there is something really strange happen with this update. It is indeed. Like Michael said, the only difference in udev 215-12 was for mmcblk devices with RPMB functionality which are not very widespread (and even then, this wouldn't affect input devices). So I'm afraid we need a lot more information here, like the udevadm test input/... output from both a working and a failing situation. Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#778615: installation-reports: Lenovo T61 8889-B35 NVIDIA G86M Quadro NVS 140M
Package: installation-reports Severity: normal Dear Maintainer, installation, wethernet, wireless and brightness controll works without any problems. There is a problem with graphics when waking up from suspend, I will fill in a seperate bug report upstream. -- Package-specific info: Boot method: CD Image version: http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/jessie_di_beta_2/amd64/iso-cd/firmware-jessie-DI-b2-amd64-netinst.iso Date: Date and time of the install Machine: Lenovo T61 8889-B35 NVIDIA G86M Quadro NVS 140M Partitions: DateisystemTyp 1K-Blöcke Benutzt Verfügbar Verw% Eingehängt auf /dev/sda1 ext4 88776 5925684 995919766% / udev devtmpfs 10240 0 102400% /dev tmpfs tmpfs 40490861163987922% /run tmpfs tmpfs 1012268 80 10121881% /dev/shm tmpfs tmpfs 5120 4 51161% /run/lock tmpfs tmpfs 1012268 0 10122680% /sys/fs/cgroup tmpfs tmpfs 202456 42024521% /run/user/1000 tmpfs tmpfs 202456 122024441% /run/user/119 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=8 (jessie) - installer build 20141002 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux znote-t61-03 3.16-2-amd64 #1 SMP Debian 3.16.3-2 (2014-09-20) x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 0c) lspci -knn: Subsystem: Lenovo Device [17aa:20b1] lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation Mobile PM965/GM965/GL960 PCI Express Root Port [8086:2a01] (rev 0c) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 82566MM Gigabit Network Connection [8086:1049] (rev 03) lspci -knn: Subsystem: Lenovo Device [17aa:20b9] lspci -knn: Kernel driver in use: e1000e lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 [8086:2834] (rev 03) lspci -knn: Subsystem: Lenovo Device [17aa:20aa] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1a.1 USB controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 [8086:2835] (rev 03) lspci -knn: Subsystem: Lenovo Device [17aa:20aa] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1a.7 USB controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 [8086:283a] (rev 03) lspci -knn: Subsystem: Lenovo Device [17aa:20ab] lspci -knn: Kernel driver in use: ehci-pci lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) HD Audio Controller [8086:284b] (rev 03) lspci -knn: Subsystem: Lenovo Device [17aa:20ac] lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 [8086:283f] (rev 03) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 [8086:2841] (rev 03) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 [8086:2843] (rev 03) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 [8086:2845] (rev 03) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 [8086:2847] (rev 03) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 [8086:2830] (rev 03) lspci -knn: Subsystem: Lenovo Device [17aa:20aa] lspci
Bug#778614: D-I: Unable to load firmware from NTFS formated usb stick
Control: severity -1 wishlist On Tue, 2015-02-17 at 16:55 +0300, Andrey Tataranovich wrote: Package: debian-installer Version: 8.0 beta Severity: important Tags: d-i Dear Maintainer, A few days ago I tried to install Debian Jessie using Debian GNU/Linux testing Jessie - Official Snapshot amd64 NETINST Binary-1 20150209-06:32 disk. Network card require non-free firmware to work (d-i unable to detect network hardware without it) so I inserted NTFS formated usb stick with needed firmware (/firmware). But seems NTFS is not supported so I was unable to proceed. Why not to add support for NTFS for loading missing firmware? As I know kernel already have support for reading NTFS volumes. NTFS is special because it is not a user-space filesystem. And Windows does not allow formatting removable drives as NTFS, so this is not a normal filesystem to use on removable drives. Reducing the severity accordingly. Ben. -- Ben Hutchings Never attribute to conspiracy what can adequately be explained by stupidity. signature.asc Description: This is a digitally signed message part
Bug#778614: D-I: Unable to load firmware from NTFS formated usb stick
Andrey Tataranovich, le Tue 17 Feb 2015 16:55:47 +0300, a écrit : Why not to add support for NTFS for loading missing firmware? As I know kernel already have support for reading NTFS volumes. Just FTR (not implying anything, just giving the number), ntfs.ko weighs 326KiB on my 3.16 kernel. Samuel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
