Bug#1012286: RFS: zig/0.9.1-1 [ITP] -- Programming language
Hi, * Nick Hastings [240716 10:08]: > > I just merged the zig-0.11.0 branch into main. Note however that as far as I > understand it, the wasm blob introduced in 0.11.0 now makes this dsfg > non-free. > > The build for this version worked for me locally, but seems to have failed on > salsa. Will look into it. To clarify: - i386 package build failed but the default one succeeded - Obviously wasm binary means that the lintian check failed - blhc failed: complaining about missing -fstack-protector-strong - reprotest failed: exceeded maximum number of open file descriptors? https://salsa.debian.org/zig-team/zig/-/pipelines/702071 Cheers, Nick.
Bug#1012286: RFS: zig/0.9.1-1 [ITP] -- Programming language
Hi, * Otto Kekäläinen [240715 12:07]: > > The CI at > https://salsa.debian.org/zig-team/zig/-/jobs/5643130 fails on: > > /bin/sh: 1: ./obj-x86_64-linux-gnu/zig: not found Checking the log, it seems that the build worked but it failed to run the tests since it seems that the path to the final zig binary changed. > Do you need help getting past this? No, I know how to fix it. I just merged the zig-0.11.0 branch into main. Note however that as far as I understand it, the wasm blob introduced in 0.11.0 now makes this dsfg non-free. The build for this version worked for me locally, but seems to have failed on salsa. Will look into it. Cheers, Nick.
Bug#1012286: RFS: zig/0.9.1-1 [ITP] -- Programming language
* Otto Kekäläinen [240715 07:07]: > > Any particular reason this is not hosted on Salsa and using Salsa-CI > to validate that all easily testable things are correct? https://salsa.debian.org/zig-team/zig-team
Bug#1066072: ITP: swappy -- Wayland native snapshot and editor tool
Package: wnpp Severity: wishlist Owner: Nick Hastings X-Debbugs-Cc: debian-de...@lists.debian.org, nicholaschasti...@gmail.com * Package name: swappy Version : 1.5.1 Upstream Contact: Jeremy Attali * URL : https://github.com/jtheoof/swappy * License : MIT Programming Lang: C Description : Wayland native snapshot and editor tool A Wayland native snapshot and editor tool, inspired by Snappy on macOS. Works great with grim, slurp and sway. But can easily work with other screen copy tools that can output a final image to stdout. This tool provides a nice balance between feature set and ease of used for quickly annotating screenshots or other images. A sponsor will be needed.
Bug#995670: ITP: zig -- General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software
Hi, * Maytham Alsudany [240117 11:37]: > > Are you still working on the zig package? > I'd be happy to help you fix any problems that remain. I updated the package to Zig 0.10.1. The RFS bug still still open. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012286 I'll likely not even try packaging 0.11 or newer until it can once again bootstrap. However I don't expect that to happen anytime soon. Nick.
Bug#1043258: texlive-latex-extra-doc: moderncv.tex fails to build
Hi, sorry the bug subject line is wrong/bad. Better would be something like: "template.tex for moderncv.cls fails to build". Regards, Nick.
Bug#1043258: texlive-latex-extra-doc: moderncv.tex fails to build
Package: texlive-latex-extra-doc
Version: 2022.20230122-4
Severity: normal
X-Debbugs-Cc: nicholaschasti...@gmail.com
Dear Maintainer,
I have been unable to build a document using moderncv.cls. It seems
that either the documentation of the immplementaion of moderncv.cls
has a problem. The /usr/share/doc/texlive-doc/latex/moderncv/README.md
indicates that the example should be compiled with: `latexmk -pdf
./template.tex`
Following this documentation:
mkdir ~/tmp
cd tmp
zcat /usr/share/doc/texlive-doc/latex/moderncv/template.tex.gz > template.tex
cp /usr/share/doc/texlive-doc/latex/moderncv/picture.jpg .
latexmk -pdf template.tex 2>&1 | tee build.log
This results in the build hanging and the error:
.
.
.
*geometry* driver: auto-detecting
*geometry* detected driver: pdftex
(/usr/share/texmf/tex/latex/lm/ot1lmr.fd)
(/usr/share/texlive/texmf-dist/tex/latex/microtype/mt-cmr.cfg)
(/usr/share/texmf/tex/latex/lm/omllmm.fd)
(/usr/share/texmf/tex/latex/lm/omslmsy.fd)
(/usr/share/texmf/tex/latex/lm/omxlmex.fd)
Underfull \hbox (badness 1) in paragraph at lines 93--93
! Missing number, treated as zero.
}
l.95 \section{Education}
The build.log and template.log are attached.
Regards,
Nick.
-- System Information:
Debian Release: 12.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-10-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8),
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages texlive-latex-extra-doc depends on:
ii tex-common6.18
ii texlive-base 2022.20230122-3
texlive-latex-extra-doc recommends no packages.
texlive-latex-extra-doc suggests no packages.
Versions of packages tex-common depends on:
ii ucf 3.0043+nmu1
Versions of packages tex-common suggests:
ii debhelper 13.11.4
Versions of packages texlive-latex-extra-doc is related to:
ii tex-common6.18
ii texlive-binaries 2022.20220321.62855-5.1+deb12u1
-- no debconf information
build.log.gz
Description: application/gzip
template.log.gz
Description: application/gzip
Bug#1040783: libvirt-daemon: libvirt firewalld zone is missing
Hi, On Tue, 11 Jul 2023 04:41:07 +0200 =?UTF-8?Q?Niccol=C3=B2_Belli?= wrote: > I've found the root of the problem: I was connecting to libvirt via ssh > using an unprivileged user part of the libvirt group. That works for > most of the tasks but not for creating the firewalld libvirt zone. Using > root, while being less than ideal, works fine. I'm facing the same problem. I'm running virt-manager on the localhost as a user who is a member of the libvirt group. What did you actually run as root to have the libvirt zone created? Thanks, Nick.
Bug#1036530: Regression from "ACPI: OSI: Remove Linux-Dell-Video _OSI string"? (was: Re: Bug#1036530: linux-signed-amd64: Hard lock up of system)
Hi, * Limonciello, Mario [230701 06:40]: > > > > Nevertheless: thx for your report your help through this thread. > > > > No problem. I am willing to try to do more, but right now I don't know > > how to do what has been suggested. > > > > Here is where to report Nouveau bugs: > > https://gitlab.freedesktop.org/drm/nouveau/-/issues/ Thanks. Done: https://gitlab.freedesktop.org/drm/nouveau/-/issues/241 Cheers, Nick.
Bug#1036530: Regression from "ACPI: OSI: Remove Linux-Dell-Video _OSI string"? (was: Re: Bug#1036530: linux-signed-amd64: Hard lock up of system)
Hi, * Thorsten Leemhuis [230630 22:02]: > On 27.06.23 00:34, Nick Hastings wrote: > > * Linux regression tracking (Thorsten Leemhuis) > > [230626 21:09]: > >> Hi, Thorsten here, the Linux kernel's regression tracker. Top-posting > >> for once, to make this easily accessible to everyone. > >> > >> Nick, what's the status/was there any progress? Did you do what Mario > >> suggested and file a nouveau bug? > > > > It was not apparent that the suggestion to open "a Nouveau drm bug" was > > addressed to me. > > I wish things were earlier for reporters, but from what I can see this > is the only way forward if you or some silent bystander cares. In principle I can open another bug report, but I don't know how or where to report "a Nouveau drm bug". Please keep in mind that I'm just an end user. I learnt to use git bisect specifically because of this bug. Prior to that, I hadn't compiled a kernel in about 15 years. > >> I ask, as I still have this on my list of regressions and it seems there > >> was no progress in three+ weeks now. > > > > I have not pursued this further since as far as I could tell I already > > provided all requested information and I don't actually use nouveau, so > > I blacklisted it. > > I doubt any developer cares enough to take a closer look[1] without a > proper nouveau bug and some help & prodding from someone affected. And > looks to me like reverting the culprit now might create even bigger > problems for users. If someone can point me to some docs about for reporting nouveau bugs I can look into it. > Hence I guess then this won't be fixed in the end. In a ideal world this > would not happen, but we don't live in one and all have just 24 hours in > a day. :-/ This is a very common Dell XPS 15 7590 so I expect many people could experience this issue. Or maybe like me they only use the intel GPU. > Nevertheless: thx for your report your help through this thread. No problem. I am willing to try to do more, but right now I don't know how to do what has been suggested. Cheers, Nick. > [1] some points on the following page kinda explain this > https://linux-regtracking.leemhuis.info/post/frequent-reasons-why-linux-kernel-bug-reports-are-ignored/ > > Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) > -- > Everything you wanna know about Linux kernel regression tracking: > https://linux-regtracking.leemhuis.info/about/#tldr > If I did something stupid, please tell me, as explained on that page. > > #regzbot inconclusive: reporting deadlock (see thread for details) > > > > >> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) > >> -- > >> Everything you wanna know about Linux kernel regression tracking: > >> https://linux-regtracking.leemhuis.info/about/#tldr > >> If I did something stupid, please tell me, as explained on that page. > >> > >> #regzbot backburner: slow progress, likely just affects one machine > >> #regzbot poke > >> > >> > >> On 02.06.23 02:57, Limonciello, Mario wrote: > >>> [AMD Official Use Only - General] > >>> > >>>> -Original Message- > >>>> From: Nick Hastings > >>>> Sent: Thursday, June 1, 2023 7:02 PM > >>>> To: Karol Herbst > >>>> Cc: Limonciello, Mario ; Lyude Paul > >>>> ; Lukas Wunner ; Salvatore > >>>> Bonaccorso ; 1036...@bugs.debian.org; Rafael J. > >>>> Wysocki ; Len Brown ; linux- > >>>> a...@vger.kernel.org; linux-ker...@vger.kernel.org; > >>>> regressi...@lists.linux.dev > >>>> Subject: Re: Regression from "ACPI: OSI: Remove Linux-Dell-Video _OSI > >>>> string"? (was: Re: Bug#1036530: linux-signed-amd64: Hard lock up of > >>>> system) > >>>> > >>>> Hi, > >>>> > >>>> * Karol Herbst [230602 03:10]: > >>>>> On Thu, Jun 1, 2023 at 7:21 PM Limonciello, Mario > >>>>> wrote: > >>>>>>> -Original Message- > >>>>>>> From: Karol Herbst > >>>>>>> Sent: Thursday, June 1, 2023 12:19 PM > >>>>>>> To: Limonciello, Mario > >>>>>>> Cc: Nick Hastings ; Lyude Paul > >>>>>>> ; Lukas Wunner ; Salvatore > >>>>>>> Bonaccorso ; 1036...@bugs.debian.org; Rafael J. > >>>>>>> Wysocki ; Len Brown ;
Bug#1039867: release.debian.org: Site uses old favicon.ico
Package: release.debian.org Severity: minor X-Debbugs-Cc: nicholaschasti...@gmail.com Hi, the site https://release.debian.org uses an old version of the debian favicon.ico that renders poorly on dark backgrounds. Please use the same favicon.ico as https://www.debian.org Note that this is also a problem on https://backports.debian.org and https://search.debian.org. I have already attempted to alert the relevant people for those sites. Regards, Nick.
Bug#1036530: Regression from "ACPI: OSI: Remove Linux-Dell-Video _OSI string"? (was: Re: Bug#1036530: linux-signed-amd64: Hard lock up of system)
Hi Thorsten,
* Linux regression tracking (Thorsten Leemhuis)
[230626 21:09]:
> Hi, Thorsten here, the Linux kernel's regression tracker. Top-posting
> for once, to make this easily accessible to everyone.
>
> Nick, what's the status/was there any progress? Did you do what Mario
> suggested and file a nouveau bug?
It was not apparent that the suggestion to open "a Nouveau drm bug" was
addressed to me.
> I ask, as I still have this on my list of regressions and it seems there
> was no progress in three+ weeks now.
I have not pursued this further since as far as I could tell I already
provided all requested information and I don't actually use nouveau, so
I blacklisted it.
Regards,
Nick.
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> --
> Everything you wanna know about Linux kernel regression tracking:
> https://linux-regtracking.leemhuis.info/about/#tldr
> If I did something stupid, please tell me, as explained on that page.
>
> #regzbot backburner: slow progress, likely just affects one machine
> #regzbot poke
>
>
> On 02.06.23 02:57, Limonciello, Mario wrote:
> > [AMD Official Use Only - General]
> >
> >> -Original Message-
> >> From: Nick Hastings
> >> Sent: Thursday, June 1, 2023 7:02 PM
> >> To: Karol Herbst
> >> Cc: Limonciello, Mario ; Lyude Paul
> >> ; Lukas Wunner ; Salvatore
> >> Bonaccorso ; 1036...@bugs.debian.org; Rafael J.
> >> Wysocki ; Len Brown ; linux-
> >> a...@vger.kernel.org; linux-ker...@vger.kernel.org;
> >> regressi...@lists.linux.dev
> >> Subject: Re: Regression from "ACPI: OSI: Remove Linux-Dell-Video _OSI
> >> string"? (was: Re: Bug#1036530: linux-signed-amd64: Hard lock up of system)
> >>
> >> Hi,
> >>
> >> * Karol Herbst [230602 03:10]:
> >>> On Thu, Jun 1, 2023 at 7:21 PM Limonciello, Mario
> >>> wrote:
> >>>>> -Original Message-
> >>>>> From: Karol Herbst
> >>>>> Sent: Thursday, June 1, 2023 12:19 PM
> >>>>> To: Limonciello, Mario
> >>>>> Cc: Nick Hastings ; Lyude Paul
> >>>>> ; Lukas Wunner ; Salvatore
> >>>>> Bonaccorso ; 1036...@bugs.debian.org; Rafael J.
> >>>>> Wysocki ; Len Brown ; linux-
> >>>>> a...@vger.kernel.org; linux-ker...@vger.kernel.org;
> >>>>> regressi...@lists.linux.dev
> >>>>> Subject: Re: Regression from "ACPI: OSI: Remove Linux-Dell-Video _OSI
> >>>>> string"? (was: Re: Bug#1036530: linux-signed-amd64: Hard lock up of
> >> system)
> >>>>>
> >>>>> On Thu, Jun 1, 2023 at 6:54 PM Limonciello, Mario
> >>>>> wrote:
> >>>>>>
> >>>>>> [AMD Official Use Only - General]
> >>>>>>
> >>>>>>> -Original Message-
> >>>>>>> From: Karol Herbst
> >>>>>>> Sent: Thursday, June 1, 2023 11:33 AM
> >>>>>>> To: Limonciello, Mario
> >>>>>>> Cc: Nick Hastings ; Lyude Paul
> >>>>>>> ; Lukas Wunner ; Salvatore
> >>>>>>> Bonaccorso ; 1036...@bugs.debian.org; Rafael
> >> J.
> >>>>>>> Wysocki ; Len Brown ; linux-
> >>>>>>> a...@vger.kernel.org; linux-ker...@vger.kernel.org;
> >>>>>>> regressi...@lists.linux.dev
> >>>>>>> Subject: Re: Regression from "ACPI: OSI: Remove Linux-Dell-Video
> >> _OSI
> >>>>>>> string"? (was: Re: Bug#1036530: linux-signed-amd64: Hard lock up of
> >>>>> system)
> >>>>>>>
> >>>>>>> On Thu, Jun 1, 2023 at 6:18 PM Limonciello, Mario
> >>>>>>>>
> >>>>>>>> Lyude, Lukas, Karol
> >>>>>>>>
> >>>>>>>> This thread is in relation to this commit:
> >>>>>>>>
> >>>>>>>> 24867516f06d ("ACPI: OSI: Remove Linux-Dell-Video _OSI string")
> >>>>>>>>
> >>>>>>>> Nick has found that runtime PM is *not* working for nouveau.
> >>>>>>>>
> >>>>>>>
> >>>>>>> keep in mind we have a list of PCIe controllers where we apply a
> >>>>>>> workaround:
> >>>>>>>
> >>>
Bug#995670: What's the status of this ITP?
Hi, * Abraham Raji [230620 17:37]: > > On 20/06/23 13:54, Nick Hastings wrote: > > > As far as I know the d/copyright file covers everything. > > > > > Or is there a licensing issue here? > > > > I don't think there is a licensing issue. > > > > It is the specifics of the d/copyright file I produced. Please see the > > RFS bug for details. > > Will take a look. Thanks. > > > > > I have created a zig-team namespace on salsa and I've invited you there. > > > We can move the packaging work there as it will make it easier for > > > potential contributors to find it. > > > > I joined it. > > Great let's get the zig package there. Done. > > > Also is there any particular reason you are only committing the debian > > > directory? > > > > That is all that exists in the repo. Builds are done by downloading the > > source with uscan with the info from the d/watch file. I did try to look > > into keeping upstream in the same repo but I didn't find a clear path > > forward. So I just stuck with what I am currently doing since it works > > and from the documentation I have read is not "incorrect". If you could > > recommend specific documentation for this I can have a look. > > I do find the ruby team's approach to be very nice here. Adding link > to a sample ruby package for reference[0]. The approach is to keep > the upstream files and tar ball deltas in separate branches (upstream > and pristine-tar). The tooling makes maintaining this pretty seamless. I see. I'll try to have a look. > Please take a look at these page for more information: - > https://wiki.debian.org/SimplePackagingTutorial - > https://wiki.abrahamraji.in/simple-packaging-tutorial.html I'm familiar with this level of packaging. IIRC when I tried to look at a "proper" packaging work flow using git there did not appear to be a "correct" way to do it. Multiple different approaches only quite briefly documented. Perhaps without much information about why particular things were done, and seemingly to expecting knowledge of the other approaches. Cheers, Nick. > [0]: https://salsa.debian.org/ruby-team/atig
Bug#995670: What's the status of this ITP?
Hi, * Abraham Raji [230620 16:53]: > > On 20/06/23 04:48, Nick Hastings wrote: > > There was some progress and some interest from a potential sponsor but > > it seems that the copyright file has become a road block. > > What exactly is the roadblock? Is it just a matter of going through each > of the files and adding the entries? As far as I know the d/copyright file covers everything. > Or is there a licensing issue here? I don't think there is a licensing issue. It is the specifics of the d/copyright file I produced. Please see the RFS bug for details. > Asking because for the first we can always try and get more people to > help out. That would be nice. > > My package is on salsa: https://github.com/NickHastings/zig-debian Adding the correction here too: https://salsa.debian.org/nickh/zig > I have created a zig-team namespace on salsa and I've invited you there. > We can move the packaging work there as it will make it easier for > potential contributors to find it. I joined it. > Also is there any particular reason you are only committing the debian > directory? That is all that exists in the repo. Builds are done by downloading the source with uscan with the info from the d/watch file. I did try to look into keeping upstream in the same repo but I didn't find a clear path forward. So I just stuck with what I am currently doing since it works and from the documentation I have read is not "incorrect". If you could recommend specific documentation for this I can have a look. Cheers, Nick.
Bug#995670: What's the status of this ITP?
* Nick Hastings [230620 08:18]: > > My package is on salsa: https://github.com/NickHastings/zig-debian While that statement is true, the link is clearly not the intended one. https://salsa.debian.org/nickh/zig Nick.
Bug#995670: What's the status of this ITP?
Hi, * Abraham Raji [230620 06:38]: > > What's the status of this ITP? It seems like Nick is pulling a > considerable amount of work himself. I filed an RFS bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012286 There was some progress and some interest from a potential sponsor but it seems that the copyright file has become a road block. > I would personally love to see Zig in the Debian archives so I am > ready to volunteer some of my time towards the effort. My zig package is up to date with the current version of zig 0.10.1 and this version of zig can bootstrap. However, it seems that the next planned release of zig will not be able to bootstrap (in the usual sense). See for example https://ziglang.org/news/goodbye-cpp/ > I feel we can move the work for this package to salsa if no one has any > issues. My package is on salsa: https://github.com/NickHastings/zig-debian Cheers, Nick.
Bug#1036530: Regression from "ACPI: OSI: Remove Linux-Dell-Video _OSI string"? (was: Re: Bug#1036530: linux-signed-amd64: Hard lock up of system)
Hi,
* Karol Herbst [230602 03:10]:
> On Thu, Jun 1, 2023 at 7:21 PM Limonciello, Mario
> wrote:
> > > -Original Message-
> > > From: Karol Herbst
> > > Sent: Thursday, June 1, 2023 12:19 PM
> > > To: Limonciello, Mario
> > > Cc: Nick Hastings ; Lyude Paul
> > > ; Lukas Wunner ; Salvatore
> > > Bonaccorso ; 1036...@bugs.debian.org; Rafael J.
> > > Wysocki ; Len Brown ; linux-
> > > a...@vger.kernel.org; linux-ker...@vger.kernel.org;
> > > regressi...@lists.linux.dev
> > > Subject: Re: Regression from "ACPI: OSI: Remove Linux-Dell-Video _OSI
> > > string"? (was: Re: Bug#1036530: linux-signed-amd64: Hard lock up of
> > > system)
> > >
> > > On Thu, Jun 1, 2023 at 6:54 PM Limonciello, Mario
> > > wrote:
> > > >
> > > > [AMD Official Use Only - General]
> > > >
> > > > > -Original Message-
> > > > > From: Karol Herbst
> > > > > Sent: Thursday, June 1, 2023 11:33 AM
> > > > > To: Limonciello, Mario
> > > > > Cc: Nick Hastings ; Lyude Paul
> > > > > ; Lukas Wunner ; Salvatore
> > > > > Bonaccorso ; 1036...@bugs.debian.org; Rafael J.
> > > > > Wysocki ; Len Brown ; linux-
> > > > > a...@vger.kernel.org; linux-ker...@vger.kernel.org;
> > > > > regressi...@lists.linux.dev
> > > > > Subject: Re: Regression from "ACPI: OSI: Remove Linux-Dell-Video _OSI
> > > > > string"? (was: Re: Bug#1036530: linux-signed-amd64: Hard lock up of
> > > system)
> > > > >
> > > > > On Thu, Jun 1, 2023 at 6:18 PM Limonciello, Mario
> > > > > >
> > > > > > Lyude, Lukas, Karol
> > > > > >
> > > > > > This thread is in relation to this commit:
> > > > > >
> > > > > > 24867516f06d ("ACPI: OSI: Remove Linux-Dell-Video _OSI string")
> > > > > >
> > > > > > Nick has found that runtime PM is *not* working for nouveau.
> > > > > >
> > > > >
> > > > > keep in mind we have a list of PCIe controllers where we apply a
> > > > > workaround:
> > > > >
> > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers
> > > > > /gpu/drm/nouveau/nouveau_drm.c?h=v6.4-rc4#n682
> > > > >
> > > > > And I suspect there might be one or two more IDs we'll have to add
> > > > > there. Do we have any logs?
> > > >
> > > > There's some archived onto the distro bug. Search this page for
> > > "journalctl.log.gz"
> > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036530
> > > >
> > >
> > > interesting.. It seems to be the same controller used here. I wonder
> > > if the pci topology is different or if the workaround is applied at
> > > all.
> >
> > I didn't see the message in the log about the workaround being applied
> > in that log, so I guess PCI topology difference is a likely suspect.
> >
>
> yeah, but I also couldn't see a log with the usual nouveau messages,
> so it's kinda weird.
>
> Anyway, the output of `lspci -tvnn` would help
% lspci -tvnn
-[:00]-+-00.0 Intel Corporation Device [8086:3e20]
+-01.0-[01]00.0 NVIDIA Corporation TU117M [GeForce GTX 1650
Mobile / Max-Q] [10de:1f91]
+-02.0 Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630]
[8086:3e9b]
+-04.0 Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core
Processor Thermal Subsystem [8086:1903]
+-08.0 Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 /
6th/7th/8th Gen Core Processor Gaussian Mixture Model [8086:1911]
+-12.0 Intel Corporation Cannon Lake PCH Thermal Controller
[8086:a379]
+-14.0 Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host
Controller [8086:a36d]
+-14.2 Intel Corporation Cannon Lake PCH Shared SRAM [8086:a36f]
+-15.0 Intel Corporation Cannon Lake PCH Serial IO I2C Controller
#0 [8086:a368]
+-15.1 Intel Corporation Cannon Lake PCH Serial IO I2C Controller
#1 [8086:a369]
+-16.0 Intel Corporation Cannon Lake PCH HECI Controller [8086:a360]
+-17.0 Intel Corporation Cannon Lake Mobile PCH SATA AHCI
Controller [8086:a353]
+-1b.0-[02-3a]00.0-[03-3a]--+-00.0-[04]00.0 Intel
Corporation JHL6340 Thunderbolt 3 NHI (C step) [Alpine Ridge 2C 2016]
[8086:15d9]
| +-01.0-[05-39]--
| \-02.0-[3a]00.0 Intel
Corporation JHL6340 Thunderbolt 3 USB 3.1 Controller (C step) [Alpine Ridge 2C
2016] [8086:15db]
+-1c.0-[3b]00.0 Intel Corporation Wi-Fi 6 AX200 [8086:2723]
+-1c.4-[3c]00.0 Realtek Semiconductor Co., Ltd. RTS525A PCI
Express Card Reader [10ec:525a]
+-1d.0-[3d]00.0 Samsung Electronics Co Ltd NVMe SSD Controller
SM981/PM981/PM983 [144d:a808]
+-1f.0 Intel Corporation Cannon Lake LPC Controller [8086:a30e]
+-1f.3 Intel Corporation Cannon Lake PCH cAVS [8086:a348]
+-1f.4 Intel Corporation Cannon Lake PCH SMBus Controller
[8086:a323]
\-1f.5 Intel Corporation Cannon Lake PCH SPI Controller
[8086:a324]
Regards,
Nick.
Bug#1036530: Regression from "ACPI: OSI: Remove Linux-Dell-Video _OSI string"? (was: Re: Bug#1036530: linux-signed-amd64: Hard lock up of system)
Hi, * Limonciello, Mario [230602 01:18]: > +Lyude, Lukas, Karol > > On 5/31/2023 6:40 PM, Nick Hastings wrote: > > > > * Nick Hastings [230530 16:01]: > > > * Mario Limonciello [230530 13:00]: > > > > > > As you're actually loading nouveau, can you please try nouveau.runpm=0 > > > > on > > > > the kernel command line? > > > I'm not intentionally loading it. This machine also has intel graphics > > > which is what I prefer. Checking my > > > /etc/modprobe.d/blacklist-nvidia-nouveau.conf > > > I see: > > > > > > blacklist nvidia > > > blacklist nvidia-drm > > > blacklist nvidia-modeset > > > blacklist nvidia-uvm > > > blacklist ipmi_msghandler > > > blacklist ipmi_devintf > > > > > > So I thought I had blacklisted it but it seems I did not. Since I do not > > > want to use it maybe it is better to check if the lock up occurs with > > > nouveau blacklisted. I will try that now. > > I blacklisted nouveau and booted into a 6.1 kernel: > > % uname -a > > Linux xps 6.1.0-9-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1 (2023-05-08) > > x86_64 GNU/Linux > > > > It has been running without problems for nearly two days now: > > % uptime > > 08:34:48 up 1 day, 16:22, 2 users, load average: 1.33, 1.26, 1.27 > > > > Regards, > > > > Nick. > > Thanks, that makes a lot more sense now. > > Nick, Can you please test if nouveau works with runtime PM in the > latest 6.4-rc? I reported this twice already. I guess it was lost since for some reason emails in this thread are not being trimmed. I'll repeat here: I did eventually see a lockup of this kernel. On the console I saw: [ 151.035036] vfio-pci :01:00.0 Unable to change power state from D3cold to D0, device inaccessible I did not see the other two lines that were present in earlier lock ups. Regards, Nick.
Bug#1036530: Regression from "ACPI: OSI: Remove Linux-Dell-Video _OSI string"? (was: Re: Bug#1036530: linux-signed-amd64: Hard lock up of system)
Hi, * Nick Hastings [230530 16:01]: > > * Mario Limonciello [230530 13:00]: > > As you're actually loading nouveau, can you please try nouveau.runpm=0 on > > the kernel command line? > > I'm not intentionally loading it. This machine also has intel graphics > which is what I prefer. Checking my > /etc/modprobe.d/blacklist-nvidia-nouveau.conf > I see: > > blacklist nvidia > blacklist nvidia-drm > blacklist nvidia-modeset > blacklist nvidia-uvm > blacklist ipmi_msghandler > blacklist ipmi_devintf > > So I thought I had blacklisted it but it seems I did not. Since I do not > want to use it maybe it is better to check if the lock up occurs with > nouveau blacklisted. I will try that now. I blacklisted nouveau and booted into a 6.1 kernel: % uname -a Linux xps 6.1.0-9-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1 (2023-05-08) x86_64 GNU/Linux It has been running without problems for nearly two days now: % uptime 08:34:48 up 1 day, 16:22, 2 users, load average: 1.33, 1.26, 1.27 Regards, Nick.
Bug#1036530: Regression from "ACPI: OSI: Remove Linux-Dell-Video _OSI string"? (was: Re: Bug#1036530: linux-signed-amd64: Hard lock up of system)
Hi,
* Mario Limonciello [230530 13:00]:
> On 5/29/23 18:01, Nick Hastings wrote:
> > Hi,
> >
> > * Nick Hastings [230529 12:51]:
> > > * Mario Limonciello [230529 10:14]:
> > > > On 5/28/23 19:56, Nick Hastings wrote:
> > > > > Hi,
> > > > >
> > > > > * Mario Limonciello [230528 21:44]:
> > > > > > On 5/28/23 01:49, Salvatore Bonaccorso wrote:
> > > > > > > Hi Mario
> > > > > > >
> > > > > > > Nick Hastings reported in Debian in
> > > > > > > https://bugs.debian.org/1036530
> > > > > > > lockups from his system after updating from a 6.0 based version to
> > > > > > > 6.1.y. >
> > > > > > > #regzbot ^introduced 24867516f06d
> > > > > > >
> > > > > > > he bisected the issue and tracked it down to:
> > > > > > >
> > > > > > > On Sun, May 28, 2023 at 10:14:51AM +0900, Nick Hastings wrote:
> > > > > > > > Control: tags -1 - moreinfo
> > > > > > > >
> > > > > > > > Hi,
> > > > > > > >
> > > > > > > > I repeated the git bisect, and the bad commit seems to be:
> > > > > > > >
> > > > > > > > (git)-[v6.1-rc1~206^2~4^5~3|bisect] % git bisect bad
> > > > > > > > 24867516f06dabedef3be7eea0ef0846b91538bc is the first bad commit
> > > > > > > > commit 24867516f06dabedef3be7eea0ef0846b91538bc
> > > > > > > > Author: Mario Limonciello
> > > > > > > > Date: Tue Aug 23 13:51:31 2022 -0500
> > > > > > > >
> > > > > > > >ACPI: OSI: Remove Linux-Dell-Video _OSI string
> > > > > > > >This string was introduced because drivers for NVIDIA
> > > > > > > > hardware
> > > > > > > >had bugs supporting RTD3 in the past.
> > > > > > > >Before proprietary NVIDIA driver started to support
> > > > > > > > RTD3, Ubuntu had
> > > > > > > >had a mechanism for switching PRIME on and off, though
> > > > > > > > it had required
> > > > > > > >to logout/login to make the library switch happen.
> > > > > > > >When the PRIME had been off, the mechanism had unloaded
> > > > > > > > the NVIDIA
> > > > > > > >driver and put the device into D3cold, but the GPU had
> > > > > > > > never come back
> > > > > > > >to D0 again which is why ODMs used the _OSI to expose an
> > > > > > > > old _DSM
> > > > > > > >method to switch the power on/off.
> > > > > > > >That has been fixed by commit 5775b843a619 ("PCI:
> > > > > > > > Restore config space
> > > > > > > >on runtime resume despite being unbound"). so vendors
> > > > > > > > shouldn't be
> > > > > > > >using this string to modify ASL any more.
> > > > > > > >Reviewed-by: Lyude Paul
> > > > > > > >Signed-off-by: Mario Limonciello
> > > > > > > >
> > > > > > > >Signed-off-by: Rafael J. Wysocki
> > > > > > > >
> > > > > > > >
> > > > > > > > drivers/acpi/osi.c | 9 -
> > > > > > > > 1 file changed, 9 deletions(-)
> > > > > > > >
> > > > > > > > This machine is a Dell with an nvidia chip so it looks like
> > > > > > > > this really
> > > > > > > > could be the commit that that is causing the problems. The
> > > > > > > > description
> > > > > > > > of the commit also seems (to my untrained eye) to be consistent
> > > > > > > > with the
> > > > > > > > error reported on the console when the lockup occurs:
> > > > > > > >
> > > > > > > > [ 58.729863] ACPI Error: Aborting method \_SB.PCI0.PGON due
> > > > > > > > to previous error (AE_AML_LOOP_TIMEOUT) (
Bug#1036530: Regression from "ACPI: OSI: Remove Linux-Dell-Video _OSI string"? (was: Re: Bug#1036530: linux-signed-amd64: Hard lock up of system)
Hi,
* Nick Hastings [230529 12:51]:
> * Mario Limonciello [230529 10:14]:
> > On 5/28/23 19:56, Nick Hastings wrote:
> > > Hi,
> > >
> > > * Mario Limonciello [230528 21:44]:
> > > > On 5/28/23 01:49, Salvatore Bonaccorso wrote:
> > > > > Hi Mario
> > > > >
> > > > > Nick Hastings reported in Debian in https://bugs.debian.org/1036530
> > > > > lockups from his system after updating from a 6.0 based version to
> > > > > 6.1.y. >
> > > > > #regzbot ^introduced 24867516f06d
> > > > >
> > > > > he bisected the issue and tracked it down to:
> > > > >
> > > > > On Sun, May 28, 2023 at 10:14:51AM +0900, Nick Hastings wrote:
> > > > > > Control: tags -1 - moreinfo
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I repeated the git bisect, and the bad commit seems to be:
> > > > > >
> > > > > > (git)-[v6.1-rc1~206^2~4^5~3|bisect] % git bisect bad
> > > > > > 24867516f06dabedef3be7eea0ef0846b91538bc is the first bad commit
> > > > > > commit 24867516f06dabedef3be7eea0ef0846b91538bc
> > > > > > Author: Mario Limonciello
> > > > > > Date: Tue Aug 23 13:51:31 2022 -0500
> > > > > >
> > > > > > ACPI: OSI: Remove Linux-Dell-Video _OSI string
> > > > > > This string was introduced because drivers for NVIDIA hardware
> > > > > > had bugs supporting RTD3 in the past.
> > > > > > Before proprietary NVIDIA driver started to support RTD3,
> > > > > > Ubuntu had
> > > > > > had a mechanism for switching PRIME on and off, though it had
> > > > > > required
> > > > > > to logout/login to make the library switch happen.
> > > > > > When the PRIME had been off, the mechanism had unloaded the
> > > > > > NVIDIA
> > > > > > driver and put the device into D3cold, but the GPU had never
> > > > > > come back
> > > > > > to D0 again which is why ODMs used the _OSI to expose an old
> > > > > > _DSM
> > > > > > method to switch the power on/off.
> > > > > > That has been fixed by commit 5775b843a619 ("PCI: Restore
> > > > > > config space
> > > > > > on runtime resume despite being unbound"). so vendors
> > > > > > shouldn't be
> > > > > > using this string to modify ASL any more.
> > > > > > Reviewed-by: Lyude Paul
> > > > > > Signed-off-by: Mario Limonciello
> > > > > > Signed-off-by: Rafael J. Wysocki
> > > > > >
> > > > > >drivers/acpi/osi.c | 9 -
> > > > > >1 file changed, 9 deletions(-)
> > > > > >
> > > > > > This machine is a Dell with an nvidia chip so it looks like this
> > > > > > really
> > > > > > could be the commit that that is causing the problems. The
> > > > > > description
> > > > > > of the commit also seems (to my untrained eye) to be consistent
> > > > > > with the
> > > > > > error reported on the console when the lockup occurs:
> > > > > >
> > > > > > [ 58.729863] ACPI Error: Aborting method \_SB.PCI0.PGON due to
> > > > > > previous error (AE_AML_LOOP_TIMEOUT) (20220331/psparse-529)
> > > > > > [ 58.729904] ACPI Error: Aborting method \_SB.PCI0.PEG0.PG00._ON
> > > > > > due to previous error (AE_AML_LOOP_TIMEOUT) (20220331/psparse-529)
> > > > > > [ 60.083261] vfio-pci :01:00.0 Unable to change power state
> > > > > > from D3cold to D0, device inaccessible
> > > > > >
> > > > > > Hopefully this is enough information for experts to resolve this.
> > > > >
> > > > > Does this ring some bell for you? Do you need any further information
> > > > > from Nick?
> > > > >
> > > > > Regards,
> > > > > Salvatore
> > > >
> > >
> > > > Have Nick try using "pcie_port_pm=off" and see if it helps the issue.
> > >
> > > I booted into
Bug#1036530: Regression from "ACPI: OSI: Remove Linux-Dell-Video _OSI string"? (was: Re: Bug#1036530: linux-signed-amd64: Hard lock up of system)
* Mario Limonciello [230529 10:14]:
> On 5/28/23 19:56, Nick Hastings wrote:
> > Hi,
> >
> > * Mario Limonciello [230528 21:44]:
> > > On 5/28/23 01:49, Salvatore Bonaccorso wrote:
> > > > Hi Mario
> > > >
> > > > Nick Hastings reported in Debian in https://bugs.debian.org/1036530
> > > > lockups from his system after updating from a 6.0 based version to
> > > > 6.1.y. >
> > > > #regzbot ^introduced 24867516f06d
> > > >
> > > > he bisected the issue and tracked it down to:
> > > >
> > > > On Sun, May 28, 2023 at 10:14:51AM +0900, Nick Hastings wrote:
> > > > > Control: tags -1 - moreinfo
> > > > >
> > > > > Hi,
> > > > >
> > > > > I repeated the git bisect, and the bad commit seems to be:
> > > > >
> > > > > (git)-[v6.1-rc1~206^2~4^5~3|bisect] % git bisect bad
> > > > > 24867516f06dabedef3be7eea0ef0846b91538bc is the first bad commit
> > > > > commit 24867516f06dabedef3be7eea0ef0846b91538bc
> > > > > Author: Mario Limonciello
> > > > > Date: Tue Aug 23 13:51:31 2022 -0500
> > > > >
> > > > > ACPI: OSI: Remove Linux-Dell-Video _OSI string
> > > > > This string was introduced because drivers for NVIDIA hardware
> > > > > had bugs supporting RTD3 in the past.
> > > > > Before proprietary NVIDIA driver started to support RTD3,
> > > > > Ubuntu had
> > > > > had a mechanism for switching PRIME on and off, though it had
> > > > > required
> > > > > to logout/login to make the library switch happen.
> > > > > When the PRIME had been off, the mechanism had unloaded the
> > > > > NVIDIA
> > > > > driver and put the device into D3cold, but the GPU had never
> > > > > come back
> > > > > to D0 again which is why ODMs used the _OSI to expose an old
> > > > > _DSM
> > > > > method to switch the power on/off.
> > > > > That has been fixed by commit 5775b843a619 ("PCI: Restore
> > > > > config space
> > > > > on runtime resume despite being unbound"). so vendors shouldn't
> > > > > be
> > > > > using this string to modify ASL any more.
> > > > > Reviewed-by: Lyude Paul
> > > > > Signed-off-by: Mario Limonciello
> > > > > Signed-off-by: Rafael J. Wysocki
> > > > >
> > > > >drivers/acpi/osi.c | 9 -
> > > > >1 file changed, 9 deletions(-)
> > > > >
> > > > > This machine is a Dell with an nvidia chip so it looks like this
> > > > > really
> > > > > could be the commit that that is causing the problems. The description
> > > > > of the commit also seems (to my untrained eye) to be consistent with
> > > > > the
> > > > > error reported on the console when the lockup occurs:
> > > > >
> > > > > [ 58.729863] ACPI Error: Aborting method \_SB.PCI0.PGON due to
> > > > > previous error (AE_AML_LOOP_TIMEOUT) (20220331/psparse-529)
> > > > > [ 58.729904] ACPI Error: Aborting method \_SB.PCI0.PEG0.PG00._ON
> > > > > due to previous error (AE_AML_LOOP_TIMEOUT) (20220331/psparse-529)
> > > > > [ 60.083261] vfio-pci :01:00.0 Unable to change power state
> > > > > from D3cold to D0, device inaccessible
> > > > >
> > > > > Hopefully this is enough information for experts to resolve this.
> > > >
> > > > Does this ring some bell for you? Do you need any further information
> > > > from Nick?
> > > >
> > > > Regards,
> > > > Salvatore
> > >
> >
> > > Have Nick try using "pcie_port_pm=off" and see if it helps the issue.
> >
> > I booted into a 6.1 kernel with this option. It has been running without
> > problems for 1.5 hours. Usually I would expect the lockup to have
> > occurred by now.
I let this run for 3 hours without issue.
> > > Does this happen in the latest 6.4 RC as well?
> >
> > I have compiled that kernel and will boot into it after running this one
> > with the pcie_port_pm=off for another hour or so.
I'm now running 6.4.0-rc4 without seeing the problem after 1 hour.
I did however see two unrelated problems that I include here for
completeness:
1. iwlwifi module did not automatically load
2. Xwayland used huge amount of CPU even though was not running any X
programs. Recompiling my wayland compositor without XWayland support
"fixed" this.
> > > I think we need to see a full dmesg and acpidump to better
> > > characterize it.
> >
> > Please find attached. Let me know if there is anything else I can provide.
> >
> > Regards,
> >
> > Nick.
>
> I don't see nouveau loading, are you explicitly preventing it from
> loading?
Yes nouveau is blacklisted.
> Can I see the journal from a boot when it reproduced?
Hmm not sure which n for "journalctl -b n" maps to which kernel (is that
what you are requesting?). The commit hash doesn't not seem to be
listed. I may have to boot into a bad kernel again.
Regards,
Ncik.
Bug#1036530: linux-signed-amd64: Hard lock up of system
Control: tags -1 - moreinfo
Hi,
I repeated the git bisect, and the bad commit seems to be:
(git)-[v6.1-rc1~206^2~4^5~3|bisect] % git bisect bad
24867516f06dabedef3be7eea0ef0846b91538bc is the first bad commit
commit 24867516f06dabedef3be7eea0ef0846b91538bc
Author: Mario Limonciello
Date: Tue Aug 23 13:51:31 2022 -0500
ACPI: OSI: Remove Linux-Dell-Video _OSI string
This string was introduced because drivers for NVIDIA hardware
had bugs supporting RTD3 in the past.
Before proprietary NVIDIA driver started to support RTD3, Ubuntu had
had a mechanism for switching PRIME on and off, though it had required
to logout/login to make the library switch happen.
When the PRIME had been off, the mechanism had unloaded the NVIDIA
driver and put the device into D3cold, but the GPU had never come back
to D0 again which is why ODMs used the _OSI to expose an old _DSM
method to switch the power on/off.
That has been fixed by commit 5775b843a619 ("PCI: Restore config space
on runtime resume despite being unbound"). so vendors shouldn't be
using this string to modify ASL any more.
Reviewed-by: Lyude Paul
Signed-off-by: Mario Limonciello
Signed-off-by: Rafael J. Wysocki
drivers/acpi/osi.c | 9 -
1 file changed, 9 deletions(-)
This machine is a Dell with an nvidia chip so it looks like this really
could be the commit that that is causing the problems. The description
of the commit also seems (to my untrained eye) to be consistent with the
error reported on the console when the lockup occurs:
[ 58.729863] ACPI Error: Aborting method \_SB.PCI0.PGON due to previous error
(AE_AML_LOOP_TIMEOUT) (20220331/psparse-529)
[ 58.729904] ACPI Error: Aborting method \_SB.PCI0.PEG0.PG00._ON due to
previous error (AE_AML_LOOP_TIMEOUT) (20220331/psparse-529)
[ 60.083261] vfio-pci :01:00.0 Unable to change power state from D3cold
to D0, device inaccessible
Hopefully this is enough information for experts to resolve this.
Regards,
Nick.
* Salvatore Bonaccorso [230526 20:30]:
> Control: tags -1 + moreinfo
>
> Hi Nick,
>
> On Fri, May 26, 2023 at 09:25:23AM +0900, Nick Hastings wrote:
> > Hi Salvatore,
> >
> > thanks for your help. However, I'm now not sure if I really have
> > identified the commit that causes my problems. I fear I may have made
> > one or more mistakes when setting "git bisect good". I had been under
> > the impression that the lock up would happen no more than a few tens of
> > minutes after booting, however it seems that sometimes it can take a few
> > hours to occur.
> >
> > So, I'm running the git bisect again and will be more careful before
> > marking "git bisect good". It could take a few days.
> >
> > Should this particular bug be closed?
>
> Thanks a lot for reporting back, you time put in into bisect is very
> appreciated and valued! No, no need to close this one, as the bug
> still persist. Just followup please once you have identified the
> culprit with the fresh bisect.
>
> Please do remove by then as well the moreinfo tag again (you can write
> a control message with tag -1 - moreinfo, so won't appear as bug
> needing information from reporter).
>
> Thank you!
>
> Regards,
> Salvatore
Bug#1036530: linux-signed-amd64: Hard lock up of system
Hi Salvatore,
thanks for your help. However, I'm now not sure if I really have
identified the commit that causes my problems. I fear I may have made
one or more mistakes when setting "git bisect good". I had been under
the impression that the lock up would happen no more than a few tens of
minutes after booting, however it seems that sometimes it can take a few
hours to occur.
So, I'm running the git bisect again and will be more careful before
marking "git bisect good". It could take a few days.
Should this particular bug be closed?
Thanks,
Nick.
* Salvatore Bonaccorso [230526 00:19]:
> Hi Nick,
>
> On Thu, May 25, 2023 at 08:23:15AM +0900, Nick Hastings wrote:
> > Hi,
> >
> > * Salvatore Bonaccorso [230524 19:26]:
> > >
> > > Given you were able to bisect it so far, can you try to isolate the
> > > commit from the merge commit causing it?
> >
> > I guess I can try. The commit message states:
> >
> > Merge: c77f54a9bcec a1cf1fd62ae7 562163595a91 018d6711c26e 6cc401be1648
> >
> > Is there a way extract out each of those?
>
> Th way i usuually get all commits from a merge request is
>
> git log --oneline $mergecommit^$mergecommit^2
>
> though here we have three merge commits, merged with one merge commit
> on top, so you would go down the merges of the acpi-properties,
> acpi-tables, acpi-x86 and acpi-soc branches. Those are those:
>
> * acpi-properties:
> ACPI: property: Silence missing-declarations warning in apple.c
>
> * acpi-tables:
> ACPI: HMAT: Drop unused dev_fmt() and redundant 'HMAT' prefix
> ACPI: tables: FPDT: Don't call acpi_os_map_memory() on invalid phys
> address
>
> * acpi-x86:
> ACPI: x86: Add a quirk for Dell Inspiron 14 2-in-1 for StorageD3Enable
>
> * acpi-soc:
> ACPI: LPSS: Deduplicate skipping device in acpi_lpss_create_device()
> ACPI: LPSS: Replace loop with first entry retrieval
>
> > > One remotely related might be "ACPI: x86: Add a quirk for Dell
> > > Inspiron 14 2-in-1 for StorageD3Enable".
> >
> > Manually looking at the diff with
> > git diff e996c7e01892ac18ec0db447294d4f591c325efe~
> > e996c7e01892ac18ec0db447294d4f591c325efe
> > I guess that means the following:
> >
> > --- a/drivers/acpi/x86/utils.c
> > +++ b/drivers/acpi/x86/utils.c
> > @@ -207,9 +207,26 @@ static const struct x86_cpu_id storage_d3_cpu_ids[] = {
> > {}
> > };
> >
> > +static const struct dmi_system_id force_storage_d3_dmi[] = {
> > + {
> > + /*
> > +* _ADR is ambiguous between GPP1.DEV0 and GPP1.NVME
> > +* but .NVME is needed to get StorageD3Enable node
> > +* https://bugzilla.kernel.org/show_bug.cgi?id=216440
> > +*/
> > + .matches = {
> > + DMI_MATCH(DMI_SYS_VENDOR, "Dell Inc."),
> > + DMI_MATCH(DMI_PRODUCT_NAME, "Inspiron 14 7425
> > 2-in-1"),
> > + }
> > + },
> > + {}
> > +};
> > +
> > bool force_storage_d3(void)
> > {
> > - return x86_match_cpu(storage_d3_cpu_ids);
> > + const struct dmi_system_id *dmi_id =
> > dmi_first_match(force_storage_d3_dmi);
> > +
> > + return dmi_id || x86_match_cpu(storage_d3_cpu_ids);
> > }
>
> That probably won't work actually as the code has been refactored
> substantiantly after the commit.
>
> In the ideal case we could confirm the quirk change is the responsable
> commit, so we can make upstream aware.
>
> Regards,
> Salvatore
Bug#1036530: linux-signed-amd64: Hard lock up of system
Hi,
* Salvatore Bonaccorso [230524 19:26]:
>
> Given you were able to bisect it so far, can you try to isolate the
> commit from the merge commit causing it?
I guess I can try. The commit message states:
Merge: c77f54a9bcec a1cf1fd62ae7 562163595a91 018d6711c26e 6cc401be1648
Is there a way extract out each of those?
> One remotely related might be "ACPI: x86: Add a quirk for Dell
> Inspiron 14 2-in-1 for StorageD3Enable".
Manually looking at the diff with
git diff e996c7e01892ac18ec0db447294d4f591c325efe~
e996c7e01892ac18ec0db447294d4f591c325efe
I guess that means the following:
--- a/drivers/acpi/x86/utils.c
+++ b/drivers/acpi/x86/utils.c
@@ -207,9 +207,26 @@ static const struct x86_cpu_id storage_d3_cpu_ids[] = {
{}
};
+static const struct dmi_system_id force_storage_d3_dmi[] = {
+ {
+ /*
+* _ADR is ambiguous between GPP1.DEV0 and GPP1.NVME
+* but .NVME is needed to get StorageD3Enable node
+* https://bugzilla.kernel.org/show_bug.cgi?id=216440
+*/
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "Dell Inc."),
+ DMI_MATCH(DMI_PRODUCT_NAME, "Inspiron 14 7425 2-in-1"),
+ }
+ },
+ {}
+};
+
bool force_storage_d3(void)
{
- return x86_match_cpu(storage_d3_cpu_ids);
+ const struct dmi_system_id *dmi_id =
dmi_first_match(force_storage_d3_dmi);
+
+ return dmi_id || x86_match_cpu(storage_d3_cpu_ids);
}
Thanks,
Nick.
Bug#1036530: linux-signed-amd64: Hard lock up of system
Source: linux-signed-amd64
Severity: important
Tags: upstream
X-Debbugs-Cc: nicholaschasti...@gmail.com
Dear Maintainer,
after upgrading from a 6.0.0 kernel to a 6.1.0 kernel I experienced
hard lockups on my Dell XPS 15 7590 a few minutes after each boot. On
more than one occasion I was on the console and was able to see the
error message. It was the same error on each occasion, and I reproduce
it here:
[ 58.729863] ACPI Error: Aborting method \_SB.PCI0.PGON due to previous error
(AE_AML_LOOP_TIMEOUT) (20220331/psparse-529)
[ 58.729904] ACPI Error: Aborting method \_SB.PCI0.PEG0.PG00._ON due to
previous error (AE_AML_LOOP_TIMEOUT) (20220331/psparse-529)
[ 60.083261] vfio-pci :01:00.0 Unable to change power state from D3cold
to D0, device inaccessible
N.B. the message on the console was recorded with at photograph and
then manually typed in, so it is possible that it may contain one or
more errors.
I ran git bisect as descirbed at
https://wiki.debian.org/DebianKernel/GitBisect which seems to have
found the bad commit. It is a merge commit that deals with acpi code.
However I don't see what may actually be causing this issue.
The commit is e996c7e01892ac18ec0db447294d4f591c325efe
Please find the report from git bisect below.
Regards,
Nick.
-- System Information:
Debian Release: 12.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.0.0-rc6-1-g018d6711c26e (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8),
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
% git bisect good
e996c7e01892ac18ec0db447294d4f591c325efe is the first bad commit
commit e996c7e01892ac18ec0db447294d4f591c325efe
Merge: c77f54a9bcec a1cf1fd62ae7 562163595a91 018d6711c26e 6cc401be1648
Author: Rafael J. Wysocki
Date: Fri Sep 30 20:52:39 2022 +0200
Merge branches 'acpi-properties', 'acpi-tables', 'acpi-x86' and 'acpi-soc'
Merge changes related to ACPI data-only tables handling and ACPI device
properties management, x86-specific ACPI code changes and ACPI SoC driver
changes for 6.1-rc1:
- Clean up the ACPI LPSS (Intel SoC) driver (Andy Shevchenko).
- Add a quirk for Dell Inspiron 14 2-in-1 for StorageD3Enable (Mario
Limonciello).
- Drop unused dev_fmt() and redundant 'HMAT' prefix from the HMAT
parsing code (Liu Shixin).
- Make ACPI FPDT parsing code avoid calling acpi_os_map_memory() on
invalid physical addresses (Hans de Goede).
- Silence missing-declarations warning related to Apple device
properties management (Lukas Wunner).
* acpi-properties:
ACPI: property: Silence missing-declarations warning in apple.c
* acpi-tables:
ACPI: HMAT: Drop unused dev_fmt() and redundant 'HMAT' prefix
ACPI: tables: FPDT: Don't call acpi_os_map_memory() on invalid phys
address
* acpi-x86:
ACPI: x86: Add a quirk for Dell Inspiron 14 2-in-1 for StorageD3Enable
* acpi-soc:
ACPI: LPSS: Deduplicate skipping device in acpi_lpss_create_device()
ACPI: LPSS: Replace loop with first entry retrieval
drivers/acpi/acpi_fpdt.c | 22 ++
drivers/acpi/acpi_lpss.c | 45 +
drivers/acpi/numa/hmat.c | 25 -
drivers/acpi/x86/apple.c | 1 +
drivers/acpi/x86/utils.c | 19 ++-
5 files changed, 74 insertions(+), 38 deletions(-)
[0 running job(s)] {history#6810} 2023-05-20 20:54:16
Bug#1032402: calcurse: New upstream since 2022-04-16
Package: calcurse Version: 4.6.0-2 Severity: normal X-Debbugs-Cc: nicholaschasti...@gmail.com Dear Maintainer, unstable contains calcurse 4.7.1-1, howver a new version, 4.8.0 of calcurse was released 11 months ago. Could the calcurse version in Debian please be updated? Thanks, Nick. -- System Information: Debian Release: 11.6 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable'), (100, 'bullseye-fasttrack'), (100, 'bullseye-backports-staging') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-0.deb11.2-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages calcurse depends on: ii libc6 2.31-13+deb11u5 ii libncursesw6 6.2+20201114-2 ii libtinfo6 6.2+20201114-2 ii python3 3.9.2-3 calcurse recommends no packages. calcurse suggests no packages. -- no debconf information
Bug#1012286: RFS: zig/0.9.1-1 [ITP] -- Programming language
* Bastian Germann [230113 18:05]: > Am 13.01.23 um 03:40 schrieb Nick Hastings: > > This debian/copyright file was originally produced by decopy and I > > adjusted it wherever I found problems. I hesitate to change things that > > I do not know to be wrong, at the risk of introducing errors simply to > > reduce the number of lines in the file. > > If you want this to be sponsored by me, please do so. I spent a couple of hours grinding through the LGPL-2.1 section of lib/libc/include and was able reduce the copyright file by about 760 lines. I was also able to save a few lines from the APSL-2 an GPL-2 sections. > I will not review a non-reviewable copyright file. I'm not clear on what constitutes a reviewable vs non-reviewable copyright file. If there are other specific parts of the copyright file that you think need more work please let me know.
Bug#1012286: RFS: zig/0.9.1-1 [ITP] -- Programming language
* Bastian Germann [230104 02:20]: > Control: tags -1 moreinfo > > Am 15.12.22 um 06:40 schrieb Nick Hastings: > > > d/copyright > > > === > > > Please use more wildcards so you do not have to list so many files. > > This is where it gets tricky for me. As I understand it the last match > > in d/copyright file is the one that applies. So for example, the block > > starting at line 253 specifies a LGPL-2.1+ license for a bunch of files > > under lib/libc/include/. Lines 253-270 explicitly list header files > > under lib/libc/include/aarch64-linux-gnu/bits/. So first thought is to > > just list them all as a glob lib/libc/include/aarch64-linux-gnu/bits/* > > However on closer inspection I see that there is a file in that > > directory that is not listed. Specifically > > lib/libc/include/aarch64-linux-gnu/bits/fcntl/endianness.h > > Inspecting this file and the others in the directory I see that > > explicitly listed files contain the LGPL-2.1+ text, but that > > endianness.h contains no license text. Thus endianness.h is actually > > Expat license and is covered in the block starting on line 10 "Files: > > lib/*". > > > > So if I change the explicit list of files under > > lib/libc/include/aarch64-linux-gnu/bits/ to a glob, I'll need to and > > anther block later to explicitly list endianness.h as Expat. > > Yes, you would use a glob for the LGPL files and add another block > specifically > for the Expat-licensed file after the LGPL block. Understood. However I do not feel confident that I can correctly make these changes by hand. The above is just one example where I found that using a glob would require an additional section/exception. There are likely many more. This debian/copyright file was originally produced by decopy and I adjusted it wherever I found problems. I hesitate to change things that I do not know to be wrong, at the risk of introducing errors simply to reduce the number of lines in the file.
Bug#1012286: RFS: zig/0.9.1-1 [ITP] -- Programming language
Hi Bastian,
* Bastian Germann [221219 06:22]:
> A quick note before I forget it: llvm-toolchain-13 is on its way out of
> Debian.
> Can we make this package use the unversioned (default, currently v14)
> llvm packages or v15?
The cmake setup is quite specific about needing v13 so changing it to
greater than v13 would be significant work. Instead I changed it from
v13 to v14. I was able to get it to configure, but the build failed.
make[3]: Leaving directory '/build/zig-0.9.1/obj-x86_64-linux-gnu'
[ 82%] Built target embedded_softfloat
/build/zig-0.9.1/src/zig_llvm-ar.cpp:139:1: error: 'LLVM_ATTRIBUTE_NORETURN'
does not name a type; did you mean 'LLVM_ATTRIBUTE_NODEBUG'?
139 | LLVM_ATTRIBUTE_NORETURN static void badUsage(Twine Error) {
| ^~~
| LLVM_ATTRIBUTE_NODEBUG
/build/zig-0.9.1/src/zig_llvm-ar.cpp:146:1: error: 'LLVM_ATTRIBUTE_NORETURN'
does not name a type; did you mean 'LLVM_ATTRIBUTE_NODEBUG'?
146 | LLVM_ATTRIBUTE_NORETURN static void fail(Twine Error) {
| ^~~
| LLVM_ATTRIBUTE_NODEBUG
I changed these LLVM_ATTRIBUTE_NORETURN to "[[ noreturn ]]" and then the
build failed soon after at:
make[3]: Leaving directory '/build/zig-0.9.1/obj-x86_64-linux-gnu'
[ 82%] Built target embedded_softfloat
/build/zig-0.9.1/src/zig_clang.cpp: In function 'void
ZigClang_detect_enum_TypeClass(clang::Type::TypeClass)':
/build/zig-0.9.1/src/zig_clang.cpp:297:27: error: 'DependentExtInt' is not a
member of 'clang::Type'
297 | case clang::Type::DependentExtInt:
| ^~~
/build/zig-0.9.1/src/zig_clang.cpp:318:27: error: 'ExtInt' is not a member of
'clang::Type'
318 | case clang::Type::ExtInt:
| ^~
So I think the short answer is: no, we can't use LLVM 14 or 15. I guess
it may be possible by patching the source but if that level of effort is
to be spent I think would be better spending it on getting Zig 0.10.0
(which depends on LLVM 15) to build. See
https://github.com/ziglang/zig/issues/13915
Cheers,
Nick.
Bug#1012286: RFS: zig/0.9.1-1 [ITP] -- Programming language
Hi, thought it may be a little while until I could dig into this but actually found the time today. So here's another quick update. * Nick Hastings [221216 13:15]: > Hi, > > quick update. > > * Nick Hastings [221215 14:40]: > > > * Bastian Germann [221215 08:57]: > > > > > Your package fails to build from scratch on amd64 with a test fail > > > (maybecaused by wrong pwd?): Yes, turns out to be wrong pwd. > > I don't know why that is. It works for me on amd64 on unstable > > (bullseye with backports). I do recall that someone on #mentors had > > issues building it using sbuild at some point. But at least 3 or 4 > > others did not: success was reported with both pbuilder and sbuild. > > I updated my unstable chroot and now build the fails in this way for me > too. I will investigate. I don't actually understand why this ever worked. As I now understand it dh_auto_test is run before dh_auto_install so I had no reason to expect that the binary would already be in debian/zig/usr/bin/zig. Updating this to the build time path fixed this (thanks to pabs and mjt in #debian-mentors). Now all but one of the test suites completes without error. An updated d/rules skips that test suite for now. I was able to build the package on x86_64 unstable with pbuilder. New package uploaded to both mentors and salsa. Cheers, Nick.
Bug#1012286: RFS: zig/0.9.1-1 [ITP] -- Programming language
Hi, quick update. * Nick Hastings [221215 14:40]: > * Bastian Germann [221215 08:57]: > > > Your package fails to build from scratch on amd64 with a test fail > > (maybecaused by wrong pwd?): > > > > [100%] Built target zig > > make[2]: Leaving directory '/home/bage/zig-0.9.1/obj-x86_64-linux-gnu' > > /usr/bin/cmake -E cmake_progress_start > > /home/bage/zig-0.9.1/obj-x86_64-linux-gnu/CMakeFiles 0 > > make[1]: Leaving directory '/home/bage/zig-0.9.1/obj-x86_64-linux-gnu' > >debian/rules override_dh_auto_test > > make[1]: Entering directory '/home/bage/zig-0.9.1' > > ./debian/zig/usr/bin/zig build test-fmt || exit 1; ./debian/zig/usr/bin/zig > > build test-behavior || exit 1; ./debian/zig/usr/bin/zig build > > test-compiler-rt || exit 1; ./debian/zig/usr/bin/zig build test-minilibc || > > exit 1; ./debian/zig/usr/bin/zig build test-compare-output || exit 1; > > ./debian/zig/usr/bin/zig build test-standalone || exit 1; > > ./debian/zig/usr/bin/zig build test-stack-traces || exit 1; > > ./debian/zig/usr/bin/zig build test-cli || exit 1; ./debian/zig/usr/bin/zig > > build test-asm-link || exit 1; ./debian/zig/usr/bin/zig build > > test-runtime-safety || exit 1; ./debian/zig/usr/bin/zig build > > test-translate-c || exit 1; ./debian/zig/usr/bin/zig build > > test-run-translated-c || exit 1; ./debian/zig/usr/bin/zig build test-std || > > exit 1; > > /bin/sh: 1: ./debian/zig/usr/bin/zig: not found > > make[1]: *** [debian/rules:16: override_dh_auto_test] Error 1 > > make[1]: Leaving directory '/home/bage/zig-0.9.1' > > make: *** [debian/rules:8: binary] Error 2 > > I don't know why that is. It works for me on amd64 on unstable > (bullseye with backports). I do recall that someone on #mentors had > issues building it using sbuild at some point. But at least 3 or 4 > others did not: success was reported with both pbuilder and sbuild. I updated my unstable chroot and now build the fails in this way for me too. I will investigate. Cheers, Nick.
Bug#1012286: RFS: zig/0.9.1-1 [ITP] -- Programming language
Hi Bastian, * Bastian Germann [221215 08:57]: > > Thanks for draft package. No problem, thanks for looking at it. > Let's go for 0.9 and when that is in we'll see what version can be > packaged next. Great. I've filed an issue about the problems I have building 0.10.0 on the Zig github but no response yet. I've also tried raising it twice in Zig IRC but no luck there either. > I have reopened Thr RFS bug. Please have that in copy during the discussion > so other sponsors can pick up if I am not repsonsive. Ok. > In general it is a good idea to put your package in a repo on Debian's salsa > git service because that has a CI system with a working setup to build > Debian packages. You would then have to put the files that are in your > repository's root into a debian directory. With the CI in place you will get > an idea of the quality of your package before posting it for review. I'd be more than happy to move it to salsa, but thought it was only available for DDs/DMs. I see now that that is incorrect. I registered an account and it seems to be pending approval. In the mean time I've made a debian directory in the repo and moved everything into it. > d/rules > === > You should leave the CMAKE_BUILD_TYPE default because this will build the > debug info that will then be extracted and stripped by default. Ok done. > Your package fails to build from scratch on amd64 with a test fail > (maybecaused by wrong pwd?): > > [100%] Built target zig > make[2]: Leaving directory '/home/bage/zig-0.9.1/obj-x86_64-linux-gnu' > /usr/bin/cmake -E cmake_progress_start > /home/bage/zig-0.9.1/obj-x86_64-linux-gnu/CMakeFiles 0 > make[1]: Leaving directory '/home/bage/zig-0.9.1/obj-x86_64-linux-gnu' >debian/rules override_dh_auto_test > make[1]: Entering directory '/home/bage/zig-0.9.1' > ./debian/zig/usr/bin/zig build test-fmt || exit 1; ./debian/zig/usr/bin/zig > build test-behavior || exit 1; ./debian/zig/usr/bin/zig build > test-compiler-rt || exit 1; ./debian/zig/usr/bin/zig build test-minilibc || > exit 1; ./debian/zig/usr/bin/zig build test-compare-output || exit 1; > ./debian/zig/usr/bin/zig build test-standalone || exit 1; > ./debian/zig/usr/bin/zig build test-stack-traces || exit 1; > ./debian/zig/usr/bin/zig build test-cli || exit 1; ./debian/zig/usr/bin/zig > build test-asm-link || exit 1; ./debian/zig/usr/bin/zig build > test-runtime-safety || exit 1; ./debian/zig/usr/bin/zig build > test-translate-c || exit 1; ./debian/zig/usr/bin/zig build > test-run-translated-c || exit 1; ./debian/zig/usr/bin/zig build test-std || > exit 1; > /bin/sh: 1: ./debian/zig/usr/bin/zig: not found > make[1]: *** [debian/rules:16: override_dh_auto_test] Error 1 > make[1]: Leaving directory '/home/bage/zig-0.9.1' > make: *** [debian/rules:8: binary] Error 2 I don't know why that is. It works for me on amd64 on unstable (bullseye with backports). I do recall that someone on #mentors had issues building it using sbuild at some point. But at least 3 or 4 others did not: success was reported with both pbuilder and sbuild. > d/watch > === > The watch file in your upload differs from the one in git. Please keep > them in sync. Hmm, at least in the main branch I think it is the same. Anyway I will be more careful to try to keep them in sync. Unfortunately I've not yet found a workflow for easily doing so, although I'm sure one (probably many) exists. > d/changelog > === > As long as the package is not sponsored, please only keep one version > (0.9.1-1) with the ITP closing entry. Your latest upload has 3 > versions. Ok. > d/copyright > === > Please use more wildcards so you do not have to list so many files. This is where it gets tricky for me. As I understand it the last match in d/copyright file is the one that applies. So for example, the block starting at line 253 specifies a LGPL-2.1+ license for a bunch of files under lib/libc/include/. Lines 253-270 explicitly list header files under lib/libc/include/aarch64-linux-gnu/bits/. So first thought is to just list them all as a glob lib/libc/include/aarch64-linux-gnu/bits/* However on closer inspection I see that there is a file in that directory that is not listed. Specifically lib/libc/include/aarch64-linux-gnu/bits/fcntl/endianness.h Inspecting this file and the others in the directory I see that explicitly listed files contain the LGPL-2.1+ text, but that endianness.h contains no license text. Thus endianness.h is actually Expat license and is covered in the block starting on line 10 "Files: lib/*". So if I change the explicit list of files under lib/libc/include/aarch64-linux-gnu/bits/ to a glob, I'll need to and anther block later to explicitly list endianness.h as Expat. Or is possible to not use a glob but instead use a regex that includes everything other than endianness.h? This is the sort of thing that I've been battling with the whole time with that d/copyright. > Your comment: > "COPYRIGHT file has a lont list of "Authors/contribut
Bug#995670: Updated Zig package uploaded to mentors.d.n
Hi, I did some more work on the copyright file, I think it may be ready to be reviewed. The package is now again at https://mentors.debian.net/package/zig/ I looked at updating to Zig 0.10.0 (released Oct 31). However, there are significant changes to the build between 0.9.1 and 0.10.0. Release notes are at https://ziglang.org/download/0.10.0/release-notes.html Zig 0.9.1 simply built a Zig compiler using the system provided compiler and libraries. This new release attempts to do a self hosted build. Details are at https://ziglang.org/download/0.10.0/release-notes.html#Self-Hosted-Compiler There are three stages to the 0.10.0 build. As I understand them, they are: 1. Build a zig compiler using system compilers and libraries (similar to 0.9.1). 2. Use the zig compiler from stage 1 to build a zig compiler from zig bundled libraries. 3. Repeat stage 2 using the zig compiler in produced in stage 2. Attempting this on Debian unstable (and also on bullseye with backported llvm-15) resulted in a failure at stage 2. It seems the build was not able to find a particular header file. There may be other problems too, but I did not investigate further. The release notes actually suggest waiting until Zig 0.10.1 or Zig 0.11.0 before upgrading from 0.9.1. It seems there will be even larger changes to the build system for Zig 0.11.0 so I'm not sure how much effort upstream will be put into fixing build related issues in 0.10.0. So, at this point I think it may be best to wait for the next release before attempting to update this package. Regards, Nick.
Bug#995670: Zig package status
Hi Bastian, * Bastian Germann [221204 09:02]: > > With the copyright in place I will sponsor it. Please notify me when you > think you have represented the applicable licenses completely and I will > review it. Many thanks for stepping forward for this. I started looking at the copyright again and have some questions. I'm not sure if the discussion should continue here in this bug report or if it is better to take it "offline" to be just with you as the potential sponsor. Thanks, Nick.
Bug#995670: Zig package status
Hi Bastian, * Bastian Germann [221203 02:45]: > The package got removed from mentors. Yes, no one sponsored it. > Nick, do you still have time to work on it? If not please make this a > RFP. I think I have time. Zig 0.10.0 was just released and I'm updating the package for it. Hope to upload to mentors soon. I think the biggest problem is still the copyright file. I tried using scancode but it seems that d/copyright output option is still a work in progress. Without a sponsor the package can't enter Debian so I don't want to spend the many tedious hours required to manually produce a correct copyright file if it will not be used. If/when there is indication that someone may sponsor this package I can look to put more time/effort into the d/copyright. Regards, Nick.
Bug#995670: Zig package status
Hi, * Henrique Almeida [220811 03:57]: > Hello, what's the current status of the Zig package for the Debian > official repository ? I've filed a request for a sponsor https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012286 Other than not have a sponsor, the two main issues I see are: 1. Some of the post build tests fail. Checking on zig issues and IRC it seems not so unusual for some tests to fail in certain situations. I'm not sure how worthwhile it is chasing down these issues before zig reaches 1.0.0. 2. The copyright file. With so much bundled source code from different projects it's quite challenging to write a correct copyright file. I've put considerable time into this, but it is horribly tedious and boring work. Without a sponsor to get zig into Debian I could just be completely wasting my time. Cheers, Nick.
Bug#1012286: RFS: zig/0.9.1-1 [ITP] -- Programming language
Hi,
quick progress report.
* Nick Hastings [220615 14:20]:
>
> * Adam Borowski [220603 23:34]:
> > On Fri, Jun 03, 2022 at 09:38:37AM +0900, Nick Hastings wrote:
> >
> > Worst news first: the copyright file requires a lot more work. I see for
> > example unlisted Khronos stuff (lib/libc/include/any-windows-any/{GL,KHR}/),
> > NTP (lib/libc/include/any-linux-any/linux/timex.h), Zope (mingw), ISC,
> > Apache, APSL, ... And the list of copyright holders is even more
> > incomplete. This is a big honking waste of time but it's
> > required... :(
>
> I actually already put quite a bit of effort into the copyright file,
> but it has been a very long time since I last worked on it.
>
> Taking a quick look now I wonder if maybe I have overlooked include
> directories, perhaps assuming that anything in there would be covered by
> src directories. Or maybe I'd just become burned out with it and wanted
> to move on!
>
> Anyway I think I'm ready to dive back in.
The initial copyright file was generated by debmake, have since used
decopy which seems to have found a lot of things that were previously
missed. I'm slowly grinding though it, adding and fixing things. It's
very time consuming, but I'm making progress.
https://github.com/NickHastings/zig-debian/blob/decopy/copyright
> > The package includes a bunch of tests, and with the likelihood of code not
> > handling a particular arch, glibc, etc, I'd say it's a must to run
> > them.
>
> Ok, I'll investigate running the tests.
I've added the tests to debian/rules. However two of them fail. See
https://github.com/NickHastings/zig-debian/blob/tests/rules
It's unclear to me if they are important. Have asked on zig irc, but so
far, no response. Will try to chase it up soon.
> > Not a strict requirement, but a man page would be greatly appreciated.
>
> Will put it on the todo list, but hopefully I can get upstream to do
> something on that front.
This is still sitting untouched at the bottom of the todo list.
Cheers,
Nick.
Bug#1012286: RFS: zig/0.9.1-1 [ITP] -- Programming language
Hi Adam,
wow, this is unfortunate - gmail flagged this as spam and I only just saw
it now. So please don't interpret my late reply as being from a lack of
motivation.
* Adam Borowski [220603 23:34]:
> On Fri, Jun 03, 2022 at 09:38:37AM +0900, Nick Hastings wrote:
> > * Package name: zig
> > * URL : https://github.com/ziglang/zig
> > * License : Expat, Apache-2, Apache-2 with LLVM exception,
> > CC0, BSD-2-Clause, and LGPL-2+
> > * Vcs : https://github.com/NickHastings/zig-debian
>
> > zig - Imperative, general-purpose, statically typed, system programming
> > language
>
> Hi!
> Worst news first: the copyright file requires a lot more work. I see for
> example unlisted Khronos stuff (lib/libc/include/any-windows-any/{GL,KHR}/),
> NTP (lib/libc/include/any-linux-any/linux/timex.h), Zope (mingw), ISC,
> Apache, APSL, ... And the list of copyright holders is even more
> incomplete. This is a big honking waste of time but it's
> required... :(
I actually already put quite a bit of effort into the copyright file,
but it has been a very long time since I last worked on it.
Taking a quick look now I wonder if maybe I have overlooked include
directories, perhaps assuming that anything in there would be covered by
src directories. Or maybe I'd just become burned out with it and wanted
to move on!
Anyway I think I'm ready to dive back in.
> The package includes a bunch of tests, and with the likelihood of code not
> handling a particular arch, glibc, etc, I'd say it's a must to run
> them.
Ok, I'll investigate running the tests.
> Not a strict requirement, but a man page would be greatly appreciated.
Will put it on the todo list, but hopefully I can get upstream to do
something on that front.
Thanks for taking interest in this package.
Cheers,
Nick.
Bug#1012286: RFS: zig/0.9.1-1 [ITP] -- Programming language
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "zig": * Package name: zig Version : 0.9.1-1 Upstream Author : Andrew Kelley * URL : https://github.com/ziglang/zig * License : Expat, Apache-2, Apache-2 with LLVM exception, CC0, BSD-2-Clause, and LGPL-2+ * Vcs : https://github.com/NickHastings/zig-debian Section : devel The source builds a single binary package: zig - Imperative, general-purpose, statically typed, system programming language To access further information about this package, please visit the following URL: https://mentors.debian.net/package/zig/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/z/zig/zig_0.9.1-1.dsc An ITP bug, #995670, has been filed. It can be seen at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995670 Regards, Nick Hastings.
Bug#995670: Another zig packaging effort
Hi Bastian, thanks for taking an interest in this and getting it moving along. * Bastian Germann [220603 05:47]: > Control: owner -1 Nick Hastings > > Okay then; Nick, please file a RFS on sponsorship-requests when you > have provided an upload with the changelog addition. I've updated the changelog and uploaded again to m.d.n. https://mentors.debian.net/package/zig/ I can file an RFS on the sponsorship-requests list, but I'm a slightly unsure because https://mentors.debian.net/sponsors/rfs-howto/ describes a different way to do this. It says to file a new bug against the sponsorship-requests pseudo-package. Can you please confirm which is the correct or best way to do this? Thanks, Nick.
Bug#1006593: ITP: river -- Dynamic tiling Wayland compositor
Package: wnpp Severity: wishlist Owner: Nick Hastings X-Debbugs-Cc: debian-de...@lists.debian.org, nicholaschasti...@gmail.com * Package name: river Version : 0.1.3 Upstream Author : Isaac Freund * URL : https://github.com/riverwm/river * License : GPL-3.0 Programming Lang: Zig Description : Dynamic tiling Wayland compositor This is the River, dynamic tiling Wayland compositor which includes a flexible runtime configuration. Debian currently seems to have no Wayland compositor that can perform as replacement for the dynamic tiling X11 window mangers like dwm, awesome, xmonad, etc. River is such a Wayland compositor. Although it is still under early development it is already extremely capable and stable. I have already created a package for river. River has one main blocking dependency, zig, for which an ITP exists. However, progress on that package seems to have stalled and as such I have also created a zig package. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995670 regarding zig. My river and zig packages can be found on mentors.d.n at https://mentors.debian.net/package/river/ and https://mentors.debian.net/package/zig/ I have been using river built with these packages on bullseye (after backporting some dependencies from testing/unstable) as my daily driver for almost two months. Note that a tiling Wayland compositor, sway, already exists in Debian. However, sway is a drop in replacement for i3 and as such provides a very different experience to the dynamic tiling scheme from river. As I understand it, there is no plan for sway to ever be extended to include this sort of functionality. River would uniquely fill a large gap in the existing Wayland compositor landscape in Debian.
Bug#1004836: foot: Incorrect location for zsh completions
Package: foot Version: 1.10.3-2~bpo11+1 Severity: normal X-Debbugs-Cc: nicholaschasti...@gmail.com Dear Maintainer, zsh in debian adds /usr/share/zsh/vendor-completions to the fpath but not /usr/share/zsh/site-functions. This foot package installs _foot and _footclient to /usr/share/zsh/site-functions. This means that these completions are not avaiable to users unless they modify their zpath. Please install these completions to /usr/share/zsh/vendor-completions instead of /usr/share/zsh/site-functions. Regards, Nick. *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: 11.2 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-11-amd64 (SMP w/16 CPU threads) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages foot depends on: ii foot-terminfo 1.10.3-2~bpo11+1 ii libc6 2.31-13+deb11u2 ii libfcft32.5.1-1~bpo11+1 ii libfontconfig1 2.13.1-4.2 ii libpixman-1-0 0.40.0-1 ii libwayland-client0 1.19.0-2~bpo11+1 ii libwayland-cursor0 1.19.0-2~bpo11+1 ii libxkbcommon0 1.0.3-2 foot recommends no packages. Versions of packages foot suggests: ii foot-themes 1.10.3-2~bpo11+1 -- no debconf information
Bug#995670: Another zig packaging effort
Hi, I just discovered this ITP bug report. I have also started working on making a zig Debian package. So far I've been able to generate a zig 0.9.0 package on bullseye after backporting llvm-13 from testing. I had not originally planned for this to be an official package for Debian, I just wanted a working zig on my system so that I could compile (and package) the river wayland compositor. I thought I should speak up in case I can be of some help with the official packaging efforts. You can find my package at https://github.com/NickHastings/zig-debian and https://mentors.debian.net/package/zig/ Regards, Nick.
Bug#611702: clipit: Typo in warning dialog
Package: clipit Version: 1.3.11-1 Severity: minor The "Save history" dialog includes the text: "If you copy passwords or other sensible data" Presumably that should read: "If you copy passwords or other sensitive data" -- System Information: Debian Release: 6.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages clipit depends on: ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib ii libglib2.0-0 2.24.2-1 The GLib library of C routines ii libgtk2.0-0 2.20.1-2 The GTK+ graphical user interface ii libx11-6 2:1.3.3-4 X11 client-side library clipit recommends no packages. clipit suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#593552: zathura: No config file documentation
Package: zathura Version: 0.0.8.1-1 Severity: normal The package does not contain any documentation describing syntax or variables/options that can be set in the config file. The man page does provides a URL to upstream, however the documentation there is incomplete. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.35-amd64-evo (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages zathura depends on: ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib ii libcairo2 1.8.10-5 The Cairo 2D vector graphics libra ii libglib2.0-0 2.24.1-1 The GLib library of C routines ii libgtk2.0-0 2.20.1-1 The GTK+ graphical user interface ii libpango1.0-0 1.28.1-1 Layout and rendering of internatio ii libpoppler-glib4 0.12.4-1.1 PDF rendering library (GLib-based zathura recommends no packages. Versions of packages zathura suggests: ii chromium-browser [w 5.0.375.125~r53311-1 Chromium browser ii cups-client 1.4.4-3 Common UNIX Printing System(tm) - ii iceweasel [www-brow 3.5.11-1 Web browser based on Firefox ii lynx-cur [www-brows 2.8.8dev.4-3 Text-mode WWW Browser with NLS sup ii poppler-data0.4.3-1 Encoding data for the poppler PDF ii w3m [www-browser] 0.5.2-9 WWW browsable pager with excellent -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#589058: awesome-extra: /usr/share/awesome/lib/vicious/ empty
Package: awesome-extra Version: 2010071401 Severity: important The /usr/share/awesome/lib/vicious/ directory is empty. Ie the vicious module is missing. This appears to just be a packaging error since there is no relevant comment in the changelog and AFIAK there is no plan to deprecate vicious. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash awesome-extra depends on no packages. Versions of packages awesome-extra recommends: ii awesome 3.4.6-1highly configurable, next generati awesome-extra suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#571610: mysql-server-5.0: wait_timeout in /etc/mysql/my.cnf ignored
Hi, well, I'm not sure what the problem was, but it seems I was doing something wrong: typo in the config file perhaps. This config option is now working for me. This bug can be closed. Sorry for the spam, Nick. signature.asc Description: Digital signature
Bug#571610: mysql-server-5.0: wait_timeout in /etc/mysql/my.cnf ignored
Package: mysql-server-5.0 Version: 5.0.84-1 Severity: normal Setting the variable wait_timout (and possibly others )in /etc/mysql/my.cnf appears to be ignored by the mysqld startup scripts. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.29-2-686-bigmem (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mysql-server-5.0 depends on: ii adduser 3.112add and remove users and groups ii debconf [debconf-2.0] 1.5.28 Debian configuration management sy ii libc6 2.10.2-5 Embedded GNU C Library: Shared lib ii libdbi-perl 1.609-1 Perl Database Interface (DBI) ii libgcc1 1:4.4.3-2GCC support library ii libmysqlclient15off 5.0.84-1 MySQL database client library ii libncurses5 5.7+20090803-2 shared libraries for terminal hand ii libreadline55.2-6GNU readline and history libraries ii libstdc++6 4.4.3-2 The GNU Standard C++ Library v3 ii libwrap07.6.q-18 Wietse Venema's TCP wrappers libra ii lsb-base3.2-23 Linux Standard Base 3.2 init scrip ii mysql-client-5.05.0.84-1 MySQL database client binaries ii mysql-common5.1.43-1 MySQL database common files (e.g. ii passwd 1:4.1.4.2-1 change and administer password and ii perl5.10.1-11Larry Wall's Practical Extraction ii psmisc 22.10-1 utilities that use the proc file s ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages mysql-server-5.0 recommends: ii bsd-mailx [mailx] 8.1.2-0.20090911cvs-2 simple mail user agent ii libhtml-template-p 2.9-1 HTML::Template : A module for usin ii mailx 1:20081101-2 Transitional package for mailx ren Versions of packages mysql-server-5.0 suggests: pn tinyca (no description available) -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#559126: roxterm: Full path required for Web Browser
Package: roxterm Version: 1.16.2-1 Severity: minor Since upgrading to roxterm 1.16.2-1, I have needed to specify the full path to the web browser in the profile configuration. eg. /usr/bin/iceweasel Previosly, just "iceweasel" worked. Cheers, Nick. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.29-2-686-bigmem (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages roxterm depends on: ii libc6 2.9-27 GNU C Library: Shared libraries ii libdbus-1-3 1.2.16-2 simple interprocess messaging syst ii libdbus-glib-1-2 0.82-2 simple interprocess messaging syst ii libglade2-0 1:2.6.4-1 library to load .glade files at ru ii libglib2.0-0 2.22.2-2 The GLib library of C routines ii libgtk2.0-0 2.18.3-1 The GTK+ graphical user interface ii libpango1.0-0 1.26.1-1 Layout and rendering of internatio ii libvte9 1:0.22.5-1 Terminal emulator widget for GTK+ roxterm recommends no packages. roxterm suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#536455: linux-source-2.6.30: Unable to set NIC hwaddress
Hi Ben,
* Ben Hutchings [090710 11:56]:
>
> The MAC change operation seems to have been accidentally left out of
> this driver in a change to the way net device operations are set up.
>
> Please try applying the following patch:
>
> --- a/drivers/net/wireless/orinoco/main.c
> +++ b/drivers/net/wireless/orinoco/main.c
> @@ -2523,6 +2523,8 @@ static const struct net_device_ops orinoco_netdev_ops =
> {
> .ndo_change_mtu = orinoco_change_mtu,
> .ndo_tx_timeout = orinoco_tx_timeout,
> .ndo_get_stats = orinoco_get_stats,
> + .ndo_set_mac_address= eth_mac_addr,
> + .ndo_validate_addr = eth_validate_addr,
> };
>
> struct net_device
> --- END ---
Nice one. I applied the patch and can confirm that it fixes the problem.
I can now change my mac address. Thanks for the very fast fix.
Cheers,
Nick.
signature.asc
Description: Digital signature
Bug#536455: linux-source-2.6.30: Unable to set NIC hwaddress
Package: linux-source-2.6.30 Version: 2.6.30-1 Severity: normal After upgrading my kernel from 2.6.29 to 2.6.30 I am unable to set the MAC address of my Prism 2.5 pci wireless NIC using the orinoco-pci driver. My interfaces file has a section like: iface eth1-foo inet dhcp wireless_key s:foobar wireless_essid barfoo wireless_mode managed hwaddress ether 00:01:02:03:04:05 Trying to bring up this interface results in the following: # ifscheme foo # ifup eth1 SIOCSIFHWADDR: Operation not supported Failed to bring up eth1-foo I have experienced this problem with the stock linux-image-2.6.30-1-486 package kerenel and with custom built images for the crusoe processor using the same config file as a 2.6.29 kernel (which has no problem setting the NIC hwaddress). Booting back into a 2.6.29 kernel allows me to set the hardware address, so this problem seems to really be kernel related and not caused by the userland networking tools. I have not yet investigated if this problem specifically relates to the orinoco driver or if it is a more general issue. Cheers, Nick. PS. The system information appended by reportbug below are for the system on which the custom kernels were built, *not* the machine in which the bug was observed. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.29-2-686-bigmem (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-source-2.6.30 depends on: ii binutils 2.19.1-1 The GNU assembler, linker and bina ii bzip2 1.0.5-2high-quality block-sorting file co Versions of packages linux-source-2.6.30 recommends: ii gcc 4:4.3.3-9 The GNU C compiler ii libc6-dev [libc-dev] 2.9-14 GNU C Library: Development Librari ii make 3.81-5 The GNU version of the "make" util Versions of packages linux-source-2.6.30 suggests: ii kernel-package12.014 A utility for building Linux kerne ii libncurses5-dev [ncurses- 5.7+20090523-1 developer's libraries and docs for ii libqt3-mt-dev 3:3.3.8b-5+b1 Qt development files (Threaded) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#477304: closed by "Felix Zielcke" <[EMAIL PROTECTED]> (Grub fails to find /boot/boot/grub/device.map)
grub-common ... Preparing to replace grub 0.97-36 (using grub_0.97-36_i386.deb) ... Unpacking replacement grub ... Setting up grub-common (1.96+20080704-2) ... Setting up grub (0.97-36) ... woody:/home/guest# update-grub Searching for GRUB installation directory ... found: /boot/boot/grub grub-probe: error: Cannot open `/boot/grub/device.map' If anyone is interested I can provide a snapshot of the image that I took just before upgrading to lenny. Anyway it seems that the bug is indeed reproducable and better news it is fixed in grub 0.97-41. Nick. > From: Nick Hastings <[EMAIL PROTECTED]> > To: Debian Bug Tracking System <[EMAIL PROTECTED]> > Subject: Grub fails to find /boot/boot/grub/device.map > Date: Tue, 22 Apr 2008 19:05:19 +0900 > X-Mailer: reportbug 3.39-0.1 > X-Spam-Status: No, score=-9.9 required=4.0 tests=BAYES_00,FOURLA,HAS_PACKAGE > autolearn=no version=3.1.4-bugs.debian.org_2005_01_02 > > Package: grub > Version: 0.97-36 > Severity: important > > > During the runing of the postinst script for a recent kernel upgrade, grub > failed to find `/boot/boot/grub/device.map'. Instead it complained: > > grub-probe: error: Cannot open `/boot/grub/device.map' > > On a system with a separate /boot partition (such as this one), I > would have thought that device.map should live in /boot/boot/grub > along with menu.lst and friends. Downgrading to grub 0.97-35 did not > help, but downgradingto grub 0.97-27 in stable did. > > Here is the output from the failed kernel postinst with grub 0.97-36 > (note that grub install dir is correctly found at /boot/boot/grub, but > that grub-probe looks for /boot/grub/device.map): > > % sudo aptitude install > Reading package lists... Done > Building dependency tree > Reading state information... Done > Reading extended state information > Initializing package states... Done > The following partially installed packages will be configured: > linux-image-2.6.24-1-686-bigmem > 0 packages upgraded, 0 newly installed, 0 to remove and 31 not upgraded. > Need to get 0B of archives. After unpacking 0B will be used. > Setting up linux-image-2.6.24-1-686-bigmem (2.6.24-6) ... > Running depmod. > Finding valid ramdisk creators. > Using mkinitramfs-kpkg to build the ramdisk. > Other valid candidates: mkinitramfs-kpkg mkinitrd.yaird > Not updating initrd symbolic links since we are being updated/reinstalled > (2.6.24-5 was configured last, according to dpkg) > Not updating image symbolic links since we are being updated/reinstalled > (2.6.24-5 was configured last, according to dpkg) > Running postinst hook script update-grub. > Searching for GRUB installation directory ... found: /boot/boot/grub > grub-probe: error: Cannot open `/boot/grub/device.map' > User postinst hook script [update-grub] exited with value 1 > dpkg: error processing linux-image-2.6.24-1-686-bigmem (--configure): > subprocess post-installation script returned error exit status 1 > Errors were encountered while processing: > linux-image-2.6.24-1-686-bigmem > E: Sub-process /usr/bin/dpkg returned an error code (1) > A package failed to install. Trying to recover: > Setting up linux-image-2.6.24-1-686-bigmem (2.6.24-6) ... > Running depmod. > Finding valid ramdisk creators. > Using mkinitramfs-kpkg to build the ramdisk. > Other valid candidates: mkinitramfs-kpkg mkinitrd.yaird > Not updating initrd symbolic links since we are being updated/reinstalled > (2.6.24-5 was configured last, according to dpkg) > Not updating image symbolic links since we are being updated/reinstalled > (2.6.24-5 was configured last, according to dpkg) > Running postinst hook script update-grub. > Searching for GRUB installation directory ... found: /boot/boot/grub > grub-probe: error: Cannot open `/boot/grub/device.map' > User postinst hook script [update-grub] exited with value 1 > dpkg: error processing linux-image-2.6.24-1-686-bigmem (--configure): > subprocess post-installation script returned error exit status 1 > Errors were encountered while processing: > linux-image-2.6.24-1-686-bigmem > Reading package lists... Done > Building dependency tree > Reading state information... Done > Reading extended state information > Initializing package states... Done > > > > > -- System Information: > Debian Release: lenny/sid > APT prefers unstable > APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, > 'experimental') > Architecture: i386 (i686) > > Kernel: Linux 2.6.24-1-686-bigmem (SMP w/4 CPU cores) > Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/bash > > Versions of packages grub depends on: > ii libc6 2.7-10 GNU C Library: Shared libraries > ii libncurses5 5.6+20080419-1 Shared libraries for terminal > hand > > grub recommends no packages. > > -- no debconf information > > -- Nicholas C. Hastings, Research Staff Aihara Group/Department of Physics, The University of Tokyo signature.asc Description: Digital signature
Bug#491989: tedia2sql: Include views for MySQL output
Package: tedia2sql
Version: 1.2.12-2
Severity: normal
Tags: patch
Since version 5.0 MySQL supports views. tedia2sql should be updated to
accommodate this. The following patch corrects the warnings and impletments
the 'drop view' which was previosly only output in a comment.
Cheers,
Nick.
--- /usr/bin/tedia2sql 2006-12-03 04:47:40.0 +0900
+++ tedia2sql 2008-07-23 10:55:58.0 +0900
@@ -1199,8 +1199,7 @@
}
if (($opt_t eq 'mysql' || $opt_t eq 'innodb') && $objectType eq 'view')
{
- print $createFileHandle &sqlComment("WARNING! tedia2sql
currently believes MySQL does not support") . "\n";
- print $createFileHandle &sqlComment("views, but you're trying
to create a view here. Expect errors.") . "\n";
+ print $createFileHandle &sqlComment("WARNING: MySQL versions
prior to 5.0 don't support views.") . "\n";
}
# the create part
@@ -2884,8 +2883,7 @@
} elsif ($opt_t eq 'mysql' || $opt_t eq 'innodb') {
my $toComment;
if ($objectType eq 'view') {
- $toComment = &sqlComment("MySQL doesn't support views
yet") . "\n";
- $toComment .= &sqlComment(" ");
+ $toComment = &sqlComment("WARNING: MySQL versions
prior to 5.0 don't support views.") . "\n";
} else {
$toComment = '';
}
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-1-686-bigmem (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages tedia2sql depends on:
ii libxml-dom-perl 1.44-1 Perl module for building DOM Level
ii perl 5.10.0-11.1 Larry Wall's Practical Extraction
tedia2sql recommends no packages.
Versions of packages tedia2sql suggests:
ii dia 0.96.1-7 Diagram editor
ii dia-gnome 0.96.1-7 Diagram editor (GNOME version)
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#477304: Grub fails to find /boot/boot/grub/device.map
Hi, * Felix Zielcke <[EMAIL PROTECTED]> [080723 05:04]: > Hello, > > From: "Nick Hastings" <[EMAIL PROTECTED]> > >> Seems to be no errors but it seems that /boot/boot/ is being completely >> ignored. Please see the results of the install, linux-image reconfigure >> and file listing under /boot below. > > I used grub-legacy long ago, and I think I never used it with a /boot > partition. But I did use grub2 with a seperate /boot partition. It > works fine with just /grub instead of /boot/grub Well, I was very suspicious that it had left my system in an unbootable state, with nothing in /usr/share/doc/grub-common to indicate how to make it bootable ... no README.Debian etc >> I think I will downgrade to the old grub > > Please don't, please try grub2 :) If you call grub-install then the > *.img and *.mod files get copied to /boot/grub/ which it needs. Ok done and it works: thanks for the new boot loader. Please note that I think it is vitally important to include a README.Debian file that includes at least the following instructions 1. grub-install "(hd0)" 2. update-grub It seems that if the above steps aren't taken the user will be left with an unbootable system. Should I file a bug report for this? Thanks again, Nick. signature.asc Description: Digital signature
Bug#477304: Debian bug #477304 Grub fails to find /boot/boot/grub/device.map
Hi,
* Felix Zielcke <[EMAIL PROTECTED]> [080720 21:27]:
> Is this still an issue? Can you please try it with grub-pc
> 1.96+20080704-2 currently in testing/unstable
Seems to be no errors but it seems that /boot/boot/ is being completely
ignored. Please see the results of the install, linux-image reconfigure
and file listing under /boot below.
$ sudo aptitude install grub-pc
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
The following NEW packages will be installed:
grub-pc
The following packages will be REMOVED:
grub{a}
0 packages upgraded, 1 newly installed, 1 to remove and 138 not
upgraded.
Need to get 1101kB of archives. After unpacking 2044kB will be used.
Do you want to continue? [Y/n/?]
Writing extended state information... Done
Get:1 http://hat.kek.jp lenny/main grub-pc 1.96+20080704-2 [1101kB]
Fetched 1101kB in 4s (255kB/s)
Preconfiguring packages ...
(Reading database ... 318733 files and directories currently installed.)
Removing grub ...
Processing triggers for man-db ...
Selecting previously deselected package grub-pc.
(Reading database ... 318685 files and directories currently installed.)
Unpacking grub-pc (from .../grub-pc_1.96+20080704-2_i386.deb) ...
Processing triggers for man-db ...
Setting up grub-pc (1.96+20080704-2) ...
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Writing extended state information... Done
$ sudo dpkg-reconfigure linux-image-2.6.24-1-686-bigmem
Running depmod.
Finding valid ramdisk creators.
Using mkinitramfs-kpkg to build the ramdisk.
Other valid candidates: mkinitramfs-kpkg mkinitrd.yaird
Running postinst hook script update-grub.
Updating /boot/grub/grub.cfg ...
Found linux image: /boot/vmlinuz-2.6.24-1-686-bigmem
Found initrd image: /boot/initrd.img-2.6.24-1-686-bigmem
Found memtest86+ image: /boot/memtest86+.bin
done
$ tree -Dt /boot
/boot
|-- [Jul 22 8:42] grub
| |-- [Jul 22 8:42] grub.cfg
| |-- [Jul 22 8:42] device.map
| |-- [Jul 22 8:41] ascii.pff
| -- [Jul 22 8:41] debian-blueish-wallpaper-640x480.png
|-- [Jul 22 8:42] initrd.img-2.6.24-1-686-bigmem
|-- [Jun 26 10:12] initrd.img-2.6.24-1-686-bigmem.bak
|-- [May 8 13:50] System.map-2.6.24-1-686-bigmem
|-- [May 8 13:50] config-2.6.24-1-686-bigmem
|-- [May 8 13:49] vmlinuz-2.6.24-1-686-bigmem
|-- [Apr 24 4:24] memtest86+.bin
|-- [Dec 16 2005] boot
| -- [Jul 22 8:48] grub
| |-- [Jun 17 16:41] menu.lst
| |-- [Jun 17 16:41] menu.lst~
| |-- [Apr 23 12:32] stage2
| |-- [Apr 23 12:32] default
| |-- [Apr 23 12:32] e2fs_stage1_5
| |-- [Apr 23 12:32] fat_stage1_5
| |-- [Apr 23 12:32] jfs_stage1_5
| |-- [Apr 23 12:32] minix_stage1_5
| |-- [Apr 23 12:32] reiserfs_stage1_5
| |-- [Apr 23 12:32] stage1
| |-- [Apr 23 12:32] xfs_stage1_5
| -- [Nov 28 2005] device.map
-- [Jan 21 2004] lost+found [error opening dir]
I think I will down grade to the old grub: I can currently afford the
time potentially needed to recover a possibly unbootable machine.
Cheers,
Nick.
signature.asc
Description: Digital signature
Bug#491267: tedia2sql: foreign key bug with mysql output
Package: tedia2sql
Version: 1.2.12-2
Severity: normal
Tags: patch
When using mysql output tedia2sql will produce an partly commented
line. It appears that perhaps this line was intended to be entirely
commented out, assuming that mysql cannot deal with this syntax.
Please find the patch below: perhaps it explains the situation best.
Cheers,
Nick.
--- /usr/bin/tedia2sql 2006-12-03 04:47:40.0 +0900
+++ tedia2sql 2008-07-18 09:27:31.0 +0900
@@ -2815,9 +2815,9 @@
$return .= $in . "foreign key ($keyColumns)" . $nl;
$return .= $in . "references $refTable ($refColumns)
$goCommand";
} elsif ($opt_t eq 'mysql' || $opt_t eq 'ingres') {
- $return = &sqlComment("alter table $className add constraint
$constraintName") . $nl;
- $return .= $in . "foreign key ($keyColumns) references" . $nl;
- $return .= $in . "$refTable ($refColumns) for $opt_t";
+ $return = "alter table $className add constraint
$constraintName" . $nl;
+ $return .= $in . "foreign key ($keyColumns) references" . $nl;
+ $return .= $in . "$refTable ($refColumns);";
}
return $return;
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-1-686-bigmem (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages tedia2sql depends on:
ii libxml-dom-perl 1.44-1 Perl module for building DOM Level
ii perl 5.10.0-11.1 Larry Wall's Practical Extraction
tedia2sql recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#490019: fatsort: Fails to determine if filesystem is mounted
Package: fatsort
Version: 0.9.8.2-1
Severity: important
After upgrading to version 0.9.8.2-1 fatsort is unable to confirm that
the filesystem is not mounted and so exits without sorting it.
---
% fatsort /dev/iriver
FATSort Utility 0.9.8.2 by Boris Leidner
check_mounted: Unable to get realpath!
sort_fs: Could not check if filesystem is mounted!
main: Failed to sort file system!
---
Additonal info that may (or may not) be of interest:
% lsusb | grep -i iriver
Bus 004 Device 028: ID 4102:1014 iRiver, Ltd. T20 series mp3/ogg vorbis player
(ums firmware)
% grep iriver /etc/udev/local.rules
BUS=="scsi", SYSFS{vendor}=="iriver", NAME{all_partitions}="iriver"
Downgrading to 0.9.7.1-1 solves the problem.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-1-686-bigmem (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages fatsort depends on:
ii libc6 2.7-12 GNU C Library: Shared libraries
fatsort recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#477304: Grub fails to find /boot/boot/grub/device.map
Package: grub Version: 0.97-36 Severity: important During the runing of the postinst script for a recent kernel upgrade, grub failed to find `/boot/boot/grub/device.map'. Instead it complained: grub-probe: error: Cannot open `/boot/grub/device.map' On a system with a separate /boot partition (such as this one), I would have thought that device.map should live in /boot/boot/grub along with menu.lst and friends. Downgrading to grub 0.97-35 did not help, but downgradingto grub 0.97-27 in stable did. Here is the output from the failed kernel postinst with grub 0.97-36 (note that grub install dir is correctly found at /boot/boot/grub, but that grub-probe looks for /boot/grub/device.map): % sudo aptitude install Reading package lists... Done Building dependency tree Reading state information... Done Reading extended state information Initializing package states... Done The following partially installed packages will be configured: linux-image-2.6.24-1-686-bigmem 0 packages upgraded, 0 newly installed, 0 to remove and 31 not upgraded. Need to get 0B of archives. After unpacking 0B will be used. Setting up linux-image-2.6.24-1-686-bigmem (2.6.24-6) ... Running depmod. Finding valid ramdisk creators. Using mkinitramfs-kpkg to build the ramdisk. Other valid candidates: mkinitramfs-kpkg mkinitrd.yaird Not updating initrd symbolic links since we are being updated/reinstalled (2.6.24-5 was configured last, according to dpkg) Not updating image symbolic links since we are being updated/reinstalled (2.6.24-5 was configured last, according to dpkg) Running postinst hook script update-grub. Searching for GRUB installation directory ... found: /boot/boot/grub grub-probe: error: Cannot open `/boot/grub/device.map' User postinst hook script [update-grub] exited with value 1 dpkg: error processing linux-image-2.6.24-1-686-bigmem (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: linux-image-2.6.24-1-686-bigmem E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up linux-image-2.6.24-1-686-bigmem (2.6.24-6) ... Running depmod. Finding valid ramdisk creators. Using mkinitramfs-kpkg to build the ramdisk. Other valid candidates: mkinitramfs-kpkg mkinitrd.yaird Not updating initrd symbolic links since we are being updated/reinstalled (2.6.24-5 was configured last, according to dpkg) Not updating image symbolic links since we are being updated/reinstalled (2.6.24-5 was configured last, according to dpkg) Running postinst hook script update-grub. Searching for GRUB installation directory ... found: /boot/boot/grub grub-probe: error: Cannot open `/boot/grub/device.map' User postinst hook script [update-grub] exited with value 1 dpkg: error processing linux-image-2.6.24-1-686-bigmem (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: linux-image-2.6.24-1-686-bigmem Reading package lists... Done Building dependency tree Reading state information... Done Reading extended state information Initializing package states... Done -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686-bigmem (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages grub depends on: ii libc6 2.7-10 GNU C Library: Shared libraries ii libncurses5 5.6+20080419-1 Shared libraries for terminal hand grub recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#444234: xserver-xorg-video-ati: Brightness buttons not working on notebook with Radeon Mobility M6 LY
Hi Brice, * Brice Goglin <[EMAIL PROTECTED]> [070928 04:41]: > Nick Hastings wrote: > > After upgrading from 1:6.6.3-2 to 1:6.6.193-3 "the hotkeys" for > > increase and decrease brightness on my notebook stopped working under > > X. On a normal console (eg vt1 - vt6 ) the hotkeys work fine. > > > > This behaviour exists both with and without: > > > > Option "BIOSHotkeys" > > > > in the Device section of my xorg.conf > > > > My notebook is a "Fujitsu FMV-BIBLIO LOOX T93C" which as indicated > > below has a "M6 LY" controller. > > > > Please note that the symptoms of this bug appear to be are idential to > > bug #433876 but for a different controller. Apparently bug #433876 was > > fixed between versions 1:6.6.3-2 and 1:6.6.193-3 so I wonder if maybe > > this fix is resoponsible for the breakage with my "M6 LY". > > I guess you upgraded xserver-xorg-core from 1.3 to 1.4 at the same time. Correct. > So it's not completely clear that the problem is in > xserver-xorg-video-ati. To check that, could you try the package that I > rebuilt at: > http://people.debian.org/~bgoglin/ati-rebuilds/6.6.3-Xserver1.4/ > It's the old 6.6.3 for the current xserver-xorg-core 1.4 in unstable. I installed it and the brightness hot keys started working again. So it seems the problem really was in the new video driver, not the new X. > Then, could you try xserver-xorg-video-ati 1:6.7.194-1 currently in > experimental? The 6.6.x branch is dead now, all the fixes are made in > the 6.7.x branch. I installed this too and it also returns the function of the brightness hot keys. So it seems whatever problems were introduced with the 6.7.193 driver have now been fixed. Thanks! Cheers, Nick. -- Nicholas C. Hastings, Research Staff Aihara Group/Department of Physics, The University of Tokyo signature.asc Description: Digital signature
Bug#444234: xserver-xorg-video-ati: Brightness buttons not working on notebook with Radeon Mobility M6 LY
Package: xserver-xorg-video-ati Version: 1:6.6.193-3 Severity: normal Hi, After upgrading from 1:6.6.3-2 to 1:6.6.193-3 "the hotkeys" for increase and decrease brightness on my notebook stopped working under X. On a normal console (eg vt1 - vt6 ) the hotkeys work fine. This behaviour exists both with and without: Option "BIOSHotkeys" in the Device section of my xorg.conf My notebook is a "Fujitsu FMV-BIBLIO LOOX T93C" which as indicated below has a "M6 LY" controller. Please note that the symptoms of this bug appear to be are idential to bug #433876 but for a different controller. Apparently bug #433876 was fixed between versions 1:6.6.3-2 and 1:6.6.193-3 so I wonder if maybe this fix is resoponsible for the breakage with my "M6 LY". Cheers, Nick. -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /etc/X11/X target unchanged from checksum in /var/lib/x11/X.md5sum. X server symlink status: lrwxrwxrwx 1 root root 13 2006-04-25 16:48 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1669528 2007-09-17 03:56 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 00:14.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LY /etc/X11/xorg.conf does not match checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: lrwxrwxrwx 1 root root 18 2007-01-31 09:47 /etc/X11/xorg.conf -> xorg.conf.20070115 Contents of /etc/X11/xorg.conf: ## BEGIN DEBCONF SECTION # XF86Config-4 (XFree86 server configuration file) generated by dexconf, the # Debian X Configuration tool, using values from the debconf database. # # Edit this file with caution, and see the XF86Config-4 manual page. # (Type "man XF86Config-4" at the shell prompt.) # # If you want your changes to this file preserved by dexconf, only make changes # before the "### BEGIN DEBCONF SECTION" line above, and/or after the # "### END DEBCONF SECTION" line below. # # To change things within the debconf section, run the command: # dpkg-reconfigure xserver-xfree86 # as root. Also see "How do I add custom sections to a dexconf-generated # XF86Config or XF86Config-4 file?" in /usr/share/doc/xfree86-common/FAQ.gz. ### END DEBCONF SECTION Section "Files" FontPath"unix/:7100"# local font server # if the local font server has problems, we can fall back on these FontPath"/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" FontPath"/usr/share/fonts/X11/misc" FontPath"/usr/share/fonts/X11/cyrillic" FontPath"/usr/share/fonts/X11/100dpi/:unscaled" FontPath"/usr/share/fonts/X11/75dpi/:unscaled" FontPath"/usr/share/fonts/X11/Type1" FontPath"/usr/share/fonts/X11/CID" FontPath"/usr/share/fonts/X11/100dpi" FontPath"/usr/share/fonts/X11/75dpi" FontPath"/usr/share/fonts/X11/misc" FontPath"/usr/lib/X11/fonts/misc" FontPath"/usr/share/fonts/X11/cyrillic" FontPath"/usr/lib/X11/fonts/cyrillic" FontPath"/usr/lib/X11/fonts/75dpi/:unscaled" FontPath"/usr/lib/X11/fonts/100dpi/:unscaled" FontPath"/usr/lib/X11/fonts/Speedo" FontPath"/usr/share/fonts/X11/75dpi" FontPath"/usr/lib/X11/fonts/75dpi" FontPath"/usr/share/fonts/X11/100dpi" FontPath"/usr/lib/X11/fonts/100dpi" FontPath"/usr/share/fonts/X11/CID" FontPath"/usr/lib/X11/fonts/CID" FontPath"/usr/share/fonts/X11/Type1" FontPath"/usr/lib/X11/fonts/Type1" # ModulePath "/usr/X11R6/lib/modules-dri-trunk" # ModulePath "/usr/X11R6/lib/modules" EndSection Section "Module" # Don't load it explicitly ... Bug#362121 # Load"GLcore" Load"dri" Load"glx" # Load"bitmap" Load"dbe" Load"ddc" Load"extmod" Load"freetype" Load"int10" Load"record" # Load"speedo" Load"type1" Load"vbe" EndSection Section "InputDevice" Identifier "Generic Keyboard" # Driver "keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xfree86" Option "XkbModel" "jp106" Option "XkbLayout" "jp" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/input/mice" Option "Protocol" "ExplorerPS/2" # Option "Protocol" "ImPS/2" Option "Emulate3Buttons" "true" Option "Buttons"
Bug#440601: iso-codes: Spelling eror for JP-07 name
Package: iso-codes Version: 1.4-1 Severity: normal The Japanese prefecture name for code JP-07 is given as "Fukusima". This is usually written "Fukushima". See for example: www.pref.fukushima.jp/index_e.htm Cheers, Nick. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.22-1-686 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#429780: RFP: vec2web -- Convert DXF format drawings to various image formats.
Package: wnpp Severity: wishlist * Package name: vec2web Version : 2.0.4-7 Upstream Author : Andrew Mustun <[EMAIL PROTECTED]> * URL : http://www.qcad.org/vec2web_downloads.html * License : GPL V2 Programming Lang: C++ Description : Convert DXF format drawings to various image formats. (Include the long description here.) Commandline tool to convert DXF format drawings to various image formats, including bpm, png, jpeg, ppm, xbm, xpm, PostScript and dxml. Upstream: -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.21-1-686 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#429766: bash: [completion] support new aptitude actions safe-upgrade and full-upgrade
Package: bash Version: 3.1dfsg-8 Severity: minor As of version 0.4.5.1 aptitude has added the new actions "safe-upgrade" and "full-upgrade" which are synonyms for "upgrade" (now apparently deprecated) and "dist-upgrade" respectively. Please add these new actions to the aptitude section of /etc/bash_completion. Cheers, Nick. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.21-1-686 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages bash depends on: ii base-files4.0.0 Debian base system miscellaneous f ii debianutils 2.21 Miscellaneous utilities specific t ii libc6 2.5-11 GNU C Library: Shared libraries ii libncurses5 5.6-3 Shared libraries for terminal hand bash recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#355838: mairix: Old documentation - please update
Package: mairix Version: 0.17-2 Severity: minor This version of mairix supports gzipped and bzipped mboxs. The documentation in the package does not mention this. The upstream documentation does. Please update the docs. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14-1-686-smp Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Versions of packages mairix depends on: ii libc6 2.3.6-3GNU C Library: Shared libraries an ii zlib1g1:1.2.3-10 compression library - runtime mairix recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#329596: gnome-screenshot: one head blank with xinerama
Package: gnome-utils Version: 2.10.1-3 Severity: normal When using gnome-screenshot (either from the menu, pannel or command line), with a dual head xinerama machine, the resulting png file only shows the contents of the left head. Where the image for the right head should be, a transparent rectangle is shown. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-686-smp Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Versions of packages gnome-utils depends on: ii e2fslibs 1.38-2 ext2 filesystem libraries ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libatk1.0-0 1.10.3-1 The ATK accessibility toolkit ii libbonobo2-0 2.10.1-1 Bonobo CORBA interfaces library ii libbonoboui2-02.10.1-1 The Bonobo UI library ii libc6 2.3.5-6GNU C Library: Shared libraries an ii libgconf2-4 2.10.1-2 GNOME configuration database syste ii libglade2-0 1:2.5.1-2 library to load .glade files at ru ii libglib2.0-0 2.8.0-1The GLib library of C routines ii libgnome-desktop-22.10.2-1 Utility library for loading .deskt ii libgnome2-0 2.10.1-1 The GNOME 2 library - runtime file ii libgnomecanvas2-0 2.10.2-2 A powerful object-oriented display ii libgnomeprint2.2-02.10.3-3 The GNOME 2.2 print architecture - ii libgnomeprintui2.2-0 2.10.2-2 GNOME 2.2 print architecture User ii libgnomeui-0 2.10.1-1 The GNOME 2 libraries (User Interf ii libgnomevfs2-02.10.1-5 The GNOME virtual file-system libr ii libgtk2.0-0 2.6.10-1 The GTK+ graphical user interface ii libice6 6.8.2.dfsg.1-7 Inter-Client Exchange library ii liborbit2 1:2.12.2-3 libraries for ORBit2 - a CORBA ORB ii libpanel-applet2-02.10.2-1 library for GNOME 2 panel applets ii libpango1.0-0 1.8.2-2Layout and rendering of internatio ii libpopt0 1.7-5 lib for parsing cmdline parameters ii libsm66.8.2.dfsg.1-7 X Window System Session Management ii libstartup-notification0 0.8-1 library for program launch feedbac ii libx11-6 6.8.2.dfsg.1-7 X Window System protocol client li ii libxext6 6.8.2.dfsg.1-7 X Window System miscellaneous exte ii libxml2 2.6.22-1 GNOME XML library ii scrollkeeper 0.3.14-10 A free electronic cataloging syste ii xlibs 6.8.2.dfsg.1-7 X Window System client libraries m ii zlib1g1:1.2.3-4 compression library - runtime Versions of packages gnome-utils recommends: ii gksu 1.3.4-1graphical frontend to su -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#302131: ~/.skippyrc not loaded
Package: skippy Version: 0.5.0-2 Severity: important After copying /etc/X11/skippy/skippyrc to ~/.skippyrc skippy fails to load the ~/.skippyrc file. At start up the following warning is give: "WARNING: $HOME not set, not loading config." However the $HOME environment variable *is* set. Nick. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.10-1-686-smp Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Versions of packages skippy depends on: ii libc62.3.2.ds1-20GNU C Library: Shared libraries an ii libfontconfig1 2.3.1-2 generic font configuration library ii libfreetype6 2.1.7-2.3 FreeType 2 font engine, shared lib ii libimlib21.2.0-2.2 powerful image loading and renderi ii libx11-6 4.3.0.dfsg.1-12.0.1 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-12.0.1 X Window System miscellaneous exte ii libxft2 2.1.2-6 FreeType-based font drawing librar ii libxrender1 0.8.3-7 X Rendering Extension client libra ii xlibs4.3.0.dfsg.1-12 X Keyboard Extension (XKB) configu ii zlib1g 1:1.2.2-4 compression library - runtime -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
