Bug#780772: [drupal7] Security update for drupla7 & drupal6
Package: drupal7 Version: 7.32-1+deb8u1 Severity: serious Tags: security X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org --- Please enter the report below this line. --- Hi! https://www.drupal.org/drupal-7.35 says: >Drupal 7.35 and Drupal 6.35, maintenance releases which contain fixes >for security vulnerabilities, are now available for download. See the >Drupal 7.35 and Drupal 6.35 release notes for further information. > >Upgrading your existing Drupal 7 and 6 sites is strongly recommended. >There are no new features or non-security-related bug fixes in these >releases. For more information about the Drupal 7.x release series, >consult the Drupal 7.0 release announcement. More information on the >Drupal 6.x release series can be found in the Drupal 6.0 release >announcement. Please supply a fixed package upload ASAP, thanks! Ingo --- System information. --- Architecture: amd64 Kernel: Linux 3.16.0-4-amd64 Debian Release: 8.0 500 unstablewww.deb-multimedia.org 500 unstableftp.de.debian.org --- Package information. --- Depends(Version) | Installed -+- debconf(>= 0.5) | 1.5.55 OR debconf-2.0 | apache2 | 2.4.10-10 OR httpd| php5 | 5.6.6+dfsg-2 php5-mysql | 5.6.6+dfsg-2 OR php5-pgsql | 5.6.6+dfsg-2 OR php5-sqlite | 5.6.6+dfsg-2 php5-gd | 5.6.6+dfsg-2 default-mta | OR mail-transport-agent | wwwconfig-common (>= 0.0.37) | 0.2.2 mysql-client | 5.5.42-1 OR virtual-mysql-client | OR postgresql-client| 9.4+166 dbconfig-common | 1.8.47+nmu3 curl | 7.38.0-4 Recommends(Version) | Installed ===-+-=== mysql-server| 5.5.42-1 OR postgresql | 9.4+166 OR sqlite3 | 3.8.7.4-1 Package's Suggests field is empty. -- Ciao...// Fon: 0381-2744150 Ingo \X/ http://blog.windfluechter.net Please don't share this address with Facebook or Google! gpg pubkey: http://www.juergensmann.de/ij_public_key.asc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780020: [UDD] bugs.cgi: YAML contains raw HTML and "ruby objects"
On 2015-03-18 18:38, Lucas Nussbaum wrote: > Hi Niels, > > bugs.cgi started as a huge amount of spaghetti code, and is slightly > become better. > > [...] > > For last_modified, I've added a new 'last_modified_string' field that > shows the date as text. Should be easily parsable by about everything. > > For caffected, the raw data is already available: > affects_stable: false > affects_testing: true > affects_unstable: false > affects_experimental: true > > For cdeferred, it's probably easy enough to parse right now. > > For chints, I did not manage to output something clean, for strange > reasons. > > bugs.cgi needs a fall rewrite (with a design similar to DMD). In the > meantime, it's not possible to fix this properly. > > Lucas > Ok, thanks for the changes so far. :) ~Niels -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#750999: qa.debian.org: I would be usefull have a comment field in dmd
On 19/03/15 at 12:51 +0800, Paul Wise wrote: > On Thu, Mar 19, 2015 at 1:37 AM, Lucas Nussbaum wrote: > > > I wonder if there are external services that could serve as data stores > > for the comments? Something like disqus, but simpler. > > I think it would be best to store the data in UDD or another Debian service. Do you have a suggestion about how to implement that, that would not be unacceptable in terms of security? Lucas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780555: apt-cacher-ng: Use with Fedora Rawhide is problematic
On 19/03/15 05:56, Eduard Bloch wrote: > Control: tags 780555 +upstream > > Hallo, > * Carlos Maddela [Mon, Mar 16 2015, 12:21:54PM]: > >> Using apt-cacher-ng to cache RPMs from Fedora Rawhide eventually results >> in packages that cannot be verified, because it would seem that Fedora >> allows them to be rebuilt without incrementing the version number. >> >> I tried fixing this problem by marking them as volatile with the >> VfilePatternEx option: >> >> /development/rawhide/.* >> >> However, this fails to achieve anything, since the default SPfilePattern >> includes all RPMs and this option overrides any VfilePattern option. >> >> Not completely understading why the default SPfilePattern must include >> all RPMs, I have provided a possible solution which allows for > It's a bug. It was intended to match only .gpg files but the final > bracket is misplaced. > > Even with that small fix the SPfilePattern checking implementation > doesn't allow to make files like foo.rpm.gpg considered volatile, so I > will add your patch soon, probably with minor modifications after > review/check for side effects. Thanks! > > But the last patch with extra mirrors is something I do not fully agree > with. The backends files are generated semi-automatically (see special > make targets) and Fedora mirror list is fed from > https://mirrors.fedoraproject.org/publiclist . Some of the sites you > added are already in the list that I compiled a couple of weeks ago but > not all; and they are also not on the publiclist page. Could you reveal > the source of that mirror urls? > > Kind Regards, > Eduard. > Those mirrors were automatically generated by the metalink line in the standard fedora-repos-rawhide package, which was https://mirrors.fedoraproject.org/metalink?repo=rawhide&arch=$basearch. I ended up disabling the metalink feature, because just when you thought you had all mirrors covered, a new one would be chosen. I've been using an unpatched version of apt-cacher-ng for the past couple of days, but haven't been able to reproduce the bug again. None of the RPMs that I have cached have been rebuilt with the same version number. It just seems odd to me that this would be standard practice for Fedora, but I could have sworn that that was what was happening when I checked the HTTP headers with curl. I'll keep monitoring to see if this really is a problem. Thanks, Carlos -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780771: php5-curl: libcurl no more sends client certificate during mutual TLS authentication
Package: php5-curl Version: 5.4.38-0+deb7u1 Severity: normal Dear Maintainer, I upgraded today from 5.4.36 to 5.4.38 and the mutual authentication that I have coded with the curl php module is no more working : the client certificate is no more sent to the server. Here is the code to reproduce the bug : https://www.myweb.com";); echo curl_exec($ch); ?> Output is : * About to connect() to www.myweb.com port 443 (#0) * Trying 10.11.12.13... * connected * Connected to myweb.com (10.11.12.13) port 443 (#0) * successfully set certificate verify locations: * CAfile: none CApath: /etc/ssl/certs * SSL connection using DHE-RSA-AES256-SHA [...] * Server certificate: *subject: C=FR; O=Org; CN=*.myweb.com *start date: 2014-01-31 16:15:52 GMT *expire date: 2019-01-31 16:15:52 GMT *common name: *.myweb.com (matched) *issuer: C=FR; O=Org; CN= Auth Server CA *SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway. > GET / HTTP/1.1 Host: www.myweb.com Accept: */* * additional stuff not fine transfer.c:1037: 0 0 * HTTP 1.1 or later with persistent connection, pipelining supported < HTTP/1.1 400 Bad Request < Server: nginx/1.4.4 < Date: Wed, 18 Mar 2015 19:57:28 GMT < Content-Type: text/html < Content-Length: 252 < Connection: close < * Closing connection #0 400 No required SSL certificate was sent 400 Bad Request No required SSL certificate was sent nginx/1.4.4 Regards, -- 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=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages php5-curl depends on: ii dpkg 1.16.15 ii libapache2-mod-php5 [phpapi-20100525] 5.4.38-0+deb7u1 ii libc6 2.13-38+deb7u8 ii libcurl3 7.26.0-1+wheezy12 ii php5-cli [phpapi-20100525] 5.4.38-0+deb7u1 ii php5-common5.4.38-0+deb7u1 ii ucf3.0025+nmu3 php5-curl recommends no packages. php5-curl 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#780770: The show_damage option does not show spell damage
Package: angband Version: 1:3.5.1-2 Severity: normal The show_damage option shows the damage done by melee or ranged attacks, but not the damage done by spells. - Josh Triplett -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages angband depends on: ii angband-data 1:3.5.1-2 ii libc62.19-17 ii libncursesw5 5.9+20140913-1+b1 ii libsdl-image1.2 1.2.12-5+b5 ii libsdl-mixer1.2 1.2.12-11+b1 ii libsdl-ttf2.0-0 2.0.11-3 ii libsdl1.2debian 1.2.15-10+b1 ii libtinfo55.9+20140913-1+b1 ii libx11-6 2:1.6.2-3 Versions of packages angband recommends: ii xfonts-base 1:1.0.4 Versions of packages angband suggests: pn angband-audio pn angband-bigtiles -- Configuration Files: /etc/angband/edit/shop_own.txt 9006ce000ef68033a37963813609b6a9 [Errno 2] No such file or directory: u'/etc/angband/edit/shop_own.txt 9006ce000ef68033a37963813609b6a9' /etc/angband/pref/font-gcu.prf changed [not included] /etc/angband/pref/font-mac.prf 61784cbe0a1a02878b228867c79da566 [Errno 2] No such file or directory: u'/etc/angband/pref/font-mac.prf 61784cbe0a1a02878b228867c79da566' -- no debconf information -- debsums errors found: debsums: changed file /var/games/angband/apex/scores.raw (from angband package) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#750999: qa.debian.org: I would be usefull have a comment field in dmd
On Thu, Mar 19, 2015 at 1:37 AM, Lucas Nussbaum wrote: > I wonder if there are external services that could serve as data stores > for the comments? Something like disqus, but simpler. I think it would be best to store the data in UDD or another Debian service. -- 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#780675: systemd: segfault in systemd when running systemctl daemon-reload
Am 18.03.2015 um 19:01 schrieb Michael Biebl: > Control: fixed -1 219-4 > > Am 18.03.2015 um 18:00 schrieb Michael Biebl: >> Thanks for sharing the contents of the file. I can confirm the crash and >> we have enough information now to debug this issue properly. >> Marking the bug accordingly. > > Can't reproduce the issue with the version from experimental. > Marking accordingly Found the commit which fixes it [1]. Applies neatly on top of v215: The commit message fits rather perfectly here :-) core: do not add dependencies to self Adds a pair of files which cause a segfault (also with systemd-analyze verify). https://bugzilla.redhat.com/show_bug.cgi?id=1124843 [1] http://cgit.freedesktop.org/systemd/systemd/commit/?id=e66047ff62c971eefa32b42373420d61e3f2a9c1 -- 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#780705: udev: floating net device number on devices with ro rootfs
Am 19.03.2015 um 04:34 schrieb You-Sheng Yang: > On Wed, 18 Mar 2015 18:46:00 +0100 Michael Biebl wrote: >> Dear You-Sheng Yang, >> >> first of all, the bug report was filed against the wrong package. The >> package dealing with the network renaming is udev. Therefore reassigning >> to udev. > > Sorry, I thought it had to be filed under its source package. In that case, you need to use Source: systemd, but using Package: udev is correct in this case >> Third, and this is the most important part, the patch/solution you are >> suggesting, don't work / make any sense. The persistent network interface >> naming feature as used by default in Debian udev requires a persistent >> storage, i.e. a writable /etc/udev/rules.d by design. If you deviate >> from a default Debian setup and make / or /etc ro, you can simply not >> use this particular feature. Simple as that. > > https://wiki.debian.org/ReadonlyRoot > Looks like read-only rootfs is also permitted in Debian. Bugs blocking > ro rootfs are accepted in other packages, and there is also a small > section addressing udev under ro rootfs. Let me quote the wiki: Preconditions: "Locations that must be writable are /etc, /home, /srv, /tmp, /var." > Anyway, here is another patch that solves the same problem. It actually > tries to avoid duplicated written entries in "70-persistent-net.rules". > If there is already a rule with the same match conditions, let > "write_net_rules" reuse the existing one and therefore it increases > device name no more. This patch is generated directly from the device > under test. Not writing duplicated entries in "70-persistent-net.rules" should indeed be the case. I'll let Marco, who wrote the code, review the patch. He should be more familiar with it. Marco, if you think this patch is correct and worthwile to apply, please reopen this bug report. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#780241: [NETWORKING #LVG-179-41238]: Re: mirror submission for debian.mirror.digitalpacific.com.au
Hi Donald, Thanks for the response! > It is wiser to sync from a more or less local mirror than over great distance, especially if cost is an issue. However you can change your upstream as needs or failures arise. > The most important thing is the mirror is current within the totality of the archive. I agree. Cost isn't really an issue as our traffic profile is predominantly egress. It just made more sense to sync from something which is more local to where we are located. Just as a FYI, the vast majority of Internet "activity" happens within Sydney, as almost all of the international links terminate local to Sydney. The mirror owner of the IP behind ftp.au.debian.org is a company called IX-Australia (formally known as WAIX [Western Australia Internet Exchange]). They recently expanded over to the east cost (Sydney/Melbourne/Queensland), so I'll ping them and see if they have future plans with the server (we actually are provisioning a 10Gig peering port with them at the moment too). > Your mirror will be added to the official listing. Fantastic, thanks! :) > If you are interested I can send you a followup or cc to the admins at aarnet.edu. No need! But thank you for offering! Regards, Matthew. Ticket Details Ticket ID: LVG-179-41238 Department: Networking Type: Issue Status: Closed Priority: Medium Helpdesk: https://www.digitalpacific.com.au/internal-esupport/index.php?/default_import -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780754: README.html screenshot
> See attached screenshot.
Bug#780769: debian-installer: monolithic images miss crypto components
Package: debian-installer Version: 20130613+deb7u2 20150107 Severity: normal Toying around with monolithic images made me (re?)discover that crypto components are missing there. The reason seems to be their priority (optional), meaning they don't get automatically picked up in the pkg-lists/standard-udebs target & file, later included from the build/pkg-lists/monolithic/common file. I'm not sure what to do with it to be honest. Not touching the priority and the standard-udebs generation would seem the best way for now, and adding a few udebs to monolithic/common might make sense. But then, why are those optional in the first place anyway? Looking at it, one can see (e.g. partman-auto-lvm): | commit 3df509c8b87451e3649cdc87ceecd53cd3e8cb2a | Author: Frans Pop | Date: Thu Dec 6 16:37:48 2007 + | | Dynamically load support for LVM and crypto | | Only load components for LVM and crypto support when there is | sufficient free memory. For crypto this only loads base support | components; additional crypto components will only be loaded on | demand. | | Support for guided (encrypted) LVM partitioning is only loaded if | partman-auto has already been loaded (which it may not be for | lowmem installs). | | The priority of partman-(auto-)lvm and partman-(auto-)crypto is | lowered to optional to allow dynamic loading by partman-base. | | The dynamic loading is done from the main partman script instead | of an init.d script to avoid interference from anna's progress bar | with the init.d progress bar. | | The limit of 7500kB for LVM is based on tests on i386 (VirtualBox | with 5GB hard disk); the limit of 11000kB for crypto is based on | the existing limit used in partman-crypto for loading additional | components. | | r50370 Since monolithic images are meant to embed a lot of stuff, it might make sense to add a few udebs below the #include mentioned above. Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780705: udev: floating net device number on devices with ro rootfs
On Wed, 18 Mar 2015 18:46:00 +0100 Michael Biebl wrote:
> Dear You-Sheng Yang,
>
> first of all, the bug report was filed against the wrong package. The
> package dealing with the network renaming is udev. Therefore reassigning
> to udev.
Sorry, I thought it had to be filed under its source package.
> Second, the patch itself is not working. The temporary file is called
> /run/udev/tmp-rules--70-persistent-net.rules, not tmp-ruiles--..., so
> this patch can't have been tested, therefore removing the patch tag.
Yes, I noticed that but still re-attached the wrong one.
> Third, and this is the most important part, the patch/solution you are
> suggesting, don't work / make any sense. The persistent network interface
> naming feature as used by default in Debian udev requires a persistent
> storage, i.e. a writable /etc/udev/rules.d by design. If you deviate
> from a default Debian setup and make / or /etc ro, you can simply not
> use this particular feature. Simple as that.
https://wiki.debian.org/ReadonlyRoot
Looks like read-only rootfs is also permitted in Debian. Bugs blocking
ro rootfs are accepted in other packages, and there is also a small
section addressing udev under ro rootfs.
Anyway, here is another patch that solves the same problem. It actually
tries to avoid duplicated written entries in "70-persistent-net.rules".
If there is already a rule with the same match conditions, let
"write_net_rules" reuse the existing one and therefore it increases
device name no more. This patch is generated directly from the device
under test.
--
You-Sheng Yang (Vicamo)
From ca74f1efff06983160fe28bc3f931de73438de0a Mon Sep 17 00:00:00 2001
From: You-Sheng Yang
Date: Wed, 18 Mar 2015 11:33:32 +0800
Subject: [PATCH] Avoid duplicated udev match rules
On devices with read-only rootfs, e.g. mobile phones, nic device number
(wlan) may increase every time disabled and re-enabled. To be more
precisely, this happens only on devices when disabling a nic removes the
corresponding driver.
"/lib/udev/rules.d/75-persistent-net-generator.rules" checks whether
NAME attribute has been assigned to wlan device: if yes, skip all the
followed steps, or, call to "/lib/udev/write_net_rules" to generate a
persistent device name rule file. That persistent file should be created
under "/etc/udev/rules.d" and named "70-persistent-net.rules", so it
guarantees NAME attribute should be assigned if available before being
read. However, when rootfs was previously mounted as read-only, a file
"/run/udev/tmp-rules--70-persistent-net.rules" is created instead. This
temporary file is supposed to be moved back into "/etc/udev/rules.d" by
a systemd service udev-finish right after the system finishes start-up
chaos. Again, if rootfs is still mounted as read-only, this move will
certainly fail. One last important thing, /run/udev is _NOT_ included in
udev rules inclusion paths, so any rules written here will not be taken
into account when processing uevents.
So, when wlan0 is probed for the first time on a device with read-only
rootfs, udev creates "/run/udev/tmp-rules--70-persistent-net.rules" and
inserts one rule for it. When wlan0 is disabled and re-enabled, since
"/run/udev/tmp-rules--70-persistent-net.rules" is not taken into
account, its NAME attribute will not be set, and udev recognize it as a
new nic and tries to write another rule for it again. However, in this
time, "wlan0" has been taken in the previously written temporary rules
file, so "wlan1" is chosen instead, and an exactly the same matching
rule (except for NAME= part) is appended to
"/run/udev/tmp-rules--70-persistent-net.rules". When the device is
again disabled and re-enabled, "wlan2" will be assigned. And so on
This patch add an additional step to search if current match rule had
been previously written and reuse that interface name if available.
Signed-off-by: You-Sheng Yang
diff --git a/debian/extra/rule_generator.functions
b/debian/extra/rule_generator.functions
index 925193e..a676ff7 100644
--- a/debian/extra/rule_generator.functions
+++ b/debian/extra/rule_generator.functions
@@ -100,14 +100,14 @@ raw_find_next_available() {
}
# Find all rules matching a key (with action) and a pattern.
find_all_rules() {
local key="$1"
local linkre="$2"
local match="$3"
- local search='.*[[:space:],]'"$key"'"('"$linkre"')".*'
+ local search='.*'"$key"'"('"$linkre"')".*'
echo $(sed -n -r -e 's/^#.*//' -e "${match}s/${search}/\1/p" \
$RO_RULES_FILE \
$([ -e $RULES_FILE ] && echo $RULES_FILE) \
2>/dev/null)
}
diff --git a/debian/extra/write_net_rules b/debian/extra/write_net_rules
index 4379792..b05ed43 100644
--- a/debian/extra/write_net_rules
+++ b/debian/extra/write_net_rules
@@ -38,26 +38,26 @@ if [ -n "$UDEV_LOG" ]; then
fi
fi
RULES_FILE='/etc/udev/rules.d/70-persistent-net.rules'
. /lib/udev/rule_generator.functions
interface_name_taken() {
- loca
Bug#778500: iputils-ping: reconfiguring with setcap leaves the binary suid
tags 778500 + pending thanks On Sun, Feb 15, 2015 at 11:33:54PM +0100, Trek wrote: > I have installed iputils-ping without having setcap, so the /bin/ping* > binaries where suid root > > thanks to the warning message, I have installed libcap2-bin and then ran > dpkg-reconfigure on iputils-ping, but even if the setcap was done > correctly, the binaries remain setuid Thanks; I've fixed the postinst scripts for all the packages. The fix will be included in the -6 release, whenever that happens. noah signature.asc Description: Digital signature
Bug#780721: iputils: Please raise libcap2-bin from Recommends to Depends
On Wed, Mar 18, 2015 at 12:12:48PM +0100, John Paul Adrian Glaubitz wrote: > The new version of iputils in Jessie uses capabilities instead of set-uid > to gain the necessary priviliges to send ICMP requests. While this is a > great improvement with regards to security, it currently may lead to > rendering the ping and arping commands unusable for non-root users. iputils-ping, as priority "important", cannot declare a dependency on libcap2-bin, which is priority "optional". Thus, the Recommends relationship. It is perfectly valid to run system with iputils-ping installed and setcap2-bin not installed, with no loss of functionality. The iputils-ping postinst script takes care to handle the case where setcap is either not available or not functional (due e.g. to running on a filesystem that doesn't support capabilities. In such a case, it falls back to setting the setuid bit on the binary, which allows non-root users to run the program. The code in question: if command -v setcap > /dev/null; then if setcap cap_net_raw+ep /bin/ping cap_net_raw+ep /bin/ping6; then echo "Setcap worked! Ping(6) is not suid!" else echo "Setcap failed on /bin/ping, falling back to setuid" >&2 If this isn't working for you, you'll need to send some more details about your system. The output from the postinst script may be helpful (even though it shouldn't actually be there; see Bug #757433) noah signature.asc Description: Digital signature
Bug#780768: network-manager: build up of dhcp*.lease files in /var/lib/NetworkManager: have hundreds, expect 2
Package: network-manager Version: 0.9.10.0-6 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Trying to debug malfunctioning internet. * What exactly did you do (or not do) that was effective (or ineffective)? Tried to determine live lease by reading dhclient lease file. Found hundreds of files. * What was the outcome of this action? Had difficulty identifying active file due to large number of files with untypable names. * What outcome did you expect instead? 2 files: dhclient-eth1.lease and dhclient6-eth1.lease (the fact that's eth1 instead of eth0 is a minor bug in udev) *** End of the template - remove these template lines *** -- 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.bpo.3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages network-manager depends on: ii adduser3.113+nmu3 ii dbus 1.8.16-1 ii init-system-helpers1.22 ii isc-dhcp-client4.3.1-6 ii libc6 2.19-15 ii libdbus-1-31.8.16-1 ii libdbus-glib-1-2 0.102-1 ii libgcrypt201.6.2-4+b1 ii libglib2.0-0 2.42.1-1 ii libgnutls-deb0-28 3.3.8-5 ii libgudev-1.0-0 215-12 ii libmm-glib01.4.0-1 ii libndp01.4-2 ii libnewt0.520.52.17-1+b1 ii libnl-3-2003.2.24-2 ii libnl-genl-3-200 3.2.24-2 ii libnl-route-3-200 3.2.24-2 ii libnm-glib40.9.10.0-6 ii libnm-util20.9.10.0-6 ii libpam-systemd 215-12 ii libpolkit-gobject-1-0 0.105-8 ii libreadline6 6.3-8+b3 ii libsoup2.4-1 2.48.0-1 ii libsystemd0215-12 ii libteamdctl0 1.12-1 ii libuuid1 2.25.2-5 ii lsb-base 4.1+Debian13+nmu1 ii policykit-10.105-8 ii udev 215-12 ii wpasupplicant 2.3-1 Versions of packages network-manager recommends: ii crda3.13-1 ii dnsmasq-base2.72-3 ii iptables1.4.21-2+b1 ii iputils-arping 3:20121221-5+b2 ii modemmanager1.4.0-1 ii ppp 2.4.6-3 Versions of packages network-manager suggests: pn avahi-autoipd pn libteam-utils -- 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#779075: unblock: partman-target/94
Cyril Brulebois (2015-02-27): > Control: tag -1 moreinfo > > Since I'd like to perform some more tests with that one, tagging this > bug report moreinfo to make sure this version doesn't get accidentally > hinted into jessie too soon. No good news for the time being, see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761815#57 Mraw, KiBi. signature.asc Description: Digital signature
Bug#780767: linux-image-3.2.0-4-amd64: snd_hda crash on boot
Package: src:linux Version: 3.2.65-1+deb7u2 Severity: important Dear Maintainer, snd_hda crashes on boot sometimes. HDA codec fails to init othertimes. -- Package-specific info: ** Version: Linux version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.65-1+deb7u2 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 root=UUID=97e66d00-88d8-4f66-bf78-2b840d3acdac ro rootflags=data=writeback quiet ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. ** Kernel log: [6.241359] hda-codec: out of range cmd 0:0:9e5c:f09:0 [6.241379] HDMI status: Codec=0 Pin=40540 Presence_Detect=1 ELD_Valid=1 [6.241381] hda-codec: out of range cmd 0:0:9e5c:f2e:8 [6.241401] hda-codec: out of range cmd 0:0:9e5c:709:0 [6.241421] hda-codec: out of range cmd 0:0:9e5c:f09:0 [6.241482] HDMI status: Codec=0 Pin=0 Presence_Detect=0 ELD_Valid=0 [6.241537] HDMI status: Codec=0 Pin=1 Presence_Detect=0 ELD_Valid=0 [6.241571] hda_codec: cannot build controls for #0 (error -16) [6.241594] hda_codec: cannot revert codec [6.241969] snd_hda_intel: probe of :08:00.1 failed with error -16 [6.590980] Adding 1951740k swap on /dev/sda5. Priority:-1 extents:1 across:1951740k [6.601237] EXT4-fs (sda7): re-mounted. Opts: (null) [6.699464] EXT4-fs (sda7): re-mounted. Opts: errors=remount-ro [6.713445] loop: module loaded [7.104181] FAT-fs (sda1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! [7.214215] EXT4-fs (sda6): mounted filesystem with writeback data mode. Opts: data=writeback [7.399786] RPC: Registered named UNIX socket transport module. [7.399788] RPC: Registered udp transport module. [7.399789] RPC: Registered tcp transport module. [7.399790] RPC: Registered tcp NFSv4.1 backchannel transport module. [7.404891] FS-Cache: Loaded [7.412418] FS-Cache: Netfs 'nfs' registered for caching [7.416963] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). [7.749643] Bluetooth: Core ver 2.16 [7.749660] NET: Registered protocol family 31 [7.749662] Bluetooth: HCI device and connection manager initialized [7.749665] Bluetooth: HCI socket layer initialized [7.749667] Bluetooth: L2CAP socket layer initialized [7.749787] Bluetooth: SCO socket layer initialized [7.751775] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [7.751778] Bluetooth: BNEP filters: protocol multicast [7.756796] Bluetooth: RFCOMM TTY layer initialized [7.756800] Bluetooth: RFCOMM socket layer initialized [7.756802] Bluetooth: RFCOMM ver 1.11 [7.830163] lp: driver loaded but no devices found [7.843945] powernow-k8: Found 1 AMD FX(tm)-4300 Quad-Core Processor (4 cpu cores) (version 2.20.00) [7.843955] powernow-k8: Core Performance Boosting: on. [7.843964] [Firmware Bug]: powernow-k8: No compatible ACPI _PSS objects found. [7.843965] [Firmware Bug]: powernow-k8: Try again with latest BIOS. [7.846305] ppdev: user-space parallel port driver [7.864724] e1000e :03:00.0: irq 72 for MSI/MSI-X [7.968100] e1000e :03:00.0: irq 72 for MSI/MSI-X [7.969097] ADDRCONF(NETDEV_UP): eth0: link is not ready [8.055433] vgaarb: this pci device is not a vga device [8.055442] vgaarb: this pci device is not a vga device [8.055449] vgaarb: this pci device is not a vga device [8.055456] vgaarb: this pci device is not a vga device [8.055463] vgaarb: this pci device is not a vga device [8.055470] vgaarb: this pci device is not a vga device [8.055476] vgaarb: this pci device is not a vga device [8.055483] vgaarb: this pci device is not a vga device [8.055490] vgaarb: this pci device is not a vga device [8.055497] vgaarb: this pci device is not a vga device [8.055504] vgaarb: this pci device is not a vga device [8.055511] vgaarb: this pci device is not a vga device [8.055517] vgaarb: this pci device is not a vga device [8.055524] vgaarb: this pci device is not a vga device [8.055531] vgaarb: this pci device is not a vga device [8.055537] vgaarb: this pci device is not a vga device [8.055544] vgaarb: this pci device is not a vga device [8.01] vgaarb: this pci device is not a vga device [8.07] vgaarb: this pci device is not a vga device [8.055564] vgaarb: this pci device is not a vga device [8.055571] vgaarb: this pci device is not a vga device [8.055578] vgaarb: this pci device is not a vga device [8.055584] vgaarb: this pci device is not a vga device [8.055591] vgaarb: this pci device is not a vga device [8.055598] vgaarb: this pci device is not a vga device [8.055604] vgaarb: this pci device is not a vga device [8.055611] vgaarb: this pci device is not a vga device [8.055618] vgaarb: this pci device is not a vga device [8.055632] vgaarb: this p
Bug#780766: ITP: memtailor -- C++ library of special purpose memory allocators
Package: wnpp Severity: wishlist Owner: Doug Torrance * Package name: memtailor Version : 1.0 Upstream Author : Bjarke Hammersholt Roune * URL : https://github.com/broune/memtailor * License : BSD-3-clause Programming Lang: C++ Description : C++ library of special purpose memory allocators Memtailor is a C++ library of special purpose memory allocators. It currently offers an arena allocator and a memory pool. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780765: syslinux fixes for Chromebooks
Package: syslinux
Version: 3:6.03+dfsg-5
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu vivid ubuntu-patch
Hi Daniel,
In Ubuntu, my attention was recently called to a problem with syslinux 6.03
not booting correctly on Chromebooks. To fix this problem, I've applied two
patches to the Ubuntu package taken from the upstream mailing list. You may
find it beneficial to apply these patches to the Debian package as well.
The changelog for the upload to Ubuntu is:
* debian/patches/relocatable-kernel-loads.patch: load_linux: relocate
protected-mode code as intended. Thanks to Scot Doyle
. Closes LP: #1429323.
* debian/patches/load_linux-correct-type.patch: load_linux: correct a
type. Thanks to Scot Doyle .
Thanks for considering the patch.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru syslinux-6.03+dfsg/debian/changelog syslinux-6.03+dfsg/debian/changelog
diff -Nru syslinux-6.03+dfsg/debian/patches/load_linux-correct-type.patch syslinux-6.03+dfsg/debian/patches/load_linux-correct-type.patch
--- syslinux-6.03+dfsg/debian/patches/load_linux-correct-type.patch 1969-12-31 16:00:00.0 -0800
+++ syslinux-6.03+dfsg/debian/patches/load_linux-correct-type.patch 2015-03-18 16:11:07.0 -0700
@@ -0,0 +1,29 @@
+Author: Scot Doyle
+Description: load_linux: correct a type
+ Correct base's type to match its initialization from prot_mode_base and
+ passage to syslinux_memmap_find(). Tested with extlinux.
+Signed-off-by: Scot Doyle
+Forwarded: http://www.syslinux.org/archives/2015-February/023179.html
+
+---
+ com32/lib/syslinux/load_linux.c | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/com32/lib/syslinux/load_linux.c b/com32/lib/syslinux/load_linux.c
+index 06ae2a9..ac73729 100644
+--- a/com32/lib/syslinux/load_linux.c
b/com32/lib/syslinux/load_linux.c
+@@ -155,8 +155,8 @@ int bios_boot_linux(void *kernel_buf, size_t kernel_size,
+ char *cmdline)
+ {
+ struct linux_header hdr, *whdr;
+-size_t real_mode_size, prot_mode_size, base;
+-addr_t real_mode_base, prot_mode_base, prot_mode_max;
++size_t real_mode_size, prot_mode_size;
++addr_t real_mode_base, prot_mode_base, prot_mode_max, base;
+ addr_t irf_size;
+ size_t cmdline_size, cmdline_offset;
+ struct setup_data *sdp;
+--
+2.3.0-rc2
+
diff -Nru syslinux-6.03+dfsg/debian/patches/relocatable-kernel-loads.patch syslinux-6.03+dfsg/debian/patches/relocatable-kernel-loads.patch
--- syslinux-6.03+dfsg/debian/patches/relocatable-kernel-loads.patch 1969-12-31 16:00:00.0 -0800
+++ syslinux-6.03+dfsg/debian/patches/relocatable-kernel-loads.patch 2015-03-18 16:10:47.0 -0700
@@ -0,0 +1,38 @@
+Author: Scot Doyle
+Description: load_linux: relocate protected-mode code as intended
+ If the kernel is relocatable and the protected mode code will not fit
+ in the initially determined location, that code will be moved to the
+ next available location. However, beginning with commit 8f470e7b, the
+ code is moved to the initially determined location instead of the next
+ available location because prot_mode_base is no longer updated to the
+ correct location. Since whdr->code32_start is updated, it is pointing
+ to the wrong execution start location, random code is executed and
+ the machine is rebooted.
+ .
+ Restore the old behavior by assigning prot_mode_base the value of
+ base. Tested on a machine that exposed this behavior.
+Signed-off-by: Scot Doyle
+Bug-Ubuntu: https://bugs.launchpad.net/bugs/1429323
+Forwarded: http://www.syslinux.org/archives/2015-February/023209.html
+
+---
+This patch may be applied in addition to "load_linux: correct a type"
+
+ com32/lib/syslinux/load_linux.c | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/com32/lib/syslinux/load_linux.c b/com32/lib/syslinux/load_linux.c
+index 06ae2a9..5cecef4 100644
+--- a/com32/lib/syslinux/load_linux.c
b/com32/lib/syslinux/load_linux.c
+@@ -323,6 +323,7 @@ int bios_boot_linux(void *kernel_buf, size_t kernel_size,
+ }
+
+ whdr->code32_start += base - prot_mode_base;
++prot_mode_base = base;
+
+ /* Real mode code */
+ if (syslinux_memmap_find(amap, &real_mode_base,
+--
+2.3.0-rc2
+
diff -Nru syslinux-6.03+dfsg/debian/patches/series syslinux-6.03+dfsg/debian/patches/series
--- syslinux-6.03+dfsg/debian/patches/series 2014-12-07 11:51:56.0 -0800
+++ syslinux-6.03+dfsg/debian/patches/series 2015-03-18 16:09:21.0 -0700
@@ -2,3 +2,5 @@
0002-gfxboot-menu-label.patch
0003-extlinux-manpage.patch
0004-gnu-efi-git.patch
+relocatable-kernel-loads.patch
+load_linux-correct-type.patch
Bug#780241: [NETWORKING #LVG-179-41238]: Re: mirror submission for debian.mirror.digitalpacific.com.au
Hi Donald, We was syncing the archive from mirror.aarnet.edu.au -- looking at their trace directory, it's all there too: http://mirror.aarnet.edu.au/pub/debian/project/trace/ The only reason why we sync from there is as because it's local to Sydney, AU.. where as the official AU mirror is in Western Australia (3,900km away!). Either way, I've updated the rsync target to ftp.au.debian.org > The archive should be listed as /debian/. No problems. The directory has been renamed from /debian-archive/ to /debian/ http://debian.mirror.digitalpacific.com.au/debian/ rsyncd.conf has been updated too: rsync://mirror.digitalpacific.com.au/debian/ Please let us know if you have any other questions. Thanks! Regards, Matthew. Ticket Details Ticket ID: LVG-179-41238 Department: Networking Type: Issue Status: Open Priority: Medium Helpdesk: https://www.digitalpacific.com.au/internal-esupport/index.php?/default_import -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780764: php5-curl: Cookie header not send on request
Package: php5-curl Version: 5.4.38-0+deb7u1 Severity: important Dear PHP Maintainers, When setting a curl CURLOPT_COOKIEFILE and CURLOPT_COOKIEJAR the Cookie header is not set after receive a Set-Cookie from the server. This error was not present in wheezy 5.4.36-0+deb7u3 and is not present on jessie 5.6.6+dfsg-2. This error is present on 5.4.36-0+deb7u3 after a wheezy-security update. Downgrading version 5.4.38-0+deb7u1 to 5.4.36-0+deb7u3 solves the problem for me. Example (example.com is not the real host): > POST /BuzonDigital/Acceso/SignUp HTTP/1.1 User-Agent: Mozilla/5.0 (X11; Linux x86_64; en-us) Gecko/20100101 Curl/20140110 Host: www.example.com Accept: */* Content-Length: 43 Content-Type: application/x-www-form-urlencoded < HTTP/1.1 302 Found < Cache-Control: private < Content-Type: text/html; charset=utf-8 < Location: /BuzonDigital/Home/Bienvenido < Server: Microsoft-IIS/7.5 < X-AspNetMvc-Version: 3.0 < X-AspNet-Version: 4.0.30319 < Set-Cookie: .ASPXAUTH=8F68B591851568FFB64A3E051DDAD33619338A85677CE83CDAA2355B570E45BE2FF4BDCF4F17121E9818EE348113DA325F9F5B4FC9996A8BCA53D36CD44B0524F84832A8B5109E4263A57D48028050B8F723E7A79BE9C0BCC2684ED28A21FBB757E8F6AD7150589299E081787F; path=/; HttpOnly < X-Powered-By: ASP.NET < Date: Wed, 18 Mar 2015 22:17:36 GMT < Content-Length: 146 < > GET /BuzonDigital/Home/Bienvenido HTTP/1.1 User-Agent: Mozilla/5.0 (X11; Linux x86_64; en-us) Gecko/20100101 Curl/20140110 Host: www.example.com Accept: */* Referer: https://www.example.com/BuzonDigital/Acceso/SignUp < HTTP/1.1 302 Found < ... The Cookie header was not sent on GET request -- System Information: Debian Release: 7.8 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=es_MX.UTF-8, LC_CTYPE=es_MX.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages php5-curl depends on: ii dpkg 1.16.15 ii libapache2-mod-php5 [phpapi-20100525] 5.4.38-0+deb7u1 ii libc6 2.13-38+deb7u8 ii libcurl3 7.26.0-1+wheezy12 ii php5-cli [phpapi-20100525] 5.4.38-0+deb7u1 ii php5-common5.4.38-0+deb7u1 ii ucf3.0025+nmu3 php5-curl recommends no packages. php5-curl 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#778874: terminator: Moving between terminals buggy
forwarded 778874 https://bugs.launchpad.net/bugs/1433810
thanks
Hello Martin,
Thanks for it, I'll check it.
Kind regards,
--
Julián Moreno Patiño
Debian Developer
.''`. Debian GNU/{Linux,KfreeBSD}
: :' : Free Operating Systems
`. `' http://debian.org/
`- GPG Fingerprint:
C2C8 904E 314C D8FA 041D 9B00 D5FD FC15 6168 BF60
Registered GNU Linux User ID 488513
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#773097: mate-notification-daemon: this is still an issue with the latest 1.8.2-1 re; eased to experimental.
at bottom :- On 3/18/15, Alessandro Barbieri wrote: > I commented exec in kde.notify.service because knotif was running > disabled kwin and rebooted > neiter knotify4 nor mate-notification are running > > and i can't run it > > /usr/lib/mate-notification-daemon/mate-notification-daemon > > ** (mate-notification-daemon:10327): WARNING **: Failed to acquire name > org.freedesktop.Notifications > > > ps aux | grep notif > root39 0.0 0.0 0 0 ?S19:02 0:00 > [fsnotify_mark] > ale 2969 0.0 0.4 274456 16392 ?Sl 19:04 0:00 > /usr/lib/mate-panel/notification-area-applet > ale 9078 0.0 0.0 12748 2172 pts/0S+ 19:09 0:00 grep > --color=auto notif > > -- > sip:alebar...@ekiga.net I dunno if you are supposed to run it like that, because I get the same error if I try it. I ran mate-notification properties in the CLI and asked it to change positions and it did. Upto the maintainer to guide us as to what is the correct way. -- 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#750837: ITP: moarvm -- virtual machine for Rakudo Perl 6 and NQP
gregor herrmann writes: > Yay, great! > > Looks like the ITP bug can be tagged pending :) The new 2015.03 is out, this will permit to drop the patch ;-) Regards. -- Daniel Dehennin Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF Fingerprint: 3E69 014E 5C23 50E8 9ED6 2AAD CC1E 9E5B 7A6F E2DF signature.asc Description: PGP signature
Bug#780719: unblock: flightgear/3.0.0-5
On 18/03/15 21:32, Markus Wanner wrote:
On 03/18/2015 09:09 PM, Adam D. Barratt wrote:
++write_allowed_paths.push_back("/tmp/*.xml");
Is that really intended? (Both the hardcoding of /tmp/ rather than using
something respecting TMPDIR and being allowed to write any ".xml"
there.)
It certainly matches Nasal/IOrules in flightgear-data,
Yes, the allowed-paths list is intentionally identical to the
(post-#780716-fix) Nasal/IOrules: the purpose of this patch is to move
the checking process to somewhere scripts can't disable.
I'm not quite sure what Nasal scripts need to write
temporary XML files.
I'm not aware of any that do, but haven't specifically looked.
Is untrusted scripts being able to write (not read) /tmp/*.xml a
security or other RC bug (which would require a new upload of flightgear
_and_ flightgear-data with the obvious fixes), or just not a good idea?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#429606: must ~/.mailcap be a plain file with only one link?
On Tue, Mar 17, 2015 at 05:03:27PM +0100, Denis Briand wrote: > tags 429606 moreinfo > severity 429606 minor > thanks > > > Hello, > Is this issue fixed on 2.8.9dev4 version? > regards Well - note my response pointing out that the issue with symbolic links was by design. There was no followup from the OP pursuing the question of a hardlink. (Generally, if there's some followup explaining why they wanted a change, I'll either explain why not, or make the change, but lacking a dialogue, there's little to go on). The feature in question had been there more than ten years: http://lynx.isc.org/current/CHANGES.html#v2.8.1dev.20 -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net signature.asc Description: Digital signature
Bug#746967: buildd.debian.org: d-i daily builds happen with unsigned code from alioth
On 2014-12-28 13:34, Philipp Kern wrote: > On Thu, Sep 11, 2014 at 10:49:06PM +0200, Aurelien Jarno wrote: > > If we choose this solution, here is a quick and dirty patch against > > di-autobuild to do that. It's basically changing the hardcoded paths > > and call to schroot. There is probably more fixes/cleanup to do, but > > it's just a proof of concept to show this solution works without > > additional privilege on the porterboxes. Note that I haven't tried the > > upload part, but I guess it's just a matter of having the right packages > > installed (if not already the case). > > > > We probably want to have a dedicated d-i account for that on the > > porterbox. Also we have only one amd64/i386 porterbox, and the current > > script doesn't support that, but that should be easy to test. > > > > If this solution is chosen, I'll be happy to continue working on this > > script as time permits. > > I'm ok with this approach for the time being. Obviously building on real > infrastructure the way other stuff is built would be even better. (For With the help of Hector Oron, we have been able to setup this on the porterbox of 4 architectures: arm64, armel, armhf and mips. This has been done by allowing the d-i role account on the porterboxes. As a nice side effect, this mean that d-i people can now do/fix the setup themselves without having to go through the buildd team. The code used is available in the porterbox branch of the di-autobuild git. Note that the chroots on the porterbox are created in a very similar way than on the newer buildds (it's even done by the same script IIRC), so the problems should be similar. For example both were affected by bug#775136. > instance binNMUing the unstable d-i into experimental every day, or > similar.) BinNMUing the unstable d-i into experimental actually doesn't really work as it doesn't take into account the changes done on the debian-installer package itself. It is not uploaded that often, so it's important to have daily-builds to test it. Cheers, Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net signature.asc Description: Digital signature
Bug#750863: Please include package contents information
On Wed, Mar 18, 2015 at 10:28:46PM +0100, Lucas Nussbaum wrote: > On 18/03/15 at 13:21 -0700, j...@joshtriplett.org wrote: > > On Wed, Mar 18, 2015 at 08:14:20PM +0100, Ralf Treinen wrote: > > > On Wed, Mar 18, 2015 at 10:59:35AM -0700, j...@joshtriplett.org wrote: > > > > And I'd like to search for things like filename conflicts and compare > > > > them to package metadata; for instance, do packages that ship the same > > > > filename conflict or not, and do the versions of the conflict match the > > > > versions that ship the same file? (That won't be perfect, since it > > > > can't take diversions into account, which are unfortunately still > > > > programmatic in maintainer scripts rather than being declarative.) > > > > > > these could be found by inspecting the Contents file - this is how it > > > is done in [1]. This is today integrated in piuparts, code to find > > > packages sharing a path name can be found in [2]. > > > > > > [1] https://qa.debian.org/dose/file-overwrites.html > > > [2] https://alioth.debian.org/scm/browser.php?group_id=30965 > > > > Sure, though that's not correlated by version and package metadata the > > way UDD is. But yeah, that use case is much lower priority for me than > > the metadata issue (user/group/mode). > > Wouldn't this one be better solved as a lintian check? The conflicts item? Lintian doesn't always have multiple packages around for a simultaneous check. The user/group/mode item? No, I'm not looking to write a specific lintian check there; I'm trying to evaluate usage of specific users/groups/modes as part of trying to find better ways to handle them. - Josh Triplett -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780733: fai-client: SSH login on installing client not possible as devpts is not mounted
On 03/18/2015 10:57 PM, Thomas Lange wrote: > Yes, you are right. The code is wrong. I will fix this. Thank you! > But this is not an important bug, only a normal one. Sure, feel free to downgrade it. I usually just want to keep from people shooting themselves into the foot which is why I thought it would be a good idea to have it fixed with a slightly higher priority. > And btw, do not use live-boot and initramfs-tools any more, FAI now > uses dracut as default. Well, Debian currently hasn't switched to Dracut as the default initial ramdisk filesystem yet and therefore we haven't done any real world testing with Dracut either. > live-boot support will be removed in the next version of FAI, even for fai-cd. I expect Debian to be switching to Dracut for Stretch and that will be when we're going to switch to Dracut for the installation systems as well. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#761815: fixed in partman-target 94
Hi, Christian Perrier (2015-01-26): > partman-target (94) unstable; urgency=medium > . >[ Steve McIntyre ] >* Don't add entries for random USB media to /etc/fstab, they're not > useful. Closes: #761815 I'd like to know how that was tested. Using libvirt, importing mini.iso as a USB hard drive (appearing as /dev/sda during installation), installing on to an IDE disc (appearing as /dev/sdb), leads to the use of partman-target 94 per syslog, and yet /etc/fstab ends up containing a /media/usb0 entry: | # /etc/fstab: static file system information. | # | # Use 'blkid' to print the universally unique identifier for a | # device; this may be used with UUID= as a more robust way to name devices | # that works even if disks are added and removed. See fstab(5). | # | # | # / was on /dev/sdb1 during installation | UUID=a38aa670-fb4c-4482-8af1-42f34b41ebdb / ext4 errors=remount-ro 0 1 | # swap was on /dev/sdb5 during installation | UUID=cd9c4a52-91c4-4b44-8d34-c880357974b9 noneswapsw 0 0 | /dev/sda1 /media/usb0 autorw,user,noauto 0 0 Looking a bit more into it, I tried marking said device as removable in libvirt, but that didn't seem to make any difference. It might very well be that I've managed to make a boo-boo while trying to configure stuff, or that libvirt's support for such things is buggy; but I haven't managed to trick either kvm/qemu or virtualbox into booting from removable USB. Any hints? Mraw, KiBi. signature.asc Description: Digital signature
Bug#780733: fai-client: SSH login on installing client not possible as devpts is not mounted
> On Wed, 18 Mar 2015 22:45:16 +0100, John Paul Adrian Glaubitz > said: > In any case, I'd still argue it's a bug simply because the condition for > the mount command for devpts is flawed. Why should devpts be mounted if > it's already mounted? That doesn't really make any sense to me. Yes, you are right. The code is wrong. I will fix this. But this is not an important bug, only a normal one. And btw, do not use live-boot and initramfs-tools any more, FAI now uses dracut as default. live-boot support will be removed in the next version of FAI, even for fai-cd. -- regards Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780763: nut install won't complete because of service start check
Package: nut Version: 2.7.2-3 Severity: important Dear Maintainer, When installing nut, nut-server, nut-ipmi, nut-snmp I get the following errors. The problem seems to be that there is an install time check to see if the nut services start, but the servies are set to not start by default, until the user has a chance to set it up and choose what mode it will run in. That check should soft fail and allow the install to continue. Error messages: root@egdb1:/etc/network# apt-get install nut Reading package lists... Done Building dependency tree Reading state information... Done nut is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 4 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up nut-server (2.7.2-3) ... A dependency job for nut-server.service failed. See 'journalctl -xn' for details. invoke-rc.d: initscript nut-server, action "start" failed. dpkg: error processing package nut-server (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of nut: nut depends on nut-server; however: Package nut-server is not configured yet. dpkg: error processing package nut (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of nut-ipmi: nut-ipmi depends on nut (>= 1.4.1-pre1); however: Package nut is not configured yet. dpkg: error processing package nut-ipmi (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of nut-snmp: nut-snmp depends on nut (>= 1.4.1-pre1); however: Package nut is not configured yet. dpkg: error processing package nut-snmp (--configure): dependency problems - leaving unconfigured E: Sub-process /usr/bin/dpkg returned an error code (1) journalctl -xn shows Mar 18 16:20:37 egdb1 upsdrvctl[21555]: Error: no UPS definitions found in ups.conf Mar 18 16:20:37 egdb1 upsdrvctl[21555]: Network UPS Tools - UPS driver controller 2.7.2 Mar 18 16:20:37 egdb1 systemd[1]: nut-driver.service: control process exited, code=exited status=1 Mar 18 16:20:37 egdb1 systemd[1]: Failed to start Network UPS Tools - power device driver controller. -- Subject: Unit nut-driver.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit nut-driver.service has failed. -- -- The result is failed. Mar 18 16:20:37 egdb1 systemd[1]: Dependency failed for Network UPS Tools - power devices information server. -- Subject: Unit nut-server.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit nut-server.service has failed. -- -- The result is dependency. Mar 18 16:20:37 egdb1 systemd[1]: Unit nut-driver.service entered failed state. I tried to do some basic config, but it seems like it has to be fully configured to finish the install which I'm not ready to do yet. -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/24 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages nut depends on: ii nut-client 2.7.2-3 ih nut-server 2.7.2-3 nut recommends no packages. nut 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#780733: fai-client: SSH login on installing client not possible as devpts is not mounted
On 03/18/2015 10:42 PM, Thomas Lange wrote: > root@xfcehost:~# mount|grep pts > devpts on /dev/pts type devpts > (rw,nosuid,noexec,relatime,mode=600,ptmxmode=000) > devpts on /target/dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000) This is how it worked on Wheezy, yes. > Are you using dracut? And are you installing sysvinit-core into the > nfsroot (which is th default)? No, we're still on initramfs. Init system is still sysvinit for the NFSROOT, not systemd. In any case, I'd still argue it's a bug simply because the condition for the mount command for devpts is flawed. Why should devpts be mounted if it's already mounted? That doesn't really make any sense to me. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780733: fai-client: SSH login on installing client not possible as devpts is not mounted
> On Wed, 18 Mar 2015 17:07:27 +0100, John Paul Adrian Glaubitz > said: > Logging into the system while it is being installed. I cannot confirm this bug. Using jessie inside the NFSROOT and fai 4.3.2 and dracut 040+1-1 and doing a PXE boot of the install client I managed to log in via ssh during installation. root@xfcehost:~# mount|grep pts devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,mode=600,ptmxmode=000) devpts on /target/dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000) Are you using dracut? And are you installing sysvinit-core into the nfsroot (which is th default)? -- regards Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780719: unblock: flightgear/3.0.0-5
On 03/18/2015 09:09 PM, Adam D. Barratt wrote:
> Well, not really. A debdiff from which you'd filtered the patch was
> attached, as was the patch. I'm not convinced that actually provided any
> benefit over simply providing the unfiltered debdiff.
I personally always have trouble reading nested diffs ('+-' vs '-+',
anybody?). So this was intended to be helpful. Apologies, if it's not.
Granted, an entire file added is not quite as hard to read (i.e. no '-+'
possible).
> ++write_allowed_paths.push_back("/tmp/*.xml");
>
> Is that really intended? (Both the hardcoding of /tmp/ rather than using
> something respecting TMPDIR and being allowed to write any ".xml"
> there.)
It certainly matches Nasal/IOrules in flightgear-data, so it seems well
intended, yes. And as advertized, it's clearly more restrictive than it
used to be.
According to the comment in that same file, only $FG_HOME and $FG_ROOT
are known variables to be replaced, there. Adding $TMPDIR might be a
bigger effort, but I'm not quite sure what Nasal scripts need to write
temporary XML files.
Rebecca, care to comment?
Regards
Markus Wanner
signature.asc
Description: OpenPGP digital signature
Bug#780762: unblock: debsums/2.0.53
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package debsums/2.0.53
Release 2.0.53 of debsums fixes https://bugs.debian.org/773136 which
has been upped to RC recently and Niels has acked that I should go on
with a fix of #773136 for Jessie.
Compared to my previous NMUs of debsums, this release also contains
the takeover of debsums by the Debian Perl Group with me added as
additional Uploader. For the discussions about moving to group
maintenance, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744398#722 and
https://lists.debian.org/debian-perl/2015/01/msg00010.html.
I initially planned this switch with the first post-Jessie upload, but
since we now do another upload target for Jessie, I included the
takeover in this upload, too. This makes the diff a little bit larger:
diff -Nru debsums-2.0.52+nmu3/debian/changelog debsums-2.0.53/debian/changelog
--- debsums-2.0.52+nmu3/debian/changelog2015-01-25 08:59:28.0
+0100
+++ debsums-2.0.53/debian/changelog 2015-03-18 21:44:45.0 +0100
@@ -1,3 +1,19 @@
+debsums (2.0.53) unstable; urgency=medium
+
+ * Take package under maintenance of the Debian Perl Group
++ Move Maintainer to Uploaders
++ Set Maintainer to the Debian Perl Group
++ Update Vcs-* header to point to pkg-perl git repository
++ See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744398#722 and
+ https://lists.debian.org/debian-perl/2015/01/msg00010.html for
+ discussions about moving to group maintenance.
+ * Add myself as Uploader.
+ * Canonicalize Vcs-* headers.
+ * Apply patch by Vladimir N. Solovyov to also report modified files of
+arch-qualified (multiarch) packages. (Closes: #773136)
+
+ -- Axel Beckert Wed, 18 Mar 2015 20:35:02 +0100
+
debsums (2.0.52+nmu3) unstable; urgency=medium
* Non-maintainer upload
diff -Nru debsums-2.0.52+nmu3/debian/control debsums-2.0.53/debian/control
--- debsums-2.0.52+nmu3/debian/control 2015-01-25 08:58:22.0 +0100
+++ debsums-2.0.53/debian/control 2015-03-18 21:44:45.0 +0100
@@ -1,12 +1,12 @@
Source: debsums
Section: admin
Priority: optional
-Maintainer: Ryan Niebur
-Uploaders: Anders Kaseorg
+Maintainer: Debian Perl Group
+Uploaders: Ryan Niebur , Anders Kaseorg ,
Axel Beckert
Build-Depends: debhelper (>= 8), po-debconf, po4a
Standards-Version: 3.9.3
-Vcs-Git: git://git.debian.org/git/collab-maint/debsums.git
-Vcs-Browser: http://git.debian.org/?p=collab-maint/debsums.git;a=summary
+Vcs-Git: git://anonscm.debian.org/pkg-perl/packages/debsums.git
+Vcs-Browser: https://anonscm.debian.org/cgit/pkg-perl/packages/debsums.git
Package: debsums
Architecture: all
diff -Nru debsums-2.0.52+nmu3/debsums debsums-2.0.53/debsums
--- debsums-2.0.52+nmu3/debsums 2015-01-25 08:59:28.0 +0100
+++ debsums-2.0.53/debsums 2015-03-18 21:44:45.0 +0100
@@ -462,7 +462,7 @@
return 0;
}
- my $correct_package = `dpkg-query "--admindir=$DPKG" -S "/$path" | awk
-F: '{print \$1}'`;
+ my $correct_package = `dpkg-query "--admindir=$DPKG" -S "/$path" | awk
-F': ' '{print \$1}'`;
chomp($correct_package);
if ($pack ne $correct_package) {
#print "$pack != $correct_package\n";
So please
unblock debsums/2.0.53
P.S.: Thanks to Niels for his help with stripping down the debdiff to
what's necessary to properly include the Maintainer switch.
-- System Information:
Debian Release: 8.0
APT prefers unstable
APT policy: (990, 'unstable'), (600, 'testing'), (110, 'experimental'), (109,
'buildd-unstable'), (109, 'buildd-experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.19.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.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#750863: Please include package contents information
On 18/03/15 at 13:21 -0700, j...@joshtriplett.org wrote: > On Wed, Mar 18, 2015 at 08:14:20PM +0100, Ralf Treinen wrote: > > On Wed, Mar 18, 2015 at 10:59:35AM -0700, j...@joshtriplett.org wrote: > > > And I'd like to search for things like filename conflicts and compare > > > them to package metadata; for instance, do packages that ship the same > > > filename conflict or not, and do the versions of the conflict match the > > > versions that ship the same file? (That won't be perfect, since it > > > can't take diversions into account, which are unfortunately still > > > programmatic in maintainer scripts rather than being declarative.) > > > > these could be found by inspecting the Contents file - this is how it > > is done in [1]. This is today integrated in piuparts, code to find > > packages sharing a path name can be found in [2]. > > > > [1] https://qa.debian.org/dose/file-overwrites.html > > [2] https://alioth.debian.org/scm/browser.php?group_id=30965 > > Sure, though that's not correlated by version and package metadata the > way UDD is. But yeah, that use case is much lower priority for me than > the metadata issue (user/group/mode). Wouldn't this one be better solved as a lintian check? Lucas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780102: libjbcrypt-java: CVE-2015-0886
On Mon, Mar 09, 2015 at 03:00:27PM +0100, Emmanuel Bourg wrote: > Thank you for the report Moritz. > > According to the Bugzilla report the issue happens when BCrypt.gensalt() > is called with the value 31. jenkins is the only package using this > library and it calls this method with no parameter [1], the default > value being 10 [2]. > > So I don't think this issue is critical for Jessie. Ok. It probably fairly unlikely that external Java applications use the shipped libjbcrypt-java package. 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#780748: Invalid URL
Hi, I just had to update the upstream fix as I accidentally made a mistake which means it didn't compile. Please ignore the "raw patch" link above, and instead use the codereview link[1] which links to the newest version. Sorry for the inconveniences! [1] https://codereview.qt-project.org/#/c/108936/ -- http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc I love long mails! | http://email.is-not-s.ms/ pgp54mR4x1OY3.pgp Description: PGP signature
Bug#780680: libpam-modules: pam_userdb.so depends on a library in /usr
Control: reassign -1 libdb5.3
On Wed, Mar 18, 2015 at 08:58:50PM +0100, Ansgar Burchardt wrote:
> severity 780680 normal
> thanks
> Adam Heath writes:
> > A library in /lib shouldn't depend on a library in /usr/lib. However,
> > pam_userdb.so has such an issue.
> Arguably pam_userdb.so is not a library, but a plugin. So I don't think
> this is a release critical bug or even a real bug at all, but I'll leave
> the definite decision to the pam maintainers.
> For reference, there are lots of other PAM and NSS modules doing the
> same: libpam-{pgsql,mysql,ldap} and libnss-{pgsql2,mysql-bg,ldap} come
> to mind, but probably many other libpam-* and libnss-* packages are
> doing the same.
The bug, to the extent that there is one, is that the depended-on library is
in /usr instead of in /lib. It's not a bug for pam_userdb to provide this
functionality; it's also not a bug for this module to be shipped in /lib,
as it is a plugin for a library that is (and must be) also in /lib.
But this is not a high-priority bug; for jessie forward, /usr will need to
be mounted from the initramfs, and we should stop worrying about the
root/usr split.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: Digital signature
Bug#726062: update
Hello, An update on this bug to add due support to the arduino package: the arduino sam support relies on CMSIS, which is not DFSG free (you are only allowed to use it with ARM development) SAM support will end up in non-free as a package arduino-hardware-sam, and will probably not land until after Jessie is released. I'm working on 1.6.0, but have also asked for an updated license from arduino: https://github.com/arduino/Arduino/pull/2703 ~Scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#761963: security-tracker: consolidate vulnerable/fixed per release in overviews
On Wed, Sep 17, 2014 at 09:10:39AM +, Thijs Kinkhorst wrote:
> Package: security-tracker
> Severity: wishlist
>
> Hi,
>
> In the overview per-package, the tracker currently shows for each CVE
> name about seven columns: squeeze, squeeze-security, squeeze-lts, wheezy,
> wheezy-security, jessie, sid.
>
> I think for the overviews it would be preferable if the table just shows the
> status for each release ('squeeze', 'wheezy' (or maybe even
> 'oldstable','stable')) etc overall, that is, 'wheezy' will show fixed if an
> issue is fixed in wheezy-security. I believe that this represents best how
> people think about an issue being fixed.
>
> For an individual CVE page, I think the same would go for the overview on the
> top (this currently shows only "Debian/stable" for all wheezy suites but
> confusingly shows "vulnerable" if it's fixed in wheezy-security).
>
> The detailed info about the exact suites can remain to be found in the table
> under "Vulnerable and fixed packages" on the CVE page.
Full ack. This is especially bad for Squeeze, which no longer has point
update, so e.g. https://security-tracker.debian.org/tracker/source-package/php5
shows many issues which are marked as open because they "only fixed in
squeeze-lts".
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#743474: And another new upstream version is out...
Hello again, a few days ago upstream released 3.8.0. Any chance to package it? I even consider to help maintain it in the future if some mentoring is provided. Regards, Jens -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780706: arduino: Request for Arduino IDE 1.6.1 package
On Wed, Mar 18, 2015 at 1:23 AM, Martin Stoufer wrote: > I am having a miserable time getting the current 1.5.2 unstable release to > patch properly > for 1.6.0 release on my Raspberry Pi (jessie/main). Is it all possible to get > this in the pipeline (and even skip 1.5.2 release?) Hello - the plan is to have 1.6+ after jessie and it is already to go. However, we need updated licensing info from arduino: https://github.com/arduino/Arduino/pull/2703 Also, the arduino-mk tool will have to be updated to the 1.5+ branch, which that project has not done yet. In the meantime, 1.5.6rc2 is packaged in experimental: https://packages.debian.org/experimental/arduino Hope that help ~Scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780761: debbindiff fails noisily when run over perversely recursive input files
Package: debbindiff Version: 9 Severity: wishlist I'm attaching two ugly fake little .debs that look roughly the same from the outside. they each ship only one file in data.tar.gz, which is r.zip. in both cases, r.zip is a nasty file that unpacks to show another file, r.zip, which happens to be identical to the original file [0]. however, the r.zip files in each .deb differ from each other a little bit. the result is a huge python backtrace that ultimately ends with: File "/usr/lib/python2.7/dist-packages/debbindiff/comparators/zip.py", line 61, in compare_zip_files source=name)) File "/usr/lib/python2.7/dist-packages/debbindiff/comparators/__init__.py", line 119, in compare_files return comparator(path1, path2, source) File "/usr/lib/python2.7/dist-packages/debbindiff/comparators/utils.py", line 55, in with_fallback inside_differences = original_function(path1, path2, source) File "/usr/lib/python2.7/dist-packages/debbindiff/comparators/zip.py", line 43, in compare_zip_files with ZipFile(path1, 'r') as zip1: File "/usr/lib/python2.7/zipfile.py", line 770, in __init__ self._RealGetContents() File "/usr/lib/python2.7/zipfile.py", line 844, in _RealGetContents x = ZipInfo(filename) RuntimeError: maximum recursion depth exceeded Perhaps leaving debbindiff to the mercies of the python recursion limits is the way to go here -- at least it's a relatively quick failure. But it's conceivable that we want to do something marginally cleaner. Some options might be: 0) limit the unpacking recursion ourselves (mayve 20 levels?), and having a graceful termination suggesting that the packages are likely to be bogus? 1) caching the digest of every archive unpacked on the stack, and bailing gracefully when we find another internal archive with a digest already unpacked. (maybe this doesn't need to be an error for debbindiff -- could we just stop the nested recursion there and treat the archive as a non-archive?) or we could do both of the above, i guess. I'm open to other suggestions. --dkg [0] hat tip to http://research.swtch.com/zip for the construction -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing'), (200, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages debbindiff depends on: ii binutils-multiarch 2.25-5 ii bzip2 1.0.6-7+b2 ii cpio2.11+dfsg-4.1 ii diffutils 1:3.3-1+b1 ii file1:5.22+15-2 ii fontforge-extras0.3-4 ii gettext 0.19.3-2 ii ghc 7.6.3-20 ii gnupg 1.4.19-1 ii pdftk 2.02-2 ii poppler-utils 0.26.5-2 ii python 2.7.8-4 ii python-debian 0.1.25 ii python-magic1:5.22+15-2 ii python-rpm 4.11.3-1.1 ii rpm2cpio4.11.3-1.1 ii sng 1.0.2-7 ii unzip 6.0-16 ii vim 2:7.4.488-4 ii vim-common 2:7.4.488-4 ii xz-utils5.1.1alpha+20120614-2+b3 debbindiff recommends no packages. debbindiff suggests no packages. -- debconf-show failed turtles_1_all.deb Description: application/vnd.debian.binary-package turtles_2_all.deb Description: application/vnd.debian.binary-package
Bug#780284: nss-pam-ldapd: Descriptions do not explain why to use this over lib{pam, nss}-ldap
Control: tags -1 + help On Wed, 2015-03-11 at 12:23 -0400, Samuel Bronson wrote: > The descriptions of your binary packages do not describe the key > advantage that your modules provide over the "reference" > implementation, which is summarized by one of your users thus: > > libnss-ldapd is a fresh implementation written by Arthur de > Jong, which doesn't install TLS and LDAP libraries into every single > running program > > Instead [it] loads a shim that talks over a socket to nslcd, a > dedicated daemon. > > He thinks maybe you meant to be modest in your descriptions, but IMO > this would be a silly reason not to mention reasons one might (or > might not) prefer a package over its competitors. Improvements to the description are more than welcome ;) Some more information can be found here: http://arthurdejong.org/nss-pam-ldapd/ Thanks, -- -- arthur - adej...@debian.org - http://people.debian.org/~adejong -- signature.asc Description: This is a digitally signed message part
Bug#780760: Filter "due.before" with relative dates stopped working
Package: taskwarrior Version: 2.4.1+dfsg-3 Severity: normal Starting with taskwarrior 2.4, the filter "due.before" doesn't seem to work correctly with relative dates anymore. $ task add due:7d test Created task 1. $ task list due.before:7d No matches. $ task list ID Age D DueDescription Urg 1 2s2015-03-26 test8.75 Using an absolute specifier instead works: $ task list due.before:26th ID Age D DueDescription Urg 1 5s2015-03-26 test8.75 This looks like a regression. -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages taskwarrior depends on: ii libc6 2.19-17 ii libgcc11:4.9.2-10 ii libgnutls-deb0-28 3.3.8-6 ii libstdc++6 4.9.2-10 ii libuuid1 2.25.2-5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780759: ldd.fakechroot : wrong path of the elf loader
Package: fakechroot
Version: 2.17.2-1
Tags: patch
Dear maintainer,
It seems that ldd.fakechroot outputs a wrong path of the elf
loader on alpha, i.e. /lib64/ld-linux.so.2 instead of the correct
path /lib/ld-linux.so.2 :
$ ldd minimal/root/bin/ls
libselinux.so.1 => /lib/alpha-linux-gnu/libselinux.so.1
(0x0200c000)
libacl.so.1 => /lib/alpha-linux-gnu/libacl.so.1 (0x02046000)
libc.so.6.1 => /lib/alpha-linux-gnu/libc.so.6.1 (0x02064000)
libpcre.so.3 => /lib/alpha-linux-gnu/libpcre.so.3 (0x0222a000)
libdl.so.2.1 => /lib/alpha-linux-gnu/libdl.so.2.1 (0x02286000)
/lib/ld-linux.so.2 (0x02000100)
libattr.so.1 => /lib/alpha-linux-gnu/libattr.so.1 (0x0229c000)
$ debirf enter minimal/
debirf> loading profile 'minimal'...
0 alpha3:/# ldd bin/ls
linux-vdso.so.1 => (0x)
libfakechroot.so =>
/usr/lib/alpha-linux-gnu/fakechroot/libfakechroot.so (0x)
libfakeroot-sysv.so =>
/usr/lib/alpha-linux-gnu/libfakeroot/libfakeroot-sysv.so (0x)
libselinux.so.1 => /lib/alpha-linux-gnu/libselinux.so.1
(0x)
libpcre.so.3 => /lib/alpha-linux-gnu/libpcre.so.3 (0x)
libc.so.6.1 => /lib/alpha-linux-gnu/libc.so.6.1 (0x)
/lib64/ld-linux.so.2 (0x)
libdl.so.2.1 => /lib/alpha-linux-gnu/libdl.so.2.1 (0x)
libacl.so.1 => /lib/alpha-linux-gnu/libacl.so.1 (0x)
libattr.so.1 => /lib/alpha-linux-gnu/libattr.so.1 (0x)
With the following patch (untested on sparc64 and x32), we get the correct
result :
0 alpha3:/# ldd /bin/ls
linux-vdso.so.1 => (0x)
libfakechroot.so =>
/usr/lib/alpha-linux-gnu/fakechroot/libfakechroot.so (0x)
libfakeroot-sysv.so =>
/usr/lib/alpha-linux-gnu/libfakeroot/libfakeroot-sysv.so (0x)
libselinux.so.1 => /lib/alpha-linux-gnu/libselinux.so.1
(0x)
libpcre.so.3 => /lib/alpha-linux-gnu/libpcre.so.3 (0x)
libc.so.6.1 => /lib/alpha-linux-gnu/libc.so.6.1 (0x)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x)
libdl.so.2.1 => /lib/alpha-linux-gnu/libdl.so.2.1 (0x)
libacl.so.1 => /lib/alpha-linux-gnu/libacl.so.1 (0x)
libattr.so.1 => /lib/alpha-linux-gnu/libattr.so.1 (0x)
Regards,
JH Chatenet
diff -Naur a/usr/bin/ldd.fakechroot b/usr/bin/ldd.fakechroot
--- a/usr/bin/ldd.fakechroot2015-02-20 15:57:17.0 +0100
+++ b/usr/bin/ldd.fakechroot2015-03-03 23:26:41.0 +0100
@@ -81,10 +81,15 @@
$Format = $1;
if ($^O eq 'linux') {
+if ($Format =~ /^elf64-(x86-64|sparc)$/) {
+$Ldsodir = "/lib64";
+} elsif ($Format =~ /^elf32-x86-64$/) {
+$Ldsodir = "/libx32";
+}
+
if ($Format =~ /^elf64-/) {
push @Libs, 'linux-vdso.so.1';
$Libs{'linux-vdso.so.1'} = '';
-$Ldsodir = "/lib64";
}
else {
push @Libs, 'linux-gate.so.1';
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780719: unblock: flightgear/3.0.0-5
Control: tags -1 + moreinfo
On Wed, 2015-03-18 at 11:50 +0100, Markus Wanner wrote:
> please unblock the package flightgear-3.0.0-5 as recently uploaded to
> unstable. It fixes a security issue by disallowing nasal scripts to
> access or modify files, see #780712. I kept the packaging changes as
> minimal as possible. A debdiff and the patch are attached for review.
Well, not really. A debdiff from which you'd filtered the patch was
attached, as was the patch. I'm not convinced that actually provided any
benefit over simply providing the unfiltered debdiff.
++write_allowed_paths.push_back("/tmp/*.xml");
Is that really intended? (Both the hardcoding of /tmp/ rather than using
something respecting TMPDIR and being allowed to write any ".xml"
there.)
Regards,
Adam
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#750863: Please include package contents information
On Wed, Mar 18, 2015 at 08:14:20PM +0100, Ralf Treinen wrote: > On Wed, Mar 18, 2015 at 10:59:35AM -0700, j...@joshtriplett.org wrote: > > And I'd like to search for things like filename conflicts and compare > > them to package metadata; for instance, do packages that ship the same > > filename conflict or not, and do the versions of the conflict match the > > versions that ship the same file? (That won't be perfect, since it > > can't take diversions into account, which are unfortunately still > > programmatic in maintainer scripts rather than being declarative.) > > these could be found by inspecting the Contents file - this is how it > is done in [1]. This is today integrated in piuparts, code to find > packages sharing a path name can be found in [2]. > > [1] https://qa.debian.org/dose/file-overwrites.html > [2] https://alioth.debian.org/scm/browser.php?group_id=30965 Sure, though that's not correlated by version and package metadata the way UDD is. But yeah, that use case is much lower priority for me than the metadata issue (user/group/mode). - Josh Triplett -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780170: Please, update compatibility.js symlink
Hi David, Quoting David Prévot (2015-03-18 21:05:11) > > I’d like to get rid of the compatibility symlinks introduced in pdf.js > > 1.0.21+dfsg-1, and thus encourage you to change the > > /usr/share/pdf2htmlEX/compatibility.js symlink so it points to > > /usr/share/javascript/pdf/web/compatibility.js > > Even better: you may use directly /usr/share/pdf.js/compatibility.js as > shipped in pdf.js-common (>= 1.0.1149) instead of depending on > libjs-pdf. thanks a lot for your bug report! I'll make the change as soon as Jessie is released :) cheers, josch signature.asc Description: signature
Bug#542899: manpages for os-prober
Hello all, in attachment proposal for manpages for os-prober based on it's documentation. Please review and improve. Feel free to use it. -- Melhores cumprimentos/Best regards, Miguel Figueiredo .\" Manpage for os-prober. .\" Contact debian-b...@lists.debian.org for improvements. .TH os-prober 1 "20 Sep 2014" "1.0" "os-prober man page" .SH NAME os-prober - detect other filesystems with operating systems on them .SH SYNOPSIS os-prober .SH DESCRIPTION This is a small package that may be depended on by any bootloader installer package to detect other filesystems with o perating systems on them, and work out how to boot other linux installs. All one has to do is Depend on os-prober, and then run the os-prober command. This command takes no arguments: it will scan all disks available on the system for other operating systems, and output a list of strings such as: /dev/sda1:Windows NT/2000/XP:WinNT:chain ^---^ ^^ ^---^ ^---^ part.OS name for boot short May change: type of boot loader loader's pretty name required. Usually there is only output a 'linux' style bootloader or a chain one for other partitions with their own boot sectors. Tests are executable programs in the directory /usr/lib/os-probes/. Each test is called once per partition, with the partiton to check as its parameter, and may output a string as described above, or nothing if it does not recognise an OS on that partition. Tests return an exit code of 0 if they successfully found an OS, and no further tests will be run on that partition; or return an exit code of 1 to indicate that no OS was found, and let the next test run. Tests that require the partition to be mounted can be placed in /usr/lib/os-probes/mounted/. These tests are passed the following parameters: partition, mount point, filesystem. Bootloader installer packages will then have to process this output (fairly trivial) to create valid configuration entries for the bootloader. Note that os-prober can find other Linux installations, as well as other operating systems. It does not try to work out all the information needed to boot Linux (initrd, kernel params, etc). That task is left to linux-boot-prober. .SH OPTIONS os-prober does not take any options. .SH SEE ALSO linux-boot-prober(1) .SH BUGS See http://bugs.debian-org/os-prober .SH AUTHOR os-prober by the Debian Installer Team .\" Manpage for linux-boot-prober. .\" Contact debian-b...@lists.debian.org for improvements. .TH linux-boot-prober 1 "20 Sep 2014" "1.0" "linux-boot-prober man page" .SH NAME linux-boot-prober - figures out how to boot a linux partition .SH SYNOPSIS linux-boot-prober PARTITION_STRING (as returned by os-prober) .SH DESCRIPTION the linux-boot-prober command should be run with a single argument consisting of a partition that is known to have a linux root filesystem on it, as returned by the os-prober command. It will try to work out how to boot that linux installation, and if it is successful, will output one or more lines in the form: /dev/sda2:/dev/sda1:Linux:/vmlinuz:/initrd.gz:root=/dev/sda1 ^---^ ^---^ ^---^ ^--^ ^^ ^^ root bootlabel kernelinitrdkernel params part. part. The root partition and boot partition may of course be the same. No guarantee is made that any partitions referred to in the kernel parameters will still be in the same place after Debian is installed, or that the /etc/fstab of the system will be right, or that the system will even boot. The initrd field may be empty if there is no initrd. The label is whatever label was used in the boot loader for this linux installation, and it may be quite long or very short (or nonexistent), and may be inaccurate, confusing, or non-unique. See TODO for other limitations. The tests used by linux-boot-prober are in the directory /usr/lib/linux-boot-probes/ and also in /usr/lib/linux-boot-probes/mounted, and they are called in a similar way as the os-probes described above. The mounted probes are passed parameters for the root partition, the boot partition, and the directory the filesystems are mounted in. linux-boot-prober skips over partitions that are currently mounted on /, /target, or /target/boot. .SH OPTIONS linux-boot-prober does not take any options .SH SEE ALSO os-prober(1) .SH BUGS See http://bugs.debian-org/os-prober .SH AUTHOR os-prober by the Debian Installer Team
Bug#780170: Please, update compatibility.js symlink
Control: affects -1 libjs-pdf Hi Johannes, On Mon, Mar 09, 2015 at 09:36:42PM -0400, David Prévot wrote: > Package: pdf2htmlex > I’d like to get rid of the compatibility symlinks introduced in pdf.js > 1.0.21+dfsg-1, and thus encourage you to change the > /usr/share/pdf2htmlEX/compatibility.js symlink so it points to > /usr/share/javascript/pdf/web/compatibility.js Even better: you may use directly /usr/share/pdf.js/compatibility.js as shipped in pdf.js-common (>= 1.0.1149) instead of depending on libjs-pdf. > You may use a simple debian/links file containing the following line and > drop the current override_dh_auto_install from debian/rules: /usr/share/pdf.js/compatibility.js usr/share/pdf2htmlEX/compatibility.js Regards David signature.asc Description: Digital signature
Bug#780758: pcmanfm: hangs while copying files
Package: pcmanfm Version: 1.2.3-1.1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I was copying my home folder to an external hard drive that is windows formatted It would copy small amounts of files, but after a certain length of time for copying, (between 1:30 and 2:00) the operation would hang. the LXDE CPU monitor would show very low usage, and when a terminal was brought up no prompt would appear * What exactly did you do (or not do) that was effective (or ineffective)? All I could do was copy small amounts of files a chunk at a time. * What was the outcome of this action? * What outcome did you expect instead? I've used PCManFM since Squeeze- I've always been able to copy my entire home folder The disk that Debian was installed upon only has 270 MB free- could this be related? Unfortunately this is the last day for Jessie on this computer so I won't be able to help much more - I need this computer to be stable over the next few months due to extreme business in my life *** End of the template - remove these template lines *** -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (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: systemd (via /run/systemd/system) Versions of packages pcmanfm depends on: ii libatk1.0-0 2.14.0-1 ii libc62.19-15 ii libcairo21.14.0-2.1 ii libfm-gtk4 1.2.3-1 ii libfm4 1.2.3-1 ii libfontconfig1 2.11.0-6.3 ii libfreetype6 2.5.2-3 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgtk2.0-0 2.24.25-3 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpangoft2-1.0-01.36.8-3 ii libx11-6 2:1.6.2-3 Versions of packages pcmanfm recommends: ii gnome-icon-theme 3.12.0-1 ii gvfs-backends 1.22.2-1 ii gvfs-fuse 1.22.2-1 ii lxde-icon-theme0.5.1-1 ii lxsession [policykit-1-gnome] 0.5.1-2 ii policykit-1-gnome 0.105-2 pcmanfm 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#780680: libpam-modules: pam_userdb.so depends on a library in /usr
severity 780680 normal
thanks
Hi,
Adam Heath writes:
> A library in /lib shouldn't depend on a library in /usr/lib. However,
> pam_userdb.so has such an issue.
Arguably pam_userdb.so is not a library, but a plugin. So I don't think
this is a release critical bug or even a real bug at all, but I'll leave
the definite decision to the pam maintainers.
For reference, there are lots of other PAM and NSS modules doing the
same: libpam-{pgsql,mysql,ldap} and libnss-{pgsql2,mysql-bg,ldap} come
to mind, but probably many other libpam-* and libnss-* packages are
doing the same.
Ansgar
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780757: gnome-disk-utility: Cannot create encrypted Ext4 partition on removable flash drive
Package: gnome-disk-utility Version: 3.12.1-1+b1 Severity: normal Dear Maintainer, Steps to reproduce the problem: 1. Insert flash drive 2. Start gnome disk utility 3. Using gnome disk utility unmount automounted partitions on inserted flash drive 4. Delete partitions on inserted flash drive 5. Create new partition: LUKS + Ext4 Error popup appears: "Error wiping newly created partition /dev/sde1: Command-line `wipefs -a "/dev/sde1"' exited with non-zero exit status 1: wipefs: error: /dev/sde1: probing initialization failed: No such file or directory (udisks-error-quark, 0)" Encrypted partition does not get created. For the info: During the procedure, I have couple external encrypted USB hard drives already attached and mounted. Best regards, Svjatoslav -- 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=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 gnome-disk-utility depends on: ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii libatk1.0-0 2.14.0-1 ii libc62.19-15 ii libcairo-gobject21.14.0-2.1 ii libcairo21.14.0-2.1 ii libcanberra-gtk3-0 0.30-2.1 ii libcanberra0 0.30-2.1 ii libdvdread4 5.0.0-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 liblzma5 5.1.1alpha+20120614-2+b3 ii libnotify4 0.7.6-2 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpwquality11.2.3-1 ii libsecret-1-00.18-1+b1 ii libsystemd0 215-12 ii libudisks2-0 2.1.3-5 ii libx11-6 2:1.6.2-3 ii udisks2 2.1.3-5 gnome-disk-utility recommends no packages. gnome-disk-utility 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#780756: libzip: CVE-2015-2331: ZIP integer overflow
Source: libzip Version: 0.11.2-1 Severity: grave Tags: security upstream Justification: user security hole Hi, the following vulnerability was published for libzip. CVE-2015-2331[0]: ZIP Integer Overflow The issue was originally reported to php5 for the embedded (modified) copy of libzip there, but affects as well libzip. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2015-2331 Please adjust the affected versions in the BTS as needed. Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780755: release-notes: please mention availability of the Debian Games Blend
Package: release-notes Severity: normal Tags: patch Hello, please consider to apply the attached patch to Jessie's release notes and mention the availability of the Debian Games Blend. https://tracker.debian.org/pkg/debian-games For the first time this blend allows gamers and game developers to quickly install and find games and developer tools based on programming language or games category. Thank you Markus --- whats-new.dbk 2015-03-18 20:32:23.788808185 +0100 +++ whats-new.dbk.new 2015-03-18 20:33:35.105332676 +0100 @@ -503,5 +503,21 @@ the php-horde package. + +Debian Games Blend +The Debian Games Team proudly presents the Debian Games http://blends.debian.org/blends/";>Blend consisting of +https://tracker.debian.org/pkg/debian-games";>33 +metapackages which simplify the installation of games per +category. The selection includes among many others strategy, simulation, card +and programming games. Debian Games also offers developers a quick way to +install recommended software for developing games in the C++, Java, Perl or +Python 3 programming languages. Content developers will find useful tools +for creating game art in games-content-dev. +The project homepage provides screenshots and further information and +offers a compact overview about all games including +http://blends.debian.org/games/tasks/finest";>Debian's finest games. + +
Bug#780754: ruby-rmagick: README.html is defective
Package: ruby-rmagick Version: 2.13.2-4+b1 Severity: normal There's clearly something wrong with the README.html documentation file for this package. See attached screenshot. -- System Information: Debian Release: 7.1 APT prefers testing APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ruby-rmagick depends on: ii libc6 2.19-15 ii libgmp10 2:6.0.0+dfsg-6 ii libmagickcore-6.q16-2 8:6.8.9.9-5 ii libruby2.1 2.1.5-1 ii ruby 1:2.1.5 ruby-rmagick recommends no packages. ruby-rmagick 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#780753: clementine: Remove me from Uploaders
Source: clementine Severity: wishlist Hi Thomas! I'm barely using clementine nowadays and I really didn't like upstream's attitude, so please remove me from Uploaders on the next upload. Thanks! -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (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#780752: FTBFS related : Hang and Error
Package: glib2.0 Version: 2.0-2.42.1 There seems to be two problems... 1. Hangup ---x--x--xx # Start of gdbus tests ok 1 /gdbus/message-serialize-basic PASS: gdbus-serialization 1 /gdbus/message-serialize-basic ok 2 /gdbus/message-serialize-complex PASS: gdbus-serialization 2 /gdbus/message-serialize-complex ok 3 /gdbus/message-serialize-invalid PASS: gdbus-serialization 3 /gdbus/message-serialize-invalid ok 4 /gdbus/message-serialize-header-checks PASS: gdbus-serialization 4 /gdbus/message-serialize-header-checks # Bug Reference: https://bugzilla.gnome.org/show_bug.cgi?id=673612 ok 5 /gdbus/message-parse-empty-arrays-of-arrays PASS: gdbus-serialization 5 /gdbus/message-parse-empty-arrays-of-arrays # Start of message-serialize tests # Bug Reference: https://bugzilla.gnome.org/show_bug.cgi?id=732754 # GLib-GIO:ERROR:/home/jeffrin/glib2.0-2.42.1/./gio/tests/gdbus-serialization.c:1061:test_double_array: assertion failed (error == NULL): Unknown or unsupported transport 'this-should-not-be-used-and-will-fail' for address 'this-should-not-be-used-and-will-fail:' (g-io-error-quark, 13) ERROR: gdbus-serialization - missing test plan ERROR: gdbus-serialization - exited with status 134 (terminated by signal 6?) ERROR: gsettings # random seed: R02S224adaee498ca4ae2c3c0941d9a44f02 # Start of gsettings tests ok 1 /gsettings/basic PASS: gsettings 1 /gsettings/basic ok 2 /gsettings/no-schema PASS: gsettings 2 /gsettings/no-schema ok 3 /gsettings/unknown-key PASS: gsettings 3 /gsettings/unknown-key ok 4 /gsettings/wrong-type PASS: gsettings 4 /gsettings/wrong-type ok 5 /gsettings/wrong-path PASS: gsettings 5 /gsettings/wrong-path ok 6 /gsettings/no-path PASS: gsettings 6 /gsettings/no-path ok 7 /gsettings/basic-types warning: translation is not working... skipping test. PASS: gsettings 7 /gsettings/basic-types ok 8 /gsettings/complex-types warning: translation is not working... skipping test. PASS: gsettings 8 /gsettings/complex-types ok 9 /gsettings/changes PASS: gsettings 9 /gsettings/changes ok 10 /gsettings/l10n PASS: gsettings 10 /gsettings/l10n ok 11 /gsettings/l10n-context PASS: gsettings 11 /gsettings/l10n-context ok 12 /gsettings/delay-apply PASS: gsettings 12 /gsettings/delay-apply ok 13 /gsettings/delay-revert PASS: gsettings 13 /gsettings/delay-revert ok 14 /gsettings/delay-child PASS: gsettings 14 /gsettings/delay-child ok 15 /gsettings/atomic PASS: gsettings 15 /gsettings/atomic ok 16 /gsettings/simple-binding PASS: gsettings 16 /gsettings/simple-binding ok 17 /gsettings/directional-binding PASS: gsettings 17 /gsettings/directional-binding ok 18 /gsettings/custom-binding PASS: gsettings 18 /gsettings/custom-binding ok 19 /gsettings/no-change-binding PASS: gsettings 19 /gsettings/no-change-binding ok 20 /gsettings/unbinding PASS: gsettings 20 /gsettings/unbinding ok 21 /gsettings/writable-binding PASS: gsettings 21 /gsettings/writable-binding ok 22 /gsettings/typesafe-binding PASS: gsettings 22 /gsettings/typesafe-binding ok 23 /gsettings/no-read-binding PASS: gsettings 23 /gsettings/no-read-binding Trace/breakpoint trap ok 24 /gsettings/no-write-binding PASS: gsettings 24 /gsettings/no-write-binding ERROR: gsettings - missing test plan ERROR: gsettings - exited with status 133 (terminated by signal 5?) --x-x---x The program continued to Error following execution after i gave a SIGTRAP signal -x--x-x-- 2. Error Testsuite summary for glib 2.42.1 # TOTAL: 28 # PASS: 28 # SKIP: 0 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 0 make[7]: Leaving directory '/home/jeffrin/glib2.0-2.42.1/debian/build/deb/tests' TEST: testglib... (pid=4561) /testglib/Infos: OK /testglib/Types Sizes: OK /testglib/GStrings: OK /testglib/Various Strings: OK /testglib/GList: OK /testglib/GSList: OK /testglib/GNode: OK /testglib/GTree: OK /testglib/Arrays: OK /testglib/GHashTable: OK /testglib/Relation (deprecated): OK /testglib/File Paths: OK /testglib/File F
Bug#780751: mono: CVE-2015-2318 CVE-2015-2319 CVE-2015-2320
Source: mono Version: 3.2.8+dfsg-9 Severity: grave Tags: security upstream fixed-upstream the following vulnerabilities were published for mono. CVE-2015-2318[0]: SKIP-TLS issue CVE-2015-2319[1]: FREAK issue CVE-2015-2320[2]: Remove the client-side SSLv2 fallback If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2015-2318 [1] https://security-tracker.debian.org/tracker/CVE-2015-2319 [2] https://security-tracker.debian.org/tracker/CVE-2015-2320 Please adjust the affected versions in the BTS as needed. Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780749: glib: FTBFS related : Hang and Error
Package: glib2.0Version: 2.0-2.42.1 There seems to be two problems... 1. Hangup ---x--x--xx # Start of gdbus tests ok 1 /gdbus/message-serialize-basic PASS: gdbus-serialization 1 /gdbus/message-serialize-basic ok 2 /gdbus/message-serialize-complex PASS: gdbus-serialization 2 /gdbus/message-serialize-complex ok 3 /gdbus/message-serialize-invalid PASS: gdbus-serialization 3 /gdbus/message-serialize-invalid ok 4 /gdbus/message-serialize-header-checks PASS: gdbus-serialization 4 /gdbus/message-serialize-header-checks # Bug Reference: https://bugzilla.gnome.org/show_bug.cgi?id=673612 ok 5 /gdbus/message-parse-empty-arrays-of-arrays PASS: gdbus-serialization 5 /gdbus/message-parse-empty-arrays-of-arrays # Start of message-serialize tests # Bug Reference: https://bugzilla.gnome.org/show_bug.cgi?id=732754 # GLib-GIO:ERROR:/home/jeffrin/glib2.0-2.42.1/./gio/tests/gdbus-serialization.c:1061:test_double_array: assertion failed (error == NULL): Unknown or unsupported transport 'this-should-not-be-used-and-will-fail' for address 'this-should-not-be-used-and-will-fail:' (g-io-error-quark, 13) ERROR: gdbus-serialization - missing test plan ERROR: gdbus-serialization - exited with status 134 (terminated by signal 6?) ERROR: gsettings # random seed: R02S224adaee498ca4ae2c3c0941d9a44f02 # Start of gsettings tests ok 1 /gsettings/basic PASS: gsettings 1 /gsettings/basic ok 2 /gsettings/no-schema PASS: gsettings 2 /gsettings/no-schema ok 3 /gsettings/unknown-key PASS: gsettings 3 /gsettings/unknown-key ok 4 /gsettings/wrong-type PASS: gsettings 4 /gsettings/wrong-type ok 5 /gsettings/wrong-path PASS: gsettings 5 /gsettings/wrong-path ok 6 /gsettings/no-path PASS: gsettings 6 /gsettings/no-path ok 7 /gsettings/basic-types warning: translation is not working... skipping test. PASS: gsettings 7 /gsettings/basic-types ok 8 /gsettings/complex-types warning: translation is not working... skipping test. PASS: gsettings 8 /gsettings/complex-types ok 9 /gsettings/changes PASS: gsettings 9 /gsettings/changes ok 10 /gsettings/l10n PASS: gsettings 10 /gsettings/l10n ok 11 /gsettings/l10n-context PASS: gsettings 11 /gsettings/l10n-context ok 12 /gsettings/delay-apply PASS: gsettings 12 /gsettings/delay-apply ok 13 /gsettings/delay-revert PASS: gsettings 13 /gsettings/delay-revert ok 14 /gsettings/delay-child PASS: gsettings 14 /gsettings/delay-child ok 15 /gsettings/atomic PASS: gsettings 15 /gsettings/atomic ok 16 /gsettings/simple-binding PASS: gsettings 16 /gsettings/simple-binding ok 17 /gsettings/directional-binding PASS: gsettings 17 /gsettings/directional-binding ok 18 /gsettings/custom-binding PASS: gsettings 18 /gsettings/custom-binding ok 19 /gsettings/no-change-binding PASS: gsettings 19 /gsettings/no-change-binding ok 20 /gsettings/unbinding PASS: gsettings 20 /gsettings/unbinding ok 21 /gsettings/writable-binding PASS: gsettings 21 /gsettings/writable-binding ok 22 /gsettings/typesafe-binding PASS: gsettings 22 /gsettings/typesafe-binding ok 23 /gsettings/no-read-binding PASS: gsettings 23 /gsettings/no-read-binding Trace/breakpoint trap ok 24 /gsettings/no-write-binding PASS: gsettings 24 /gsettings/no-write-binding ERROR: gsettings - missing test plan ERROR: gsettings - exited with status 133 (terminated by signal 5?) --x-x---x The program continued to Error following execution after i gave a SIGTRAP signal -x--x-x-- 2. Error Testsuite summary for glib 2.42.1 # TOTAL: 28 # PASS: 28 # SKIP: 0 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 0 make[7]: Leaving directory '/home/jeffrin/glib2.0-2.42.1/debian/build/deb/tests' TEST: testglib... (pid=4561) /testglib/Infos: OK /testglib/Types Sizes: OK /testglib/GStrings: OK /testglib/Various Strings: OK /testglib/GList: OK /testglib/GSList: OK /testglib/GNode: OK /testglib/GTree: OK /testglib/Arrays: OK /testglib/GHashTable: OK /testglib/Relation (deprecated): OK /testglib/File Paths: OK /testglib/File Func
Bug#780750: vips should build depend on libgsf-1-dev
Package: vips Version: 7.42.1-1 Severity: normal See https://github.com/lovell/sharp/pull/173#issuecomment-76177598 Github user lovell says: "I think libgsf-1-dev should be added as a mandatory dependency of lipvips-dev given libgsf-1-114 is a mandatory dependency of libvips38." -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#771485: Processed: jessie
Hi, On Montag, 9. März 2015, Cyril Brulebois wrote: > Well, what happened in #757413 doesn't fill me with joy indeed. And > now the same happens with these bug reports a few hours after that… about #771617: I often setup LVM inside encrypted partitions on wheezy, so I was fairly sure this bug does not occur on wheezy. about #771485: I never heard about parted segfaulting on released wheezy images, so I thought this bug was not (as) relevant for wheezy. > Regardless of whether I'm annoyed, I think it would be much more > constructive and straightforward to ask when you're not sure. Having > tags go back & forth (possibly several times) isn't a very productive > way of spending everybody's time. In the last two years I've never argued when someone (seldomly) correcty my tagging of wheezy-rc bugs. (And except for this one accident with the one bug last week I also never played tag ping pong once.) Right now I'm also not argueing but rather trying to explain why I tagged them as I tagged. But, as it seems people making mistakes annoy you more than people doing nothing, I will do this from now. It's no fun to do this (mostly) thankless janitor work if one has to justify oneself like this. Perfect is the enemy of good and all that.. I already noticed a bad feeling and "fear" of such replies when I did the tagging today and in future I think I will rather do other things when I'm looking for little things to do to wake up... Which is kind of ironic as you also seem to care about Wheezy (which should make me happy.) Sigh. FWIW, wheezy was the first release where the RC list for wheezy (most of the times) only contained bugs relevant for wheezy (and not 30-50% bugs not affecting wheezy). I thought this was useful work... And yes, when tagging 20 bugs I don't research each of them for very long... but I also thought (wished?) we were doing kind of team work, where people help each other when they sometimes do little mistakes. Holger I wrote this mail a week ago and didnt send it, to see if I change my mind. Now I was just reminded of RC bugs in wheezy, thought about this, read what I wrote and decided to push the send button. It's no fun if it's no fun. signature.asc Description: This is a digitally signed message part.
Bug#750863: Please include package contents information
On Wed, Mar 18, 2015 at 10:59:35AM -0700, j...@joshtriplett.org wrote: > And I'd like to search for things like filename conflicts and compare > them to package metadata; for instance, do packages that ship the same > filename conflict or not, and do the versions of the conflict match the > versions that ship the same file? (That won't be perfect, since it > can't take diversions into account, which are unfortunately still > programmatic in maintainer scripts rather than being declarative.) these could be found by inspecting the Contents file - this is how it is done in [1]. This is today integrated in piuparts, code to find packages sharing a path name can be found in [2]. [1] https://qa.debian.org/dose/file-overwrites.html [2] https://alioth.debian.org/scm/browser.php?group_id=30965 -Ralf. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780748: libqt5webkit5: QtWebKit logs visited URLs to WebpageIcons.db in private browsing mode
Package: libqt5webkit5 Version: 5.3.2+dfsg-3 Severity: important Tags: upstream patch security Dear Maintainer, I've just submitted a change[1] to QtWebKit upstream to prevent it recording visited URLs to its favicon database (WebpageIcons.db) while using private browsing mode. The change has been accepted in upstream's Gerrit and is currently integrating in their CI. Raw patch: [2] I think this should be backported as it's a privacy issue. Thanks, Florian [1] https://codereview.qt-project.org/#/c/108936/ [2] http://code.qt.io/cgit/qt/qtwebkit.git/patch/?id=101feb8867ba85b1615656669bbb3ecf8574aaab -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.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 Init: systemd (via /run/systemd/system) Versions of packages libqt5webkit5 depends on: ii dpkg 1.17.24 ii libc6 2.19-15 ii libgl1-mesa-glx [libgl1] 10.3.2-1 ii libglib2.0-0 2.42.1-1 ii libgstreamer-plugins-base0.10-0 0.10.36-2 ii libgstreamer0.10-00.10.36-1.5 ii libicu52 52.1-7.1 ii libjpeg62-turbo 1:1.3.1-11+deb7u1 ii libpng12-01.2.50-2+b2 ii libqt5core5a [qtbase-abi-5-3-2] 5.3.2+dfsg-4+b1 ii libqt5gui55.3.2+dfsg-4+b1 ii libqt5network55.3.2+dfsg-4+b1 ii libqt5opengl5 5.3.2+dfsg-4+b1 ii libqt5printsupport5 5.3.2+dfsg-4+b1 ii libqt5qml5 [qtdeclarative-abi-5-3-2] 5.3.2-4 ii libqt5quick5 5.3.2-4 ii libqt5sql55.3.2+dfsg-4+b1 ii libqt5widgets55.3.2+dfsg-4+b1 ii libsqlite3-0 3.8.7.1-1 ii libstdc++64.9.2-10 ii libwebp5 0.4.1-1.2+b2 ii libx11-6 2:1.6.2-3 ii libxcomposite11:0.4.4-1 ii libxml2 2.9.1+dfsg1-5 ii libxrender1 1:0.9.8-1+b1 ii libxslt1.11.1.28-2+b2 ii multiarch-support 2.19-15 ii zlib1g1:1.2.8.dfsg-2+b1 libqt5webkit5 recommends no packages. libqt5webkit5 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#780555: apt-cacher-ng: Use with Fedora Rawhide is problematic
Control: tags 780555 +upstream Hallo, * Carlos Maddela [Mon, Mar 16 2015, 12:21:54PM]: > Using apt-cacher-ng to cache RPMs from Fedora Rawhide eventually results > in packages that cannot be verified, because it would seem that Fedora > allows them to be rebuilt without incrementing the version number. > > I tried fixing this problem by marking them as volatile with the > VfilePatternEx option: > > /development/rawhide/.* > > However, this fails to achieve anything, since the default SPfilePattern > includes all RPMs and this option overrides any VfilePattern option. > > Not completely understading why the default SPfilePattern must include > all RPMs, I have provided a possible solution which allows for It's a bug. It was intended to match only .gpg files but the final bracket is misplaced. Even with that small fix the SPfilePattern checking implementation doesn't allow to make files like foo.rpm.gpg considered volatile, so I will add your patch soon, probably with minor modifications after review/check for side effects. Thanks! But the last patch with extra mirrors is something I do not fully agree with. The backends files are generated semi-automatically (see special make targets) and Fedora mirror list is fed from https://mirrors.fedoraproject.org/publiclist . Some of the sites you added are already in the list that I compiled a couple of weeks ago but not all; and they are also not on the publiclist page. Could you reveal the source of that mirror urls? Kind Regards, Eduard. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765379: gcc-4.7 should not ship with jessie
Hi, this was a bad one; gcc-4.9-base from jessie breaks gcc-4.7-base from wheezy, so you had to update gcc-4.7-base to jessie/unstable for a stable/testing mix as soon as some package required gcc-4.9-base from testing. For now using gcc-4.7-base from unstable seems to work; wheezy/jessie mix is broken otherwise. regards, Stefan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#778380: Progress on package update
Hi! I have already updated the package to the lastest release, which is working fine in production on Jessie (not based on git-buildpackage until now). I am also willing to help out on the package, since we will need this in production. Ilya is there any progress on your side? I would also like to address some of the other issues and I am willing to spend some time on this. Greetings Torge signature.asc Description: Message signed with OpenPGP using GPGMail
Bug#765577: netboot install writes duplicates to 70-persistent-net.rules
Am 18.03.2015 um 18:52 schrieb Michael Biebl: > Am 18.03.2015 um 18:15 schrieb Faidon Liambotis: >> Another less arbitrary/racy workaround I suggesed was a grep near the >> top of write_net_rules' write_rule() function. Since write_rule() >> operates under a lock, this would completely eliminate any kind of race >> here. I pitched this to Marco but he wasn't thrilled with the idea -- he >> said he'd prefer finding the root cause. I've done the change and tested >> it anyway, though, and it successfully aleviates this issue: > > I'm with Marco here. Before adding any workarounds, we need to > understand what the underlying problem is. Otherwise we are adding cruft > which nobody understands anymore a few years from now. > > Since I can't reproduce the issue and already have trouble keeping up > with other bug reports, further investigation needs to be done by > someone else. Btw, thanks for looking into this. Would be awesome if you can dig further and get to the bottom of this. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#780591: ltsp-client-builder fails when installing Debian Edu combined server in virtualbox environment
On Tue, Mar 17, 2015 at 10:00:08PM +0100, Wolfgang Schweer wrote: > On Tue, Mar 17, 2015 at 07:25:11PM +0100, Petter Reinholdtsen wrote: > > > > > if [ "$USE_CDROM" != "false" ] && [ ! -f /target/media/cdrom/.disk/info > > > ]; then > > > chroot /target mount /media/cdrom > > > log "mounting /media/cdrom" > > > fi > > > > When I just tested and the LTSP installation failed, the USE_CDROM value > > is 'true' and nothing is mounted in /target/media/. The CD from > > /dev/sr0 is mounted on /cdrom/. > > With this (trivial) modification installation succeeded. > > --- a/postinst2015-03-06 10:00:00.0 +0100 > +++ ltsp-client-builder.postinst 2015-03-17 21:39:38.824682599 +0100 > @@ -64,7 +64,7 @@ > db_progress STEP 1 > > if [ "$USE_CDROM" != "false" ] && [ ! -f /target/media/cdrom/.disk/info ]; > then > -chroot /target mount /media/cdrom > +mount /dev/cdrom /target/media/cdrom > log "mounting /media/cdrom" > fi Tested once again using the just rsynced usbstick ISO image (containing newest udebs): LTSP chroot installation fails as before. After /var/lib/dpkg/info/ltsp-client-builder.postinst (d-i env) had been modified like stated above, choosing LTSP chroot installation out of the d-i main-menu once again made the chroot installation start. So I guess the only chance to get the Sebian Edu LTSP installation going would be a fixed version of the ltsp-client-builder udeb. And this bug should be reassigned to ltsp, although most probably changes of d-i component caused this issue since some weeks. Wolfgang signature.asc Description: Digital signature
Bug#765577: (no subject)
On Wed, Mar 18, 2015 at 06:52:14PM +0100, Michael Biebl wrote:
> I'm with Marco here. Before adding any workarounds, we need to
> understand what the underlying problem is. Otherwise we are adding cruft
> which nobody understands anymore a few years from now.
>
> Since I can't reproduce the issue and already have trouble keeping up
> with other bug reports, further investigation needs to be done by
> someone else.
Well, the root cause IMO is that 75-persistent-net-generator.rules is
inherently susceptible to races. It's my understanding that it's valid
for events to be triggered multiple times -- there are multiple places
in d-i that "udevadm trigger" is called, including start-udev (as
shipped by udev-udeb) which would trigger another set of "add" events
beyond the original "hotplug" one.
This is why write_net_rules operates under a lockfile too (again, AIUI).
It's just that this doesn't fix the race, just limits the race window
significantly but not entirely (as it makes write_net_rules idempotent,
but not 75-persistent-net-generator.rules).
The reason this is found in current jessie might just be that udev got
faster, or more udevadm triggers were added in other parts of the
installer etc.
In any case, if you need more input from a buggy system, feel free to
let me know and I'll try my best to get back to you with more details.
Oh, my original patch was buggy for many reasons, here's the updated
version:
diff --git a/debian/extra/write_net_rules b/debian/extra/write_net_rules
index 4379792..95939b8 100644
--- a/debian/extra/write_net_rules
+++ b/debian/extra/write_net_rules
@@ -117,6 +117,12 @@ fi
basename=${INTERFACE%%[0-9]*}
match="$match, KERNEL==\"$basename*\""
+# detect a race and abort, cf. #765577
+if [ -f $RULES_FILE ] && grep -q -F "$match" $RULES_FILE; then
+ unlock_rules_file
+ exit 0
+fi
+
if [ "$INTERFACE_NAME" ]; then
# external tools may request a custom name
COMMENT="$COMMENT (custom name provided by external tool)"
Regards,
Faidon
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#773097: mate-notification-daemon: this is still an issue with the latest 1.8.2-1 re; eased to experimental.
On Tue, 17 Mar 2015 00:54:17 +0530 =?UTF-8?B?c2hpcmlzaCDgpLbgpL/gpLDgpYDgpLc=?= wrote: > > Is it possible that you are actually seeing notifications from another > > notification-daemon provider, e.g., notify-osd (XFCE), > > notification-daemon (GNOMEv3), etc.? > > > > Check output of ps aux | grep notif, what daemon is actually running > > and if mate-notification is _really_ running for the current $DISPLAY. > > Aha, that solved it. First kde-notify was rearing it head. Once I > disabled it, then xfce4-notifyd was doing the same. > > Once I disabled both (commenting both the services at > /usr/share/dbus-1/services) namely org.kde.knotify.service and > org.xfce.xfce4-notifyd.Notifications.service the Exec part, rebooted > and it was working as it should be. > I commented exec in kde.notify.service because knotif was running disabled kwin and rebooted neiter knotify4 nor mate-notification are running and i can't run it /usr/lib/mate-notification-daemon/mate-notification-daemon ** (mate-notification-daemon:10327): WARNING **: Failed to acquire name org.freedesktop.Notifications ps aux | grep notif root39 0.0 0.0 0 0 ?S19:02 0:00 [fsnotify_mark] ale 2969 0.0 0.4 274456 16392 ?Sl 19:04 0:00 /usr/lib/mate-panel/notification-area-applet ale 9078 0.0 0.0 12748 2172 pts/0S+ 19:09 0:00 grep --color=auto notif -- sip:alebar...@ekiga.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780675: systemd: segfault in systemd when running systemctl daemon-reload
Am 18.03.2015 um 16:29 schrieb Robert Pumphrey: > #!/bin/bash > ### BEGIN INIT INFO > # Provides: iptables > # Required-Start:$network $remote_fs $syslog > # Required-Stop: $network $remote_fs $syslog > # Should-Start: iptables > # Default-Start: 2 3 4 5 > # Default-Stop: 0 1 6 > ### END INIT INFO > Also note that the problem is not reproducible if the Provides: and > Should-Start: name match the init script name, so I guess mismatch in > the script name and header is at the root of the problem. The mismatch between init script name and Provides shouldn't be a problem. You can certainly name your init script foo and have Provides: bar (the systemd-sysv-generator will then create a bar symlink pointing at foo). I think the problem is that you depend on yourself: Provides: iptables and Should-Start: iptables This is of course bogus and a bug in the init script, but shouldn't cause a segfault. If you remove the # Should-Start: iptables line, the problem should be gone. Now will need to dig into the code, to find the problem. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#780746: libreoffice-impress: Need youtube resolutions and aspect ratios.
Package: libreoffice-impress Version: 1:4.3.3-2 Severity: wishlist Dear Maintainer, Slide show can be used to create youtube videos. To better support this functionality there should be an option to set slide show resolution, of the output window, to one of the prefered youtube resolutions and aspect ratios. Reference: Advanced encoding settings https://support.google.com/youtube/answer/1722171?hl=en&ref_topic=2888648 2160p: 3840x2160 1440p: 2560x1440 1080p: 1920x1080 720p: 1280x720 480p: 854x480 360p: 640x360 240p: 426x240 Thank You. -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (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: systemd (via /run/systemd/system) Versions of packages libreoffice-impress depends on: ii libc6 2.19-15 ii libetonyek-0.1-1 0.1.1-2 ii libgcc1 1:4.9.2-10 ii libgl1-mesa-glx [libgl1] 10.3.2-1 ii libglew1.10 1.10.0-3 ii libglu1-mesa [libglu1]9.0.0-2 ii libodfgen-0.1-1 0.1.1-2 ii libreoffice-core 1:4.3.3-2 ii libreoffice-draw 1:4.3.3-2 ii librevenge-0.0-0 0.0.1-3 ii libstdc++64.9.2-10 ii libxml2 2.9.1+dfsg1-5 ii uno-libs3 4.3.3-2 ii ure 4.3.3-2 ii zlib1g1:1.2.8.dfsg-2+b1 Versions of packages libreoffice-impress recommends: ii libreoffice-avmedia-backend-gstreamer 1:4.3.3-2 Versions of packages libreoffice-impress suggests: ii bluez 5.23-2+b1 Versions of packages libreoffice-core depends on: ii fontconfig2.11.0-6.3 ii fonts-opensymbol 2:102.6+LibO4.3.3-2 ii libatk1.0-0 2.14.0-1 ii libboost-date-time1.55.0 1.55.0+dfsg-3 ii libc6 2.19-15 ii libcairo2 1.14.0-2.1 ii libclucene-contribs1 2.3.3.4-4 ii libclucene-core1 2.3.3.4-4 ii libcmis-0.4-4 0.4.1-7 ii libcups2 1.7.5-11 ii libcurl3-gnutls 7.38.0-4 ii libdbus-1-3 1.8.16-1 ii libdbus-glib-1-2 0.102-1 ii libeot0 0.01-3 ii libexpat1 2.1.0-6+b3 ii libexttextcat-2.0-0 3.4.4-1 ii libfontconfig12.11.0-6.3 ii libfreetype6 2.5.2-3 ii libgcc1 1:4.9.2-10 ii libgdk-pixbuf2.0-02.31.1-2+b1 ii libgl1-mesa-glx [libgl1] 10.3.2-1 ii libglew1.10 1.10.0-3 ii libglib2.0-0 2.42.1-1 ii libgltf-0.0-0 0.0.2-2 ii libglu1-mesa [libglu1]9.0.0-2 ii libgraphite2-31.2.4-3 ii libgtk2.0-0 2.24.25-3 ii libharfbuzz-icu0 0.9.35-2 ii libharfbuzz0b 0.9.35-2 ii libhunspell-1.3-0 1.3.3-3 ii libhyphen02.8.8-1 ii libice6 2:1.0.9-1+b1 ii libicu52 52.1-7.1 ii libjpeg62-turbo 1:1.3.1-11 ii liblangtag1 0.5.1-3 ii liblcms2-22.6-3+b3 ii libldap-2.4-2 2.4.40-4 ii libmythes-1.2-0 2:1.2.4-1 ii libneon27-gnutls 0.30.1-1 ii libnspr4 2:4.10.7-1 ii libnss3 2:3.17.2-1.1 ii libnss3-1d2:3.17.2-1.1 ii libodfgen-0.1-1 0.1.1-2 ii libpango-1.0-01.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpangoft2-1.0-0 1.36.8-3 ii libpng12-01.2.50-2+b2 ii librdf0 1.0.17-1+b1 ii libreoffice-common1:4.3.3-2 ii librevenge-0.0-0 0.0.1-3 ii libsm62:1.2.2-1+b1 ii libssl1.0.0 1.0.1k-1 ii libstdc++64.9.2-10 ii libx11-6 2:1.6.2-3 ii libxext6 2:1.3.3-1 ii libxinerama1 2:1.1.3-1+b1 ii libxml2 2.9.1+dfsg1-5 ii libxrandr22:1.4.2-1+b1 ii libxrender1 1:0.9.8-1+b1 ii libxslt1.11.1.28-2+b2 ii libxt61:1.1.4-1+b1 ii uno-libs3 4.3.3-2 ii ure 4.3.3-2 ii zlib1g1:1.2.8.dfsg-2+b1 Versions of packages libreoffice-draw depends on: ii libc6 2.19-15 ii libcdr-0.1-1 0.1.0-3 ii libdbus-1-31.8.16-1 ii libdbus-glib-1-2 0.102-1 ii libfreehand-0.1-1 0.1.0-2 ii libgcc11:4.9.2-10 ii libglib2.0-0 2.42.1-1 ii libicu52 52.1-7.1 ii liblcms2-2 2.6-3+b3 ii libmspub-0.1-1 0.1.1-2 ii libmwaw-0.3-3 0.3.1-2 ii libodfgen-0.1-10.1.1-2 ii libreoffice-core 1:4.3.3-2 ii librevenge-0.0-0 0.0.1-3 ii libstdc++6 4.9.2-10 ii libvisio-0.1-1 0.1.0-2 ii libwpd-0.10-10 0.10.0-2+b1 ii libwpg-0.3-3 0.3.0
Bug#780747: reportbug: -o option is ignored on first run after fresh install
Package: reportbug Version: 6.6.3 Severity: normal Dear Maintainer, To file a previous bug report I invoked: reportbug --email 'bju...@clarku.edu' -o cust/sensible.bug.txt The -o option was supposed to prevent the use of email by the reportbug tool and instead generate the file that I could email by hand. The report was automatically submitted by SMTP nonetheless. For those that just use reportbug to generate headers and then edit the email afterwards, this could result in a lot of blank bug reports being filed with the BTS. In addition to that, despite the -o option, reportbug prompted for details of how to get email off the box (which I don't want to happen ever, actually, and it is only luck that it worked at all as I have not finished purging all traces of SMTP from this system.) This was the first time I had run reportbug on a fresh jessie install (from jessie netboot disks). When I filed this bug, the -o option worked as intended and I was able to edit this text before pasting it into an email client. -- Package-specific info: ** Environment settings: INTERFACE="text" ** /home/bri/.reportbugrc: reportbug_version "6.6.3" mode standard ui text offline email "bju...@clarku.edu" no-cc header "X-Debbugs-CC: bju...@clarku.edu" smtphost reportbug.debian.org -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (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: systemd (via /run/systemd/system) Versions of packages reportbug depends on: ii apt 1.0.9.7 ii python2.7.8-4 ii python-reportbug 6.6.3 pn python:any reportbug recommends no packages. Versions of packages reportbug suggests: pn claws-mail pn debconf-utils pn debsums pn dlocate ii emacs24-bin-common 24.4+1-5 ii file1:5.22+15-2 ii gnupg 1.4.18-7 pn postfix | exim4 | mail-transport-agent ii python-gtk2 2.24.0-4 pn python-gtkspell pn python-urwid pn python-vte ii xdg-utils 1.1.0~rc1+git20111210-7.4 Versions of packages python-reportbug depends on: ii apt 1.0.9.7 ii python-debian 0.1.25 ii python-debianbts 1.12 pn python:any python-reportbug suggests no packages. -- no debconf information
Bug#780675: systemd: segfault in systemd when running systemctl daemon-reload
Control: fixed -1 219-4 Am 18.03.2015 um 18:00 schrieb Michael Biebl: > Thanks for sharing the contents of the file. I can confirm the crash and > we have enough information now to debug this issue properly. > Marking the bug accordingly. Can't reproduce the issue with the version from experimental. Marking accordingly -- 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#750863: Please include package contents information
On Wed, Mar 18, 2015 at 06:36:02PM +0100, Lucas Nussbaum wrote: > On 07/06/14 at 11:10 -0700, Josh Triplett wrote: > > Package: qa.debian.org > > Severity: wishlist > > User: qa.debian@packages.debian.org > > > > It'd be quite handy to have package contents information in UDD. > > > > Columns, in addition to a unique package ID foreign-keyed to the > > packages table: > > > > filename > > owner > > group > > mode > > Hi Josh, > > What is your use case for that? > > This would add quite a lot of information to UDD, so I'd like to make > sure it's really useful before implementing this. Several use cases. My original motivation in filing that bug is that I'd like to search for files shipped in packages with user:group other than root:root, or with modes other than 644 or 755 (as appropriate for file/directory). Right now, that would require downloading and unpacking every package. That actually suggests a useful compression technique: for owner, group, and mode, you could provide a table or tables that *only* list unusual files/directories that have user:group other than root:root or a mode other than 644/755. The rest of the data could then be synthesized with an appropriate view. That would eliminate the metadata entries for the vast majority of the files in Debian packages, while transparently providing all the same data. I'd also like to search for packages that contain empty directories (easily found by looking for directories without containing files) and correlate that with whether any other package ships files in that directory (or if it's provided solely for users). And I'd like to search for things like filename conflicts and compare them to package metadata; for instance, do packages that ship the same filename conflict or not, and do the versions of the conflict match the versions that ship the same file? (That won't be perfect, since it can't take diversions into account, which are unfortunately still programmatic in maintainer scripts rather than being declarative.) - Josh Triplett -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780745: root-system: FTBFS on mips64el - Explicitly required Kerberos5 dependencies not fulfilled
Source: root-system Version: 5.34.19+dfsg-1.2 Severity: important Tags: patch Hi, root-system FTBFS on mips64el with the error: > Checking for krb5.h ... /usr/include > Checking for krb5.h redirect ... /usr/include/krb5/krb5.h > Checking for krb5_c_valid_cksumtype in krb5.h ... yes > Checking for valid_cksumtype in krb5.h ... no > Checking for libk5crypto ... /usr/lib/mips64el-linux-gnuabi64 > Checking whether we're using MIT Kerberos ... yes > Checking for krb5_c_valid_cksumtype in > /usr/lib/mips64el-linux-gnuabi64/libk5crypto.so ... no > Checking for valid_cksumtype in > /usr/lib/mips64el-linux-gnuabi64/libk5crypto.so ... no > Either 'krb5_c_valid_cksumtype' or 'valid_cksumtype' are available; disabling > krb5 > Explicitly required Kerberos5 dependencies not fulfilled > make: *** [config.status] Error 1 This is because it tries to compile the test program with -mabi=32 which fails at the linker stage because you can't mix 32-bit and 64-bit code (the kerberos libraries were the 64-bit files). I've added a patch which adds the linuxmips64 architecture (which was partially there already) which fixes this for me. The 79-mips64el.patch can be dropped into debian/patches which does this. I haven't added any mips64 arch detection because it's a bit more complicated since 'uname -r' doesn't work - you would have to run the C compiler and test for some defines. This is a bit of a catch 22 since the 'Makefile.' files are needed to specify where the compiler is. The mips64el-drules.patch is a simpler way but will only work in the Debian package. Thanks, James --- a/config/ARCHS +++ b/config/ARCHS @@ -22,6 +22,7 @@ linuxhppafor HPPA Linux with linuxia64ecc for Itanium Linux with Intel icc linuxia64gcc for Itanium Linux with gcc >= 3 linuxmipsfor MIPS Linux with gcc +linuxmips64 for MIPS n64 Linux with gcc linuxppcgcc for PPC Linux with gcc linuxppc64gccfor PPC 64 Linux with gcc >= 3 linuxx8664gccfor x86-64 Linux with gcc >= 3.x --- a/config/Makefile.linuxmips64 +++ b/config/Makefile.linuxmips64 @@ -20,17 +20,15 @@ CC= gcc CXXFLAGS = -pipe -Wall -W -Woverloaded-virtual \ -fPIC $(EXTRA_CXXFLAGS) CFLAGS= -pipe -Wall -W -fPIC $(EXTRA_CFLAGS) -# G__64BIT should only be defined if mips is truly 64bit. Check for -# example that _ABI64 is defined or so. CINTCXXFLAGS = -pipe -Wall -W -Woverloaded-virtual \ -fPIC $(EXTRA_CXXFLAGS) \ -DG__REGEXP -DG__UNIX -DG__SHAREDLIB \ -DG__OSFDLL -DG__ROOT -DG__REDIRECTIO \ --DG__STD_EXCEPTION +-DG__STD_EXCEPTION -DG__64BIT CINTCFLAGS= -pipe -Wall -W -fPIC $(EXTRA_CFLAGS) \ -DG__REGEXP -DG__UNIX -DG__SHAREDLIB \ -DG__OSFDLL -DG__ROOT -DG__REDIRECTIO \ --DG__STD_EXCEPTION +-DG__STD_EXCEPTION -DG__64BIT COMPILER = gnu # Linker: --- a/config/root-config.in +++ b/config/root-config.in @@ -266,8 +266,14 @@ linux) ;; linuxmips) # Linux on mips with gcc >= 3.x - auxcflags="-mapi=32" - auxldflags="-mapi=32" + auxcflags="-mabi=32" + auxldflags="-mabi=32" + auxlibs="-lm -ldl -rdynamic" + ;; +linuxmips64) + # Linux on mips n64 + auxcflags="" + auxldflags="" auxlibs="-lm -ldl -rdynamic" ;; linuxhppa) --- a/debian/rules +++ b/debian/rules @@ -25,6 +25,8 @@ export CFLAGS EXTRA_LDFLAGS DEB_HOST_MUL ifeq ($(DEB_HOST_ARCH_CPU),powerpc) PLATFORM = linux +else ifeq ($(DEB_HOST_ARCH_CPU),mips64el) +PLATFORM = linuxmips64 else PLATFORM = endif signature.asc Description: This is a digitally signed message part
Bug#765577: (no subject)
Am 18.03.2015 um 18:15 schrieb Faidon Liambotis: > Another less arbitrary/racy workaround I suggesed was a grep near the > top of write_net_rules' write_rule() function. Since write_rule() > operates under a lock, this would completely eliminate any kind of race > here. I pitched this to Marco but he wasn't thrilled with the idea -- he > said he'd prefer finding the root cause. I've done the change and tested > it anyway, though, and it successfully aleviates this issue: I'm with Marco here. Before adding any workarounds, we need to understand what the underlying problem is. Otherwise we are adding cruft which nobody understands anymore a few years from now. Since I can't reproduce the issue and already have trouble keeping up with other bug reports, further investigation needs to be done by someone else. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#780744: miro: should Recommend: libavahi-compat-libdnssd1
Package: miro Version: 6.0-1 Severity: normal When starting miro without libavahi-compat-libdnssd1 installed it pops up a warning that it should be installed to maximize functionality. Thus there should be a recommendation on this library. -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.0.0-rc3-next-20150316 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages miro depends on: ii gstreamer0.10-plugins-bad 0.10.23-7.4 ii gstreamer0.10-plugins-base 0.10.36-2 ii gstreamer0.10-plugins-good 0.10.31-3+nmu4+b1 ii gstreamer0.10-x 0.10.36-2 ii libatk1.0-0 2.14.0-1 ii libav-tools 6:11.3-1 ii libavcodec566:11.3-1 ii libavformat56 6:11.3-1 ii libavutil54 6:11.3-1 ii libc6 2.19-17 ii libcairo2 1.14.0-2.1 ii libfontconfig1 2.11.0-6.3 ii libfreetype62.5.2-4 ii libgcc1 1:5-20150307-1 ii libgdk-pixbuf2.0-0 2.31.3-1 ii libglib2.0-02.43.91-1 ii libgtk2.0-0 2.24.25-3 ii libjavascriptcoregtk-1.0-0 2.4.8-1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpangoft2-1.0-0 1.36.8-3 ii libsoup2.4-12.49.91.1-1 ii libsqlite3-03.8.8.3-1 ii libstdc++6 5-20150307-1 ii libtag1c2a 1.9.1-2.1 ii libwebkitgtk-1.0-0 2.4.8-1 ii libx11-62:1.6.2-3 ii miro-data 6.0-1 ii python 2.7.8-4 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-gst0.10 0.10.22-3 ii python-gtk2 2.24.0-4 ii python-libtorrent 0.16.18-1 ii python-mutagen 1.25.1-1 ii python-pycurl 7.19.5-3 ii python-pysqlite22.6.3-3 ii python-support 1.0.15 ii python-webkit 1.1.8-3 ii zlib1g 1:1.2.8.dfsg-2+b1 miro recommends no packages. Versions of packages miro suggests: pn ffmpeg2theora pn gstreamer0.10-ffmpeg pn gstreamer0.10-plugins-ugly ii libavahi-compat-libdnssd1 0.6.31-4+b2 ii python-notify 0.1.1-4 pn ttf-dejavu -- 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#780633: f3: please include f3detect and f3fix
Package: f3
Version: 5.0-1
Followup-For: Bug #780633
Hello,
Attaching patch.
I tested the experimental tools when built from the source locally but
not the packaged version.
Thanks
-- 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 f3 depends on:
ii libc6 2.19-17
f3 recommends no packages.
f3 suggests no packages.
-- no debconf information
diff -Nru f3-5.0/debian/changelog f3-5.0/debian/changelog
--- f3-5.0/debian/changelog 2015-02-23 17:32:29.0 +0100
+++ f3-5.0/debian/changelog 2015-03-17 08:43:09.0 +0100
@@ -1,3 +1,10 @@
+f3 (5.0-1ex1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Add experimental binaries.
+
+ -- Michal Suchanek Tue, 17 Mar 2015 08:42:35 +0100
+
f3 (5.0-1) experimental; urgency=medium
* New upstream release.
diff -Nru f3-5.0/debian/control f3-5.0/debian/control
--- f3-5.0/debian/control 2014-10-26 22:59:36.0 +0100
+++ f3-5.0/debian/control 2015-03-17 08:44:38.0 +0100
@@ -2,7 +2,7 @@
Section: utils
Priority: optional
Maintainer: Joao Eriberto Mota Filho
-Build-Depends: debhelper (>= 9)
+Build-Depends: debhelper (>= 9), libparted-dev, libudev-dev
Standards-Version: 3.9.6
Homepage: http://oss.digirati.com.br/f3
Vcs-Browser: http://anonscm.debian.org/cgit/collab-maint/f3.git
diff -Nru f3-5.0/debian/install f3-5.0/debian/install
--- f3-5.0/debian/install 2014-09-19 23:59:59.0 +0200
+++ f3-5.0/debian/install 2015-03-18 18:25:28.0 +0100
@@ -1,4 +1,6 @@
f3read usr/bin
f3write usr/bin
+f3fix usr/bin
+f3probe usr/bin
f3write.h2w usr/share/f3
log-f3wr usr/share/f3
diff -Nru f3-5.0/debian/patches/Fix_crash_when_card_reader_lacks_serial_number f3-5.0/debian/patches/Fix_crash_when_card_reader_lacks_serial_number
--- f3-5.0/debian/patches/Fix_crash_when_card_reader_lacks_serial_number 1970-01-01 01:00:00.0 +0100
+++ f3-5.0/debian/patches/Fix_crash_when_card_reader_lacks_serial_number 2015-03-18 18:26:12.0 +0100
@@ -0,0 +1,60 @@
+Udev attributes can be null.
+ -- Michal Suchanek
+Index: f3-5.0/libdevs.c
+===
+--- f3-5.0.orig/libdevs.c 2014-12-24 16:10:47.0 +0100
f3-5.0/libdevs.c 2015-03-18 18:20:07.946835419 +0100
+@@ -418,6 +418,16 @@
+ return mon;
+ }
+
++static int compare_udev_attr(struct udev_device *usb_dev, const char * attr, const char * cmp)
++{
++const char * value = udev_device_get_sysattr_value(usb_dev, attr);
++if (!value && !cmp) return 0;
++if (!value) return 1;
++if (!cmp) return -1;
++return strcmp(value, cmp);
++}
++
++
+ static char *wait_for_add_action(struct udev *udev,
+ const char *id_vendor, const char *id_product, const char *serial)
+ {
+@@ -439,12 +449,9 @@
+
+ usb_dev = map_dev_to_usb_dev(dev);
+ if (usb_dev &&
+- !strcmp(udev_device_get_sysattr_value(usb_dev,
+-"idVendor"), id_vendor) &&
+- !strcmp(udev_device_get_sysattr_value(usb_dev,
+-"idProduct"), id_product) &&
+- !strcmp(udev_device_get_sysattr_value(usb_dev,
+-"serial"), serial)) {
++ !compare_udev_attr(usb_dev, "idVendor", id_vendor) &&
++ !compare_udev_attr(usb_dev, "idProduct", id_product) &&
++ !compare_udev_attr(usb_dev, "serial", serial)) {
+ devnode = strdup(udev_device_get_devnode(dev));
+ assert(devnode);
+ done = true;
+Index: f3-5.0/f3fix.c
+===
+--- f3-5.0.orig/f3fix.c 2014-12-24 16:10:47.0 +0100
f3-5.0/f3fix.c 2015-03-18 18:24:25.562844530 +0100
+@@ -74,14 +74,14 @@
+ args->disk_type = ped_disk_type_get(arg);
+ if (!args->disk_type)
+ argp_error(state,
+-"Disk type `%s' is not supported; use --list-disk-types to see the supported types");
++"Disk type `%s' is not supported; use --list-disk-types to see the supported types", arg);
+ break;
+
+ case 'f':
+ args->fs_type = ped_file_system_type_get(arg);
+ if (!args->fs_type)
+ argp_error(state,
+-"File system type `%s' is not supported; use --list-fs-types to see the supported types");
++"File system type `%s' is not supported; use --list-fs-types to see the supported types", arg);
+ break;
+
+ case 'b':
diff -Nru f3-5.0/debian/patches/Makefile f3-5.0/debian/patches/Makefile
--- f3-5.0/debian/patches/Makefile 2015-02-23 15:35:00.0 +0100
+++ f3-5.0/debian/patches/Makefile 2015-03-17 08:32:35.0 +0100
@@ -3,9 +3,9 @@
Last-Update: 2015-02-23
Index: f3-5.0/Makefile
===
f3-5.0.orig/Makefile
-+++ f3-5.0/Makefil
Bug#750999: qa.debian.org: I would be usefull have a comment field in dmd
On 15/07/14 at 11:12 +0200, Leo Iannacone wrote: > Try to go to a page with a TODO list, mine[0] for instance, and to run > the attached JS code in a browser console just to see what I mean... > > Obviously this code works only for localStorage, which means only the > user can see his own comments. Having a database entry for this could > be more useful. I wonder if there are external services that could serve as data stores for the comments? Something like disqus, but simpler. Lucas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780020: [UDD] bugs.cgi: YAML contains raw HTML and "ruby objects"
Hi Niels, bugs.cgi started as a huge amount of spaghetti code, and is slightly become better. On 08/03/15 at 10:36 +0100, Niels Thykier wrote: > Package: qa.debian.org > Severity: minor > > Hi, > > The generated YAML contains raw HTML and Ruby specific objects, example > (from the query in [1]): > > """ > - id: 644047 > package: gdm3 > [...] > title: ! 'gdm3: /etc/default/locale ignored, locale set to C, breaks > gnome-terminal' > last_modified: !ruby/object:DateTime 2015-03-05 22:36:21.0 +00:00 > [...] > chints: ! 'http://release.debian.org/britney/hints/nthykier"; > title="3.14.1-4 > nthykier #2015-03-06 > > # #644047, #774889">unblock ' > [...] > caffected: (T) > """ > > At least, chints and caffected is basically just raw HTML dumped in a > YAML stream. The last_modified is a seriraled Ruby object. The rest > of the fields are just there fore reference and to make it easier to > find the example (as long as it lasts). > > For me the issue with: > * Raw HTML is that it is a poor machine parsable representation of the data. >- For caffected, a list of the distribution names would be better (e.g. > ["testing"]). >- For chints, it would probably need to be split into a list of > dictionaries with the following fields: > - hinter => "nthykier" in this example > - hint (or hint name/type) => "unblock" in this example > - hinter_comment => The contents of the "title" attribute > * Ruby objects is that the client may not be written in Ruby. In such > cases, we have "massage" the >data to parse it with conventional parsers of other languages. >- Note, I certainly do not mind that the YAML uses Ruby objects in > addition to regular values. > Alternatively, it could be an "opt-in"/"opt-out" feature to get ruby > objects. > > NB: Feel free to apply a healthy amount of bikeshedding to the above. > The proposed formats are only meant as a suggestion. For last_modified, I've added a new 'last_modified_string' field that shows the date as text. Should be easily parsable by about everything. For caffected, the raw data is already available: affects_stable: false affects_testing: true affects_unstable: false affects_experimental: true For cdeferred, it's probably easy enough to parse right now. For chints, I did not manage to output something clean, for strange reasons. bugs.cgi needs a fall rewrite (with a design similar to DMD). In the meantime, it's not possible to fix this properly. Lucas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#750863: Please include package contents information
On 07/06/14 at 11:10 -0700, Josh Triplett wrote: > Package: qa.debian.org > Severity: wishlist > User: qa.debian@packages.debian.org > > It'd be quite handy to have package contents information in UDD. > > Columns, in addition to a unique package ID foreign-keyed to the > packages table: > > filename > owner > group > mode Hi Josh, What is your use case for that? This would add quite a lot of information to UDD, so I'd like to make sure it's really useful before implementing this. Lucas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780241: mirror submission for debian.mirror.digitalpacific.com.au
Control: tag -1 +moreinfo Hi, Thank you for mirroring Debian. A quick question and comment for you to address please. Your trace directories indicate multiple upstream sources while you list only one, could you please clarify this? The archive should be listed as /debian/. On Wed, 11 Mar 2015 00:48:38 + "Matthew Taylor" wrote: > Package: mirrors > Severity: wishlist > > Submission-Type: new > Site: debian.mirror.digitalpacific.com.au > Type: leaf > Archive-architecture: ALL amd64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc s390x sparc > Archive-http: /debian-archive/ > Archive-rsync: debian-archive/ > Backports-http: /debian-backports/ > Backports-rsync: debian-backports/ > CDImage-http: /debian-cd/ > CDImage-rsync: debian-cd/ > IPv6: no > Archive-upstream: mirror.aarnet.edu.au > Backports-upstream: mirror.as24220.net > CDImage-upstream: ftp.iinet.net.au > Updates: four > Maintainer: Matthew Taylor > Country: AU Australia > Location: Sydney, Australia > Sponsor: Digital Pacific http://www.digitalpacific.com.au/ > Comment: Server is on a 1Gbit link in Sydney, Australia. Best regards, Donald Norwood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780743: fitscut: Package description possibly missing a piece
Package: fitscut Severity: minor Hi, the first sentence of the package description currently reads: «fitscut is designed to FITS, PNG, and JPEG output types are supported.» and it is not very clear. Seeing the description of the tool on its web page[1] I strongly suspect that there is a piece missing and that it should have been: «fitscut is designed to extract cutouts from FITS image format files. FITS, PNG, and JPEG output types are supported.» Thanks, beatrice [1] http://acs.pha.jhu.edu/general/software/fitscut/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765577: (no subject)
severity 765577 serious
thanks
On Wed, Feb 25, 2015 at 03:24:08PM +, Filippo Giunchedi wrote:
> FWIW we're running into the same bug with jessie installer, passing
> 'debug' at boot apparently is enough to not trigger the race with good
> success rate.
Filippo and I both work for the Wikimedia Foundation, where this is
affecting us on dozens of systems.
I tried to debug this extensively and had a chat with Marco d'Itri on
IRC. It's both mine & Marco's opinion that this is an RC bug, thus
elevating this to serious. Unfortunately, Marco told me that he won't
able to tackle this and suggested to reply to this bug report so that
the other udev maintainers can help out.
The result of my own investigation is (not speaking for Marco):
It's clear that there's some race condition happening here both because
there are reports of it happening sporadically (not in my case, though)
and because setting d-i to debug mode fixes it.
Therefore, the operating theory is that multiple events for the same
"add" event are triggered. This race is supposed to be handled, as:
a) write_net_rules takes a lock before writing anything -- it's also
evident this happens, as the duplicate entries have ethNs that are
numerically ascending and not the same for the same card.
b) 75-persistent-net-generator.rules is supposed to be idempotent, as it
bails out early (3rd line) for interfaces that already have a NAME set.
For the ones that don't, it also sets NAME right after the
write_net_rules invocation.
However this still leaves room for a race: write_net_rules is *not*
idempotent and hence if 75-persistent-net-generator.rules gets called
twice in very quick succession, before write_net_rules gets a chance to
finish and name the interface, then an interface will be named twice,
with a different name (and hence, eth0 will be renamed to e.g. eth2).
It's still unknown to me why this is a regression.
I've tried the following, under /lib/debian-installer/start-udev:
1) Adding a "udevadm settle || true" right after the "udevadm trigger".
2) Adding a "sleep 15" before "udevadm trigger"
3) Adding a "sleep 15" (or 3) *after* "udevadm trigger".
Surprisingly, of these three, only (3) worked around the bug.
Another less arbitrary/racy workaround I suggesed was a grep near the
top of write_net_rules' write_rule() function. Since write_rule()
operates under a lock, this would completely eliminate any kind of race
here. I pitched this to Marco but he wasn't thrilled with the idea -- he
said he'd prefer finding the root cause. I've done the change and tested
it anyway, though, and it successfully aleviates this issue:
diff --git a/debian/extra/write_net_rules b/debian/extra/write_net_rules
index 4379792..fbd1230 100644
--- a/debian/extra/write_net_rules
+++ b/debian/extra/write_net_rules
@@ -60,6 +60,9 @@ write_rule() {
local name="$2"
local comment="$3"
+ # workaround potential races, #765577
+ if grep -q -F $match $RULES_FILE then return; fi
+
{
if [ "$PRINT_HEADER" ]; then
PRINT_HEADER=
Thanks,
Faidon
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780742: sensible-utils: Please install .desktop files for editor and pager
Package: sensible-utils Version: 0.0.9 Severity: wishlist It would be handy if sensible-editor and sensible-pager appeared as defined applications so that they might be used from "Open With" dialogues in file and web browsers for those times when you would prefer a terminal-based editor or pager be opened. For GNOME, files similar to the following might do the trick, however an experienced GNOME administrator might be consulted to ascertain how to handle the case where sensible-editor might have been set to a program that has an X11 mode as well as a terminal mode. /usr/share/applications/sensibleeditor.desktop: [Desktop Entry] Name=Sensible Default Editor Exec=/usr/bin/sensible-editor %U StartupNotify=true Terminal=true Type=Application Icon=utilities-terminal /usr/share/applications/sensiblepager.desktop: [Desktop Entry] Name=Sensible Default Pager Exec=/usr/bin/sensible-pager StartupNotify=true Terminal=true Type=Application Icon=utilities-terminal -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (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: 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#779142: mirror submission for mirror.uta.edu.ec
Control: tag -1 +moreinfo Hi Ernesto, Your copy of the archive has not been updated since: 2015-Feb-24 18:02:31 Please correct the update cycle and report back when you can. On Tue, 24 Feb 2015 19:37:28 + "Ernesto Perez Estevez" wrote: > Package: mirrors > Severity: wishlist > > Submission-Type: new > Site: mirror.uta.edu.ec > Type: leaf > Archive-architecture: ALL amd64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc s390x sparc > CDImage-http: /debian-cd/ > IPv6: no > CDImage-upstream: sft.if.usp.br > Updates: four > Maintainer: Ernesto Perez Estevez > Country: EC Ecuador > Location: Ambato > Sponsor: Universidad Tecnica de Ambato http://www.uta.edu.ec > > Best regards, Donald Norwood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780741: redland-bindings: please support python3
Source: redland-bindings
Severity: wishlist
Tags: patch
Dear Maintainer,
It would be nice to have python3 compatible packages for librdf.
There's only a few minor changes to the build process to build the library.
Diane Trout
-- System Information:
Debian Release: 8.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (100,
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff --git a/debian/control b/debian/control
index 41fe042..1c5840d 100644
--- a/debian/control
+++ b/debian/control
@@ -2,7 +2,7 @@ Source: redland-bindings
Section: devel
Priority: optional
Maintainer: Dave Beckett
-Build-Depends: debhelper (>= 5.0.37.2), autotools-dev, libtool (>= 1.5), perl (>= 5.8.1-2), python-all-dev (>= 2.6.6-3~), ruby2.1, ruby2.1-dev, librdf0-dev (>= 1.0.14), swig (>= 2.0.0), php5-cli, php5-dev
+Build-Depends: debhelper (>= 5.0.37.2), autotools-dev, libtool (>= 1.5), perl (>= 5.8.1-2), python-all-dev (>= 2.6.6-3~), python3-all-dev (>= 3.2), ruby2.1, ruby2.1-dev, librdf0-dev (>= 1.0.14), swig (>= 2.0.0), php5-cli, php5-dev
X-Python-Version: >= 2.6
Standards-Version: 3.9.5
Homepage: http://librdf.org/
@@ -22,9 +22,23 @@ Architecture: any
Section: python
Depends: ${misc:Depends}, ${shlibs:Depends}, ${python:Depends}
Provides: ${python:Provides}
-Description: Python language bindings for the Redland RDF library
+Description: Python 2 language bindings for the Redland RDF library
This package contains the files needed to use the Redland Resource
Description Framework (RDF) library in Python programs.
+ .
+ This contains the Python 2 version.
+Homepage: http://librdf.org/docs/python.html
+
+Package: python3-librdf
+Architecture: any
+Section: python
+Depends: ${misc:Depends}, ${shlibs:Depends}, ${python:Depends}
+Provides: ${python:Provides}
+Description: Python 3 language bindings for the Redland RDF library
+ This package contains the files needed to use the Redland Resource
+ Description Framework (RDF) library in Python programs.
+ .
+ This contains the Python 3 version.
Homepage: http://librdf.org/docs/python.html
Package: librdf-ruby
diff --git a/debian/patches/series b/debian/patches/series
deleted file mode 100644
index e69de29..000
diff --git a/debian/rules b/debian/rules
index 5ad2d1c..1ee3186 100755
--- a/debian/rules
+++ b/debian/rules
@@ -44,8 +44,10 @@ export PHP_CONFIG
# Python versions from constraints in X-Python-Version in debian/control
PYVERS= $(shell pyversions -r)
+PY3VERS= $(shell py3versions -r)
# Default python
PYDEF= $(shell pyversions -d)
+PY3DEF= $(shell py3versions -d)
# Perl vendorarch gets dynamic with 5.20
PERL_ARCHLIB := $(shell perl -MConfig -e 'print $$Config{vendorarch}')
@@ -97,6 +99,7 @@ clean1:
-cd python && $(MAKE) clean
-cd python && rm -f Redland_wrap.c Redland.py
+ -cd python && rm -rf __pycache__
-cd ruby && $(MAKE) clean
-cd ruby && rm -f redland_wrap.c
@@ -126,6 +129,17 @@ install: build
done
find $(CURDIR)/debian/python-librdf/usr -name "*.py[co]" -exec rm -f {} \;
+ cd python; \
+ for python in $(PY3VERS); do \
+ pylib=$$($$python -c 'from distutils import sysconfig; print(sysconfig.get_python_lib())'); \
+ pyext=$$($$python -c 'from distutils import sysconfig; print(sysconfig.get_config_var("EXT_SUFFIX"))'); \
+ PYTHON=$$(echo $$python | sed "s/$(PY3DEF)/python3/"); \
+ PYTHON=$$PYTHON make install DESTDIR=$(CURDIR)/debian/python3-librdf pythondir=$$pylib PYTHON_INCLUDES=-I/usr/include/$$python PYTHON_LIBEXT=$$pyext; \
+ $(MAKE) clean >/dev/null 2>&1; \
+ done
+ find $(CURDIR)/debian/python-librdf/usr -name "*.py[co]" -exec rm -f {} \;
+
+
cd ruby ; \
$(MAKE) install DESTDIR=$(CURDIR)/debian/librdf-ruby
@@ -154,6 +168,7 @@ binary-arch: build install
dh_makeshlibs
dh_perl
dh_python2 -ppython-librdf
+ dh_python3 -ppython3-librdf
dh_installdeb
dh_shlibdeps
echo "php:Depends=phpapi-$(shell $(PHP_CONFIG) --phpapi)" >> \
Bug#780728: systemd: fsck checks root partition and superblock is rewritten on every boot
Am 18.03.2015 um 17:51 schrieb Michael Biebl: > See the initramfs-tools changelog. Or specificially /usr/share/doc/initramfs-tools/NEWS.Debian.gz resp. http://anonscm.debian.org/cgit/kernel/initramfs-tools.git/tree/debian/NEWS#n1 -- 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#780740: debian-edu-config: 099-mount-cdrom script should be removed to avoid possible conflicts with ltsp-client-builder.udeb
Package: debian-edu-config Version: 1.817 Severity: important Tags: patch The script share/ltsp/plugins/ltsp-build-client/Debian-custom/099-mount-cdrom has been used to replace the related Debian/099-mount-cdrom from ltsp. This script has been removed in jessie, cdrom mounting ensured by ltsp-client-builder postinst. So 099-mount-cdrom should be removed to avoid possible conflicts. diff --git a/Makefile b/Makefile index d450756..7671178 100644 --- a/Makefile +++ b/Makefile @@ -439,7 +439,6 @@ install: install-testsuite share/ltsp/plugins/ltsp-build-client/Debian-custom/050-nbdquery \ share/ltsp/plugins/ltsp-build-client/Debian-custom/095-umount-error \ share/ltsp/plugins/ltsp-build-client/Debian-custom/098-etckeeper \ - share/ltsp/plugins/ltsp-build-client/Debian-custom/099-mount-cdrom \ ; do \ $(INSTALL_DATA) $$f $(DESTDIR)/usr/$$f ; \ done diff --git a/share/ltsp/plugins/ltsp-build-client/Debian-custom/099-mount-cdrom b/share/ltsp/plugins/ltsp-build-client/Debian-custom/099-mount-cdrom deleted file mode 100644 index 46bd33d..000 --- a/share/ltsp/plugins/ltsp-build-client/Debian-custom/099-mount-cdrom +++ /dev/null @@ -1,28 +0,0 @@ -# Replacement for the Debian/099-mount-cdrom script in the official ltsp -# package. Having the file here is a workaround for #606313, -# triggered when using USB sticks with CD isos. -case "$MODE" in -commandline) -add_option "mount-cdrom" "`eval_gettext "mounts CDROM before installation"`" "advanced" "false" -;; -configure) -if [ -n "$option_mount_cdrom_value" ]; then -MOUNT_CDROM="true" -fi -;; -before-install) -if [ "$MOUNT_CDROM" = "true" ]; then -if mount /media/cdrom ; then -: -else -echo "unble to mount cdrom, trying to continue" -MOUNT_CDROM=false -fi -fi -;; -finalization) -if [ "$MOUNT_CDROM" = "true" ]; then -umount /media/cdrom -fi -;; -esac Wolfgang signature.asc Description: Digital signature
Bug#748223: UDD: DMD - "uscan returned an error" while fixed in PTS
On 15/05/14 at 14:11 +0200, Leo Iannacone wrote: > Package: qa.debian.org > Severity: normal > > Dear Maintainer, > there is some problem with watch checks. > > It this dmd query: > > http://udd.debian.org/dmd/?email1=&email2=&email3=&packages=node-jsconfig+node-jsdom+node-postgres+pdf.js+rainbow.js+step.js+wax.js&ignpackages=&format=html#todo > > packages node-jsconfig, node-jsdom, node-postgres, pdf.js, > rainbow.js, step.js, wax.js report "error" in the upstream column. > > While, according with PTS page, watch check is fine: > > * http://packages.qa.debian.org/node-jsconfig > * http://packages.qa.debian.org/node-jsdom > * http://packages.qa.debian.org/node-postgres > * http://packages.qa.debian.org/pdf.js > * http://packages.qa.debian.org/rainbow.js > * http://packages.qa.debian.org/step.js > * http://packages.qa.debian.org/wax.js Hi, One of those was failing because of a uscan corner case (now fixed in UDD). The other ones are failing because githubredir.debian.net is dead. DMD now displays the uscan warning/error when you leave your mouse on 'error', which makes it easier to debug. Lucas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780675: systemd: segfault in systemd when running systemctl daemon-reload
Control: tags -1 = confirmed
Control: severity -1 serious
Am 18.03.2015 um 16:29 schrieb Robert Pumphrey:
> 2. put the following into /etc/init.d/firewall
> #!/bin/bash
> ### BEGIN INIT INFO
> # Provides: iptables
> # Required-Start:$network $remote_fs $syslog
> # Required-Stop: $network $remote_fs $syslog
> # Should-Start: iptables
> # Default-Start: 2 3 4 5
> # Default-Stop: 0 1 6
> ### END INIT INFO
>
> #
> ###
> ### Firewall rules
> ###
> #
>
> case "$1" in
> start)
> echo "start"
> ;;
> stop)
> echo "stop"
> ;;
> restart)
> echo "restart"
> ;;
> *)
> echo "Usage: /etc/init.d/firewall {start|stop|restart}"
> exit 1
> ;;
> esac
>
> 3. chmod u+x /etc/init.d/firewall
> 4. update-rc.d firewall defaults
> 5. reboot
> 6. login as root
> 7. systemctl --system daemon-reload
>
> then we see:
>
> Message from syslogd@joule at Mar 18 14:10:40 ...
> kernel:[ 27.526029] systemd[1]: segfault at b739cdac ip b739cdac sp
> bf9af36c error 15
> Failed to execute operation: Connection reset by peer
>
...
>
> Also note that the problem is not reproducible if the Provides: and
> Should-Start: name match the init script name, so I guess mismatch in
> the script name and header is at the root of the problem.
Thanks for sharing the contents of the file. I can confirm the crash and
we have enough information now to debug this issue properly.
Marking the bug accordingly.
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
Bug#748223: [ol...@debian.org: UDD's DEHS reimplementation, FTP upstreams and GPG signature checking]
retitle 748223 UDD: uscan doesn't understand pgpsigurlmangle thanks On 20/05/14 at 07:47 +0200, Lucas Nussbaum wrote: > UDD's DEHS reimplementation seems to fail for two distinct usecases: FTP > connections that need active mode are failing (for instance a lot of the KDE > team watch files are failing), and the uscan version installed on ullmann > doesn't understand the gpg signature checking and fails with an error. Both > those issues make the (very useful) DMD a bit redder than necessary. > > The first issue can be solved two ways: enabling the conntrack on ftp > connections in the firewall, or adding --pasv to the uscan invocation (which > will fail if the ftp server doesn't support passive mode, but that's a bit > crazy anyway). --pasv added to the uscan call, so this is fixed now. > The second issue would be fixed by using a backported uscan on ullmann. That > might have other ramifications though, and I can't clean up afterwards so I > won't request it directly. This only fails for 82 packages, according to: select source, warnings from upstream where warnings ~ 'pgp' and status = 'error'; This will be magically fixed when ullmann will be upgraded to jessie. (just copying the uscan script from a jessie system doesn't work, as it also uses some stuff from the devscripts lib) Lucas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#173851: lynx: asks me about cookie again when wanting to see source
Yes I have tried with google. I hit "\" to see source and I hit "\" again to come back to the google main page. It works fine here, he doesn't ask me again about cookie. Is it the good way to reproduce it? regards Denis Briand signature.asc Description: Digital signature
Bug#779142: mirror submission for mirror.uta.edu.ec
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 18/03/15 11:05, Donald Norwood wrote: > Control: tag -1 +moreinfo > > > > Hi Ernesto, > > Your copy of the archive has not been updated since: 2015-Feb-24 > 18:02:31 > > Please correct the update cycle and report back when you can. hi we have added debian-cd to our sync process. The trace file is now correct: [replica@mirror ~]$ cat mirror/debian-cd/project/trace/mirror.uta.edu.ec Wed 18 Mar 16:21:21 UTC 2015 [replica@mirror ~]$ please check thanks! epe > > > On Tue, 24 Feb 2015 19:37:28 + "Ernesto Perez Estevez" > wrote: >> Package: mirrors Severity: wishlist >> >> Submission-Type: new Site: mirror.uta.edu.ec Type: leaf >> Archive-architecture: ALL amd64 armel armhf hurd-i386 i386 > kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc s390x sparc >> CDImage-http: /debian-cd/ IPv6: no CDImage-upstream: >> sft.if.usp.br Updates: four Maintainer: Ernesto Perez Estevez >> Country: EC Ecuador Location: >> Ambato Sponsor: Universidad Tecnica de Ambato >> http://www.uta.edu.ec >> >> > > > Best regards, > > Donald Norwood > - -- - -- CEDIA La principal herramienta de Investigación en el Ecuador. Calle La Condamine 12-109 "Casa Rivera". Cuenca - Ecuador Telf: (593) 7405 1000 Ext. 4220/4223 i...@cedia.org.ec www.cedia.org.ec -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJVCakEAAoJEI8SQ0eoZD/XHOoQAKL2m/MnZvvxS8VLm5ZG88Qg yEfk6chpg3x+IkuXC5DnM2Ie1vukJOdYDslseM1I9mgO275DiOnuTanna2sdNgnu HXkOBXel8j458cfRc4SYUBl3eRkjIy7xYJFFAtXXXPlL0A82NjLlR8h+NBXOTnwG lwV/5zvPKNpObhuxHm/j3+pgx2cdfxv9spc7d9dxgyhMHzQSRFpkn/wJ1gam38oz Bjy9It1ygPz3H5G7RAYWIEX9qK7jgw2IKcsJ0KjCcMXXBiCBO+e6Mr5IFwPbnx9B it3W5hOoDPlaNq3RUpYdWM0Y8mJfhAFS5jQJ9t/hNP8jx3/CMuPqeJx9EFftO/Hm 3Fgj21+ETOWGNrKbeyjDYqF5qHJ0zpvSdhfTDMaP24ARyq1FcBJah6Y+VexxC1g6 N4GoAFmZai8xSQGUh5RbBp1NjwrcUoWD09TicUEA4BzK+MD6SAO7Xp1+/tSIGJs1 nJvv50SdBQ05uUacRBlt6O4J4puj40pmSywNEPyBOBC1HkRUUpnQeSoQIfk+Ato9 j3xfYE3vS+kmCWP/XL4+t92ZQfg3+U6XJqcpfVlpiYVJv1g+CP18lVI/WJxOB3UL nIumwGdfqsBEFo+HW9PLyQSe6rjZne7oEbGIvhEYftBJZWq3dTfvIib/zK3RshGy zXZ0BO1XVEY7QSNuxHcX =K0LN -END PGP SIGNATURE- Email secured by Check Point -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
