Hi Craig,
Thanks for the update. I just tried the lastest package version, but it
seems that RFC1212 and RFC1215 are still not generated. It seems that
the RFC files included in the packages are not patched.
> The IETF MIBs are shipped with the downloader, so I can include them
> and then patch t
Package: snmp-mibs-downloader
Version: 1.6
Severity: wishlist
Hi,
I've been using snmp-mibs-downloader for getting MIB files for my
netgear switch, but I'm running into problems because RFC-1212, RFC-1215
and IANA-ENTITY-MIB are not present.
# RFC-1212 and RFC-1215
Looking at these rfcs, they ar
Hi James,
> The relevant CMake file addition was sourced[1] from the LLVM codebase, which
> is licensed under a variant of the Apache 2.0 license with some exception
> clauses added for the LLVM project. This is not yet documented in the source
> package.
Thanks for pointing this out.
It turns
forwarded 1059296 https://github.com/projecthamster/hamster/issues/750
thanks
Hi Moritz,
Thanks for bringing this to attention, this was not reported upstream
yet.
> https://github.com/BrunoTeixeira1996/CVE-2023-36250/blob/main/README.md
> sounds a little bogus, I don't see how this crosses any
Hi Maytham,
> Nice! It's not on the Salsa repo, so I'm assuming you're yet to push your
> changes.
Yup. I've justed pushed and uploaded!
> Thanks for your quick responses, and thanks for maintaining this awesome
> package! Looking forward to the new version. :)
Thanks for your interest and effort
Hi Maytham,
> nmudiff (from devscripts) did that gigantic diff, but I've followed
> your workflow in my fork of the repo at [1], if you want to just copy
> the commits over (and change the Debian revision from -0.1 to -1).
Ah, I already imported the tarball myself :-)
> I've built it on my comput
Hi Maytham,
> I've prepared an NMU for openttd (versioned as 13.4-0.1). The diff
> is attached to this message.
Thanks for your patch. I should have uploaded a new OpenTTD version
a long time ago, so let met correct that by handling the update now.
I'll go through my normal git-based workflow rath
Hey Toni,
> please consider packaging the jgrpp patches, too.
Thanks for your suggestion. What did you have in mind exactly?
I won't include third-party patches in the main build, since that
affects multiplayer compatibility (i.e. a patched build will be
incompatible with other people playing un
forwarded 1027860 https://github.com/projecthamster/hamster/issues/710
thanks
Hi,
> AttributeError: module 'gettext' has no attribute 'bind_textdomain_codeset'
Thanks for reporting this. There is also an upstream issue about this,
with a suggested workaround:
https://github.com/projecthamster/ha
Package: wnpp
Followup-For: Bug #793749
FYI: It seems that Ubuntu has started packaging telegraf in 2020:
https://packages.ubuntu.com/source/kinetic/telegraf
http://changelogs.ubuntu.com/changelogs/pool/universe/t/telegraf/telegraf_1.22.3+ds1-0ubuntu1/changelog
Package: fzf
Version: 0.30.0-1+b1
Severity: normal
Hi,
README.Debian says:
Note, since fzf 0.29.0-1, the bash completion is installed for bash by
default. Feel free to ignore the following instruction for fzf >=
0.29.0-1.
It seems this means that the completion is installed as
/usr/share/
Hey Daniel,
> timidity was recommended but now timdity is suggested instead
Bugger.
I've fixed this locally, will be included in the next upload (but I'm
not going to reupload just for this, I think).
Thanks for reporting!
Gr.
Matthijs
signature.asc
Description: PGP signature
Package: devscripts
Version: 2.21.7
Severity: normal
Hi,
I was trying to use build-rdeps on Ubuntu today, and the default settings seem
unusable there. I tried both the Ubuntu version from impish and the Sid
version, both with the same result:
$ sudo build-rdeps -d dh-cmake
DEBUG: Package =>
Package: devscripts
Version: 2.21.7
Severity: normal
Hi,
when running build-rdeps without deb-src lines in sources.list, it
produces perl errors, rather than providing useful feedback. This also
happens when a deb-src line is present for the main packages, but
missing for debug packages.
E.g. wi
Hi Aurelien,
Thanks for reporting, I had already seen the failure and am working on
a fix, probably next weekend. The issue is caused by the buildds
building arch and arch-indep separately, which exposes a problem in the
rules file, but I hadn't tested this scenario before upload.
Gr.
Matthijs
Hi Adrian,
It took a while longer than anticipated, because of a problem with last
month's keyring update, but that has now been resolved, so my uploads
have come through.
> packages without valid signature are usually silently dropped,
> expect that you might have to reupload.
Maybe packages wit
Hi Adrian,
> I've prepared an NMU for grfcodec (versioned as 6.0.6-5.1) and uploaded
> it to DELAYED/15. Please feel free to tell me if I should cancel it, or
> to use the changes for a maintainer upload instead.
Thanks for your interest and picking this up!
However, I had actually *just* upload
forwarded 984158 https://github.com/OpenTTD/grfcodec/issues/12
tags 984158 fixed-upstream
thanks
Hi Matthias,
thanks for reporting this issue. I've forwarded it upstream and they
have fixed it, should be included in their next release (6.0.7 or
6.1.0).
Gr
Matthijs
signature.asc
Description: P
Hey folks,
this issue still seems to exist, I just discovered that an upload I did
three months ago was never processed because I forgot to push my
extended key to Debian, which is a bit of a bummer.
Gr.
Matthijs
signature.asc
Description: PGP signature
Hi Phil,
> Indeed, I've cleaned up my local test and pushed to salsa:
>
> https://salsa.debian.org/emorrp1/nml/-/commit/27c0aea7cd2670462c24246caf510d7dd8cb99dd
Thanks! I think to be really correct, though, I'd have to backup the old
files and restore them on clean (or maybe make a copy of the ent
Hi Phil, Mathias,
Thanks for your interest in nml and your effort in getting this bug
squashed :-)
> It would be a shame if openttd got autorm'ed just as the bullseye
> freeze starts in earnest.
Yeah, I'll make sure that doesn't happen.
> Upstream have re-exported the pcx files and I can confir
Package: libinput-tools
Version: 1.15.5-1ubuntu0.1
Severity: normal
Hi,
the manpage, `libinput --help` output and upstream [1] document a
`libinput debug-gui` command, but that does not seem to be available:
$ libinput debug-gui
libinput: debug-gui is not a libinput command or not installed.
Hey Mattia,
> Thank you for this, I've now merged it.
Thanks!
> Also, I personally hate changing long-standing defaults.
Yeah, I can see that.
> > Maybe the default could be changed to only scan the current directory
> > *if* it is a debian source tree, and default to recursive scanning if
> > n
Package: release.debian.org
Followup-For: Bug #926455
Hi,
I also ran into this today. To me, it seems the observable problem is
not so much an incorrect version number in the email warning, but the
fact that the email warning is sent out at pretty much exactly the
moment the autorm for a package
Package: ant-optional
Version: 1.10.6-1ubuntu0.1
Severity: normal
Hi,
I'm trying to run junit-based tests for the JOSM application using ant,
which does not work out of the box. The error I'm getting is:
build.xml:491: The following error occurred while executing this line:
build.xml:442: Pr
> Has anybody succeeded in running systemd inside an LXC container with
> "lxc.cap.drop = sys_admin" ?
Yup, on a Buster system, I'm using this config, which works:
https://github.com/daenney/Tika/blob/tika-host/etc/lxc/login/config
Not sure what the essential part is, but maybe you can compare th
Hey Niels,
> As far as I can tell, the underlying desire is to do some form of
> deduplication.
Yes, indeed.
> If so, then I think this is similar to #888397 with an expanded scope
> and a proposal for doing this via dh_link (rather than dh_installdocs
> or a new helper).
I guess my proposal is
Package: git-buildpackage
Version: 0.9.15
Severity: normal
Hi Guido,
I'm trying to figure out whether I need pristine-tar or not, and I can't
quite figure it out based on the documentation.
I understand that, when upstream supplies a tarball, you can use
`gbp import-orig --pristine-tar` to impor
Package: lintian
Version: 2.72.0
Severity: minor
Hi,
lintian is incorrectly triggering no-dh-sequencer on my package (nml
0.5.1-2). The debian/rules file contains:
# Use debhelper default for all targets (but some are overridden below).
%:
# Force the pybuild buildsystem, since the
Hey folks,
> (...)
> and then goes on to detail how this directory name checking works
> exactly. AFAICS, this directory name checking should protect against
> these stray watch files in most of the cases, but apparently it is not
> working.
> (...)
> AFAIU, "subdir" should have matched /^test(-+.
Package: devscripts
Version: 2.20.3
Severity: minor
Hi,
while working on another problem, I noticed something weird in the code.
See
https://salsa.debian.org/debian/devscripts/-/blob/master/lib/Devscripts/Uscan/FindFiles.pm#L167-193
There is a comment there, that says:
# Now process the w
Package: debhelper
Severity: wishlist
Hi,
in the openttd-opengfx package, I'm using dh_link to replace some
upstream-installed files with symlinks. To prevent accidentally linking
to the wrong file, I now explicitly diff the files before creating the
link. It would be nice if dh_link could handle
Package: git-buildpackage
Followup-For: Bug #959665
Hi,
It does seem that having a full stop at the end of debian/changelogs is
conventional. However, this is already easy to configure locally. I had
this in my debian/gbp.conf for a long time:
[import-orig]
import-msg = New upstream release
Hey folks,
I've upgraded this system to buster and it seems that either the new
kernel (4.19.0-8-amd64) or new lxc version (1:3.1.0+really3.0.3-8) has
fixed this problem: I can now again re-exec systemd in containers even
with lxc.cap.drop = sys_admin enabled.
I guess this issue could be closed?
Package: apt
Followup-For: Bug #880170
Hi,
I just also ran into this problem. It's on a stretch system, so with an
older apt, but maybe my observations help regardless.
I saw this error running `aptitude update`. It happened with the stretch
security updates translation file for contrib and non-
reassign 954672 nml 0.4.5-2
thanks
Hi Lucas,
> > Error:(AttributeError) "module 'time' has no attribute 'clock'".
> > Command: ['/usr/bin/nmlc', '-c', '-p', 'DOS', '-M',
> > '--MF=ogfx1_base.grf.dep', '--grf', 'ogfx1_base.grf', 'ogfx1_base.nml']
> > Location: File "/usr/lib/python3/dist-pac
Package: dh-python
Version: 4.20191017
Severity: wishlist
Hi,
it would be nice if dh-python could automatically handle
DEB_BUILD_OPTIONS=terse.
Debhelper does already have some machinery for this:
/usr/share/perl5/Debian/Debhelper$ grep -r QUIET
Dh_Lib.pm: # make sure verbose is on. Ot
Package: qa.debian.org
Severity: normal
Hi,
for the "nml" package, I'm seeing some warnings from debcheck at [1]:
Package declares a build time dependency on 'python3-all-dev:any' which is
broken Syntax.
Package declares a build time dependency on 'python3-pil ' which is broken
Syntax.
P
Hey Matthias,
> patch at
> http://launchpadlibrarian.net/447871899/nml_0.4.5-1build2_0.4.5-1ubuntu1.diff.gz
Thanks for the report and the patch, looks good. I'll prepare an upload
with it, probably somewhere next week.
Gr.
Matthijs
signature.asc
Description: PGP signature
Hey Matthias,
> Thanks for the report and the patch, looks good. I'll prepare an upload
> with it, probably somewhere next week.
I had another look upstream, seems they fixed it by falling back to
PILLOW_VERSION unconditionally, but I also noticed PIL.__version__ is
actually the recommended replac
Hey folks,
> It is possible to override these defaults by passing `--vendor` to dch,
> so it would be good if a value could be configured in gbp that is passed
> to `dch --vendor`. Ideally, the value could be configured globally, or
> per-package, I think.
I found the `dch-opt` configuration as a
Package: git-buildpackage
Version: 0.9.14
Severity: normal
Hi,
I'm running gbp on an Ubuntu system to build packages for Debian. By
default, dch (and thus also gbp dch) uses distribution and version
number defaults for Ubuntu, rather than Debian (based on the results of
dpkg-vendor).
It is possi
Package: devscripts
Version: 2.19.6
Severity: normal
When running dhc on Ubuntu with --release, it uses the upcoming ubuntu
version (eoan currently), rather than unstable as the distribution name
to put into the changelog. It took me a while to figure out that dch was doing
this, since this except
Package: devscripts
Version: 2.19.4
Followup-For: Bug #905866
Hey folks,
I'm also running into problems with uscan processing debian/watch files
in subdirectories. Looking at the manpage, it *seems* to say it only
scans `debian/watch`, but at the end of the manpage, under ADVANCED
FEATURES, it sa
Package: devscripts
Followup-For: Bug #895982
Hey folks,
it seems this was partly fixed in 2.19.6 by specifically ignoring .git
directories:
https://salsa.debian.org/debian/devscripts/merge_requests/132
There is also a similar bug report to this one that is not limited to
VCS directories, but
Hi Georg,
> new upstream version 1.9.3 is available.
Thanks for the headsup, seems I missed that. I'll try to get this
uploaded ASAP.
Gr.
Matthijs
signature.asc
Description: PGP signature
Package: libpam-script
Followup-For: Bug #927079
Hi,
you mentioned that libpam-script filters environment variables, but I
think this is not actually the case. Looking at the code, it only seems
to *add* a number of variables, not remove any.
For example I added the following line to my /etc/pa
Package: libpam-script
Version: 1.1.9-4
Severity: normal
Hi,
I've just installed libpam-script, and noticed it uses "sufficient" in
its pam config lines. This results in e.g. the following common-auth on
my system:
# here are the per-package modules (the "Primary" block)
authsufficient
Package: libpam-fscrypt
Version: 0.2.4-2
Severity: normal
Hi,
I'm trying to use libpam-fscrypt, but I'm missing a manpage that
describes its usage.
I've found /usr/share/doc/fscrypt/README.md.gz which has some info on
the module, but is mostly limited to examples (for example, it is not
clear wh
Package: modemmanager
Version: 1.10.0-1
Severity: normal
Hi,
since a while, ModemManager is using the new "strict" filter policy.
Rather than probing all serial ports that are not blacklisted (which
causes problems with serial devices that do not like to be probed), it
now uses more specific rule
Hi Adrian,
I just updated the MR with the changes I discussed in my previous mail
(and also listed below). My previous mail also contained some responses
and questions, if you have some time to respond to those that would be
great.
> > >>> 3) Remove ldlinux.c32 for extlinux and syslinux (6fc68c1d
Package: modemmanager
Followup-For: Bug #920765
Hey folks,
AFAICS modemmanager 1.10 is available in sid and buster currently, so
this bug can be closed?
Gr.
Matthijs
Hi Adrian,
thanks again for your thorough review. I'm responding to both your
e-mails inline below.
> >>> 3) Remove ldlinux.c32 for extlinux and syslinux (6fc68c1d)
> >>
> >> 3.1) Nice. I didn't know about those new syslinux architecture dependent
> >> files. As per the wiki you link (
> >> https
Hi Adrian,
thanks for your extensive review. I'll respond inline.
> I might take a look into your notes to implement grub-efi + secure boot
> in hdd img but... this might be in 2021 XD . Too busy at the moment.
Familiar sentiment. Would be nice to have it, though.
> What's your use case? What do
Hey Thierry,
> Is there a chance that this work will be part of buster live-build
> package, or is it too late already ?
I'm not the maintainer of live-build, but given the freeze state that
buster is in, I highly doubt this will make it into buster.
Gr.
Matthijs
signature.asc
Description: PGP
Hey Adrian,
[ About removing --templates from the manpage ]
> In that case IMO that commit should be in its own pull request and not
> the current one.
Done: https://salsa.debian.org/live-team/live-build/merge_requests/21
Gr.
Matthijs
signature.asc
Description: PGP signature
Hi Adrian,
> 1) What is the rationale behind removing the --templates option
> explanation on manpage?
I wondered about this option and looked around the source for it, but
could not find any implementation for it, so it seemed good to remove
the documentation for it.
Prompted by your question, I
Hi Luca & others,
I've been working on syslinux-efi support in the past weeks and just
submitted a MR with a working implementation, along with some small
bootloader-related cleanups and refactors:
https://salsa.debian.org/live-team/live-build/merge_requests/19
In the end, I opted to imp
Package: live-build
Version: 1:20190311
Followup-For: Bug #778317
Hi folks,
this bug still exists. The original report talks about erronously
reusing the same debootstrap cache when chaning architectures, but the
problem seems broader than that. E.g. when switching distributions,
you'll also get
ach ]
+ * [e61a00b] Force build to abort upon endian_check failure. Thanks to
+Helmut Grohne for suggesting this fix (Closes: #922625)
+
+ -- Matthijs Kooijman Tue, 12 Mar 2019 22:19:01 +0100
+
grfcodec (6.0.6-2) unstable; urgency=medium
* [4dce67c] Bump debhelper version to v11
diff -Nru
Hi Steve,
> In fact, one of the projects I've been trying to get to for a couple
> of years now is simplifying things by going the other way: using GRUB
> for everything and dropping syslinux on Debian media.
Hm, that's another interesting thought. I was aiming for syslinux, since
our current set
Hey Luca,
> > So for the secure boot case in binary_grub-efi, what we do is that
> > if the signed monolithic EFI binaries are available we copy those
> > instead of building a new image.
> >
> > ...
> >
> > https://salsa.debian.org/live-team/live-build/blob/master/scripts/build/binary_grub-efi#L7
Hey Luca,
> At a quick glance it all sounds good to me, although I can't say I have
> a lot of experience with syslinux.
Ok.
> For feature parity, I'd encourage to look into supporting Secure Boot
> like the grub-efi implementation does, since we are preparing to ship
> that in Debian 10. It's no
Hi Thomas,
> > it seems isohybrid can include a small FAT filesystem with the
> > bootloader files. [...]
> > https://www.syslinux.org/wiki/index.php?title=Isohybrid#UEFI
>
> This describes the equipment of debian-live and debian-cd (DVD-*, BD-*,
> netinst) ISOs. See e.g. debian-live-9.5.0-i386-x
Package: live-build
Version: 1:20180925
Severity: wishlist
Hi folks,
currently, live-build seems to only support EFI systems using the
grub-efi bootloader, but not for netboot or hdd images (effectively only
for iso images, I believe).
Syslinux also has an EFI version, that can be installed thro
severity 919259 normal
found 919259 232-25
retitle 919259 Reexecuting fails in containers without CAP_SYS_ADMIN
thanks
Hey Michael,
> My suggestion would be to roll back to 232-25+deb9u1 and then gradually
> upgrading to deb9u2, deb9u2 ... deb9u3
Yeah, that was my intention. I discovered some int
Hi Helmut,
On Sun, Nov 18, 2018 at 04:27:29PM +0100, Helmut Grohne wrote:
> Hi Matthijs,
>
> On Sat, Nov 17, 2018 at 09:28:54PM +0100, Matthijs Kooijman wrote:
> > Thanks for testing and provide a patch. I've included in the build, and
> > verified it works. I did run i
Hey folks,
> Meanwhile, Matthijs can you tell us how the OpenTTD layout work goes?
> May you have any ETA from its upstream? It would be good to drop
> icu-le-hb very soon.
As already noted elsewhere, I just uploaded an OpenTTD version without
the iculx and icu-le-hb dependency. Not sure how that
Hi Helmut,
> openttd fails to cross build from source, because it uses the build
> architecture pkg-config. The build system expects the packaging to pass
> --pkg-config to use a triplet-prefixed pkg-config. Doing so is
> sufficient to make openttd cross buildable. Please consider applying the
> a
Hi folks,
I just uploaded openttd 1.8.0-2, which no longer has the ICU layout API
enabled. This should clear the way for dropping iculx and icu-le-hb.
This change makes at least Arabic and Hebrew support in OpenTTD pretty
much unusable. However, some additional investigation suggests that
Harfbuz
Hi László,
thanks for your investigation and patch. I ended up backporting the
upstream patches for the issue, which turned out to be identical to your
patch :-)
I've just uploaded a version with this patch, as well as a bunch of
other pending changes.
Gr.
Matthijs
signature.asc
Description:
Hi László & Ivo,
> > That's too much time for blocking the ICU transition. I'll clear this
> > barrier of the openttd NMU in some days. :-/
Ah, I hadn't realized this was blocking a transition. Because of that, I
tried a bit harder to find time, and just uploaded a fixed version to
unstable.
> I
Hi Lásló,
> That's too much time for blocking the ICU transition. I'll clear this
> barrier of the openttd NMU in some days. :-/
Prompted by your other mail, I found some time in the airport today to
look at the ICU build issue in OpenTTD. I still have a few minor things
to include, but I should
Hey László,
> Matthijs working on a normal package upload? At least he answers my
> mails quick and I thought he can apply my patch and upload it as
> 1.8.0-2 package version.
Ack, it's on my list. I'm a bit busy these weeks, but I expect to find
some time in the next 2/3 weeks.
Gr.
Matthijs
s
Hi Laszlo,
> I do Cc its maintainer Matthijs and if he acknowledges I will drop
> libiculx and icu-le-hb altogether.
Yeah, I think that dropping icu-le-hb is the best course forward. I want
to doublecheck that that does not have any unintended side effects. Ok
if I get back to you about this in 2
Hey folks,
I've (finally) opened an upstream bug for this to track progress:
https://github.com/OpenTTD/OpenTTD/issues/6922
If this cannot be fixed upstream in a timely manner, one additional
option would be to simply not compile OpenTTD with ICU layout support.
There is already a simpler fallbac
> Meanwhile, Matthijs can you tell us how the OpenTTD layout work goes?
> May you have any ETA from its upstream? It would be good to drop
> icu-le-hb very soon.
There's not much progress here. I haven't got time to really work on
this, and haven't gotten around to pushing at this since we first
sp
package consolekit
merge 898411 846320
thanks
Hi,
I found these two bugs are actually about the same issue, so I went
ahead and merged them.
I'm also seeing this issue on 0.4.6-6. Looking around, I found an old
bug report at Fedora which suggests this might be caused by ConsoleKit
calling udev-
Hi Guido,
> --git-pbuilder-options-append="option1"
> --git-pbuilder-options-append="option2"
>
> so you can decide on a per option basis if you want to append to the
> currently set value. Each "--git-pbuilder-options" would reset the whole
> thing and start over so:
>
> --git-pbuilder-opt
Hi Guido,
> > My suggestion of adding a --git-append-pbuilder-option could solve both
> > usecases:
> > - you can use --git-pbuilder-options on the commandline to override all
> >previously set options, including in gbp.conf
> > - you can use --git-append-pbuilder-option to extend any previo
Hi Guido,
> > When passing multiple options on the commandline, this is (for me)
> > unexpected but easily fixed by passing all needed options into a single
> > --git-pbuilder-options, but when a gbp.conf file also uses
> > "pbuilder-options", these are also overriden by the commandline, which
> >
Package: cowbuilder
Version: 0.87+b1
Severity: normal
Hi,
currently, cowbuilder seems to support only one occurance of the
--extrapackages option, where each subsequent occurance overrides the
previous one.
E.g.:
sudo -E cowbuilder --build --extrapackages=a.deb --extrapackages=b.deb some.dsc
r
Hi Guido,
I noticed one more related thing, also possibly a bug. It seems that the
arguments to --git-pbuilder-options are further processed. I tried
running this command:
gbp buildpackage --git-pbuilder-options=--extrapackage=/foo/a.deb\
--extrapackage=/foo/b.deb\ --bindmounts=/foo
Which resul
Package: git-buildpackage
Version: 0.9.8
Severity: normal
Hi Guido,
I was using the --git-pbuilder-options option to gbp-buildpackage today,
and was surprised that multiple options do not stack. Instead, each
--git-pbuilder-options passed overrides the previous one, so only the
last one is effect
Hi László,
> > So you're saying I could upload OpenTTD now, and it will be recompiled
> > with icu60 once that is uploaded to Sid? Or should I wait a few days?
> Well, the transition update and _maybe_ the real start is hours soon. But
> as I see, OpenTTD might be uploaded and built, installed a
Hi László,
> > First off: I have a pending new upstream version of OpenTTD that I'd
> > like to upload, but I don't want to interfere with this transition.
> > Should I hold it off, or do we expect that resolving these issues will
> > take a while and should I just upload it now (and have it build
Package: openttd
Version: 1.7.1-1
Severity: normal
Hi,
OpenTTD currently uses the ICU ParagraphLayout API for doing
internationalized wordwrapping. This usage is a problematic, since
ICU deprecated and removed their layout API for being buggy and
unmaintained. The ParagraphLayout API that OpenTTD
Hi folks,
I'm the maintainer of the OpenTTD package, and stumbled on this bug
report, which refers to my package as the last user of the
ParagraphLayout API in icu.
First off: I have a pending new upstream version of OpenTTD that I'd
like to upload, but I don't want to interfere with this transit
Hey folks,
previously, people suggested completely disabling ipv6 as a workaround
(or at least debugging tool). This, combined with the previous analysis
made me realize another workaround: Just disable ipv6 autoconf by the
kernel. I dropped these two lines in my sysctl.conf:
net.ipv6.con
Package: network-manager
Version: 1.10.4-1+b1
Followup-For: Bug #755202
Hi folks,
I've also been seeing this bug on my system for quite some while now,
and decided to investigate today. I haven't quite figured it out, but
I'll share my findings here.
>From the previous discussion on this bug, mo
d this fix from working. See
https://github.com/lxc/lxc/issues/2084 for more details.
Gr.
Matthijs
From f1aa85a4b1c1c38211a9fa15afac72b3df142b3d Mon Sep 17 00:00:00 2001
From: Matthijs Kooijman
Date: Sun, 14 Jan 2018 15:47:31 +0100
Subject: [PATCH] Backport upstream commits to fix runni
Package: parted
Version: 3.2-17
Followup-For: Bug #840710
Hi,
I'd also be grateful if this patch could be backported. In the current
situation, resizing of bootable partitions simply is not possible
without breaking things.
I also tried downgrading to (lib)parted 3.1, but that caused segfaults
i
Source: pam
Version: 1.1.8-3.6
Severity: normal
Hi maintainers,
When looking for some strange behaviour pam_unix, I came across a possible typo
in the securetty patch [1]. I'll highlight the relevant parts of the code
below.
if (isdigit(uttyname[0])) {
snprintf(ptname, sizeof(ptname)
Package: stterm
Followup-For: Bug #785219
Hi folks,
I can't really reproduce this problem, but for me `ls --color` outputs
color even when I run with TERM=foo or whatever, so there might be
something else going on.
However, I wanted to point out that the stterm package currently
provides stterm-
Hi Raphael,
> Would you like to become co-maintainer of live-build? I maintain
> it because I use it in Kali but I use only a very limited set of
> the features and it would be nice to have other people who can
> look at bugs.
I won't really have time to dedicate to that, unfortunately. I'm happy
hijs
>From 05e0703d82e0189e40d88f5070b1c2f955a0ad9e Mon Sep 17 00:00:00 2001
From: Matthijs Kooijman
Date: Tue, 29 Aug 2017 15:04:31 +0200
Subject: [PATCH 3/4] Pass --partscan to losetup
Recent versions of Linux, parted or some other bit of software cause
partition devices, like /dev/loop0p1 to be created
ks more gracefully in any case.
I've tested with version 1:20170807 and 1:20170829, but marked this bug
as found in 1:20161202 since that is the first version that has the
above commit.
Gr.
Matthijs
>From 0c313e9ed3d0de7cfa6ef8e8e21c01a08b8e4a8c Mon Sep 17 00:00:00 2001
From: Matthijs Kooij
8-4
live-build suggests no packages.
-- no debconf information
>From 406ed00e806abb84252033ac609fcc9bcd83 Mon Sep 17 00:00:00 2001
From: Matthijs Kooijman
Date: Mon, 28 Aug 2017 15:14:34 +0200
Subject: [PATCH 1/2] Error out when needed packages are missing on the host
Previously, Check_package would only show an err
Control: fixed -1 1:20161202
Control: notfixed 773833 5.0~a3-1
Control: fixed 773833 1:20161202
Hi,
it seems this bug wrt mbr.bin is fixed in live-build 1:20161202. The
changelog says:
* Correct syslinux/extlinux mbr.bin path. Closes: #773833
And looking at the source, this is indeed the chan
Source: ofono
Severity: wishlist
Hi,
The oFono git repository contains a number of helper scripts in the
test/ directory. These python scripts help to query the internal state of oFono
through dbus calls, and it would be helpful to have them available. It
is probably best to put them in a separat
1 - 100 of 448 matches
Mail list logo
