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]
Package: gpointing-device-settings
Version: 1.6.0~git20150314.de7fe9e7-1
Severity: grave
No matter which settings I change, whether I run the software as my own
user or via sudo, whenever I try to apply changes, it crashes with the
attached backtrace printed on the terminal I launched it from. Thi
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]
Peter van der Does writes:
> On Thu, 02 Oct 2014 09:30:33 +0200 Jeremie Burtin
> 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
Control: reassign 757903 dh-systemd
Control: forcemerge 751741 757903
Control: affects + 751741 syslog-ng-core
Gergely Nagy 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
> no
> % 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:
Sebastian Ramacher 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.
> | invok
Petter Reinholdtsen 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 b
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:
,
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
di
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
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.
The problem here is that lib/mainloop.c does not #include ,
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-
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 rec
"Laszlo Boszormenyi (GCS)" 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.
Control: tag -1 patch
Gergely Nagy 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:
>&g
Gergely Nagy 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 ne
Martin Zobel-Helas 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
Control: reassign -1 src:maven
Moritz Muehlenhoff 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 securit
Alexey Eromenko 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 mi
Control: reassign -1 general
Alexey Eromenko 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-B
Control: severity -1 normal
>> From: Ivo De Decker
>> 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
Csillag Tamas 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 eith
Enrico Zini 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 t
found 690992 libmongo-client-dev 0.1.5-1
thanks
On Fri, Oct 19, 2012 at 10:58 PM, Michael Biebl 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 UN
> > 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 o
Gergely Nagy 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
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 trou
Pantelis Koukousoulas 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
ssing json_object_iterator.h header in
+libjson0-dev. (Closes: #685714)
+
+ -- Gergely Nagy 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.in
reassign 684479 general
thanks
Hughe Chung 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
reassign 684175 python-poker-network 1.7.7-3.2
thanks
Andreas Beckmann 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 debia
Ben Hutchings 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
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
reassign 681115 pdns-server 3.1-4
thanks
Werner Detter 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 agai
> 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
satisfy
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 k
Ondřej Surý 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 b
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 pl
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 onl
le 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
Signed-off-by: Gergely Nagy
Closes: #665905
diff --git a/debian/syslog-ng-cor
Andreas Beckmann 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',
> a
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 Informati
"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
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
reassign 658220 kipi-plugins 1.9.0-3
thanks
Michael Rasmussen 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 "un
reassign 651948 dpatch
found 651948 2.0.32
severity 651948 serious
affects 651948 pinfo
thanks
Steve McIntyre 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
> 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
Andrey Paramonov 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 yo
reassign 646699 debian-installer
thanks
Maarten 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
> err
Jakub Wilk writes:
> Disclaimer: I'm not maintainer of this package.
>
> * nick black , 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 .../
found 643001 0.37-1
thanks
On Mon, Sep 26, 2011 at 14:16, Julien Cristau 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
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 rebui
reassign 641734 src:gdal
thanks
Alastair McKinstry 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,
Jérémie Koenig writes:
> On Wed, Sep 7, 2011 at 11:07 AM, Philipp Kern 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 groun
Dirk Blau writes:
> Gergely Nagy :
>
>> 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 advis
Dirk Blau 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
packa
"Peter T. Breuer" 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
Richard Hartmann writes:
> Package: zsh
> Version: 4.3.11-5
> Severity: grave
> Justification: renders package unusable
>
> Rationale: zsh-static is a shell used for root and in fall-back
> scenarios. As it does not work at all, this can make system maintenance
> or repairing this hard to impossi
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
c
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=
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 L
> 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 "unsub
63 matches
Mail list logo
