severity 768093 important
thanks
On second thought I don't consider this RC:
* It doesn't seem to actually result in very significant data loss.
* Pointing --git-dir at something not a git repo is asking for undefined
behavior. This is a little more undefined than could be desired,
but the
Package: wnpp
Severity: normal
I have orphaned the github-backup package.
I will continue to develop the software upstream.
--
see shy jo
signature.asc
Description: Digital signature
Gergely Nagy wrote:
Control: retitle -1 ITA: propellor -- property-based host configuration
management in haskell
I intend to adopt propellor. I'm starting to use it at work, and at home
too, would be a shame to let it fall out of Debian. It's also a great
excuse to learn more about
it to eventually
something like dpkg --archive or similar.
Actually, with the changelog message not being explicit about this:
,---
dpkg-repack (1.39) unstable; urgency=medium
* Orphaned dpkg-repack.
-- Joey Hess jo...@debian.org Fri, 07 Nov 2014 17:17:56 -0400
`---
and the package
Package: wnpp
Severity: normal
I intend to orphan the propellor package.
The package description is:
Propellor enures that the system it's run in satisfies a list of
properties, taking action as necessary when a property is not yet met.
.
It is configured using haskell.
I continue as
Package: wnpp
Severity: normal
I have orphaned etckeeper. I will be continuing development upstream.
--
see shy jo
signature.asc
Description: Digital signature
Package: wnpp
Severity: normal
I intend to orphan the mpdtoys package. I will continue maintaining it
upstream.
The package description is:
This is a collection of small toys and tools for doing various things
to MPD (Music Player Daemon) from the command line. Some of them are
very useful,
Package: wnpp
Severity: normal
I'm orphaning liblingua-en-words2nums-perl. I guess I'll still be
maintaining it upstream, although I've not needed to touch it in half a
decade.
--
see shy jo
signature.asc
Description: Digital signature
Package: wnpp
Severity: normal
I've orphaned jetring.
I'm also the upstream author, and I don't anticipate doing any upstream
maintenance.
It may be best to let this package fall out of Debian.
Although IIRC someone is using it for something or other.
--
see shy jo
signature.asc
Package: wnpp
Severity: normal
I've orphaned pdmenu.
I will continue to maintain it upstream, although it's in super
deep maintenance mode.
--
see shy jo
signature.asc
Description: Digital signature
Package: wnpp
Severity: normal
I've orphaned ticker.
I still maintain it as upstream, although I don't know that it has
any users and I haven't needed to touch it in 7 years.
It would be fine to remove this package from Debian.
--
see shy jo
signature.asc
Description: Digital signature
Package: wnpp
Severity: normal
I've orphaned moreutils.
I will still be developing it as upstream.
--
see shy jo
signature.asc
Description: Digital signature
Package: wnpp
Severity: normal
I've orphaned filters.
I will still be developing it as upstream.
--
see shy jo
signature.asc
Description: Digital signature
Package: wnpp
Severity: normal
Needs new maintainer (debian upstream).
--
see shy jo
signature.asc
Description: Digital signature
Package: git-annex
Version: 5.20141024
Severity: serious
http://git-annex.branchable.com/bugs/misuse_of_--git-dir_might_destroy_a_git_repository_completely/
--
see shy jo
signature.asc
Description: Digital signature
I can confirm that, on a clear theme (like Adwaita), when disabling the
compositor, the nm (and blueman) applet background is black.
Since nothing changed in xfce4-panel I still think that's a fallout of
the gtk 3.14 update, but I have no idea how to fix that…
This seems to have been fixed
Martin-Éric Racine wrote:
The manual states that --generate can be used to create the directory
structure for further manipulation.
However, the command line sample given to get around building a *.deb will
result in a hidden file called ..deb which is less than optimal. Here's a
better
There is no reason for fstrim to be run by a systemd timer in Debian.
We have cron.weekly. So, fixing #732054 will fix this bug too.
--
see shy jo
signature.asc
Description: Digital signature
If the systemd stuff does continue to be shipped, the postinst script
should not be starting fstrim.service at all. The timer will take care
of that at an appropriate time.
--
see shy jo
signature.asc
Description: Digital signature
Package: systemd
Version: 215-5+b1
Severity: minor
systemctl(1) mentions --failed in passing, but forgot to include
it in the list of options. This makes systemctl --failed, which seems
a very useful command, hard to find.
--
see shy jo, filling in on jidanni's sick day
signature.asc
Based on the fstrim.timer and fstrim.service now shipped by util-linux,
all that's needed is a cron.weekly script that runs fstrim -a.
(I suppose that there would be no real reason to include the timer if
there was a cron.weekly script; fstrim shouldn't be run by two different
things..)
--
see
Package: systemd-cron
Version: 1.3.1+ds1-2
Severity: normal
I had @reboot jobs existing, that had already run when my laptop booted.
I then installed systemd-cron, and noticed this caused the jobs to run
again.
● cron-joey-1.service - [Cron] @reboot mpd; mpdscribble
Loaded: loaded
+This tool currently only work if you are root, because python scripts can't be
setgid.
+.TP
+As a workaround, you can have root create first a blank crontab for you:
+.br
+sudo touch @statedir@/$USER
+.br
+sudo chown $USER @statedir@/$USER
These instructions are incomplete, because
Package: docker.io
Version: 1.3.0~dfsg1-1
Severity: normal
root@darkstar:/var/lib/docker/initls -l
total 23212
-rwx-- 1 root root 9178470 Jul 2 14:59 dockerinit-1.0.0*
-rwx-- 1 root root 7338600 Oct 15 14:49 dockerinit-1.2.0*
-rwx-- 1 root root 7246144 Oct 20 15:42 dockerinit-1.3.0*
Maybe --restart=always or --restart=on-error is needed to get the old
behavior? I cannot make much sense of the upstream changelog.
--
see shy jo
signature.asc
Description: Digital signature
Santiago Vila wrote:
Instead, the work of debootstrap is precisely to guess the right order
in which packages should be configured so that everything work.
In other words, essential packages should not get in the business of
breaking dependency cycles, because that's debootstrap job.
This
by --minimal patch.
-- Joey Hess jo...@debian.org Sun, 31 Aug 2014 14:05:56 -0700
-- Package-specific info:
--- /etc/devscripts.conf ---
--- ~/.devscripts ---
DEBCHANGE_RELEASE_HEURISTIC=changelog
DEBCOMMIT_SIGN_TAGS=yes
DEBSIGN_KEYID=2512E3C7
DEBSIGN_SIGNLIKE=gpg
DEBSIGN_MAINT=jo...@debian.org
Package: dpkg-dev
Version: 1.17.18
Severity: normal
The new dpkg-buildpackage -g option can also be passed to
dpkg-genchanges, but is not documented on its man page. This makes it
hard to figure out that dpkg-buildpackage --changes-option=-g can be
used.
-- System Information:
Debian Release:
Package: gtk-redshift
Version: 1.9.1-4
Severity: normal
Previous versions allowed just clicking on the icon to toggle redshift
on and off. Now I have to click, hold, scroll up several items and
select the Enabled item in the menu.
After trying to live with this for several weeks, I'm still
Package: docker.io
Version: 1.3.0~dfsg1-1
Severity: normal
IIRC, in previous versions of docker, if a container was running when
the system got rebooted, docker started the container back up on boot.
This is no longer happening. Seems a problem if docker is being used
to run servers.
For
Adam Borowski wrote:
* powerpc in qemu
(using an existing system on real metal, d-i on qemu)
What specific real metal did you use to test gnome on powerpc?
--
see shy jo
signature.asc
Description: Digital signature
Package: release.debian.org
Severity: normal
debootstrap needs to contain the name of jessie+1 release, in order to
support debootstrapping that on a jessie system.
In the wheezy release process, we didn't learn the name of jessie until
it was too late to get debootstrap to support it. (#706788)
Most countries have only one timezone, and for those the country-zone
mapping is stored in the tzmap file (automatically generated from
zone.tab), and no question is asked. Some countries have multiple timezones
listed in zone.tab, but these are only of historical interest (ie, to get
the correct
Dude, if you thinkn that posting offtopic stuff to a bug report is the
way to convince people of something, you might want to think again.
--
see shy jo
signature.asc
Description: Digital signature
Adam Borowski wrote:
I have tried Gnome3 on:
* an armhf laptop, Omega OAN133, with:
* framebuffer
* proprietary Mali drivers
* an armhf desktop, hardkernel Odroid U2 (also Mali)
* powerpc in qemu
(using an existing system on real metal, d-i on qemu)
What was the result of all these
Apparently docker 1.2.0 had a service file that didn't tell systemd to
start it, and nor did it set up a link in /etc to make the multi-user
system want it, so it didn't get started.
Seems to be fixed in 1.3.0.
--
see shy jo
signature.asc
Description: Digital signature
Package: docker.io
Version: 1.2.0~dfsg1-2
Severity: normal
root@elephant:/etcdocker.io ps
2014/10/19 03:31:46 Cannot connect to the Docker daemon. Is 'docker -d'
running on this host?
root@elephant:/etcps ax |grep 'docker.io -d'
3172 pts/3S+ 0:00 grep docker.io -d
12111 pts/1S+
I think this is a duplicate of #752867, so I'll merge them.
Also, note that I'm using propellor with docker, and propellor does
some grubbing around in the docker.io output (I guess docker has an API
it should be using instead.) It seems not unlikely that results in
something like Vincent's
Package: docker.io
Version: 1.2.0~dfsg1-2
Severity: normal
I have docker installed on my laptop, which uses systemd,
and typically has no containers running. I have observed that docker
frequently does not get started at boot. Possibly after an unclean
shutdown, which is typical of a laptop.
●
I thought this might be caused by the broken systemd service symlink
reported in #763519. But it seems not; I removed that broken symlink,
and docker is still not started on boot. Quite reproducible, BTW, at
least on my laptop here.
--
see shy jo
signature.asc
Description: Digital signature
I booted with debug, and checked the journal. Here's all that
was logged about docker on boot:
Oct 19 00:45:16 darkstar systemd-sysv-generator[152]: Ignoring K01docker
symlink in rc1.d, not generating docker.service.
Oct 19 00:45:16 darkstar systemd-sysv-generator[152]: Ignoring S19docker
Mikko Rapeli wrote:
debhelper build status log file is not documented in manual pages.
Common developer use cases involve modifying list of installed files
and package install scripts, and for these use cases a complete re-compile
of the packages in not necessary. Instead developers could
Mikko Rapeli wrote:
I have fought this issue for years. Build a package and then try to fix
some bugs locally. Silly bugs like bad .install or package scripts should be
straight forward to fix without complete rebuild of the package,
which can take hours, or even days on smaller machines. If I
Christoph Anton Mitterer wrote:
For git it's e.g. quite clear that it's use of SHA1 *is* security
relevant.
I've talked about this with the git developers before, and while they
seemed to have some ideas for how to handle a conversion to a different
hash, they're not keen on doing it until
Petter Reinholdtsen wrote:
Here is another draft, this time also providing the module name. I
dropped the code looking in /proc/modules, as three ways to find
firmware seem a bit too much.
Looking at dmesg might fail if something is spamming it and the message
drops out of the ring buffer.
Bill Allombert wrote:
Indeed, but I am concerned that providing data for a small subset of
the archive is a increasing the risk a deanonymization.
Currently unstable+testing is about 15% of the archive but it is
often much less. Furthermore if we publish data for unstable+testing,
then
Bill Allombert wrote:
I am a bit confused by your report. I would expect what you request to be
adequately provided by the popcon.debian.org website and the
popularity-contest version field. We even provide separate data for stable.
But not separate data for unstable+testing.
Also, there
Santiago Vila wrote:
Before systemd arrived, it was possible to have a chroot free from
init packages (not needed to build packages).
It seems reasonable for debootstrap --variant=buildd to omit any init
systems, if it doesn't already.
--
see shy jo
signature.asc
Description: Digital
Package: popularity-contest
Version: 1.61
Severity: normal
I use popcon data a lot for eg, tasksel, and often one is only
interested in data for unstable, or stable. But there's no good way to
separate those in the results. Instead, various workarounds have to be
used, like trying to tease out
Source: haskell-dav
Severity: normal
To allow DAV to be built with latest hackage, you need to copy
some lines from http://hackage.haskell.org/package/network-uri into
its cabal file.
(Does not currently affect debian package.)
--
see shy jo
signature.asc
Description: Digital signature
This bug was fixed back in version 3.2011.
madduck's related .git prefix bug is not fixed yet so I'll close this
bug once it is.
--
see shy jo
signature.asc
Description: Digital signature
Cyril Brulebois wrote:
Ah, yes. I remember having wondered about that when installing jessie
on a new machine. I'm not particularly happy about being able to pull
packages from backports without any kind of manual action.
apt won't install newer versions from backports
unless the user
Johannes Schauer wrote:
If you like that better, then I can also prepare a patch which uses
libdpkg-perl directly instead of copypasting the build profile evaluation
logic from it. Since debhelper already indirectly depends on libdpkg-perl
through dpkg-dev this additional dependency should not
Paul Wise wrote:
+ if ($data) {
This fails if $data = 0, which I don't think is what you want
to check for here. You probably want to check if $data is defined,
or empty.
+ } else {
This and other else bracing is not in the code style used in mr.
--
Thomas Skardal wrote:
If I select all four (Gnome, KDE, XFCE, MATE) desktop environments
during tasksel I'm unable to continue without an error.
Tasks should all be co-installable, so it would be useful to know what
the error message is.
--
see shy jo
signature.asc
Description: Digital
Baptiste Jammet wrote:
Testing debian-jessie-DI-b2-kfreebsd-amd64-netinst.iso under qemu-kvm,
if I only choose Graphical desktop environment, d-i doesn't install any
DE, just something like desktop-base. It seems that I have to choose
explicitly.
(Tested 2 times)
Oct 6 17:03:32 in-target:
Steven Chamberlain wrote:
I noticed there was an option to install GNOME, even though it is
not available for kFreeBSD jessie.
I think tasksel is already supposed to hide uninstallable tasks, and
indeed, meta-gnome-desktop should be uninstallable in testing:
Tasksel hides tasks that are
westlake wrote:
when there's low ram available and dpkg-reconfigure is issued (eg,
dpkg-reconfigure locales), if there are premature exits when building
locales it could lead to a filesystem corruption.
This happened to me more than once where I was using a 128MB ram for kvm,
and there was
Package: electrum
Version: 1.9.8-1
Severity: normal
I have no .electrum directory, and would like to recover a wallet from a
seed. So I start electrum. It displays a Electrum could not find an
existing wallet dialog. I pick an option (which one doesn't matter) and
click Next. It then displays the
Package: docker.io
Version: 1.2.0~dfsg1-1
Severity: normal
I have 2 servers, which have been running docker.io on unstable
without incident for months. Last week I installed systemd on both, and
now the docker service dies after some period of time (hours to
days).
● docker.service - Docker
Aurelien Jarno wrote:
We have scheduled a few thousands of binNMUs on s390x due to the libc
ABI breakage. It occurs that most of the non binNMUs safe packages are
wrongly using this --link-doc option.
I am therefore increasing the severity of this bug. dh_installdocs
--link-doc should
Tianon Gravi wrote:
Ah interesting. Do you happen to know if these symlinks created by
dh_systemd_* or are they created by systemd itself?
I suspect that systemd might have created those links due to an Alias=
setting in the service file, which perhaps got removed.
But I have not verified
Package: docker.io
Version: 1.2.0~dfsg1-1
Severity: normal
joey@darkstar:/etc/systemdfind -name \*docker\* -ls
57690440 lrwxrwxrwx 1 root root 37 Jul 2 14:59
./system/multi-user.target.wants/docker.io.service -
/lib/systemd/system/docker.io.service
I have this broken
Gianfranco Costamagna wrote:
llvm maintainer (Sylvestre) says that llvm-3.4 is going to disappear
(not before jessie, but somewhen after), and llvm-3.5 is built
correctly on arm{el,hf}.
Isn't it better to just upload with llvm-3.5 and do some binNMUs
instead of using the old one and be hit
Ben Armstrong wrote:
Both Mate and Cinnamon feature
the traditional panel and menu design that GNOME 2 did, so share more in
common in design than they do with gnome-shell
But then there's gnome 3 fallback mode.
What perplexes me is why Mate, which is a throwback desktop based on an
aging
Package: xfce4-panel
Version: 4.10.1-1
Severity: normal
The icons for network-manager and redshift both have a black
background, while the panel itself has a grey background.
This first happened a few days ago, and only to network-manager. After
upgrading today, and rebooting, both icons had the
Christian Hudon wrote:
That was a not a problem for me, because in my .mrconfig file, the on()
function is run every time. But good point in general. Anyways, I guess the
initial version of this on() function in this bug report was more of a
Would you potentially be interested in this? thing.
Yves-Alexis Perez wrote:
Can you switch to the Adwaita theme and see if it changes anything?
I /think/ it might be related to the gtk 3.14 upload, which broke
existing themes.
Adwaita does not seem to change the color.
(Restarted nm-applet to make sure.)
--
see shy jo
signature.asc
I noticed that I can get the correct background by running compton.
As soon as compton stops, it's back to the black background.
I don't normally use a compositor.
--
see shy jo
signature.asc
Description: Digital signature
Christian Hudon wrote:
# Check hostname
if [ $shorthostname = $host -o
$fullhostname = $host -o \
$domainname = $host ]; then
None of these variables seem to be defined in your patch.
--
see
Here's some debian/rules hacks to fix this.
This forces use of llvm-3.4 for building ghc, as well as
modifying the wrapper scripts to force use of that version at runtime.
The control file also needs to be changed to depend on llvm-3.4, rather
than llvm.
Note that just uploading ghc with this
Sylvestre Ledru wrote:
Yes, I know :(
However, 3.5 has been released a few weeks before this freeze, 3.4 is
unmaintained,
3.5 will be maintained a bit more, Ubuntu is also doing the switch to
3.5 and I wanted to default Debian
on the last version. And as you found, the workaround is easy,
Christian Hudon wrote:
whoami=$(whoami)
shorthostname=$(hostname -s)
fullhostname=$(hostname -f)
domainname=${fullhostname#*.}
These commands would run every time myrepos is run, even if `on` is not
used.
I think it would probably
You need to upgrade to a current version of git.
I thought I had fixed the dependency, but I didn't.
--
see shy jo
signature.asc
Description: Digital signature
Package: ghc, llvm
Version: 7.6.3-16
Severity: serious
It seems that ./Setup configure segfaults:
(sid_armhf-dchroot)joeyh@harris:/tmp/git-annex-5.20140926$ ./dist/setup/setup
configure
Segmentation fault
Confirmed that installing llvm-3.4 and putting /usr/lib/llvm-3.4/bin
first in PATH before running ghc lets it build working executables on
armel and armhf.
This is certianly a bug in ghc. It should not depend on llvm, but on the
llvm-$ver it was built against, and it should use the toolchain from
This close to the freeze is not time to be introducing new breakage like #763078
--
see shy jo
signature.asc
Description: Digital signature
Klaus Ethgen wrote:
I made this a grave bug as it is security relevant due the current bash
bugs and against the debian policy to use /bin/sh if possible.
The bash bug has been comprehensively fixed now. Bash no longer tries to
parse random environment variables as if they contained shell code.
Didier 'OdyX' Raboud wrote:
Le lundi, 22 septembre 2014 14.31:19, vous avez écrit :
tasksel allows selecting the desktop now, so the selection in
win32-loader is unncessary (the list there is also incomplete).
Thanks for the heads'up, patch in the pipes.
I think that
etckeeper has a cron.daily file, and systemd-cron's description says:
Description-en: systemd units to provide minimal cron daemon functionality
Provides systemd units to run cron jobs in /etc/cron.hourly cron.hourly
cron.monthly cron.weekly and cron.boot directories, without having cron
or
Package: bash
Version: 4.2+dfsg-0.1+deb7u1
Severity: grave
Tags: security
http://seclists.org/oss-sec/2014/q3/679
root@diatom:/tmp/emptybash --version
GNU bash, version 4.2.37(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or
We're starting to have to work around this bug in d-i, by eg making
separate /usr a harder situation to get into when installing Debian.
My calendar says 10 days until freeze start. I sincerely hope someone
does something.
--
see shy jo
signature.asc
Description: Digital signature
Ben Armstrong wrote:
Please turn on display of the Cinnamon desktop task. I have tested
building Jessie live images with Cinnamon included and it seems to
already provide a usable desktop. It would be useful for testers to
be able to see Cinnamon so they can try it and help shake out any
Package: debian-cd
Severity: normal
tools/boot/jessie/common.sh looks for the first desktop task in the
Recommends of task-desktop to get the default. That will still work, but
it would be better if it sourced /usr/lib/tasksel/default_desktop and
passed an architecture name to
place.
--
see shy jo
From 742e335531a1ed27757db3b3ce95bc330e7d51f6 Mon Sep 17 00:00:00 2001
From: Joey Hess j...@kitenet.net
Date: Tue, 23 Sep 2014 14:59:10 -0400
Subject: [PATCH] remove desktop=xfce preseeding
Moved to tasksel 3.27.
---
build/boot/hurd/grub-hurd-cdrom.cfg | 2 +-
build
Steven Chamberlain wrote:
Agreed, although we should try evaluate if XFCE is still the best
default for these (and perhaps find something that caters to other
situations where GNOME isn't viable)
As far as I'm concerned, this decision is up to the porters for an
architecture. If there is more
Steven Chamberlain wrote:
On 16:04, Joey Hess wrote:
There is also the potential for tasksel to look at properties of the
system and fall back to eg, a lighter desktop, or a configuration that
works better on a tablet. My changes to tasksel support such things, but
it would be up
Package: win32-loader
Version: 0.7.5
Severity: normal
tasksel allows selecting the desktop now, so the selection in
win32-loader is unncessary (the list there is also incomplete).
I think that default_desktop=xfce might still be passed for kfreebsd
installs, to override the current default of
2001
From: Joey Hess j...@kitenet.net
Date: Mon, 22 Sep 2014 15:14:47 -0400
Subject: [PATCH] adapt desktop handling for tasksel/d-i changes
tasksel now allows selecting the desktop, and d-i has dropped the boot menu
desktop selection. This patch attempts to update debian-cd for these
changes, removing
Package: docker.io
Version: 1.2.0~dfsg1-1
Severity: normal
Despite there being closed bugs about this in docker's bug tracker
(https://github.com/docker/docker/issues/5663)
it remains a problem to use ssh and cron in docker containers, because
pam_loginuid.so fails to work inside docker in the
Source: make-guile
Severity: normal
make is priority standard for reasonable reasons. But, make-guile seems
to have inherited this priority accidentially, from the Source package
stanza.
(Note that make-guile depends on some things outside of standard, which
would need to be fixed if you for
I get either no audio playback or no audio track in the rendered file.
Input file is a debconf talk video (webm).
The audio works in the monitor in kdenlive.
The render dialog only lets me pick audio rates from 64-384, which
is much lower than I would expect. I assume this is why no audio gets
Paul Wise wrote:
I think the daemon should exit if I
completely remove the directory that it is monitoring.
This would be a nice feature..
I think it would require a separate inotify on the parent directory
containing the repository directory in order to get an event when the
repository is
Paul Wise wrote:
When I clone over SSH from another user's home directory, git-annex
writes the daemon.status outside of the git-annex I am cloning:
pabs@chianamo ~/some/parent/directory $ git clone
server.example.com:~user/other/parent/directory/their-git-annex/ my-git-annex
Cloning into
David Liontooth wrote:
I use sponge in scripts that process a succession of files, and run into this
error occasionally.
It will fail in parallel instances at the same time, so I guess some call is
getting the wrong response. Maybe just try again?
sponge uses temp files in the standard
Martin-Éric Racine wrote:
dh_pysupport is routinely executed by the build target, even when the package
doesn't contain any Python file.
Personally, I find it hard to imagine how that would be a feature, so I'm
reporting this as a bug.
Of course, if there's any rationale for this, I
Harald Dunkel wrote:
Looking at the output of debconf-get-selections and the
preset values shown by dpkg-reconfigure it seems to me
that sometimes they do not match. Example: If I change
the database for mdadm using
echo -e mdadm\tmdadm/mail_to\tstring\tmonitor...@example.com |
martin f krafft wrote:
also sprach Joey Hess jo...@debian.org [2014-09-10 02:44 +0200]:
So saying something like chain=pure is really the same, except it
would handle status/log/diff etc. as well, and implicitly. Maybe
there is also a better way to do it, e.g. chain=true
martin f krafft wrote:
Previously, the CWD was just left at the top-level, right?
Therefore, I assume that the commands all already took precautions
to ensure that they operate on the right subdir, e.g. by setting
GIT_DIR.
No, mr chdirs before running lots of stuff. And doesn't chdir before
Package: alpine
Version: 2.11+dfsg1-3
Severity: normal
A user reported that alpine had suddenly started saying things about
rsh to IMAP server, and prompting for a password but not accepting any
input... Rather than opening her inbox.
Investigation showed that alpine was running:
26465 pts/9
401 - 500 of 6094 matches
Mail list logo
