Package: spamassassin
Version: 4.0.1~pre1-1
Severity: normal
Tags: patch
In this following commit systemd timers were introduced.
https://salsa.debian.org/debian/spamassassin/-/commit/f2753c72e8052f03e60c5a5532ccb4e1080b6406#b323bf39a23be9c27fd25690d333c4e9dbcddec7
In this following commit
George Robbert wrote:
> On an intel system, where uCode/AMD.pm was run before uCode/Intel.pm
>
> intel_sys1# needrestart -b
> NEEDRESTART-VER: 3.6
> NEEDRESTART-KCUR: 6.1.0-18-amd64
> NEEDRESTART-KEXP: 6.1.0-18-amd64
> NEEDRESTART-KSTA: 1
> NEEDRESTART-UCSTA: 1
> Use of
Richard Laager wrote:
> Bob Proulx wrote:
> > if ! getent passwd ntpsec > /dev/null; then
> > addgroup --system --quiet ntpsec
> > fi
> > if ! getent group ntpsec > /dev/null; then
> > adduser --system --quiet --ingroup ntpsec \
Package: ntpsec
Version: 1.2.2+dfsg1-3
Severity: normal
Tags: patch
Every time the ntpsec package upgrades it attempts to unconditionally
add the ntpsec user and group as per the following postinst snippet.
addgroup --system --quiet ntpsec
adduser --system --quiet --ingroup
Ansgar wrote:
> > On systems using sysvinit and not yet UsrMerged this snags a
> > problem in the sysvinit init script. I know and understand that
> > this is not a combination that you or Debian is officially
> > supporting. But it would help out interoperability if a one line
> > fix were
Package: bind9
Version: 1:9.19.17-1
Severity: normal
Tags: patch
A recent change in the iproute2 package moved the installed location
of the "ip" program from /bin/ip to /usr/bin/ip with the
iproute2-6.5.0-5 packaging. That's all well and good of course.
On systems using sysvinit and not yet
First let me thank you Holger for addressing the issue and resolving
it. It is much appreciated! Things are once again in a happy state.
Michael Biebl wrote:
> Bob Proulx wrote:
> > Holger Levsen wrote:
> > > Bob Proulx wrote:
> > > > The introduction of systemctl
Holger Levsen wrote:
> Bob Proulx wrote:
> > > where?
> > The /etc/logrotate.d/munin-node file contains TAB characters.
>
> yes, on purpose :)
Sure. I use TABs all of the time. I was only commenting on my email
describing the patch!
Bob
Holger Levsen wrote:
> Bob Proulx wrote:
> > The introduction of systemctl is problematic especially when used in
> > chroots.
>
> systemctl handles chroots, so can you elaborate on this?
The policy-rc.d layer was created so that dpkg upgrading packages in
chroot
Package: munin-node
Version: 2.0.73-2
Severity: normal
Tags: patch
The recent upgrade to 2.0.73-2 from 2.0.73-1 introduced the following changes.
--- a/logrotate.d/munin-node
+++ b/logrotate.d/munin-node
@@ -3,7 +3,11 @@
missingok
rotate 7
compress
- copytruncate
+
Package: procmail
Version: 3.24-1
Severity: normal
I am very happy to see procmail upstream is now active again!
Excellent news! I am a long time user and have quite a few mail
filtering rules.
The recent upgrade to 3.24 broke using a pipe action to set a variable
using stdin. Reverting to
Package: ksh93u+m
Version: 1.0.3-1
Severity: normal
Upgrading today I noticed this warning printed by the package.
update-binfmts: warning: current package is ksh93u+m, but binary format
already installed by ksh
Looking a little closer I find that the package did not transition the
binfmts
Package: mutt
Version: 2.2.3-1
Severity: normal
I upgrade my Sid Unstable desktop daily. The upgrade from 2.1.4-1 to
2.2.3-1 breaks the change-folder action (normally bound to 'c').
Normally and up through mutt 2.1.4-1 (at least) typing 'c' would
prompt with the next mailbox that has new mail
I posted an update to the upstream bug tracker.
https://savannah.gnu.org/bugs/?61125
Bob Proulx wrote:
> In today's daily upgrade wget 1.21.2-1 was installed and now emits a
> spurious "SSL_INIT" message. This is breaking scripts. :-(
>
> $ wget -q -O/dev/null https://www.example.com/
> SSL_INIT
Already fixed upstream.
https://git.savan
Package: wget
Version: 1.21.2-1
Severity: normal
In today's daily upgrade wget 1.21.2-1 was installed and now emits a
spurious "SSL_INIT" message. This is breaking scripts. :-(
$ wget -q -O/dev/null https://www.example.com/
SSL_INIT
A temporary workaround is to downgrade to the
Package: man2html
Version: 1.6g-14
Severity: normal
The recent change to "which" now cascades to this weekly message.
From: Cron Daemon
To: root
Subject: Cron test -x /usr/sbin/anacron || ( cd / && run-parts
--report /etc/cron.weekly )
/etc/cron.weekly/man2html:
I also hit this today with the latest upgrade. On a system that has
been upgraded many times in the past. It's 2.02+dfsg1-20+deb10u4
upgrade this week caused it to fail to boot. It's was installed in
2014 and upgraded continuously since then.
root@euphoria:~# ll /var/log/installer/syslog
Matthias Klose wrote:
> I prepared the time 1.9 release, and I'd like to NMU the package, planning to
> upload on Tuesday to DELAYED/7.
Thank you for preparing this NMU. I appreciate your help with this
package. It is okay with me if you upload it to an earlier delayed
queue if you desire.
Bob
Thorsten Glaser wrote:
> Bob Proulx wrote:
> > root@angst:/etc# find /etc/rc?.d -name '*bind9' -delete
> > root@angst:/etc# find /etc/rc?.d -name '*bind9'
> >
> > All removed. The re-install will reset the links to the defaults.
> >
> > root@
This appears to be a minimal way to recreate the problem. Try this.
env -i PATH=$PATH HOME=$HOME TERM=$TERM MANWIDTH=80 /usr/bin/emacs -Q -nw
Then I will repeat the recreation instructions.
emacs -Q# no configuration
M-x man RET # look at a man
Bob Proulx wrote:
> Rob Browning wrote:
> > And you could probably eliminate more variables by testing in a minimal
> > debian VM, particularly if you also see the problem via the console
> > (i.e. emacs -nw).
>
> I generally only use emacs -nw and would find it quite s
Rob Browning wrote:
> Hmm, I don't see that here. That is, after the final C-x o, the manpage
> buffer continues to show the ls "SEE ALSO" section.
Hmm... That's annoying for me that it isn't universial.
> I wonder if "something else" could be interfering. If it's easy, I
> suppose you might
Package: emacs
Version: 1:27.1+1-2
Severity: normal
This is terribly annoying. :-(
emacs -Q# no configuration
M-x man RET # look at a man page
ls RET # something a few pages long
C-x o # go there
Package: mariadb-server-10.5
Version: 1:10.5.5-1
Severity: normal
Since the daily Sid upgrade to mariadb-server-10.5 1:10.5.5-1
on Monday, 2020-09-28, one now receives the following from logrotate
due to the /etc/logrotate.d/mysql-server file.
my_print_defaults: unknown option '--mariadbd'
Package: smartmontools
Version: 7.1-1
Severity: normal
Tags: patch
Since the recent updates to debianutils 4.10 the tempfile program now
emits a run time deprecation warning. This is now printed by the
smartmontools smartd-runner program whenever it is invoked.
Attached is the trivial and
Elimar Riesebieter wrote:
> Argument "1.20200513.1" isn't numeric in numeric ge (>=) at
> /usr/share/perl5/Mail/SpamAssassin/Plugin/DKIM.pm line 686
> Argument "1.20200513.1" isn't numeric in numeric ge (>=) at
> /usr/share/perl5/Mail/SpamAssassin/Plugin/DKIM.pm line 809.
In order to silence
Thomas Liske wrote:
> thanks for the report. The bug has been fixed upstream.
Awesome! :-)
Bob
Package: needrestart
Version: 3.0-1
Severity: normal
On some systems I see the following:
root@clash:~# needrestart -b
NEEDRESTART-VER: 3.0
NEEDRESTART-KCUR: 4.15.0-1-amd64
NEEDRESTART-KEXP: 4.15.0-1-amd64
NEEDRESTART-KSTA: 1
NEEDRESTART-UCSTA: 0
Use of uninitialized value
Package: mutt
Version: 1.9.3-1
Severity: normal
I was surprised to find that a mail message really looked awful when
displayed in Mutt. (It was a financial report.) But then I realized
that Mutt was not displaying all of the dots! What?
This line should have . 25 dots
severity 885989 wishlist
tags 885989 + wontfix
thanks
TemTem wrote:
> A large portion of websites are being (willingly) attacked by
> man-in-the-middles (MitM) such as Cloudflare.
When someone commissions a service provider such as CloudFlare to host
their web site CloudFlare then of course
H.-Dirk Schmitt wrote:
> The sort behaviour depends deeply on the LC_COLLATE settings.
> See e.g. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884943
>
> This behaviour is not documented in the primary documentation
> provided by `sort --help` or `man sort`.
But it is mentioned in all three
H.-Dirk Schmitt wrote:
> O.k. I understand that it is working as defined in the 19th century.
> So it is maybe not a bug but still a weird behaviour.
>
> In my case it takes several hour to find out why I don't get rid of
> ~ 2.000 false entries in a blocklist for squid.
>
> Reason for the lost
Noah Meyerhans wrote:
> Believe it or not, it's a bug that you were running spamd in the first
> place, as you had not enabled it. spamd is an optional feature of the
> spamassassin package. Therefor, unlike most daemons shipped with Debian,
> it is disabled by default and only enabled at the
Package: mutt
Version: 1.9.1-4
Severity: normal
With the latest mutt package it appears that local email addresses are
now created using the short host name instead of the FQDN as done
previously.
With the previous mutt version:
$ mutt rwp
To: Bob Proulx <r...@joseki.proulx.
Package: mutt
Version: 1.9.1-3
Severity: normal
With the lastest package we now have a regression of Bug#823971
https://bugs.debian.org/823971 where viewing text/html parts is
displayed as the raw html instead of using mailcap. At the previous
bug report time it was determined to be the loss of
Package: tinyproxy
Version: 1.8.4-4
Severity: normal
While doing the daily upgrade in Sid today:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
tinyproxy-bin
The
Package: php7.0-fpm
Version: 7.0.22-3
Severity: normal
File: /etc/init/php7.0-fpm.conf
The /etc/init/php7.0-fpm.conf file is missing a final newline making
it a non-text file. Please add a newline so that every "line" in the
file is terminated with a newline, literally making each line a line.
Now that I am reminded to look at this bug again I will just note that
the section of code I reported this bug against in the postinst seems
to have been removed entirely in some version. So almost certainly
this bug should have been closed at that previous time.
Bob
Hello Manuel,
Manuel A. Fernandez Montecelo wrote:
> It seems that the changelog [1] mentions "Addresses", not "Closes",
> therefore this bug report has not been closed even if the original
> problem has really been fixed.
That NMU only "addressed" bug#751776 but didn't close it because there
> $ cat /var/lib/dpkg/info/sudo.postinst
> [...]
> if [ -f /etc/sudoers.dist ]; then
> rm /etc/sudoers.dist
> fi
> [...]
...
> sorry, my mistake :-(
>
> the sudoers.dist is an example file in another directory
For the previous history of this bit of postinst code please see
Bug#862309
Alban Browaeys wrote:
> This is likely sssd related.
>
> I upgraded both today (sssd to 1.15.3-1) and "sudo ls" output was empty.
>
> Local workaround was to comment out "sss" on /etc/nsswitch.conf "sudoers:"
> sudoers:files sss
> to
> sudoers:files #sss
While sss might be
Hello Jean-Luc,
Jean-Luc Coulon wrote:
> Thank you for the clear and detailed informations.
You are most welcome. I know it was a confusing case.
> Yes, *I* use cat (display a file on a terminal) as you said since... well...
> maybe 1976 ;) But in these years, the standard output was a belt
Hello Francois,
Francois Mescam wrote:
> I've made some test about this error and to trim to 200 caracters the string
> I modify line 923 to :
>
> $str =~ s/^(.{0,200}).*$/$1/gs;
>
> With perl 5.26 there no warning and it gives the result explained by the
> comment.
This modification does
Dale Harris wrote:
> Package: coreutils
> Version: 8.26-3
> Severity: normal
> Tags: upstream
>
> Dear Maintainer,
>
>
> Just trying to figure out what the first, second, third days are of a month.
>
> So for August 2017:
>
>
> August 2017
> Su Mo Tu We Th Fr Sa
>1 _2 34
Package: src:linux
Version: 4.11.11-1+b1
Severity: normal
My Sid desktop is normally updated daily. After being gone for some
days I applied the latest package upgrades, including the latest
linux-image-4.11.0-2-amd64 kernel. Immediately the system immediately
began suffering problems. The
Noah Meyerhans wrote:
> Ivan Sergio Borgonovo wrote:
> > After upgrading perl to 5.26.0-4 I get:
> >
> > Unescaped left brace in regex is deprecated here (and will be fatal in Perl
> > 5.30), passed through in regex; marked by <-- HERE in m/^(.{ <-- HERE
> > ,200}).*$/ at
found 1.0-6
notfound 2.0-5
thanks
Fixing my goofed up cross-versioning from the original report. Sorry
about that.
Package: fonts-orya-extra
Version: 2.0-5
Severity: normal
This is almost certainly related to https://bugs.debian.org/854166
which reported a related issue of which the fix almost certainly
created this one.
Today's Sid upgrade brought in a change from having a directory to
having a file of the
Package: fonts-guru-extra
Version: 2.0-4
Severity: normal
This is almost certainly related to https://bugs.debian.org/854166
which reported a related issue of which the fix almost certainly
created this one.
Today's Sid upgrade brought in a change from having a directory to
having a file of the
Package: fonts-gujr-extra
Version: 1.0-6
Severity: normal
This is almost certainly related to https://bugs.debian.org/854166
which reported a related issue of which the fix almost certainly
created this one.
Today's Sid upgrade brought in a change from having a directory to
having a file of the
Package: fonts-deva-extra
Version: 3.0-4
Severity: normal
This is almost certainly related to https://bugs.debian.org/854166
which reported a related issue of which the fix almost certainly
created this one.
Today's Sid upgrade to 2.0-5 brought in a change from having a
directory to having a
Package: fonts-beng-extra
Version: 2.0-5
Severity: normal
This is almost certainly related to https://bugs.debian.org/854166
which reported a related issue of which the fix almost certainly
created this one.
Today's Sid upgrade to 2.0-5 brought in a change from having a
directory to having a
Paul Wise wrote:
> Michael Biebl wrote:
> > the latest update installed a new conffile /etc/sudoers.dist.
> > Afaics, this is a sample file provided by upstream and I don't think
> > this should go into /etc
>
> Agreed, but it might be useful to install it as an example instead.
> A sudoers
Emmanuel Revah wrote:
> Dear Maintainer,
Hello Emmanuel. I am not the maintainer but I have a suggestion.
When you find strange things like this it is always good to double
check using one of the command line tools. Note also that many sites
have custom 404 pages that may be fooling you.
Michael Musenbrock wrote:
> sort produces wrong output with combined '-u' and '-n' switch, if input lines
> have an preceding '\' character.
I think you have a misunderstanding of what is happening here.
> # echo -e "\2\n\1\n\2" | sort -u -n
First lets see what is produced by echo -e with the
reassign 687149 sa-exim
thanks
Marco Gaiarin wrote:
> Ahem, this little annoying bug is still here in jessie.
>
> Attached current patch for jessie.
...
> ---exec /usr/bin/sa-compile -- --quiet
> +--exec /usr/bin/sa-compile -- --quiet > /dev/null 2>&1
...
> -
severity normal
thanks
Hans-J. Ullrich wrote:
> Dear Maintainer,
I am not the maintainer. I am simply another long time user.
> either I misunderstood resolvconf or I resolvconf does not recognize dns
> entries.
> In /etc/network/intefaces I have
I believe you are misunderstanding how
Sébastien Delafond wrote:
> On Dec/03, Bob Proulx wrote:
> > By my count there are 23 "<<" dependencies in use with mitmproxy!
> > Wow! That is a lot of very fragile and breakage prone packages. It
> > is doomed to have repeated breakages in Sid and Test
by the patch provided in Bug#833741#15 by Kristian Klausen
+but rewritten. Closes: #833741.
+ * Adds in 32-bit support.
+
+ -- Bob Proulx <b...@proulx.com> Mon, 12 Dec 2016 15:41:55 -0700
+
pepperflashplugin-nonfree (1.8.1+deb8u1) jessie; urgency=medium
* Non-maintainer upload.
Package: bash
Version: 4.4-2
Severity: normal
In the packaged /etc/skel/.profile it sources the .bashrc *before*
setting PATH. But PATH should be set before not after. Or put
another way the sourcing of the .bashrc file should be the last thing
the .profile does and not the first. That way any
Manolo Díaz wrote:
> I find du buggy. I think it's taking International System of Units
> values as if they was binary values. An example:
>
> # stat file.pdf
> File: 'file.pdf'
> Size: 160594Blocks: 320IO Block: 4096 regular file
^^^ 320
Package: mitmproxy
Version: 0.18.2-3
Severity: important
The dependencies for mitmproxy render it uninstallable in Sid today
due to "Depends: python-passlib (<< 1.7)". But python-passlib 1.7.0-1
was uploaded to Sid on 2016-11-28. This is basically a deja-vu bug of
Bug#844060 with a different
Bas Zoetekouw wrote:
> -eval mail $XHEADERS -s \"$SUBJECT\" \"$MAILTO\" < "$MAIL"
> +( printf "$hdr\n"; echo; cat $MAIL ) | sendmail -t
If using sendmail and reading from stdin then the -oi option should
also be used. The sendmail man page says:
-oi When reading a
Package: mitmproxy
Version: 0.18.2-1
Severity: normal
The dependencies for mitmproxy render it uninstallable in Sid today
due to "Depends: python-html2text (< 2016.9.19)".
The following packages have unmet dependencies:
mitmproxy : Depends: python-html2text (< 2016.9.19) but 2016.9.19-1 is to
Leszek Dubiel wrote:
> Dear Maintainer, :)
Note that I am not the maintainer but another long time shell user.
> Create file /tmp/test that contains:
>
> echo 'a\nb'
Use of the echo command with escape sequences is inherently
non-portable behavior. See the bash FAQ item E5.
severity 841427 important
tags 841427 + pending
thanks
Changing severity level to prevent removal from Testing. This is a
build time issue not a run time issue. I don't think this is a severe
enough problem to warrant removing the working package from Testing.
Bob
Chris Lamb wrote:
> unifdef fails to build from source in unstable/amd64 under some
> locales (eg. LANG="fr_CH.UTF-8").
Thank you for the report. I am preparing a new package upload and
will fix this in that upload.
> This is due to hard-coded error messages in the testsuite:
I would say due
Андрей Василишин wrote:
> Thanks for your reply.
> If you watched my first message, you can see difference between df and du
> used space 237G vs 24G. There are no open deleted files. If I unmount this
> filesystems and do fsck, du and df will show the same used space.
I did read your message
Андрей Василишин wrote:
> Usually df -h and du -hs shows the same used space. But now I have a
> problem. I am using two SSD for a cache. Script all time writes and deletes
> files.
>
> df -H
> /dev/sdc1 237G 178G 47G 80% /megastorage1
> /dev/sdb1 237G
Kevin Bradenstein wrote:
> everytime I start chromium the gnome-keyring starts.
> This behaviour is very annoying, because I am using a tiling window
> manager and the gnome-keyring windows captures all input except ESC.
Agreed. I am hoping there is a way to disable that new behavior. It
is
Harald Dunkel wrote:
> Pádraig Brady wrote:
> > > tail --retry doesn't
> > Oh the file is renamed.
> > You probably need `tail -F` rather than `tail -f --retry`
>
> Please check the man page.
The man page says:
-f, --follow[={name|descriptor}]
output appended data as the
Mark Stafford wrote:
> I was attempting to write a script something like a world clock to help
> schedule a task in six time zones.
Are you familiar with the GNU date FAQ entry? It contains a lot of
useful information concerning date and practical date input formats.
Note that I am not the maintainer but simply another user.
Gerald Turner wrote:
> I have a Linux router running jessie that has four ethernet ports and a
> pair of ath9k radios.
>
> Three of the ethernet interfaces (eth0, eth1, eth2) are statically
> configured LAN ports. The fourth ethernet
Package: e2fsprogs
Version: 1.43.1-1
Severity: normal
The 'tune2fs -l' command modifies the file system. The man page says:
-l List the contents of the filesystem superblock, including the
current values of the parameters that can be set via this program.
To recreate the problem:
#
Carsten Hey wrote:
> reopen 824346
But you forgot to terminate the command with 'thanks' or 'stop' and
therefore the entire rest of your message went to the control robot
generating many parse errors.
https://www.debian.org/Bugs/server-control
> Looks like this bug even influenced you, i.e.,
Package: mutt
Version: 1.6.0-1
Severity: normal
The recent version 1.6.0-1 ignores both ~/.mailcap and /etc/mailcap
files. At least for text/html entries.
cat >> ~/.mailcap <.
To report a bug, please visit http://bugs.mutt.org/.
misc/am-maintainer-mode.patch
features/ifdef.patch
Steven Sumichrast wrote:
> It's been about a year since I last checked on this.
I am not one of the package maintainers. I am just another user.
However I wanted to comment.
> I'm really not sure what the method to proceed here is -- am I going
> to have to custom build my own package for
Florian Lohoff wrote:
> After diving into the problem the cause was that actually not the
> shipped sa-update was called but a locally (and broken) version
> in /usr/local/sbin/
>
> The postinst should take care of not calling binarys with relative
> path or relying on the PATH variable:
No.
reassign 820212 net-tools
found 820212 1.60+git20150829.73cef8a-2
retitle 820212 ifconfig output format change breaks downstream programs
thanks
Hi Justin,
Justin McZeal wrote:
> Starting from the beginning, ...
:-)
> there is this firewall agent we have
Reading your latest I think I
Justin McZeal wrote:
> and /sbin/ip -o link show eth0:1: to both come up without a
> hitch. The ones without the colon have been tested to fully work on
> a stock Debian 8 (jessie) image, not Debian 9 (stretch).
I cannot reproduce this on stock Jessie 8.4. It needs "eth0" not
"eth0:1". Note
Michael Stone wrote:
> Bob Proulx wrote:
> > The "locale independent format" looks to be the problem in the above
> > to me. But I think that is only your command line test as that is
> > different from what I see in the tzdata postinst.
>
> This is wher
Ben Hutchings wrote:
> $ readlink /etc/localtime
> /usr/share/zoneinfo/Europe/London
I assume that your locale is set to en_GB.UTF-8? Could you provide
the output of locale so that we could see the other settings? I am
interested in LC_TIME and LC_ALL particularly.
locale
> $ date -d 00:59
severity 761676 wishlist
thanks
Zdenek Kabelac wrote:
> Bob Proulx wrote:
> > Since the latest update the "lvs" command now emits output lines that
> > are so long that they wrap on standard sized terminals.
>
> see the 'lvm.conf'report { compact_output = 1
So far I have been unable to recreate this problem. I tried various
combinations today trying to set up a similar environment to the one
reported. Always for me the host field in the sudoers file requires
the short host name.
I think this is going to require someone who is experiencing the
r.ductor wrote:
> Apparently the hostname parameter is now checked against the
> qualified hostmane. If true, please correct or document it.
There was an additional report of this from Johannes Rohr in
Bug#816915 that turned out to be the same issue. Now merged with this
report.
On my system I
Johannes Rohr wrote:
> Thank you,
> obviously the sudoers on Debian now needs to contain the full hostname
> including the domain. It used to be different in the past, and it is
> different on other distributions.
>
> This is not mentioned in README.Debian and NEWS.Debian
But it doesn't need to
> Pádraig Brady wrote:
> > mv no longer supports moving a file to a hardlink, instead issuing an
> > error.
> > The implementation was susceptible to races in the presence of multiple mv
> > instances, which could result in both hardlinks being deleted. Also on
> > case
> > insensitive
Johannes Rohr wrote:
> Current versions of sudo fail to honour the NOPASSWD directive set for a
> user/host/command set in /etc/sudoers:
>
> sudo -n apt-get update
> sudo: a password is required
>
> /etc/sudoers says:
>
> xxx =NOPASSWD:/usr/bin/apt-get
I am not the maintainer but just
Package: postfix
Version: 3.0.4-5
Severity: normal
With the recent 3.0 Postfix now complains with "backwards-compatible
default settings" warnings about the package default settings in the
master.cf file. Specifically the chroot default has changed from yes
to no. This causes a new warning to
Frederik Himpe wrote:
> When upgrading my system from Squeeze to Jessie using apt-get dist-upgrade,
>...
Upgrades are supported from one major release to the next major
release. The next dist-upgrade from Debian 6 "Squeeze" is to Debian 7
"Wheezy". This file ownership transition is handled in
Bernhard wrote:
> Do you see any chance to prevent the autoremoval?
> I see you have a patch because of bug #808216.
> For me, this package works fine, because i don't use the diff-files.
I don't think 'grave' "renders package unusable" is correct for this
since it seems to only affect those
severity 809789 normal
tag 809789 + moreinfo
thanks
Brendan Reilly wrote:
> Dear Maintainer,
I am not the gawk maintainer but in this just another awk user.
However I recognize this as being a misunderstanding of %G.
> %G returns the date as 2015It is 2016
%G does not return the current
Michael Biebl wrote:
> schrieb Bob Proulx:
> > If a client system requires an NFS mounted file system then the admin
> > must configure the network to be "auto" and not "allow-hotplug".
> > The simple reason is that because otherwise it won't work. :-)
&
Martin Pitt wrote:
> Michael Biebl wrote:
> > I still think though, that we should consider allow-hotplug interfaces
> > when dealing with network-online.target.
> >
> > The reason is, that the debian installer uses allow-hotplug by default.
>
> Argh, this is indeed a tremendously bad default.
>* Drop event plugin directory move. This moves the plugins back into
> the main library path. (closes: #807279)
I have confirmed that the "Monitoring v1/snapshot0 failed." is now
gone with this update. Yay!
Thank you for maintaining lvm in Debian! :-)
Bob
Michael Gilbert wrote:
> control: tag -1 moreinfo
>...
> That said, I don't see the problem with my setup (xfce for what it's
> worth), so maybe there is something about the environment that can
> avoid the issue. If so, I would prefer users configure that, rather
> than applying a patch.
I see
Package: lvm2
Version: 2.02.133-1
Severity: normal
Snapshot creation reports a failure using Sid but not Jessie 8 Stable.
# lvs | sed 's/ *$//' | grep -e LV -e root
LVVG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync
Convert
root v1 -wi-ao 16.00g
Package: ntp
Version: 1:4.2.8p4+dfsg-3
Severity: minor
In the recent release the default Debian config file scheme has
changed from "server" to "pool". That's great! But the included
Debian man pages do not document the pool configuration option.
man ntp.conf
Upstream documentation
severity 802636 normal
tag 802636 + moreinfo
thanks
Imam Kurniawan wrote:
> First, I do apologize if I have put this into the wrong category of bug
> report.
> Because I have to submit the package name, which is sync command is from the
> coreutils package.
> But it definitely related with
1 - 100 of 710 matches
Mail list logo
