Hi,
On Sun, Mar 16, 2025 at 01:30:41AM -0400, Dave Vasilevsky wrote:
> Package: tuned-ppd
> Version: 2.24.1-1
> Severity: normal
> X-Debbugs-Cc: d...@vasilevsky.ca
>
> With gnome-shell 48~rc-2, the Gnome quick settings menu no longer shows the
> Power
> Mode section that should be backed by tune
On Sun, Jan 15, 2023 at 09:27:05PM +0100, Jochen Sprickerhof wrote:
> > Is this problem resolved? Is it okay to mark this bug as closed?
>
> I think the real solution here would be a package with up to date data (or
> some online service to check against, maybe). The current workaround is just
>
On Sun, Jan 15, 2023 at 09:27:05PM +0100, Jochen Sprickerhof wrote:
> > Is this problem resolved? Is it okay to mark this bug as closed?
>
> I think the real solution here would be a package with up to date data (or
> some online service to check against, maybe). The current workaround is just
>
Package: jverein
Version: 2.8.19+dfsg-1
Severity: normal
X-Debbugs-Cc: evg...@debian.org
Ohai!
When you install jverein as-is and then try to import a member list
(JVerein → Administration → Import, then select a file via the "Datei
wählen" dialog), the import fails and the following error is se
Package: jverein
Version: 2.8.19+dfsg-1
Severity: normal
X-Debbugs-Cc: evg...@debian.org
Ohai!
When you install jverein as-is and then try to import a member list
(JVerein → Administration → Import, then select a file via the "Datei
wählen" dialog), the import fails and the following error is se
I've not touched geany packaging for, uhm, a while. Sorry.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/992#issuecomment-2212524787
You are receiving this because you are subscribed to this thread.
Message ID:
On Tue, Apr 02, 2024 at 09:31:55PM GMT, Thomas Lange wrote:
> > On Tue, 02 Apr 2024 19:59:57 +0200, Jörg Behrmann
> > said:
>
>
> > Activity in dracut upstream has died down recently and though there is
> a version
> > 60 of dracut in sid, upstream has not tagged such a release
On Wed, May 22, 2024 at 05:58:50PM +0200, Evgeni Golov wrote:
> On Tue, May 21, 2024 at 10:10:02PM -0700, Benjamin Lee wrote:
> > > It's probably the same issue with missing libraries, but I do not use
> > > either dracut nor LVM so I cannot help, reassigning to dracut s
On Tue, May 21, 2024 at 10:10:02PM -0700, Benjamin Lee wrote:
> > It's probably the same issue with missing libraries, but I do not use
> > either dracut nor LVM so I cannot help, reassigning to dracut so that
> > you might get some help with debugging and finding out what the actual
> > issue is
On Tue, May 21, 2024 at 07:46:43AM +0200, Manny wrote:
> > This was reported and fixed in #1038207
> >
> > If you're using a bpo kernel, I highly suggest to use kernel modules
> > from bpo too.
>
> I appreciate the suggestion. But I have to wonder, why didn’t apt
> prevent this? The purpose of a
On Tue, May 21, 2024 at 07:46:43AM +0200, Manny wrote:
> > This was reported and fixed in #1038207
> >
> > If you're using a bpo kernel, I highly suggest to use kernel modules
> > from bpo too.
>
> I appreciate the suggestion. But I have to wonder, why didn’t apt
> prevent this? The purpose of a
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 beca
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
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 ansible-ru
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 '/usr/lib
\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 p
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
> https://github
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
> https://github
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
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 (s
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 (s
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.
>
>https://salsa.debian.org/ci-team/autopkgtest/raw/master/doc/README.p
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
Title: Message Title
Evgeni Golov
Title: Message Title
Evgeni Golov updated
Title: Message Title
Evgeni Golov updated
Title: Message Title
Evgeni Golov created
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
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 pic
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 pic
Title: Message Title
Evgeni Golov
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 100644
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 working
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 recen
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:
https://salsa.
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:
https://salsa.
Evgeni Golov created PROTON-2434:
Summary: Container.connect doesn't set virtual_host by default,
making peer verification harder than it should be
Key: PROTON-2434
URL: https://issues.apache.org/jira/b
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
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
--- aprx-2.9.0+dfsg/debian/rule
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
--- aprx-2.9.0+dfsg/debian/rule
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
>
> poking
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
>
> poking
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
>
> poking
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), an
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), an
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), an
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 conversatio
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 conversatio
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 i
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 i
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 that cha
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 that cha
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 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/pci:0
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/pci:0
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
> Starti
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
> Starti
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
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
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 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 know whi
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 know whi
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 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 --d
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 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
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,
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 GRUB
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] https://app.vagrantup.com/debian/boxes/buste
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] https://app.vagrantup.com/debian/boxes/buste
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 GRUB
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: dracut-in
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) i
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) i
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 con
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: thinkf
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 file=sid.qcow2,if
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.
>
> I original
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.
> >
> >
1 - 100 of 4905 matches
Mail list logo
