can't see crash in buster with lshw version 02.18.85-0.1.
I think we can close this bug.
signature.asc
Description: This is a digitally signed message part
Control: severity -1 serious
pandas 0.25 is now in unstable.
The explicit Breaks: (causing the current "badpkg" status) end on the
next upload of these packages, but the underlying issues (see above log)
also need to be dealt with.
On 2019-11-14, Chris Lamb wrote:
>> It would be nice if lintian checked for the presence of a .buildinfo
>> file when processing a .changes file.
>
> I'm obviously sold on the idea of .buildinfo files but what error or
> mistake might such a missing file imply on behalf of the developer?
I'm not
Hi All,
On Fri, Aug 30, 2019 at 07:56:16AM +, Matthias Klose wrote:
> Package: src:trace-cmd
> Version: 2.6.1-0.1
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal
trace-cmd/2.8.3-1 is not using python anymore and so I have marked this
as
Hi,
I'm running buster with
apt-cache policy phantomjs
phantomjs:
Installiert: 2.1.1+dfsg-2
Installationskandidat: 2.1.1+dfsg-2
Versionstabelle:
*** 2.1.1+dfsg-2 500
500 http://httpredir.debian.org/debian buster/main amd64 Packages
100 /var/lib/dpkg/status
and
tags 944707 + moreinfo
thanks
Hi Vagrant,
> It would be nice if lintian checked for the presence of a .buildinfo
> file when processing a .changes file.
I'm obviously sold on the idea of .buildinfo files but what error or
mistake might such a missing file imply on behalf of the developer?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2019-11-13 at 20:58 +, Mike Gabriel wrote:
> One last question: For the themes you maintain, is it ok if I provide
> the "Provides: any-murrine-theme" patches (as MRs or pushed commits)
> and possibly even NMU them for those
Package: feh
Version: 3.2.1-1
Severity: minor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
feh includes a manpage for feh-cam which is not included in the package.
- -- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500,
Package: lintian
Version: 2.33.0
Severity: wishlist
It would be nice if lintian checked for the presence of a .buildinfo
file when processing a .changes file.
For a stretch goal, it would be nice if it also checked if the
.buildinfo file was signed. :)
live well,
vagrant
signature.asc
Package: firefox-esr
Version: 68.2.0esr-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I don't know where to report, but I want to share an experience and
possible workaround.
I hav filed a mozilla bugzilla entry:
https://bugzilla.mozilla.org/show_bug.cgi?id=1596338
Package: python3-mako
Version: 1.0.7+ds-1
Severity: important
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal
Dear maintainers,
The alembic package fails to build from source in Ubuntu focal, because
Ubuntu has begun the transition to python3.8 and mako is not
source-compatible
Package: wnpp
Severity: wishlist
Owner: Nicholas D Steeves
* Package name: org-html-themes
Version : 1.0.0
Upstream Author :
* URL : https://github.com/fniessen/org-html-themes
* License : GPL-3+
Programming Lang: Org_style_markdown, HTML, CSS, js vs
Hi,
Don't forget to provide GSequencer configuration in $HOME/.gsequencer/ags.conf
regards,
Joël
On Wed, Nov 13, 2019 at 1:25 PM Joël Krähemann wrote:
>
> Hi,
>
> I just installed realtime kernel and gsequencer from debian repository.
>
> I am not able to reproduce.
>
> please provide more
Source: nvidia-graphics-drivers
Severity: normal
Dear Maintainer,
Vcs-* fields for nvidia-graphics-drivers points to
https://salsa.debian.org/nvidia-team/nvidia-graphics-drivers
but going to this link leads to 404 error. I'm unable to checkout the source
using debcheckout
Can some one point me
Status update: I've deferred the question of Webkit vs Web Engine and
am working on Martchus' prerequisite libraries, starting with
"c++utilities" aka "cpputilities". I will need to consult with
someone more how to package this for Debian such that it doesn't make
such a huge namespace grab, or
Package: ftp.debian.org
Severity: normal
The recent LTSP upload seems to be missing the arch:all "ltsp" binary
from sid's Packages files...
< vagrantc> so, the packaging for "ltsp" was radically changed; it only
ships one arch:all package also named "ltsp" now rather than several
arch:all
Source: doit
Version: 0.31.1-3
Severity: important
Tags: patch
Dear Maintainer,
After the pytest fix in 0.31.1-3, unfortunately the autopkgtest still
fails due to output on stderr:
https://ci.debian.net/data/autopkgtest/testing/amd64/d/doit/3403646/log.gz
Easy to fix though, I'm attaching what
Control: retitle -1 gitlab ssh access broken with protobuf 3.10
Control: severity -1 serious
On ബു, Nov 13, 2019 at 23:44, Pirate Praveen
wrote:
On Mon, 11 Nov 2019 22:15:20 +0530 Pirate Praveen
mailto:prav...@onenetbeyond.org>> wrote:
Control: retitle -1 ssh access fails with
Source: python-multipletau
Version: 0.3.3+ds-2
Severity: normal
Tags: patch
Dear Maintainer,
As subject. Patch attached, but really, making the needed change will
take about as long as opening the patch.
Cheers,
mwh
-- System Information:
Debian Release: buster/sid
APT prefers eoan-updates
Package: bsdutils
Version: 1:2.33.2-0.1
Severity: normal
I was debugging a dhclient-script hook when I noticed this in the
journal
Nov 14 09:31:23 debian olaf[3598]:
/etc/dhcp/dhclient-exit-hooks.d/local-static-route returned non-zero exit
status 1
THe issue is not with the non-zero exit
Hi Matthias,
Thanks for filing this bug report, I'll try to fix it as soon as I can.
On 10/27/19 6:33 AM, Matthias Klose wrote:
> Package: src:cegui-mk2
> Version: 0.8.7-3
> Severity: important
> Tags: sid bullseye patch
> User: debian-pyt...@lists.debian.org
> Usertags: python3.8
I noticed
Package: gitlab
Version: 12.2.9-2
severity: important
Currently only pure ruby gems are handled in debian/gitlab.triggers
Note if I run the example command under gdb then it always works so that
implies a timing/race condition.
As of eog version 3.34.1-1 , bug is still present.
Cyril Brulebois (2019-11-14):
> Looking at the current (as of 2019-11-14 00:27:00 UTC) indices for
> buster/updates on security.debian.org, one can only see SHA256 entries
> in Release and Packages files, which is likely the reason for
> python-apt's explosion. I've asked #debian-ftp to add
Package: ftp.debian.org
Severity: serious
Justification: breaks image generation tools
Hi,
I've mentioned this on #debian-ftp already, but filing a bug report in
addition to make sure it's not lost.
Assuming the FTP team is responsible for security's dak setup as well,
we'd like to get MD5Sum
Daniel Kahn Gillmor (2019-10-22):
> The Packages file is growing, and we would like to keep it smaller.
>
> The MD5sum lines are vestigial at this point. Anything that they do
> can be done better with the data from the SHA256sum lines.
>
> Removal of the MD5sum lines would reduce the size of
Package: python-apt
Version: 1.8.4
Severity: serious
Justification: some people want to get rid of MD5Sum in indices
Hi,
While debugging a live-wrapper (lwr) failure that started occurring
(literally) overnight, I ended up discovering it was triggered by the
intel-microcode package's getting a
Package: sddm
Version: 0.18.0-1
Severity: normal
Dear Maintainer,
My system has 2 screens - a primary display connected to HDMI-0 and a
smaller secondary display to
the right, on DVI-D-1. On boot, the displays are swapped so that the
smaller display is configured
on the left. In the Displays
Source: resource-agents
Version: 1:4.4.0-1
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: shell
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Attached is a patch to fix a typo in heartbeat/MailTo that behaves
differently when /bin/sh is bash vs.
Ya the branch and pristine tar config can stay the rest is better left as a
local config, thanks!!
On Wed, Nov 13, 2019, 18:40 Carl Suster wrote:
> Thanks for sponsoring!
>
> Sure, I'd left this config there since my first attempts at learning the
> gbp workflow. I understand why things like
Thanks for sponsoring!
Sure, I'd left this config there since my first attempts at learning the
gbp workflow. I understand why things like the pbuilder config don't
belong in the package repo, but the branch/tag naming config is still
relevant, no?
Cheers,
Carl
Hi,
I backported and tried the patch for Debian LTS.
The patch is trivial (basically s/0777/0600/).
However, I could not find a way to reproduce the initial issue.
The only way to get those 0777 shm in `ipcs` is to run Kali specifically
in virt-manager or VirtualBox.
I could not reproduce this
Greetings, and thanks! I'm on it...
Take care,
Ivo De Decker writes:
> package: src:gcl
> version: 2.6.12-88
> severity: serious
> tags: ftbfs
>
> Hi,
>
> The latest upload of gcl to unstable fails on ppc64el:
>
> https://buildd.debian.org/status/package.php?p=gcl
>
> I suspect the FTBFS of
Just for the record, this does build a python 3 module, removing the
python 2 one is just a matter of rdeps being migrated.
On Wed, Nov 13, 2019 at 9:35 PM Dmitry Smirnov wrote:
>
> On Thursday, 14 November 2019 3:33:42 AM AEDT Alexandros Kosiaris wrote:
> > Thanks, I 'll take up on your offer. If anything I 'll manage to learn
> > more about the bureaucracy aspects of package maintainer ship and
> > avoid such
Just for the record, this does build a python 3 module, removing the
python 2 one is just a matter of rdeps being migrated.
Just for FYI, this now exports a Python 3 module, droppin the Python 2
one is just a matter of rdeps.
On 2019-11-14 00:24:15, Osamu Aoki wrote:
> On Wed, Nov 13, 2019 at 03:31:04PM +0100, Iustin Pop wrote:
> > On 2019-11-13 15:06:54, Thomas Goirand wrote:
> > > On 11/12/19 4:37 PM, Osamu Aoki wrote:
> > > > The related binary packages are available in 2 binary names (depending
> > > > on release)
Package: mailavenger
Version: 0.8.5-2
Severity: serious
Justification: Policy 2.2.1
Hello,
I [noticed] that package mailavenger includes some files which are
derived from code originally released under the terms of the
4-clause BSD license, but their modifications are released under
the terms of
I submitted a merge request on salsa which fixes this issue (and some
others):
https://salsa.debian.org/lvm-team/thin-provisioning-tools/merge_requests/2
Thanks for considering this!
--
Lucas Kanashiro
psychopy isn't blocking pandas' testing migration because psychopy
already isn't in testing (for reasons unrelated to py2removal).
Upstream say it's now Python 3 compatible [0], but I haven't tried to
fix its other problems.
The ones that are blocking pandas [1] are python-skbio,
reopen 936277
thanks
> cctools (7.0.9-3) unstable; urgency=medium
> .
>* Move to debhelper-compat 12
>* Drop python-workqueue for python2 transition. Closes: #936277
Hi Alastair,
coop-computing-tools still depends on python:
$ apt-cache show coop-computing-tools
(..)
Version: 7.0.9-3
I stumbled across this issue yet again in a fresh buster installation.
Various conversions did not solve it for me, but after reading [1], I
checked and found that my initramfs indeed did not contain raid1.ko.
Adding raid1 to /etc/initramfs/modules made my system boot.
This suggests
On Wed, 13 Nov 2019 11:55:12 +0100 Johannes Schauer wrote:
> Control: tag -1 + pending
>
> Hi,
>
> the bug is now fixed upstream:
>
> https://gitlab.mister-muffin.de/josch/mmdebstrap/commit/bc423e6ab63f7db04ef3deefe40a0068442ac7a5
>
> Thanks!
Thanks to you! :-)
--
Am Mi., 13. Nov. 2019 um 08:45 Uhr schrieb Raphaël Hertzog
:
>
> Source: gtk-d
> Version: 3.9.0-2
> Severity: important
> Tags: ftbfs
>
> Hi,
>
> can you make a new source upload to let the package migrate to testing
> please ?
>
> I also noticed that the package still fails to build on
ke 13. marrask. 2019 klo 23.16 Michael Biebl (bi...@debian.org) kirjoitti:
>
> Ok, at this point I guess it's best to involve upstream.
> Would you mind filing an upstream bug report at
> https://github.com/systemd/system/issues
> mentionting that a daemon-reload triggers an assert in
>
Marc Dequènes wrote...
> On 2019-11-01 19:32, Christoph Biedl wrote:
>
> > Upstream uses "After=network.target" only, basically
> > https://sources.debian.org/src/inspircd/3.3.0-1/make/template/inspircd.service/
>
> Yes, but as referenced on this other bug systemd upstream recommends both
>
Hi Hilko,
On Fri, 30 Aug 2019 07:31:12 + Matthias Klose wrote:
> Package: src:plaso
> Version: 20190131-1
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal
can you just go ahead and remove py2 support here? thanks!
Hi Paul
A bit more info. I have tested to compile all of the reverse dependencies of
qscintilla2-2.11.2 and all compile without problems.
$apt rdepends libqscintilla2-qt5-13
libqscintilla2-qt5-13
Reverse Depends:
Depends: sqlitebrowser (>= 2.10.2)
Depends: sonic-pi (>= 2.8.4)
Depends:
Ok, at this point I guess it's best to involve upstream.
Would you mind filing an upstream bug report at
https://github.com/systemd/system/issues
mentionting that a daemon-reload triggers an assert in
manager_unref_uid_internal() and attaching your backtrace.
Thanks,
Michael
--
Why is it that
Package: debhelper
Version: 12.7.1
Severity: wishlist
I’ve recently gained a build reproducibility error in src:musescore where
cmake is used to first copy a few files around, generate some, and then
create a PKZIP archive from them using its built-in archiver. The files
in that archive were
Hi,
I am trying to package v2.3.0 but we need upload python3-m2r to unstable.
Pymodbus depends of m2r (2.3.0 and 2.2.0 too) for documentation.
We should submit a bugs for m2r upload?
Cheers,
Arias Emmanuel
@eamanu
http://eamanu.com
El mié., 13 de nov. de 2019 a la(s) 11:39, Gianfranco
Hi Yves-Alexis,
thanks for your reply.
On Mi 13 Nov 2019 16:27:06 CET, Yves-Alexis Perez wrote:
On Tue, 2019-11-12 at 12:09 +0100, Mike Gabriel wrote:
As I haven't had any reply nor statement nor veto nor anything from any
of you on the above, here is what is going to happen, if noone
Package: python3-debianbts
Severity: important
Version: 3.0.0
Dear python-debianbts developer,
Your package python-debianbts will not migrate to Debian Testing due to
uploads that contain maintainer-built packages. Please rebuild your package
and make another source-only upload to allow it to
While waiting for resolve this issue we can use the 6.0.14 version from
Ubuntu which is linked
on the debian tracker site:
https://tracker.debian.org/pkg/virtualbox-guest-additions-iso
(right side below "links")
On Wed, 30 Oct 2019 17:16:49 +0100 =?UTF-8?Q?Holger_Schr=c3=b6der?= <
Hello Paul,
Am 13.11.19 um 19:35 schrieb Paul Gevers:
> Hi Carsten,
>
> On 13-11-2019 07:20, Carsten Schoenert wrote:
>> But I"m struggling *how* to add such an versioned test dependency. This
>> version requirements are only needed for the autopkgtest(s) so because
>> of this we haven't bumped
You are right, the file was downloaded from github, and files gives,
picca@cush:~/Debian/tango$ file tango-9.3.4-rc2.tar.gz
tango-9.3.4-rc2.tar.gz: gzip compressed data, from FAT filesystem (MS-DOS,
OS/2, NT), original size 284221440
once repack with tar
picca@cush:~/Debian/tango$ file
Hi Ivo,
On Tue, Nov 12, 2019 at 06:55:45PM +0100, Ivo De Decker wrote:
> package: pam-python
> version: 1.0.7-1
> severity: important
>
> Hi,
>
> The latest upload of pam-python contains maintainer binaries, which blocks the
> transition to testing. Please do a source-only upload to allow the
A nine year old bug with no response. I am closing it. If it has
relevance to today's printing system, someone will reopen it.
--
Brian.
Hi,
On Sun, Oct 06, 2019 at 05:09:30PM -0400, Jeremy Bicha wrote:
> Control: severity -1 serious
> Control: tags -1 -buster
>
>
> As part of the Python2 removal, it is our intent that pygtk will be removed
> from Testing before the release of Debian 11
> "Bullseye". Therefore, I am bumping the
Hi Ovidijus,
On 13/11/2019 11:18, Ovidijus Balkauskas wrote:
> Installing this version of prometheus on either:
> - A machine that has a previous version of prometheus installed
> - A machine that does not have a version of prometheus installed
> fails during installation due to
reassign -1 ftp.debian.org
retitle -1 RM: lepton -- RoQA; FTBFS; NPOASR; RC-buggy for 2 years
severity -1 normal
thanks
Dear maintainer,
As there was no response in over a month I hereby reassign this bug to
ftp-masters as a removal request (RoQA).
Just a note that, even though I've merged these fixes, we are actually
not vulnerable because we do not enable HTTP*S*BOOT in our builds.
That would require setting -DNETWORK_TLS_ENABLE=TRUE at build time,
which we do not do currently.
Am 13.11.19 um 20:48 schrieb Martin-Éric Racine:
> ke 13. marrask. 2019 klo 21.03 Michael Biebl (bi...@debian.org) kirjoitti:
>>
>> Btw, this reminds me of
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883877#103
>>
>> Is this the same host where this is happening (again)?
>> Is this a
ke 13. marrask. 2019 klo 21.03 Michael Biebl (bi...@debian.org) kirjoitti:
>
> Btw, this reminds me of
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883877#103
>
> Is this the same host where this is happening (again)?
> Is this a Virtualbox guest?
Same host. This has never been a
ke 13. marrask. 2019 klo 20.52 Michael Biebl (bi...@debian.org) kirjoitti:
>
> Thanks a lot for the information so far.
>
> Am 13.11.19 um 16:53 schrieb Martin-Éric Racine:
>
> > Setting up udev (243-5) ...
>
> Could you add a "set -x" to
> /var/lib/dpkg/info/udev.postinst to see which command
Hi
On 12-11-2019 10:52, Christoph Berg wrote:
> Here's the list of remaining packages that need a "rebuild on buildd"
> binnmu:
>
> bgw-replstatus
> ip4r
> jsquery
> orafce
> pg-cron
> pg-dirtyread
> pgextwlist
> pgfincore
> pgmemcache
> pg-partman
> pgq
> pg-qualstats
> pg-rage-terminator
>
Source: deal.ii
Version: 9.1.1-6
Severity: serious
Tags: ftbfs sid bullseye
Justification: ftbfs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dear maintainer,
Your package is part of the assimp transition. I scheduled binNMU's but you
package fails to build everywhere it build in the past.
Small updates/notes:
- Apparently a few additional "release" tags have been made since opening
this
- I believe #940813 is the same issue
I can confirm this, I just spent half an hour debugging this exact problem until
I realized the package is buggy, not my server.
Kind regards,
Ralf
control: notfound -1 242-8
control: found -1 243-5
Am 13.11.19 um 17:01 schrieb Peter Habcak:
> Package: udev
> Version: 242-8
> Severity: normal
>
> Dear Maintainer,
>
> After upgrading systemd (including udev) from 242-8 to 243-5 on my SID laptop,
> keyboard and mouse suddenly stopped working
Hi Peter,
can you file this issue to upstream at
https://github.com/systemd/systemd/issues and report back with the issue
number.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description:
On Thursday, 14 November 2019 3:33:42 AM AEDT Alexandros Kosiaris wrote:
> Thanks, I 'll take up on your offer. If anything I 'll manage to learn
> more about the bureaucracy aspects of package maintainer ship and
> avoid such mistakes in the future.
That's not a bureaucracy but important aspects
Source: terminaltables
Severity: important
most of those configs are your personal preferences, that are not strictly
needed to build a package from the DPMT repo.
while sponsoring this package, i had to empty its content so that i could build
it properly, extra work id rather dedicate to fix
Btw, this reminds me of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883877#103
Is this the same host where this is happening (again)?
Is this a Virtualbox guest?
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
Thanks a lot for the information so far.
Am 13.11.19 um 16:53 schrieb Martin-Éric Racine:
> Setting up udev (243-5) ...
Could you add a "set -x" to
/var/lib/dpkg/info/udev.postinst to see which command triggers the segfault.
I suspect it's the daemon-reload, if so, it would be interesting if a
Package: spectre-meltdown-checker
Version: 0.42-2
Severity: wishlist
It looks like upstream added some changes for the new TAA vulnerability
CVE-2019-11135, made some other fixes since 0.42, updated the mcedb,
etc. but hasn't yet issued a new release. It looks like maybe they are
still working on
Am Mittwoch, den 13.11.2019, 19:25 +0100 schrieb Johannes Schauer:
> Hi,
>
> Quoting Benjamin Drung (2019-11-13 19:22:14)
> > mmdebstrap fails to remove all APT list files at the cleanup stage.
> > APT
> > list files for /etc/apt/sources.list.d/*.list remain in image. You
> > can
> > reproduce it
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
nmu petsc_3.12.0+dfsg1-2 . ANY . experimental . -m "Rebuild against libhypre
2.18.2"
Andreas
Am Mittwoch, den 13.11.2019, 19:22 +0100 schrieb Johannes Schauer:
> Hi,
>
> Quoting Benjamin Drung (2019-11-13 19:03:31)
> > > If you are successfully using hooks today, then I'd be happy to
> > > hear
> > > whether the way the work now is useful for you or not.
> > Yes, I am successfully using
Hi,
Quoting Benjamin Drung (2019-11-13 19:22:14)
> mmdebstrap fails to remove all APT list files at the cleanup stage. APT
> list files for /etc/apt/sources.list.d/*.list remain in image. You can
> reproduce it by running:
>
> mmdebstrap --keyring=/usr/share/keyrings/debian-archive-keyring.gpg \
Hi,
Quoting Benjamin Drung (2019-11-13 19:03:31)
> > If you are successfully using hooks today, then I'd be happy to hear
> > whether the way the work now is useful for you or not.
> Yes, I am successfully using hooks now. I migrated our custom in-house build
> script from using debootstrap to
Package: mmdebstrap
Version: 0.5.1-2
Severity: normal
Hi,
mmdebstrap fails to remove all APT list files at the cleanup stage. APT
list files for /etc/apt/sources.list.d/*.list remain in image. You can
reproduce it by running:
mmdebstrap --keyring=/usr/share/keyrings/debian-archive-keyring.gpg \
On Tue, 12 Nov 2019 23:51:02 +0100, Guillem Jover wrote:
> * Package name: libcatalyst-plugin-session-store-redis-perl
> Attached a working and tested packaging, where only the ITP bug number
> needs to be filled in the debian/changelog, Maintainer changed, and
> Vcs fields added if
On Mon, 11 Nov 2019 22:15:20 +0530 Pirate Praveen
wrote:
> Control: retitle -1 ssh access fails with gitaly-upload-pack: fatal:
> error: %v
> On Sat, 2 Nov 2019 14:51:42 +0100 Romain Bignon wrote:
> > Hello,
> >
> > The problem is still here, and is so not related to compatibility between
> >
Am Montag, den 21.10.2019, 13:59 +0200 schrieb Johannes Schauer:
> Hi,
>
> Quoting Benjamin Drung (2019-10-21 09:41:37)
> > The hooks are not documented in the man page / --help output
> > despite
> > having them documented in the end of the mmdebstrap file:
> >
> > $ man mmdebstrap | grep hook
On Tue, 2019-11-12 at 20:43 -0800, Vagrant Cascadian wrote:
> On 2019-05-28, Vagrant Cascadian wrote:
> > On 2019-05-16, Vagrant Cascadian wrote:
> > > So in a bit of a focused run of packaging, I've been chasing the
> > > dependency chain necessary to get guix building on Debian:
>
> Summary:
Package: orthanc-dicomweb
Version: orthanc-dicomweb_1.0+dfsg-1
Severity: serious
Justification: 4
Dear Maintainer,
While I was trying to rebuild the package to use libgdcm-dev instead
of
libgdcm2-dev (change already pushed to the repo) the package failed to
build for another reason with the
Hi,
Quoting Benjamin Drung (2019-11-13 18:47:09)
> Thanks for implementing it. Specifying --keyring before --aptopt fails:
>
> mmdebstrap --keyring=/usr/share/keyrings/debian-archive-keyring.gpg \
> -v --aptopt='Acquire::http { Proxy "123"; }' \
> buster /tmp/buster.tar.xz
>
I know. The
On Wed, Nov 13, 2019 at 11:38:55AM +0100, Svante Signell wrote:
> Source: e2fsprogs
> Version: 1.45.4-1
> Severity: important
> Tags: patch
> Usertags: hurd
> User: debian-h...@lists.debian.org
>
> Hello,
>
> The latest version of e2fsprogs in sid, 1.45.4-1, FTBFS on GNU/Hurd due to two
>
Am Freitag, den 25.10.2019, 09:57 +0200 schrieb Johannes Schauer:
> Hi,
>
> Quoting Benjamin Drung (2019-10-24 11:54:14)
> > Since automatically choosing the right keyring is non-reliable and
> > adding symlinks into /etc/apt/trusted.gpg.d affects the host
> > system, I
> > like to have a
Am Mittwoch, den 13.11.2019, 17:54 +0100 schrieb Johannes Schauer:
> Quoting Benjamin Drung (2019-11-13 17:08:46)
> > > with some minor changes committed here:
> > >
> > > https://gitlab.mister-muffin.de/josch/mmdebstrap/commit/4b82a664daa5b2430a00b737706ee77c75288158
> >
> > Sadly, this change
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
nmu slic3r-prusa_1.41.3+dfsg-1 . ANY . experimental . -m "Rebuild against Perl
5.30."
slic3r-prusa/experimental still depends on perl 5.28 packages.
Andreas
Source: py-libzfs
Version: 0.0+git20190717.39ccb15-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
py-libzfs FTBFS on all architectures:
https://buildd.debian.org/status/package.php?p=py-libzfs=experimental
I can also reproduce it on amd64.
dh_auto_build -a
Source: python-ftputil
Version: 3.4-1
Severity: serious
Tags: sid bullseye
Justification: Python 2 is going away.
User: debian-pyt...@lists.debian.org
Usertags: py2removal
New Python 2 packages shouldn't be added to bullseye at this stage unless it's
the *only* way of helping some other package
ke 13. marrask. 2019 klo 17.37 Michael Biebl (bi...@debian.org) kirjoitti:
>
> Am 13.11.19 um 16:06 schrieb Martin-Éric Racine:
>
> >> Can you provide a dmesg dump and the output of journalctl -alb.
> >
> > Attached.
> >
> >> Please mark the time when the upgrade happened.
> >
> > It happened
Package: extlinux
Version: 3:6.04~git20190206.bf6db5b4+dfsg1-1
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear Maintainer,
My current kernel command line is about 400-character long. When it was
shorter, I didn't have any issues when I wanted to edit this line in the
Quoting Benjamin Drung (2019-11-13 17:08:46)
> > with some minor changes committed here:
> >
> > https://gitlab.mister-muffin.de/josch/mmdebstrap/commit/4b82a664daa5b2430a00b737706ee77c75288158
>
> Sadly, this change breaks mmdebstrap:
>
> $ LANG=C tar -tf root.tar.xz
> ./dev/
> ./dev/console
1 - 100 of 195 matches
Mail list logo
