Hi Philipp,
thanks for the pointers, I'll try to test the alternative patch you've
suggested within the week.
On Sun, 16 Oct 2022 09:20:37 +
Philipp Kern wrote:
> Apparently I cannot test this within qemu OVMF (per [3] and it also
> didn't boot for me).
Interesting – this is how I tested
Hi Vangelis,
thanks for your report!
On Sun, 23 Jan 2022 17:32:34 +0200
Vangelis Koukis wrote:
> After installing syslinux on a FAT32 fs:
> (...)
> I see the md5sum of ldlinux.c32 doesn't match the md5sum of
> /usr/lib/syslinux/modules/bios/ldlinux.c32:
> (...)
>
> I don't know where syslinux/
Thanks for providing the details! Unfortunately I still don't have a
good idea of what could be causing the broken/truncated mails you're
seeing. I have a very similar setup and things are working fine here.
The way arpwatch creates and sends reports is roughly as follows:
* Create a temporary
Control: tags -1 + moreinfo
Hi Yanko,
thanks for your report! Please help me to understand what's happening
by providing the following information:
* How exactly is arpwatch invoked? Please provide the output of
`ps -U arpwatch -F` or (in case that doesn't show any processes)
`ps -eF | grep
Source: syslinux
Version: 3:6.04~git20190206.bf6db5b4+dfsg1-3
Severity: serious
Tags: ftbfs
With the new version of gnu-efi that was recently uploaded [1] to
unstable, syslinux fails to build from source.
So far I tried applying a simple fix from the upstream mailing list [2]
which result in a s
Package: lintian
Version: 2.106.0
Severity: normal
Dear lintian maintainers,
running lintian 2.106.0 against syslinux I'm getting the following
warnings:
W: syslinux source: superfluous-file-pattern debian/copyright bios
(Files-Excluded, line 8)
W: syslinux source: superfluous-file-pattern deb
Package: lintian
Version: 2.105.0
Severity: important
Dear maintainer,
I noticed that invoking lintian on a .dsc file in the current working
directory does not work in version 2.105.0:
$ lintian librtr_0.8.0-1.dsc
Warning in processable librtr_0.8.0-1.dsc: Use of uninitialized value $base in
p
Hi,
> Thanks for finding that! I'll report back once I've had a chance to
> try this.
The attached PR is quite large and I wasn't able to apply it against
the version now in bullseye, and I don't want to change to a different
systemd/udev altogether. Carefully reading the descriptions I'm
confide
Hi Michael,
thanks a lot for your quick response.
On Sun, 5 Sep 2021 19:44:15 +0200
Michael Biebl wrote:
> So you create a lot of partitions which all have the same label?
>
> Isn't this asking for trouble anyway as you can't be certain, which
> device the /dev/disk/by-label/dummy will point
Hi Guilhem,
thanks for your quick response.
On Sun, 5 Sep 2021 17:04:06 +0200
Guilhem Moulin wrote:
> Which concrete problem does this fix? At initramfs stage only
> required devices (holding /, /usr, the resume device, or those
> explicitely marked ‘initramfs’) are unlocked and we *do* need t
udevadm control --reload
Notice how the activation now is very fast. To undo this workaround
remove /etc/udev/rules.d/60-persistent-storage-dm.rules and reload udev
rules again.
The same issue is *not* present in the udev version from buster
(241-7~deb10u8).
Thank you
Lukas Schwaighofer
pgp7lJETh0lyP.pgp
Description: OpenPGP digital signature
atch, and if if the list is set but empty, no
> LVs match. Autoactivation should be used during system boot to
> make it possible to select which LVs should be automatically
> activated by the system. See lvmlockd(8) for more information
> about activation options ey and sy for shar
I was kindly pointed to
https://bugzilla.suse.com/show_bug.cgi?id=1166605#c5
privately (thanks!), which explains that __builtin_strlen is not
actually a "builtin" and relying on that without providing a strlen
implementation is not correct (and in fact broken with GCC-10).
I'm updating the patch
Control: reopen -1 !
Control: notfixed -1 3.3.2-2
Dear Maintainer,
this was redirected to "smtp.8debian" instead of "smtp.8postfix" so the
issue is still present:
$ man lmtp
man: can't open /usr/share/man/man8/smtp.8debian: No such file or
directory No manual entry for lmtp
Thanks
Lukas
Control: tags -1 + moreinfo
Hi Mikhail,
apologies for the long delay, there was a lot going on the before winter
holidays.
On Wed, 13 Nov 2019 17:59:13 +0100
Mikhail Morfikov wrote:
> My current kernel command line is about 400-character long. When it
> was shorter, I didn't have any issues wh
On Wed, 30 Oct 2019 22:41:48 +0100
Sven Joachim wrote:
> On 2019-10-30 21:03 +0100, Lukas Schwaighofer wrote:
> > I'm suspecting that there is somehow a mismatch between the version
> > of syslinux/extlinux used while installing (i.e. running `extlinux
> > -i`) and the
Control: tags -1 + moreinfo
Hi Sven,
thanks for your report!
On Wed, 30 Oct 2019 18:58:12 +0100
Sven Joachim wrote:
> Today I built myself a USB stick with grml on it (see #943838 for the
> problems I had with that). When booting an old 32-bit laptop with
> this stick syslinux threw some erro
Hi James,
On Fri, 6 Sep 2019 11:07:20 +0100
James Beck wrote:
> I tested a local build with that patch and I don't think it is a
> complete fix. In our setup, it stalls replication for our webmail
> users who use the Roundcube sieve plugin:
>
> Sep 05 23:21:04 dovecot[12574]: doveadm: Error:
Hi,
thanks for your report.
On Tue, 06 Aug 2019 01:58:43 +1100
Dev wrote:
> Arpwatch not working properly (bug) on Debian 10.0 (Buster)
> (...)
There has been an intentional change on how arpwatch is started in
buster. From the NEWS file (you should have seen the content of this
during the up
Hi Timothy,
thanks for reporting. The whole file organization of syslinux (both
which file is in which package, as well as the location of files) needs
improvement. This is something I intend to work on during the bullseye
cycle.
As part of that, I'll also look into whether we need both the per
Source: dovecot
Version: 1:2.3.2-1
Severity: important
Tags: upstream patch
Dear Maintainer,
starting with Debian version 1:2.3.2-1, dsync no longer syncs sieve
filters. Incoming syncs for sieve changes made on older servers (e.g.
using dovecot from stretch) are still synced, but changes made on
Control: tags -1 + confirmed patch
Hi Andreas,
On Fri, 3 May 2019 14:21:06 +0200
Andreas Steinel wrote:
> In version 6.04~git20190206.bf6db5b4+dfsg1-1, the bug that was closed
> in 6.04~git20171011.af7e95c3+dfsg1-6 is back - at least in the 64-bit
> UEFI part, legacy works fine:
>
> Full log i
Control: tags -1 + confirmed
Hi Wolfgang,
thanks for reporting!
On Thu, 10 Jan 2019 15:27:07 +0100
Wolfgang Scheicher wrote:
> After switching from stretch to buster i realized that the
> Hardware Detection Tool (HDT) in the Advanced options Boot menu fails
> with this error:
>
> Undef symbol
On Sun, 9 Dec 2018 12:48:30 +0100
Lukas Schwaighofer wrote:
> I've fixed this for my need with the following change:
I messed up the patch formatting, corrected below. Sorry for the noise.
--- /usr/bin/sbuild-createchroot2018-11-13 16:07:19.0 +0100
+++ sbuild-crea
Package: sbuild
Version: 0.77.1-2
Severity: normal
Tags: patch
Dear Maintainer,
the sbuild-createchroot --setup-only option is designed to perform setup
tasks on an existing chroot. Thus the check for non-empty directories
introduced in
https://salsa.debian.org/debian/sbuild/commit/53e250c
Seconded, we could really use a working Munich list again.
Hi Marco,
On Sun, 2 Sep 2018 14:08:09 +0200
Marco d'Itri wrote:
> When providing to syslinux.efi an http URL in option 67:
>
> dhcp-option=option:bootfile-name,http://pxe.example.net/EFI/SYSLINUX/syslinux.efi
>
> then it will try to download the modules like ldlinux.e64, the
> configuration f
Control: owner -1 debian-security-to...@lists.debian.org
Control: retitle -1 ITP: librtr -- Library implementing the client-side of the
RPKI-RTR Protocol.
This library has been gaining more popularity recently, e.g.
https://github.com/FRRouting/frr. Packaging it will enable more
software to be ea
On Sat, 18 Aug 2018 12:42:45 +0200
Lukas Schwaighofer wrote:
> Unfortunately my tests shows that with this new build the efi binary
> no longer works (at least when testing tianocore). I have not yet
> determined if this is also related to binutils and I suspect this is
> actually
Hi,
On Fri, 17 Aug 2018 21:43:50 +0200
Lukas Schwaighofer wrote:
> Matthias: As the binutils maintainer, can you provide any help? I
> don't really know how to proceed… and since this was broken by a
> Debian revision, it's probably not an upstream problem? Thanks!
I'v
Hi,
the problem started with the upgrade from binutils 2.31.1-1 to
2.31.1-2. If I download the following 4 packages and install them, I
can build syslinux just fine:
https://snapshot.debian.org/archive/debian/20180726T092202Z/pool/main/b/binutils/binutils-x86-64-linux-gnu_2.31.1-1_amd64.deb
https:
Control: tags -1 + confirmed
Hi Santiago,
I can confirm the build failures. The same error also happens when
building syslinux on buster from upstream's git repository.
I'll try to find out which dependency change caused the size of mbr.bin
to grow and will then probably need to work with upstre
Hello Alexander,
thank you for your report. Unfortunately I'll have to disappoint:
I've no plans on extending arpwatch to be able to "follow" ethernet
addresses. I also don't want to merge #527251, as it adds quite a bit
of code that we would need to support. Substantial changes like that
are t
Hello Roland,
thanks for your report!
On Mon, 8 Jan 2018 10:50:49 +0100
Roland Rosenfeld wrote:
> I use arpwatch via systemd, but had to notice, that arpwatch tries to
> start up before the network interface is fully up (some spanning tree
> issue). This leads to arpwatch failing and not corre
Hi again,
I just checked the contents of the
/etc/kernel/post{inst,rm}.d/zz-extlinux
files which are identical:
#!/bin/sh
set -e
# Exit if extlinux was removed (!= purged)
if [ -x /usr/sbin/extlinux-update ]
then
# Update
On Tue, 7 Nov 2017 21:48:04 +0100
Lukas Schwaighofer wrote:
> 0. The syslinux installer is part of the syslinux binary package
That should have been:
0. The syslinux installer is part of the *extlinux* binary package
Hi Laurent,
thanks for reporting this problem. Leftover files in /etc/kernel/*.d
are bad… I made a bit of research and found out the following, all of
which happened during the jessie release cycle:
0. The syslinux installer is part of the syslinux binary package
1. Version 3:6.03~pre1+dfsg-2:
Hi Christian,
thanks for reporting this problem. I've only recently taken over
maintenance of syslinux/pxelinux in the Debian CD Group. Sorry you had
to wait more than a year for a response…
We recently uploaded a pre-release of syslinux 6.04 to Debian
experimental. Amongst other things the cha
Source: gnu-efi
Version: 3.0.4-2
Severity: wishlist
Hi Julian,
please update gnu-efi to the latest upstream version (3.0.6).
It appears that upstream made a few small API changes from
3.0.4 → 3.0.5, which at least for syslinux will cause a FTBFS [1]
(patches are available). I think it's a good
+around 2005 by correcting the C/H/S order (thanks Thomas Schmitt,
+Closes: #879004).
+
+ -- Lukas Schwaighofer Sun, 29 Oct 2017 19:12:43 +0100
+
syslinux (3:6.03+dfsg-5+deb8u1) jessie; urgency=low
* Cherry-pick upstream patches that fix booting on some Chromebooks
diff -Nru syslinux
Package: snoopy
Version: 2.4.6-1
Severity: important
Tags: upstream
Forwarded: https://github.com/a2o/snoopy/pull/126
Process names are extracted incorrectly by snoopy when they contain
colons (:) and incorrectly by the test suite when they contain
white-space characters.
The parent process name
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: pu
Tags: stretch
Severity: normal
X-Debbugs-CC: debian...@lists.debian.org, debian-b...@lists.debian.org,
k...@debian.org
Dear release team and other involved parties,
I hereby ask for permission to update the sy
Hi Marek,
I've recently taken over maintenance of syslinux/exlinux as part of
the Debian CD Group, so I it's time to have a look at my own bug report.
Thanks for providing the link to the upstream changelog :) .
I've just compiled the most recent version of syslinux from git. It
turns out that e
Control: retitle -1 extlinux: cannot boot from ext4 filesystems with 64bit
feature enabled
Control: tags -1 - moreinfo + confirmed upstream
Hi,
thanks for reporting and working on this issue. I'm certain the
experienced problem is due to the 64bit feature in ext4, which is set by
default when u
Hi Thomas,
thanks for pushing this forward :) .
On Sat, 14 Oct 2017 19:53:46 +0200
"Thomas Schmitt" wrote:
> now that a new set of SYSLINUX packages is announced by
> (...)
> what to do with this bug report ?
> Re-assign to package "syslinux" and then close it ?
Well, that bug is only solved o
Control: tags -1 + confirmed
Hi Marek & Peter,
thanks a lot for not only reporting this issue but also finding and
testing the fix. I can also reproduce the problem and confirm that the
mentioned commit fixes the issue.
I am in the process of adopting syslinux as part of the debian-cd
team. A
Control: owner -1 Debian CD Group
Control: retitle -1 ITA: syslinux -- collection of bootloaders (DOS FAT and
NTFS bootloader)
Hi,
I intend to work on syslinux as part of the Debian CD Group. I'm open
to team maintenance and will probably need help every now and then
anyways, so if you read th
Package: devscripts
Version: 2.17.10
Severity: minor
Hi,
the uscan(1) man page states:
Please note that the short keyid 72543FAF is the last 4 Bytes, the
long keyid C77E2D6872543FAF is the last 8 Bytes, and the finger
print is the last 20 Bytes of the public key in hexadecimal form.
Hi Gabriel,
it seems you are getting the knack of it quickly :) . I don't have
any additional feedback. I hope you're able to find a sponsor soon.
You can also look at the available packaging teams [1]. For your
package it looks like the Debian Multimedia team [2] would be the most
suitable on
Hi Gabriel,
thanks for the git link, makes things easier for me.
> Where did you get pragha-1.3.3.tar.gz from?
> I got it from
> https://github.com/pragha-music-player/pragha/archive/v1.3.3.tar.gz.
I got the same one (but I used `uscan -dd` to download, which uses the
debian/watch file and also
Hi Gabriel,
thanks for improving upon our suggestions.
On Sun, 24 Sep 2017 15:15:41 -0300
"Gabriel F. T. Gomes" wrote:
> Lukas,
> In that same message [1], you suggested the use of a version control
> system, but I don't know where to make it public (I know that alioth
> is being discontinued, s
Package: nm.debian.org
Severity: important
Hi,
the confirmation e-mail for newly created entries/accounts on
https://nm.debian.org contains a `Reply-To: t...@example.com` header.
This header should be removed.
Thanks
Lukas
Package: nm.debian.org
Severity: minor
Hi,
I was surprised to find my account at nm.debian.org deleted after 30
days. As account deletion also means losing the short biography, I
think the system should either
* warn the user (possibly as part of the confirmation mail) that the
account will be
Package: libpcap0.8-dev
Version: 1.8.1-4
Severity: important
X-Debbugs-CC: pkg-security-t...@lists.alioth.debian.org
Dear libpcap maintainer,
the fix for Bug#760370 [1] has caused the output of
pcap-config --libs
to start with a space. This appears to be a problem for applications
using the
Hi,
while I'm not against introducing the patch, in my opinion we should
file a bug against libpcap0.8-dev instead (or at least in addition).
The starting space in the output of
pcap-config --libs
is due to Debian specific changes to the pcap-config tool. This
starting space in the output mig
Hi Timo,
thanks for the very thorough bug report and for discussing it with
upstream. I'm doing a bit of housekeeping of the nmap bugs and tried
to determine if this bug is still present.
According to upstream [1], this issue might have been mitigated by
newer versions of the Linux kernel, in pa
Control: tags -1 + moreinfo
Hi Gary,
you reported this bug regarding nmap induced kernel panics a few years
ago: https://bugs.debian.org/772731
Do you still experience this bug? If so, can you provide any
information regarding the kernel panic (e.g. picture of the backtrace
printed by the kerne
Control: tags -1 + moreinfo
Hi Miguel,
sorry for reviving the old bug report
https://bugs.debian.org/535441
you filed a few years ago, I'm doing a bit of housekeeping.
Do you still have the same setup and does the problem still persist?
If that's the case, I will need your help in determinin
Control: tags -1 + moreinfo unreproducible
Hi Fabrice,
I'm doing a bit of housekeeping of old nmap bugs. Are you still able
to reproduce the bug you reported here more than 10 years ago:
https://bugs.debian.org/396062
I cannot reproduce the problem myself. I suspect that this problem is
either
Hi Michael,
sorry for reviving this almost 9 year old bug, I'm trying to do a bit
of housekeeping :) .
I suspect that what you experienced is a limitation of libdnet (the
library that nmap uses to query the routing table) in combination with
policy routing: It looks like the "default" table is n
Control: severity -1 wishlist
Control: tags -1 + upstream
Hi Sheridan,
thanks for your bug report. While I agree that this might be a useful
feature, it's outside the scope of packaging. If you want arpon to
deal with changes in network interfaces gracefully, you should try to
convince the upst
ols-dev are being superseded
by the dh_update_autotools_config debhelper command [1]
I've added a suggestion as patch.
Thank you
Lukas Schwaighofer
[1]
http://lists.alioth.debian.org/pipermail/debhelper-devel/2017-August/006303.html
diff --git a/dh-autoreconf.pod b/dh-autoreconf.pod
index
Hi Adrian,
On Thu, 20 Jul 2017 14:57:46 +0300
Adrian Bunk wrote:
> dsniff sometimes FTBFS in parallel builds: (...)
> The problem is a race condition where decode_mountd.c includes
> mount.h before rpcgen has finished generating it.
Indeed.
> A fix is attached.
Thanks a lot for debugging this
Control: reopen -1
control: tags -1 + upstream
Control: forwarded -1
https://wald.intevation.org/tracker/index.php?func=detail&aid=6929&group_id=29&atid=220
Control: severity -1 wishlist
Hi,
since radcli is source compatible with freeradius-client we shouldn't
have to drop this functionality. I
Control: severity -1 wishlist
Hi Thomas,
> it would be nice if gmrun would read its configuration file according
> to the xdg base directory specification and thus not clutter my $HOME:
> http://wiki.debian.org/XDGBaseDirectorySpecification
I agree that this would be desirable. Unfortunately up
Control: retitle -1 RFS: gmrun/0.9.2-3 [ITA]
My last commit accidentally increased the Debian version, corrected.
pgpDeA3pvxDKQ.pgp
Description: OpenPGP digital signature
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for the gmrun package, which I intend to
adopt. I've uploaded the current state to mentors:
https://mentors.debian.net/package/gmrun
I've done the packaging using git. You can access my repository from
Control: tags -1 + confirmed
Hi again,
I can confirm that arpwatch does indeed start too early when capturing
on bridge devices. I have also verified that adding $network to the
Required-Start field in the LSB header fixes the problem.
I will push the fix into our git repository soon, but I will
Hi,
thanks for reporting this issue.
On Mon, 08 May 2017 21:40:06 -0700
jmol...@swoncology.net wrote:
> Arpwatch seems to start before the networking is really ready. In this
> case, we are listening on a bridge interface, so that might have
> something to do with it.
>
> This might be a problem
which has
severity important. The upload also includes a minor update to the man
page.
The changelog entry is:
hydra (8.3-3) unstable; urgency=medium
* Team upload.
[ Gianfranco Costamagna ]
* Fix newline in manpage (Closes: #853807)
[ Lukas Schwaighofer ]
* Allocate required po
Hi,
I think the problem reported by Antonio is because the default RAM size
of kvm is too little.
Antonio: Can you retry with `-m 256M` or even `-m 512M` to have more
than the default of 128M RAM?
Yves: I cannot reproduce the problems reported by you. In particular,
microcode packages should n
Control: found -1 hydra/8.3-2
Control: tags -1 + upstream
Hi Ivan,
thanks for reporting this bug. I was able to reproduce the problem
(also for the version 8.3-2 from Debian stretch). The bug is also
already known upstream:
https://github.com/vanhauser-thc/thc-hydra/issues/27
I've just looke
Hi Stephan,
thanks for your reply, I'll make the discussed changes.
On Sat, 22 Apr 2017 15:00:29 +0200
Stephen Kitt wrote:
> What’s the situation with upstream arpwatch? Is there an upstream now?
Unfortunately not… but as there are still use cases for this software
and no better alternative ex
problem. The changelog
entry is:
dsniff (2.4b1+debian-25) unstable; urgency=medium
* debian/control: Added myself to Uploaders.
* Make sure libmissing.a is built before PROGS (Closes: #860611).
-- Lukas Schwaighofer Wed, 19 Apr 2017 20:15:27
+0200
The source debdiff between the versions
Control: tags -1 + pending
Hi,
On Wed, 19 Apr 2017 15:36:07 +0200
Marcos Fouces wrote:
> Maybe you should create a "debian/stretch" branch from
> 2.4b1+debian-24 tag and commit your patch here. If you want, you can
> add yourself as uploader and tag it as "2.4b1+debian-25" release.
> Later we wi
an-25) unstable; urgency=medium
+
+ * Team upload.
+ * Make sure libmissing.a is built before PROGS (Closes: #860611).
+
+ -- Lukas Schwaighofer Wed, 19 Apr 2017 10:14:38 +0200
+
dsniff (2.4b1+debian-24) unstable; urgency=medium
* Fix FTCBFS: Pass triplet-prefixed CC to configure.
diff --git a/d
Hello Helmut,
On Thu, 13 Apr 2017 22:05:02 +0200
Helmut Grohne wrote:
> > Does that mean that the snippet
> > > include /usr/share/dpkg/architecture.mk
> > > ifeq ($(origin CC),default)
> > > export CC := $(DEB_HOST_GNU_TYPE)-gcc
> > > endif
> > can be removed again from debian/rules? I trie
Control: tags -1 + moreinfo
Hi Philippe,
I recently took over arpwatch maintenance and I'm working through the
list of open bugs. I'm writing you regarding a bug report about
arpwatch not starting you filed back in 2012 [1].
Is this issue still present in the version of arpwatch in Debian
jessie
Hi Debian cross team,
I have a question regarding Bug#852360 and cross compiling dsniff.
The bug report mentions moving to a more recent autotools fixes the
problem as well. Since the package uses debhelper 10 (which enables the
autoreconf sequence by default), the configure script is regenerated
Control: severity -1 wishlist
Hi Brian,
thanks for your bug report. Unfortunately, arpwatch's upstream is dead
so we cannot forward the feature request. I'm lowering the severity to
wishlist. I currently do not plan on implementing exceptions for the
flip flop detection.
Regards
Lukas
pgpm6Nwc
Control: retitle -1 arpwatch: allow specific IPs to be used by multiple MAC
addresses without generating flip flop messages
Control: severity -1 wishlist
Hi,
thanks for your bug report.
Unfortunately, suppressing specific flip flop messages is not
implemented in arpwatch. Normally we would for
Hi Stephen,
I recently took over maintenance of arpwatch as part of the
pkg-security team, sorry for reviving this more than 7 years old bug.
Thanks for reporting the bug regarding the restart functionality and
providing a patch. As you probably know (or knew 7 years ago), the
restart functionali
Control: tags -1 + moreinfo
Hi,
sorry for reviving such an old bug report. I recently took over
maintenance of arpwatch as part of the pkg-security-team.
In your bug report you described two different problems.
1. Arpwatch does not start properly after startup, requires manual
restart
Is
Hi Hugo,
On Wed, 5 Apr 2017 18:25:04 +0200
Hugo Lefeuvre wrote:
> Are you already a member of the team ? If yes, could you move your git
> repository to
> https://anonscm.debian.org/git/pkg-security/arpwatch.git ?
I've now officially joined the team, the repository is available at
that URL.
I'
On Thu, 6 Apr 2017 15:24:04 + (UTC)
Gianfranco Costamagna wrote:
> - $(INSTALL) -m 555 -o bin -g bin arpwatch $(DESTDIR)$(BINDEST)
> + $(INSTALL) -Dm 555 -o bin -g bin arpwatch $(DESTDIR)$(BINDEST)
>
>
> this should work too (as said above) and is less invasive :)
As everybod
Hi Christian,
On Thu, 6 Apr 2017 14:30:24 +0200
Christian Seiler wrote:
> The problem is that dirs is only interpreted by dh_installdirs, which
> is typically run after dh_auto_install, so that wouldn't actually
> solve your problem.
It does solve the problem (i.e. the error is gone if `usr/sbin
Hi Hugo,
thanks again for the review and the comments!
On Wed, 5 Apr 2017 18:25:04 +0200
Hugo Lefeuvre wrote:
> > * debian-watch-may-check-gpg-signature
>
> I wouldn't override debian-watch-may-check-gpg-signature btw.
Ok, I will revert that override.
> > If I remove `usr/sbin` from dirs, b
Hi Hugo,
thanks a lot for looking at this. I have made some changes to the
package based on your feedback, pushed them to my git repository and
uploaded the new version to mentors:
https://mentors.debian.net/package/arpwatch
Some further questions and comments follow inline below.
On Tue, 4 Apr
Hi security tools packaging team,
On Mon, 27 Mar 2017 23:03:19 +0200
Lukas Schwaighofer wrote:
> Gianfranco suggested also asking the pkg-security-team for possible
> sponsors. It would be great if one of you could have a look and
> provide guidance! If team maintenance is be possible,
Hi,
in case anybody else is frustrated about this, I've found a
workaround (as root):
mkdir -p /etc/skel/.config/chromium/Default
touch "/etc/skel/.config/chromium/First Run"
echo "{}" > /etc/skel/.config/chromium/Default/Preferences
The lines responsible for this mess in the code seem to be (a
s (documented in
NEWS). I would be happy if someone has ideas how to avoid that.
Gianfranco suggested also asking the pkg-security-team for possible
sponsors. It would be great if one of you could have a look and provide
guidance! If team maintenance is be possible, I'd like that very
much
Hi Martin,
the package is already in the debian archive (as part of the "unstable"
release) and the release team has approved the unblock request [1]. You
can monitor the transition to stretch here:
https://tracker.debian.org/pkg/gmrun
The current migration status is:
Too young, only 2 of 5 d
rn type of gtk_completion_line_get_type (Closes: #857065)
-- Lukas Schwaighofer Sun, 12 Mar 2017 23:49:46
+0100
I've attached the debdiff between the version in testing and in
unstable.
Thank you
Lukas Schwaighofer
diff -Nru gmrun-0.9.2/debian/changelog gmrun-0.9.2/debian/changelog
--- gmr
065
and we basically agreed to only fix the RC bug and make further changes
to the package in buster (and possibly experimental) only.
Thank you
Lukas Schwaighofer
pgpbMW6tLeZc7.pgp
Description: OpenPGP digital signature
t run.
I have not found a way to disable the dialog :( . As this seems to be
an upstream bug feel free to close.
Thanks
Lukas Schwaighofer
pgpJiwbQ4Bbsi.pgp
Description: OpenPGP digital signature
nd to disable this behavior is to add the
following to /usr/share/chromium/master_preferences:
"sync_promo": {
"show_on_first_run_allowed": false
}
It would be nice if you could either disable this sync promotion by
default or provide a way to disable it (without requiring dpkg-divert).
Thank you
Lukas Schwaighofer
pgp6v9EMRoKXL.pgp
Description: OpenPGP digital signature
On Sun, 12 Mar 2017 23:11:39 +0100
Mateusz Łukasik wrote:
> I think now package should stay untouched only RC bug need be fixed.
> After that I suggest making package orphaned and upload as QA to
> experimental with more fixes.
That sounds reasonable. I've uploaded a version which just contains
#x27;m not sure if enabling BIND_NOW in addition to PIE is considered a
trivial enough change, or if we should stick to only fixing the bug so
it can get unblocked by the release team.
Thanks
Lukas Schwaighofer
[1] https://wiki.debian.org/HardeningWalkthrough
pgpTyX54gBSWk.pgp
Description: OpenPGP digital signature
YED/3.
Sounds good to me, thanks for taking care of this!
Regards
Lukas Schwaighofer
pgpW8Ylq8FPe1.pgp
Description: OpenPGP digital signature
Hello Andreas,
On Fri, 10 Mar 2017 14:10:15 +0100
Andreas Henriksson wrote:
> On Fri, Mar 10, 2017 at 01:36:06PM +0100, Lukas Schwaighofer wrote:
> > On Fri, 10 Mar 2017 13:14:57 +0100
> > Andreas Henriksson wrote:
> > > Either way I think we should take the
1 - 100 of 123 matches
Mail list logo