Package: debootstick
Version: 2.1
Severity: important
Dear Maintainer,
I'm running the Buster and, due to a recent (and reckless) change
in the LVM, creating an image takes forever on a host which has
LVM setup. What happens is that all LVM programs try to get some
information from udev, but
Package: wnpp
Severity: wishlist
* Package name: ghidra
Version : ?
Upstream Author : NSA
* URL : https://github.com/NationalSecurityAgency/ghidra
* License : Apache-2
Programming Lang: Java
Description : Ghidra is a software reverse engineering (SRE)
Arthur D.:
> Thanks for great answer. You really helped a lot!
>
>> Can you tell a bit about where you expected this to be documented? I.e.
>> where would you have found it if it had been documented?
>
> Personally I tried to find some info about the issue using these commands:
> man dh
> man
On Wed, Mar 06, 2019 at 06:33:00AM +, Niels Thykier wrote:
> I am sorry to hear that you are sad by this. To be honest, I had
> expected you were informed about this already.
>
> This was requested in #922826 with the argument that our live image
> builds no longer worked and that it was too
Package: debootstick
Version: 2.1
Severity: wishlist
Dear Maintainer,
I would like to create bootable images with more than just
rootfs, i.e. to include several partitions. How would you find
such a feature?
Best regards,
Dejan
-- System Information:
Debian Release: buster/sid
APT prefers
Hi Cyril,
On Sun, 2019-03-03 at 17:24 +0100, Cyril Brulebois wrote:
>
> > My complete Debian installation is on an iSCSI target. So for
> booting I
> > use U-Boot to start iPXE (snp.efi), which loads grubaa64.efi from
> the
> > iSCSI target.
> >
> > As I am booting from an iSCSI target the
Package: ruby-rjb
Version: 1.5.5-3
Severity: important
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu disco
Hi Chris,
Since March of last year, the autopkgtests for ruby-rjb have been failing.
The oldest available log on ci.debian.net is for 1.5.5-3, which fails with:
[...]
Control: reassign -1 vsftpd
> Hi there,
> vsftpd does not use libgcrypto directly. From the ldd log, libcrypto
> is from openssl (no "g").
> I think this issue should be fixed from PAM.
> From
> https://www.gnupg.org/documentation/manuals/gcrypt/Initializing-the-library.html:
>
Lars Wirzenius:
> On Tue, Mar 05, 2019 at 07:24:03PM +, Debian Bug Tracking System wrote:
>> Added tag(s) bullseye and sid.
>
> Does this mean buster is going to be released with vmdebootstrap? This
> would make me sad. Why is this? I'm not going to spend any time to fix
> vmdebootstrap. I'd
On Mon, 4 Mar 2019 at 20:03, Giorgi Modebadze
wrote:
>
> Package: vsftpd
> Version: 3.0.3-8+b1
>
> Whenever a client connects to vsftpd, Libgcrypt seems to complain. Output in
> syslog:
>
> > vsftpd: Libgcrypt warning: missing initialization - please fix the
> > application
>
>
> Dependencies
On Tue, Mar 05, 2019 at 07:24:03PM +, Debian Bug Tracking System wrote:
> Added tag(s) bullseye and sid.
Does this mean buster is going to be released with vmdebootstrap? This
would make me sad. Why is this? I'm not going to spend any time to fix
vmdebootstrap. I'd really rather nobody else
Sent from Mail for Windows 10
Sent from Mail for Windows 10
On Wed, 6 Mar 2019 04:11:41 +0100
Matija Nalis wrote:
...
> "Severity: important" would indicate that package is just one small
> step away from "rendering it completely unusable to everyone", which
According to the documentation, "important" denotes:
"a bug which has a major effect on the
On Tue 2019-03-05 18:48:11 +0100, Santiago Vila wrote:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907191
ugh :(
> I'll take a look at the kernel feature to see if it's better than this.
fwiw, the change isn't in the kernel -- it's in how userspace talks to
the kernel to get its
Re: https://bugs.debian.org/850269:
I'm closing this bug report against gpgme because the underlying problem
was solved in libgcrypt. There isn't really a version of gpgme which
fixes the problem (the tests do apparently use --debug-quick-random in
1.8.1, but with the updated gcrypt that won't
great, i never received
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919442#39 in my
mailbox :(
On Sat, Feb 9, 2019 at 6:05 PM Sandro Tosi wrote:
>
> On Sat, Feb 9, 2019 at 6:04 PM Sandro Tosi wrote:
> >
> > On Thu, Feb 7, 2019 at 11:24 AM Andreas Beckmann wrote:
> > >
> > > Followup-For:
severity 662960 wishlist
thanks
The bug have been added tag "security", which is in sync with its TLS
deficiencies. However (as you noticed) "Severity" values (while they
might look innocently like plain English) have quite specific meanings
in BTS, which sometimes might be at odds with their
control: reassign -1 libdrm-amdgpu1
On Sat, Feb 23, 2019 at 7:33 AM Siyia brb wrote:
>
> kernel parameter "amdgpu.audio=0" was responsible for the flickering i
> removed it updated grub and no screen flickering
> its is important to note that i am using an active dvi-d to vga monitor setup
Hi Arnaud,
Thanks for the summary.
On Wed, Mar 6, 2019 at 9:51 AM Arnaud Rebillout
wrote:
>
> Dear Go team,
>
> So let met sum up this bug now to avoid you reading the backlog:
>
> In short, docker doesn't recognize the output of `runc --version`, and
> then it misbehaves and flood the log
> On Mar 5, 2019, at 7:50 PM, Arnaud Rebillout
> wrote:
>
> Dear Go team,
>
> So let met sum up this bug now to avoid you reading the backlog:
>
> In short, docker doesn't recognize the output of `runc --version`, and
> then it misbehaves and flood the log forever. To be more accurate,
>
Package: finish-install
Version: 2.100
Severity: minor
Noticed while committing other changes in finish-install.d/90console -
it still has support in here for upstart (for setting up serial
console). I've left this along for now, but adding this bug as a
reminder to look again in future.
On Mon, 04 Feb 2019 11:16:29 +0200 Adrian Bunk wrote:
> Fix:
>
> --- debian/rules.old 2019-02-04 09:12:02.674701984 +
> +++ debian/rules 2019-02-04 09:13:52.286700939 +
> @@ -9,6 +9,10 @@
> # Astropy-affiliated packages do.
> export PYBUILD_AFTER_INSTALL := find {destdir} -name
Hi all,
did someone checked
https://git.xiph.org/?p=libao.git;a=commit;h=d5221655dfd1a2156aa6be83b5aadea7c1e0f5bd
?
Elimar
--
We all know Linux is great... it does infinite loops in 5 seconds.
-Linus Torvalds
signature.asc
Description: PGP signature
On Sat, Jan 26, 2019 at 11:17:35PM +0100, Andreas Beckmann wrote:
> I think I now understood what is happening here.
> Both python3 and dicoweb are being installed in the same run.
> At the time python3 gets configured, dicoweb is already unpacked, but
> not yet configured and therefore
Dear Go team,
So let met sum up this bug now to avoid you reading the backlog:
In short, docker doesn't recognize the output of `runc --version`, and
then it misbehaves and flood the log forever. To be more accurate,
docker is not happy because it wants to know the git commit that was
used to
On Wed, Feb 27, 2019 at 04:58:51PM +0100, Matthias Klose wrote:
> This has to be fixed on the dico side. One possible solution is to guard the
> import and fall back to some defaults, either provided inline, or using a
> defaults config file shipped in /usr/lib/... This way the package can be
>
Understood. I noted today that even nvidia-current was not able to
build the dkms module against 5.0, so this is really not urgent. -- sRw
On 3/5/19 7:25 PM, Andreas Beckmann wrote:
Control: tag -1 upstream
On 2019-03-05 18:49, S R Wright wrote:
The latest version of
Control: tag -1 upstream
On 2019-03-05 18:49, S R Wright wrote:
> The latest version of nvidia-legacy-340xx-kernel-dkms has build errors
> when built against the latest 5.0 kernel source.
I will not investigate this before Linux 5.0 has reached experimental
and hope for a new ustream release
On Tue, 5 Mar 2019 23:26:58 +0100
Matija Nalis wrote:
> Hi Celejar,
>
> you have raised severity to "serious" on ssmtp Debian package
> in bug #662960, which is reserved for "Serious policy violations" as
> described at https://www.debian.org/Bugs/Developer#severities
>
> It is customary to
eclipse-titan (6.5.0-1) unstable; urgency=high
* New release.
+ Upstream fixed the GCC version issues (Closes: #879816)
No! you need to fix the packaging, why don't you do it?
Package: eclipse-titan
Version: 6.5.0-1
Depends: [...] gcc (>= 4:8.2.0), gcc (<< 4:8.2.0.0), [...]
Package: mat2
Version: 0.8.0-3
Severity: normal
(Follow-up for #858204)
We should ensure that the Nautilus extension is in fact available and
working, if Nautilus get started.
Cheers,
Georg
signature.asc
Description: Digital signature
Upon manually deleting the directory and re-installing the package, I
see some surprising omissions that I expect are due to third-party
packages installing their own scripts into the
/usr/share/bash-completion/completions folder instead of into
/etc/bash_completion.d/ . Does that need to be
Package: redmine
Version: 4.0.1-1
Severity: grave
Justification: renders package unusable
Upgrading to 4.0.1-1 produces the following output.
root@mail:/etc/apt# dpkg --configure -a
Setting up redmine (4.0.1-1) ...
Determining localhost credentials from /etc/mysql/debian.cnf: succeeded.
I forgot: This could also be a bug in javadoc/openjdk and not in elki.
Note that the package also fails in stable:
https://tests.reproducible-builds.org/debian/logs/stretch/i386/elki_0.7.1-3.build2.log.gz
If you reassign, please use "affects 923841 src:elki" so that this bug
is still shown in
Package: parcellite
Version: 1.2.1-3
Severity: normal
Tags: a11y
Dear Maintainer,
when I start parcellite in openbox it gives the following error
Flag 0x0001, status 256, EXIT 1 STAT 1
Unable to open fifo '/home/XXX/.local/share/parcellite/fifo_p' No such device
or address
Unable to open fifo
Package: src:elki
Version: 0.7.1-10
Severity: serious
Tags: ftbfs patch
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --buildsystem=maven
Package: bash-completion
Version: 1:2.8-6
Severity: normal
Dear Maintainer,
Performing an 'apt-get purge bash-completion' does not delete the folder
/usr/share/bash-completion.
Over time, that folder has accumulated what is now cruft, because when
that package updates, it does not remove
On Tue, Mar 5, 2019 at 12:35 PM procmem wrote:
> I stand corrected its in your version since you cherry picked the patch.
Yes. Could you verify whether that version fixes your issue?
Thanks,
Jeremy Bicha
Control: reassign -1 src:grub2
Control: severity -1 minor
Control: affects -1 shim-signed
Control: retitle -1 efibootmgr should only be called if changes are needed
Thanks for reporting this issue.
The problem here is not a bug in shim-signed, which is merely making the
necessary calls to ensure
Hi,
On 17-03-19 19:19:17, intrig...@debian.org wrote:
> Debian bug #858058 was a security issue: the "Clean metadata" action
> in the Nautilus contextual menu *silently* failed to do anything
> useful, due to a tiny programming error + lack of appropriate QA.
>
> I think should have automated
On Tue, 5 Mar 2019 23:39:00 +0100
Michael Biebl wrote:
> Strictly speaking, we should only need either --notify-await when
> starting the daemon via s-s-d, or --wait-daemon when calling udevadm
> trigger. Using both probably doesn't hurt, but isn't really necessary.
correct, actually only the
Hi Bart,
> Are you aware that the file debian/not-installed was added? I doubt that this
> was intentional.
I do not know if you can help me, but when I go to debuild[1] my package, this
warning
occurs.
[1] https://paste.debian.net/1071745
I followed the options debuild offered me.
Thanks!
On Tue, 2019-03-05 at 16:27 -0500, Phillip Susi wrote:
> On 3/5/2019 10:58 AM, Kevin Locke wrote:
>> Sounds great. How do you propose that the kernel determine the
>> optimal alignment?
>
> md does it using the stripe size. Not sure if anything other the md or
> dm would make sense to populate
Control: reassign -1 insserv
On Thu, 28 Feb 2019 19:13:31 -0300 Felipe Sateler
wrote:
> On Thu, Feb 28, 2019 at 6:50 PM Michael Biebl wrote:
> >
> > Am 28.02.19 um 14:08 schrieb Michael Biebl:
> >
> > >> Since initramfs-maintainer says, that initramfs-tools do not invoke
> > >> insserv, another
Am 05.03.19 um 22:40 schrieb Trek:
> On Tue, 5 Mar 2019 09:46:53 +0100
> Andreas Henriksson wrote:
>
>> You likely also want to include in your patch a debian/control
>> change that makes udev depend on a new enough dpkg which has the
>> new flags you're making use of.
>
> right, a new patch is
Hi Celejar,
you have raised severity to "serious" on ssmtp Debian package
in bug #662960, which is reserved for "Serious policy violations" as
described at https://www.debian.org/Bugs/Developer#severities
It is customary to indicate exactly which section of Debian policy
Manual (at
(Not release team)
Iain Lane wrote:
I should have uploaded this with a higher urgency probably
That wouldn't have done anything: urgencies have been ignored since soft
freeze.
some quite nice
fixes
Are any of them Important or higher?
On Tue, 5 Mar 2019 09:46:53 +0100
Andreas Henriksson wrote:
> You likely also want to include in your patch a debian/control
> change that makes udev depend on a new enough dpkg which has the
> new flags you're making use of.
right, a new patch is attached
thank you!diff --git a/debian/control
Hi Carlos,
About this package at mentors:
Version:0.3.5-4
Uploaded: 2019-03-03 08:05
Source package:
https://mentors.debian.net/debian/pool/main/j/jag/jag_0.3.5-4.dsc
Are you aware that the file debian/not-installed was added? I doubt that this
was intentional.
|
Package: shim-signed
Version: 1.28+nmu1+0.9+1474479173.6c180c6-1
Severity: critical
Justification: breaks the whole system
While running a normal apt-get dist-upgrade, setup of the package
failed:
>...
>shim-signed (1.28+nmu1+0.9+1474479173.6c180c6-1) wird eingerichtet ...
>x86_64-efi wird für
Hello Pedro,
Am 05.03.19 um 15:14 schrieb Pedro Pena:
> Hello Markus,
>
> I have been able to remove the majority of the warnings that appear.
> Unfortunately I can not seem to get lintian to show me the same errors
> locally. I have to upload to mentors.debian.net to see the warnings.
>
> I
I have the same problem on about 10 rasbperry-pi installations.
Linux moni 4.14.98-v7+ #1200 SMP Tue Feb 12 20:27:48 GMT 2019 armv7l
GNU/Linux
ss utility, iproute2-ss161212
Has anyone found at least a workaround?
I don't want to disable rkhunter hidden_ports test, but those false
positive
block 460404 326647
tags 460404 moreinfo
thanks
> Running fsck on battery should be configurable, e.g. by some option
> in /lib/init/vars.sh. For an ext2 filesystem it is fatal to ignore a
> fsck, esp. since there is a higher risk for laptops. They either run
> out of power, or they are just shut
Source: ghostwriter
Version: 1.7.4-1
Severity: normal
Dear ghostwriter maintainer,
When trying to clone the Vcs repository using the content of Vcs-Git field, I
encountered the following error:
% LANG=C git clone https://gitlab.com/ghostwriter-deb.git
Cloning into 'ghostwriter-deb'...
fatal:
Source: ghostwriter
Version: 1.7.4-1
Severity: normal
Dear ghostwriter maintainer,
As indicated by lintian, you documented file
resources/linux/ghostwriter.appdata.xml as licensed under GPL-3.0+ yet the
content of this file indicates that it is licensed under CC-BY-SA-4.0. Please
fix this issue
reassign 923746 sysctl
thanks
Thank you, and apologies for the noise.
int0 is the LAN interface, on which dnsmasq serves both ipv4 and ipv6
requests for dns and dhcp.
he-ipv6 is the tunnel out to the world (via ext0).
You are correct that dnsmasq is correctly advertising the int0 mtu
On 3/5/2019 10:58 AM, Kevin Locke wrote:
> Sounds great. How do you propose that the kernel determine the
> optimal alignment?
md does it using the stripe size. Not sure if anything other the md or
dm would make sense to populate the value. Well, I guess hardware raid
drivers.
> I disagree
Package: ftp.debian.org
Please remove libsmali-1-java from sid, it has been replaced by
libsmali-java.
signature.asc
Description: OpenPGP digital signature
Package: ftp.debian.org
androguard is now pure Python and architecture independent (the tests
don't pass on big-endian, but that's a separate issue).
Please remove these packages from sid:
* androguard 3.1.0~rc2-1 [debports]: alpha m68k powerpcspe sh4 x32
* androguard 2.0-3 [debports]: hppa
Control: reassign -1 javahelper
Control: retitle -1 javahelper: javadoc: error - The code being documented uses
packages in the unnamed module
Am 05.03.19 um 21:06 schrieb Andreas Tille:
[...]
> Considering that the problem can be solved by fixing javatools instead
> of libhac-java do you think
On Tue, Mar 05, 2019 at 06:46:51PM +0100, Roland Gruber wrote:
> About #923736 it seems the link is wrong. LDAP Account Manager depends
> on TCPDF.
So then you should formally adopt it and take care of all security issues
which affect it during the buster lifecycle.
Cheers,
Moritz
Hi,
On 19-01-09 19:16 +0100, Cristian Ionescu-Idbohrn wrote:
> It redirects to streaming-loadbalancer.ur.se/loadbalancer.json
> (130.242.59.74), which seems to be _the real problem_ (supports _only_
> TLS 1.0/SSL3). loadbalancer.json is just one line (with no line
> terminators):
>
>
tags 585398 moreinfo
thanks
> Could you please provide a way for me to tell sysv-rc to keep its hands
> off my configuration as I'm not using sysvinit and would rather keep it
> that way? Alternatively, make it not try to convert on each upgrade,
> but just try once.
> I think this is pointing
Package: hatari
Version: 2.2.0+dfsg-1
Hatari release v2.2 has buggy UNPK instruction emulation,
which is a regression from the previous release.
Hatari v2.2.1 with the regression fix was released week later:
https://git.tuxfamily.org/hatari/hatari.git/log/?h=v2.2.1
Please update Hatari v2.2 to
Am 05.03.19 um 18:17 schrieb Mark Hindley:
> On Tue, Mar 05, 2019 at 05:58:30PM +0100, Michael Biebl wrote:
>> Am 05.03.19 um 15:34 schrieb Mark Hindley:
>>>
>>> reassign -1 elogind
>>> retitle -1 Make libelogind0 ABI compatible with libsystemd0
>>> tags -1 + pending
>>> thanks
>>>
>>> On Wed, Feb
On Tue, Mar 05, 2019 at 02:02:05PM +0100, Markus Koschany wrote:
> ...
> Maybe we should change our javadoc policy too. Developers shall not
> build-depend on other -doc packages by default and override jh_build if
> they wish to link against external packages. This way they have more
> fine
Package: g++-6
Version: 6.3.0-18+rpi1+deb9u1
Severity: important
Dear Maintainer,
* What led up to the situation?
I have been using raspicam on a raspberry PI 3 B+. doing some development work.
recompiling a working program begain giving me invalid strtab errors.
* What exactly did you
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package pyfr
diff -Nru pyfr-1.5.0/debian/changelog pyfr-1.5.0/debian/changelog
--- pyfr-1.5.0/debian/changelog 2018-05-20 06:47:05.0 +0200
+++
Hello All,
as was suggested ( by Timo I think ) using the --no-ntp option fixed this for
me some time ago now.
I had no further problems with the laptops enrolled as freeipa-client.
Further updates in Debian Buster caused no issues.
Greetings, J
--
Deze e-mail en alle documenten die
On Sun, Jan 20, 2019 at 07:19:00AM +, Ximin Luo wrote:
> I can't reproduce this, can you install cargo-dbgsym rustc-dbgsym rust-gdb
> libstd-rust-1.31-dbgsym libllvm7-dbgsym libc6-dbg and provide a backtrace?
I can reliably reproduce this, and I think I've figured out the
distinguishing
severity 923830 important
thanks
retitle 923830 libnet-jabber-bot-perl: FTBFS randomly (failing tests)
thanks
Note: Downgrading because this is really random for me.
(But apparently not in reproducible-builds.org)
Thanks.
Package: src:libnet-jabber-bot-perl
Version: 2.1.5-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
CDBS WARNING:
Package: src:golang-github-posener-complete
Version: 1.1+git20180108.57878c9-3
Severity: important
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
Package: src:starlet
Version: 0.31-1
Severity: important
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep
Package: src:libdancer2-plugin-database-perl
Version: 2.17-1
Severity: important
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep
Package: src:ruby-riddle
Version: 2.3.1-1
Severity: important
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --buildsystem=ruby
Package: src:golang-github-ivpusic-grpool
Version: 1.0.0-1
Severity: important
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep
Package: src:golang-github-hashicorp-raft
Version: 1.0.0+git20180823.82694fb-3
Severity: important
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
Package: src:golang-gopkg-mcuadros-go-syslog.v2
Version: 2.2.1-1
Severity: important
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh
Package: src:python-blessed
Version: 1.15.0-1
Severity: important
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules binary-indep
dh binary-indep --with
Package: src:python-zake
Version: 0.2.2-2
Severity: important
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
pyversions: missing
Package: src:golang-github-google-martian
Version: 2.1.0+git20181219.d0b5ad3-2
Severity: important
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
Package: src:multiverse-core
Version: 0.7.0-4
Severity: important
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --with javahelper
Hi Daniel,
On Fri, Mar 1, 2019 at 4:12 AM Daniel Kahn Gillmor
wrote:
>
>
> I think what you're describing takes aim a different problem, so i don't
> think it addresses the underlying concern here.
I believe it solves your problem, just not the way you expect.
As you point out, the current
Source: mosquitto
Severity: wishlist
It would be useful if mosquitto provided a systemd unit, I suggest
something like:
[Unit]
Description=mosquitto MQTT v3.1 message broker
[Service]
ExecStart=/usr/sbin/mosquitto -c /etc/mosquitto/mosquitto.conf
Restart=on-failure
[Install]
Hi all,
On Wed, 27 Feb 2019 00:38:16 +0100 Mathias Behrle
wrote:> I don't see how
> anything could be done from the side of cached_property at this stage of the
> freeze. Therefore I am bumping the bug to severity serious to be safe this
> version of freezegun will not migrate to testing and
Package: gnat-gps
Version: 18-5
Severity: important
Dear Maintainer,
The menubar button actions "Build & Run" and "Build & Debug" in GNAT
Programming Studio (GPS) are currently broken.
When clicking those buttons, the following message appears in the "Message"
view of GPS:
Uncaught exception
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package piuparts (or age it), we missed the freeze deadline by
a day because I had forgotten the new binary packages added by Andreas...
The diff is mostly only relevant for
Hi Niels,
On Tue, Mar 05, 2019 at 07:12:00AM +, Niels Thykier wrote:
> I have unblocked mblaze/0.5.1-1.
Thanks :)
> For next time, it would have made it
> easier if you had waited for mblaze/0.5-1 to migrate to testing before
> uploading mblaze/0.5.1-1.
Yes, I simply didn't want to delay
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Control: tags + patch
I have created a merge request in Salsa for this:
https://salsa.debian.org/debian/ca-certificates/merge_requests/2
- --
- -- arthur - adej...@debian.org - http://people.debian.org/~adejong --
-BEGIN PGP SIGNATURE-
Package: src:linux
Version: 4.9.144-3.1
Severity: important
Dear Maintainer,
After updating the kernel 4 days ago to 4.9.144-3.1 from 4.9.130-2, I
have had two instances in the last 24 hours where a BTRFS filesystem has
failed and started reporting "No space left on device" for any attempt to
Hi.
Incidentally, my current workaround for this and related issues
has been (for the last months) to bind-mount /dev/urandom on /dev/random
inside the chroot.
This has been working like a charm in most cases, the exception being
packages who insist on testing the hardware or the operating
Hi Salvatore,
can you provide some more details why TCPDF needs to be removed from buster?
TCPDF 6.2.26 entered testing yesterday. I see no more open security
issues assigned to this package.
This is also the latest version of the application.
About #923736 it seems the link is wrong. LDAP
Hi,
I was affected by this, too when compiling Gpg4win. Caused an error in Boost
and the mentioned Qt error.
I want to thank you very much for investigating and causing this bug to be
fixed. I've compiled myself packages with the fix from https://gcc.gnu.org/
bugzilla/show_bug.cgi?id=88568
On Thu 2019-01-24 15:12:24 -0500, Daniel Kahn Gillmor wrote:
> re: https://bugs.debian.org/841208 --
>
> entropy exhaustion should no longer be an issue on debian buster, since
> the gcrypt started using getrandom() as of gcrypt 1.8.4 (see upstream
> https://dev.gnupg.org/T3894)
I'm closing this
I stand corrected its in your version since you cherry picked the patch.
On 3/5/19 6:16 AM, Jeremy Bicha wrote:
> I just uploaded libblockdev 2.20-7. Please check if it fixes your issue.
>
> If it does, would you be interested in filing the unblock bug to get
> the fix in to Debian Buster?
>
> https://release.debian.org/buster/freeze_policy.html
>
> Thanks,
> Jeremy
Quoting Manas Kashyap (2019-03-05 17:50:50)
> Package: wnpp
> Severity: wishlist
> Owner: Manas Kashyap
> X-Debbugs-CC: debian-de...@lists.debian.org, debian-r...@lists.debian.org
>
> * Package name: ruby-sassc
> Version : 2.0.1
> Upstream Author : Ryan Boland.
> * URL
1 - 100 of 210 matches
Mail list logo
