Bug#622394: systemd: nfs-common and rpcbind unit files to fix systemd NFS issues properly
On 2015-01-17 02:42, Simon McVittie wrote: > Control: clone 622394 -2 -3 > Control: retitle -2 NFS mounts from /etc/fstab do not work > Control: submitter -2 m...@mattgrant.net.nz > Control: retitle -3 NFS exports fail due to rpcbind not starting before > nfs-common and nfs-kernel-server > Control: submitter -3 m...@mattgrant.net.nz > Control: tags -3 moreinfo unreproducible > Control: user release.debian@packages.debian.org > Control: usertag -2 - jessie-is-blocker > Control: usertag -3 - jessie-is-blocker > Control: tags 622394 unreproducible > > On 16/01/15 21:27, Niels Thykier wrote: >> Can anyone provide me with an up to date status on this bug? It seems >> to be a mismatch of no less than 3 different bugs if I understand >> Simon's comment in message #41 correctly (see [1] for the full text). > > That is my understanding, but I am not an expert on this package (I > don't use NFS myself). > > I was hoping for a response from a maintainer and/or bug reporters, > but apparently I'm not going to get one, so... cloning it is. I hope > I got the usertags and stuff right - please check. > The new ones do not appear on: https://udd.debian.org/bugs/?release=jessie_and_sid&patch=ign&merged=ign&done=ign&rtjessie-is-blocker=only&fnewerval=7&flastmodval=7&rc=1&ctags=1&cdeferred=1&sortby=id&sorto=asc&format=html#results So it was working. :) >> In particular, this bug is correctly marked as a Jessie blocker due to >> the current bug title, which suggests that nfs-common has a circular >> dependency causing NFS to break under systemd. However, reading the bug >> I am understanding that this loop is now assumed to be fixed? > > That's my "bug A" and yes I suspect it's been fixed by better > sysvinit compatibility in systemd... but I could be wrong, and I > don't know specifically what the fix was. Let's use #622394 for this. > > I haven't closed it immediately, but I've tagged it unreproducible. > I certainly didn't see it myself. > > [...] >> On the topic of "_netdev": Did you conclude that systemd correctly >> auto-discovered NFS as a _netdev *without* explicitly stating it in >> /etc/fstab? > > I believe so. systemd does have code to do this, and Ben's logic > concluding that the test results indicate it is working > correctly does seem valid. > > S > Excellent, thanks. I will revisit the "unreproducible" or/and "moreinfo" bugs in a week; if there has been no follow up on the bugs with more information I will deal with them (close or downgrade, whichever seems more applicable). Thanks, ~Niels -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756253: Upgrade from 2.02~beta2-10 to 2.02~beta2-11 left grub unbootable
On Fri, Jan 16, 2015 at 10:28:51PM +, Steve McIntyre wrote: > Hi Mike, > > Have you seen this again recently? Is it still happening for you? As a matter of fact, it hasn't happened recently. That being said, I'm not upgrading grub that often, but I happen to have upgraded it today, and a reboot worked. It's too late now to know what the efi boot table looked like before, but during the package install, efibootmgr complained like this: Installing for x86_64-efi platform. efibootmgr: Could not set variable Boot0001: No such file or directory efibootmgr: Could not prepare boot variable: No such file or directory And its current output is: BootCurrent: Timeout: 0 seconds BootOrder: ,0002 Boot* grub Boot0002* Windows Boot Manager Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: severity of 774917 is minor
Processing commands for cont...@bugs.debian.org: > severity 774917 minor Bug #774917 [icinga-idoutils] icinga-idoutils: fails to upgrade squeeze -> wheezy -> jessie: ERROR: syntax error at or near "EXISTS" LINE 1: ALTER TABLE icinga_comments DROP CONSTRAINT IF EXISTS uq_com... ^ Severity set to 'minor' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 774917: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774917 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#774917: severity of 774917 is minor
severity 774917 minor thanks Hi, as already stated in the bug we are not able to support every database version that ever was in stable. Therefore I will downgrade this bug to minor. If you are doing upgrade tests from squeeze to jessie, you should also upgrade the database. Alex -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#771871: netscript: fails to install due to insserv rejecting the script header: There is a loop between service networking and netscript if started
Followup-For: Bug #771871 This bug now also shows up on wheezy. Andreas netscript-2.4_5.2.12.log.gz Description: application/gzip
Bug#775471: xserver-xorg-video-geode-dbg: copyright file missing after upgrade (policy 12.5)
On 2015-01-16 14:15, Martin-Éric Racine wrote:
> ---
> xserver-xorg-video-geode-2.11.16/debian/xserver-xorg-video-geode-dbg.maintscript
> 1970-01-01 02:00:00.0 +0200
> +++
> xserver-xorg-video-geode-2.11.16/debian/xserver-xorg-video-geode-dbg.maintscript
> 2015-01-16 15:02:13.0 +0200
> @@ -0,0 +1 @@
> +dir_to_symlink /usr/share/doc/xserver-xorg-video-geode-dbg
> /usr/share/doc/xserver-xorg-video-geode 2.11.13-5
I think you should use the relative target as it is in the current package:
lrwxrwxrwx 1 root root 24 Nov 10 23:22
/usr/share/doc/xserver-xorg-video-geode-dbg -> xserver-xorg-video-geode
Also the prior-version was wrong, so the .maintscript file should look like
dir_to_symlink /usr/share/doc/xserver-xorg-video-geode-dbg
xserver-xorg-video-geode 2.11.13-6~
For debian/control I'd recommend to use ${misc:Pre-Depends) instead of
hardcoding it manually.
Andreas
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#770194: [DRE-maint] Bug#770194: please confirm the version of ruby-i18n
Hi, At Thu, 4 Dec 2014 10:43:20 -0200, Antonio Terceiro wrote: - snip - > > please don't, the right fix for this is to make stringex compatible > with the new i18n. << dependencies will always come back to bite you > in the future. I think so. I'll take care of this bug after jessie release. Best wishes, Youhei --- Youhei SASAKI GPG fingerprint: 4096/RSA: 66A4 EA70 4FE2 4055 8D6A C2E6 9394 F354 891D 7E07 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed (with 3 errors): Re: Bug#622394: systemd: nfs-common and rpcbind unit files to fix systemd NFS issues properly
Processing control commands: > clone 622394 -2 -3 Bug #622394 [nfs-common] nfs-common: breaks systemd - dependency cycle in require-start leads to removal of critical jobs Bug 622394 cloned as bugs 775541-775542 > retitle -2 NFS mounts from /etc/fstab do not work Bug #775541 [nfs-common] nfs-common: breaks systemd - dependency cycle in require-start leads to removal of critical jobs Changed Bug title to 'NFS mounts from /etc/fstab do not work' from 'nfs-common: breaks systemd - dependency cycle in require-start leads to removal of critical jobs' > submitter -2 m...@mattgrant.net.nz Bug #775541 [nfs-common] NFS mounts from /etc/fstab do not work Changed Bug submitter to 'm...@mattgrant.net.nz' from 'Alban Browaeys ' > retitle -3 NFS exports fail due to rpcbind not starting before nfs-common and > nfs-kernel-server Bug #775542 [nfs-common] nfs-common: breaks systemd - dependency cycle in require-start leads to removal of critical jobs Changed Bug title to 'NFS exports fail due to rpcbind not starting before nfs-common and nfs-kernel-server' from 'nfs-common: breaks systemd - dependency cycle in require-start leads to removal of critical jobs' > submitter -3 m...@mattgrant.net.nz Bug #775542 [nfs-common] NFS exports fail due to rpcbind not starting before nfs-common and nfs-kernel-server Changed Bug submitter to 'm...@mattgrant.net.nz' from 'Alban Browaeys ' > tags -3 moreinfo unreproducible Bug #775542 [nfs-common] NFS exports fail due to rpcbind not starting before nfs-common and nfs-kernel-server Added tag(s) unreproducible and moreinfo. > user release.debian@packages.debian.org Unknown command or malformed arguments to command. > usertag -2 - jessie-is-blocker Unknown command or malformed arguments to command. > usertag -3 - jessie-is-blocker Unknown command or malformed arguments to command. > tags 622394 unreproducible Bug #622394 [nfs-common] nfs-common: breaks systemd - dependency cycle in require-start leads to removal of critical jobs Added tag(s) unreproducible. -- 622394: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622394 775541: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775541 775542: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775542 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#622394: systemd: nfs-common and rpcbind unit files to fix systemd NFS issues properly
Control: clone 622394 -2 -3 Control: retitle -2 NFS mounts from /etc/fstab do not work Control: submitter -2 m...@mattgrant.net.nz Control: retitle -3 NFS exports fail due to rpcbind not starting before nfs-common and nfs-kernel-server Control: submitter -3 m...@mattgrant.net.nz Control: tags -3 moreinfo unreproducible Control: user release.debian@packages.debian.org Control: usertag -2 - jessie-is-blocker Control: usertag -3 - jessie-is-blocker Control: tags 622394 unreproducible On 16/01/15 21:27, Niels Thykier wrote: > Can anyone provide me with an up to date status on this bug? It seems > to be a mismatch of no less than 3 different bugs if I understand > Simon's comment in message #41 correctly (see [1] for the full text). That is my understanding, but I am not an expert on this package (I don't use NFS myself). I was hoping for a response from a maintainer and/or bug reporters, but apparently I'm not going to get one, so... cloning it is. I hope I got the usertags and stuff right - please check. > In particular, this bug is correctly marked as a Jessie blocker due to > the current bug title, which suggests that nfs-common has a circular > dependency causing NFS to break under systemd. However, reading the bug > I am understanding that this loop is now assumed to be fixed? That's my "bug A" and yes I suspect it's been fixed by better sysvinit compatibility in systemd... but I could be wrong, and I don't know specifically what the fix was. Let's use #622394 for this. I haven't closed it immediately, but I've tagged it unreproducible. I certainly didn't see it myself. > If the other bugs (see below) are still present, let us clone this > bug/file separate bugs for those! I believe M1 and M2 may be separate bugs, and C1 might be the same thing as M1 or a fourth bug (it's unclear). The clone "NFS mounts from /etc/fstab do not work" is M1 and probably also C1; I'm leaving them entangled for now. Matthew, Chris, if you have any additional info / newer test results / etc. on this specific issue, please send it to that clone (check https://bugs.debian.org/nfs-common for its bug number). The clone "NFS exports fail due to rpcbind not starting before nfs-common and nfs-kernel-server" is M2. Matthew, if you have additional info on that, please send it there (again, check https://bugs.debian.org/nfs-common for its bug number). > On the topic of "_netdev": Did you conclude that systemd correctly > auto-discovered NFS as a _netdev *without* explicitly stating it in > /etc/fstab? I believe so. systemd does have code to do this, and Ben's logic concluding that the test results indicate it is working correctly does seem valid. S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765540: missing symbol
Control: severity -1 normal Control: retitle -1 Problems with grub upgrades getting out of step on a RAID configuration On Mon, Oct 20, 2014 at 09:16:03AM +0200, Enrico Zini wrote: >On Thu, Oct 16, 2014 at 11:40:23AM +0100, Colin Watson wrote: > >> Right, you have two disks on this system and you're only installing GRUB >> to the second one. There's probably a vestige of GRUB on the other disk >> which happened to be compatible with the modules from 2.00-22 but not >> the modules from the new version. I recommend running: >> >> sudo dpkg-reconfigure grub-pc >> >> Step through without changing anything until you get to the "GRUB >> install devices:" question, and then select the master boot records of >> both your hard disks, rather than just one of them. That should fix it. > >I've recently been bitten by this: after I installed a new SSH in my >laptop, grub stopped upgrading itself correctly. It's fixed now, >finally, thanks to your message here. > >The take away message for me is that if I change or add a hard disk to >my system, I need to remember to run "dpkg-reconfigure grub-pc". From my >point of view, the most obvious way I had to learn about this was to >wait until my system became unbootable, rescue it, then find your >message when looking for what happened. > >Could grub's machinery could store somewhere the output of something >like this: > > ls /dev/disk/by-id/ | grep ^ata | grep -v -- -part > >and print at least a big warning during upgrades if it sees that it has >changed? Hi Enrico, That looks like a generally useful thing to have, yes, but I don't think it's RC to *not* have it. Downgrading and retitling appropriately. I'll see what I can do to add support for something like that soon. In a related(ish) sense, we could do with some similar extra work to make EFI systems and RAID play nicely too... :-/ -- Steve McIntyre, Cambridge, UK.st...@einval.com Getting a SCSI chain working is perfectly simple if you remember that there must be exactly three terminations: one on one end of the cable, one on the far end, and the goat, terminated over the SCSI chain with a silver-handled knife whilst burning *black* candles. --- Anthony DeBoer -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#765540: missing symbol
Processing control commands: > severity -1 normal Bug #765540 [grub-pc] missing symbol Severity set to 'normal' from 'grave' > retitle -1 Problems with grub upgrades getting out of step on a RAID > configuration Bug #765540 [grub-pc] missing symbol Changed Bug title to 'Problems with grub upgrades getting out of step on a RAID configuration' from 'missing symbol' -- 765540: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765540 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#775005: marked as done ([macchanger] MAC randomization doesn't generate a random MAC)
Your message dated Fri, 16 Jan 2015 23:48:20 +
with message-id
and subject line Bug#775005: fixed in macchanger 1.7.0-5.1
has caused the Debian Bug report #775005,
regarding [macchanger] MAC randomization doesn't generate a random MAC
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
775005: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775005
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: macchanger
Version: 1.7.0-3.2
Severity: grave
Trying to randomize the MAC address of an interface toggles between two MAC
addresses instead of setting a random MAC address. See the following example:
$ macchanger -A wlan8
Current MAC: 00:05:01:98:56:c3 (CISCO SYSTEMS, INC.)
Permanent MAC: 24:fd:52:XX:XX:XX (Liteon Technology Corporation)
New MAC: 00:05:01:98:26:05 (CISCO SYSTEMS, INC.)
$ macchanger -A wlan8
Current MAC: 00:05:01:98:26:05 (CISCO SYSTEMS, INC.)
Permanent MAC: 24:fd:52:XX:XX:XX (Liteon Technology Corporation)
New MAC: 00:05:01:98:56:c3 (CISCO SYSTEMS, INC.)
$ macchanger -A wlan8
Current MAC: 00:05:01:98:56:c3 (CISCO SYSTEMS, INC.)
Permanent MAC: 24:fd:52:XX:XX:XX (Liteon Technology Corporation)
New MAC: 00:05:01:98:26:05 (CISCO SYSTEMS, INC.)
$ macchanger -A wlan8
Current MAC: 00:05:01:98:26:05 (CISCO SYSTEMS, INC.)
Permanent MAC: 24:fd:52:XX:XX:XX (Liteon Technology Corporation)
New MAC: 00:05:01:98:56:c3 (CISCO SYSTEMS, INC.)
The problem here seems to be in the random_seed function where macchanger
tries to open different devices for random numbers and takes the first one
where open() is successful but never checks if the following read() is
successful.
http://sources.debian.net/src/macchanger/1.7.0-5/src/main.c/#L92
also see this strace snippet:
open("/dev/hwrng", O_RDONLY)= 3
read(3, 0x7fffe23909ec, 4) = -1 ENODEV (No such device)
close(3)= 0
I don't know why I do have this non-working /dev/hwrng device. It gets somehow
automatically created by loading the b43 kernel module.
Macchanger should check if the read() was successful and if not try the next
entropy device or at least abort with an error instead pretending to set a
random MAC address which clearly is not random.
Another problem I spotted is that if reading from an entropy device does work
only sizeof(unsigned int) entropy is read, which is only guaranteed to be 2
octets. However from these are then up to 6 octets of "random" data generated
(in case of a fully random MAC) which clearly does not work as expected.
--- System information. ---
Architecture: amd64
Kernel: Linux 3.18.0-trunk-amd64
Debian Release: 8.0
500 testing security.debian.org
500 testing mirror.stusta.mhn.de
500 testing http.debian.net
--- Package information. ---
Depends (Version) | Installed
=-+-=
libc6(>= 2.4) |
dpkg (>= 1.15.4) |
OR install-info |
Package's Recommends field is empty.
Package's Suggests field is empty.
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Source: macchanger
Source-Version: 1.7.0-5.1
We believe that the bug you reported is fixed in the latest version of
macchanger, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 775...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ben Hutchings (supplier of updated macchanger package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 16 Jan 2015 23:22:13 +
Source: macchanger
Binary: macchanger
Architecture: i386 source
Version: 1.7.0-5.1
Distribution: unstable
Urgency: medium
Maintainer: David Paleino
Changed-By: Ben Hutchings
Closes: 775005
Description:
macchanger - utility for manipulating the MAC address of network interfaces
Changes:
macchanger (1.7.0-5.1) unstable; urgency=medium
.
* Non-maintainer upload
* Check for random device read errors (Closes: #775005)
Checksums-Sha1:
9e7d686a8439381fc867972db492aae5ef05aac7 1921 macchanger_1.7.0-5.1.dsc
ae6b54e
Bug#775375: python-django: diff for NMU version 1.7.1-1.1
Control: tags 775375 + patch Control: tags 775375 + pending Dear maintainer, I've prepared an NMU for python-django (versioned as 1.7.1-1.1) and I'll do some more testing of it before uploading it, likely to Delayed-2 or possibly 4. Regards. diff -Nru python-django-1.7.1/debian/changelog python-django-1.7.1/debian/changelog --- python-django-1.7.1/debian/changelog 2014-10-27 15:57:12.0 + +++ python-django-1.7.1/debian/changelog 2015-01-16 23:22:26.0 + @@ -1,3 +1,18 @@ +python-django (1.7.1-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix CVE-2015-0219 - WSGI header spoofing via underscore/dash +conflation + * Fix CVE-2015-0220 - Mitigated possible XSS attack via +user-supplied redirect URLs. + * Fix CVE-2015-0221 - Denial-of-service attack against +django.views.static.serve + * Fix CVE-2015-0222 - Database denial-of-service with +ModelMultipleChoiceField +(Closes: #775375) + + -- Neil Williams Fri, 16 Jan 2015 23:05:55 + + python-django (1.7.1-1) unstable; urgency=medium [ Raphaël Hertzog ] diff -Nru python-django-1.7.1/debian/patches/header-underscore.diff python-django-1.7.1/debian/patches/header-underscore.diff --- python-django-1.7.1/debian/patches/header-underscore.diff 1970-01-01 01:00:00.0 +0100 +++ python-django-1.7.1/debian/patches/header-underscore.diff 2015-01-16 23:10:56.0 + @@ -0,0 +1,128 @@ +Description: WSGI header spoofing via underscore/dash conflation + This issue has been assigned the CVE identifier CVE-2015-0219. + [PATCH] [1.7.x] Stripped headers containing underscores to prevent + spoofing in WSGI environ. + . + Thanks to Jedediah Smith for the report. + . +--- + +Author: Neil Williams +Bug-Debian: https://bugs.debian.org/775375 +Origin: upstream, https://github.com/django/django/commit/41b4bc73ee0da7b2e09f4af47fc1fd21144c710f.patch + +--- python-django-1.7.1.orig/django/core/servers/basehttp.py python-django-1.7.1/django/core/servers/basehttp.py +@@ -155,6 +155,17 @@ class WSGIRequestHandler(simple_server.W + + sys.stderr.write(msg) + ++def get_environ(self): ++# Strip all headers with underscores in the name before constructing ++# the WSGI environ. This prevents header-spoofing based on ambiguity ++# between underscores and dashes both normalized to underscores in WSGI ++# env vars. Nginx and Apache 2.4+ both do this as well. ++for k, v in self.headers.items(): ++if '_' in k: ++del self.headers[k] ++ ++return super(WSGIRequestHandler, self).get_environ() ++ + + def run(addr, port, wsgi_handler, ipv6=False, threading=False): + server_address = (addr, port) +--- python-django-1.7.1.orig/docs/howto/auth-remote-user.txt python-django-1.7.1/docs/howto/auth-remote-user.txt +@@ -64,6 +64,22 @@ If your authentication mechanism uses a + class CustomHeaderMiddleware(RemoteUserMiddleware): + header = 'HTTP_AUTHUSER' + ++.. warning:: ++ ++Be very careful if using a ``RemoteUserMiddleware`` subclass with a custom ++HTTP header. You must be sure that your front-end web server always sets or ++strips that header based on the appropriate authentication checks, never ++permitting an end-user to submit a fake (or "spoofed") header value. Since ++the HTTP headers ``X-Auth-User`` and ``X-Auth_User`` (for example) both ++normalize to the ``HTTP_X_AUTH_USER`` key in ``request.META``, you must ++also check that your web server doesn't allow a spoofed header using ++underscores in place of dashes. ++ ++This warning doesn't apply to ``RemoteUserMiddleware`` in its default ++configuration with ``header = 'REMOTE_USER'``, since a key that doesn't ++start with ``HTTP_`` in ``request.META`` can only be set by your WSGI ++server, not directly from an HTTP request header. ++ + If you need more control, you can create your own authentication backend + that inherits from :class:`~django.contrib.auth.backends.RemoteUserBackend` and + override one or more of its attributes and methods. +--- /dev/null python-django-1.7.1/tests/servers/test_basehttp.py +@@ -0,0 +1,67 @@ ++import sys ++ ++from django.core.servers.basehttp import WSGIRequestHandler ++from django.test import TestCase ++from django.utils.six import BytesIO, StringIO ++ ++ ++class Stub(object): ++def __init__(self, **kwargs): ++self.__dict__.update(kwargs) ++ ++ ++class WSGIRequestHandlerTestCase(TestCase): ++ ++def test_strips_underscore_headers(self): ++"""WSGIRequestHandler ignores headers containing underscores. ++ ++This follows the lead of nginx and Apache 2.4, and is to avoid ++ambiguity between dashes and underscores in mapping to WSGI environ, ++which can have security implications. ++""" ++def test_app(environ, start_response): ++"""A WSGI app that just reflects its HTTP environ.""" ++start
Processed: python-django: diff for NMU version 1.7.1-1.1
Processing control commands: > tags 775375 + patch Bug #775375 [src:python-django] python-django: CVE-2015-0219 CVE-2015-0220 CVE-2015-0221 CVE-2015-0222 Added tag(s) patch. > tags 775375 + pending Bug #775375 [src:python-django] python-django: CVE-2015-0219 CVE-2015-0220 CVE-2015-0221 CVE-2015-0222 Added tag(s) pending. -- 775375: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775375 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#775471: xserver-xorg-video-geode-dbg: copyright file missing after upgrade (policy 12.5)
On Fri, Jan 16, 2015 at 03:15:29PM +0200, Martin-Éric Racine wrote: > Wait. Got it: DPKG won't squash a previous directory. > > Fixed in maintainer script. Patch attached. > > Release Team: > > Is this something worth getting a freeze exception for? If yes, should > it be introduced via unstable, jessies-update, or something else? Yes please, via unstable. -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 signature.asc Description: Digital signature
Bug#775005: [macchanger] MAC randomization doesn't generate a random MAC
I don't know how it is possible for /dev/hwrng to be present but
unreadable. Loading rng-core on a system without a hardware random
driver doesn't do it. However, it is possible to reproduce this poor
randomisation after running 'ln -s null /dev/hwrng'.
I've uploaded a fix for this and am attaching the NMU diff.
Ben.
--
Ben Hutchings
Lowery's Law:
If it jams, force it. If it breaks, it needed replacing anyway.
diff -Nru macchanger-1.7.0/debian/changelog macchanger-1.7.0/debian/changelog
--- macchanger-1.7.0/debian/changelog 2014-12-18 11:51:19.0 +
+++ macchanger-1.7.0/debian/changelog 2015-01-16 23:22:14.0 +
@@ -1,3 +1,10 @@
+macchanger (1.7.0-5.1) unstable; urgency=medium
+
+ * Non-maintainer upload
+ * Check for random device read errors (Closes: #775005)
+
+ -- Ben Hutchings Fri, 16 Jan 2015 23:22:13 +
+
macchanger (1.7.0-5) unstable; urgency=low
* fix maintainer-script-without-set-e config
diff -Nru macchanger-1.7.0/debian/patches/check-random-device-read-errors.patch macchanger-1.7.0/debian/patches/check-random-device-read-errors.patch
--- macchanger-1.7.0/debian/patches/check-random-device-read-errors.patch 1970-01-01 01:00:00.0 +0100
+++ macchanger-1.7.0/debian/patches/check-random-device-read-errors.patch 2015-01-16 23:03:34.0 +
@@ -0,0 +1,47 @@
+Description: Check for random device read errors
+ In some cases it is possible to open /dev/hwrng but not to read from it.
+ We need to check for errors and move on to the next possible random device
+ in this case.
+Author: Ben Hutchings
+Bug-Debian: https://bugs.debian.org/775005
+
+---
+--- a/src/main.c
b/src/main.c
+@@ -91,17 +91,29 @@ print_mac (const char *s, const mac_t *m
+ static void
+ random_seed (void)
+ {
++ static const char *const dev_names[] = {
++ "/dev/hwrng",
++ "/dev/random",
++ "/dev/urandom",
++ NULL,
++ };
+ intfd;
+ struct timeval tv;
+ unsigned int seed;
++ const char *const *name;
++ ssize_tread_len = 0;
+
+- if ((fd = open("/dev/hwrng", O_RDONLY)) >= 0 ||
+- (fd = open("/dev/random", O_RDONLY)) >= 0 ||
+- (fd = open("/dev/urandom", O_RDONLY)) >= 0)
+- {
+- read (fd, &seed, sizeof(seed));
+- close (fd);
+- } else {
++ for (name = dev_names; *name; name++) {
++ fd = open(*name, O_RDONLY);
++ if (fd >= 0) {
++ read_len = read (fd, &seed, sizeof(seed));
++ close (fd);
++ if (read_len == sizeof(seed))
++break;
++ }
++ }
++
++ if (read_len != sizeof(seed)) {
+ gettimeofday (&tv, NULL);
+ seed = (getpid() << 16) ^ tv.tv_sec ^ tv.tv_usec;
+ }
diff -Nru macchanger-1.7.0/debian/patches/series macchanger-1.7.0/debian/patches/series
--- macchanger-1.7.0/debian/patches/series 2014-03-18 14:59:20.0 +
+++ macchanger-1.7.0/debian/patches/series 2015-01-16 22:51:05.0 +
@@ -1,3 +1,4 @@
02-fix_usage_message.patch
06-update_OUI_list.patch
08-fix_random_MAC_choice.patch
+check-random-device-read-errors.patch
signature.asc
Description: This is a digitally signed message part
Bug#756253: Upgrade from 2.02~beta2-10 to 2.02~beta2-11 left grub unbootable
[ Hoping to help investigate this... ] On Fri, Oct 24, 2014 at 07:30:26PM +0900, Mike Hommey wrote: >On Mon, Oct 13, 2014 at 03:45:31PM +0100, Colin Watson wrote: >> On Mon, Jul 28, 2014 at 09:26:22AM +0900, Mike Hommey wrote: >> > After the upgrade from 2.02~beta2-10 to 2.02~beta2-11, a reboot just got >> > me under Windows. The EFI boot menu had two entries for Windows (I don't >> > think it had two in the past, but maybe it did, and that's not related), >> > and one for "UEFI OS" which was set as the default. Choosing that one >> > manually in the boot menu still brought Windows up. >> > >> > After booting with a USB stick in rescue mode, deleting the duplicate >> > Windows entry and the UEFI OS entry, and re-running grub-install, grub >> > showed up at reboot. After grub-install, the EFI entry is now named >> > "debian". >> > >> > Note I haven't run grub-install in a while, so I'm not sure what version >> > of grub had done a grub-install last. >> >> Sorry for the delayed response. I think this is unlikely to have been a >> problem introduced by the new version of GRUB as such (unless switching >> to GCC 4.9 did this, but that seems a pretty tenuous theory), and >> grub-install is run automatically provided that /boot/efi/EFI/debian/ >> exists. Could you please post the output of: >> >> dpkg -l efibootmgr >> sudo efibootmgr >> find /boot/efi -ls > >It happened again today. Grub was not updated, but the kernel was. > ># dpkg -l efibootmgr >Desired=Unknown/Install/Remove/Purge/Hold >| >Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend >|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) >||/ NameVersionArchitecture >Description >+++-===-==-==- >ii efibootmgr 0.9.0-2amd64 >Interact with the EFI Boot Manager > ># efibootmgr >BootCurrent: 0002 >Timeout: 0 seconds >BootOrder: 0002,0001, >Boot* Windows Boot Manager >Boot0001* Windows Boot Manager >Boot0002* grub > ># # NOTE: the "grub" entry is one I added from the BIOS in order to boot ># # at all. It was *not* there. Both Windows entries were. after re-running ># # grub-install, I get: > >BootCurrent: 0002 >Timeout: 0 seconds >BootOrder: 0003,0002,0001, >Boot* Windows Boot Manager >Boot0001* Windows Boot Manager >Boot0002* grub >Boot0003* debian ... > > 4534 drwxr-xr-x 2 root root 4096 1月 8 2014 > /boot/efi/EFI/Boot > 455 1580 -rwxr-xr-x 1 root root 1617240 4月 27 2014 > /boot/efi/EFI/Boot/bootx64.efi > 4564 drwxr-xr-x 2 root root 4096 1月 22 2014 > /boot/efi/EFI/debian > 458 120 -rwxr-xr-x 1 root root 119808 10月 18 10:59 > /boot/efi/EFI/debian/grubx64.efi Hi Mike, Have you seen this again recently? Is it still happening for you? -- Steve McIntyre, Cambridge, UK.st...@einval.com Can't keep my eyes from the circling sky, Tongue-tied & twisted, Just an earth-bound misfit, I... -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#713311: marked as done (harden-doc: FTBFS: debiandoc2latexps: ERROR: securing-debian-howto.de.dvi could not be generated properly)
Your message dated Fri, 16 Jan 2015 22:18:33 + with message-id and subject line Bug#713311: fixed in harden-doc 3.16 has caused the Debian Bug report #713311, regarding harden-doc: FTBFS: debiandoc2latexps: ERROR: securing-debian-howto.de.dvi could not be generated properly to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 713311: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713311 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: harden-doc Version: 3.15.1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130620 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[2]: Entering directory `/«PKGBUILDDIR»/howto-source' > sed -e "s/@@LANGS@@/en/g" \ > -e "s/@@DIRS@@/en/g" \ > -e "s/@@NAME@@/securing-debian-howto/g" \ > securing-debian-howto.sgml > securing-debian-howto.en.sgml > sed -e "s/@@LANGS@@/de/g" \ > -e "s/@@DIRS@@/de/g" \ > -e "s/@@NAME@@/securing-debian-howto/g" \ > securing-debian-howto.sgml > securing-debian-howto.de.sgml > echo "" > > securing-debian-howto.en.ent > echo "" >> > securing-debian-howto.en.ent > echo "" >> > securing-debian-howto.en.ent > echo "" >> > securing-debian-howto.en.ent > po4a po4a/po4a.cfg > (2507 entries) > debiandoc2html -len -C securing-debian-howto.en.sgml > touch securing-debian-howto.en.html.stamp > echo "" > > securing-debian-howto.de.ent > echo "" >> > securing-debian-howto.de.ent > echo "" >> > securing-debian-howto.de.ent > echo "" >> > securing-debian-howto.de.ent > debiandoc2html -lde -C securing-debian-howto.de.sgml > touch securing-debian-howto.de.html.stamp > echo "" > > securing-debian-howto.fr.ent > echo "" >> > securing-debian-howto.fr.ent > echo "" >> > securing-debian-howto.fr.ent > echo "" >> > securing-debian-howto.fr.ent > debiandoc2html -lfr.UTF-8 -C securing-debian-howto.fr.sgml > touch securing-debian-howto.fr.html.stamp > debiandoc2text -len securing-debian-howto.en.sgml > debiandoc2text -lde securing-debian-howto.de.sgml > debiandoc2text -lfr.UTF-8 securing-debian-howto.fr.sgml > debiandoc2latexps -len securing-debian-howto.en.sgml > debiandoc2latexps -lde securing-debian-howto.de.sgml > debiandoc2latexps: ERROR: securing-debian-howto.de.dvi could not be generated > properly > debiandoc2latexps: rerun with the -v option to find out why > debiandoc2latexps: or check the log file securing-debian-howto.de.log > make[2]: *** [securing-debian-howto.de.ps] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/06/20/harden-doc_3.15.1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: harden-doc Source-Version: 3.16 We believe that the bug you reported is fixed in the latest version of harden-doc, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 713...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thijs Kinkhorst (supplier of updated harden-doc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 30 Dec 2014 12:31:43 + Source: harden-doc Binary: harden-doc Architecture: source all Version: 3.16 Distribution: unstable Urgency: low Maintainer: Javier Fernandez-Sanguino Pen~a Changed-By: Thijs Kinkhorst Description: harden-doc - useful documentation to secure a Debian system Closes: 415529 420380 442893 694822 713311 750554 755003 773904 Changes: harden-doc (3.16) unstable; urgency=low . [ Javier Fernández-Sanguino Peña ] * Update to latest version in SVN:
Bug#774437: ovirt-guest-agent: fails in preinst due to hardcoded uid and gid values
On Fri, 9 Jan 2015 12:47:28 -0800 Cameron Norman wrote: > On Fri, Jan 9, 2015 at 12:03 PM, László Böszörményi (GCS) > wrote: > > On Fri, Jan 2, 2015 at 8:33 PM, Cameron Norman wrote: > >> It hardcodes them as 175. The uid was not taken, but the gid was so the > >> package installation failed. Funnily enough, I was trying to fix #767028 at > >> the time. > > Can you confirm that #767028 happens due to udevadm failure because > > /proc is not mounted? > > What has gid 175 on your system? > > Not at my comp (will get back to you when I am), but I am pretty sure > it was "radicale". > > I actually did not experience #767028 on a system that does have /proc > mounted, so it is likely. Again, I will double check later today. I said I would check but I never followed up on that :). I already deleted the group so I could not see who it was. I could not umount /proc in a container, and I ended up getting too lazy to set up a chroot (yes I know it is pretty easy, I am just kind of busy and tired). That said your hypothesis that it is a udevadm failure seems extremely likely. Best regards, -- Cameron Norman
Bug#775062: grok: diff for NMU version 1.20110708.1-4.1
Control: tags 775062 + patch Control: tags 775062 + pending Dear maintainer, I've prepared an NMU for grok (versioned as 1.20110708.1-4.1) and I plan to upload it to unstable whilst at the Debian-UK BSP: https://wiki.debian.org/BSP/2015/01/gb/Alcester#Bugs Regards. diff -Nru grok-1.20110708.1/debian/changelog grok-1.20110708.1/debian/changelog --- grok-1.20110708.1/debian/changelog 2012-10-14 10:08:33.0 +0100 +++ grok-1.20110708.1/debian/changelog 2015-01-16 22:03:19.0 + @@ -1,3 +1,11 @@ +grok (1.20110708.1-4.1) unstable; urgency=medium + + * Non-maintainer upload. + * Apply fix from upstream to working with PCRE >= 8.34 +(Closes: #775062) + + -- Neil Williams Fri, 16 Jan 2015 22:03:17 + + grok (1.20110708.1-4) unstable; urgency=low * Add GNU/Hurd patch which disappeared from -3 (Closes: #675104) diff -Nru grok-1.20110708.1/debian/patches/pcre-group-name.patch grok-1.20110708.1/debian/patches/pcre-group-name.patch --- grok-1.20110708.1/debian/patches/pcre-group-name.patch 1970-01-01 01:00:00.0 +0100 +++ grok-1.20110708.1/debian/patches/pcre-group-name.patch 2015-01-16 22:07:11.0 + @@ -0,0 +1,33 @@ +Description: [fix] grok is not working anymore with PCRE >= 8.34 + From 44ce9372a29319c01d4ac7f24287fb36315e0e34 Mon Sep 17 00:00:00 2001 + From: Guillaume Bour + Subject: [PATCH] [fix] grok is not working anymore with PCRE >= 8.34 because + the latter does not allow anymore a group name to start with digits (PCRE + Changelog version 8.34, point 36) + . + this commit fix the issue by prepending a '_' at the start of group + name. + . + grok (1.20110708.1-4.1) unstable; urgency=medium + . + * Non-maintainer upload. + * Apply fix from upstream to working with PCRE >= 8.34 + (Closes: #775062) +Author: Neil Williams +Bug-Debian: https://bugs.debian.org/775062 +Origin: upstream, https://github.com/jordansissel/grok/commit/44ce9372a29319c01d4ac7f24287fb36315e0e34.patch +--- + +--- grok-1.20110708.1.orig/grokre.c grok-1.20110708.1/grokre.c +@@ -12,8 +12,8 @@ + + /* global, static variables */ + +-#define CAPTURE_ID_LEN 4 +-#define CAPTURE_FORMAT "%04x" ++#define CAPTURE_ID_LEN 5 ++#define CAPTURE_FORMAT "_%04x" + + /* internal functions */ + static char *grok_pattern_expand(grok_t *grok); //, int offset, int length); diff -Nru grok-1.20110708.1/debian/patches/series grok-1.20110708.1/debian/patches/series --- grok-1.20110708.1/debian/patches/series 2012-10-14 10:08:43.0 +0100 +++ grok-1.20110708.1/debian/patches/series 2015-01-16 22:04:43.0 + @@ -1,3 +1,4 @@ # debian/source/git-patches exported from git by quilt-patches-deb-export-hook 0001-Support-GNU-kFreeBSD-add-necessary-linker-flag.patch 0002-Support-GNU-Hurd-add-necessary-linker-flag.patch +pcre-group-name.patch
Processed: grok: diff for NMU version 1.20110708.1-4.1
Processing control commands:
> tags 775062 + patch
Bug #775062 [grok] grok doesn't grok group name ('group name must start with a
non-digit')
Added tag(s) patch.
> tags 775062 + pending
Bug #775062 [grok] grok doesn't grok group name ('group name must start with a
non-digit')
Added tag(s) pending.
--
775062: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775062
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#769388: 'PermitRootLogin without-password' in new installations breaks some use cases
On Thu, 13 Nov 2014 11:08:45 + Simon McVittie wrote: > [...] > Hi, Thanks for the summary. CC'ing debian-boot as I suspect the "easiest" solution will involve documentation this in the installation-guide. > [...] > > * However, new installations of Debian 8 do not ask which configuration > to use; they use the new one (PermitRootLogin without-password) > unconditionally. > > Concrete effects reported in this bug: > > [...] > > I understand the request to have debian-installer ask which configuration > to use, and I have some sympathy for that; I've been doing a bit of > installer testing in disposable VMs recently, and it's annoying to have to > log in once at the (emulated) console to switch to "PermitRootLogin yes". > However, I do think maintainers are right to err on the side of asking the > minimum feasible number of questions in the installer. > > Another possibility would be to use a low-priority question that is > only shown in the "expert" installer, but can be pre-seeded. > Please also keep in mind that such questions need to be translated. I am not certain on the policy for d-i for having pre-seedable configuration without an "expert" question. If this is not an issue for d-i, I suppose it could be added solely in the openssh-server-udeb package. > It is already possible to put something like this on the kernel command line > when booting the installer, which might be useful: > > preseed/late_command="in-target sed -i 's/PermitRootLogin > without-password/PermitRootLogin yes/' /etc/ssh/sshd_config" > > If you are producing VM images that are designed to be cloned repeatedly, > to make those VM images secure and correct, you already need a > post-processing step to do things like deleting the ssh host key, > setting a new unique systemd/D-Bus machine ID and so on; it seems If we are going down this route, then let us have it documented in the installation-guide. If needed be, we can add a reference from the release notes to the relevant part of the installation guide (or maybe just a remark about it). Though note that the release-notes only handles upgrades between the (soon-to-be) previous and the (soon-to-be) current release, so I firmly believe it should be documented in the installation-guide to ensure it is a stand-alone document. Assuming no objections to this, let us have this reassigned to the installation-guide package. Simon McVittie also wrote: > * Upgrading openssh-server from Debian 7's version to Debian 8's version > uses debconf to ask whether to update the configuration, as far as > I can see. > For reference, it is also documented in the release-notes (including how to preseed the question). ~Niels -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756253: Upgrade from 2.02~beta2-10 to 2.02~beta2-11 left grub unbootable
On Wed, Oct 29, 2014 at 09:19:26PM -0300, Ibirisol wrote:
>Hi there,
>
>I have the same problem here. I'm using rEFInd to boot.
Sorry, but I think you're seeing a slightly different bug here.
># efibootmgr -c -l "\\EFI\\debian\\grubx64.efi" -L "Debian" -v
>Alternate GPT is invalid, using primary GPT.
>Alternate GPT is invalid, using primary GPT.
>
>Could not prepare boot variable: No such file or directory
>---
>
>In attachment follow the strace output for the above command.
Going right to the end of the log you've posted:
...
>access("/sys/firmware/efi/vars/Boot0001-8be4df61-93ca-11d2-aa0d-00e098032b8c/data",
> F_OK) = -1 ENOENT (No such file or directory)
>open("/sys/firmware/efi/vars/new_var", O_WRONLY) = 3
>write(3,
>"B\0o\0o\0t\\\\0001\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 2084) =
>-1 ENOSPC (No space left on device)
>umask(0)= 022
...
That ENOSPC error is the cause of your problem - your firmware has
filled up the EFI variable space, so the system cannot add new EFI
variables. I suggest you look for documentation on ow to fix that -
it'll depend on the type of computer you have.
--
Steve McIntyre, Cambridge, UK.st...@einval.com
< liw> everything I know about UK hotels I learned from "Fawlty Towers"
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: forcibly merging 766711 766795
Processing commands for cont...@bugs.debian.org: > forcemerge 766711 766795 Bug #766711 [debhelper] support --link-doc arch:all <=> arch:any Bug #766711 [debhelper] support --link-doc arch:all <=> arch:any Added tag(s) wheezy-ignore. Bug #766795 [debhelper] afterstep not binnmu safe Severity set to 'wishlist' from 'serious' 766795 was not blocked by any bugs. 766795 was not blocking any bugs. Added blocking bug(s) of 766795: 767839 Marked as found in versions debhelper/9.20141003, debhelper/9.20141222, debhelper/9.20140228, and debhelper/9.20141022. Added tag(s) jessie-ignore, patch, and wontfix. Merged 766711 766795 > thanks Stopping processing here. Please contact me if you need assistance. -- 766711: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766711 766795: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766795 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#622394: systemd: nfs-common and rpcbind unit files to fix systemd NFS issues properly
Hi, Can anyone provide me with an up to date status on this bug? It seems to be a mismatch of no less than 3 different bugs if I understand Simon's comment in message #41 correctly (see [1] for the full text). In particular, this bug is correctly marked as a Jessie blocker due to the current bug title, which suggests that nfs-common has a circular dependency causing NFS to break under systemd. However, reading the bug I am understanding that this loop is now assumed to be fixed? Simon McVittie wrote (cite [1]): > Bug A, reported by Alban Browaeys, present in 1:1.2.3-2: "systemd[1]: > Found ordering cycle on basic.target/start" and an unbootable system. I > believe newer systemd and/or nfs-common have probably fixed this, so > #622394 should probably have been closed, and the other symptoms should > probably have had distinct bug numbers. > If this is indeed closed, I would very much like this bug to be closed. If the other bugs (see below) are still present, let us clone this bug/file separate bugs for those! NB: If you clone this bug, please remember to remove the "jessie-is-blocker" tag. If these bugs below lack information or/and are unreproducible, please also tag them as such. > Bug M1, reported by Matthew Grant, present in 1:1.2.8-6: "NFS mounts > from /etc/fstab do not work". (What symptoms? What error messages?) This > one might be related to NFS entries in /etc/fstab that don't have _netdev. > > Bug M2, reported by Matthew Grant, present in 1:1.2.8-6: "NFS exports > also fail due to rpcbind not starting before nfs-common and nfs- > kernel-server". > > Bug C1, sort-of-reported by Chris Butler, present in 1:1.2.8-9: "the > boot order problem on NFS clients that mount remote filesystems on > boot". This might be the same thing as M1. (Do you have _netdev in the > options of the relevant mounts?) > > Bug C2, reported by Chris Butler, present in 1:1.2.8-9 with Matthew's > systemd units added: 'tries to start "statd" before "rpcbind"'. I > believe this is an omission in one of Matthew's systemd units, and I am > about to test a version of nfs-common that should fix that bit. On the topic of "_netdev": Did you conclude that systemd correctly auto-discovered NFS as a _netdev *without* explicitly stating it in /etc/fstab? There is a mail between Simon and Ben that suggests this to be the case. If *not* the case, we /can/ add a warning in the release notes problems for that. We already have a clause for updating fstab with nodefault and nofail on disks are not critical. Having a paragraph for adding _netdev is not going to be a huge problem at this point. :) Thanks, ~Niels [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622394#41 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#774868: marked as done (php-pager: unhandled symlink to directory conversion: /usr/share/php/tests/Pager/tests)
Your message dated Fri, 16 Jan 2015 21:19:39 +
with message-id
and subject line Bug#774868: fixed in php-pager 2.4.8-3
has caused the Debian Bug report #774868,
regarding php-pager: unhandled symlink to directory conversion:
/usr/share/php/tests/Pager/tests
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
774868: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774868
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-pager
Version: 2.4.8-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.
This was observed on the following upgrade paths:
squeeze -> wheezy -> jessie
For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile
For other overwritten locations anything interesting may happen.
Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase
It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.mainstscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.
>From the attached log (usually somewhere in the middle...):
3m38.1s INFO: dirname part contains a symlink:
/usr/share/php/tests/Pager/tests/README (php-pager) !=
/usr/share/doc/php-pager/tests/README (?)
/usr/share/php/tests/Pager/tests -> ../../../doc/php-pager/tests
/usr/share/php/tests/Pager/tests/all_tests.php (php-pager) !=
/usr/share/doc/php-pager/tests/all_tests.php (?)
/usr/share/php/tests/Pager/tests -> ../../../doc/php-pager/tests
/usr/share/php/tests/Pager/tests/multibyte_post.php (php-pager) !=
/usr/share/doc/php-pager/tests/multibyte_post.php (?)
/usr/share/php/tests/Pager/tests -> ../../../doc/php-pager/tests
/usr/share/php/tests/Pager/tests/pager_include.php (php-pager) !=
/usr/share/doc/php-pager/tests/pager_include.php (?)
/usr/share/php/tests/Pager/tests -> ../../../doc/php-pager/tests
/usr/share/php/tests/Pager/tests/pager_jumping_noData_test.php (php-pager) !=
/usr/share/doc/php-pager/tests/pager_jumping_noData_test.php (?)
/usr/share/php/tests/Pager/tests -> ../../../doc/php-pager/tests
/usr/share/php/tests/Pager/tests/pager_jumping_test.php (php-pager) !=
/usr/share/doc/php-pager/tests/pager_jumping_test.php (?)
/usr/share/php/tests/Pager/tests -> ../../../doc/php-pager/tests
/usr/share/php/tests/Pager/tests/pager_jumping_tests.php (php-pager) !=
/usr/share/doc/php-pager/tests/pager_jumping_tests.php (?)
/usr/share/php/tests/Pager/tests -> ../../../doc/php-pager/tests
/usr/share/php/tests/Pager/tests/pager_noData_test.php (php-pager) !=
/usr/share/doc/php-pager/tests/pager_noData_test.php (?)
/usr/share/php/tests/Pager/tests -> ../../../doc/php-pager/tests
/usr/share/php/tests/Pager/tests/pager_post_test.php (php-pager) !=
/usr/share/doc/php-pager/tests/pager_post_test.php (?)
/usr/share/php/tests/Pager/tests -> ../../../doc/php-pager/tests
/usr/share/php/tests/Pager/tests/pager_post_test_simple.php (php-pager) !=
/usr/share/doc/php-pager/tests/pager_post_test_simple.php (?)
/usr/share/php/tests/Pager/tests -> ../../../doc/php-pager/tests
/usr/share/php/tests/Pager/tests/pager_post_tests.php (php-pager) !=
/usr/share/doc/php-pager/tests/pager_post_tests.php (?)
/usr/share/php/tests/Pager/tests -> ../../../doc/php-pager/tests
/usr/share/php/tests/Pager/tests/pager_sliding_noData_test.php (php-pager) !=
/usr/share/doc/php-pager/tests/pager_sliding_noData_test.php (?)
/usr/share/php/tests/Pager/tests -> ../../../doc/php-pager/tests
/usr/share/php/tests/Pager/tests/pager_sliding_notExp
Bug#774890: Is this bug really RC?
On 2015-01-16 12:03, Axel Beckert wrote: > Hi together, > > Andreas Tille wrote: >> [...] >> I'm seriously wondering whether this issue is RC critical for Jessie >> release > > To be honest: I think this is generally an RC-level issue and should > be fixed. > > [...] TL;DR - it seems like this bug is faster to fix (based on the subject of #774890) than it is to argue over whether it needs to be fixed? If it is truly just a regular dir -> symlink transition, please just implement it (using dpkg-maintscript-helper) and request an unblock for it. It would apparently also do some of our long term users a favour. :) If there is some reason why it is more difficult to solve, please - by all means highlight and I will revisit the situation. Thanks, ~Niels -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#775044: openjdk-7: FTBFS: java.lang.RuntimeException: time is more than 10 years from present: 1104530400000
Daniel Schepler wrote:
Version: 7u71-2.5.3-2
This isn't limited to the testing/unstable version of openjdk-7. I just
encountered it with while merging the raspbian changes into wheezy's
openjdk-6 and I strongly suspect it affects all versions of openjdk-6
and openjdk-7 in all releases of Debian.
Moritz Mühlenhoff write:
Patch attached, this fixes the build for me.
What concerns me is that while this fixes this particular case it
doesn't fix the root cause. Basically it appears that any currency which
has a transition rule also has a timebomb 10 years after the transition
date and it appears there are at least a couple more timebombs set to go
off in the not too distant future.
Personally I would rather see the timebomb code removed/disabled. I do
not belive Debian should knowingly be shipping timebombed code.
I have just prepared a patch against wheezy's openjdk-6 to disable the
timebomb code. I have attatched this patch which I am currently in the
process of testing.
Theres also the issue that new transitions don't seem to have been
getting added to the file. I'm not sure how critical this is because I
don't know how much software uses the data in question.
--- openjdk-ecj/jdk/make/tools/src/build/tools/generatecurrencydata/GenerateCurrencyData.java 2014-10-08 15:35:08.0 +
+++ openjdk/jdk/make/tools/src/build/tools/generatecurrencydata/GenerateCurrencyData.java 2015-01-16 20:04:19.0 +
@@ -281,9 +281,9 @@
checkCurrencyCode(newCurrency);
String timeString = currencyInfo.substring(4, length - 4);
long time = format.parse(timeString).getTime();
-if (Math.abs(time - System.currentTimeMillis()) > ((long) 10) * 365 * 24 * 60 * 60 * 1000) {
-throw new RuntimeException("time is more than 10 years from present: " + time);
-}
+//if (Math.abs(time - System.currentTimeMillis()) > ((long) 10) * 365 * 24 * 60 * 60 * 1000) {
+//throw new RuntimeException("time is more than 10 years from present: " + time);
+//}
specialCaseCutOverTimes[specialCaseCount] = time;
specialCaseOldCurrencies[specialCaseCount] = oldCurrency;
specialCaseOldCurrenciesDefaultFractionDigits[specialCaseCount] = getDefaultFractionDigits(oldCurrency);
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 775255 upstream fixed-upstream Bug #775255 [fetchmail] fetchmail: Fails to start when libssl has SSLv3 disabled Added tag(s) upstream and fixed-upstream. > severity 775255 normal Bug #775255 [fetchmail] fetchmail: Fails to start when libssl has SSLv3 disabled Severity set to 'normal' from 'grave' > End of message, stopping processing here. Please contact me if you need assistance. -- 775255: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775255 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#775255: fetchmail: Fails to start when libssl has SSLv3 disabled
Am 16.01.2015 um 01:24 schrieb Debian Bug Tracking System: > Processing control commands: > >> tags -1 + experimental > Bug #775255 [fetchmail] fetchmail: Fails to start when libssl has SSLv3 > disabled > Added tag(s) experimental. > IMO this is an error from the shell and the dynamic run-time linker, not a fetchmail issue, and Sebastian is right, symbol removal REQUIRES bumping the .so version appropriately. It needs to be OpenSSL 2.0 then (at least libssl) in my understanding. I wonder how people get the package build though, if the symbol is dropped from the lib it most certainly should also be dropped from the header, and that would already jam the build. (OK chances are that the library package is younger than the fetchmail package, please check that. You should NOT be able to build fetchmail on a libssl that has SSLv3 disable, else please file a bug against the libssl*-dev package.) Now, if OpenSSL chooses to disable options in an incompatible way, by causing compile or run-time link trouble by removing symbols, so be it, the proposed fix however is wrong and rejected. For 6.3 the proper fix will be to amend to configure and conditionally disable SSLv3, but it will need to tell the user what the matter is, so just silently removing a line without adjusting parsers and thereabout is an offense. For 7.x I may consider killing SSLv3 support altogether, it's no longer default in the Git version since 2014-10-15 anyhow. I would need to add a deprecation warning in a 6.x release though, and distributors may also need to do that. Having said all that, grab a2ae6f8d15d7caf815d7bdd13df833fd1b2af5cc from one of the three upstream Git mirrors and extract the relevant parts. If you break it, you get to keep the pieces, though... My take is that this bug should be demoted to wishlist and also bestowed with "upstream, fixed-upstream, patch" tags. HTH -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#773749: Resolvconf vs wicd
On 14 January 2015 at 16:18, Axel Beckert wrote: >> It's up to the admin to change things in /etc/. Programs that play >> around with things in /etc/ at runtime are not well behaved by Debian >> standards. > > Depends. I agree for anything in the maintainer scripts, but I > disagree for anything which can be seen as (configuration) editor. Configuration is what the administrator does before starting a service, not what a program does to maintain state at runtime. As the FHS puts it: «The /etc hierarchy contains configuration files. A "configuration file" is a local file used to control the operation of a program; it must be static [...].» Configuration is thus by definition not dynamic. The list of nameserver addresses obtained via the most recent DHCP negotiation *is* dynamic. Admittedly it is difficult to draw a completely sharp distinction between configuration and state. But the idea behind it, which is clear enough, is that it should be possible to run a Debian machine with the root filesystem (including /etc) mounted read-only. These issues were discussed at some length in 2003, e.g., in the following thread. https://lists.debian.org/debian-devel/2003/03/msg00493.html So as dictated by the FHS, well-behaved programs do not change files in /etc at run time. Resolvconf was introduced in order to deal with the exceptional case of the file /etc/resolv.conf which is under /etc but has to be updated dynamically. In the resolvconf scheme, the dynamic file is on another filesystem and /etc/resolv.conf itself is a static but configurable symbolic link. -- Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#774868: [pkg-php-pear] php-pager is marked for autoremoval from testing
2015-01-16 9:08 GMT+01:00 Mathieu Parent : > Hello, > >> It is affected by these RC bugs: >> 774868: php-pager: unhandled symlink to directory conversion: >> /usr/share/php/tests/Pager/tests > > I don't use php-pager myself, here is a quick tip: > > To fix this RC, build again the package with current pkg-php-tools (in > testing=sid). I will do it myself. (sorry for the noise) -- Mathieu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#775063: marked as done (greylistd: fails to install, remove, distupgrade, and install again)
Your message dated Fri, 16 Jan 2015 18:48:23 + with message-id and subject line Bug#775063: fixed in greylistd 0.8.8.4 has caused the Debian Bug report #775063, regarding greylistd: fails to install, remove, distupgrade, and install again to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 775063: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775063 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: greylistd Version: 0.8.8.3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install (in 'wheezy'), remove (but not purge), distupgrade to 'jessie', and install again. Before the second installation the package is in config-files-remaining state. The configuration is remaining from the last version that was successfully configured - which is from the previous release. Like a plain failure on initial install this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Selecting previously unselected package greylistd. Unpacking greylistd (from .../greylistd_0.8.8_all.deb) ... Setting up greylistd (0.8.8) ... Adding system user `greylist' (UID 100) ... Adding new group `greylist' (GID 150) ... Adding new user `greylist' (UID 100) with group `greylist' ... Not creating home directory `/var/lib/greylistd'. Creating directory /var/run/greylistd: Done. Copying /usr/share/doc/greylistd/examples/whitelist-hosts to /etc/greylistd: Done. invoke-rc.d: policy-rc.d denied execution of start. Removing greylistd ... invoke-rc.d: policy-rc.d denied execution of stop. Selecting previously unselected package greylistd. (Reading database ... 8369 files and directories currently installed.) Preparing to unpack .../greylistd_0.8.8.3_all.deb ... Unpacking greylistd (0.8.8.3) ... Setting up greylistd (0.8.8.3) ... insserv: script greylistd: service greylist already provided! insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing package greylistd (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: greylistd The fix should be rather simple: the preinst script actions but be performed on both "install" and "upgrade" (install will get a second argument if the conffiles from an old version were remaining): [...] case "$1" in install|upgrade) [...] cheers, Andreas greylistd_0.8.8.3.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: greylistd Source-Version: 0.8.8.4 We believe that the bug you reported is fixed in the latest version of greylistd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 775...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Alteholz (supplier of updated greylistd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 16 Jan 2015 18:10:00 +0100 Source: greylistd Binary: greylistd Architecture: source all Version: 0.8.8.4 Distribution: unstable Urgency: medium Maintainer: Thorsten Alteholz Changed-By: Thorsten Alteholz Description: greylistd - Greylisting daemon for use with Exim 4 Closes: 775063 Changes: greylistd (0.8.8.4) unstable; urgency=medium . * debian/preinst: take care of old /etc/init.d/greylist while doing install -> remove -> distupgrade -> install (Closes: #775063) Checksums-Sha1: 194123a3c3b8b136deaeaaebb0ed43d364472c54 1580 greylistd_0.8.8.4.dsc d094463beff9a16bf7325827ae1bd679ed2ae78a 50392 greylistd_0.8.8.4.tar.xz eb41678dfab4bb2b9562e7e369e67ba33ed3c990 57460 greylistd_0.8.8.4_all.deb Checksums-Sha256: 92f5a26286fb37ea819e2a30c04a361a548d7bba7eb0b499c348ac678981a444 1580 greylistd_0.8.8.4.dsc f21f93ef5d04231afdbe27dda2ad371124dceca05b3224bc805ff53088a5e9c0 50392 greylistd_0.8.8.4.tar.xz 00fb41dd294f0b06cc5311bc27f9fed5cd7cf91d14ad2a7760d4013b39824f88 57460 greylistd_0.8.8.4_all.deb Files: 2bd78430f7bbe1e0268e9f6618c9ad97 1580 mail optional g
Bug#775389: marked as done (lua-mode: fails to upgrade lenny -> squeeze -> wheezy -> jessie)
Your message dated Fri, 16 Jan 2015 17:18:21 + with message-id and subject line Bug#775389: fixed in lua-mode 20140514-2 has caused the Debian Bug report #775389, regarding lua-mode: fails to upgrade lenny -> squeeze -> wheezy -> jessie to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 775389: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775389 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lua-mode Version: 20140514-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'lenny' to 'squeeze' to 'wheezy' to 'jessie'. It installed fine in 'lenny', and upgraded to 'squeeze' and 'wheezy' successfully, but then the upgrade to 'jessie' failed. >From the attached log (scroll to the bottom...): Setting up emacsen-common (2.0.8) ... Install emacsen-common for emacs22 emacsen-common: Handling install of emacsen flavor emacs22 Wrote /etc/emacs22/site-start.d/00debian-vars.elc Wrote /usr/share/emacs22/site-lisp/debian-startup.elc Setting up lua-mode (20140514-1) ... Installing new version of config file /etc/emacs/site-start.d/50lua-mode.el ... ERROR: lua-mode is broken - called emacs-package-install as a new-style add-on, but has no compat file. Install lua-mode for emacs Install lua-mode for emacs22 install/lua-mode: Handling install for emacsen flavor emacs22 In toplevel form: lua-mode.el:115:1:Error: Symbol's function definition is void: rx-form ERROR: install script from lua-mode package failed dpkg: error processing package lua-mode (--configure): subprocess installed post-installation script returned error exit status 1 Setting up makedev (2.3.1-93) ... Processing triggers for libc-bin (2.19-13) ... Errors were encountered while processing: lua-mode cheers, Andreas lua-mode_20140514-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: lua-mode Source-Version: 20140514-2 We believe that the bug you reported is fixed in the latest version of lua-mode, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 775...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilko Bengen (supplier of updated lua-mode package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 16 Jan 2015 10:41:29 +0100 Source: lua-mode Binary: lua-mode Architecture: source all Version: 20140514-2 Distribution: unstable Urgency: medium Maintainer: Hilko Bengen Changed-By: Hilko Bengen Description: lua-mode - Emacs mode for editing Lua programs Closes: 775389 Changes: lua-mode (20140514-2) unstable; urgency=medium . * Dropped emacs22 support (Closes: #775389) Checksums-Sha1: efc8e9540d3f9a8cc92a7f59f02b094a866ffdcd 1713 lua-mode_20140514-2.dsc 10efebe6015237d0512b4cdbb25d9ac75e3edfcd 4528 lua-mode_20140514-2.debian.tar.xz 088d3221f4338f8a6f8d210353997c89ef06cc35 24250 lua-mode_20140514-2_all.deb Checksums-Sha256: 9e652eca6eb9933b634dfe6ef30210ae5d2cea9463c84dd3b1f7111d1407cfe6 1713 lua-mode_20140514-2.dsc ab166c879173aa6f1abccf28e078bc141a0564c32249ccc76b263cfe616bda99 4528 lua-mode_20140514-2.debian.tar.xz 52d5060a87129486a92e0a8384e332e2cc596ea292b32a99fe9a08a2b3f66924 24250 lua-mode_20140514-2_all.deb Files: 00436ff91b8d1a10b7eba06b39596916 1713 editors optional lua-mode_20140514-2.dsc aba262c3987c135ed8bbb290706e35c3 4528 editors optional lua-mode_20140514-2.debian.tar.xz 2502cc10de64bd5aa2e0db0f26d2f12a 24250 editors optional lua-mode_20140514-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUuUQiAAoJEHW3EGNcITp+ayAQAJHNVwXUZFr81Gtuyt8hIPeI FwqBDjqg3ONS02dBD96eiECgb0NniepJrvYXmoVIcv8ghDcsAxeizyrTvakvH0wE ETvDXLpQS8JsyAFjaYvgkKdo5PLRIC98TBYmok86dGPhKwVtzx6O1/GEw9ZlGGwn 6U+H8H+qvaXoclQAoDTbpuexoV7a1SYaVhSU5r+FnCF6C83AAMsoaa3wFOLHQBN5 1zuYzB8dcFxtoFbQ1PkZKN2HaCLH8CRXnLawBxbxLeIjlWfoY7uVo9W/t/41ubUB 2VJmnLJbnn8HVZSI3JwV/GVyp2UD8dDwMBoXEGtgf6M/JD1E8ZeGbcoGYuFiTyY4 jD08YWYSZF8Vk3/7x6FBeMeBxS1cZHf7H1DGgVoGKK5MQv5qz/uBEwCtRgBOoDGu fOVtP0bncPlt6JkCfZe9bKgHoYoylWLQFvP4nSK/GGuJRJ+CvPA/oLb9Wp+H/gkf ywgcp
Bug#774866: libqglviewer: diff for NMU version 2.5.3+dfsg-2.1
Hi Anton, On 2015-01-16 06:35:08, Anton Gladky wrote: > thanks a lot for the patch and NMU! Feel free to bypass 2-days delay > and reschedule it to DAYS/0. you're welcome. I've rescheduled it earlier today. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#753760: marked as done (Non free logo)
Your message dated Fri, 16 Jan 2015 16:18:38 + with message-id and subject line Bug#753760: fixed in uncrustify 0.59+dfsg1-1.1 has caused the Debian Bug report #753760, regarding Non free logo to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 753760: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753760 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: uncrustify version: 0.59-2 severity: serious user: lintian.debian.org usertag: license-problem-md5sum-non-free-file Hi, Uncrustify include the non free logo: documentation/htdocs/project-support.jpg Please remove this file from your package. Bastien --- End Message --- --- Begin Message --- Source: uncrustify Source-Version: 0.59+dfsg1-1.1 We believe that the bug you reported is fixed in the latest version of uncrustify, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 753...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathieu Malaterre (supplier of updated uncrustify package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 16 Jan 2015 16:52:15 +0100 Source: uncrustify Binary: uncrustify Architecture: source amd64 Version: 0.59+dfsg1-1.1 Distribution: unstable Urgency: medium Maintainer: Johann Rudloff Changed-By: Mathieu Malaterre Description: uncrustify - C, C++, C#, D, Java and Pawn source code beautifier Closes: 753760 Changes: uncrustify (0.59+dfsg1-1.1) unstable; urgency=medium . * Non-maintainer upload. * Remove non-free file (project-support.jpg). Closes: #753760 Checksums-Sha1: 713884dbb350bfe8e38a1f0c002ceb382c882769 1810 uncrustify_0.59+dfsg1-1.1.dsc 7aeee2f8e55f65eaabd4ca377e9ccee17de74d19 979466 uncrustify_0.59+dfsg1.orig.tar.gz c1674df163b6aa2c8fa01dd0510dfd8c1c362023 3816 uncrustify_0.59+dfsg1-1.1.debian.tar.xz 4ea9e9694b97bad571e82ddb8bab19005ff460f1 208616 uncrustify_0.59+dfsg1-1.1_amd64.deb Checksums-Sha256: ebd50c84da4ba605a9e2b941fa454c19272165779f4885e088588a7ca7a42cac 1810 uncrustify_0.59+dfsg1-1.1.dsc 9b95d3c02f005b43dea9b2b4f750dcc29a8072d4d4a354c755d77d7611ea39e5 979466 uncrustify_0.59+dfsg1.orig.tar.gz bb87d2dd53de455dd2a507861a00d7b7f2689d69ba889341eb78d6de394ce2c8 3816 uncrustify_0.59+dfsg1-1.1.debian.tar.xz 8bee1462762484e1e8e2dbb7979aca32217cafa88e667f35eb973cf1b48268b1 208616 uncrustify_0.59+dfsg1-1.1_amd64.deb Files: d75a6fe2694eefdfee88b5dc57e3a95f 1810 devel optional uncrustify_0.59+dfsg1-1.1.dsc b19b6f5b0a9c5c9dce7aec8e6f8dfa34 979466 devel optional uncrustify_0.59+dfsg1.orig.tar.gz 2c63665bb38d663e6db727d1455c6464 3816 devel optional uncrustify_0.59+dfsg1-1.1.debian.tar.xz a4e8e0f93d5f2e170a4bbb3a8835676a 208616 devel optional uncrustify_0.59+dfsg1-1.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJUuTQDAAoJEAFx4YKK4JNFIGwP/3+Lu6jfPd/OxPhQF67UXD0l +ZMuThQtQnaMCY3zDG0Uc6Y9rE1lbRtI44s7aXtEDE4ShLGK5Zkq/WiYH+UqHnV/ TlmSTdhmaC+QOW6KyXGNEXcsc82MRe0mK1XBMfsqQM4Ee3XfWiWIyk4/IGXJa0rs YHcoZkrDrzT1lxFhirhuCYl1dkLbsI3Cn2bJKDzhPVKMeovqZ0cAvLjaRWDRGbRI IiTBb4HFsiiQgdvP/78TVlyVriMxINv3a5uYLr2VH5IcGjZPiQRSI8HqUIHGjmUX w8xM6hIxgV/HGfLzETHZzK1sFomSH4JLmkBj9Wu9iRYvI4OOuF8YFYbDCRETMnSx ycvwOjDiTjdP65kHVq+3Hl3HeUyfp7lZ6UoKwBPNdXMJEwQe72kWdH62CsBGrQgF 0DTVqkPepY75t2DN4hCD2bAsIJs1jH+TzUt91WlAKcD7nNdTyDvz8mS557TIQfxo ZeEm0p7yFj1npoySg9lPzGavLNuYEVOmSaQZNqtuGpS9V1XuHYJu6qD4IPOaF7Oa Xvr5VFpsxAAf4RitteDJkUBmkWyIUNdJRb7zR6I8ePfFJUzOF5jmhhXGOBxWK2RQ 5TjdIhO9qnprdyONc2nWTS+d6J1A4JdymMZ4bzciiJTWF7O33SSs6aFBIIyzUk8D GZWh9erHSy5iZU6zoihj =aqPJ -END PGP SIGNATURE End Message ---
Bug#753760: NMU
Steps: dget -u http://ftp.de.debian.org/debian/pool/main/u/uncrustify/uncrustify_0.59-2.dsc gunzip uncrustify_0.59.orig.tar.gz tar --delete -f uncrustify_0.59.orig.tar uncrustify-0.59/documentation/htdocs/project-support.jpg gzip --best uncrustify_0.59.orig.tar mv uncrustify_0.59.orig.tar.gz uncrustify_0.59+dfsg1.orig.tar.gz Will upload in a few minutes. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#772195: marked as done (389-ds-base: bashism in /bin/sh script)
Your message dated Fri, 16 Jan 2015 15:18:56 + with message-id and subject line Bug#772195: fixed in 389-ds-base 1.3.3.5-3 has caused the Debian Bug report #772195, regarding 389-ds-base: bashism in /bin/sh script to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 772195: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772195 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: 389-ds-base Severity: serious Version: 1.3.3.5-2 User: debian-rele...@lists.debian.org Usertags: goal-dash Hi, I've ran checkbashisms (from the 'devscripts' package) over the whole archive and I found that your package has a /bin/sh script that uses a "bashism". checkbashisms' output: > possible bashism in ./usr/sbin/saveconfig line 34 (should be 'b = a'): > if [ $? == 1 ] > possible bashism in ./usr/sbin/dn2rdn line 42 (should be 'b = a'): > if [ $? == 1 ] > possible bashism in ./usr/sbin/dbverify line 48 (should be 'b = a'): > if [ $? == 1 ] > possible bashism in ./usr/sbin/dbverify line 59 (should be 'b = a'): > if [ $display_version == "yes" ]; then > possible bashism in ./usr/sbin/restoreconfig line 34 (should be 'b = a'): > if [ $? == 1 ] > possible bashism in ./usr/sbin/suffix2instance line 35 (should be 'b = a'): > if [ "$args" == "" ] > possible bashism in ./usr/sbin/suffix2instance line 42 (should be 'b = a'): > if [ $? == 1 ] > possible bashism in ./usr/sbin/vlvindex line 48 (should be 'b = a'): > if [ $? == 1 ] > possible bashism in ./usr/sbin/bak2db line 61 (should be 'b = a'): > if [ $? == 1 ] > possible bashism in ./usr/sbin/stop-dirsrv line 42 (should be 'b = a'): > if [ -d "/lib/systemd/system" ] && [ "$(id -u)" == "0" ];then > possible bashism in ./usr/sbin/ldif2ldap line 43 (should be 'b = a'): > if [ "$input_file" == "" ] > possible bashism in ./usr/sbin/ldif2ldap line 50 (should be 'b = a'): > if [ $? == 1 ] > possible bashism in ./usr/sbin/ldif2ldap line 70 (should be 'b = a'): > if [ "$rootdn" == "" ]; then > possible bashism in ./usr/sbin/ldif2ldap line 102 (should be 'b = a'): > if [ "$security" == "on" ]; then > possible bashism in ./usr/sbin/ldif2ldap line 103 (should be 'b = a'): > if [ "$protocol" == "STARTTLS" ] || [ "$protocol" == "" ]; then > possible bashism in ./usr/sbin/ldif2ldap line 104 (should be 'b = a'): > if [ "$error" == "yes" ]; then > possible bashism in ./usr/sbin/ldif2ldap line 107 (should be 'b = a'): > if [ "$openldap" == "yes" ]; then > possible bashism in ./usr/sbin/ldif2ldap line 119 (should be 'b = a'): > if [ "$security" == "on" ]; then > possible bashism in ./usr/sbin/ldif2ldap line 120 (should be 'b = a'): > if [ "$protocol" == "LDAPS" ] || [ "$protocol" == "" ]; then > possible bashism in ./usr/sbin/ldif2ldap line 121 (should be 'b = a'): > if [ "$error" == "yes" ]; then > possible bashism in ./usr/sbin/ldif2ldap line 124 (should be 'b = a'): > if [ "$openldap" == "yes" ]; then > possible bashism in ./usr/sbin/ldif2ldap line 136 (should be 'b = a'): > if [ "$ldapi" == "on" ] && [ "$openldap" == "yes" ]; then > possible bashism in ./usr/sbin/ldif2ldap line 137 (should be 'b = a'): > if [ "$protocol" == "LDAPI" ] || [ "$protocol" == "" ]; then > possible bashism in ./usr/sbin/ldif2ldap line 138 (should be 'b = a'): > if [ "$(id -u)" == "0" ] && [ "$autobind" == "on" ]; then > possible bashism in ./usr/sbin/ldif2ldap line 139 (should be 'b = a'): > if [ "$error" == "yes" ]; then > possible bashism in ./usr/sbin/ldif2ldap line 144 (should be 'b = a'): > if [ "$error" == "yes" ]; then > possible bashism in ./usr/sbin/ldif2ldap line 161 (should be 'b = a'): > if [ "$protocol" == "LDAP" ] || [ "$protocol" == "" ]; then > possible bashism in ./usr/sbin/ldif2ldap line 162 (should be 'b = a'): > if [ "$error" == "yes" ]; then > possible bashism in ./usr/sbin/ldif2ldap line 165 (should be 'b = a'): > if [ "$openldap" == "yes" ]; then > possible bashism in ./usr/sbin/ldif2db line 85 (should be 'b = a'): > if [ $? == 1 ] > possible bashism in ./usr/sbin/db2index line 62 (should be 'b = a'): > if [ $? == 1 ] > possible bashism in ./usr/sbin/db2bak line 60 (should be 'b = a'): > if [ $? == 1 ] > possible bashism in ./usr/sbin/upgradednformat line 58 (should be 'b = a'): > if [ $? == 1 ] > possible bashism in ./usr/sbin/upgradedb line 42 (should be 'b = a'): > if [ $? == 1 ] > possible bashism in ./usr/sbin/db2ldif line 140 (should be 'b = a'): > if [ $? == 1 ] > possible bashism in ./usr/sbin/monitor line 44 (should be 'b = a'): > if [ $? == 1 ] > possible bashism in ./
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> severity 756233 grave
Bug #756233 {Done: Steve Capper } [libtbb2] libtbb2
for i386 is miscompiled, it contains the cmov instruction
Severity set to 'grave' from 'normal'
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
756233: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756233
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#775471: xserver-xorg-video-geode-dbg: copyright file missing after upgrade (policy 12.5)
Wait. Got it: DPKG won't squash a previous directory.
Fixed in maintainer script. Patch attached.
Release Team:
Is this something worth getting a freeze exception for? If yes, should
it be introduced via unstable, jessies-update, or something else?
Cheers!
Martin-Éric
2015-01-16 14:48 GMT+02:00 Martin-Éric Racine :
> Hey Andreas,
>
> debian/rules uses this:
>
> override_dh_installdocs:
> dh_installdocs --link-doc=xserver-xorg-video-geode NEWS README TODO
>
> Surely that would link the -dbg package's /usr/share/doc/foo-dbg to
> .../foo, wouldn't it?
>
> Martin-Éric
>
>
> 2015-01-16 5:21 GMT+02:00 Andreas Beckmann :
>> Package: xserver-xorg-video-geode-dbg
>> Version: 2.11.16-5
>> Severity: serious
>> User: debian...@lists.debian.org
>> Usertags: piuparts
>>
>> Hi,
>>
>> a test with piuparts revealed that your package misses the copyright
>> file after an upgrade, which is a violation of Policy 12.5:
>> https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile
>>
>> After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory.
>>
>> This was observed on the following upgrade paths:
>>
>> wheezy -> jessie
>>
>> >From the attached log (scroll to the bottom...):
>>
>> 3m56.0s ERROR: WARN: Inadequate results from running adequate!
>> xserver-xorg-video-geode-dbg: missing-copyright-file
>> /usr/share/doc/xserver-xorg-video-geode-dbg/copyright
>>
>> 3m59.5s DUMP:
>> MISSING COPYRIGHT FILE:
>> /usr/share/doc/xserver-xorg-video-geode-dbg/copyright
>> # ls -lad /usr/share/doc/xserver-xorg-video-geode-dbg
>> drwxr-xr-x 2 root root 40 Jan 15 11:43
>> /usr/share/doc/xserver-xorg-video-geode-dbg
>> # ls -la /usr/share/doc/xserver-xorg-video-geode-dbg/
>> total 0
>> drwxr-xr-x 2 root root 40 Jan 15 11:43 .
>> drwxr-xr-x 185 root root 3840 Jan 15 11:43 ..
>>
>>
>> Additional info may be available here:
>> https://wiki.debian.org/MissingCopyrightFile
>>
>> Note that dpkg intentionally does not replace directories with symlinks
>> and vice versa, you need the maintainer scripts to do this.
>> See in particular the end of point 4 in
>> https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase
>>
>> It is recommended to use the dpkg-maintscript-helper commands
>> 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
>> to perform the conversion, ideally using d/$PACKAGE.mainstscript.
>> Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
>> See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.
>>
>>
>> cheers,
>>
>> Andreas
diff -Nru xserver-xorg-video-geode-2.11.16/debian/changelog
xserver-xorg-video-geode-2.11.16/debian/changelog
--- xserver-xorg-video-geode-2.11.16/debian/changelog 2014-11-11
01:12:48.0 +0200
+++ xserver-xorg-video-geode-2.11.16/debian/changelog 2015-01-16
15:11:33.0 +0200
@@ -1,3 +1,12 @@
+xserver-xorg-video-geode (2.11.16-6) unstable; urgency=medium
+
+ * debian/xserver-xorg-video-geode-dbg.maintscript:
++ New file. Handles dir_to_symlink for 2.11.13-5 (Closes: # 775471).
+ * debian/control:
++ xserver-xorg-video-geode-dbg: Pre-Depends: dpkg (>= 1.17.14)
+
+ -- Martin-Éric Racine Fri, 16 Jan 2015 15:10:36
+0200
+
xserver-xorg-video-geode (2.11.16-5) unstable; urgency=medium
* debian/control:
diff -Nru xserver-xorg-video-geode-2.11.16/debian/control
xserver-xorg-video-geode-2.11.16/debian/control
--- xserver-xorg-video-geode-2.11.16/debian/control 2014-11-11
00:33:21.0 +0200
+++ xserver-xorg-video-geode-2.11.16/debian/control 2015-01-16
15:10:27.0 +0200
@@ -40,6 +40,7 @@
Architecture: any-i386
Section: debug
Priority: extra
+Pre-Depends: dpkg (>= 1.17.14)
Depends: xserver-xorg-core-dbg,
xserver-xorg-video-geode (= ${binary:Version}),
${misc:Depends},
diff -Nru
xserver-xorg-video-geode-2.11.16/debian/xserver-xorg-video-geode-dbg.maintscript
xserver-xorg-video-geode-2.11.16/debian/xserver-xorg-video-geode-dbg.maintscript
---
xserver-xorg-video-geode-2.11.16/debian/xserver-xorg-video-geode-dbg.maintscript
1970-01-01 02:00:00.0 +0200
+++
xserver-xorg-video-geode-2.11.16/debian/xserver-xorg-video-geode-dbg.maintscript
2015-01-16 15:02:13.0 +0200
@@ -0,0 +1 @@
+dir_to_symlink /usr/share/doc/xserver-xorg-video-geode-dbg
/usr/share/doc/xserver-xorg-video-geode 2.11.13-5
Bug#774890: Is this bug really RC?
Hi Axel, On Fri, Jan 16, 2015 at 12:03:41PM +0100, Axel Beckert wrote: > Well, you (Andreas T) did not cite a possible relevant part here: > > | This was observed on the following upgrade paths: > | > | lenny -> squeeze -> wheezy -> jessie Yes, I was a bit short. > > I'm seriously wondering whether this issue is RC critical for Jessie > > release > > To be honest: I think this is generally an RC-level issue and should > be fixed. I think any bug should be fixed (if possible) not only RC bugs. :-) > But I also think, it's a candidate for a jessie-ignore tag as the bug > has been in there for quite a while (obviously) and -- from a first > glance at the log which Andreas B. attached -- has no operational > impact, just legal impact (wrong copyright file, etc.). +1 > One more thing I'm still curious about: How the fuck do you stumble > upon such a bug? :-) I don't expect that Andreas runs piuparts > starting with Lenny on a daily business or without reason. I expect > that a real-life case (which Andreas B. didn't mention) is hidden > behind it and caused him to do that piuparts run. I'd also like to know this. :-) Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#775471: xserver-xorg-video-geode-dbg: copyright file missing after upgrade (policy 12.5)
Hey Andreas,
debian/rules uses this:
override_dh_installdocs:
dh_installdocs --link-doc=xserver-xorg-video-geode NEWS README TODO
Surely that would link the -dbg package's /usr/share/doc/foo-dbg to
.../foo, wouldn't it?
Martin-Éric
2015-01-16 5:21 GMT+02:00 Andreas Beckmann :
> Package: xserver-xorg-video-geode-dbg
> Version: 2.11.16-5
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> a test with piuparts revealed that your package misses the copyright
> file after an upgrade, which is a violation of Policy 12.5:
> https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile
>
> After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory.
>
> This was observed on the following upgrade paths:
>
> wheezy -> jessie
>
> >From the attached log (scroll to the bottom...):
>
> 3m56.0s ERROR: WARN: Inadequate results from running adequate!
> xserver-xorg-video-geode-dbg: missing-copyright-file
> /usr/share/doc/xserver-xorg-video-geode-dbg/copyright
>
> 3m59.5s DUMP:
> MISSING COPYRIGHT FILE:
> /usr/share/doc/xserver-xorg-video-geode-dbg/copyright
> # ls -lad /usr/share/doc/xserver-xorg-video-geode-dbg
> drwxr-xr-x 2 root root 40 Jan 15 11:43
> /usr/share/doc/xserver-xorg-video-geode-dbg
> # ls -la /usr/share/doc/xserver-xorg-video-geode-dbg/
> total 0
> drwxr-xr-x 2 root root 40 Jan 15 11:43 .
> drwxr-xr-x 185 root root 3840 Jan 15 11:43 ..
>
>
> Additional info may be available here:
> https://wiki.debian.org/MissingCopyrightFile
>
> Note that dpkg intentionally does not replace directories with symlinks
> and vice versa, you need the maintainer scripts to do this.
> See in particular the end of point 4 in
> https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase
>
> It is recommended to use the dpkg-maintscript-helper commands
> 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
> to perform the conversion, ideally using d/$PACKAGE.mainstscript.
> Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
> See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.
>
>
> cheers,
>
> Andreas
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#772195: [Pkg-fedora-ds-maintainers] Bug#772195: 389-ds-base: bashism in /bin/sh script
On 15.01.2015 08:18, Vagrant Cascadian wrote: > On 2014-12-10, Rowan Thorpe wrote: >> I've attached a debian-patch which hopefully addresses all of these >> (and one or two which checkbashisms didn't get). Please let me know if >> I missed anything. > > This seems like a patch that should be forwarded upstream, but maybe a > bit much to carry in Debian... wouldn't it make more sense to simply > depend on bash in this case? I've attached the patch to https://fedorahosted.org/389/ticket/47511 So the options are to add this to the package or change every violating script to invoke bash instead. I'll ask the release team which is more likely to get in jessie. -- t -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: severity 771205 grave
Processing commands for cont...@bugs.debian.org: > severity 771205 grave Bug #771205 [libgtk-3-0] libgtk-3-0: Scale bug in gtk which affect a lot gnome applications Severity set to 'grave' from 'important' > End of message, stopping processing here. Please contact me if you need assistance. -- 771205: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771205 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#774866: marked as done (libqglviewer2: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)
Your message dated Fri, 16 Jan 2015 11:48:33 +
with message-id
and subject line Bug#774866: fixed in libqglviewer 2.5.3+dfsg-2.1
has caused the Debian Bug report #774866,
regarding libqglviewer2: unhandled symlink to directory conversion:
/usr/share/doc/PACKAGE
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
774866: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774866
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libqglviewer2
Version: 2.5.3+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.
This was observed on the following upgrade paths:
squeeze -> wheezy (keeping the squeeze package) -> jessie
For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile
For other overwritten locations anything interesting may happen.
Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase
It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.mainstscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.
>From the attached log (usually somewhere in the middle...):
3m55.2s INFO: dirname part contains a symlink:
/usr/share/doc/libqglviewer2/README (libqglviewer2:amd64) !=
/usr/share/doc/libqglviewer-qt3-2/README (?)
/usr/share/doc/libqglviewer2 -> libqglviewer-qt3-2
/usr/share/doc/libqglviewer2/changelog.Debian.gz (libqglviewer2:amd64) !=
/usr/share/doc/libqglviewer-qt3-2/changelog.Debian.gz (?)
/usr/share/doc/libqglviewer2 -> libqglviewer-qt3-2
/usr/share/doc/libqglviewer2/changelog.gz (libqglviewer2:amd64) !=
/usr/share/doc/libqglviewer-qt3-2/changelog.gz (?)
/usr/share/doc/libqglviewer2 -> libqglviewer-qt3-2
/usr/share/doc/libqglviewer2/copyright (libqglviewer2:amd64) !=
/usr/share/doc/libqglviewer-qt3-2/copyright (?)
/usr/share/doc/libqglviewer2 -> libqglviewer-qt3-2
3m55.9s ERROR: FAIL: debsums reports modifications inside the chroot:
debsums: missing file /usr/share/doc/libqglviewer2/README (from
libqglviewer2:amd64 package)
debsums: missing file /usr/share/doc/libqglviewer2/changelog.Debian.gz (from
libqglviewer2:amd64 package)
debsums: missing file /usr/share/doc/libqglviewer2/changelog.gz (from
libqglviewer2:amd64 package)
debsums: missing file /usr/share/doc/libqglviewer2/copyright (from
libqglviewer2:amd64 package)
cheers,
Andreas
libqglviewer2_2.5.3+dfsg-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libqglviewer
Source-Version: 2.5.3+dfsg-2.1
We believe that the bug you reported is fixed in the latest version of
libqglviewer, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 774...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sebastian Ramacher (supplier of updated libqglviewer
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 15 Jan 2015 23:26:55 +0100
Source: libqglviewer
Binary: libqglviewer-dev libqglviewer-doc libqglviewer2
Architecture: source all
Version: 2.5.3+dfsg-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintai
Bug#759361: freerdp-x11: Segfaults on too-long command line with old-style options
Hi, On Di 26 Aug 2014 20:01:31 CEST, Peter Karbaliotis wrote: Package: freerdp-x11 Version: 1.1.0~git20140809.1.b07a5c1+dfsg-4 Severity: important xfreerdp -g 1920x1200 -d domain -u username -D -a 16 --plugin rdpsnd --plugin rdpdr -data disk media /home/username/media/ -x l --rfx --ignore-certificate --plugin cliprdr some.host.name.com WARNING: Using deprecated command-line interface! Segmentation fault I asked one of the freerdp upstream devs to look into this the coming week. Hoping for positive feedback from him. Mike (who agrees on the latest severity raisal to "grave") -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpEFDpO8K0tI.pgp Description: Digitale PGP-Signatur
Processed: severity of 759361 is grave
Processing commands for cont...@bugs.debian.org: > severity 759361 grave Bug #759361 [freerdp-x11] freerdp-x11: Segfaults on too-long command line with old-style options Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 759361: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759361 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#774924: marked as done (apt: Jessie version cannot find upgrade path (but Wheezy version can))
Your message dated Fri, 16 Jan 2015 11:03:29 + with message-id and subject line Bug#774924: fixed in apt 1.0.9.6 has caused the Debian Bug report #774924, regarding apt: Jessie version cannot find upgrade path (but Wheezy version can) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 774924: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774924 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: apt Version: 1.0.9.5 Severity: serious Hi, Based on the latest reports from jenkins.debian.net, it seems that Jessie's version of APT cannot fully complete the dist-upgrade while Wheezy's version can. Compare [1] with [2]. The difference is that in [2] we upgrade dpkg and APT alone prior to upgrading, while in [1] we start the upgrade with the current version of APT (i.e. the one from Wheezy). In the "dpkg + APT first" run[2], APT ends up concluding that "login" should be removed and aborts as it refuses the uninstall an essential package. In the regular run[1], the "login" package is (eventually) upgraded without any issues. Please note that there are more upgrade issues for reference at [3]. The general story is that upgrading "APT + dpkg first" fails, while not doing so works. For the sole case where the "original" upgrade test also fails, it is caused by the removal of sudo. I am not entirely sure if this is caused by a broken solution from APT or just the jenkins setup that needs changing. Anyway, that would be [4]. ~Niels [1] https://jenkins.debian.net/view/chroot-installation/view/upgrade%20wheezy2jessie/job/chroot-installation_wheezy_install_xfce_upgrade_to_jessie/515/consoleFull [2] https://jenkins.debian.net/view/chroot-installation/view/Problems/job/chroot-installation_wheezy_install_xfce_upgrade_to_jessie_aptdpkg_first/5/consoleFull [3] https://jenkins.debian.net/view/chroot-installation/view/Problems/ [4] https://jenkins.debian.net/view/chroot-installation/view/Problems/job/chroot-installation_wheezy_install_gnome_upgrade_to_jessie/519/console --- End Message --- --- Begin Message --- Source: apt Source-Version: 1.0.9.6 We believe that the bug you reported is fixed in the latest version of apt, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 774...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Vogt (supplier of updated apt package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 16 Jan 2015 08:37:25 +0100 Source: apt Binary: apt libapt-pkg4.12 libapt-inst1.5 apt-doc libapt-pkg-dev libapt-pkg-doc apt-utils apt-transport-https Architecture: source all amd64 Version: 1.0.9.6 Distribution: unstable Urgency: medium Maintainer: APT Development Team Changed-By: Michael Vogt Description: apt- commandline package manager apt-doc- documentation for APT apt-transport-https - https download transport for APT apt-utils - package management related utility programs libapt-inst1.5 - deb package format runtime library libapt-pkg-dev - development files for APT's libapt-pkg and libapt-inst libapt-pkg-doc - documentation for APT development libapt-pkg4.12 - package management runtime library Closes: 774893 774924 Changes: apt (1.0.9.6) unstable; urgency=medium . [ Michael Vogt ] * Fix missing URIStart() for https downloads * Add regression test for the previous commit . [ David Kalnischkies ] * 128 KiB DSC files ought to be enough for everyone (Closes: 774893) * award points for positive dependencies again (Closes: 774924) Checksums-Sha1: 41b1050ca18114cd26f7759b0b6a218b9223f9e2 2353 apt_1.0.9.6.dsc b93cbcae23b813a099e0cf7e41acb8b6bdc0c2a8 1822112 apt_1.0.9.6.tar.xz d6bf39fea076e9d85f6b1729db44af7d8d0f3a95 302428 apt-doc_1.0.9.6_all.deb ca70309659707528eefc300b3246a811ffe07ef2 781656 libapt-pkg-doc_1.0.9.6_all.deb e3a645b420fbf347fb181d04f8c627e7ae02c5e5 790200 libapt-pkg4.12_1.0.9.6_amd64.deb 33f9f38ccfcca1eac5c1bf08c0b5649c9971bec6 168102 libapt-inst1.5_1.0.9.6_amd64.deb 635d09fcb600ec12810e3136d51e696bcfa636a6 1107560 apt_1.0.9.6_amd64.deb 8d9b5e6694180f944da49f058069fa5e9867060d 193176 libapt-pkg-dev_1.0.9.6_amd
Bug#774890: Is this bug really RC?
Hi together, Andreas Tille wrote: > I stumbled upon this bug since it affects staden maintained by > Debian Med. Same here with gnudatalanguage. > When reading the bug report I stumbled upon > >The errors seems to date back to the lenny->squeeze update ... Well, you (Andreas T) did not cite a possible relevant part here: | This was observed on the following upgrade paths: | | lenny -> squeeze -> wheezy -> jessie Although this upgrade path is not 100% true for all involved packages. See below. > I'm seriously wondering whether this issue is RC critical for Jessie > release To be honest: I think this is generally an RC-level issue and should be fixed. But I also think, it's a candidate for a jessie-ignore tag as the bug has been in there for quite a while (obviously) and -- from a first glance at the log which Andreas B. attached -- has no operational impact, just legal impact (wrong copyright file, etc.). Cc'ing debian-release for that. (This does not mean that I think it can't be fixed for Jessie. I just think that it's not an urgent issue as it exists for about 5 years now.) > since we do not support upgrades over several releases. I'm not 100% sure what you mean with "upgrades over several releases". Let me elaborate: We definitely support sequent dist-upgrades, even if it's not explicitly mentioned anywhere. Everyone does them. There's no rule that you need to reinstall after one dist-upgrade and can't do the next one because it's not supported. What we don't support is upgrades where releases are skipped, e.g. upgrades directly from Squeeze to Jessie without first upgrading to Wheezy -- that's clearly not supported. So far so good, but the attached log shows a case not covered by either scenario above: A package (msort-gui) which was not part of the one release was kept installed for that release: During the squeeze state of that chroot, the msort-gui package from lenny was still installed and then upgraded to the Wheezy version with the dist-upgrade to Wheezy. So the package which triggered this issue is msort-gui which was not part of the Squeeze release. But itk3 was. So while this issue showed up in an unsupported scenario, it still could happen and be an issue in a supported scenario. (I initially thought, Andreas B. attached the wrong piuparts log, because it's not for itk3 but for msort-gui. But msort-gui depends on itk3 via iwidgets4 and the issue in itk3 indeed shows up in that log.) > Can you please be more verbose in how far this issue affects the > Jessie release? The issue was likely caused by this non-trivial change back in 2009 (3.3-1): * New upstream release, moving itk3 to a separate source package. Lenny had itcl3 and itk3 in version 3.2.1-5 and Squeeze itk3 version 3.3-2. As far as I understand it, the issue is that on a box which such a history, the file /usr/share/doc/itcl3/copyright is actually the copyright file of itk3 which comes from different source package. This clearly violates the policy and is hence RC. The issue exists probably since itk3/3.3-1 -- it just hasn't been found before as it has no operational impact. And piuparts back then probably didn't do _that_ kind of check. So this issue will persist until any later package fixes it. I though wonder how to fix it, since the copyright file of itcl3 already has been overwritten. May require a Breaks in itcl3, too, so that itk3 is first upgraded and can fix the issue, and the itcl3 upgrade then fixes the missing copyright file. Such a Breaks, which forces itk3 to fix the issue before itcl3 gets upgraded, likely also fixes the issues Sergei brought up in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774890#15 (which has been posted after I started writing this mail). One more thing I'm still curious about: How the fuck do you stumble upon such a bug? :-) I don't expect that Andreas runs piuparts starting with Lenny on a daily business or without reason. I expect that a real-life case (which Andreas B. didn't mention) is hidden behind it and caused him to do that piuparts run. Regards, Axel -- ,''`. | Axel Beckert , http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#774972: marked as done (libedit-dev: fails to upgrade from 'sid' - trying to overwrite /usr/share/man/man3/editline.3.gz)
Your message dated Fri, 16 Jan 2015 10:48:26 + with message-id and subject line Bug#774972: fixed in libedit 3.1-20141030-1~exp2 has caused the Debian Bug report #774972, regarding libedit-dev: fails to upgrade from 'sid' - trying to overwrite /usr/share/man/man3/editline.3.gz to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 774972: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774972 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libedit-dev Version: 3.1-20141030-1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package libedit-dev:amd64. Preparing to unpack .../libedit-dev_3.1-20141030-1~exp1_amd64.deb ... Unpacking libedit-dev:amd64 (3.1-20141030-1~exp1) ... dpkg: error processing archive /var/cache/apt/archives/libedit-dev_3.1-20141030-1~exp1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man3/editline.3.gz', which is also in package libeditline-dev 1.12-6.1 Errors were encountered while processing: /var/cache/apt/archives/libedit-dev_3.1-20141030-1~exp1_amd64.deb cheers, Andreas libeditline-dev=1.12-6.1_libedit-dev=3.1-20141030-1~exp1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: libedit Source-Version: 3.1-20141030-1~exp2 We believe that the bug you reported is fixed in the latest version of libedit, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 774...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru (supplier of updated libedit package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 12 Jan 2015 08:58:58 +0100 Source: libedit Binary: libedit2 libedit-dev libedit2-dbg Architecture: source amd64 Version: 3.1-20141030-1~exp2 Distribution: experimental Urgency: medium Maintainer: LLVM Packaging Team Changed-By: Sylvestre Ledru Description: libedit-dev - BSD editline and history libraries (development files) libedit2 - BSD editline and history libraries libedit2-dbg - BSD editline and history libraries (debug package) Closes: 774972 Changes: libedit (3.1-20141030-1~exp2) experimental; urgency=medium . * Fix a conflict on libedit manpage (Closes: #774972) Checksums-Sha1: ec809f022c83f725a542830c495028f7af74d725 2255 libedit_3.1-20141030-1~exp2.dsc 14e9543f183ae06d29d1f83a792abd0d992afdd6 10798 libedit_3.1-20141030-1~exp2.debian.tar.bz2 daf1751eb90d70926b0fbee66de76984d4a79a24 85792 libedit2_3.1-20141030-1~exp2_amd64.deb f3bfb515376c0e210e6f70b432d48699eb1989cb 101024 libedit-dev_3.1-20141030-1~exp2_amd64.deb bcf89c84bfd6c310fca0ef111927cdd660189c12 183686 libedit2-dbg_3.1-20141030-1~exp2_amd64.deb Checksums-Sha256: cc35210b6b497965988d779e012b050f0d842aff56ec02831e9e88c4681fc12e 2255 libedit_3.1-20141030-1~exp2.dsc e8d42e56cd37c6adad0d417a49c2bfea5b5e5bf611bbcfab40f774dfb584d0c1 10798 libedit_3.1-20141030-1~exp2.debian.tar.bz2 87627ec0bde1c0d0493cf157dd07c5f99e4114bcee4e29993a6ef87f214ad9f4 85792 libedit2_3.1-20141030-1~exp2_amd64.deb 586f15d92329446349b3424739a2d7f0ebf81d69f2a40a11761cfb57d035d1dd 101024 libedit-dev_3.1-20141030-1~exp2_amd64.deb ea49ef926efa689ec2f3fd67e6199e9d5f2fc6c44ac5c1d827e4404f1a288d3f 183686 libedit2-dbg_3.1-20141030-1~exp2_amd64.deb Files: 67da310d0e7f5162fd35c624c6277f35 2255 libs standard libedit_3.1-20141030-1~exp2.dsc 38087e677576030ea4535c7330b96b7d 10798 libs standard libedit_3.1-20141030-1~exp2.debian.tar.bz2 c72e28af672b1f221f26e9c0b8f30c6f 85792 libs standard libedit2_3.1-20141030-1~exp2_amd64.deb 52cc3d18b5f4ec220c77198a4a7038fd 101024 libdevel optional libedit-dev_3.1-20141030-1~exp2_amd64.deb 4e625cd5f47f2216778b456a92cf039c 183686 debug extra
Bug#774890: [Pkg-tcltk-devel] Bug#774890: itk3: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Hi Andreas, On Thu, Jan 8, 2015 at 8:46 PM, Andreas Beckmann wrote: > Hi, > > an upgrade test with piuparts revealed that your package installs files > over existing symlinks and possibly overwrites files owned by other > packages. This usually means an old version of the package shipped a > symlink but that was later replaced by a real (and non-empty) > directory. This kind of overwriting another package's files cannot be > detected by dpkg. > > This was observed on the following upgrade paths: > > lenny -> squeeze -> wheezy -> jessie > > The errors seems to date back to the lenny->squeeze update ... Yes, I see that. But I'm not sure if this bug is serious for now. And since even squeeze is already discontinued I'm not sure if this can be qualified as a bug at all. Though I can add calls to dpkg-maintscript-helper to the itk3 maintainer's scripts for jessie. It'll fix the overwriting the itcl3 package files, but upgrade path lenny->squeeze->wheezy->jessie will still fail leaving a few files unowned after the packages wil be purged (they are left from upgrades lenny->squeeze and squeeze->jessie): /usr/share/doc/itcl3/CHANGES.gznot owned /usr/share/doc/itcl3/INCOMPATIBLE.gz not owned /usr/share/doc/itcl3/README.gz not owned /usr/share/doc/itcl3/TODO not owned /usr/share/doc/itcl3/changelog.gz not owned But anyway, I'm tempted to just close this bugreport since it's reproducible for upgrades from really old distribution. Cheers! -- Sergei Golovan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: user debian...@lists.debian.org, affects 749722, found 774952 in 2014.2.1-3, unarchiving 769764 ...
Processing commands for cont...@bugs.debian.org:
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> affects 749722 + python-sss libpam-sss
Bug #749722 [libsss-sudo] libsss-sudo: modified /etc/nsswitch.conf after purge
Added indication that 749722 affects python-sss and libpam-sss
> found 774952 2014.2.1-3
Bug #774952 {Done: Thomas Goirand } [heat-common] heat-common:
fails to install: subprocess installed post-installation script returned error
exit status 10
Marked as found in versions heat/2014.2.1-3 and reopened.
> unarchive 769764
Bug #769764 {Done: Thomas Goirand } [ironic-common]
ironic-common: fails to upgrade from 'sid': No support for ALTER of constraints
in SQLite dialect
Unarchived Bug 769764
> found 769764 2014.2-3
Bug #769764 {Done: Thomas Goirand } [ironic-common]
ironic-common: fails to upgrade from 'sid': No support for ALTER of constraints
in SQLite dialect
Marked as found in versions ironic/2014.2-3 and reopened.
> close 769764
Bug #769764 [ironic-common] ironic-common: fails to upgrade from 'sid': No
support for ALTER of constraints in SQLite dialect
Marked Bug as done
> affects 775149 + task-lxde-desktop education-desktop-lxde
Bug #775149 [dictionaries-common] dictionaries-common: fails to install:
update-default-wordlist: Question empty but elements installed for class
"wordlist"
Bug #751367 [dictionaries-common] unupgradeable: "shared/packages-wordlist
doesn't exist"
Added indication that 775149 affects task-lxde-desktop
Added indication that 751367 affects task-lxde-desktop
> notfixed 708487 6.1.2-16
Bug #708487 [src:axe] axe: Please get rid of install-info call in maint-script
No longer marked as fixed in versions axe/6.1.2-16.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
708487: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708487
749722: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749722
751367: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751367
769764: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769764
774952: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774952
775149: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775149
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: axe: Please get rid of install-info call in maint-script
Processing control commands:
> tag -1 - wheezy + patch pending
Bug #708487 {Done: Hwei Sheng Teoh } [src:axe] axe: Please
get rid of install-info call in maint-script
Removed tag(s) wheezy.
Bug #708487 {Done: Hwei Sheng Teoh } [src:axe] axe: Please
get rid of install-info call in maint-script
Added tag(s) pending and patch.
> found -1 6.1.2-16.1
Bug #708487 {Done: Hwei Sheng Teoh } [src:axe] axe: Please
get rid of install-info call in maint-script
Marked as found in versions axe/6.1.2-16.1 and reopened.
--
708487: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708487
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#708487: axe: Please get rid of install-info call in maint-script
Control: tag -1 - wheezy + patch pending Control: found -1 6.1.2-16.1 On 2015-01-15 14:06, Andreas Beckmann wrote: > This needs to be fixed in wheezy-pu, too. > Since axe switched architecture from i386 to amd64, there is no upgrade > path from wheezy to jessie and the package from wheezy fails to remove > in jessie due to lack of install-info. > I'll prepare a patch. Or we can just build the package in i386 again, too and fix it in jessie instead by re-adding a dummy empty prerm script. NMU uploaded to DELAYED/2. Andreas axe_6.1.2-16.2.dsc.diff Description: application/pgp-keys
Bug#774877: marked as done (sympa: prompting due to modified conffiles which were not modified by the user: /etc/sympa/facility)
Your message dated Fri, 16 Jan 2015 09:20:49 + with message-id and subject line Bug#774877: fixed in sympa 6.1.23~dfsg-2 has caused the Debian Bug report #774877, regarding sympa: prompting due to modified conffiles which were not modified by the user: /etc/sympa/facility to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 774877: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774877 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sympa Version: 6.1.23~dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed the piuparts upgrade test because dpkg detected a conffile as being modified and then prompted the user for an action. As there is no user input, this fails. But this is not the real problem, the real problem is that this prompt shows up in the first place, as there was nobody modifying this conffile at all, the package has just been installed and upgraded... This is a violation of policy 10.7.3, see https://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3, which says "[These scripts handling conffiles] must not ask unnecessary questions (particularly during upgrades), and must otherwise be good citizens." https://wiki.debian.org/DpkgConffileHandling should help with figuring out how to do this properly. In https://lists.debian.org/debian-devel/2009/08/msg00675.html and followups it has been agreed that these bugs are to be filed with severity serious. >From the attached log (scroll to the bottom...): Setting up sympa (6.1.23~dfsg-1) ... Installing new version of config file /etc/init.d/sympa ... Configuration file '/etc/sympa/facility' ==> File on system created by you or by a script. ==> File also in package provided by package maintainer. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** facility (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package sympa (--configure): EOF on stdin at conffile prompt This was observed during an squeeze -> wheezy -> jessie upgrade test. cheers, Andreas sympa_6.1.23~dfsg-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: sympa Source-Version: 6.1.23~dfsg-2 We believe that the bug you reported is fixed in the latest version of sympa, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 774...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bouthenot (supplier of updated sympa package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 16 Jan 2015 02:48:12 +0100 Source: sympa Binary: sympa Architecture: source amd64 Version: 6.1.23~dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Sympa team Changed-By: Emmanuel Bouthenot Description: sympa - Modern mailing list manager Closes: 774877 Changes: sympa (6.1.23~dfsg-2) unstable; urgency=medium . * Fix a bug in /etc/sympa/facility conffile handling (Closes: #774877) * Add a patch to fix a vulnerability in the web interface (wwsympa) which allows one to send himself by email any readable file by the sympa user on the filesystem. Checksums-Sha1: 8531f4170cc6c8f7a408c7ba4564d3cd98b22c0a 2502 sympa_6.1.23~dfsg-2.dsc 746a03eac6e5164f1fbd36fd72700ba615e1 90064 sympa_6.1.23~dfsg-2.debian.tar.xz 40c4d2ca2cc5575737998696acf0e2f83375630e 2264036 sympa_6.1.23~dfsg-2_amd64.deb Checksums-Sha256: 5e1b9a101598f99a39a81189e849c4d6783bf7ab81f05622fdc9e8b2e09e82a6 2502 sympa_6.1.23~dfsg-2.dsc 557ff70a6f37c4c275961804308b07bcc0b7745469da0945812107603e044662 90064 sympa_6.1.23~dfsg-2.debian.tar.xz c0cb5e54cbe938d1e51221395e645e06e63f5323217ec8b4782f60b2dcacc68e 2264036 sympa_6.1.23~dfsg-2_amd64.deb Files: 7651a52d1b130e2ef697d424fcfa5d17 2502 mail optional sympa_6.1.23~dfsg-2.dsc 9a34ab2e23a5cc075c89f1473b848d11
Bug#774915: live-tools: fails to upgrade from 'wheezy': dpkg-divert: error: rename involves overwriting `/usr/bin/uptime' with different file
Followup-For: Bug #774915 Cleanup of obsolete diversions needs to be performed in postinst. This is a completely untested suggestion for live-tools.postinst to properly clean up the obsolete uptime diversions. = 8< = #!/bin/sh set -e if [ "$1" = "configure" ] then if dpkg --compare-versions "$1" lt-nl "4.0.2-2~" then dpkg-divert --package live-tools --remove --rename --divert /usr/bin/uptime.orig.procps /usr/bin/uptime dpkg-divert --package live-tools --remove --rename --divert /usr/share/man/man1/uptime.orig.procps.1.gz /usr/share/man/man1/uptime.1.gz fi fi #DEBHELPER# = >8 = Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#774890: Is this bug really RC?
Hi, I stumbled upon this bug since it affects staden maintained by Debian Med. When reading the bug report I stumbled upon The errors seems to date back to the lenny->squeeze update ... I'm seriously wondering whether this issue is RC critical for Jessie release since we do not support upgrades over several releases. Can you please be more verbose in how far this issue affects the Jessie release? Kind regards and thanks for your QA work Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#775479: phabricator: insecure configuration permissions
Source: phabricator Version: 0~git20141101-1 Severity: grave Tags: security Justification: user security hole Dear Maintainer, The local configuration created by the phabricator package under /usr/share/phabricator/conf/local is globally readable and contains sensitive information like phabricator's database credentials. Access to it should be restricted to only the necessary users (www-data and phabricator in our case). See also #775478 regarding the configuration location. Regards, Apollon -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing'), (90, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=el_GR.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#774328: [Pkg-samba-maint] Bug#774328: ctdb: Failed to start ctdb.service: Unit ctdb.service failed to load: No such file or directory.
On Tue, 13 Jan 2015 11:26:48 +0100, Mathieu Parent
wrote:
> 2014-12-31 23:16 GMT+01:00 Martin Schwenke :
> > # systemctl start ctdb
> > Failed to start ctdb.service: Unit ctdb.service failed to load: No such
> > file or directory.
> [...]
>
> Couldn't reproduce here. But I need to test again in a clean VM.
Yikes! :-(
> Anything relevant in /var/log/{syslog,ctdb/log.ctdb}? journalctl -u
> ctdb.service?
No, nothing at all. It looks like it is failing somewhere in systemd.
Well, I do get this from selinux:
Jan 16 18:52:20 rover kernel: audit: type=1107 audit(1421394740.536:41175):
pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='Unknown permission start for class system exe="/lib/systemd/systemd"
sauid=0 hostname=? addr=? terminal=?'
However, I am running in *permissive* mode, so selinux shouldn't be
getting in the way:
# sestatus | grep -i mode
Current mode: permissive
Mode from config file: permissive
My gut is telling me that this has something to do with the selinux
message... but how can this happen in permissive mode?
> Was this machine migrated from wheezy? Do you have rsyslog installed?
Yes, this machine was probably upgraded from wheezy. I have rsyslog
installed.
Do you know if there's a way of getting some debug out of systemd?
peace & happiness,
martin
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#775478: phabricator writes configuration data under /usr
Source: phabricator Version: 0~git20141101-1 Severity: serious Justification: Policy 9.1.1 Dear Maintainer, Phabricator as shipped in Debian writes its configuration under /usr/share/phabricator/conf. According to FHS ch. 4[1], /usr contains read-only data and should be shareable between systems. Please consider moving the configuration to /var/lib/phabricator and replacing /usr/share/phabricator/conf with a symlink. Regards, Apollon [1] https://www.debian.org/doc/packaging-manuals/fhs/fhs-2.3.html#PURPOSE18 -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing'), (90, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=el_GR.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#774868: [pkg-php-pear] php-pager is marked for autoremoval from testing
Hello, > It is affected by these RC bugs: > 774868: php-pager: unhandled symlink to directory conversion: > /usr/share/php/tests/Pager/tests I don't use php-pager myself, here is a quick tip: To fix this RC, build again the package with current pkg-php-tools (in testing=sid). See also #732641. Regards Mathieu Parent -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
