On Sat, Dec 08, 2018 at 09:41:03PM +0100, Mikhail Morfikov wrote:
>
> I think I have a similar (or the same) issue.
>
> Basically, when I lock the screen (via light-locker), the screen goes black,
> but it doesn't turn off. Keystrokes and mouse seem to dead because they don't
> turn the screen
Package: xwayland
Version: 2:1.20.3-1
Severity: important
Tags: patch upstream
Dear Maintainer,
This is a crasher that is present in xwayland for a long time and
has been fixed already upstream. I have locally built a debian patch
that includes the patches in the merge request linked below and
b...@debian.org wrote:
> quest to purge ash ;)
But who is supposed to fight the Evil Dead then?!
- Fabian
Hi Paolo,
thanks for your email. Unfortunately I cannot even try to reproduce it
since not all necessary files are provided. The doxygen_manual.tex tries
to include lots of files from ../html/... which are not available, so
compilation immediately finishes succesfully.
Also, it would be nice if
Control: reopen -1
Control: tags -1 help upstream
Control: forwarded -1 https://github.com/konstantint/intervaltree-bio/issues/8
Hi Paul,
On Sun, Jan 27, 2019 at 09:32:33PM +0100, Paul Gevers wrote:
> Thanks for picking this up so quickly, however...
>
> On 27-01-2019 00:39, Debian Bug Tracking
Control: tags 917700 + patch
Control: tags 917700 + pending
Dear maintainer,
I've prepared an NMU for dimbl (versioned as 0.15-2.1) and
uploaded it to DELAYED/14. Please feel free to tell me if I
should cancel it.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly
On 28.01.19 07:54, Paolo Greppi wrote:
Hi,
> thanks for the quick response.
> Inspired by the issue you forwarded to, I tried removing xcolor in
> the hope to find a workaround to make doxygen 1.8.15 build.
>
> Unfortunately I still get the same error (see attached files).
>
I boiled down the
Hi,
intrigeri:
> Helmut Grohne:
>> I've concluded that regardless of whether this is a bug in gcc, it is a
>> bug in libapparmor-dev. I think that putting static and dynamic
>> libraries in different directories is a recipe for breakage. You really
>> should put them in the same directory. That
On Mon, 14 Jan 2019 10:26:58 + Colin Watson wrote:
> Control: tag -1 pending
>
> Hello,
>
> Bug #904927 in debmirror 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:
>
>
Hi,
thanks for the quick response.
Inspired by the issue you forwarded to, I tried removing xcolor in the hope to
find a workaround to make doxygen 1.8.15 build.
Unfortunately I still get the same error (see attached files).
This either means that I miss some additional step (likely), or that
Hmm, moving the files out of the original directory structure and trying from
there works.
This gets weirder and weirder.
Package: installation-reports
Severity: normal
[email not working from system. This is cut and pasted from reportbug]
Dear Maintainer,
Since the system is unbootable, this may warrant higher severity.
After a seemingly successful installation the system would not start
because the pass phrase
On Monday 28 January 2019 04:53 AM, Jonas Meurer wrote:
...
> Hi Abhijith,
>
> a log would be very helpful.
>
> I tried to reproduce your bug recently, but failed to do so. For me, the
> template feature in postorius works as expected. Several lists on the
> list server in question have
Control: tags 919856 fixed-upstream
Norbert Preining wrote:
>> The exact cause would be there is an empty cache remained in
>> gnome-keyring-daemon. In my case, it is under:
> [...]
>> Attached is a Python script (I name it test_clear.py) to clear the cache
>> entry (your specific keygrip is
Sure thing! Sadly doesn't seem to make a difference. I've included another log,
this time starting from the time wpa_supplicant was brought back up to a little
bit after I got the popup that the connection had failed.
Thanks,
Diff
‐‐‐ Original Message ‐‐‐
On Saturday, January 26, 2019
Package: marisa
Version: 0.2.5-2+b1
Severity: minor
Marisa is dual licensed under BSD-2-clause and LGPL-2.1+. But the
license statement in debian/copyright says:
#+begin_example
License: BSD-3-clause or LGPL-2.1+
#+end_example
"BSD-3-clause" should be changed to "BSD-2-clause".
-- System
Hi Ralf,
> In fact, when I build ocaml-migrate-parsetree using pbuilder it builds
> fine. However If I build it with gbp buildpackage I get the error as
> described in the bug report.
I've just tried to reproduce it again, this time with gbp
buildpackage, in a clean debian:unstable docker image,
On Monday, 28 January 2019 2:26:00 AM AEDT Holger Schröder wrote:
> sorry, is not solved. next problem.
>
> docker run -it -u0 --rm alpine:latest
> docker: Error response from daemon: failed to start shim: exec:
> "containerd-shim": executable file not found in $PATH: unknown.
Apologies for
Package: orthanc-mysql
Version: 1.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
the above link now can build a preliminary debian package
hopefully this helps,
Jeff Cliff
Package: docker.io
Version: 18.09.1+dfsg1-3
Severity: important
Hi,
I cannot build docker image due to the following error. It looks like
there is some path related problem?
$ docker build .
Sending build context to Docker daemon 57.34kB
...
...
...
failed to start shim: exec:
Helmut Grohne writes:
> Thank you for applying my previous FTCBFS patch. We knew it was
> incomplete and now things improved a little as fltk1.3 moved away from
> freetype-config. Unfortunately, things don't just work yet.
Thanks for all your work on FTCBFS reporting, and sorry for the delayed
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "rmlint"
* Package name: rmlint
Version : 2.8.0-3
Upstream Author : Christopher Pahl
* URL : https://rmlint.readthedocs.io/
* License : GPL-3+
Anyone?
Package: caffe-cuda
Version: 1.0.0+git20180821.99bd997-2
Severity: normal
Dear Maintainer,
* What led up to the situation?
$ caffe time -model examples/mnist/lenet.prototxt -gpu 0
I0128 01:30:26.382874 7238 caffe.cpp:339] Use GPU with device ID 0
F0128 01:30:26.384541 7238 common.cpp:152]
Hello Jonas,
On 1/27/2019 7:59 AM, Jonas Smedegaard wrote:
Quoting Joseph Nahmias (2019-01-27 03:48:50)
Package: wnpp
Severity: wishlist
Owner: Joseph Nahmias
* Package name: radicale-auth-pam
Version : 0.2
Upstream Author : Joseph Nahmias
* URL :
This is now in NEW. There was a bit of a SNAFU on my side which might
have led to a different source in NEW and in the git repo, but I don't
think it should block inclusion - probably nothing significant.
This is now in NEW. I asked upstream to provide tagged releases and,
surprisingly, they did!
https://github.com/ivpusic/grpool/issues/10
so whoohoo! 1.0.0 packaged!
--
We know the road to freedom has always been stalked by death.
- Angela Davis
This is now in NEW.
The main challenge with this package is that it requires libgpgme to
build, but dependencies will likely need it to *run* as well, but
there's no good way to indicate this through the dependency system right
now.
For my purposes, it's not used by dmarc-cat - only .zip files
Ah, and I asked upstream to make an official release and, surprisingly,
they did!
https://github.com/proglottis/gpgme/issues/19
So 1.0 was packaged, wheepee!
--
Some believe it is only great power that can hold evil in check, but
that is not what I have found. It is the small everyday deeds
On 2019-01-27 19:49:08, Antoine Beaupré wrote:
> Ah, and I asked upstream to make an official release and, surprisingly,
> they did!
>
> https://github.com/proglottis/gpgme/issues/19
Ah no wait, I got confused with grpool:
https://github.com/ivpusic/grpool/issues/10
--
Il faut tout un village
Control: tags -1 +pending
The four dependencies of this package are now in NEW, with various
levels of "easiness".
I've uploaded this one to NEW as well, hopefully this will all go
through shortly and might even hit buster!
a.
--
La démocratie réelle se définit d'abord et avant tout par la
Control: tag -1 moreinfo
On Sat, 26 Jan 2019 20:03:49 + Toni wrote:
> Package: src:linux
> Version: 4.19.16-1
> Severity: critical
> File: linux-image-4.19.0-2-amd64
Is this a new problem with version 4.19.16-1? Or did it happen with
earlier versions as well?
> my laptop lasts a few hours
AFAIK upstream now supports (and requires) QT 5.1:
http://vmpk.sourceforge.net/#Requirements
Thank you for the report. This issue has been addressed upstream. The
fix to show full path names will be included in insserv 1.19.0, expected
to be released in early 2019.
- Jesse
Package: wnpp
Severity: wishlist
* Package name: sedsed
Version : 1.0
Upstream Author : Aurelio Jargas
* URL : http://aurelio.net/projects/sedsed
* License : MIT
Programming Lang: Python2
Description : sed script debugger
sedsed can debug, indent,
Hi Steve,
On 2019-01-27 15:56, Steve McIntyre wrote:
>
> Updated to say
>
> "Automatic account creation disabled to stop spammers signing
>up. Please contact $admin_private and describe what you want to do in
>the wiki."
>
> How does that sound?
Great news, I think this new message
Package: src:libpng1.6
Version: 1.6.36-3
Tags: ftbfs
Dear maintainer:
I tried to build this package in sid but it failed:
[...]
debian/rules build-arch
dh build-arch
dh_update_autotools_config -a
Source: ganeti-2.15
Version: 2.15.2-7+deb9u3
Severity: important
User: debian-ad...@lists.debian.org
Usertags: needed-by-DSA-Team
X-Debbugs-Cc: debian-ad...@lists.debian.org
As seen in Linux sources:
arch/alpha/include/uapi/asm/mman.h:#define MCL_CURRENT 8192 /* lock
all currently
Abhijith PA:
> Hi Pierre-Elliott Bécue
>
> On Tuesday 22 January 2019 05:46 AM, Pierre-Elliott Bécue wrote:
>> tags -1 + moreinfo
>>
>> Le lundi 21 janvier 2019 à 12:49:11+0530, Abhijith PA a écrit :
>>> Package: mailman3 Version: 3.2.0-4 Severity: important
>>>
>>> Hello.
>>>
>>> When creating
Package: git-annex
Version: 7.20190122-1
Followup-For: Bug #915333
Dear Maintainer,
This also happens on Marvel Kirkwood systems, e.g. a GoFlex NAS.
I suspect that this is a code generation problem further upstream and not
necessarily a git-annex specific problem and probably happens on all
I gave this bug a test run, performing a debootstrap both ways (as root
and in a fakeroot) and, on my test machine (Debian 9) with insserv
1.14.0, both methods work. That is to say, both chroot environments end
up with the init symbolic links in their etc/rc?.d/ directories.
This suggests to me
Source: ganeti-2.15
Version: 2.15.2-7+deb9u3
Severity: important
User: debian-ad...@lists.debian.org
Usertags: needed-by-DSA-Team
X-Debbugs-Cc: debian-ad...@lists.debian.org
Hi,
take this small C program:
#include
#include
#include
int main() {
printf("0x%x\n",
tags 919950 + patch pending
quit
Josh Triplett wrote:
> liblzma5 currently contains a compatibility hack for liblzma.so.2, which
> is the only thing pulling libdl into liblzma. liblzma.so.2 hasn't been
> in Debian since Squeeze, released in 2011; wheezy, released in 2013, has
> liblzma5. Please
tags 920575 + moreinfo
thanks
Hi Josh,
Thanks for the report. I'm afraid I'm finding it hard to parse in
the lofty abstract; can you perhaps share which package you are
refering to?
> (This lintian issue currently leads me to have a build wrapper script
> generating debian/copyright, rather
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "liboauth"
* Package name: liboauth
Version : 1.0.3-3
Upstream Author : Robin Gareus
* URL : http://liboauth.sourceforge.net/
* License : Expat
Package: autoconf-archive
Version: 20180313-1
Severity: normal
Tags: patch upstream
Forwarded: https://savannah.gnu.org/patch/index.php?9750
The PTHREAD_PRIO_INHERIT check can trigger a -Wunused-variable warning,
which can be turned into an error when -Werror is used, with the
consequence that
After a little more testing and research, I have found a workaround for
failures to create socket paths larger than the predefined size.
It seems rather silly, but it turns out that the size is not based on
the absolute, canonical file path. This means a simple symlink in
another location works
On Mon, 28 Jan 2019, Norbert Preining wrote:
> Umpf, you have broken the font installation by not calling dh_installtex
> or adding --with tex in the dh call.
Ok, I admit that it was broken before, too ;-) because the map files was
not installed properly. Still, the dh_installtex call, even if it
在 2019-01-28一的 07:29 +0900，Norbert Preining写道：
> On Mon, 28 Jan 2019, Norbert Preining wrote:
> > Umpf, you have broken the font installation by not calling dh_installtex
> > or adding --with tex in the dh call.
>
> Ok, I admit that it was broken before, too ;-) because the map files was
> not
On 27.01.19 21:45, Julian Gilbey wrote:
Hi,
according to my knowledge the bug /could/ have been solved in upstreams
git, but did not made it into Debian (probably not CTAN).
I'll test ASAP.
H.
> ~ $ texdoc -l number
> 47 results. Display them all? (y/N) y
> [and then lists just 46]
>
> On
Hi Boyuan,
On Mon, 28 Jan 2019, Norbert Preining wrote:
> Umpf, you have broken the font installation by not calling dh_installtex
> or adding --with tex in the dh call.
And you could have checked the git repository and provided a patched
based on the sources there, since the bug was fixed in
Hi
thanks for your work on this, but ...
On Sun, 27 Jan 2019, Boyuan Yang wrote:
> Please review the changes and fix it in a new upload if necessary.
Umpf, you have broken the font installation by not calling dh_installtex
or adding --with tex in the dh call.
Please at least *try* out the
On Sun, Jan 27, 2019 at 09:28:56PM +, Alain Ducharme wrote:
> To be clear: I don’t have a problem with Firejail being a setuid executable
> (perhaps a little trepidation ;-), I have an issue with the default broad
> powers granted to unprivileged users with the install of the Firejail
Hi,
Repeating what I posted on bug 920408:
I've posted this on the mate-utils issue you linked to:
It doesn't have to use multicore. Going to the gsearchtool/help/pt directory
and repeatedly saying
itstool -m pt.mo ../C/index.docbook ../C/legal.xml
will eventually cause an exception in
Hello.
The attached patch works around this bug in python-igraph.
The issue should probably be fixed globally by adding 'm'
in package python3-stdlib-extensions
in filedebian/patches/3.7/distutils-install-layout.diff
in line'headers': '$base/include/python$py_version_short/$dist_name'
Package: webext-ublock-origin
Version: 1.18.2+dfsg-1
Severity: important
ublock origin version 1.18.2+dfsg-1 fails to display the list of
blocked or existing hosts which you can see when you toggle "all". There is no
indication that the addon blocks any content at the moment. All the
menus appear
Package: src:linux
Version: 4.19.12-1
Severity: wishlist
I would like to use an ARM64 system as an AX.25 node. Could you please
enable CONFIG_HAMRADIO and the associated modules?
ARM64 kernels currently have this:
# CONFIG_HAMRADIO is not set
AMD64 kernels have these options:
On Sun, Jan 27, 2019 at 09:57:05PM +0100, Andrej Shadura wrote:
> Any news on this? Do you need any help maybe?
I've just uploaded it (the pending issue I had was to include all the
fixed bugs), so this reminder actually helped :-)
Minor comment: I've had to add a debian/clean file containing
Package: fluidsynth
Version: 1.1.11-1
Severity: wishlist
The fluidsynth project has released a new major version; they are currently on
2.0.3 as of this bug report.
I hope the whole fluidsynth package ecosystem (e.g. libfluidsynth,
libfluidsynth-dev) will soon be upgraded to this version.
--
Hi,
Daniel Kahn Gillmor:
> On Sun 2018-10-07 10:31:13 +0200, intrigeri wrote:
>> intrigeri:
>>> What matters to me is the users' perspective. I think we should
>>> provide a clear, unambiguous transition path and avoid leaking
>>> technical details to users. So once MAT2 reaches feature parity
reassign 899298 golang-1.11-src
found 899298 1.11.5-1
reopen 899298
thanks
This bug was closed when golang 1.10 was removed from Debian, but the
bug is present, and it is at least affecting x/tools.
The golang-X.Y-src packages, which provide /usr/share/go-X.Yapi/, should
also ship a symlink in
Package: wine
Version: 3.0.3-2~bpo9+1
Severity: normal
Dear Maintainer,
I am using wine 3.0.3 from stretch-backports.
With the latest update (v1.6.0) of the reMarkable desktop GUI, the upgrade
breaks on an unimplemented function.
https://remarkable.com
https://remarkable.engineering
Wine
Gürkan Myczko wrote:
> Hi Yavor many thanks would you mind doing a pr for that on github?
I don't have a GitHub account and don't plan to make one at least
until it is possible to do it off the web, with one of the cli tools
that are available.
I can send you the modified .gorm file in private
Hans-Christoph Steiner writes:
> this also goes the other way, where tarballs created in tar 1.30 fail to
> work in pristine-tar when tar 1.29 is installed:
Unfortunately, the nature of pristine-tar is such that it's somewhat
brittle in the face of upstream changes to tar.
I don't think it's
Hi,
On Sat, 29 Dec 2018 at 17:27, Andrej Shadura wrote:
>
> On Sat, 29 Dec 2018 at 17:17, Santiago Vila wrote:
> >
> > On Tue, Dec 11, 2018 at 11:30:59AM +0100, Andrej Shadura wrote:
> > > Package: indent
> > > Version: 2.2.11-5
> > > Severity: normal
> > >
> > > Indent 2.2.12 has been released
Hello Reiner,
Thanks for your response.
To be clear: I don’t have a problem with Firejail being a setuid executable
(perhaps a little trepidation ;-), I have an issue with the default broad
powers granted to unprivileged users with the install of the Firejail package.
> I think the most common
Hi,
Jonas Meurer:
> I'll see whether I find time during the next days to work out something
> for option a, but I have my doubts that we'll make it in time for Buster.
Thanks a lot for your work on this!
I'll reply on #910493.
Cheers,
--
intrigeri
On Wed, Feb 16, 2011 at 12:02:15PM -0500, Daniel Kahn Gillmor wrote:
> On 02/16/2011 11:32 AM, Moritz Mühlenhoff wrote:
> > I would propose to either skip the "basic" test suite if the length of pwd
> > is
> > below a threshold or to run the testsuite in
> > (mktemp -d /tmp/mstest.X)
Control: reassign -1 bind9
Control: user pkg-apparmor-t...@lists.alioth.debian.org
Control: usertag -1 + modify-profile
Control: tag -1 + moreinfo
Hi,
Vroomfondel:
> […] However in its currently shipping
> form this broke the bind DLZ that's used with samba (to host DNS for active
>
在 2019-01-27日的 16:01 -0500，Boyuan Yang写道：
> Control: tags 492932 + patch
> Control: tags 492932 + pending
>
> Dear Debian TeX Maintainers,
>
> I've prepared an NMU for context-nonfree (versioned as 2007.03.22-1.1) and
> uploaded it to DELAYED/10.
>
> This upload fixes Bug #492932.
>
> Besides,
Hello everybody,
Georg Faerber:
> Short update on this:
>
> - python-nautilus 1.2.2-1 was uploaded to unstable some days ago.
>
> - Therefore, in theory, we could now ship and install the Nautilus
> extension.
>
> - I just tried to do so, however, it seems, that currently
> python-nautilus
Control: tags 920135 help
buster will ship with gradle v4.4.1, so 5.x support might break things.
But patches welcome for supporting the gradle version that buster will
ship with. As far as I'm concerned, this is LowNMU.
forwarded 920621 https://github.com/tabu-fixed/tabu/issues/1
stop
On 27.01.19 15:37, Paolo Greppi wrote:
> I am preparing the next relase of doxygen (1.8.15).
>
> Last week it built fine with texlive-base 2018.20181214-1.
> I tried today with 2018.20190126-1 and it fails.
>
> You can see the
Control: tags 920134 help
I've never used zsh in my life, so I wouldn't know how to do this, or
test it. Patches welcome! As far as I'm concerned, this is LowNMU.
Package: ntopng
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu disco ubuntu-patch
Version: 3.8+dfsg1-2
Severity: serious
Tags: patch
Hello, I'm filing this bug as serious, even if the build failure is not
experienced in Debian builds, just by luck.
Problem is that the embedded
this also goes the other way, where tarballs created in tar 1.30 fail to
work in pristine-tar when tar 1.29 is installed:
https://salsa.debian.org/python-team/modules/libcloud/-/jobs/115815
Package: lintian
Version: 2.5.123
Hi,
I patched a appdata.xml file.
Lintian now warns about a licensing mismatch, not because of the file
itself, but because the *quilt working directory* has a copy that
doesn't match the path in debian/copyright:
IW: ballz source:
Control: tags 492932 + patch
Control: tags 492932 + pending
Dear Debian TeX Maintainers,
I've prepared an NMU for context-nonfree (versioned as 2007.03.22-1.1) and
uploaded it to DELAYED/10.
This upload fixes Bug #492932.
Besides, this NMU also acts as a clean-up upload since context-nonfree
On Sun, Jan 27, 2019 at 08:28:41PM +, Brian Potkin wrote:
>On Sun 27 Jan 2019 at 17:56:34 +, Steve McIntyre wrote:
>
>> On Sun, Jan 20, 2019 at 04:22:41PM -0800, Tassia Camoes Araujo wrote:
>> >Hi folks,
>> >
>> >I would add to the issue the portion of the message that says "from some
>>
On Fri, Jan 25, 2019 at 10:52:34PM +0100, Hilmar Preuße wrote:
> On 29.11.18 11:06, Julian Gilbey wrote:
>
> Hi Julian,
>
> > texdoc -l number
> > reports:
> > 44 results. Display them all? (y/N)
> > but then only lists 43 results. Either the displayed count is wrong or
> > the final result is
Hello Nye,
Nye Liu [2019-01-23 14:16 -0800]:
> Please apply https://github.com/systemd/systemd/pull/11527
It's in the pipeline now, I need to sort out some git paperwork issue with
Felipe. But either way, I'll upload the fix tomorrow.
(Sorry, just back from meeting/devconf.cz week with
Control: severity -1 minor
Guten Abend Christian, hi again everyone!
(some AppArmor stuff first, then a question for the CUPS folks)
Christian Boltz:
> My guess is that John meant something like that:
> /etc/cups/** Cx -> trap,
> profile trap {
> # intentionally left empty
> }
Ah,
Source: tox
Version: 3.7.0-1
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Dear maintainers,
With a recent upload of tox the autopkgtest of tox fails in testing when
that autopkgtest is run with the binary packages of tox from unstable.
It passes
Hi Andreas,
Thanks for picking this up so quickly, however...
On 27-01-2019 00:39, Debian Bug Tracking System wrote:
> #920545: python-intervaltree breaks python-intervaltree-bio autopkgtest
the test now fails with the following error, which seems to result from
the fact that you patched a test
Hi,
On 27/01/2019 20:39, Juan Picca wrote:
> Package: gargoyle-free
> Version: 2011.1b-1
> Severity: wishlist
> Tags: upstream patch
>
> Dear maintainer,
>
> Currently the ash shell is not widely used and was superseded by dash
> shell in debian.
> The attached patch replace it with dash shell.
>
Source: libgd2
Version: 2.2.5-5
Severity: grave
Tags: security upstream
Justification: user security hole
Control: found -1 2.2.4-2+deb9u3
Control: found -1 2.2.4-2
Hi,
The following vulnerability was published for libgd2.
CVE-2019-6977[0]:
| gdImageColorMatch in gd_color_match.c in the GD
Hi Toni. I have an XPS 15 9570, which, I think, is basically the same
machine, except yours uses an NVIDIA Quadro vs my GeForce GTX 1050Ti as a
2nd graphics card.
A lot of problems with that secondary graphics card and linux. Are you
attempting to use it via Bumblebee?
See this thread (and
Control: reassign 818115 src:sphinx 1.4.9-2
Control: merge 818115 -1
Control: close -1
On Sat, Jan 26, 2019 at 05:50:13PM +0100, Helmut Grohne wrote:
> Hi Dmitry,
>
> On Sat, Jan 26, 2019 at 12:55:28AM +0300, Dmitry Shachnev wrote:
> > So I cannot promise that I will take care of half of those
Package: ash
Severity: wishlist
Dear maintainer,
According the description of the ash package, it is a compatibility
package awaiting that /bin/ash be not longer used for delete it.
With the close of bug 919992, no package depends of ash in sid.
Also, according codesearch, only a fews packages
Control: severity -1 minor
Control: tag -1 + upstream
Control: forcemerge -1 918548
Rationale for the metadata changes:
- This bug is about a given proposed solution to a broad class
of problems.
- Bumping severity to minor, as the lack of a solution to this
problem may lead to
I think this bug does qualify as RC since it can affect any source
tarball that was created with an older version of tar. So it is not
just that it comes from a different distro/release than buster, but it
could be from a package that has a source tarball that hasn't changed
since tar 1.30.
Package: mariadb-server-10.3
Version: 1:10.3.12-2
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
Upgrade to latest mariadb package on debian testing; within lxc continer.
Previous package was working fine...
on the container
Hi,
(Meta: here I'm wearing my "maintainer triaging a newly filed RC bug"
hat; once this is done, if the resulting severity is high enough, I'll
spend some time thinking about solutions.)
Jamie Strandboge:
> I don't have all the context since the bug only has part of the thread, but I
> can say
Package: gargoyle-free
Version: 2011.1b-1
Severity: wishlist
Tags: upstream patch
Dear maintainer,
Currently the ash shell is not widely used and was superseded by dash
shell in debian.
The attached patch replace it with dash shell.
When ash shell be removed of all scripts using it, the ash
Hi Mike,
I've posted this on the issue you linked to:
It doesn't have to use multicore. Going to the gsearchtool/help/pt directory
and repeatedly saying
itstool -m pt.mo ../C/index.docbook ../C/legal.xml
will eventually cause an exception in itstool. So then the question becomes,
what is this?
Source: linux
Version: 4.19.0-1-amd64
Severity: important
Dear Maintainer,
Reading from a cifs share "smb encrypt = mandatory" hangs the Application,
however ls and writing files works without porblem.
I dont have these Problems with linux 4.18.0-3.
Steps to reproduce:
1. Setup an samba server
Package: gcc-msp430
Version: 4.6.3~mspgcc-20120406-7.1
Severity: normal
Dear Maintainer,
Please consider updating the package to Texas Instruments' sources.
The current version is 4.6.3, while TI maintains an updated version
based on GCC 7.3.1
Here's a link to TI's GCC compiler:
Hi,
On Sun, Jan 27, 2019 at 09:12:58PM +0200, Adrian Bunk wrote:
> > Jup, replacing python3 with python3.6 makes this work
>
> For some reason the problem seems to be 32bit-only now:
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/lightproof.html
Not really. Still fails
Santiago,
On 06/01/2019 00:14, Santiago Vila wrote:
> I tried to build this package in buster but it failed:
I have investigated the issue. It seems to be due either to changes in
golang or in the x/tools package, I will do some more tests, and hope to
fix it soon.
--
Martín Ferrari (Tincho)
1 - 100 of 242 matches
Mail list logo
