user debian-rele...@lists.debian.org
usertag 1100286 + bsp-2025-03-ca-montreal
tags 1100286 + confirmed upstream
thank you
Hello,
I'm able to reproduce this test failure. I also tried directly on the
upstream project and the same failure is happening there, too on the
latest commin on the `mai
user debian-rele...@lists.debian.org
usertag 1099272 + bsp-2025-03-ca-montreal
tags 1099272 + fixed-upstream
thank you
Hello,
Upstream has apparently already fixed this issue:
https://github.com/bimmerconnected/bimmer_connected/pull/693
This fix was also released in a new upstream version.
So
user debian-rele...@lists.debian.org
usertag 1091947 + bsp-2025-03-ca-montreal
tags 1091947 + patch
thank you
Hello,
The error that's happening in the build log has been handled by upstream
by disabling the failing test.
So we could fix this by bumping the library version to version 0.5.7
wh
user debian-rele...@lists.debian.org
usertag 1100306 + bsp-2025-03-ca-montreal
usertag 1100307 + bsp-2025-03-ca-montreal
usertag 1100310 + bsp-2025-03-ca-montreal
usertag 1100313 + bsp-2025-03-ca-montreal
usertag 1100314 + bsp-2025-03-ca-montreal
usertag 1100315 + bsp-2025-03-ca-montreal
tags 1100
For what it's worth I found this which seems to point towards our bug
being 'thin' not yet supporting rack 3:
https://github.com/macournoyer/thin/issues/389
maybe we should reassign this to thin? (I'm not doing it now since I'm
not yet 100% confident on my analysis)
Hello,
I'm able to reproduce this bug on testing by just installing the
schleuder package.
Once that's done we can see that schleuder-api-daemon.service is
erroring out on startup
I'm not very confident about my skills for analysing ruby errors.. but
it looks like the problem might be stem
Hello,
The upstream bug report was closed with a new release 1.10 Apparently
there was already a fix committed upstream and now it's part of a new
release.
Could we bump the version (again) to 1.10.0 in the hope that this error
gets fixed?
Thanks!
close 1064686
thanks
The build issue was fixed with the tag 0.9.2-3 but the changelog did not
mark this issues as being closed by the correction.
Closing the issue now
Hello!
Just wanted to chime in to confirm that James' patch does make the
package compile.
Hi there,
This could be happening for many reasons. Just to investigate one
possiblity: in your syslog do you see messages from apparmor when you
try to load a file?
Hi,
I've just taken a look at this issue together with someone else during
the Montreal BSP and we think that the init script is possibly the
source of the problem:
the stop action fails if it is called when the service is not running,
which is the case when you install the package on a new
Hi there,
For what it's worth, upstream puppet does not yet suppport ruby 3.0.
see: https://puppet.com/docs/puppet/7/release_notes_puppet.html
puppet 7 added support for ruby 2.7 but 2.9 and 3.0 were never there
upstream. I'm guessing they'll bump to 3.x for the puppet 8 cycle only.
Package: undertime
Version: 2.6.0
Severity: grave
Justification: renders package unusable
Hello,
I'm currently getting stack traces consistently when using undertime. No matter
the timezone that I request, I get a stack trace with a TypeError exception:
$ undertime pt
Traceback (most recent call
Hi,
>> A quick workaround to get facter to run is to create the three
>> directories:
>
>> /etc/facter/facts.d
>> /etc/puppetlabs/facter/facts.d
>> /opt/puppetlabs/facter/facts.d
>
> Yup, confirmed that works. Thank you!
thanks for the workaround.
while it seems to work when running facter as
Hello,
On Wed, 21 Aug 2019 10:16:26 -0400 Antoine Beaupre
wrote:
> Vagrant, using the libvirt backend, started failing me recently, with
> something like this:
>
> anarcat@curie:stretch64(master)$ vagrant up --provider libvirt
> Bringing machine 'default' up with 'libvirt' provider...
> ==> defa
Package: puppetdb
Version: 6.2.0-3
Severity: grave
Justification: renders package unusable
Hi there!
I've hit a bug with a new installation of puppetdb on buster (e.g. I've
re-created my puppetmaster vagrant box) where puppetdb would fail to start,
erroring out on an SQL upgrade of the database s
Hi,
Since the bug report was indicating that the issue was fixed in
3.4.2-1+deb8u4, I've tried to apply upgrades and it seems to have
upgraded successfully. So the fix seems to work for me!
signature.asc
Description: OpenPGP digital signature
Hi again!
On Tue, 7 May 2019 02:24:59 -0400 Gabriel Filion wrote:
> On Mon, 29 Apr 2019 15:44:39 +0200 Santiago Vila wrote:
> > On Mon, Apr 29, 2019 at 01:22:18PM +, Holger Levsen wrote:
> > > if we now could please focus on #928172 and ignore #927450 for now,
> &g
On Mon, 29 Apr 2019 15:44:39 +0200 Santiago Vila wrote:
> On Mon, Apr 29, 2019 at 01:22:18PM +, Holger Levsen wrote:
> > if we now could please focus on #928172 and ignore #927450 for now,
> > that would be great. (and "ignoring #927450" also means not mixing them
> > up.)
>
> Let's focus on
Package: cryptsetup
Version: 2:2.1.0-2
Severity: grave
Justification: renders package unusable
Hello,
I've rebooted my computer this morning and the password prompt to unlock the
crypto device would not appear before grub would search for the lvm device
inside.
This means that the system was not
On 2019-03-26 2:43 p.m., Gabriel Filion wrote:
> Did you recently upgrade smokeping? if so what version were you using
> before? (maybe check your dpkg logs for signs of upgrade of the
> smokeping package)
I just thought of something else: if you were using the 2.7.3-1 package
previou
Hi Bertrand,
On 2019-03-25 2:57 a.m., BERTRAND Joël wrote:
> I have restarted a server last sunday and I have seen that smokeping doesn't
> start anymore.
>
> In systemd config file, smokeping is launched with --pid-dir=/run/smokeping
> and
> systemd complains about non existent pid file.
>
> I
On 2019-02-15 10:33 p.m., Gabriel Filion wrote:
> On 2019-02-15 7:53 a.m., Axel Beckert wrote:
>> sorry for the late report, but smokeping failed to configure (probably
>> after the recent upgrade) for a few days for me now:
>>
>> # dpkg --configure -a
>&
Hello,
On 2019-02-15 7:53 a.m., Axel Beckert wrote:
> sorry for the late report, but smokeping failed to configure (probably
> after the recent upgrade) for a few days for me now:
>
> # dpkg --configure -a
> Setting up smokeping (2.7.3-1) ...
> apache2_invoke: Enable module cgi
> [ ok ] Restartin
Hi there,
I just wanted to word in here that I hit exactly this bug where nothing
was working anymore (read: no firewall rules at all anymore), and after
being pointed to this ticket by folks in #debian-next I've upgraded to
1.8.1-2 and now I have a firewall again.
thanks!
signature.asc
Descri
Package: apparmor-profiles
Version: 2.11.1-3
Severity: critical
Justification: breaks unrelated software
Hello,
I've started using apparmor very recently, and when I rebooted to
activate the kernel part, I didn't notice the issue below.. but a couple
reboots afterwards I couldn't obtain a DHCP ad
Source: kedpm
Version: 1.0
Severity: grave
Tags: upstream security
Justification: user security hole
Hello,
I've discovered an information leak that can give some hints about what ppl
search and read in the password manager.
kedpm is creating a history file in ~/.kedpm/history that is written in
Hi there,
I've traced inter-package links (depends, conflicts et al) and I think I
found the reason why the server gets removed.
stretch still has a mysql-common package that has a "Replaces:" for
mysql-server-5.5.
during a dist-upgrade mysql-common will get upgraded to the stretch
version, whic
Otto Kekäläinen:
>>> One way to make this an easier transition would be to have a
>>> mysql-server package in stretch that's a dummy package that depends
>>> on
>>> default-mysql-server, and that has an upgrade notice about the
>>> transition to mariadb that is happening.
>
> The transition is sup
Lars Tangvald:
>
> - gabs...@lelutin.ca wrote:
>
>> Ugh, I fail at reportbug again :(
>>
>> real sorry about the initial report.
>>
>> here's the real description of the problem:
>>
>>
>> when upgrading from jessie to stretch, the upgrade goes through
>> without
>> an error but the end result
Ugh, I fail at reportbug again :(
real sorry about the initial report.
here's the real description of the problem:
when upgrading from jessie to stretch, the upgrade goes through without
an error but the end result is that mysql-server-5.5 gets removed and
mysql is not running anymore.
stretch
Package: mysql-server-5.5
Version: 5.5.54-0+deb8u1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effectiv
Gabriel Filion:
> I've just exerienced the same during an upgrade of sid packages.
>
> The only way to break out of this mess is to force the upgrade of the
> package with:
>
> dpkg --force-overwrite -i
> /var/cache/apt/archives/libxtables12_1.6.0+snapshot2016111
Hello,
I've just exerienced the same during an upgrade of sid packages.
The only way to break out of this mess is to force the upgrade of the
package with:
dpkg --force-overwrite -i
/var/cache/apt/archives/libxtables12_1.6.0+snapshot20161117-2_amd64.deb
then it becomes possible to continue with
Hello,
I've worked a little bit on this in the same setup as Anarcat used, here
at koumbit.
I've figured out why the users were not listed in gdm3. It was a line in
/etc/pam.d/common-session that was missing:
session optionalpam_systemd.so
with this line users are listed.
This problem
Package: parcimonie
Version: 0.10.2-1
Severity: grave
Justification: renders package unusable
Hi there,
Ever since gnupg 2.1 was set to be the main "gpg" command in sid, parcimonie
has been unable to do its bidding.
>From the process list, we can see the following:
gabster 6219 0.1 1.2 129
On 16/10/15 03:45 PM, Simon McVittie wrote:
> Control: tags 801425 + unreproducible
> Control: block 801425 by 801354
>
> On 16/10/15 20:03, Gabriel Filion wrote:
>> fwiw, dbus was upgraded again to 1.10.0-3 and later I downgraded
>> policykit-1 to 0.105-12, the version
Hi there,
On 10/10/15 06:59 PM, Simon McVittie wrote:
> On 10/10/15 17:38, Gabriel Filion wrote:
> It would be really useful to see any systemd, policykit-1 (polkit)
> and/or dbus warnings/errors from 2015-10-09, from your syslog. If you
> would prefer not to send that day's sys
Package: dbus
Version: 1.10.0-3
Severity: grave
Justification: renders package unusable
Hi,
I'm running sid and this morning I performed an apt-get upgrade and a
dist-upgrade. This pulled in dbus 1.10.0-3.
Upon restart, systemd was hanging for a bunch of time with messages like the
following:
E
in wheezy.
--
Gabriel Filion
signature.asc
Description: OpenPGP digital signature
ere this
happened, I could see this in the logs:
[2601471.852025] TCP: Peer 74.94.211.209:31059/80 unexpectedly shrunk
window 4233113998:4233124218 (repaired)
[2601479.916025] TCP: Peer 74.94.211.209:31059/80 unexpectedly shrunk
window 4233113998:4233124218 (repaired)
--
Gabriel Filion
signa
On 2012-09-30 00:46, Jaldhar H. Vyas wrote:
> On Sun, 30 Sep 2012, Gabriel Filion wrote:
>
>> This bug concerns a somewhat old version (current version in both
>> squeeze-backports and wheezy is 1:2.1.7-2).
>>
>> Also, the package dovecot-managesieved doesn't ex
t apply to the current
dovecot-managesieved.postrm file, so I marked it as unreproducible.
--
Gabriel Filion
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
't segfault and doesn't eat the cpu.
--
Gabriel Filion
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
45 matches
Mail list logo
