Hi Marco,
this was should be fixed with
https://github.com/ansible/ansible/commit/6cc97447aac5816745278f3735af128afb255c81
in ansible-core.
Can you test it again and close the bug if it's resolved for you?
Regards,
Lee
On Sun, 20 Apr 2025 12:15:25 +0200 Marco d'Itri wrote
Quick update: The function has been restored with a deprecation warning:
https://github.com/ansible/ansible/pull/85032
So the beta2 should release today or tomorrow, fixing the autopkgtests of the
other dependent packages (see
https://lists.debian.org/debian-python/2025/04/msg00029.html).
Hi Salvatore,
I'm still waiting a bit on upstream to respond to this. The beta2 should release
in the next day or two. If it's not addressed by upstream by then, I'll just
patch the function back in.
Cheers,
Lee
On Sun, 20 Apr 2025 07:14:16 +0200 Salvatore Bonaccorso
Package: src:linux
Version: 6.1.133-1
Followup-For: Bug #1102914
Dear Maintainer,
* What led up to the situation?
I use a VM to handle my NAS and use PCIe passthrough to pass a HBA
controller through to the VM, woke up today after an automagic
upgrade to lots of wonderful notificat
;exit-code'.
It looks to me like the systemd service is applying too strict settings, as
starting endlessh from the commandline works fine.
Greetings,
Lee
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: amd64 (x86_6
;ve checked
the autopkgtests of shadow and don't see this test case covered.
Set to severity grave because it's a regression and account expiry is a
potentially security sensitive subject.
Greets,
Lee
-- System Information:
Debian Release: trixie/sid
APT prefers testing
A
Hi,
this is indeed caused by the one character typo fix in the config file, which
prompts for the conffile change you see here. While this is unfortunate,
reverting the change in a new update would just trigger the same issue again. As
such, there is nothing to act on here.
Greetings,
Lee
on, as a
merged /usr is required per release notes [0]. I've tentatively set this to
severity serious, as I believe this could have been an oversight. If this is by
design, I think it's best if sbuild-createchroot would very prominently say so
on the end of the build run.
Thanks in advance!
Hi Aurelien!
On 26.07.24 13:11, Aurelien Jarno wrote:
Hi,
On 2024-07-25 00:34, Lee Garrett wrote:
So when /etc/locale.gen exists, this file is read, and then the settings in
the debconf database overwritten by those value. So once debconf is
installed, there's no programmatic way via de
reproduce it on Debian. As such, I'm
closing this bug.
Greets,
Lee
nly run on amd64 containers).
Unfortunately the logs are not available anymore. Any idea what the original
problem was?
It would be nice to have autopkgtests run on amd64 when testing things out
before uploading a package.
Regards,
Lee
Package: src:linux
Version: 6.1.76-1
Severity: critical
Justification: breaks the whole system
X-Debbugs-Cc: leeejobsacco...@mail.co.uk
Dear Maintainer,
* What led up to the situation?
Trying to boot the system with the 6.1.0-18 kernel
* What exactly did you do (or not do) that was eff
This bug can be reproduced with just a single import statement
```
import apt_inst
```
/mtrojnar/osslsigncode/releases/tag/2.3
Unfortunately, upstream has not assigned a CVE, and a quick glance at the closed
bug reports didn't reveal any further details.
Regards,
Lee
-- System Information:
Debian Release: 12.0
APT prefers testing-security
APT policy: (990, 'testing-securi
On Sat, 18 Mar 2023 17:06:08 +0100 Dominique Dumont wrote:
On Tue, 14 Feb 2023 22:21:26 +0100 Lee Garrett wrote:
> Bumped severity as this makes bts currently unusable, and probably
> breaks for quite a few DDs their workflow.
This does not break on my system where bts is connected to
] W:libpng warning: iCCP: known incorrect sRGB profile
(unknown:0, unknown)
[20230310 15:43:12] W:libpng warning: iCCP: known incorrect sRGB profile
(unknown:0, unknown)
[20230310 15:43:12] W:libpng warning: iCCP: known incorrect sRGB profile
(unknown:0, unknown)
Segmentation fault
Regards,
Lee
to have a
debian/rules entry like in [0].
I noticed that you're a DM, and since it's fairly late in the freeze process,
I'm willing to guide your through the process of fixing the package for the
bookworm release.
Regards,
Lee
[0] https://salsa.debian.org/debian/thinkfan/-/blo
I'm bumping the bug severity because currently it will ignore
security-relevant settings like keysize and algo, and the defaults are
pretty weak.
Bumped severity as this makes bts currently unusable, and probably
breaks for quite a few DDs their workflow.
fi'
E: Sub-process returned an error code
This is already fixed in unstable, but in it's current form this will break the
upgrade path from bullseye to bookworm. The fix is trivial, adding
`'non-free-firmware': 60,` to CommandNotFound/db/creator.py is enough. I propose
doing a
ous
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu lunar ubuntu-patch
Hi Lee,
The ansible-core autopkgtests fail now that /usr/bin/python3 is python 3.11:
[...]
autopkgtest [08:17:06]: test unit: [---
FATAL: Running under Python version 3.11 instead
The modification to fcgiwrap.socket doesn’t appear to use values recognised by
systemd.
I believe the configuration:
Mode=0660
SocketUser=www-data
SockerGroup=www-data
Should actually be:
SocketMode=0660
SocketUser=www-data
SocketGroup=www-data
Hi Scott,
I got around to fix the issue. I took the upstream patch as yours didn't
apply cleanly to 2.14 anymore. I will upload the package in the next hour.
Thanks for bringing this to my attention!
Regards,
Lee
On 23/11/2022 17:17, Scott Kitterman wrote:
Package: ansible-core
Ve
Hi Scott,
thanks for the bug report. A NMU is not needed, I'm currently preparing
the newest upstream release and hopefully will upload it in the next
days. If I don't upload within 7 days, feel free to NMU it.
Regards,
Lee
On 23/11/2022 17:17, Scott Kitterman wrote:
Package: an
same issue, so it looks like it's 100% reproducible.
Since I'd love to make some nice ascii art for my /etc/motd, it would be nice if
you could find the time to fix it. Thanks in advance!
Kind regards,
Lee
-- System Information:
Debian Release: 11.2
APT prefers stable-updates
APT po
ou put into these reviews!
>
> Regards,
> tony
>
--
*Tom Lee */ http://tomlee.co / @tglee <http://twitter.com/tglee>
On 07/10/2021 16:56, Daniel Baumann wrote:
> Package: ansible
> Version: 4.6.0-1
> Severity: serious
> Tags: experimental
>
> Hi,
>
> ansible in experimental is currently uninstallable because of the
> dependency on ansible-core which is unavailable/not yet uploaded in
> Debian as it seems.
>
>
e a
non-working /etc/thinkfan.yaml was placed there, taking precedence over
the thinkfan.conf, which has now been fixed. thinkfan being difficult to
configure is definitely a valid issue, but I'd like to continue that
discussion in a new wishlist bug.
Greetings from Hamburg,
Lee
Hi Baptiste,
On 20/04/2021 22:07, Baptiste Beauplat wrote:
> Hi Lee,
>
> On 2021/04/19 11:06 PM, Debian Bug Tracking System wrote:
>> #983140: ansible: Does not detect correct python interpreter on bullseye
>> target
>>
>> It has been closed by Debian FTP M
ight break
non-Debian systems (which could be targets where this code runs), I'll
have to check that first.
FYI, for 2.12+ the interpreter discovery will depend on the target OS
detected. You can already test it by setting interpreter_python=auto in
the [defaults] section of ansible.cfg.
R
I can confirm that upgrading libx11-6 to match libx11-xcb1 fixed my
issue with chromium. Thanks!
ugging purposes). Checking /var/log/apt/history.log, I don't see
any libva* packages being updated in that timeframe.
Regards,
Lee
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, '
Hi Sebastian,
thanks, I acknowledge the NMU. I'm in the process of packaging ansible
2.10.x which will already contain the fix. So feel free to consider this
bug closed.
Regards,
Lee
On Wed, 6 Jan 2021 12:07:18 +0100 Sebastian Ramacher
wrote:
> Control: tags 971309 + patch
> Co
gards,
Lee
Package: libc6
Version: 2.31-1
Followup-For: Bug #965932
Having the same issue, found an additional tidbit that may be of use:
When the failure happens, kernel logs a line like this:
Jul 20 20:04:38 hostname kernel: [ 373.963787] audit: type=1326
audit(1595289878.694:7): auid=4294967295 uid=10
nel 'asmongold' because: Received unsuccessful response from url
'https://api.twitch.tv/api/channels/asmongold/access_token' with code '410' and
body '{"error":"Gone","status":410,"message":"this API has been removed.&qu
close 955432
thanks
Hi Lucas,
nextepc was deprecated. Please use open5gs(
https://github.com/open5gs/open5gs) project.
Thanks and regards,
Sukchan
On Sun, Mar 22, 2020 at 4:39 AM Lucas Nussbaum wrote:
> Source: nextepc
> Version: 0.3.10+nods-3
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullsey
backpressue algorithm.
Source:
https://twitter.com/rspamd/status/1229774962296225799
https://www.reddit.com/r/synology/comments/f5jczp/mailplus_server_and_rspamdcom/fi0g29t/
As such, I'm closing this bug.
Regards,
Lee
in the release cycle (buster is in deep freeze), but it
might be possible that this gets added to buster-backports.
HTH,
Lee
On Wed, 19 Sep 2018 11:40:55 -0400 PICCORO McKAY Lenz
wrote:
> Package: geany-plugin-webhelper
> Version: geany-plugin-webhelper unable to install in testing
> Seve
utils)
Thanks in advance,
Lee
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNE
tag 917738 + patch
thanks
Hi, here's a patch for bug #917738 that I extracted from upstream.
Description: remove WebServiceException
Origin: upstream, https://github.com/OpenHFT/Chronicle-Threads/commit/bb1d4edfc7a783ebdc7c58bfc2f278f665e2539e#diff-e5af304c7efa4fec7930553b2fab754b
Index: openhft-c
ly solve your issue by cleanly upgrading to testing. You can also
seek help in #debian on irc.oftc.net. I'm leaving this bug open however, as
this issue could also happen during upgrade from stretch to buster. It's
missing versioned dependencies.
Regards,
Lee
> Hi,
>
> I attached a commit for you Git repository to record the changes of my NMU.
> BTW, it would be easier if you would decide to maintain capnproto on
>https://salsa.debian.org/debian
>
> Hope this helps, Andreas.
>
> --
> http://fam-tille.de
>
--
*Tom
could reproduce the issue on stretch.
On 08/11/2018 11:51, Lee Garrett wrote:
> Hi,
>
> sorry for the late response. CVE-2018-16837 should be fairly straight-forward
> to fix in stretch and jessie.
>
> For CVE-2018-10875 I have a patch in my work dir that should fix it. I'
#x27;s not clear if it affects stable. The inventory module
was completely rewritten in (IIRC) ansible 2.5, so it won't be a
straight-forward patch.
Regards,
Lee
On 07/11/2018 22:55, Moritz Mühlenhoff wrote:
> On Tue, Oct 30, 2018 at 12:35:05AM -0400, Chris Lamb wrote:
>> Hi Ivo,
Hi Sebastiaan,
On 01/11/2018 20:15, Sebastiaan Couwenberg wrote:> Hi Lee,
>
> On 11/1/18 6:41 PM, Lee Garrett wrote:
>> installing icinga2-common on a system that does not have icinga2 installed
fails
>> as follows:
>>
>> [...]
>>
>> Installing ic
t;8-->8-->8-->8-->8---
Installing icinga2 directly, which pulls in icinga2-common, makes the
installation go through cleanly.
Besides the policy violation it makes it hard to install icinga2 with the chef
cookbook at https://supermarket.chef.io/cookbooks/icinga2, as it inst
Hi,
Any update on this bug? dnssec-trigger will be autoremoved due to this bug
tomorrow. I'd like to see it in buster, though.
Regards,
Lee
ed in stretch or jessie, but was a
result of users trying to fix #756813. It may be possible that the init script
was inherited from wheezy or earlier, I did not check those releases. If that
was the case, I think the bug would have been noticed earlier.
Greetings from the Chemnitz BSP,
Lee
The problem here is that the newer enigmail from buster depends on gnupg (>=
2.2.8-2~), which is only available in stretch-backports. If there is no way to
make it work with gnupg from stable, I proprose to remove enigmail from
stable, and offer it via stretch-backports.
Whatever the eventual solu
k_connection
self.connect()
File
"/var/www/fdroid/.local/lib/python3.5/site-packages/gplaycli/gplaycli.py", line
406, in connect
gsfid = int(self.gsfid, 16)
ValueError: invalid literal for int() with base 16: 'reset'
Only positive side I'm currently seeing is that t
Hi Daniel,
I've fixed it again. However, I'm not sure how this FTBFS for you. It built
fine before, and also on the buildds. Maybe you have some setting that turns
lintian warnings into errors?
Regards,
Lee
On 18/05/18 20:55, Harlan Lieberman-Berg wrote:
> Oh, I see what's h
This bug has been fixed upstream in the torbrowser-launcher 0.2.9 release:
https://github.com/micahflee/torbrowser-launcher/releases/tag/v0.2.9
reassign 870599 python-jinja2
kthxbye
Hi,
can you add a Breaks: ansible << 2.3 to python-jinja2 in sid? That will help
with upgrading from stretch to buster. The template module in ansible 2.2.1
(stretch) is broken with jinja2 2.9 and above.
Regards,
Lee
Sorry...It may not the bug of libinput, i've downgrade my libinput to the
version 1.8.2-1, but the bug still exists...
Probably the problem has caughted by KDE, so just close this bug tracking
for sure ...
Package: libinput-bin
Version: 1.8.3-1
Severity: serious
Dear Maintainer:
After last version upgrade(from version 1.8.2-1), I found all input method
(incl
udes ibus, fcitx) were failed on Qt-based X program, but it still works on
GTK-b
ased. It becomes "blind" when my focus was a Qt-based program
27;s not supposed to be any such type, so the problem
> presumably lies in code generation. Could you please take a look?
> Thanks!
>
> --
> Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
> http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/
> finger/?a...@monk.mit.edu
>
--
*Tom Lee */ http://tomlee.co / @tglee <http://twitter.com/tglee>
installations. As a
workaround you can downgrade python-jinja2 to the version in stable. There
seems to be a patch available since a couple of hours, but I haven't got
around to test it yet.
Regards,
Lee
[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870599
[1] https://github.com/ansible/an
version is packaged yet and stretch is deep into the
freeze, I suggest removing the package from stretch.
[0]
http://blog.snort.org/2017/03/snort-2976-is-end-of-life.html
https://snort.org/eol
Regards,
Lee
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500, 'te
Package: python-iptables
Version: 0.11.0-2
Severity: serious
Justification: required
Dear Maintainer:
The python-iptables library did not work on my Debian 9. The problem occured
likes the following transcript:
-- Terminal Output --
<0> [anthon
On Fri, 10 Mar 2017, Simon McVittie wrote:
However, Matthew Gabeler-Lee's reply:
I argue this merits worse than "important" -- in a default install of
Stretch currently, munin doesn't work at all.
suggests that there may be something else going on.
Matthew, please could you describe what yo
Hi Richard,
please ask for support in the Debian IRC channel, which you can reach at
#debian on irc.oftc.net. Or the debian-user mailinglist, which is found at
https://lists.debian.org/debian-user/. There we'll be able to further debug
your issue. See you there!
Greetings,
Lee
infos and file the bug
against the respective package.
The IRC channel is #debian on irc.oftc.net, and the mailing list you can find
at https://lists.debian.org/debian-user/. See you there!
Greetings,
Lee
:3.20160805.1-3) unstable; urgency=medium
+
+ * Removed
+
debian/patches/0003-Fixed-type-window-to-use-default-1-as-manpage-stated.patch
+-- reverted upstream. (Closes: 850257)
+
+ -- Shih-Yuan Lee (FourDollars) Tue, 24 Jan 2017
17:06:54 +0800
+
xdotool (1:3.20160805.1-2) unstable
Hi,
On 07/11/16 17:56, matlink wrote:
> Hi Lee,
>
> Well the main goal for gplaycli was to provide a noconf and very easy to
> use command line for downloading apks.
I totally see the appeal, which is why I'm using it and want to see it in good
shape in Debian. :)
I'm pers
Package: pepperflashplugin-nonfree
Followup-For: Bug #833741
This is a grave issue for existing installations as well, as it is thus
impossible to upgrade them away from the releases that have critical
security vulnerabilities actively being exploited in the wild.
ckages in question, have agreed on which of the packages will
> resolve the problem please reassign the bug to that package. You may
> also register in the BTS that the other package is affected by the bug.
>
> Cheers,
>
> Andreas
>
> PS: for more information about the detection of file overwrite errors
> of this kind see https://qa.debian.org/dose/file-overwrites.html
>
--
*Tom Lee */ http://tomlee.co / @tglee <http://twitter.com/tglee>
On 17/05/16 14:21, Vlad Orlov wrote:
> Hi,
>
> This doesn't happen even in VirtualBox working on a host with an old Core 2
> Duo
> (both host and guest Debian installations are 64-bit). The upgrade went fine.
This is because your CPU architecture is not 32 bit, and not i586 or lower.
I'm sure if
Hi Dirk,
which type of processor do you have on that machine? As ydirson pointed out,
older CPU types (80586 and below on the i386 architecture) are not supported
anymore in stretch.
For everyone else: I can't reproduce this bug on my Intel i5, so it's safe to
upgrade.
Regards,
Lee
va_4.2.1.1-4_all.deb
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
Failed to perform requested operation on package. Trying to recover:
Press Return to continue.
Kind regards,
Lee Garrett
-- System Information:
Debian Release: stretch/sid
On 03/24/2016 12:31 AM, john hood wrote:
> I haven't been able to chase these glibc details down. Do you have
> pointers to specifics for this?
My assessment was based just on reading the referenced glibc-help
thread, and the commit it referenced --
https://sourceware.org/git/gitweb.cgi?p=glibc.gi
On Tue, 22 Mar 2016 23:21:31 +0100 Goffredo Baroncelli
wrote:
> Please give a look to
>
> https://sourceware.org/ml/libc-help/2016-03/msg00010.html
>
> to me it seems that the real problem is in glibc.
>From reading that thread and looking at the referenced git commit, I'm
not convinced it's a gl
Package: mosh
Version: 1.2.5-1.1
Followup-For: Bug #817929
Looks like upstream has a patch for this:
https://github.com/mobile-shell/mosh/pull/732/commits/a47917b97606a03f6bbf0cafd1fcd495b0229790
Though it looks like that's a hack and they really want this fixed in
protobuf:
https://github.com/
Package: redmine
Version: 3.0~20140825-8
Followup-For: Bug #808466
I believe this may be related to rails updating to 4.2.x in testing, whereas
redmine seems to still be searching for 4.1.x given the error message?
Hacking on /usr/share/redmine/Gemfile to change it to look for 4.2.x (making
the u
.2.1+dfsg3-0.3 doesn't work either, mpd
outputs the same error, reopen this bug then.
BTW, could maintainer please update the summary of libadplug-2.2.1-0 and
libadplug-2.2.1-0v5? I have some trouble to tell them apart...
Thanks.
--
Adam Lee
Will do Martin -- thank you!
On Jun 25, 2015 9:55 AM, "Martin Michlmayr" wrote:
> * Tom Lee [2015-05-03 02:34]:
> > Not sure if you're actively attempting test rebuilds every so often, but
> > feel free to try for yourself when 0.5.2-1 hits unstable.
>
&g
put: Assertion `redisGetReply(c,
> (void*)&replies[i]) == 0' failed.
>
> See
> https://buildd.debian.org/status/fetch.php?pkg=hiredis&arch=powerpc&ver=0.13.1-2&stamp=1434137918
> for a full log.
>
> Emilio
--
Tom Lee / http://tomlee.co / @tglee
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
s the
best way to handle this sort of situation. gbp's support for filtering may
also be an option.
libhiredis0.13 and libhiredis-dev 0.13.1-1 have been uploaded to the
experimental distribution if you'd like to reproduce this for yourself.
Cheers,
Tom
--
*Tom Lee */ http://tomlee.co / @tglee <http://twitter.com/tglee>
OK ] Capability.DynamicClient (1 ms)
[ RUN ] Capability.DynamicClientInheritance
On Sun, Mar 29, 2015 at 11:01 PM, Niels Thykier wrote:
> On 2015-03-30 04:30, Tom Lee wrote:
> > Hey Niels,
> >
> > Understood. Hard to see exactly what's going on here because we
rent version of capnproto FTBFS on armel and
> armhf due to a segmentation fault in one of the tests. This prevents
> the new version of migrating to testing as it is a regression compared
> to the version in testing.
>
> Thanks,
> ~Niels
>
--
*Tom Lee */ http://tomlee.co / @tglee <http://twitter.com/tglee>
-05.
Full details + patch:
https://github.com/sandstorm-io/capnproto/blob/master/security-advisories/2015-03-05-0-c%2B%2B-addl-cpu-amplification.md
--
*Tom Lee */ http://tomlee.co / @tglee <http://twitter.com/tglee>
ll details + patch:
https://github.com/sandstorm-io/capnproto/blob/master/security-advisories/2015-03-02-2-all-cpu-amplification.md
--
*Tom Lee */ http://tomlee.co / @tglee <http://twitter.com/tglee>
2015-03-02.
Full details + patch:
https://github.com/sandstorm-io/capnproto/blob/master/security-advisories/2015-03-02-1-c%2B%2B-integer-underflow.md
--
*Tom Lee */ http://tomlee.co / @tglee <http://twitter.com/tglee>
-02.
Full details + patch:
https://github.com/sandstorm-io/capnproto/blob/master/security-advisories/2015-03-02-0-c%2B%2B-integer-overflow.md
--
*Tom Lee */ http://tomlee.co / @tglee <http://twitter.com/tglee>
On Sun, 1 Mar 2015, Sebastian Harl wrote:
I think that MODE=none should no longer be a valid option when using
systemd as you'd then use 'systemctl disable' instead. I don't know
systemd very well, so there could be other options as well and/or maybe
a way to disable upsmon in systemd by default
Package: nut-client
Version: 2.7.2-3
Followup-For: Bug #747863
Unfortunately this bug is still present. A virgin install of nut-client
results in a service start failure and thus package install failure.
$ sudo systemctl status nut-monitor.service
● nut-monitor.service - Network UPS Tools - pow
Also broken are several pieces of horizontal layout. Items that are
supposed to be right aligned to the viewport, causing leftwards items to
be shortened, are instead often pushed off creating horizontal
scrolling. This happens on both the left pane when expanding categories
(often making _all_ t
reopen 759777
thanks
This is not fully fixed. Special feeds and folders have no icons
still. Menu roll-overs are better, but still have some "detritus"
around the edges.
Worse yet, now downgrading dojo to 1.7 makes tt-rss refuse to run, and
dojo 1.9 (what's marked as required now) was never pac
a
> plan to close this out? It sounds like a solution is very near, hopefully
> to the satisfaction of both the maintainers and release coordinators.
>
>
> Regards,
>
> Tim.
>
--
*Tom Lee */ http://tomlee.co / @tglee <http://twitter.com/tglee>
Totally disabling this feature seems very user-unfriendly :(
Digging in, clearly this can be re-enabled via about:config, perhaps
this merits a NEWS entry to alert users to this?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contac
rror when the port is not open: ");
> > #v-
> >
> > But maybe there are better ways to fix this.
>
> That would make the test kinda useless, but I guess it's no worse than
> disabling
> it completely.
>
>
I don't mind this approach if we call out the fact the test was skipped
rather than silently "passed", but at that point it's providing the same
value as a test that's been completely disabled ... keeping Tobias'
original patch for now.
--
*Tom Lee */ http://tomlee.co / @tglee <http://twitter.com/tglee>
able; urgency=medium
+
+ * Disable a network test failing in pbuilder (closes: #770648)
+
+ -- Tom Lee Mon, 24 Nov 2014 00:17:31 -0800
+
hiredis (0.11.0-4) unstable; urgency=medium
* Symlinks for cmake 3.0 (closes: #758548)
diff -Nru hiredis-0.11.0/debian/patches/04_disable-network-tests.
2014 at 11:00 AM, gregor herrmann wrote:
> On Sun, 30 Nov 2014 10:51:56 -0800, Tom Lee wrote:
>
> > Talked this over with the release team on #debian-release,
>
> Except that noone who responded is a member of the release team :)
>
> Cheers,
> gregor
>
> --
>
6:55 +0100, Tobias Frost wrote:
> > > Am Sonntag, den 30.11.2014, 00:21 -0800 schrieb Tom Lee:
>
> > > > Also, I feel like the "serious" severity is overstating the issue
> > > > given that 0.11.0-4 builds fine in buildd/sbuild. Alessan
g a new package uploaded with the pbuilder
fixes & nocheck support.
On Mon, Nov 24, 2014 at 4:32 AM, Tobias Frost wrote:
> On Mon, 24 Nov 2014 00:45:04 -0800 Tom Lee wrote:
> > Alrighty, patch applied & pbuilder's clean. Now just waiting on
> Alessandro
> > to
test] Error 2
> make[1]: Leaving directory '/tmp/buildd/hiredis-0.11.0'
> debian/rules:13: recipe for target 'build' failed
> make: *** [build] Error 2
> dpkg-buildpackage: error: debian/rules build gave error exit status 2
> E: Failed autobuilding of package
>
&
; APT prefers testing-updates
> APT policy: (500, 'testing-updates'), (500, 'testing')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
>
--
*Tom Lee */ http://tomlee.co / @tglee <http://twitter.com/tglee>
Package: gnome-shell
Version: 3.14.1-1
Followup-For: Bug #766359
I too encountered this problem. By checking syslog, I eventually tracked it
down to a missing dependency on the 3.14.1 version of libmutter0e:
gnome-session[22789]: (gnome-shell:22822): Gjs-WARNING **: JS ERROR: GLib.Error
g-invok
have to be self-signed so users would have to
click through the error. And the encryption would be redundant (though
not necessarily a bad idea -- defense in depth, in case Tor gets badly
broken in ways we can't foresee or something).
--
Micah Lee
--
To UNSUBSCRIBE, email to debian-bu
1 - 100 of 255 matches
Mail list logo
