On Tue, Apr 30, 2024 at 07:45:41AM +0200, Evgeni Golov wrote:
> On Mon, Apr 29, 2024 at 08:35:28PM +0200, Evgeni Golov wrote:
> > UNKNOWN Exception: [Errno 2] No such file or directory:
> >
> > This is because the process might have already ended between calling
> &g
On Mon, Apr 29, 2024 at 08:35:28PM +0200, Evgeni Golov wrote:
> UNKNOWN Exception: [Errno 2] No such file or directory:
>
> This is because the process might have already ended between calling
> os.listdir() and os.stat().
Turns out, os.path.realpath() also can raise FileNotFoundErr
Package: monitoring-plugins-contrib
Version: 42.20230308+deb12u1+b1
Tags: patch
Ohai,
on systems with many short-lived processes (like a monitoring server,
spawning many check_* commands), I regularly see check_libs_ng return
UNKNOWN Exception: [Errno 2] No such file or directory:
This is
Package: prometheus-node-exporter-collectors
Version: 0.0~git20230203.6f710f8-1
Ohai,
I know it's custom in Debian to auto-enable services when they are
installed, however I think that the broad variety of timers present in
the collectors package deserves a different treatment, as people usually
FWIW, this still happens with bookworm boxes.
I've tried 12.20240212.1 and 12.20231211.1
Evgeni
Package: python3-ansible-runner
Version: 2.3.4-1
Hi,
ansible is currently not in testing [1] and thus ansible-runner was also
removed [2]. However, ansible-runner only needs the binaries for
Ansible, and those are in the ansible-core package.
By switching the dependency to ansible-core
Hi,
On Mon, Dec 18, 2023 at 08:33:40AM +, Reto wrote:
> Package: tuned
> Version: 2.20.0-1
> Severity: normal
> X-Debbugs-Cc: r...@retoonline.com
>
> Dear Maintainer,
>
> I think the config 'STORAGE_PERSISTENT' in the file 'functions' should be
> updated from
> '/var/lib/tuned' to
\o
On Tue, Nov 21, 2023 at 10:35:22AM -0500, Antoine Beaupre wrote:
> Right now, our puppet-agent debian package merely "Suggests"
> those. (The puppetserver package, surprisingly, "Recommends" them,
> even though it Depends: puppet-agent. My feeling is that it should
> delegate that decision to
forcemerge 1038207 1040898
thanks
On Wed, Jul 12, 2023 at 08:46:22AM +0200, Jan Volec wrote:
> Package: tp-smapi-dkms
> Version: 0.43-3
> Severity: critical
> Justification: breaks unrelated software
no it does not :)
> DKMS fails to compile the module with the 6.4 kernels; see
>
On Wed, Jul 12, 2023 at 09:06:36AM +0200, Caren Hern wrote:
> Hi Evgeni,
>
> yes I have suspend active. Hibernate was never working.
Okay, I can at least double-check that against the machines I have here!
> I am also confused now, because I just reinstalled the package (no errors)
> but indead
Hi,
On Tue, Jul 11, 2023 at 02:24:38PM +0200, Caren Hern wrote:
> After upgrading to from bulleye to bookworm (Kernel version 6.1.0-9) I
> experienced frequent freezes after wake.
> The power LED would light up, and I was able to toggle the keyboard
> backlight, but no other buttons responded
Hi!
On Fri, Jun 16, 2023 at 04:13:51PM +0200, Andreas Beckmann wrote:
> DKMS make.log for tp_smapi-0.43 for kernel 6.4.0-0-amd64 (x86_64)
> Fri Jun 16 14:10:47 UTC 2023
> make: Entering directory '/usr/src/linux-headers-6.4.0-0-amd64'
> CC [M] /var/lib/dkms/tp_smapi/0.43/build/thinkpad_ec.o
>
On April 9, 2023 12:51:33 PM UTC, Santiago Vila wrote:
>Hello. This is an interesting bug indeed, because it forces us to re-read
>the specification and maybe suggest changes if we see that it's incomplete
>or just suboptimal.
>
Package: hello
Version: 2.10-3
Ohai,
while looking for a simple package to test something with autopkgtest, I
noticed that hello's debian/tests/upstream-tests will try to execute
*all* files from the tests/ directory (skipping greeting-2).
This works correctly when the tests are executed from a
On Wed, Oct 05, 2022 at 08:31:58AM +0200, Evgeni Golov wrote:
> As a workaround, manually adding a section to the XML, or making
> libvirt call QEMU otherwise with `-device cirrus-us,id=video0` works,
> but is clearly not how it was intended to be.
This obviously should read `-device c
Package: cloud.debian.org
X-Debbugs-CC: evg...@redhat.com, ew...@redhat.com
Ohai,
we're using the debian/bullseye64 vagrant box for some automated
testing, and to allow multiple tests to run in parallel, we configure
vagrant-libvirt with `graphics_type: none` (otherwise QEMU/Libvirt
sometimes
Hey,
On Thu, Mar 10, 2022 at 06:59:37AM +, Schmidt, Adriaan wrote:
> Evgeni Golov, 18. Februar 2022 12:49:
> > On Fri, Feb 18, 2022 at 12:34:49PM +0100, Evgeni Golov wrote:
> > > Hi Adriaan,
> > >
> > > I was looking at this for the next tuned up
On Fri, Feb 18, 2022 at 12:34:49PM +0100, Evgeni Golov wrote:
> Hi Adriaan,
>
> I was looking at this for the next tuned upload, and have a few
> questions.
>
> On Thu, May 20, 2021 at 01:27:01PM +, Schmidt, Adriaan wrote:
> > Paths related to grub (required
Hi Adriaan,
I was looking at this for the next tuned upload, and have a few
questions.
On Thu, May 20, 2021 at 01:27:01PM +, Schmidt, Adriaan wrote:
> Paths related to grub (required by the bootloader plugin):
>
> diff --git a/tuned/consts.py b/tuned/consts.py
> index 733ad51..f0acf9e
Ohai,
On Wed, Feb 02, 2022 at 06:23:44PM +0100, Michael Prokop wrote:
> Package: tuned
> Version: 2.15.0-1
> Severity: wishlist
>
> Hi,
>
> v2.17.0 is available since 2022-01-16, see:
>
> https://github.com/redhat-performance/tuned/releases
and 2.18.0 since yesterday :)
I've started
On December 25, 2021 12:35:45 PM UTC, Antonio Terceiro
wrote:
>On Fri, Dec 24, 2021 at 06:04:04AM +, Mathias Gibbens wrote:
>> Source: lxc
>> Version: 1:4.0.10-1
>> Severity: normal
>>
>> Work on packaging LXD for Debian (ITP #768073) is getting pretty
>> close to completion. I've
Package: python3-debian
Version: 0.1.42
Ohai,
filing this in Debian, as I am not aware of any other bugtracker for
python-debian, even tho the issue doesn't *really* affect Debian
unstable (as it doesn't have Python 3.5/3.6).
In python-debian 0.1.42, the following commit was made:
On Sun, Apr 25, 2021 at 03:41:38PM +0300, Heikki Hannikainen wrote:
> On Sun, 25 Apr 2021, Evgeni Golov wrote:
>
> > On Thu, Apr 22, 2021 at 12:19:57AM +0300, Heikki Hannikainen wrote:
> >
> > > - Remove N0CALL-1 from the default configuration (comment the line out) s
Hi,
On Thu, Apr 22, 2021 at 12:19:57AM +0300, Heikki Hannikainen wrote:
> - Have it not start up by default after installation, before it is configured
This should be doable by the following patch:
diff -Nru aprx-2.9.0+dfsg/debian/rules aprx-2.9.0+dfsg/debian/rules
---
On Sat, Apr 24, 2021 at 07:46:32PM +0200, Evgeni Golov wrote:
> Moin,
>
> On Sat, Apr 17, 2021 at 10:20:45PM +0200, Paul Gevers wrote:
> > Librarian::Mock::Cli
> > version
> > autopkgtest [04:30:22]: ERROR: timed out on command "su -s /bin/bash
>
> pok
Moin,
On Sat, Apr 17, 2021 at 10:20:45PM +0200, Paul Gevers wrote:
> Librarian::Mock::Cli
> version
> autopkgtest [04:30:22]: ERROR: timed out on command "su -s /bin/bash
poking around this…
the tests pass fine as long the deb is not installed (so it's only
running from the source checkout),
control: found -1 linux/5.10.28-1
Ohai,
On Mon, May 11, 2020 at 10:22:23PM +0200, Uwe Kleine-König wrote:
> > Verified: my 5.7.0-rc1 system with intel_iommu=on can suspend/resume
> > without issues.
>
> I brought this problem to the attention of the x86 guys; see above URL
> for the
On March 4, 2021 3:50:21 PM UTC, gregor herrmann wrote:
>On Tue, 02 Mar 2021 22:44:24 +, Thorsten Glaser wrote:
>
>> and the new one doesn’t work, and I don’t even
>> know what I’m supposed to put where. Perhaps upstream has some kind
>> of list what model needs which settings? Also, YAML
On March 2, 2021 9:01:28 PM UTC, Thorsten Glaser wrote:
>Evgeni Golov dixit:
>
>>>… without that it’ll also fail, which means it’ll fail package
>>>installation, which is a serious (RC) bug.
>>
>>No, the daemon is not started on install
>
>Did tha
On March 2, 2021 8:26:12 PM UTC, Thorsten Glaser wrote:
>Evgeni Golov dixit:
>
>>> No, this is about the *vanilla* config shipped by the package.
>>> It used to work (my adjustment later was only regarding the levels
>>> of temperature as I’ve got an SSD
On Tue, Mar 02, 2021 at 07:28:11PM +, Thorsten Glaser wrote:
> Evgeni Golov dixit:
>
> >> tglase@tglase-nb:~ $ sudo cleanenv / /etc/init.d/thinkfan start
> >> Starting fan control tool: thinkfan
> >> ERROR: Error scanning
> >> /sys/devices/
Hey,
On Tue, Mar 02, 2021 at 04:13:01PM +0100, Thorsten Glaser wrote:
> Unfortunately, thinkfan still fails to work:
>
> tglase@tglase-nb:~ $ sudo cleanenv / /etc/init.d/thinkfan stop
> Stopping fan control tool: thinkfan.
> tglase@tglase-nb:~ $ sudo cleanenv / /etc/init.d/thinkfan start
>
Hey again,
On Mon, Mar 01, 2021 at 07:30:14PM +, Evgeni Golov wrote:
> >By installing /etc/thinkfan.yaml on systems with a working configuration
> >in /etc/thinkfan.conf, the daemon simply fails to start (while simply
> >removing the new /etc/thinkfan.yaml allow one
found 983727 1.2.1-1
thanks
Hey David!
Thanks for the report.
On February 28, 2021 9:29:54 PM UTC, "David Prévot" wrote:
>Package: thinkfan
>Version: 1.2.1-3
>Severity: serious
>
>The “thinkfan Example Config File” currently shipped as
>/etc/thinkfan.yaml “is NOT a working config file that can
On February 27, 2021 8:44:44 PM UTC, Lucas Nussbaum wrote:
>On 27/02/21 at 15:16 +0100, Evgeni Golov wrote:
>> On Fri, Feb 26, 2021 at 10:54:32PM +0100, Lucas Nussbaum wrote:
>> > Tentative patch:
>> > https://salsa.debian.org/cloud-team/deb
On Fri, Feb 26, 2021 at 10:54:32PM +0100, Lucas Nussbaum wrote:
> On 26/02/21 at 20:07 +0100, Lucas Nussbaum wrote:
> > On 14/02/21 at 08:48 +0100, Evgeni Golov wrote:
> > > On Sat, Feb 13, 2021 at 11:57:52PM +0100, Thomas Lange wrote:
> > > > IMO we cannot
On Sat, Feb 13, 2021 at 11:57:52PM +0100, Thomas Lange wrote:
> IMO we cannot know which device name is used by the users virtualisation
> environment.
> So, what is the be setting without knowing the device name?
>
> Or is /dev/sda used in most enviroments?
For VirtualBox sda is a pretty safe
On Sat, Feb 13, 2021 at 09:22:58PM +0100, Evgeni Golov wrote:
> I have `hostonly` set, and it passes $(<"$i") to dracut_instmods, which is
> empty in
> the dock.X case.
https://github.com/dracutdevs/dracut/pull/1096
This should fix it.
Hey Thomas,
On Fri, Feb 12, 2021 at 10:40:06PM +0100, Thomas Lange wrote:
> I cannot confirm this problem.
> It works without problems on a bullseye VM.
>
> Maybe you can strace the dracut call and see which parameters are
> given to the dracut-install call.
attached is the output of `dracut
On Fri, Feb 12, 2021 at 06:55:35PM +0100, Emmanuel Kasper wrote:
> Le 12/02/2021 à 12:36, Evgeni Golov a écrit :
> > On Fri, Feb 12, 2021 at 10:03:08AM +0100, Thomas Lange wrote:
> >> This behaviour was also reported as #982182
> >
> > Interesting, thanks!
> &
On Fri, Feb 12, 2021 at 10:03:08AM +0100, Thomas Lange wrote:
> This behaviour was also reported as #982182
Interesting, thanks!
To me the GRUB change seems reasonable, even if a tad unexpected in a
point release.
You change to FAI [1] looks pretty much how I would envision a correct
fix in the
Package: cloud.debian.org
Ohai,
debian/buster64 [1] is still at 10.4, while there was 10.8 released last
weekend. Could you please update the box to the latest point release, so
that users don't have to do that manually after fetching it?
Thanks!
[1]
Package: cloud.debian.org
Ohai,
when trying to update a VM based on the debian/buster64 box from 10.4 to
10.8, grub-pc can't be upgraded non-interactively because it doesn't
know which devices to install GRUB to (grub-pc/install_devices debconf
question is empty) and that's a fatal error for
Package: ftp.debian.org
Severity: normal
Ohai,
please remove gtkperf from unstable. It's dead upstream and uses the old
and obsolete GTK 2. popcon is rather low too.
Thanks!
Evgeni
Package: ftp.debian.org
Severity: normal
Ohai!
please remove ansible-tower-cli from unstable, it's been dead upstream
for a while and has low popcon.
Thanks
Evgeni
On Sat, Feb 06, 2021 at 09:24:44PM +0100, Evgeni Golov wrote:
> when trying to build an initrd, I get the following output:
>
> root@nana:~# dracut -q /tmp/sdfsdf 5.10.0-2-amd64
> dracut-install: No SOURCE argument given
And if Evgeni would not add -q to the call, he would have
Package: dracut
Version: 051-1
Severity: normal
Ohai,
when trying to build an initrd, I get the following output:
root@nana:~# dracut -q /tmp/sdfsdf 5.10.0-2-amd64
dracut-install: No SOURCE argument given
Usage: dracut-install -D DESTROOTDIR [-r SYSROOTDIR] [OPTION]... -a SOURCE...
or:
Hey Adrian,
On Fri, Feb 05, 2021 at 01:32:15PM +0200, Adrian Bunk wrote:
> I've prepared an NMU for hdapsd (versioned as 1:20141203-1.1) and
> uploaded it to DELAYED/1. Please feel free to tell me if I should
> cancel it.
Thanks, but NACK.
I have prepared something similar (with more changes)
fixed 981251 1.2.1-2
thanks
Hi,
On Wed, Feb 03, 2021 at 12:45:11AM +0100, Thorsten Glaser wrote:
> This bug is still pertinent:
>
> thinkfan: obsolete-conffile /etc/thinkfan.conf
No, it's not. According to your dpkg output your config was modified,
and dpkg/debhelper doesn't remove modified
Hi Michael!
Indeed, I was wondering about that file but then left it in thinking "someone
will complain".
And you did ;)
Is there a policy/documentation that I could point upstream at so they also
remove it too?
Evgeni
On January 28, 2021 9:06:22 AM UTC, Michael Biebl wrote:
>Package:
On Fri, Jan 01, 2021 at 11:04:44AM +0100, Evgeni Golov wrote:
> On Mon, Dec 21, 2020 at 09:40:15AM +0100, Martin Pitt wrote:
> > curl -o sid.qcow2
> > https://cloud.debian.org/images/cloud/sid/daily/20201220-490/debian-sid-nocloud-amd64-daily-20201220-490.qcow2
> > qe
On Mon, Dec 21, 2020 at 09:40:15AM +0100, Martin Pitt wrote:
> curl -o sid.qcow2
> https://cloud.debian.org/images/cloud/sid/daily/20201220-490/debian-sid-nocloud-amd64-daily-20201220-490.qcow2
> qemu-system-x86_64 -cpu host -nographic -m 2048 -device virtio-rng-pci
> -drive
On Wed, Dec 30, 2020 at 08:33:09PM +0100, Evgeni Golov wrote:
> > And the tuned line that breaks the whole thing is
> >
> > [sysctl]
> > kernel.sched_wakeup_granularity_ns = 1500
>
> This also happens on seabios 1.13.0-1 from snapshot.d.o.
>
>
On Wed, Dec 30, 2020 at 01:06:45PM +0100, Evgeni Golov wrote:
> > This doesn't happen on the buster cloud images, and a few "apt install"
> > invocations later I could bisect the issue to be the upgrade of seabios
> > from 1.12.0-1 to 1.14.0-2.
> >
> > I al
On Wed, Dec 30, 2020 at 12:49:03PM +0100, Evgeni Golov wrote:
> On Sun, Dec 27, 2020 at 03:46:27PM +0100, Evgeni Golov wrote:
> > 1. qemu will happily continue booting cirros when you stop tuned *after*
> > starting qemu
> > 2. it boots fine if you use the "default"
On Sun, Dec 27, 2020 at 03:46:27PM +0100, Evgeni Golov wrote:
> 1. qemu will happily continue booting cirros when you stop tuned *after*
> starting qemu
> 2. it boots fine if you use the "default" (which is not default anymore,
> but a legacy fallback) or the "balanc
Hi martin,
On Mon, Dec 21, 2020 at 09:40:15AM +0100, Martin Pitt wrote:
> I re-tested this straight from the current official cloud images:
>
> curl -o sid.qcow2
> https://cloud.debian.org/images/cloud/sid/daily/20201220-490/debian-sid-nocloud-amd64-daily-20201220-490.qcow2
>
Yeah, I think I added gustavo to uploaders because of the ITP and our
discussions before the initial upload.
Gustavo, if you want, I can drop you in the 2.15 upload I am preparing?
On December 23, 2020 6:49:40 PM UTC, Nicholas D Steeves
wrote:
>Hi,
>
>gustavo panizzo writes:
>
>> Hello
It includes the "functions" file, which uses declare.
On December 13, 2020 2:59:42 PM UTC, Witold Baryluk
wrote:
>Package: tuned-gtk
>Version: 2.10.0-1
>Followup-For: Bug #930489
>X-Debbugs-Cc: witold.bary...@gmail.com
>
>Renaud, this is a bit strange.
>
>I don't see any bashisms in this
I have uploaded 2.14 today! :)
On December 12, 2020 8:27:06 PM UTC, Witold Baryluk
wrote:
>Package: tuned-gtk
>Followup-For: Bug #900858
>X-Debbugs-Cc: witold.bary...@gmail.com
>
>Hi,
>
>technically the original bug is fixed, but the 2.10 version in Debian
>doesn't work Python 3.8+.
>
>These
Hi,
On Tue, Apr 21, 2020 at 01:20:12PM +1000, lachlan-00 wrote:
> i've set this box up to just be a copy/backup dump and i'm trying to copy the
> files over.
>
> Every time i start the rsync the server disappears in under 30seconds. At
> first i thought it was a kernel panic or something weird
Hi Martin,
On Tue, May 29, 2018 at 10:48:48PM +0200, Martin Pitt wrote:
> Package: tuned
> Version: 2.9.0-1
>
> As soon as you install tuned (which auto-starts tuned.service), booting at
> least some QEMU images does not work any more:
>
> $ wget
On Sat, Dec 05, 2020 at 01:33:49PM +, Evgeni Golov wrote:
> I can also try to do an upload (or we together, I don't mind either way).
>
> I thought the "debian" group on salsa was supposed to mean "collab maint" aka
> "everyone can just upload"?
I can also try to do an upload (or we together, I don't mind either way).
I thought the "debian" group on salsa was supposed to mean "collab maint" aka
"everyone can just upload"?
On December 5, 2020 1:23:13 PM UTC, gustavo panizzo wrote:
>Hello Nicholas
>
>On Fri, Dec 04, 2020 at 11:26:00AM
Hi,
On Sat, Aug 15, 2020 at 07:52:10PM +0200, Lee Garrett wrote:
> Thanks! Looking forward to your mail.
I've imported the old git tree into https://salsa.debian.org/debian/thinkfan
Are you lgarrett-guest on Salsa?
Evgeni
>
> On 15/08/2020 08:10, Evgeni Golov wrote:
> > Hi,
&
Hi,
sorry I somehow forgot to answer this mail. Migrating to Salsa and giving you
access so you can update and upload seems like a good idea, especially as I am
currently not using thinkfan myself. Will do so in the next few days and ping
you!
Thanks
Evgeni
On May 22, 2020 9:45:39 PM UTC,
Hi Bernhard,
thanks for digging into this! I'd argue that the real bug is in the grpc
package, as dropping symbols without a soname bump is bad. But that clearly
doesn't help you now.
CCing the maintainer of grpc, shall we reassign and you do the needed changes?
Evgeni
On April 5, 2020
I think this is fixed by
https://github.com/seebk/GIMP-Lensfun/commit/ca4511c1a4dd8edabe86e4a943861fda07b7e86c
Feel free to 0day NMU, I don't have much time right now.
On January 29, 2020 7:00:30 PM UTC, Paul Gevers wrote:
>Source: gimplensfun
>Version: 0.2.4-1
>Severity: serious
Thanks Sandro, feel free to upload to sid without delay!
On December 22, 2019 8:23:22 PM UTC, Sandro Tosi wrote:
>Control: tags 938053 + patch
>
>
>Dear maintainer,
>
>I've prepared an NMU for python-publicsuffix (versioned as 1.1.0-2.1). The diff
>is attached to this message.
>
>Regards.
>
Hi Moritz,
yeah, that sounds reasonable.
PEB, terceiro, any objections?
Evgeni
On December 19, 2019 7:43:30 PM UTC, "Moritz Mühlenhoff"
wrote:
>On Fri, Aug 30, 2019 at 07:41:57AM +, Matthias Klose wrote:
>> Package: src:python-lxc
>> Version: 0.1-3
>> Severity: normal
>> Tags: sid
Unprivileged containers is the only thing I use in Stretch atm, so call me
biased. But it's also the thing that does not work out of the box (you need a
sysctl, you need to add the user to lxc-net config and you need to adjust the
users lxc.conf for the uid map). As such, I'd say having to set
Hi,
upstream suggests this is probably fixed by
https://github.com/redhat-performance/tuned/commit/c37b6220d4bca5984c7c855317d0af31ebe0ec73
which is part of the 2.10 release I have uploaded earlier today.
Can you please retest this?
Thanks
Evgeni
On 6 June 2018 02:07:27 CEST, Witold Baryluk
Package: pass
Version: 1.7.1-3
Severity: wishlist
Tags: upstream patch
Ohai,
pass git init creates a .gitattributes file, but that is not excluded
from the zsh completion file, resulting in a "stray" password being
shown.
the following patch should fix it :)
--- /tmp/_pass 2018-03-05
Package: lintian
Version: 2.5.75
Severity: normal
Ohai,
I think the check for debian-rules-is-dh_make-template instroduced in
d0fec9183b5977fa8f5e0a779631bb140ee3415d is too broad.
Just because d/rules has '# See debhelper(7) (uncomment to enable)' as
the second line, does not mean the author
Hi Andrea,
On Sun, Jan 28, 2018 at 11:34:03AM +0100, Andrea Villa wrote:
>Just create a simple user unprivileged lxc container after following the
> official Debian documentation https://wiki.debian.org/LXC#
> Unprivileged_container.
Can we for a second pretend, wiki.d.o is not official
Package: selinux-policy-dev
Version: 2:2.20171228-1
Severity: serious
Ohai,
upgrade to latest s-p-dev fails:
Setting up selinux-policy-dev (2:2.20171228-1) ...
Running sepolgen-ifgen...dpkg: error processing package selinux-policy-dev
(--configure):
installed selinux-policy-dev package
control: severity -1 important
On Fri, Dec 22, 2017 at 10:03:17AM +0100, Elimar Riesebieter wrote:
> Package: tp-smapi-dkms
> Version: 0.42-1
> Severity: serious
> Justification: fails to build from source
Nope. 4.15 is not in Debian (not even experimental), so it can't be serious.
> tp-smapi
Hi,
On Wed, Dec 20, 2017 at 05:59:42PM +0100, Clément Hermann wrote:
> On 17/12/2017 21:39, Clément Hermann wrote:
>
> > On 04/12/2017 21:40, Clément Hermann wrote:
> >> So, I did some work on golang-gopkg-flosch-pongo2
> >>
Hi Toni,
On Wed, Nov 15, 2017 at 06:10:45PM +0800, Toni Mueller wrote:
> On Sat, Dec 31, 2016 at 01:07:44PM -0500, Harlan Lieberman-Berg wrote:
> > It's been a while since we made the decision not to pull from upstream's
> > git; Toni, I'd be happy to work with you on seeing if it's doable now.
>
Hi,
On Thu, Nov 02, 2017 at 07:09:10PM +0100, Christian Boltz wrote:
> seeing the AppArmor denials would be helpful to get this fixed ;-)
I think the issue is different.
Looking at the LXC log, we see the following:
lxc-start 20171102130036.516 ERRORlxc_apparmor -
Ohai,
On Wed, Nov 01, 2017 at 12:00:12PM -0200, Antonio Terceiro wrote:
> > lxc-start 20171101123914.655 ERRORlxc_apparmor -
> > lsm/apparmor.c:apparmor_process_label_set:220 - If you really want to start
> > this container, set
> > lxc-start 20171101123914.655 ERROR
Hi,
On Mon, Oct 30, 2017 at 06:23:32PM +0100, Andreas Beckmann wrote:
> See policy 7.6 at
> https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces
This should be
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces
Where can I file a bug
Hi,
On Fri, Oct 20, 2017 at 03:09:34PM +0200, Jean-Michel Vourgère wrote:
> > I guess in your case the systemd binary is installed (but not used as
> > init) and thus the dependency did not trigger?
>
> Exactly. cgroupfs-mount was not installed and installing it fixed my issue.
>
> Maybe the
Source: koji
Version: 1.10.0-1
Severity: wishlist
Ohai,
https://pagure.io/koji/releases lists 1.14.0 as latest koji release,
please update the packaging :)
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'),
Source: koji
Severity: wishlist
please update d/control, d/copyright and d/watch accordignly :)
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign
On Sun, Sep 17, 2017 at 10:40:27AM +0200, Evgeni Golov wrote:
> TL;DR: I can reproduce the "does not create cgroups" behaviour, but I
> don't know why yet.
>
> Either way, you are right, the cgroups are missing in Stretch, and I don't
> yet understand why.
This hap
control: found -1 1:2.0.8-2
Hi,
TL;DR: I can reproduce the "does not create cgroups" behaviour, but I
don't know why yet.
On Thu, Sep 14, 2017 at 10:01:41AM +0200, Yves-Alexis Perez wrote:
> On Thu, 2017-09-14 at 09:23 +0200, Yves-Alexis Perez wrote:
> > Package: lxc
> > Version: 1:2.0.7-2
> >
Hi,
On Thu, Jul 27, 2017 at 01:03:51PM +, Jean-Michel Vourgère wrote:
> I finally had it working by adding
> "cgroup /sys/fs/cgroup cgroup defaults 0 0"
> to my /etc/fstab
>
> A little note in /usr/share/doc or elsewhere would be nice.
This is why liblxc1 has a "Depends:
On Fri, Sep 01, 2017 at 09:01:29AM +0100, Julian Gilbey wrote:
> On Fri, Aug 11, 2017 at 08:20:38AM +0200, Evgeni Golov wrote:
> > isync/mbsync defaults to use TLSv1, which was recently disabled in Debian
> > [1].
> > This results in funny errors when trying to use mbsync n
Package: libluajit-5.1-dev
Version: 2.1.0~beta3+dfsg-2
Severity: serious
Tags: upstream
Hi,
LuaJIT 2.1 introduces symbols from Lua 5.2 [1] and drops a few compat symbols
[2] that are still present in Lua 5.1 [3].
This breaks software that either not expects these 5.2 symbols, or expects the
Package: isync
Version: 1.2.1-2
Severity: important
Tags: upstream
Ohai,
isync/mbsync defaults to use TLSv1, which was recently disabled in Debian [1].
This results in funny errors when trying to use mbsync now:
Socket error: secure connect to mail.die-welt.net (81.7.13.250:143):
Hi,
On Fri, Jul 21, 2017 at 07:02:50AM -0400, Boruch Baum wrote:
> Upon upgrading `mutt' from the stable to testing repositories, mutt
> ceased to function, offering the following error message:
There is no mutt 1.7.2-1 in testing. Did you mean upgrading
jessie→stretch?
>#+BEGIN_SRC conf
>
Hi,
On Fri, Jul 14, 2017 at 08:59:14AM -0600, Kevin Locke wrote:
> On Fri, 2017-07-14 at 09:35 +0200, Evgeni Golov wrote:
> > On Mon, Jul 10, 2017 at 02:25:04PM -0600, Kevin Locke wrote:
> >> On Sat, 2016-11-12 at 10:30 +0100, Evgeni Golov wrote:
> >>> Can you pleas
Hi,
On Mon, Jul 10, 2017 at 02:25:04PM -0600, Kevin Locke wrote:
> On Sat, 2016-11-12 at 10:30 +0100, Evgeni Golov wrote:
> > Can you please try systemd 232-3?
> > You should not need to pass systemd.legacy_systemd_cgroup_controller
> > anymore as the offending change wa
Hi,
On Fri, Jul 07, 2017 at 09:49:56PM +0200, benoit barthelet wrote:
> I couldn't start my unpriviledged containers anymore, seems like the
> libpam-cgfs is the culprit, according to the discussion I had here :
> https://discuss.linuxcontainers.org/t/failed-creating-cgroups/272/6l
> Installing
tive.
>
> ---
> Tony
>
>
>
> Forwarded Message
> Subject: Re: Fwd: Re: Bug#859220: Script /usr/share/lxcfs/lxc.mount.hook
> fails with mount command error 32 and causes lxc-start to fail
> Date: Wed, 21 Jun 2017 19:07:47 -0500
>
Hi Tony,
On Sun, Jun 18, 2017 at 09:45:00PM -0500, Tony Thedford wrote:
> Hello Evgeni, Well I do not use systemd on my systems.. could that have
> anything to do with it? Other than that, everything else is standard Debian
> 8 system structures.
LXC and LXCFS should work just fine w/o systemd
On Sun, Jun 18, 2017 at 03:23:20PM +0200, Evgeni Golov wrote:
> Hi Tony, Sven,
>
> On Sat, Jun 17, 2017 at 09:36:32PM +0200, Sven Velt wrote:
> > ,---
> > | # echo /var/lib/lxcfs/cgroup/*
> > | /var/lib/lxcfs/cgroup/*
> > `---
> >
> > And I can
Hi Tony, Sven,
On Sat, Jun 17, 2017 at 09:36:32PM +0200, Sven Velt wrote:
> ,---
> | # echo /var/lib/lxcfs/cgroup/*
> | /var/lib/lxcfs/cgroup/*
> `---
>
> And I can confirm that the small fix also works for me.
One thing I wonder, though: how do you two end up with an empty
Ohai,
On Wed, May 31, 2017 at 07:10:01PM -0400, JD Friedrikson wrote:
> Debian's packaged version of LXC currently is not able to stop systemd-based
> containers as they have not responded to SIGPWR as of
> https://github.com/lxc/lxc/commit/8eb62c245e9b67b451ba0766f3ecd7c6f2081d73 .
>
> The
1 - 100 of 1254 matches
Mail list logo
