o curl recently changed. Upstream CMake has been fixed:
* https://gitlab.kitware.com/cmake/cmake/-/merge_requests/10449
The fix is in the 4.0.0 release and will be in 3.31.7 once released.
-Brad
ntal output from the toolchain.
I don't think the warning itself is a problem for binaries inside the
test suite.
I've opened an upstream CMake merge request to filter out that output:
* https://gitlab.kitware.com/cmake/cmake/-/merge_requests/10398
-Brad
has been updated
without actually modifying or patching the package's source. In cases
that no other changes to the CMake code are needed, packaging can
proceed.
-Brad
ibility with CMake < 3.10 will be removed from a future version of
> CMake.
lfortran's `examples/project1/CMakeLists.txt` needs to be updated
to set policies to at least CMake 3.10. Other examples probably
need similar updates.
-Brad
Make 3.31 introduced support for LFortran.
We now have upstream issues in lfortran and CMake:
* https://github.com/lfortran/lfortran/issues/5944
* https://gitlab.kitware.com/cmake/cmake/-/issues/26597
-Brad
On Fri, Nov 22, 2024 at 12:29 PM Brad King wrote:
> there is a bug in ParaView's CMake code
I've posted a patch to the ParaView issue:
* https://gitlab.kitware.com/paraview/paraview/-/issues/22806#note_1596824
Further discussion is needed there to select a final change
for upst
Although this was exposed by a change to CMake, whose compatibility
concerns can be discussed on the CMake side, there is a bug in
ParaView's CMake code. I've opened an upstream issue:
* https://gitlab.kitware.com/paraview/paraview/-/issues/22806
-Brad
CMake side to discuss it:
* https://gitlab.kitware.com/cmake/cmake/-/issues/26467
-Brad
caller of `find_package(ZLIB)`. The cache should have
entries corresponding to individual zlib artifacts, such as
`ZLIB_INCLUDE_DIR` and `ZLIB_LIBRARY_RELEASE`
-Brad
r will
occur during its compilation instead.
-Brad
dependency on content of `qt6-declarative-private-dev`, so why
not express that dependency in the `qt6-declarative-dev` package?
-Brad
On Wed, Nov 13, 2024 at 11:38 AM Brad King wrote:
> > If parses fine with 3.30.5 and fails with 3.31.0.
> I can reproduce the problem locally. I'll track it down.
The change in behavior is due to CMake 3.31 fixing this bug:
* https://gitlab.kitware.com/cmake/cmake/-/issues/25
On Wed, Nov 13, 2024 at 11:28 AM Hefee wrote:
> But if I do (with an empty test.qml):
> ...
> If parses fine with 3.30.5 and fails with 3.31.0.
Thanks! With that I can reproduce the problem locally.
I'll track it down.
-Brad
se has changed
behavior that leads to this symptom.
-Brad
troduced in curl 8.9.
CMake 3.30.2 will update the test with the following MR:
* https://gitlab.kitware.com/cmake/cmake/-/merge_requests/9690
-Brad
Package: wnpp
Severity: wishlist
Owner: Brad Geltz
X-Debbugs-Cc: debian-de...@lists.debian.org,christopher.m.cantal...@intel.com
* Package name: geopm-service
Version : 3.0.0
Upstream Author : Intel
* URL : https://github.com/geopm/geopm
* License : BSD-3
Package: fonts-b612
Version: 1.008-3
Severity: important
X-Debbugs-Cc: brad.m.s...@gmail.com
Dear Maintainer,
After installing the package, the regular font style is italizised.
There is no regular font style available.
If I install the fonts manually from upstream it functions correctly.
--
teps
on private implementation details of CMake's FindEXPAT. In CMake
3.27, some of those implementation details changed:
* https://gitlab.kitware.com/cmake/cmake/-/merge_requests/8225
VTK's copy needs to be updated to account for them.
-Brad
;
TAB_DEFAULT = 8;
USE_TABS = 0;
Tab_Always_Inserts_Tab = 0;
custom_variable ("Tab_Stops", [1:40] * 2 + 1);
define global_mode_hook (hook_name)
{
local_setkey ("tab_to_tab_stop", "\t");
}
On Thu, Aug 24, 2023 at 2:05 AM Rafael Laboissière
wrote:
> Control: tags -1 + u
Package: jed
Version: 1:0.99.20~pre.178+dfsg-6
I have been using jed for a very long time, and this current release is now
inserting tab characters when an automatic indent is done (C mode). This
wasn't the case before.
I have USE_TABS=0 and TAB=0. The tab key works as I want it to, inserting
On Fri, Jul 21, 2023 at 2:37 PM Brad King wrote:
> The behavior change came from this CMake merge request:
> * https://gitlab.kitware.com/cmake/cmake/-/merge_requests/8538
> because the distutils variant is deprecated.
This is now under discussion in an upstream CMake issue:
nvironment resolves this locally.
-Brad
I can confirm that 'odd' placement happens as a result of this (all
emulators are placed in 'Lost & Found' in KDE/Plasma.
A little surprised that this seems to have been forgotten, despite there
being a trivial fix.
--
Regards _ "Valid sig separator is {dash}{dash}{space}"
/ )
UNSUBSCRIBE
E-MAIL Change Notice: My E-Mail address has changed to
bbas...@eventidecommunications.com
Brad B.
Eventide Inc.
bbas...@eventidecommunications.com
Tel: 201-641-1200 X 2590
-Original Message-
From: Ansgar
Sent: Wednesday, February 1, 2023 2:54 PM
To: IOhannes m zmölnig
Package: kwin-x11
Version: 4:5.26.4-1+b1
Followup-For: Bug #1017613
I think I have this bug. If true, it's still present. I'm on mesa 22.3.3-1. I
upgraded this system on the 7th and started having the issue.
My entire desktop freezes. Seconds on the clock stops. My mouse cursor still
moves but
FI is necessary to make use of those improvements.
More information:
https://docs.kernel.org/x86/intel-hfi.html
Thanks for your work!
-Brad
-- System Information:
Debian Release: 11.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-secur
Package: apache2
Version: 2.4.54-2
Severity: important
X-Debbugs-Cc: debian-bu...@l8r.net
Dear Maintainer,
A single apache2 thread was hit by the linux kernel OOM killer, and was killed.
Systemd "helpfully" decided to then halt apache2 completely.
As per this bug report:
https://bugzilla.re
On Wed, 27 Jul 2022 14:59:50 -0300
Lisandro Damián Nicanor Pérez Meyer wrote:
Hello Lisandro,
>I definitely can't reproduce the issue. Sounds like your system might
>have been upgraded and you keep your session opened. Please try at
That might have been part of the problem, yes. Although it's
Package: choqok
Version: 1.7.0-1
Severity: important
X-Debbugs-Cc: b...@fineby.me.uk
Dear Maintainer,
Start Choqok as normal (click on menu item), program starts, but never
completes initialising and continues
to display startup banner. I discovered the error-
kf.config.core: "\"repeatedDateTim
Can confirm this bug here, and an updated patch fixes this.
See:
https://bugzilla.redhat.com/show_bug.cgi?id=2090926
And:
https://github.com/logrotate/logrotate/commit/31cf1099ab8514dfcae5a980bc77352edd5292f8
Suggest at the very least, this is updated in Debian for the next point
release.
cause any negative impact and will only potentially improve
the security of applications in Debian.
Thanks,
Brad
Virginia Tech
Package: nodejs
Version: 12.20.2~dfsg-2
Version 12.21.0 is available which fixes the mentioned CVEs, see
https://nodejs.org/en/blog/vulnerability/february-2021-security-releases/
+1 /etc/letsencrypt/archive/nrgcoin.org/{fullchain,chain}{5,6}.pem
Thanks,
Brad Warren
Package: needrestart
Version: 3.4-5
Severity: normal
buster's behaviour, in terms of ENV setup differs, when one performs 'su
-' versus 'su root'.
Due to this, 'sbin' paths are not in a 'su root' $PATH. This means that
this happens, when one does an apt-get upgrade as 'su root':
Restarting se
`
$ grep -r _GLIBCXX_USE_FLOAT128 /usr/include/c++/9
/usr/include/c++/9/type_traits:#if !defined(__STRICT_ANSI__) &&
defined(_GLIBCXX_USE_FLOAT128) && !defined(__CUDACC__)
/usr/include/c++/9/bits/std_abs.h:#if !defined(__STRICT_ANSI__) &&
defined(_GLIBCXX_USE_FLOAT128) && !defined(__CUDACC__)
```
Thanks,
-Brad
Package: bugs.debian.org
Severity: normal
/etc/init.d/checkfs.sh is failing on boot and stopping the boot
process.
/etc/init.d/checkfs.sh fails when trying to check a non-existent
filesystem. Apparently it is trying to run a fsck on a filesystem that was
removed.
As I recall, it fails even when
-transport, I'm reassigning this to cmake.
This certainly seems like the long term solution.
This has been reported to CMake upstream:
* PkgConfig chokes with `-isystem` with pkg-config 0.29.2
https://gitlab.kitware.com/cmake/cmake/-/issues/20652
-Brad
Should be fixed in version 2.18 that I just uploaded upstream.
I also went ahead and removed the auto-dating of the manpage upstream,
as I recall that has been a problem for some of my other programs that
are packaged in Debian.
On Sat, 7 Mar 2020 08:30:07 -0500 sixerjman wrote:
> Has a problem been opened with HPLIP upstream? If so is there a link
> to the issue page?
Yes. Reported just prior to message #56.
Direct link
https://bugs.launchpad.net/hplip/+bug/1866291
--
Regards _
/ ) "The blindin
On Fri, 6 Mar 2020 19:08:33 +
Brian Potkin wrote:
Hello Brian,
>An upstream issue I would think.
That's the thinking at Arch Linux, too. They've added a 'report
upstream' comment, IIRC.
Again, thanks for your time.
--
Regards _
/ ) "The blindingly obvious is
The same problem seems to have arisen in Arch Linux;
https://bugs.archlinux.org/task/65697
Thanks to Curt on D-U for bringing that report to my attention.
--
Regards _
/ ) "The blindingly obvious is
/ _)radnever immediately apparent"
What the hell has this
On Thu, 5 Mar 2020 21:01:04 +
Brian wrote:
Hello Brian,
>It is not of very much use I'm afraid, Brad. It is devoid of detail. For
>example, it doesn't refer to what filters are used. I have no idea what
>is happenning.
I tried again, with log level set to debug2.
On Thu, 5 Mar 2020 19:23:52 +
Brian wrote:
Hello Brian,
>Brad, we did not use all the tools we have at our disposal. Read
> https://wiki.debian.org/CUPSDebugging#The_CUPS_Error_Log
>and get an idea of where we are going. Now
Attached is the compressed error log. A search
Package: hplip
Version: 3.19.12+dfsg0-4
Severity: important
Dear Maintainer,
Running Debian Testing.
After upgrading to v3.20.2 of hplip, my system could no longer print anything.
Print jobs were being sent
to the printer (display panel illuminated to indicate something was
communicating with th
Source: firewalld
Severity: normal
Dear Maintainer,
The debian wiki notes that debian is moving from iptables to nftables, and the
nftables page suggests installing this package. So I did. Unfortunately, I
did so via an ssh connection, as the computer in question is a headless router.
As so
Package: virt-manager
Version: 1:2.2.1-2
Severity: normal
virt-manager crashes on me quite often. It's been doing this for the last year
or so, but never before then. I think it was when I first upgraded to 2.0.0,
but not sure.
Today I upgraded from 1:2.0.0-3 to 1:2.2.1-2 to see if it was still
enough
headaches about —dry-run breaking from those initially creating or modifying
their setup that it’s worth releasing early.
Best,
Brad
[1] https://letsencrypt.org/docs/staging-environment/
[2] https://certbot.eff.org/lets-encrypt/debianstretch-other
> On Oct 25, 2019, at 10:18 AM, Ada
Package: coreutils
Version: 8.30-3
Severity: minor
ls adds a space at the start of some output. Seems to only happen when extra
quoting is in the output:
root@hmm:/tmp/oo# ls
a b 'sd '
root@hmm:/tmp/oo# rm sd\
root@hmm:/tmp/oo# ls
a b
root@hmm:/tmp/oo# touch c
root@hmm:/tmp/oo# ls
a b
Any updates on this?
Looking at server logs, I expect ~145K+ unique installations to be affected by
this problem if it doesn’t get fixed.
Package: python3-acme
Version: 0.28.0-1~deb9u1
The python*-acme packages will no longer work with Let’s Encrypt’s “ACMEv2”
endpoint which is their RFC 8555 compliant endpoint starting November 1st. See
https://community.letsencrypt.org/t/acme-v2-scheduled-deprecation-of-unauthenticated-resource-
Attached is a snapshot of the banner, as it appears on all versions of
Firefox I use that have disabled add-ons.
This is on debian stable, 60.6.1esr-1~deb9u1.
Are you running this version? Do you have add-ons installed?
If so, you should probably submit a separate bug, either to mozilla or
her
> installing the STUDIES "hotfix" from Mozilla by hand on each one is not
> feasible.
Not to mention, this requires that other features of Firefox's 'phone
home' framework are turned on, which 'studies' uses. For example, in the
GUI, the 'studies' option is under:
"Allow Firefox to send techn
While I agree an unknown disabling of plugins, not just noscript (there
are others like noscript) is a security concern...
There is a big, yellow banner that appears and stays at the top of your
browser, informing you if any plugins/add-ons are disabled.
So for me, the 'big deal' is being infor
Ack, should have thought of that.
Just tested. OK kernel:
4.9.0-8-amd64 #1 SMP Debian 4.9.144-3 (2019-02-02) x86_64 GNU/Linux
Borked kernel:
4.9.0-9-amd64 #1 SMP Debian 4.9.168-1 (2019-04-12) x86_64
Hmm. Just noticed GNU/Linux tag is missing too..
On Sun, 28 Apr 2019 19:41:47 +0200
Mic
FYI, I'm running sysvinit.
Package: udev
Version: 232-25+deb9u11
After today's upgrade to debian 9.9, I attempted to create a disk image.
I have a script, it does the following:
###
dd if=/dev/zero of=/tmp/ff1.raw bs=1G seek=8 count=0
sync
sleep 1
parted /tmp/ff1.raw mklabel msdos
parted -s /tmp/ff1.raw mkpart primary l
On Tue, 16 Apr 2019 11:33:23 +0300
Otto Kekäläinen wrote:
Hello Otto,
>I am sorry but I am not able to replicate this bug. So it cannot at
>least be common, thus downgrading severity.
>
>Please figure out a way for me to replicate it so I can debug what is
>happening. Also, check out if there is
be to do.
Brad
> On Feb 11, 2019, at 2:28 AM, Ian Campbell wrote:
>
> On Mon, 2019-02-11 at 12:06 +0200, Adrian Bunk wrote:
>> certbot is not in jessie, so nothing to fix/update there.
>
> Oh, I hadn't realised that bit, thanks for clarifying.
>
> I have no advice/suggestions then.
>
> Ian.
>
>
on3-cryptography certainly might be a problem though.
> On Feb 9, 2019, at 12:27 PM, Ola Lundqvist wrote:
>
> Hi Holger and Brad
>
> Here is a little more extensive list of dependencies:
>
> python-certbot (of course as it is the one providing certbot)
> python3-acme (
> On Feb 9, 2019, at 6:19 AM, Holger Levsen wrote:
>
> On Sat, Feb 09, 2019 at 02:54:43PM +0100, Ola Lundqvist wrote:
>> I can also add that I have looked into this for myself and the number of
>> needed dependencies is rather large. So it is not just certbot that need an
>> update, we also ne
To provide a little more information as an upstream maintainer of Certbot, the
lack of an upgrade here will affect a lot of Debian Jessie users.
Let’s Encrypt started sending out multiple emails telling affected users they
needed to upgrade their client or they will become unable to renew their
I just wanted to make sure this was still on everyone’s radar. The change
server side where tens of thousands of Debian users will begin being unable to
renew their certificates is in less than a month.
> On Jan 8, 2019, at 4:24 PM, Harlan Lieberman-Berg wrote:
>
> Hello Julien, everyone,
>
>
cros are for compiling. It is not used during linking.
Either way, `-lfoo` can appear for other libraries and
ros-catkin needs the fix.
-Brad
mpilers), and there is an issue
related to this here:
https://gitlab.kitware.com/cmake/cmake/issues/18638
However, that does not mean the above change should be reverted.
-Brad
has a proper SONAME. What is the output of
$ readelf -d /usr/lib/i386-gnu/libsndio.so | grep SONAME
? On x86_64 libsndio.so has a proper soname:
0x000e (SONAME) Library soname: [libsndio.so.7.0]
-Brad
What can be done to get this issue resolved?
This issue has jumped in priority now that domain validation through the
TLS-SNI-01 challenge will be completely unsupported by Let’s Encrypt on
February 13th, 2019. See
https://community.letsencrypt.org/t/february-13-2019-end-of-life-for-all-tls-sni
ated issues proposing a more general solution.
-Brad
Package: installation-reports
Boot method: iso in virtualbox
Image version:
https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso
Date: September 21, 2019
Machine: 64bit Virtualbox with 'debian' selected
Processor: N/A (I worry about CPU info now, thanks
Package: telnet
Version: 0.17-41
After an upgrade from jessie to stretch, and moving my jessie .telnetrc
file into my homedir, I noticed that it was no longer parsed correctly.
# cat .telnetrc
172.16.1.1
mode char
Yet stretch's version of telnet does not switch to character mode.
A bit of
Package: clawsker
Version: 1.1.1-1
Severity: normal
Tags: patch
Clawsker silently aborts on start up when called from KDE's application
menu.
When started from command line the following is printed to console
before quitting;
The encoding pragma is no longer supported at /usr/local/bin/clawsker
I’m another upstream developer of Certbot.
Taking 0.21.1 into stable would be the most conservative update that would
resolve this issue. The oldest version you could take is 0.21.0, but 0.21.1 was
released 8 days later and as a result has been much more widely tested. Since
0.21.1 was released
Package: python3-lexicon
Version: 2.1.21-1
Over the weekend, lexicon released version 2.2.1 which adds support for
multiple TXT records on the same domain. This functionality is needed in
plugins for Certbot like python3-certbot-dns-dnsimple. Future versions of this
and other Certbot plugins wi
Package: libetpan-dev
Version: 1.8.0-1
Severity: normal
Dear Maintainer,
Whilst trying to remove transitional package libidn2-0-dev, I found that
libetpan-dev would also be removed. I discovered that libetpan should depend
on libidn2-dev, which supercedes the current package, from a similar bug
Package: jpegoptim
Version: 1.4.4-1+b1
Severity: important
Tags: lfs
Dear Maintainer,
jpegoptim is not compiled with -D_FILE_OFFSET_BITS=64, so it will fail to
properly open and operate on files when it cannot stat them because their inode
or other fields are too large to fit in the 32-bit fields
I've tried multiple times to contact the upstream maintainer of gdbm,
but I have never heard back. What next?
--
Brad Spencer
Package: virtualenv
Version: 15.1.0+ds-1
If a network error occurs while installing a package with pip in a
virtual environment, a TypeError is raised when pip attempts to retry
the request. To cause this, I installed virtualenv and python and ran:
virtualenv venv
. ./venv/bin/activate
After th
Some info.
It seems that the default for probesize might be 500:
https://ffmpeg.org/ffprobe-all.html
probesize integer (input)
Set probing size in bytes, i.e. the size of the data to analyze to
get stream information. A higher value will enable detecting more
information in cas
Package: mplayer
Version: 2:1.3.0-6
I've recently been playing more 4k / 2160p video files, 8 bit encoded.
All have been fine with the exception of two of them.
$ uname -a
Linux xsdfsdf 4.9.0-4-amd64 #1 SMP Debian 4.9.51-1 (2017-09-28) x86_64 GNU/Linux
$ /usr/bin/mplayer -fs
filename.2160p
This has been fixed in Certbot's 0.19.0 release.
re die with two cores disabled...
Presumably you could also get "0,3-4,6", and other combos too.
This bug and patch has also been reported upstream:
https://github.com/brndnmtthws/conky/pull/416
This may be the same problem reported in Bug #863144: "conky: seqfaults"
-- Brad
-- Sys
On Sat, 12 Aug 2017 12:15:20 -0400
Didier 'OdyX' Raboud wrote:
Hello Didier,
>Thanks for the log.
YW
>That's actually 'serious', and hplip should not IMHO migrate to testing
>with that bug.
It's already in testing - it's from there that I got the upgrade.
Maybe I was not explicit on that poi
On Sat, 12 Aug 2017 11:27:18 -0300
Till Kamppeter wrote:
Hello Till,
>Bug reported upstream to HP (and to Ubuntu) as:
>https://bugs.launchpad.net/debian/+source/hplip/+bug/1710378
I missed that. Thanks for the info.
is not "":
AttributeError: 'DevMgr5' object has no attribute 'latest_available_version'
At this point, hp-toolbox exits without puting an window on screen.
-- Package-specific info:
Saving output in log file: /home/brad/hp-check.log
HP Linux Imaging and Printing System (ver
Please let me know if any more information is needed about this bug
report or how I can help resolve it. Thanks.
--
Brad Spencer
Source: gdbm
Version: 1.8.3-14
Severity: important
Tags: lfs patch upstream
Dear Maintainer,
After upgrading to stretch, man-db was crashing randomly during package
upgrades. Sometimes it would instead report EOVERFLOW errors. Since I was
running it on i386 with a very large XFS filesystem, I s
Package: dpkg
Version: 1.18.23
Newer versions of dpkg have colourized output.
I can see the usage case for this, and I can see the value for some.
However, for others, it is a major detractor.
One of the issues with the recent colourization of the userland, is that
each has its own way to disab
that luck resulted in
that memspace not being used for anything I noticed.
Sorry for the issue guys, very sorry to waste your time.
And thanks for the help.
On Fri, 21 Apr 2017 18:00:25 -0400
Brad Barnett wrote:
>
>
>
> > Can you reproduce the segfault reliably by run
> Can you reproduce the segfault reliably by running:
>
> "deb-systemd-helper unmask cgmanager.service >/dev/null"
>
> With Perl 5.24?
>
Hmm.
root@newoldbe:/var/cache/apt/archives# deb-systemd-helper unmask
cgmanager.service >/dev/null /usr/bin/deb-systemd-helper was not called
from dpkg.
> Could you perhaps include the following information:
>
> * Which architecture are you using? If you have multi-arch enabled,
>please list the architecture of the perl packages (e.g. in the form
>of "dpkg -l" if you don't mind including a list of all packages
>installed)
amd64, n
Package: perl
Version: 5.24.1-2
When installing packages right after a fresh stretch install, perl started to
segfault.
EG:
Setting up cgmanager (0.41-2) ...
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segm
Package: redmine
Version: 3.3.1-4
Severity: normal
During a jessie to stretch upgrade:
1)
ln: /var/lib/redmine/default/log: cannot overwrite directory
dpkg: error processing package redmine (--configure):
A rm of existing log dir, then allowed the link to be created..
2)
The DB install prompt
On Thu, Mar 23, 2017 at 08:43:57PM +, Chris Lamb wrote:
> > Would you consider applying this patch and uploading?
>
> Friendly ping on this :)
Unless I'm mistaken, I included it upstream in 2.16. There are a few
other fixes in 2.16 and 2.17 too.
Package: mdadm
Version: 3.3.2-5+deb8u1
Because the original report was for the wrong package, the version
information above was not included in this report until now.
Ahh... that makes more sense! Thought I was losing it... :-) Thanks for
the explanation!
On Fri, Feb 10, 2017 at 2:34 PM, Julian Andres Klode wrote:
> On Fri, Feb 10, 2017 at 02:01:59PM -0800, Brad Doster wrote:
> > Huh? The problem occurs when apt updates initramfs, so it is
Huh? The problem occurs when apt updates initramfs, so it is a package
manager issue, not a RAID manager issue. Did you read the whole report?
On Fri, Feb 10, 2017 at 1:48 PM, Julian Andres Klode wrote:
> Control: reassign -1
> On Fri, Feb 10, 2017 at 01:38:45PM -0800, Brad Doster
Package: apt
Version: 1.0.9.8.4
During initial installation of Debian 8, I used mdadm to create 2 RAID
arrays as follows:
/dev/md0 - RAID 1 - 4 drives - contains /boot only
/dev/md1 - RAID 5 - 3 drives + 1 spare - contains /
Both are needed to successfully boot the system.
During installation I
ichael Tokarev wrote:
> Control: tag -1 moreinfo unreproducible
>
> 28.10.2016 17:30, Brad Barnett wrote:
> > Package: qemu-system-x86
> > Version: 1:2.1+dfsg-12+deb8u6
> >
> > I've been unable to find anything about this via Google searches,
> > mailing list se
Package: qemu-system-x86
Version: 1:2.1+dfsg-12+deb8u6
I've been unable to find anything about this via Google searches,
mailing list searches, IRC, you name it. Nor, does the documentation
seem to indicate I'm doing anything wrong.
Additional queries to qemu-devel and qemu-discuss fell flat, wi
-
FWIW I would not consider this test failure to be a blocking issue for
packaging a new CMake on this platform. The behavior of this logic is
the same as it has been for years in CMake. It is just that this test
case did not exist before.
-Brad
3.8 packages so you may need a new svn branch in the packaging
repo for 3.9. I'll follow up in
https://llvm.org/bugs/show_bug.cgi?id=28325
with more details.
-Brad
1 - 100 of 341 matches
Mail list logo
