Package: bugs.debian.org
I just submitted a couple bugs for which I'm claiming ownership, and
having noted that control submissions allow '!' to be specified as the
owner which indicates _me_ the email sending this, I assumed that this
would work for submissions also but it seems not.
why not?
Control: reopen -1
Control: found -1 0.25.3+dfsg-6
Control: retitle -1 pandas: HDF I/O crashes on armhf - bus error
test_append_frame_column_oriented does still exist - it was being
silently skipped by -m "not single". Having removed that, it again
crashes on armhf, as do
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
the source stage uses the wrong parameter value for a call to
chroot_archives.
patch to be submitted via salsa shortly (will amend commit with bug
number first)
Package: wnpp
Severity: normal
I don't use python-ssdeep anymore as it didn't solve my problem. I think
the package is in good shape if you ignore that it needs updating to a
new upstream release. It has very low popcon and a viable competitor
python3-tlsh. Possibly, removing the package is a
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
the binary_disk and source_disk scripts overlook netboot in case
statements.
patch to be submitted via salsa shortly (will amend commit with bug
number first)
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
the binary_rootfs script allies chmod 644 to the squashfs file in one
case but not another.
patch to be submitted via salsa shortly (will amend commit with bug
number first)
Package: thunderbird
Version: 1:68.4.1-1~deb10u1
Severity: normal
Dear Maintainer,
I'm trying to improve the account creation for a mail server setup of
mine. To this end, I setup and configured automx2 on the server, and
now I'm trying to get Thunderbird to use it. automx2 implements
Upstream progress of Python3 port:
https://github.com/cfv-project/cfv/issues/8
Btw, it seems development of original cfv has stalled, see
https://sourceforge.net/p/cfv/bugs/19/ but there is active fork and
2.0 release since 2019:
https://github.com/cfv-project/cfv
New upstream plans to be
Hi
The issue is due to a bug in wml which is solved in the buster package, so when
we upgrade www-master.debian.org to buster, it will be fixed and we can use svg
images without validation errors.
I'll try to review the possible blockers to the buster upgrade in the following
days.
Kind
Hi,
Carsten Schoenert wrote:
> Hi,
>
> Am 01.03.20 um 02:02 schrieb Ricardo:
> > Hello,
> > images in svg are the source. Would be better to store in svg format
> > and convert to png in build time. Are there only external companies
> > logos in repository, or are there some images that we may
Control: retitle -1 ITP: trimesh -- Python triangular meshes with an emphasis
on watertight surfaces
Control: owner -1 !
Control: tag -1 pending
Status: Waiting for https://github.com/mikedh/trimesh/issues/728
Christoph
Package: wnpp
Severity: wishlist
Owner: Michael Lustfield
* Package name: razercommander
Version : 1.2.1.1
Upstream Author : Gabriele Musco
* URL : https://github.com/GabMus/razerCommander
* License : GPL-3.0
Programming Lang: Python-3
Description :
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
the memtest option takes values of memtest86+|memtest86|none however
there are some parts of the codebase handling a value of "false",
presumably as an old backwards compatibility hack (I've not bothered to
go back in the history to
Hi,
I pushed to branch master on https://github.com/HenriWahl/dhcpy6d a
version which at least produced working .deb file. Might be still a
little bit rough but maybe it helps to get it running.
I renamed main.py to dhcpy6d.py by the way and copy it to
/usr/sbin/dhcpy6d as starter.
--
Henri
Hi,
How did you reproduce this issue?
I cannot reproduce this issue on my side by using qemu+hppa, as shown below.
AFAICT, I don't think it's an endianness or 32/64 bit issue.
==
/usr/bin/make check-TESTS
PASS: unit-tests.sh
Source: flatpak
Version: 1.6.2-1
Severity: normal
Hello,
libseccomp is not available on all architectures but flatpak has an
inconditional build-dependency against it preventing it to build
everywhere.
Shouldn't flatpak package disable seccomp support on architectures where
it's not available?
Source: synthv1
Version: 0.9.12-1
Tags: patch upstream
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
synthv1 fails to cross build from source, because two of the embedded
qmake project files hard code the build architecture strip instead of
using QMAKE_STRIP. The attached patch fixes that.
Package: radicale
Version: 2.1.11-8
Severity: important
Dear Maintainer,
Changes to the logging configuration in 2.1.11-8 make it impossible to start
by an ordinary user, who cannot write to /var/log/radicale (and probably
does not want to, either).
Cheers,
Itaï.
-- System Information:
Debian
On Sun, 01 Mar 2020 at 13:13:30 +0100, Laurent Bigonville wrote:
> libseccomp is not available on all architectures but flatpak has an
> inconditional build-dependency against it preventing it to build
> everywhere.
>
> Shouldn't flatpak package disable seccomp support on architectures where
>
Source: packagekit
Version: 1.1.11-1
Severity: important
Tags: patch ftbfs
Justification: fails to build from source
Hello,
It would be nice to fix the FTBFS on hurd-i386
The attached patch should fix this (not-tested)
Kind regards,
Laurent Bigonville
-- System Information:
Debian Release:
On 2020-03-01 7:13 a.m., SZ Lin (林上智) wrote:
> Hi,
>
> How did you reproduce this issue?
> I cannot reproduce this issue on my side by using qemu+hppa, as shown below.
It was on a 4-way rp3440. Most hppa buildds run on PA 2.0 machines with 64-bit
kernels.
I believe qemu only supports 32-bit PA
On Tue, 18 Feb 2020 18:31:50 +0100 Julien Cristau
wrote:
> On Thu, Oct 31, 2019 at 02:25:22PM +0100, Matthias Klose wrote:
> > Julian, you added the py2keep tag. Reading the upstream mail for the 5.2
> > release, it looks like the release will happen next month. So why keeping
> > it as Python2
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
...for 'configure custom sources.list'
patch to be submitted via salsa shortly (will amend commit with bug
number first)
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
Severity: wishlist
bootstrap_archives and chroot_archives would benefit from having
validation of the 'pass' parameter which resulted in usage info being
printed and the script existing, as with some other scripts. this for
instance
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
as titled. this is a sibling to the fix that just recently landed on
master for syslinux. I actually submitted the fix for both back in 2015
as part of a larger path set that was never merged. this is a
resubmission of just the grub2
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
the binary_rootfs script incorrectly tries to delete
chroot/chroot/excludes instead of chroot/excludes.
patch to be submitted via salsa shortly (will amend commit with bug
number first)
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
the bootstrap_debootstrap script performs a check for whether or not
debootstrap supports the --no-check-gpg option. this option has been
present in deboostrap since 1.0.30 so this check is long overdue for
removal.
patch to be
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
a message output by bootstrap_cache needs moving such that it is only
output when actually relevant.
patch to be submitted via salsa shortly (will amend commit with bug
number first)
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
there are various issues in the manpages to address
- parent installer option not specifying that 'daily' is a possible
value
- the list of component script descriptions is out of date
- various typos
- the mixing of primary
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
when writing to chroot/source.sh the source_iso script does so at one
point with an append write instead of replace.
patch to be submitted via salsa shortly (will amend commit with bug
number first)
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
in multiple places of the scripts generating `.sh` files shebangs are
not written to those files.
patch to be submitted via salsa shortly (will amend commit with bug
number first)
Package: live-build
Version: 1:20191221
Every script defines HELP which is made use of in Help(), but the lb
frontend redirects either to the manpage or Usage(), so Help() along
with all the HELP strings seems redundant and in need of removal.
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
there are two copies of the daily d-i URL in the code, which is not
ideal.
patch to be submitted via salsa shortly (will amend commit with bug
number first)
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
the codebase contains some unnecessary conversions of numeric exit
codes to strings.
patch to be submitted via salsa shortly (will amend commit with bug
number first)
Control: tags -1 upstream
Hello Justus,
Am 01.03.20 um 11:27 schrieb Justus Winter:
> I'm trying to improve the account creation for a mail server setup of
> mine. To this end, I setup and configured automx2 on the server, and
> now I'm trying to get Thunderbird to use it. automx2 implements
>
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
Severity: wishlist
the case block in binary_disk involves a lot of repetition and could do
with a refactor.
note, the patch to be submitted builds upon those for 952846 and
952864.
patch to be submitted via salsa shortly (will
Re-enabling these tests found that this bug (which is probably actually
multiple bugs) _does_ still exist, on big-endian systems and _possibly_
others.
pandas now (0.25.3+dfsg-7) warns the user when these are used on any
non-x86 system.
** Stata format
- All big-endian (s390x, hppa,
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
Severity: minor
the Help() and Usage() functions make unnecessary use of echo helpers
which makes them much messier than they need to be.
patch to be submitted via salsa shortly (will amend commit with bug
number first)
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
the error echo printing helper explicitly sends the main part of the
message to stderr, but prints the 'E:' prefix normally meaning that in
some use cases things go wrong such as the prefix not appearing.
patch to be submitted via
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
bootstrap_archives and chroot_archives both have incorrect usage
strings, missing the source|binary 'pass' param info.
patch to be submitted via salsa shortly (will amend commit with bug
number first)
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
the chroot_archives script is missing a line to remove a package list.
(I know that this description is not very useful, I'm just submitting
this to get a bug number for an old patch that never got merged but
still applies).
patch
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Control: forwarded -1 https://release.debian.org/transitions/html/auto-proj.html
Control: block -1 by 951655 951656
For the Debian GIS team I'd like to transition to PROJ 7.
It's not
Source: dh-python
Version: 4.20191017
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
Control: affects -1 + src:tlsh
When cross building python extensions, one is supposed to export a
_PYTHON_SYSCONFIGDATA_NAME. Unfortunately, it contains the abi and from
3.7 to 3.8 we changed
Package: live-build
Version: 1:20191221
this is an extension of #952846 which concerns netboot being missing in
case statements in binary_disk and source_disk.
i'm making a fresh bug report here because my intention with the former
bug number is to assign a bug number for my patches which just
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
lots of indentation issues in the codebase, both in terms of spaces
instead of tabs and other forms of inconsistency.
i've a whole bunch of them (hopefully all of them) wrapped up i a
single commit to be submitted shortly. creating
On Sat, 19 Aug 2017 13:14:48 +0200 Guillem Jover wrote:
> Hi!
>
> There's a proposal to add a pkexec action for update-alternatives.
> So when I went checking for the documentation of the file format, I
> noticed that the DTD is nowhere to be found?
>
> Without the DTD we cannot properly
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
the 'lb' frontend has a fixme for its help/usage strings.
- `HELP` does not actually get used anywhere since the only place that
reads it - Help() - is never called.
- `USAGE` does get called, for instance with `lb --usage`, where
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
the --debian-installer option accepts values of
true|cdrom|netinst|netboot|businesscard|live|false. Having 'true' and
'false' here is very confusing. the set of values needs replacing with
control: tags -1 moreinfo
Hi J meritt,
On Thu, May 05, 2016 at 12:49:22AM -0400, J meritt wrote:
> Attached are patches for the changes described below.
Not sure which version of the code you used to generate it but
unfortunately the patches doesn't apply to current upstream branch¹
neither to
I've attached the Debian file for a 3.3.0 build. It's a little rough and you
might want to make some changes before putting it in Debian, but it compiles
and works for a basic game.
warzone2100_3.3.0-0.debian.tar.xz
Description: application/xz
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
...for consistency, no other errors are split like it.
specifically referring to the 'ntfs' related one in defaults.sh.
patch to be submitted via salsa shortly (will amend commit with bug
number first)
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
as titled; several instances of this
patch to be submitted via salsa shortly (will amend commit with bug
number first)
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
the bootstrap_archives and chroot_archives scripts are missing the '-i'
option for sed when intending to perform inplace modifications and thus
achieve nothing.
patch to be submitted via salsa shortly (will amend commit with bug
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
the installer_debian-installer script contains an unquoted "true"
string.
patch to be submitted via salsa shortly (will amend commit with bug
number first)
Package: wesnoth
Severity: serious
This GPL2 package links with OpenSSL. The OpenSSL license is
incompatible with the GPL (see
https://ftp-master.debian.org/REJECT-FAQ.html). This can be solved by
asking upstream to add a license exception or by linking with wolfSSL
instead. You can find a patch
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
there are some places where the echo helpers are not being used when
they should be.
patch to be submitted via salsa shortly (will amend commit with bug
number first)
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
some of the echo helpers are completely unused and should be removed.
specifically:
- Echo_status
- Echo_done
- Echo_debug_running
- Echo_message_running
- Echo_verbose_running
a couple of those functions are furthermore the
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
Severity: minor
...in chroot_install-packages
patch to be submitted via salsa shortly (will amend commit with bug
number first)
Package: nm.debian.org
Severity: wishlist
Since at one point spammers start to target mailboxes,
it might make sense to not accept more emails a while after a
process has been closed, maybe one or two months.
comment from enrico:
"The mail processing script isn't very smart unfortunately at the
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
Severity: minor
every single script (those under scripts/build/) uses a subcmd to
inject a newline to the end of DESCRIPTION string which is used by
Help() or Usage() if called.
this is rediculous; the scripts can just hold a plain
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Hi,
this is a very small transition: the new version of okular bumps the
SONAME of the okular core library, and the only user of it is calligra.
calligra builds fine with the newer
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
Severity: wishlist
...in the same way as for flash-kernel
patch to be submitted via salsa shortly (will amend commit with bug
number first)
Source: pycollada
Version: 0.6-1
Severity: serious
Justification: out-of-sync unstable-to-testing
X-Debbugs-CC: kkremit...@gmail.com kurt@kwk.systems ti...@debian.org
Dear package pycollada maintainers,
The latest upload of your package was not a source-only upload. As a result,
it did not
Control: severity -1 wishlist
Hi Lorenzo,
not until opentmpfiles provides unified interface. I am not adding more shell
spaghetti anywhere if I can help it.
systemd does not enforce systemd-sysv package installation. Use
--no-install-recommends with apt.
Ondrej.
--
Ondřej Surý
> On 1 Mar
On Thu, 20 Feb 2020 13:26:44 +0530 Avinash Sonawane wrote:
> On Sat, 17 May 2003 15:36:53 -0400 Matt Zimmerman
> wrote:
> > reassign 192787 apt-listbugs
> > thanks
> >
> > This is impossible (see #80123), but in any case not apt's bug.
>
> As per this comment
>
Package: shotcut
Version: 20.02.17-2
Severity: important
Dear Maintainer,
When I try to run shotcut on a 4K monitor I get the following logs:
$ LANG=C shotcut
[Info ] Starting Shotcut version 20.02.21
[Info ] Linux version
[Info ] number of logical cores = 8
[Info ] locale =
Package: iptables
Version: 1.8.2
Hello, comrades!
In Devuan 1, Devuan 2, Devuan 3 (and Debian, and Ubuntu) have next
standard issue with *iptables*!
The current range of values for the *--tcp-option* /iptables/ flag is
1-255 - this is not correct. The correct range of values should be
Package: dfu-util
Version: 0.9-1+b1
Severity: wishlist
Tags: upstream
Dear Maintainer,
The latest upstream release of dfu-util was a very long time ago. Maybe you
could package a recent git checkout, that supports newer platforms like some
risc-v boards.
Regards
Thomas
-- System Information:
Hey Joey,
> The last version of LTS that this build of stack can handle seems to be
> 13.29. Trying to build any stack.yaml that uses a newer LTS results in
> parse failures.
I just uploaded stack v1.9.3.1 to unstable. Could you please check if it
can now correctly handle newer LTS versions?
Hi, I worked out a Python3 port of package python-cwiid to
python3-cwiid.
Please can you review the work done in
https://salsa.debian.org/georgesk/cwiid ?
As upstream development seems almost stopped, I made most changes inside
the branch upstream of the repository, and issued a new version
Hi
On Sat, Feb 29, 2020 at 09:43:55AM -0700, Sean Whitton wrote:
> Hello Matt,
>
> On Sat 25 Jan 2020 at 04:06PM -08, Matt Taggart wrote:
>
> > I am following the the "When upstream tags releases in git" section of
> > dgit-maint-merge(7) and when I get to the "Now go ahead and
> > Debianise..."
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
Severity: minor
--architectures only takes a single architecture, so should be renamed
to no longer be plural to avoid user confusion.
patch to be submitted via salsa shortly (will amend commit with bug
number first)
Thanks for your help!
The problem (much smaller) is that installing manually version
2019.11.05 did not help on its own. I had to run wget -qO-
https://www.ports.debian.org/archive_2020.key | apt-key -
Just thought I should let you know.
Best,
Prem
On 26/02/2020 22:06, Aurelien Jarno
Package: kmail
Version: 4:19.08.3-1
Severity: critical
Justification: breaks unrelated software
I tagged this critical and breaks unrelated software as there seems no better
tag for software that is dangerous for epileptic people to use.
Every time I launch kmail the message body section
Package: apticron
Version: 1.2.3+nmu1
Severity: normal
Dear Maintainer,
Normal usage of apticron.
Sometimes the mails generated by apticron bounce.
Looks like exim4 does not want to transport mails with lines longer than 998
characters.
I temporarily configured apticron to send mail to a
On Sun, 1 Mar 2020, Ben Hutchings wrote:
> The kernel sets COUNTRY in the uevent, which is copied into the device
> properties. Then udev copies the device properties into the
> environment when running an external program.
OK. But where does stderr of crda go anyway? Trying to debug this…
On Sun, 2020-03-01 at 18:28 +0100, Thorsten Glaser wrote:
> On Sun, 1 Mar 2020, Ben Hutchings wrote:
>
> > The kernel sets COUNTRY in the uevent, which is copied into the device
> > properties. Then udev copies the device properties into the
> > environment when running an external program.
>
>
Source: enchant-2
Version: 2.2.7+repack1-1
Severity: normal
X-Debbugs-CC: bi...@debian.org sjo...@debian.org
Dear enchant-2 maintainers,
Upstream has released v2.2.8 with new nuspell support. Please consider
packaging this new version in Debian.
--
Thanks,
Boyuan Yang
signature.asc
Package: wpasupplicant
Version: 2:2.9.0-8
Followup-For: Bug #951775
Dear Maintainer,
* What led up to the situation?
I follow Debian testing. Upgrading the system.
/var/log/aptitude
[UPGRADE] wpasupplicant:amd64 2:2.9+git20200213+877d9a0-1 -> 2:2.9.0-8
Inmediate effect. Just after
On Sat, Feb 29, 2020 at 07:42:16PM +0100, John Paul Adrian Glaubitz wrote:
> The upcoming 2.06 release contains a fix to set -no-PIE in TARGET_CCASFLAGS
> [1]
> such that the current workaround in debian/rules will no longer be necessary.
>
> The following patch should be applied to debian/rules
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
the echo helpers almost entirely do not explicitly direct their output
to stdout/stderr, and failing to do so means that in some use cases
(specifically use in functions whose purpose is to return a string (by
echoing it)) things go
I'm trying to address the changes in the iptables package for collectd.
I can avoid the dependency on the transitional iptables-dev package (see [1]),
but I'm confused by the
statement:
> The src:iptables debian package (v1.8.4-1) dropped the libiptc-dev and
> libiptc0 binary packages.
I see
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
Severity: minor
binary_onie takes the unusual (with respect to all other scripts) step
of outputting a series of dots as it progresses through various parts
of its script. these dots are all printed on the same line and finally
are
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
Severity: minor
functions/common.sh holds a variable PROGRAM set to "live-build" which
is used in places where both "live-build" AND "lb" should appear.
patch to be submitted via salsa shortly (will amend commit with bug
number
On Sun, Mar 01, 2020 at 08:37:43PM +0600, Judit Foglszinger wrote:
> "The mail processing script isn't very smart unfortunately at the moment, to
> avoid bringing up django every time a mail arrives, although it could
> just enqueue the mails, and the ping django for actually injecting them"
Package: php7.3-fpm
Version: 7.3.15-4
Severity: normal
Tags: patch
Dear Maintainer,
with commit ccbb813a4268e79c8bb2ef24f468eec23b53e73a is no longer possible
to install php7.3-fmp package with alternative inits when elogind is installed.
For example for me it forces removal of elogind and
Additional information:
I can't reproduce within buster/stable release, using 2.0.5-2 package
version.
Hence it may be a regression introduced by the 2.0.6-1 version.
Thanks,
François
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2020-02-13 at 13:11 +0100, Andreas Henriksson wrote:
> Control: severity -1 serious
>
> Hello XFCE Maintainers,
>
> I'm bumping the severity of this bug report because the libindicators
> package in RC buggy and likely not going to make it
On Sun, 2020-03-01 at 16:37 +0100, Thorsten Glaser wrote:
> retitle 929841 systemd-udevd: regulatory.0: Process '/sbin/crda' failed with
> exit code 255.
> thanks
>
> Could this have to do with /lib/udev/rules.d/85-regulatory.rules ?
>
> A quick search through the code shows it returns “-1”
Sorry for the noise here. I understand that these are two separate issues, and
I believe
that upstream has addressed the libiptc -> libip4tc name change in their 5.10.0
release.
My MR has been updated to only pull in libip4tc-dev and libip6tc-dev, and not
libiptc-dev
in a third patch, so there
Source: lmdb
Version: 0.9.22-1
Severity: wishlist
Hi,
Looks like upstream has relased a new version (0.9.24), please update.
Changelog since 0.9.22:
LMDB 0.9.24 Release (2019/07/24)
ITS#8969 Tweak mdb_page_split
ITS#8975 WIN32 fix writemap set_mapsize crash
ITS#9007 Fix
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
Severity: minor
Echo_message() should be used instead of Echo() for "No EFI boot code
to include in the ISO".
patch to be submitted via salsa shortly (will amend commit with bug
number first)
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
as titled.
patch to be submitted via salsa shortly (will amend commit with bug
number first)
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
there is a significant chunk of code for generating an apt sources.list
file that is duplicated in three different places in the codebase. in
two cases it is identical, in the third it only differs in the
variables used for mirrors
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
the graphical installer is only bundled if LB_DEBIAN_INSTALLER_GUI
permits it, however the bootloaders ay no attention to this and the
corresponding menu entries end up in the image anyway which will
obviously be non-functional.
Hi,
> > Failure: ModuleNotFoundError (No module named 'asn1crypto') ... ERROR
> > ...
I have attempted a fix as merge requests in salsa [1], as it seems to
be a dependencies issue.
[1] https://salsa.debian.org/python-team/modules/androguard/-/merge_requests/2
Best,
--
Diego M. Rodriguez
retitle 929841 systemd-udevd: regulatory.0: Process '/sbin/crda' failed with
exit code 255.
thanks
Could this have to do with /lib/udev/rules.d/85-regulatory.rules ?
A quick search through the code shows it returns “-1” (i.e. 255) in
multiple places (the main function is written like kernel
Sean Whitton, from FTP Master, reviewed the package and pointed out
that the file CODE_OF_CONDUCT.md is probably not suitable for
distribution in the main section. I agreed and repackaged the project,
as can be seen in:
https://salsa.debian.org/debian/pveclib/-/commits/master
(look for dfsg)
Package: cups
Version: 2.3.1-7
Severity: normal
Dear Maintainer,
Accessing CUPS via https://hostname:631 works while
https://hostname.example.com:631 fails with 400 Bad Request if
cupsd.conf does not contain either "HostNameLookups on" or
"ServerAlias printserver.example.com". This is a
Source: pillow
Version: 6.2.1-2
Severity: serious
Justification: Policy 2.3, 4.5, 12.5
During review in binary-NEW, I found the following issues with
d/copyright. Since the issues already exist in the archive I did not
REJECT, but they should be fixed.
Note that I am filing an identical list of
1 - 100 of 172 matches
Mail list logo
