Hi all,
first of all, apologies for the late reply. I moved in February, and I'm
still in the process of settling in. I have still to unpack my
development machine...
On 2017-02-14 09:39, Raphael Hertzog wrote:
> On Mon, 09 Jan 2017, Sophie Brun wrote:
>> AttributeError: 'BitEnumField' object has
Package: amqp-tools
Version: 0.11.0-1
Severity: grave
Tags: security
Forwarded: https://github.com/alanxz/rabbitmq-c/issues/575
When passing authentication data with either --password or --url, the
data is exposed in the process list, where it can be seen by any user.
Example:
$ pgrep -a ampq-c
Control: tag -1 fixed-upstream
On 2023-06-11 12:28, Christian Kastner wrote:
> Package: amqp-tools
> Version: 0.11.0-1
> Severity: grave
> Tags: security
> Forwarded: https://github.com/alanxz/rabbitmq-c/issues/575
>
> When passing authentication data with either --password
Package: debci
Version: 3.6
Severity: serious
Tags: security
X-Debbugs-Cc: Debian Security Team
Hi,
When using authentication in AMQP connections, the username and password
supplied in the --url option to amqp-consume resp. amqp-publish are
exposed in the proces list, see #1037322:
$ pgrep
On 2023-06-16 17:56, Antonio Terceiro wrote:
> Note that the variable where you inserted a username and password is
> calle debci_amqp_server, and was never supposed to be used for putting a
> password in plain text.
I think this is where the documentation of the --amqp option threw me
off, from d
(debian-ai, apologies for re-sending, I hit the wrong reply button.)
On 2023-03-08 18:21, Simon McVittie wrote:
> There is *a* version of llvm-toolchain-15 in bookworm, version 1:15.0.6-4,
> which is used by the rocm-hipamd_5.2.3-1 and mesa_22.3.3-1 in bookworm.
> I'm not suggesting that 1:15.0.6-
Package: libamdhip64-5
Version: 5.2.3-5
Severity: serious
When working on rocrand, I noticed that the rocrand libraries did not
work without libamd-comgr2 installed.
Cordell Bloor pointed out that libamd-comgr2 is essential to any library
that contains GPU kernels, and the calls are likely to be
Package: librocprim-dev
Version: 5.3.3-3
Severity: serious
librocprim-dev needs libamdhip64-dev, but this dependency is missing
from the package.
Hi Helmut,
you're quick!
On 2022-12-12 15:17, Helmut Grohne wrote:
> Package: libcap-dev
> Version: 1:2.63-1
> Severity: serious
> Jutsification: fails to install with an unpack errror
> User: helm...@debian.org
> Usertags: rebootstrap
>
> Coinstalling libcap-dev fails:
>
> | Unpacking libcap-d
On 2022-12-13 06:02, Christoph Anton Mitterer wrote:
> On installation there is a file conflict:
> Unpacking libpam-cap:amd64 (1:2.66-1) over (1:2.63-1) ...
> dpkg: error processing archive
> /tmp/apt-dpkg-install-B9lzYA/08-libpam-cap_1%3a2.66-1_amd64.deb (--unpack):
> trying to overwrite '/usr/s
Source: docopt
Version: 0.6.2-2.2
Severity: serious
User: pyt...@packages.debian.org
Usertags: pytest-v6
Hi,
docopt autopkgtests fail with pytest 6 in unstable because it uses a
deprecated feature that will be removed soon, and that, by default,
considered an error in pytest 6.
The fragment of t
Source: gitsome
Version: 0.8.0+ds-4
Severity: serious
User: pyt...@packages.debian.org
Usertags: pytest-v6
Hi,
gitsome autopkgtests fail with pytest 6 in unstable because of changes
to the use of TerminalWriter. See
https://docs.pytest.org/en/stable/changelog.html#id60
The CI error log belo
Source: ffc
Version: 2019.2.0~git20200123.6b621eb-3
Severity: serious
User: pyt...@packages.debian.org
Usertags: pytest-v6
Hi,
ffc autopkgtests with pytest 6 in unstable because it uses a deprecated
feature that will be removed soon, and that, by default, considered an
error in pytest 6.
The fra
Source: pytest-mpi
Version: 0.4-2
Severity: serious
User: pyt...@packages.debian.org
Usertags: pytest-v6
Hi,
pytest-mpi autopkgtests fail with pytest 6 in unstable. From the CI log
below, for some reason, the test gets aborted at some point:
> Testing with python3.9:
> ==
Source: xonsh
Version: 0.9.24+dfsg-2
Severity: serious
User: pyt...@packages.debian.org
Usertags: pytest-v6
Hi,
xonsh autopkgtests with pytest 6 in unstable because it uses a
deprecated feature that will be removed soon, and that, by default,
considered an error in pytest 6.
The fragment of the
Source: python-ase
Version: 3.20.1-1
Severity: serious
User: pyt...@packages.debian.org
Usertags: pytest-v6
Hi,
python-ase autopkgtests with pytest 6 in unstable. Apparently, something
is trying to write to /usr/lib/:
> File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187, in
> _
Source: python-llfuse
Version: 1.3.6+dfsg-2
Severity: serious
User: pyt...@packages.debian.org
Usertags: pytest-v6
Hi,
python-llfuse FTBFS with pytest 6 in unstable:
> ERRORS
>
> _ ERROR at setup of te
Source: sabnzbdplus
Version: 3.1.1+dfsg-1
Severity: serious
User: pyt...@packages.debian.org
Usertags: pytest-v6
Hi,
sabnzbdplus autopkgtests fail with pytest 6 in unstable. The problem
seems to be the -k expression used to exclude particular tests:
> ERROR: Wrong expression passed to '-k': test
Package: yubikey-luks
Version: 0.5.1+29.g5df2b95-5
Severity: grave
Justification: confidential information leak
Tags: security
Hi,
Looking at the upstream yubikey-luks repository, I noticed what seems to
be an important recent fix, namely for the password (used as the yubikey
challenge) being exp
On 08.03.21 20:26, Markus Frosch wrote:
> Thanks for reporting, haven't been following upstream for a while since I
> don't
> use the package actively anymore.
Admittedly, this particular information was somewhat buried.
> Due to lack of time, I'll upload a minimal patch for now. Feel free to jo
Source: qemu-sbuild-utils
Version: 0.1
Severity: serious
X-Debbugs-CC: jo...@debian.org
The sbuild maintainers raised the valid point that it might be better to
incorporate large parts of this software in src:sbuild, in which case
this package should not enter bullseye.
So until this question is
Hi,
On 11.02.21 15:20, Nilesh Patra wrote:
> On Sun, 7 Feb 2021 22:08:58 +0100 =?utf-8?Q?=C3=89tienne?= Mollier
> wrote:
>> I tried to reproduce the bug by building igdiscover 0.11-3 using
>> sbuild in a clean Sid chroot which did include pytest 6:
>>
>> $ schroot -c unstable-amd64-sbuild -d / \
Control: notfound -1 elementpath/2.0.4-1
Control: reassign -1 python-xmlschema
On 11/21/20 9:50 PM, Paul Gevers wrote:
> Source: elementpath, python-xmlschema
> Control: found -1 elementpath/2.0.4-1
> Control: found -1 python-xmlschema/1.2.2-2
> Severity: serious
> Tags: sid bullseye
> X-Debbugs-C
Control: severity -1 important
Tags: -1 unreproducible
Hi Julien,
I'm downgrading because the pytest currently does work with hundreds of
packages, implying that it cannot be (generally) unusable.
On Wed, 09 Dec 2020 21:08:39 +0100 Julien Puydt wrote:
> I was trying to update another package in
Hi,
On 2022-02-16 11:57, John Paul Adrian Glaubitz wrote:
> Hello!
>
> On 2/16/22 11:36, Graham Inggs wrote:
>> Is anyone able to help with the bus error on armhf please?
>
> Bus errors are normally easy to spot. Just run the code in question through
> GDB and see where it crashes. Then look at
On 2022-03-08 21:58, Christian Kastner wrote:
> I'll upload an NMU.
Ah, pulling the newest source from Salsa, I saw Georges' @debian.org
address. Apologies!
In that case, please NMU it yourself (as you've already prepared the
changelog).
Best,
Christian
Hi,
FYI, cron is looking for a new maintainer, see #984736, so I guess that
is why there hasn't been any activity yet.
On 2021-06-22 16:52, Wouter Verhelst wrote:
> Whoever wrote that patch should be slapped around the head with a copy
> of RFC3696.
As evident from the header, that patch was tak
Hi all,
Regarding liblinear: I thought I already set the Maintainer to Debian
Science Team, I guess I missed it.
On 2019-12-21 20:11, Chen-Tse Tsai wrote:
> I've created an account on Salsa.
>
> Do you think we should remove cdbs and use another build system
> instead? Please let me know if you
Andreas, what are you doing?
On 2019-12-25 07:52, Andreas Tille wrote:
> On Tue, Dec 24, 2019 at 10:39:55AM -0500, Chen-Tse Tsai wrote:
>> I just submitted a PR for dropping python2 dependencies:
>> https://salsa.debian.org/science-team/libsvm/merge_requests/1
>>
>> Any comment is appreciated. I'l
On 2019-12-25 10:59, Andreas Tille wrote:
> Kind regards
>
>Andreas.
I've re-read my original message and feel that I was overly harsh. I was
irritated about the rushed upgrade as in private communication with
Chen-Tse, I highlighted precisely the possible complexity of this
upgrade and h
On 2019-12-25 18:08, Chen-Tse Tsai wrote:
> Thanks Andreas and Christian for the updates/comments. I agree that I
> should have been more verbose in the changelog. I'm tracing all the
> commits to learn more about packaging. I was playing with gbp for
> updating upstream. I really like how it works
On 10.01.20 11:07, Andreas Tille wrote:
> since my upload was a bit questionable this gives us the chance
> to discuss it again. What option would you prefer:
>
>1. I just re-upload what is in Git right now to new queue
>2. Somebody who feels more competent takes over
>3. Something el
Hi all,
On 10.01.20 15:33, Chen-Tse Tsai wrote:
> Yes, my changes are merged.
I checked the package and everything looks pretty good. I just added
some minor polishing of my own.
Very surprisingly, not a single symbol has changed since 3.21 -- no
additions, no removals, no changes. It looks as w
On 11.01.20 06:09, Andreas Tille wrote:
> On Fri, Jan 10, 2020 at 11:45:15PM +0100, Christian Kastner wrote:> Strange.
> I did not intentionally set the branch protection. Hope it
> works now.
Pushing worked after this, thanks.
I test-rebuilt all packages with build dependenci
On 19.01.20 03:23, Sandro Tosi wrote:
> This bug was closed, but the package has still some dependencies towards
> Python2 packages, in details:
>
> (binary:libsvm-tools)Depends->python:any
>
> Re-opening, so that they can be taken care of.
I believe I am missing something; could you expand on
On 19.01.20 11:06, PICCA Frederic-Emmanuel wrote:
> Hello, if it is like for my ufo-core package, this could be due to a script
> file with a shebang using python instead of python3
I just tested this and indeed, there were scripts with said python in
the shebang. Changing this to python3 fixed t
Control: tag -1 pending
Hello,
Bug #955081 in deap reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/python-team/modules/deap/-/commit/4b6a0899db3b58784e5bf8a4402
Control: tag -1 pending
Hello,
Bug #955054 in pygments reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/python-team/modules/pygments/-/commit/1c2457565eced489b16
Package: python3-setuptools
Version: 49.3.1-1
Severity: grave
Justification: Package is unusable
The most recent upload broke something badly, setuptools can no longer
be imported:
$ python3 -c 'import setuptools'
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/
On 2020-02-13 09:31:54 +0100 Andreas Tille wrote:
> Control: tags -1 upstream
> Control: forwarded -1 https://github.com/biocore/scikit-bio/issues/1693
>
> > Due to the nature of this issue, I filed this bug report
> > against both packages. Can you please investigate the situation and
> > reassi
Control: reassign -1 python-skbio
On 2020-02-12 20:00:16 +0100 Paul Gevers wrote:
> With a recent upload of scikit-learn the autopkgtest of python-skbio
> fails in testing when that autopkgtest is run with the binary packages
> of scikit-learn from unstable. It passes when run with only packages
>
Control: tag -1 pending
Hello,
Bug #965362 in numpydoc reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/python-team/modules/numpydoc/-/commit/627063a3a5c88b74b9b
On 2020-07-20 11:22:16 +0100 "Chris Lamb" wrote:
> Whilst working on the Reproducible Builds effort [0] we noticed that
> numpydoc could not be built reproducibly.
>
> This is because it includes a junit-results.xml and .coverage file
> from the test run. (The latter file should have been detecte
Control: retitle -1 bcolz: FTBFS with newer python3-sphinx
On Mon, 20 Jul 2020 09:51:26 +0200 Christian Kastner wrote:
> Source: bcolz
> Version: 1.2.1+ds2-5
> Severity: serious
> Justification: FTBFS
Control: tag -1 pending
On 31.01.20 11:33, Paul Gevers wrote:
> Source: libsvm
> Version: 3.24+ds-2
> X-Debbugs-CC: debian...@lists.debian.org
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: fails-always
>
> Dear maintainers,
>
> With a recent upload of libsvm you added an aut
Source: bcolz
Version: 1.2.1+ds2-5
Severity: serious
Justification: FTBFS
Hi,
bcolz FTBFS on amd64 with an updated version of python3-numpydoc.
Here is the tail of the build log. The error seems to originate
during the build of the documentation:
PYTHONPATH=/<>/.pybuild/cpython3_3.8_bcolz/buil
Thanks, Graham.
This looked easy enough so I cherry-picked this patch, but the build
produces a ton symbol changes.
These are all C++ internal symbols that should not be public, I assume
this is gcc-14 related. Since they not part of the public interface, I
wouldn't have qualms forcefully updatin
Control: severity -1 important
I'm downgrading this bug, as the suite successfully completed on another
Navi24 device [1]. No longer RC, this should allow migration to testing
again.
Best,
Christian
[1] https://lists.debian.org/debian-ai/2023/10/msg00044.html
Version: 5.5.1-1
Closing this bug, as it is invalid. rocrand never failed, according to
the CI logs (even the linked one).
Control: tag -1 pending
Hello,
Bug #1052968 in hipcub reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/rocm-team/hipcub/-/commit/97247d25e7b4574622959e4d55a52b96
Control: tag -1 pending
Hello,
Bug #1052954 in rccl reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/rocm-team/rccl/-/commit/b936acd42edaa2c278c693477add9c7d2560
Control: tag -1 pending
Hello,
Bug #1067501 in hipsolver reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/rocm-team/hipsolver/-/commit/d51961aa5fc702bd5cf28c9524
On 2024-06-16 15:10, Lucas Nussbaum wrote:
> Source: python-xmlschema
> Version: 3.3.1-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20240615 ftbfs-trixie
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to
Control: tag -1 pending
Hello,
Bug #1045688 in rocm-device-libs reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/rocm-team/rocm-device-libs/-/commit/a5eaa2718377
Source: rocrand
Version: 5.5.1-1
Severity: serious
The tests from ci.rocm.debian.net failed on gfx1030 [1]. I'm filing this
RC bug to prevent migration to testing.
[1]
https://ci.rocm.debian.net/data/autopkgtest/unstable/amd64+gfx1030/r/rocrand/83/log.gz
Source: rocfft
Version: 5.5.0-4
Severity: grave
Justification: Can crash the host
autopkgtests for rocfft triggered a soft lockup when run with an 6500 XT
(gfx1034, Navi24).
This is very probably a kernel issue, but I'm filing this bug here until
we have actually identified the root cause, after
Hey Cory,
On 2024-02-28 21:16, Cordell Bloor wrote:
> This segfault does seem to be caused by mixing clang-15 and clang-17 in
> the HIP RTC codepath. When libamdhip64 from ROCm 5.6.1 (built with the
> same clang-17 as rocm-compilersupport 6.0+git20231212.4510c28+dfsg-1) is
> used, the segfault dis
Control: tag -1 pending
Hello,
Bug #1065351 in rocblas reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/rocm-team/rocblas/-/commit/10bafdf7949eba57ae124741cba15e
Control: tag -1 pending
Hello,
Bug #1065353 in rocsparse reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/rocm-team/rocsparse/-/commit/328d612af51ece88548bbdd131
Package: gimageview
Severity: grave
Justification: renders package unusable
I'm experiencing the exact same issue described in #459288, but all my messages
to 459...@bugs.debian.org bounced.
Regards,
Christian
-- System Information:
Debian Release: 5.0
APT prefers stable
APT policy: (500, 's
Christian Kastner wrote:
> I'm experiencing the exact same issue described in #459288, but all
my messages
> to 459...@bugs.debian.org bounced.
I just realized why I'm still seeing this bug, although it had been
marked as fixed back in August: the version in etch and in le
Hi Sebastian,
writing to you as you bumped the severity to 'serious': could the rT
please give us an extension on the autoremoval for this particular bug.
The transition from first-filing-to-serious was unusually short notice,
and caught us in the middle of our own update of the stack.
This affe
Hi Étienne,
On 2024-02-26 19:29, Étienne Mollier wrote:
> If that helps, the autoremoval timer is reset each time the RC
> critical bug triggering the autoremoval is updated, e.g. when
> reporting an evolution of the situation in a new comment.
thanks for the info! That's incredible useful to know
Hi Jeffrey,
On 2023-12-02 11:39, Jeffrey Bencteux wrote:
> Hi,
>
> Both setuid() and setgid() return values are not checked in cron's code used
> to execute user-provided commands:
This issue was reported as CVD-2006-2607 and fixed a long time ago.
Here's the relevant patch:
https://sources.d
On 06/12/2010 06:51 PM, Anthony Campbell wrote:
> Package: cron
> Version: 3.0pl1-112
> Severity: grave
> Tags: sid
> Justification: renders package unusable
>
> Cron refuses to install: error message is:
> Reverting to pervious version
> (cron_3.0pl1-111_i386.deb) eliminates the error
>
> (Rea
tag 583063 +patch
thanks
On 01/-10/-28163 08:59 PM, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
>
*snip*
>> WARN: If you are running on a 32 Bits x86 platform, you should install the
>> Python Psyco module if possible, this would gr
tag 587131 +patch
thanks
On 01/-10/-28163 08:59 PM, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
>
> Relevant part:
>> dh_usrlocal: debian/python-paver/usr/local/bin/paver is not a directory
>> rmdir: failed to remove `debian/python-pav
On 06/25/2010 04:31 PM, Christian Kastner wrote:
> tag 587131 +patch
> thanks
>
> On 01/-10/-28163 08:59 PM, Lucas Nussbaum wrote:
>> During a rebuild of all packages in sid, your package failed to build on
>> amd64.
>>
>> Relevant part:
>>> dh_usrloca
reassign 604163 debconf
forcemerge 560317 604163
thanks
Hi Marco,
On 11/20/2010 09:20 PM, Marco Nenciarini wrote:
> On a freshly installed squeeze system:
>
> mnen...@poison:~$ sudo dpkg-reconfigure -p low cron
> Stopping periodic command scheduler: cron.
> dpkg-maintscript-helper: error: coul
severity 647884 normal
thanks
Hi,
On 2011-11-07 10:34, Serguei wrote:
> Package: cron
> Version: 3.0pl1-116
> Severity: critical
^^^
Bug severities have a very specific meaning in Debian, see
http://www.debian.org/Bugs/Developer#severities
I'm downgrading this to "normal" accord
tag 625123 + confirmed pending
thanks
On 05/02/2011 02:33 PM, Lucas Nussbaum wrote:
> Source: libfann
> Version: 2.1.0~beta~dfsg-3
> Severity: serious
> Tags: wheezy sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20110502 qa-ftbfs
> Justification: FTBFS on amd64
> During a rebuild of
reopen 588588
thanks
On 05/12/2011 10:59 PM, Richard Hartmann wrote:
> According to Mister_X in #aircrack-ng on freenode, aircrack-ng never
> took any code from Pyrite, it was the other way round. Closing.
There seems to be a misunderstanding here. The issue wasn't aircrack-ng
taking code from Py
merge 597707 597705
thanks
Hi Igor,
On 09/22/2010 01:08 PM, jen...@debian.org wrote:
> Each time cron tries to execute a job from /etc/cron.d (or any other
crontab)
> I see syslog entries like these:
>
> some-machine:~# grep 'segfault at 0 ip 0 sp' /var/log/syslog
> Sep 22 07:17:01 some-machine
I think this has been open long enough now, closing.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: aircrack-ng
Severity: serious
Justification: Policy 12.5
debian/copyright neither mentions the authors of or the license under which
src/sha1-sse2.h and src/sha1-sse2.S are distributed.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstab
On Tue, 13 Jul 2010 14:52:27 +0900, Nobuhiro Iwamatsu
wrote:
> Source: libfann
> Version: 2.1.0~beta~dfsg-1
> Severity: serious
>
> Your package FTBFS on alpha, armel and sh4.
> https://buildd.debian.org/pkg.cgi?pkg=libfann
>
https://buildd.debian.org/fetch.cgi?pkg=libfann;ver=2.1.0~beta~dfsg
Hi,
On 01/-10/-28163 08:59 PM, Alexander Reichle-Schmehl wrote:
>> The authors are:
>>
>> // SHA-1 SSE2 implementation, (C) 2008 Alvaro Salmador
>> (napla...@msn.com), ported from Simon Marechal's SHA-1 MMX
>> // SHA-1 MMX implementation, (C) 2005 Simon Marechal (si...@banquise.net)
>>
>> Missing
On 07/19/2010 09:15 PM, Julien Cristau wrote:
> Can't these packages use libcrypto (not gpl-compatible, so maybe not the
> best idea in all cases) or libgcrypt or some other crypto library
> instead of having their own sha1 implementations?
Pyrit falls back to libcrypto when the SSE2 implementatio
On 01/-10/-28163 08:59 PM, Richard Hartmann wrote:
> upstream
>
> The authors are:
>
> // SHA-1 SSE2 implementation, (C) 2008 Alvaro Salmador
> (napla...@msn.com), ported from Simon Marechal's SHA-1 MMX
> // SHA-1 MMX implementation, (C) 2005 Simon Marechal (si...@banquise.net)
>
> Missing licen
Package: cronie
Version: 1.4.8-1~exp1
Severity: serious
Tags: experimental
Justification: FTBFS on Hurd
cronie FTBFS on Hurd, even though it is a supported platform.
The fix is trivial and can be traced back to #64382. I was under the impression
that cron-4.1 (cronie's ancestor) had worked around
Hi Adam,
On 2014-11-10 01:47, Adam Borowski wrote:
> Package: src:keyutils
> Version: 1.5.9-5
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
>
> Hi!
> I'm afraid that during a rebuild of jessie on armhf (using sbuild) your
> package failed to
Darn, I CCed submit. Sorry about that. I blame my webmail.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On 2014-11-12 22:07, martin f krafft wrote:
> I forgot to send the previous control messages to the control bot,
> so I just bumped the severity to RC, sorry.
>
> Please don't release sudo in stable with this bug :/
Bdale, would you be OK with me forwarding this upstream? (I ask because
you indic
Control: tag -1 confirmed fixed-upstream patch
Now *that's* a cool upstream -- fixed the bug not even 3 hours after I
reported it.
Please find attached upstream's patch from upstream's Bugzilla,
refreshed to apply against 1.8.11p2-1.
Christian
Index: sudo-1.8.11p2/plugins/sudoers/sudoers.c
=
14-11-16 01:49:48.0 +0100
@@ -1,3 +1,11 @@
+pyparted (3.10.0-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Backport patch Fix-localeC-imports.patch from upstream which fixes an
+ImportError that rendered the python3-parted package unusable.
+
+ -- Christian Kastner Sun
On 2014-11-16 14:33, martin f krafft wrote:
> also sprach intrigeri [2014-11-16 13:58 +0200]:
>> If Bdale can't take care of it shortly, does anyone affected (who can
>> actually test that the resulting package fixes the problem for them)
>> want to NMU? I think DELAYED/2 or /5 would be appropriat
control: tag -1 moreinfo
Hi everyone,
> Am 18.05.2015 um 19:04 schrieb Bernhard Übelacker:
>> Hello,
>> as I got the same problem on my raspberry, probably I can give
>> some details.
>>
>> This is the situation I started:
>> - put 2015-05-05-raspbian-wheezy.img on SD-card and booted
>> - changed
On 2015-06-02 19:48, Michael Biebl wrote:
> Am 02.06.2015 um 18:11 schrieb Cyril Brulebois:
>> libudev1-udeb depends on missing libcap2. I suspect the easiest would be
>> to drop libcap2 support from the udeb build. An alternative would be to
>> try and add a udeb in libcap2. I'd rather have the fo
Hi,
On 2015-06-06 21:33, Christoph Berg wrote:
> Re: Christian Kastner 2015-05-03 <554626d8.4090...@kvr.at>
>>>> I'd strongly opt to change the KillMode as mentioned above.
>>>> #debian-devel seems to agree, so I'm upgrading this bug to RC.
>&g
Hi all,
On 2015-06-03 00:02, Cyril Brulebois wrote:
> Michael Biebl (2015-06-02):
>> Control: block -1 by 782475
>> Am 02.06.2015 um 18:11 schrieb Cyril Brulebois:
>>> libudev1-udeb depends on missing libcap2. I suspect the easiest would be
>>> to drop libcap2 support from the udeb build. An alte
Hi again,
On 2015-06-07 23:22, Cyril Brulebois wrote:
> Christian Kastner (2015-06-07):
>> Sorry for the delay, I was AFK until just now.
>>
>> I've prepared a quick upload consisting of only Matthias' patch, minus
>> the superfluous d/shlibs.local as discu
Hi again Philipp,
On 2014-12-17 18:00, Philipp Huebner wrote:
>> did anyone manage to get this tested? It's working fine for me, but my
>> pam_mount.conf is quite trivial.
>
> I can confirm that this new version fixes the problem.
would you be willing to upload the fix to DELAYED/5 so that we ca
On 2014-12-21 20:49, Michael Gilbert wrote:
> On Sun, Dec 14, 2014 at 11:02 AM, Christian Kastner wrote:
>> I just noticed that I never uploaded the debdiffs to the BTS, so here
>> they are for 1.8.11p2 in unstable and 1.8.10p3 in testing.
>
> I reviewed and sponsored your upl
the guest's root is mounted.
This is very unfortunate, as that file sets force-unsafe-io for dpkg,
so this puts the host at risk to data loss.
Regards,
Christian
>From c8e5aac84d1de20028e85ec236a4a998938bd361 Mon Sep 17 00:00:00 2001
From: Christian Kastner
Date: Sun, 11 Jan 2015 01:28:
On Sun, 11 Jan 2015 02:12:25 +0100 Christian Kastner wrote:
> adt-setup-vm creates /etc/dpkg/dpkg.cfg.d/autopkgtest on the host,
> instead of in the guest, because the path is missing the $root
> prefix pointing to the directory where the guest's root is mounted.
>
> This
Source: xymon
Version: 4.3.17-4
Severity: serious
Justification: Policy § 12.5
Hi,
The copyright information and the license terms for the files
lib/sha?.*
is missing from debian/copyright. The sha1.* files are public domain,
and the sha2.* files are BSD-3-clause licensed.
Package haskell-
Source: tellico
Version: 2.3.9+dfsg.1-1
Severity: serious
Justification: Policy § 12.5
Hi,
The copyright information and the license terms for the files
src/fetch/sha2.*
is missing from debian/copyright. They are BSD-3-clause licensed.
Package haskell-hashed-storage has these files, too. T
Source: darcs
Version: 2.8.5-1
Severity: serious
Justification: Policy § 12.5
Hi,
The copyright information and the license terms for the files
src/Crypt/*
is missing from debian/copyright. One file is "GPL" (no
version specified, and the others are BSD-3-clause licensed.
Package haskell-h
On 2015-01-18 13:52, Joachim Breitner wrote:
> Am Samstag, den 17.01.2015, 19:39 +0100 schrieb Christian Kastner:
>> The copyright information and the license terms for the files
>>
>> src/Crypt/*
>>
>> is missing from debian/copyright.
>
> I wonder: S
On 2015-01-18 15:09, Joachim Breitner wrote:
> Well, that’s how the files are distributed to Debian. But that doesn’t
> mean that Debian cannot re-license them all under the GPL... At least I
> thought that BSD code can generally be relicensed under the GPL.
Oh, now I understand what you mean.
Wh
1 - 100 of 168 matches
Mail list logo
