Bug#347103: intent to upload sponsored NMU to fix xlibs-dev bug
Please note that maintainer uploads are preferred to NMUs! If you are able to upload, then please do so. At the moment, I am not able to - please NMU. It's much appreciated! Cheers, -- Gergely Nagy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#608491: Problem Fix (was: Bug#608491: syslog-ng: log file permissions dangerous on kfreebsd-i386)
The problem is that chwon(fn, -1) works differently on Linux than on FreeBSD. Linux doesn't change the permissions if mode is -1, FreeBSD does. The workaround would be to test for -1 in syslog-ng and not call chmod in those cases. For the record, affile_open_file gets the same arguments even on Linux, yet, permissions are eventually set right there. Thus, the problem is entirely doe to chmod(fn, -1) behaving differently on the two systems. A patch should be easy to cook up, one should be incoming soon, just need to test it. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#608491: A little more info
The problem - at a first guess - will be somewhere in the config file parsing code or thereabouts. By the time syslog-ng gets to call fchown(), the file mode is set to a horribly wrong value: #1 0x00434d66 in affile_open_file (name=0x68e030 /var/log/syslog, flags=33285, uid=0, gid=4, mode=65535, dir_uid=0, dir_gid=0, dir_mode=65535, create_dirs=0, privileged=0, is_pipe=0, fd=0x7fffddbc) at affile.c:101 101 fchmod(*fd, (mode_t) mode); Current language: auto The current source language is auto; currently c. If one looks at the parameters passed to affile_open_file, one can notice that both mode and dir_mode are wrong. They're actually (int16_t)-1. This is on kfreebsd-amd64, so it looks like it's kfreebsd specific, and the arch doesn't matter. I will know more once I dived deeper in. With a bit of luck, I'll have a fix sometime tomorrow, unless someone beats me to it. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#608491: Fixed in upstream git
The issue is fixed in upstream git, differently than how Steven proposed: http://git.balabit.hu/?p=bazsi/syslog-ng-3.1.git;a=commitdiff;h=cbcea8c95c3f07ed9eaa4d12f124db8f8ca2f74b;hp=61181dca938d2cdd8233df2a07d6e0c76f049e6f Bazsi's solution is to use gint instead of mode_t, so that syslog-ng can continue using -1 as a special value. The actual chmod calls will only be made if the permissions are correct, though. I tested his patch on both Linux and kFreeBSD, and both behave after the patch as expected. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#646699: btrfs: Installer offers BTRFS an optional filesystem
reassign 646699 debian-installer thanks Maarten mvros...@gmail.com writes: Package: btrfs Severity: critical Justification: causes serious data loss BTRFS shouldn't be offert as a option filesystem in the debian installer. It is unsafe to use. Quallity is poor. No recovery possible on filesystem errors. (The btrfs driver will even crash on a filesystem error) The provided tool btrfsck doesn't actually do anything. There doesn't seem to be any progres on a working btrfsck. Atleased users should be warned to not use it, unless they don't care about dataloss There is no btrfs package in Debian, thus, this report did not reach any developers. Furthermore, since it is the installer that is allegedly at fault, it should be filed against the debian-installer package. I went ahead and reassigned it there. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#647840: r-cran-wavelets: Doesn't work with R 2.14.0
Andrey Paramonov cmr.apara...@gmail.com writes: Package: r-cran-wavelets Version: 0.2-6-1cran1 Hrm, I can't find any r-cran-wavelets package in Debian. It's not in incoming, either, and as far as I see, it wasn't removed, either. That suggest it didn't exist. Or that I'm missing something obvious. Are you sure your package is from Debian, and not some other source? (the version number suggests it's not from Debian proper) -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648673: gconf2: GConf Error in Emacs, Liferea, Evolution and others (D-BUS error)
Evolution does not find its configuration data either and throws error messages and starts with the new configuration dialog. (evolution:9622): evolution-shell-WARNING **: Der Konfigurationsserver konnte nicht kontaktiert werden: D-BUS-Fehler: Method GetDefaultDatabase with signature on interface org.gnome.GConf.Server doesn't exist gnome-shell (3.0) throws similar warnings, and refuses to start after upgrading gconf from 2.32.4 to 3.2.3. I suppose, pretty much everything that touches gconf breaks in similar ways. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#658220: kipi-plugins-1.9.0-3: Uninstallable
reassign 658220 kipi-plugins 1.9.0-3 thanks Michael Rasmussen m...@datanom.net writes: Package: kipi-plugins-1.9.0-3 The package name need not contain the version number. Reassigning to the correct package. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660940: usbfs error causes kdm to not load on startup or reboot
reassign 660940 kdm thanks Since there is no usbfs package in Debian, that thing is part of the kernel, and the bug happens with kdm, the workaround is made there, I'm reassigning this bug to the kdm package. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660940: usbfs error causes kdm to not load on startup or reboot
mckis...@gmail.com mckis...@gmail.com writes: This bug has a workaround. You can Insert a sleep 1 into the kdm init file just before it starts kdm. This prevents the timeout bug discovered by Linus years ago. Not sure why it regressed in Squeeze. That's all fine, but send this info to the bug, not to me. I don't use kdm, I just reassigned the bug to the appropriate place. (And with this message, I forwarded your comment to the bug too :P) -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651948: FTBFS: patches not applied
reassign 651948 dpatch found 651948 2.0.32 severity 651948 serious affects 651948 pinfo thanks Steve McIntyre st...@einval.com writes: [...] dpatch -d pinfo-0.6.9 apply-all applying patch 01_pinforc to /home/steve/build/pinfo/pinfo-0.6.9/pinfo-0.6.9 ...touch: cannot touch `src/pinforc.in': No such file or directory failed. make: *** [patch-stamp] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 Whether this is a bug in pinfo, dpkg-dev or dpatch I have no idea... Going back to a previous version (2.0.31) of dpatch makes this work. The build then fails later, but that's a different (expected) bug, #646486. dpatch people: is this a dpatch problem, or a bug in pinfo in terms of dpatch usage that's only showing up now? This is a bug in dpatch. I know what broke it, apologies for that. A fixed dpatch will be uploaded shortly. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556526: hurd - FHS violation: /libexec
Jérémie Koenig j...@jk.fr.eu.org writes: On Wed, Sep 7, 2011 at 11:07 AM, Philipp Kern pk...@debian.org wrote: On Mon, Nov 16, 2009 at 03:40:05PM +0100, Bastian Blank wrote: Hurd violates the FHS by using /libexec. This name seems to be only used by init and /etc/ttys. I'm upgrading this to serious on the grounds that this package is only useful on the non-release architecture hurd-i386 and it's clearly a policy violation that makes the package unsuitable for a release. There's a patch here: http://lists.archhurd.org/devel/msg00102.html. The patch moves /libexec/* to /etc. I guess /sbin (or maybe, /lib/hurd) would be more appropriate. What do you think? With my occassional Hurd user hat on, /lib/hurd sounds like the most appropriate place to put these stuff into, or failing that, /sbin. But definitely not /etc. Neither init, nor console-run strike me as things the user would wish to edit. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#641734: gdal1: FTBFS
reassign 641734 src:gdal thanks Alastair McKinstry mckins...@debian.org writes: Package: gdal1 Version: FTBFS for gdal 1.7.3 Severity: serious Tags: squeeze Justification: unkniown For this, see what Julien said. Please try to get at least the package or source name right. I'm reassigning it to src:gdal, so that the maintainer can deal with it further, and so that there'll be less packages misfiled against unknown packages. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643001: gource: cannot be installed on amd64: versioned depends on libglew1.5
Package: gource Version: 0.35-1+b1 Severity: serious Justification: fails to install/upgrade Trying to upgrade gource on amd64 results in the following: The following packages have unmet dependencies: gource : Depends: libglew1.5 (= 1.5.8) but it is not installable 0.35-1+b1 was already rebuilt against a suitable libglew1.6, same should be done for 0.37 aswell. And to avoid this kind of breakage, perhaps the build-dep could be bumped, so it won't build against old libglew1.5, that has been removed from unstable? -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gource depends on: ii libc6 2.13-21 ii libfreetype6 2.4.6-2 ii libgcc1 1:4.6.1-12 ii libgl1-mesa-glx [libgl1] 7.11-6 ii libglew1.61.6.0-4 ii libglu1-mesa [libglu1]7.11-6 ii libpcre3 8.12-4 ii libsdl-image1.2 1.2.10-2.1+b1 ii libsdl1.2debian 1.2.14-6.4 ii libstdc++64.6.1-12 ii libtinyxml2.6.2 2.6.2-1 ii ttf-freefont 20100919-1 ii zlib1g1:1.2.3.4.dfsg-3 gource recommends no packages. gource suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643001: gource: cannot be installed on amd64: versioned depends on libglew1.5
found 643001 0.37-1 thanks On Mon, Sep 26, 2011 at 14:16, Julien Cristau julien.cris...@logilab.fr wrote: I'm not sure what you're saying here. You're reporting this bug against 0.35-1+b1, which is already built against glew1.6. I'm saying that 0.37-1 is not built against glew1.6, but against 1.5. I merely forgot to change the version in the bugreport (which I'm fixing now). -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643304: python-awn-extras: can't install: unable to open '/usr/share/pyshared/awn/extras/__init__.py.dpkg-new'
Jakub Wilk jw...@debian.org writes: Disclaimer: I'm not maintainer of this package. * nick black d...@qemfd.net, 2011-09-27, 02:17: Retrieving bug reports... Done Parsing Found/Fixed information... Done (Reading database ... 336028 files and directories currently installed.) Unpacking python-awn-extras (from .../python-awn-extras_0.4.0-4_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/python-awn-extras_0.4.0-4_amd64.deb (--unpack): unable to open '/usr/share/pyshared/awn/extras/__init__.py.dpkg-new': No such file or directory configured to not write apport reports Hmm, I cannot reproduce it here. For what its worth, I had the same problem aswell. But I didn't have time to debug it further, so I created the dir, and touched __init__.py in it, that fixed the problem for me. I still have no idea why the unpacking failed, though. Removing the package and installing again does not result in an error, so I suppose the bug's somewhere in the upgrade. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#637797: virtualbox-4.1: vboxdrv causing Kernel Panic on shutdown
Dirk Blau dirkb...@ymail.com writes: Package: virtualbox-4.1 Severity: critical Justification: breaks the whole system There is no such package in Debian (especially not in stable). Can you try it with virtualbox (4.1.0-dfsg-2) aswell? If it happens there, this bug can be reassigned to the appropriate package. Otherwise it's a problem outside of Debian, and the bug should be reported to upstream. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#637797: virtualbox-4.1: vboxdrv causing Kernel Panic on shutdown
Dirk Blau dirkb...@ymail.com writes: Gergely Nagy alger...@madhouse-project.org: There is no such package in Debian (especially not in stable). Can you try it with virtualbox (4.1.0-dfsg-2) aswell? I'm not sure how to get exactly the package you mentioned installed. If you could give me a quick advise how to do that i'll give it a try. Well, to be honest, it's not going to be quick, as virtualbox 4.1 is not available for stable from Debian's repositories. So I'd suggest not even going there, after all. Synaptic shows the following version for the package i had installed: 4.1.0-73009~Debian~squeeze Let me guess, the maintainer is Oracle Corporation i...@virtualbox.org? And you have something like the following in /etc/apt/source.list: deb http://download.virtualbox.org/virtualbox/debian squeeze contrib non-free In this case, the package is from Oracle, not Debian, and the report should be filed with them: http://www.virtualbox.org/wiki/Bugtracker -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#632874: openni-dev: installation on pentium-M breaks with illegal instruction
Peter T. Breuer p...@inv.it.uc3m.es writes: Package: openni-dev Version: 1.1.0.41-5+maverick1 Severity: serious Justification: unknown. Probably bit that says install routine should run! May I ask where did you get the package from? I can't find an openni-dev package neither in stock Debian, nor in Ubuntu. The closest I could find, which matches the version above is this PPA: https://launchpad.net/~v-launchpad-jochen-sprickerhof-de/+archive/pcl If your package came from there, the bug should be reported there aswell, as the package does not exist in Debian. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690067: syslog-ng-core: symlink conffile issues
Enrico Zini enr...@enricozini.org writes: On Mon, Oct 15, 2012 at 11:56:16AM +0200, Gergely Nagy wrote: Mostly for myself, but replacing the symlinks with real conffiles that .include the former symlink targets may be an even better course of action. I'll test that over the next few days, and see how upgrades behave. Hi, any news? Sorry, I forgot to follow up on this it seems. I tested the unit files that simply .include'd the real ones, and that works nicely. Tested the upgrade path too, seems smooth. I promised the maintainer to prepare patches suitable for wheezy, including this one, but did not get around to do them yet. With a bit of luck, I'll have some free time to make this happen around next week. (For what it's worth, the fix is available in my git tree at [1] and [2]) [1]: https://github.com/algernon/syslog-ng/commit/cd7611244c818ccc14328cddb20467adb9d7851f.patch [2]: https://github.com/algernon/syslog-ng/commit/da0cd112858fef0b6263233877edee13ff890d90.patch -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690067: what is to be done?
Csillag Tamas csta...@digitus.itk.ppke.hu writes: The patch seems fine to me. Is something missing? Is something still needs to be done? I still need to prep the other things. I most likely will have time this coming friday. For the record, pretty much everything that needs to be fixed, is fixed in my tree[1], on either on my packaging/debian/3.3 or packaging/debian/3.4 branches - all the work left now is to diff the packaging against those trees, and pick the relevant fixes for this bug, and others. [1]: https://github.com/algernon/syslog-ng/ -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696199: closed by Ivo De Decker ivo.dedec...@ugent.be (Re: Build-Depends autoconf 2.68)
Control: severity -1 normal From: Ivo De Decker ivo.dedec...@ugent.be To: 696199-d...@bugs.debian.org Date: Tue, 18 Dec 2012 22:40:31 +0100 Subject: Re: Build-Depends autoconf 2.68 Hi, On Tue, Dec 18, 2012 at 01:08:11AM +0100, Mathieu Malaterre wrote: dh-exec fails to build on debian/stable with: dh-exec is not available in stable (squeeze), so there is no reason to expect it to build in squeeze. First of all, please don't close bugs opened against my packages, unless you opened them yourself, or asked me first. I happen to agree with the reporter, this *is* a bug, although not a serious one. Your package as-is cannot be backported. If there is an implicit dependency, it is required to be versioned explicitly in d/control (there are older versions of autoconf in the archive). Not in the suites dh-exec was prepared for. Ancient versioned dependencies are not much more than noise. However, making backporting easier is a reasonable wish, so I'll add the explicit autoconf = 2.68 dependency. (That, or fix my configure to work on squeeze, if that's not too hard) If you do not want to upload, I can NMU your package. I will upload a backportable version, targetting unstable. I don't believe this issue warrants a freeze exception however, so I'm not going to pursue that. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#697270: PC 32-bit programs fails to work on amd64
Control: reassign -1 general Alexey Eromenko al4...@gmail.com writes: Package: kernel-image Version: 3.2.0 severity: serious (kernel-image-3.2.0-4-amd64-di) Dear developers, 32-bit programs, such as FireFox refuse to work on Debian 7.0 64-bit (amd64). This is new fresh stock install from di-BETA4 Wheezy DVD. (KDE) The same works great on Debian 6.0 64-bit ! This is because you do not have 32 bit libraries installed, you have to enable multi-arch: http://wiki.debian.org/Multiarch/HOWTO Meanwhile, I'm reassigning the issue to general, as it is not kernel related. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#697270: PC 32-bit programs fails to work on amd64
Alexey Eromenko al4...@gmail.com writes: User error? Huh ? It is, I'm afraid. No ! This is a Debian Bug ! No, it is not. Debian clearly says: File does not exist, while in fact it DOES EXIST. It does not. However, the file the message is referring to is not the file you think it refers to: it is missing the 32-bit dynamic linker, /lib32/ld-linux.so.2 (available in the package libc6-i386), not the firefox binary itself. The message is a bit confusing, indeed, but without a dynamic linker present, it's hard to do any better. This is a 100% proof of Debian bug. You installed a 32-bit application on a 64-bit system. That will only work if you also install the 32-bit supporting libraries, including the dynamic linker. This is not a bug in Debian. And no, installing 32-bit libraries by default would be a bad idea, for a multitude of reasons. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690067: syslog-ng-core: symlink conffile issues
Control: tag -1 + pending The easy fix is to remove debian/syslog-ng-core.conffiles. That has the downside of not allowing the user to easily change the symlink to point somewhere else (like a custom unit file) unless he diverts the file, which is kind of awkward. But alas, that's still less trouble than causing a mess with symlink conffiles, apparently. I've fixed it in my git tree, will poke GCS to pick it over for the next syslog-ng upload. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690067: syslog-ng-core: symlink conffile issues
Gergely Nagy alger...@balabit.hu writes: The easy fix is to remove debian/syslog-ng-core.conffiles. That has the downside of not allowing the user to easily change the symlink to point somewhere else (like a custom unit file) unless he diverts the file, which is kind of awkward. But alas, that's still less trouble than causing a mess with symlink conffiles, apparently. I've fixed it in my git tree, will poke GCS to pick it over for the next syslog-ng upload. Mostly for myself, but replacing the symlinks with real conffiles that .include the former symlink targets may be an even better course of action. I'll test that over the next few days, and see how upgrades behave. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#385844: libmikmod: diff for NMU version 3.1.12-4.1
I'll try to get around to do an upload in the next couple of days. I've prepared an NMU for libmikmod (versioned as 3.1.12-4.1) and uploaded it to DELAYED/7. Please feel free to tell me if I should cancel it or delay it longer. Thanks for the NMU, it's appreciated! However, there is one problem with the change: I used Suggests: oss-compat, and pulseaudio-esd was added to the suggests line, it was not bumped to Recommends as the changelog would suggest. Since the fallback to writing music.raw is undesirable, I believe it would be more useful to bump that suggests up to a recommends. Other than that, it looks good. So if you could also bump the Suggests to Recommends, and upload directly to unstable, that would be grand. Thanks in advance! One problem with the packaging style used in your git repository is that the master branch (and its tags) don't track which patches were applied: [...] Indeed, the workflow I'm using with libmikmod isn't particularly good. I was still experimenting at the time, and that shows. It will be changed eventually, so that tracking which patches were applied when will be clear, and won't require any digging outside of the git tree. Thanks for your work! -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690992: Missing dependency on libglib2.0-dev
found 690992 libmongo-client-dev 0.1.5-1 thanks On Fri, Oct 19, 2012 at 10:58 PM, Michael Biebl bi...@debian.org wrote: Package: libmongo-client-dev Version: 0.1.6.1-2 Severity: serious This also affects the version in wheezy too. I'll prepare an upload for both, thanks for the report! -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675925: Please upload a fixed accountsservice ASAP
I updated my workstation this morning, and got bit by this issue aswell. I had to downgrade to a previous version, because my system is deeply tied to systemd by now, it doesn't boot correctly with sysvinit, so the accountsservice breakage with it was a bit of a pain in the backside. I'd like to kindly ask you to upload a fixed package ASAP. If you're lacking time or opportunity to do so, since the fix appears to be in git already, I'll happily NMU it for you. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666196: closed by Scott Kitterman deb...@kitterman.com (Not sure why this got reopened)
I checked and zorp depends on python-radix in both Sid and Wheezy. Zorp does, but python-kzorp, which uses python-radix (and does not depend on zorp) does not. The dependency was added, but not to the right package. Granted, python-kzorp is kind-of useless without zorp, but accidentally satisfying dependencies is, well, accidental, and as such, not quite appropriate. On the other hand, this most likely won't affect anyone anyway, so *shrug* -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681115: powerdns-server: unexisting parameter 'bind-config'
reassign 681115 pdns-server 3.1-4 thanks Werner Detter wer...@aloah-from-hell.de writes: Package: powerdns-server Version: pdns When reporting bugs, please try to make sure you report it against a package that exists (reportbug can help there, it will - as far as I remember - warn you if you try to report a bug against something that it does not know about), and use an actual version number. Failing to do so, your report will not reach the maintainers unless someone reassigns the bug report like I did now. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682752: cups-filters: debian/copyright is misleading/incomplete
Source: cups-filters Version: 1.0.18-2 Severity: serious Justification: Policy 12.5 While casually looking through a few randomly selected debian/copyright files, I noticed that the copyright file for cups-filters is seriously misleading and incomplete. For example, it lists the Debian maintainer as the copyright owner of install-sh, configure, CHANGES.txt and a few others, with GPL-2+ as the license. At least install-sh is wrong in that list, as it is not under the GPL-2, and was written by Apple/MIT. The licenses of files under filter/fontembed are not documented at all, nor is filter/PDFError.h. I have not checked further than these, but this is already enough to report a serious bug, as licenses for *all* files must be properly documented, and not misattributed. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#385844: libmikmod: Uses deprecated /dev/dsp interface on Linux
Ben Hutchings b...@decadent.org.uk writes: Suggesting oss-compat does *not* fix this bug. It does provide a workaround until such time when a proper fix can be put in place, which is something that cannot reasonably be done for wheezy, however unfortunate. Upstream activity on this front is virtually non-existant, I tried to port libmikmod's ALSA driver to modern alsa, but what I once knew about alsa, I forgot long ago, so that effort was put on hold until I - or someone else - has more time to deal with it, post wheezy. I am well aware of the shortcomings of the workaround, and I do agree it needs to be fixed properly at one point, but unless I get a patch to bring the ALSA driver into shape, it won't happen for wheezy :/ As such, I'd like to ask for a wheezy-ignore tag for this one. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684175: pokernetwork: calls addgroup without --system
reassign 684175 python-poker-network 1.7.7-3.2 thanks Andreas Beckmann deb...@abeckmann.de writes: Package: pokernetwork [...] [python-poker-network_1.7.7-3.2.log.gz (application/x-gzip, attachment)] pokernetwork != python-poker-network. Bug reassigned accordingly. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684479: wheezy: Network File Services are major issue in Wheezy.
reassign 684479 general thanks Hughe Chung maildeliverag...@gmail.com writes: Package: wheezy Version: Wheezy When filing bugs, especially with reportbug, please make sure you file it against a package that exist, or a pseudo-package reportbug knows about, otherwise your report will not end up sent to the maintainers. I have reassigned your report to 'general' for now, lacking a better idea. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685714: json-c: NMU proposal to fix the missing header file
I just ran into this while trying to build syslog-ng on a fresh unstable system. To avoid having to go an extra mile to fix my autobuilders, I plan to NMU json-c with the patch attached. Unlike Steve's fix, this is merely a workaround, that adds the missing header to debian/libjson0-dev.install. This way, the extra build-dependency on dh-autoreconf is not needed, and if and when upstream integrates the fix, all that needs to be done is remove one line from the install file. To me, this sounds ligther, and as such, I will upload to DELAYED/0 in a few moments. -- |8] diff -Nru json-c-0.10/debian/changelog json-c-0.10/debian/changelog --- json-c-0.10/debian/changelog 2012-08-17 18:57:36.0 +0200 +++ json-c-0.10/debian/changelog 2012-08-27 12:57:51.0 +0200 @@ -1,3 +1,11 @@ +json-c (0.10-1.1) unstable; urgency=low + + * Non-maintainer upload. + * Include the missing json_object_iterator.h header in +libjson0-dev. (Closes: #685714) + + -- Gergely Nagy alger...@madhouse-project.org Mon, 27 Aug 2012 12:56:32 +0200 + json-c (0.10-1) unstable; urgency=low * New upstream release (Closes: #684058) diff -Nru json-c-0.10/debian/libjson0-dev.install json-c-0.10/debian/libjson0-dev.install --- json-c-0.10/debian/libjson0-dev.install 2011-08-13 00:22:06.0 +0200 +++ json-c-0.10/debian/libjson0-dev.install 2012-08-27 12:51:28.0 +0200 @@ -3,3 +3,4 @@ usr/lib/*/libjson.so usr/include/* usr/lib/*/pkgconfig +json_object_iterator.h /usr/include/json/
Bug#666196: zorp: Missing dependency on python-radix
Package: zorp Version: 3.9.5-3 Severity: serious Justification: Policy 7.2 Zorp's /usr/share/zorp/pylib/Zorp/Zone.py imports 'radix', which is provided by the python-radix package. Without that installed, attempting to start zorp will result in an import error and a backtrace. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages zorp depends on: ii adduser 3.113+nmu1 ii libc6 2.13-26 ii libglib2.0-02.30.2-6 ii libssl1.0.0 1.0.0g-1 ii libzorp3.9 3.9.5-3 ii libzorpll3.9-1 3.9.1.3-1 ii python 2.7.2-10 ii python-dns 2.3.6-1 ii python-kzorp3.9.5-3 ii python-openssl 0.13-1 ii python-support 1.0.14 zorp recommends no packages. Versions of packages zorp suggests: pn zorp-doc none pn zorp-modules none -- Configuration Files: /etc/zorp/instances.conf.sample [Errno 13] Permission denied: u'/etc/zorp/instances.conf.sample' /etc/zorp/policy.py.sample [Errno 13] Permission denied: u'/etc/zorp/policy.py.sample' /etc/zorp/zorpctl.conf [Errno 13] Permission denied: u'/etc/zorp/zorpctl.conf' -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#665905: syslog-ng: fails to install, remove, distupgrade, and install again
Andreas Beckmann deb...@abeckmann.de writes: Package: syslog-ng Version: 3.3.4.dfsg-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install (in 'squeeze'), remove (but not purge), distupgrade to 'wheezy', and install again. Oh, damn, this'll be horrible to fix. The logrotate file was moved from the syslog-ng package to syslog-ng-core, and the postinst/preinst magic that was supposed to disable rotation if the package is removed (but not purged) bit me. Personally, I'd lower the severity to important, since the package CAN be installed again in wheezy if it was removed in squeeze, if one answers the prompt. Nevertheless, I'll leave it at serious for now, and try to figure out how to fix the situation properly. Thanks for the report! By the way, may I ask what version of piuparts you used? Mine (on sid) does not seem to know the --install-remove-install option, which is needed to trigger this bug. (I've been testing the package with piuparts and manually too - to make sure upgrades work after the split. I never thought of the install+remove in squeeze followed by a reinstall in wheezy scenario...) -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#665905: syslog-ng: fails to install, remove, distupgrade, and install again
tag 665905 + patch thanks Nevertheless, I'll leave it at serious for now, and try to figure out how to fix the situation properly. Turns out, once I understood the problem, fixing it was rather trivial. Patch attached. -- |8] commit b0b2a4f541c15941d0038229ee75fa5692ba2e64 Author: Gergely Nagy alger...@balabit.hu Date: Fri Apr 6 16:39:15 2012 +0200 debian: Fix the squeeze-wheezy install-remove-install upgrade When one installed syslog-ng in squeeze, and removed it, then dist-upgrades to wheezy, and tries to install syslog-ng again, it won't automatically work, because the logrotate script was moved from syslog-ng to syslog-ng-core, and the preinst wasn't clever enough to deal with this situation. The way to solve this is to move the .disabled file back to its place under the following conditions (assuming the postinst is called with 'install' as its first parameter, and the .disabled file exists): * It's either an install when there was a former syslog-ng-core version. * Or it's an install where there was no former syslog-ng-core installation, and the destination file doesn't exist yet. This supports both the install-remove-install case that span squeeze-wheezy, and works even between wheezy-wheezy versions. Reported-by: Andreas Beckmann deb...@abeckmann.de Signed-off-by: Gergely Nagy alger...@balabit.hu Closes: #665905 diff --git a/debian/syslog-ng-core.preinst b/debian/syslog-ng-core.preinst index 1f7d8c4..9296632 100644 --- a/debian/syslog-ng-core.preinst +++ b/debian/syslog-ng-core.preinst @@ -2,8 +2,14 @@ set -e -if [ $1 = install -a -n $2 ] ; then - [ -f /etc/logrotate.d/syslog-ng.disabled ] mv -f /etc/logrotate.d/syslog-ng.disabled /etc/logrotate.d/syslog-ng +if [ $1 = install ]; then +if [ -f /etc/logrotate.d/syslog-ng.disabled ]; then +if [ -n $2 ]; then +mv -f /etc/logrotate.d/syslog-ng.disabled /etc/logrotate.d/syslog-ng +elif [ ! -f /etc/logrotate.d/syslog-ng ]; then +mv -f /etc/logrotate.d/syslog-ng.disabled /etc/logrotate.d/syslog-ng +fi +fi fi #DEBHELPER#
Bug#672457: syslog-ng: FTBFS on non-linux architectures, due to missing systemd symlinks
Source: syslog-ng Version: 3.3.5-1 Severity: serious Justification: Fails to build from source on non-linux architectures syslog-ng fails to build from source on non-linux architectures, due to the systemd symlinks under /etc/systemd being in debian/syslog-ng-core.conffiles. These symlinks are only installed on Linux, however: ifeq (linux,$(shell dpkg-architecture -qDEB_BUILD_ARCH_OS)) install -d debian/syslog-ng-core/etc/systemd/system/multi-user.target.wants ln -sf /lib/systemd/system/syslog-ng.service \ debian/syslog-ng-core/etc/systemd/system/syslog.service ln -sf /lib/systemd/system/syslog-ng.service \ debian/syslog-ng-core/etc/systemd/system/multi-user.target.wants/ cp -r debian/tmp/lib debian/syslog-ng-core/ endif This should be changed to run unconditionally, on all architectures, and instead of copying debian/tmp/lib to the syslog-ng-core package, install the service file ourselves, not relying on the upstream build system to do it (since it will only do that on linux, when systemd is enabled). I'll submit a patch later to do just this. Sadly, the FTBFS is my fault, the above code is mine. Should've realized that we need to install the files in .conffiles, or things will break. Next time, I'll test my changes on kFreeBSD Hurd aswell. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages syslog-ng depends on: ii syslog-ng-core 3.3.5-1 ii syslog-ng-mod-json 3.3.5-1 ii syslog-ng-mod-mongodb 3.3.5-1 ii syslog-ng-mod-sql 3.3.5-1 syslog-ng recommends no packages. syslog-ng suggests no packages. -- no debconf information -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672457: syslog-ng: FTBFS on non-linux architectures, due to missing systemd symlinks
tags 672457 + patch
thanks
The attached patch should - I believe - fix the issue. It will result in
shipping the systemd control files and the symlinks on every arch, even
when systemd is not used, even when support is not compiled into
syslog-ng.
They do no harm, and if any of these non-linux platforms grow systemd
support overnight, we'll have the files there. Plus, our conffiles are
consistent over architectures this way, which is great.
--
|8]
--- a/debian/rules 2012-05-11 12:00:38.213446208 +0200
+++ b/debian/rules 2012-05-11 12:00:42.813469008 +0200
@@ -129,14 +129,13 @@
override_dh_auto_install:
dh_auto_install
${MAKE} -C debian/build-tree/lib/ivykis install DESTDIR=$(CURDIR)/debian/tmp
-ifeq (linux,$(shell dpkg-architecture -qDEB_BUILD_ARCH_OS))
- install -d debian/syslog-ng-core/etc/systemd/system/multi-user.target.wants
+
ln -sf /lib/systemd/system/syslog-ng.service \
debian/syslog-ng-core/etc/systemd/system/syslog.service
ln -sf /lib/systemd/system/syslog-ng.service \
debian/syslog-ng-core/etc/systemd/system/multi-user.target.wants/
- cp -r debian/tmp/lib debian/syslog-ng-core/
-endif
+ install -m 0644 contrib/systemd/syslog-ng.service \
+ debian/syslog-ng-core/lib/systemd/system/
##
#* Overrides for other debhelper commands
diff --git a/debian/syslog-ng-core.dirs b/debian/syslog-ng-core.dirs
index b2c4a17..73a42f6 100644
--- a/debian/syslog-ng-core.dirs
+++ b/debian/syslog-ng-core.dirs
@@ -1 +1,3 @@
/etc/syslog-ng/conf.d/
+/etc/systemd/system/multi-user.target.wants/
+/lib/systemd/system/
Bug#672477: dh_strip --dbg-package broken
Ondřej Surý ond...@debian.org writes: Package: debhelper Version: 9.20120509 Severity: grave Tags: sid Hi, the recent debhelper update broke every dh_strip --dbg-package out there, unless of course the .build-id/* is intentional: debhelper (8.9.13) unstable; urgency=low [...] * dh_strip: Use build-id in /usr/lib/debug in v9. Closes: #642158 Thanks, Jakub Wilk And why would .build-id/ break anything, when it is supported by gdb? (The 'recent' update is from december 2011, by the way) -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#385844: libmikmod: Uses deprecated /dev/dsp interface on Linux
Pantelis Koukousoulas pkt...@gmail.com writes: There is a possible solution to this: 1) There is a patch in Fedora for many years now that fixes the esd output driver Thanks for the notice porting, I'll take a look! Also, the newest libmikmod release supposedly has correct alsa2 support, which would be even better. I started reviewing that already, but at this point in the freeze, it's probably better to go with the esd patch instead of a whole new upstream version. I'll try to get around to do an upload in the next couple of days. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690067: pending
Control: tag -1 pending I adapted the patch sent for #713982, the change is available in git[1], so the next syslog-ng upload will use dh-systemd, and have all the remaining systemd-related shortcomings fixed. [1]: https://github.com/algernon/syslog-ng/commits/packaging/debian/3.3 Thanks a lot for the patches and the help! (It will likely take a few more days to upload syslog-ng, and it will have to go through NEW as well.) -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708793: syslog-ng 3.3.6-2 FTBFS with ivykis 0.36-2
The problem here is that lib/mainloop.c does not #include iv_event.h, even though it uses stuff from it. Prior to ivykis 0.36, iv_event.h was included by iv.h, so this problem did not surface. With 0.36, it does, and the simplest fix is to apply this patch to syslog-ng: https://github.com/algernon/syslog-ng/commit/92c3dd3b35badf1d866961cafb57dee3b5cc8abb Or, even better, package a newer upstream version, 3.3.9 or 3.4.1. Though, from the 3.4 branch, 3.4.2 is expected to be released in a week or two, so I'd suggest packaging 3.3.9 instead, which already contains the above fix. As for packaging new ivykis versions: I'm following the stable-* branches, and 0.36 is thet latest from there. 0.39, while newer, is not something I would package. (I discussed this with ivykis upstream, and will move the ivykis package to another version if and when he makes a new stable release). Regarding this problem, it simply needs a newer syslog-ng. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701991: maven3: CVE-2013-0253
Control: reassign -1 src:maven Moritz Muehlenhoff j...@inutil.org writes: Package: maven3 There is no maven3 package, so I'm reassigning to maven, which does have a version = 3, so I assume it is the package you meant to file the bug against. Severity: grave Tags: security Justification: user security hole Please see http://maven.apache.org/security.html for details. Cheers, Moritz -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702131: syslog-ng childs segfault, eventfd2: Invalid argument
Martin Zobel-Helas zo...@debian.org writes: Package: syslog-ng Version: 3.3.5-2 [...] when trying to start syslog-ng on gabrielli.debian.org I see the following error: root@gabrielli:/var/lib/syslog-ng# /etc/init.d/syslog-ng start [] Starting system logging: syslog-ngeventfd2: Invalid argument failed! root@gabrielli:/var/lib/syslog-ng# [...] This is a known problem in the underlying ivykis library, and can be fixed by applying a patch to lib/ivykis, something along these lines: https://github.com/buytenh/ivykis/commit/89f67f97477aeba24aebfc58ae1a17e5bea69724.patch It will need some minor changes, as the ivykis included with 3.3.5 is a bit different from upstream. I then can see syslog-ng master-process spawining childs, which segfault immidiatly: http://paste.debian.net/239439/ This sounds like another issue, also in ivykis, but a race condition: https://github.com/buytenh/ivykis/commit/144b88cbe4a04d53acbf4525d06cc1860571d36f.patch This should apply reasonably cleanly to lib/ivykis aswell. Both problems affect unstable aswell, but there the problem needs to be fixed in the ivykis library, I'll clone the bug report shortly. Since the syslog-ng maintainer already prepared an upload targeted at wheezy that fixes other RC bugs, these two patches should be added to that mix too. Nevertheless, I'll prepare an NMU later today and will prod the release team to let it through t-p-u (unstable has a whole new syslog-ng upstream version). Build-depends for syslog-ng for wheezy are installed on host gabrielli.debian.org in the wheezy chroot. I'll run some tests there with the fixes today, and will follow up with the results to this bug report. Thanks for reporting the help so far! -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702131: syslog-ng childs segfault, eventfd2: Invalid argument
Gergely Nagy alger...@balabit.hu writes:
This is a known problem in the underlying ivykis library, and can be
fixed by applying a patch to lib/ivykis, something along these lines:
https://github.com/buytenh/ivykis/commit/89f67f97477aeba24aebfc58ae1a17e5bea69724.patch
It will need some minor changes, as the ivykis included with 3.3.5 is a
bit different from upstream.
The attached patch should fix the eventfd2 errors, and make the code
properly fall back to whatever it normally falls back to.
I then can see syslog-ng master-process spawining childs, which segfault
immidiatly:
http://paste.debian.net/239439/
This sounds like another issue, also in ivykis, but a race condition:
https://github.com/buytenh/ivykis/commit/144b88cbe4a04d53acbf4525d06cc1860571d36f.patch
This should apply reasonably cleanly to lib/ivykis aswell.
Turns out, this doesn't apply cleanly, or at all. It is not needed
either, as the code in syslog-ng's ivykis fork does not suffer from this
problem. The crash is likely due to something else, perhaps even related
to the eventfd fix.
I have not been able to reproduce the crash in the wheezy chroot on
gabrielli, unfortunately. I'm trying to figure something out using
valgrind on x86, perhaps that'll help.
Meanwhile, if I could get access to the core file that was generated,
that may help, or at least aid me in figuring out how to reproduce the
problem on my own.
--
|8]
--- iv_event_raw.c.orig 2013-03-03 17:11:37.548279231 +0100
+++ iv_event_raw.c 2013-03-03 17:11:00.664356074 +0100
@@ -91,7 +91,7 @@
ret = eventfd2(0, EFD_NONBLOCK | EFD_CLOEXEC);
if (ret 0) {
- if (errno != ENOSYS) {
+ if (errno != ENOSYS errno != EINVAL) {
perror(eventfd2);
return -1;
}
Bug#702131: syslog-ng childs segfault, eventfd2: Invalid argument
Control: tag -1 patch Gergely Nagy alger...@balabit.hu writes: I then can see syslog-ng master-process spawining childs, which segfault immidiatly: http://paste.debian.net/239439/ This sounds like another issue, also in ivykis, but a race condition: https://github.com/buytenh/ivykis/commit/144b88cbe4a04d53acbf4525d06cc1860571d36f.patch This should apply reasonably cleanly to lib/ivykis aswell. Turns out, this doesn't apply cleanly, or at all. It is not needed either, as the code in syslog-ng's ivykis fork does not suffer from this problem. The crash is likely due to something else, perhaps even related to the eventfd fix. Turns out, it *is* related to the eventfd bug. What happens is, syslog-ng tries to register an event, but that doesn't work, and instead of aborting, it goes and and tries to post that event, which results in a segfault. Since ivykis can now fall back to $whatever, the event registration succeeds, and all is well. I reproduced the original issue on gabrielli, and after fixing the eventfd bug, I could not reproduce the crash anymore, either. So the patch I attached earlier should be enough. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690067: Bug#702195: symlink conffiles are not supported, causing problems for dpkg on upgrade/removal and incorrect debsums reports
Laszlo Boszormenyi (GCS) g...@debian.hu writes: On Wed, 2013-03-06 at 13:17 +0100, Michael Biebl wrote: 1/ as you no longer mark the symlinks as conffiles, the cleanup in syslog-ng-core.postrm is not necessary. Removed. 2/ you need to remove the existing conffile symlinks in syslog-ng-core.preinst so dpkg converts it to non-conffiles on upgrades Remove those in preinst. 3/ please drop the line ExecStartPre=/bin/systemctl stop systemd-kmsg-syslogd.service from syslog-ng.service. The systemd-kmsg-syslogd.service service has been removed a long time ago and future versions of systemd will generate an error if you stop a non-existing service. Gergely told he had this change in his Git repo already. Line removed, added other fixes from the Git repo. I checked just now, and some things were picked from the merge-queue/3.5 branch (the default branch on github), namely Type=notify - that is not supported by syslog-ng 3.3, and will be new in 3.5. Other than that, Michael already said what I would've, just better. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702131: syslog-ng childs segfault, eventfd2: Invalid argument
Right, this affects unstable too, as I wrote before, but in unstable, there's nothing in syslog-ng that needs fixing, except a recompile against a newer ivykis (= 0.36.1). However, 0.36.1 is only in experimental so far. Once wheezy is out, I'll upload it to unstable, and then syslog-ng can be recompiled against it, and this bug can then be closed for good. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690067: #690067: This problem is still present in 3.3.9-1
Control: found -1 3.3.9-1 This problem was fixed in Wheezy, but the same fixes should be applied to 3.3.9-1 aswell in order to fix it in unstable too. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763725: git-flow: Bad variable name when space characters in path
Peter van der Does pe...@avirtualhome.com writes: On Thu, 02 Oct 2014 09:30:33 +0200 Jeremie Burtin jere...@jeremieburtin.fr wrote: Package: git-flow Version: 1.7.0-1 Severity: grave Tags: upstream Justification: renders package unusable Hi, When trying to perform git flow feature start feature_name, the script fails with a Bad variable name error. It seems to come from the fact the path to the directory where I'm working contains space characters (ie : 2 - Developpement) The same repository in another path with no space does not fail. This was a bug in version 1.7, it's fixed in version 1.8. P.S. I develop git-flow AVH Edition, but do not maintain the Debian package. Thanks for the report, and the heads-up on the fix being available in 1.8! I'll update the Debian package today. -- |8] pgpPsIIvLv10t.pgp Description: PGP signature
Bug#736656: libdbi-drivers: drivers not found anymore, due to multi-arch
Source: libdbi-drivers Version: 0.9.0-1 Severity: grave Justification: renders package unusable libdbi1 0.9.0-1 is built with a multi-arch, and will search for drivers in a multi-arch directory, but the binaries produced from libdbi-drivers still produce packages that use the old, non-multiarch directory. This renders any software using libdbi unusable, as they will not be able to find drivers. (Originally reported by Matt Zagrabelny mzagr...@d.umn.edu on the syslog-ng mailing list) -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739604: sysvinit: The new skeleton does not work on kFreeBSD
Source: sysvinit Version: 2.88dsf-50 Severity: serious The change introduced in sysvinit 2.88dsf-50, which turns /etc/init.d/skeleton into a script that has /lib/init/init-d-script as interpreter fails on kFreeBSD, because on that platform, interpreters cannot be other scripts. To demonstrate: ,[ test.sh ] | #!/lib/init/init-d-script | DAEMON=/bin/uname ` On linux, running ./test.sh prints the usage. On kFreeBSD (as tested locally and on falla.d.o), it prints nothing, because the #! line will be ignored, it being a script and all. If you want to do this kind of thing, you will either need a binary wrapper at least on kFreeBSD, or you'll need to use sourcing. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739604: sysvinit: The new skeleton does not work on kFreeBSD
Petter Reinholdtsen p...@hungry.com writes: [Gergely Nagy] The change introduced in sysvinit 2.88dsf-50, which turns /etc/init.d/skeleton into a script that has /lib/init/init-d-script as interpreter fails on kFreeBSD, because on that platform, interpreters cannot be other scripts. Oh. I tested on Linux and Hurd, and did not imagine that kFreeBSD was that different from these two. :) It's Linux (since 2.6), Hurd and Minix being different from anything else :) If you want to do this kind of thing, you will either need a binary wrapper at least on kFreeBSD, or you'll need to use sourcing. Right. Back to the drawing board. :) Can you test this construct instead of #!/lib/init/init-d-script: #!/bin/sh if [ true != $INIT_D_SCRIPT_SOURCED ] ; then set $0 $@; INIT_D_SCRIPT_SOURCED=true . /lib/init/init-d-script fi I can try it tomorrow or so. If you want, you can try it on the kfreebsd porter boxes, it's easily reproducible there. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757903: syslog-ng-core: invoke-rc.d: initscript syslog-ng, action stop failed.
Sebastian Ramacher sramac...@debian.org writes: Package: syslog-ng-core Version: 3.5.6-1 Severity: grave Justification: renders package unusable Today the upgrade from 3.5.5-2 to 3.5.6-1 failed with: | Processing triggers for syslog-ng-core (3.5.6-1) ... | Job for syslog-ng.service canceled. | invoke-rc.d: initscript syslog-ng, action stop failed. | dpkg: error processing package syslog-ng-core (--configure): | subprocess installed post-installation script returned error exit status 1 Uncommenting invoke-rc.d syslog-ng stop || exit $? in line 6 of the postinst script and running apt install -f fixes the issue and lets the installation complete. I've also seen this issue while installing syslog-ng-core for the first time on another system. Both systems are running systemd if that matters. Let me know if you want more info. My other system waits to be upgraded. What does systemctl status syslog-ng.service print? -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757903: [Syslog-ng-maintainers] Bug#757903: syslog-ng-core: invoke-rc.d: initscript syslog-ng, action stop failed.
% systemctl status syslog-ng.service; dpkg-reconfigure syslog-ng-core syslog-ng.service - System Logger Daemon Loaded: loaded (/lib/systemd/system/syslog-ng.service; enabled) Active: active (running) since Tue 2014-08-12 20:42:04 CEST; 1s ago Docs: man:syslog-ng(8) Main PID: 24163 (syslog-ng) CGroup: /system.slice/syslog-ng.service └─24163 /usr/sbin/syslog-ng -F Aug 12 20:42:04 mercury2 systemd[1]: Started System Logger Daemon. Aug 12 20:42:04 mercury2 systemd[1]: Started System Logger Daemon. + [ configure = triggered ] + dpkg-trigger register-syslog-ng-plugin + deb-systemd-helper unmask syslog-ng.service + deb-systemd-helper --quiet was-enabled syslog-ng.service + deb-systemd-helper enable syslog-ng.service + [ -x /etc/init.d/syslog-ng ] + update-rc.d syslog-ng defaults 10 90 + exit 0 Processing triggers for syslog-ng-core (3.5.6-1) ... + [ triggered = triggered ] + invoke-rc.d syslog-ng stop Job for syslog-ng.service canceled. invoke-rc.d: initscript syslog-ng, action stop failed. + exit 1 dpkg: error processing package syslog-ng-core (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: syslog-ng-core I was suspecting a systemd rate limit at first, but the upgrade that failed today didn't include any other packages shipping anything systemd related. See the attached history.log for the packages involved in the failing upgrade. Turns out this is a known issue with systemd and socket activated services (such as syslog-ng), see #736258 and #751744. However, we do not use the recommended --restart-after-upgrade mechanism, and I'm unsure whether that would fix the issue. Nevertheless, I have a far better idea of what is happening, and will try to reproduce the issue locally. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757903: [Syslog-ng-maintainers] Bug#757903: Bug#757903: syslog-ng-core: invoke-rc.d: initscript syslog-ng, action stop failed.
Control: reassign 757903 dh-systemd Control: forcemerge 751741 757903 Control: affects + 751741 syslog-ng-core Gergely Nagy alger...@balabit.hu writes: Turns out this is a known issue with systemd and socket activated services (such as syslog-ng), see #736258 and #751744. However, we do not use the recommended --restart-after-upgrade mechanism, and I'm unsure whether that would fix the issue. I'm changing syslog-ng-core to use --restart-after-upgrade, but that will likely not solve the problem completely (although I have not been able to reproduce it locally), so I'm reassigning the bug to dh-systemd, and merging it with other similar issues. 3.5.6-2 will likely hit unstable by tonight, I would be very interested in hearing whether the problem persists with that version. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#802034: This is a dh-exec issue
Control: reassign -1 dh-exec The problem here is that with the DH_CONFIG_ACT_ON_PACKAGES change, dh-exec lost the ability to work with plain debian/install or debian/manpages files. I'll restore that functionality in the next dh-exec upload. -- |8]
Bug#889006: dh-autoreconf is run before patching
Sorry for the brevity, I'm a tad short on time right now: yeah, I'm ok with a 0-day NMU of dpatch, that tweaks the sequence, and includes the patch for #868978 as well. Thanks! -- |8]
