Hi,
I can confirm this bug report.
Here is the build log:
DKMS make.log for broadcom-sta-6.30.223.271 for kernel 6.12.5-amd64 (x86_64)
Вс 22 дек 2024 20:53:58 +05
CFG80211 API is prefered for this kernel version
Makefile:91: Neither CFG80211 nor Wireless Extension is enabled in kernel
KBUILD_NOP
Control: severity -1 important
Hi,
It should be fixed with 9.2.8+dfsg-1, but I'm not closing the bug to
monitor the situation. I'm reducing the severity to important.
Best,
Lev
Control: tags 1077351 = moreinfo unreproducible
Hi,
I tried to reproduce this locally in clean sbuild (unstable) environment
with no luck. Let's see what Debian CI will show.
Regards,
Lev
Hi,
Вс 14 янв 2024 @ 04:34 gregor herrmann :
> On Sat, 13 Jan 2024 22:04:20 +, Jeremy Sowden wrote:
>
>> > This package fails its autopkgtest checks with Perl 5.38
>> > (currently in unstable.)
>
>> I've pushed a fix to Salsa:
>>
>> https://salsa.debian.org/emacsen-team/dh-make-elpa/-/comm
Hi,
Hmmm... strange. I cannot reproduce this. I tried to
(1) run tests locally with dh_elpa_test,
(2) run tests locally as autopkgtest supposed to with dh_elpa_test
--autopkgtest,
(3) run tests during build from scratch under sbuild,
(4) run tests with autopkgtest under sbuild.
Tests were su
Control: retitle -1 unable to set up jediepcserver, permission denied
Hi,
I've uploaded 0.2.8+git20220410.81c5a42-1, which contains all upstream
changes. Now emacs-jedi is compatible with jedi in Debian (the API was
updated to jedi 0.18).
Unfortunately, there's another problem, now due to permis
aren't broken by partial upgrades.
>
> logol should then be rebuilt to pick up a dependency on libswipl9.
Thanks for reporting!
I've tagged this bug report with 'help'. I'm a bit overwhelmed at the
moment and don't think I will have time for it or any other Debian stuff
in the coming weeks. NMU is most welcome.
Regards,
Lev Lamberov
Hi Paul,
Чт 15 дек 2022 @ 21:10 Paul Gevers :
> On 14-12-2022 10:15, Debian Bug Tracking System wrote:
>> * rebuild against new swi-prolog (Closes: #1026056)
>
> I can't but feel a bit uneasy by this "solution". Apparently it's not
> properly tracked by dependencies, so it doesn't show up on
Hi Paul,
Вс 23 окт 2022 @ 10:10 Paul Gevers :
> Hi Lev,
>
> On 23-10-2022 09:40, Lev Lamberov wrote:
>> I'm not sure it is the solution, it needs testing. The change in
>> swi-prolog concerns pre-compiled prolog source code, when there is no
>> pre-complied prolog
Вс 23 окт 2022 @ 09:16 Paul Gevers :
> Hi Lev,
>
> On 23-10-2022 09:08, Lev Lamberov wrote:
>> Сб 22 окт 2022 @ 21:27 Paul Gevers :
>>> With a recent upload of swi-prolog the autopkgtest of logol fails in
>>> testing when that autopkgtest is run with the binar
Hi,
Сб 22 окт 2022 @ 21:27 Paul Gevers :
> With a recent upload of swi-prolog the autopkgtest of logol fails in
> testing when that autopkgtest is run with the binary packages of
> swi-prolog from unstable. It passes when run with only packages from
> testing. In tabular form:
I've tried to b
This bug is fixed in the upstream repository, but the fix requires a.el,
which is in NEW at the moment. I'll upload fix for pcre2el when a-el
gets accepted.
Regards,
Lev
Ср 28 сен 2022 @ 18:59 Jonas Smedegaard :
> Quoting Lev Lamberov (2022-09-28 09:35:00)
>> Since now SWI-Prolog in Debian supports setting an arch-independent path
>> to the interpreter (8.4.3+dfsg-1, uploaded on 2022-09-18, in testing
>> since 2022-09-21), I'm reassign
t the mentioned new swi-prolog version using
something like this command:
swipl -o myexe --emulator=/usr/bin/swipl -c mycode.pl
Cheers!
Lev
Вс 18 сен 2022 @ 23:23 Lev Lamberov :
> Hi Jonas,
>
> Вт 06 сен 2022 @ 16:10 Jonas Smedegaard :
>
>> Quoting Lev Lamberov (2022-09-06
Hi Jonas,
Вт 06 сен 2022 @ 16:10 Jonas Smedegaard :
> Quoting Lev Lamberov (2022-09-06 14:00:55)
>> Hi Jonas,
>>
>> Сб 03 сен 2022 @ 21:19 Jonas Smedegaard :
>>
>> >> The autopkgtest caught that the package is not functional on !amd64:
>> >
Hi Jonas,
Сб 03 сен 2022 @ 21:19 Jonas Smedegaard :
>> The autopkgtest caught that the package is not functional on !amd64:
>>
>> (buster_arm64-dchroot)bunk@amdahl:/tmp$ eye.pvm
>> /usr/bin/eye.pvm: 3: exec: /usr/lib/swi-prolog/bin/x86_64-linux/swipl: not
>> found
>> (buster_arm64-dchroot)bunk
And here is Emacs debug output:
Debugger entered--Lisp error: (error "Invalid version syntax: ‘N/A’ (must start
with a n...")
signal(error ("Invalid version syntax: ‘N/A’ (must start with a n..."))
error("Invalid version syntax: `%s' (must start with a nu..." "N/A")
version-to-list("N/A")
Package: elpa-org
Version: 9.5.2+dfsh-1
Severity: grave
X-Debbugs-Cc: none, Lev Lamberov
Dear Maintainer,
While updating elpa-org (9.4.0+dfsg-1 -> 9.5.2+dfsh-1, in testing) I
faced a problem with post-installation, which is still there even in
case of completely removing elpa-org and t
Hi Antoine,
Вт 27 апр 2021 @ 13:53 Antoine Beaupre :
> Package: elpa-esup
> Version: 0.7.1-3
> Severity: grave
> Tags: upstream
>
> This package is unusable in Debian 11 bullseye in its current
> state. In my Emacs 1:27.1+1-3.1 session, i run M-x esup and I get:
>
> error in process sentinel: Wro
By the way here is the relevant output from *Message* on my machine:
```
Starting esup...
esup process started on port 45217
at 1
esup finished
```
Cheers!
Lev
Hi Kurt,
Вс 25 окт 2020 @ 13:30 Kurt Roeckx :
> Package: swi-prolog
> Version: 8.2.1+dfsg-2
> Severity: serious
>
> Hi,
>
> swi-prolog fails to build using OpenSSL 1.1.1h. See
> https://ci.debian.net/data/autopkgtest/testing/amd64/s/swi-prolog/7715788/log.gz
> for a log.
>
> I've filed an upstrea
Hi Roger,
Чт 24 сен 2020 @ 01:43 Roger Shimizu :
> Dear Lev,
>
> Thanks for your report!
>
> On Wed, Sep 23, 2020 at 4:00 PM Lev Lamberov wrote:
>>
>> Package: torbrowser-launcher
>> Version: 0.3.2-13
>> Severity: grave
>> Tags: upstream
>>
I've tested the patch proposed in upstream merge request and it solves
the problem.
Cheers!
Lev
Package: torbrowser-launcher
Version: 0.3.2-13
Severity: grave
Tags: upstream
Justification: renders package unusable
Dear Maintainer,
because of faulty version number check, torbrowser-launcher cannot
correctly handle TorBrowser 10.0 release. Now it shows the following
error message:
The versio
Сб 05 сен 2020 @ 16:17 Sean Whitton :
> Hello Lev,
>
> Thanks for the report and testing. New version uploaded.
>
> --
> Sean Whitton
Thanks for communication with upstream and upload, Sean.
Hi Stefan,
Сб 29 авг 2020 @ 07:52 Stefan Kangas :
> Stefan Kangas writes:
>
>> I have bumped the version of seq.el to 2.22 on the Emacs master branch.
>>
>> IIUC, the new version will be automatically picked up by the GNU ELPA
>> scripts and available for installation within 24-48 hours.
>
> It
Package: elpa-flycheck
Severity: critical
X-Debbugs-Cc: none, Lev Lamberov
User: debian-emac...@lists.debian.org
Usertags: emacs27
Dear Maintainer,
elpa-flycheck causes leak in GNU Emacs 27.1 from the Debian archive
(1:27.1+1-1, currently from experimental).
Excerpt from debug log:
Debugger
gt; https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
these changes are in git already. So, pending...
Cheers!
Lev Lamberov
Hi,
Сб 09 мая 2020 @ 20:59 Paul Gevers :
> Source: swi-prolog
> Version: 8.1.29+dfsg-2
> Severity: serious
> Tags: sid bullseye
> X-Debbugs-CC: debian...@lists.debian.org
> User: debian...@lists.debian.org
> Usertags: flaky
>
> Dear maintainer(s),
>
> You package has an autopkgtest, great. Howeve
Hi,
Since elfeed 3.3.0-2 elfeed-web is shipped in contrib, not main, so I
downgrade this bug report to normal. In future, when all elfeed-web
dependencies will be available in main, this bug may be closed.
Regards,
Lev
Чт 30 апр 2020 @ 14:56 Jan Wielemaker :
> On 4/30/20 2:50 PM, Jonas Smedegaard wrote:
>> Quoting Lev Lamberov (2020-04-30 14:40:53)
>>> Чт 30 апр 2020 @ 14:06 Jan Wielemaker :
>>>
>>>> On 4/30/20 1:41 PM, Jonas Smedegaard wrote:
>>>>> I thi
Чт 30 апр 2020 @ 14:06 Jan Wielemaker :
> On 4/30/20 1:41 PM, Jonas Smedegaard wrote:
>> I think we can use the format almost as-is - just replacing the leading
>> "swipl-" with "swi-prolog-abi-".
>
> I think adding "abi" makes sense. I can replace "swipl" with the
> package name, which is "swi-
Чт 30 апр 2020 @ 12:42 Jonas Smedegaard :
> Quoting Jan Wielemaker (2020-04-30 11:40:32)
>> On 4/28/20 5:26 PM, Jonas Smedegaard wrote:
>> > Quoting Jan Wielemaker (2020-04-28 16:56:30)
>>
>> >> That is worth a try. I guess that implies that generating
>> >> SWI-Prolog (as package) also generat
Hi,
Чт 30 апр 2020 @ 11:40 Jan Wielemaker :
> Hi Jonas,
>
> On 4/28/20 5:26 PM, Jonas Smedegaard wrote:
>> Quoting Jan Wielemaker (2020-04-28 16:56:30)
>
>>> That is worth a try. I guess that implies that generating SWI-Prolog
>>> (as package) also generates this hash. What kind of support woul
Hi Jan,
Вт 28 апр 2020 @ 16:56 Jan Wielemaker :
>> Debian packaging of Asterisk and uWSGI uses such ABI hash towards third
>> party plugins, to alow them to be rebuilt as infrequently as possible.
>> See e.g. https://packages.debian.org/buster/uwsgi-plugin-php and
>> https://packages.debian.org/b
Вт 28 апр 2020 @ 16:30 Lev Lamberov :
> Вт 28 апр 2020 @ 13:11 Jan Wielemaker :
>
>> Hi Lev,
>>
>> I most wanted to get Jos in the loop as the developer of eye. Packagers
>> working together with developers/maintainers saves a lot of work :)
>
> Awww... so,
1 Debian bug
report concerning swi-prolog and eye. You can find it there:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958561
> On 4/28/20 12:49 PM, Lev Lamberov wrote:
>> Hi Jan,
>>
>> Вт 28 апр 2020 @ 11:22 Jan Wielemaker :
>>
>>> Hi Lev, Jos,
>>&g
Hi Jan,
Вт 28 апр 2020 @ 11:22 Jan Wielemaker :
> Hi Lev, Jos,
>
> For Jos, the problem is that eye installs as a SWI-Prolog saved state,
> which is highly version dependent and this is difficult to deal with
> given the Debian dependency and upgrade policy (Lev, hope this is the
> right summary,
Hi,
I've got the following response from swi-prolog upstream about the issue:
Вс 26 апр 2020 @ 09:30 Jan Wielemaker :
> Need to think a bit about the ABI issue. Basically, saved states are
> incompatible between versions, although you can have some luck on
> closely related versions. There are t
Чт 23 апр 2020 @ 14:15 Jonas Smedegaard :
>> Ohhh, I see. Let me upload (source-only) 8.1.29 to unstable. Will be OK
>> for you?
>
> If I understand the situation correctly, then this is a bug in how eye
> is packaged: A prolog image is dumped during build and shipped as the
> executable for eye
Чт 23 апр 2020 @ 13:05 Jonas Smedegaard :
> Quoting Jonas Smedegaard (2020-04-23 12:56:23)
>> Quoting Lev Lamberov (2020-04-23 12:15:12)
>> > Чт 23 апр 2020 @ 11:58 Jonas Smedegaard :
>> >
>> > > Quoting Lev Lamberov (2020-04-23 11:38:36)
>>
Чт 23 апр 2020 @ 11:58 Jonas Smedegaard :
> Quoting Lev Lamberov (2020-04-23 11:38:36)
>> Чт 23 апр 2020 @ 10:59 Paul Gevers :
>> > [Release team member hat on]
>> >
>> > On 21-04-2020 23:48, Debian FTP Masters wrote:
>> >>
Hi,
Чт 23 апр 2020 @ 10:59 Paul Gevers :
> [Release team member hat on]
>
> On 21-04-2020 23:48, Debian FTP Masters wrote:
>> eye (20.0411.2226~ds-1) unstable; urgency=medium
>> .
>>[ upstream ]
>>* new release(s)
>> + FIXED: process_create/3: stderr was sent to stdout.
>>c
Вс 05 апр 2020 @ 13:40 Antoine Beaupre :
> magit-todos, as packaged in Debian, does not work. It seems to assume
> a magit version that is not present in Debian. When I run "M-x
> magit-todos" I get the error:
>
>magit-todos-list-internal: Symbol’s function definition is void:
> magit-setup-b
Hi Antoine,
Вс 05 апр 2020 @ 13:40 Antoine Beaupre :
> Package: elpa-magit-todos
> Version: 1.5.2-1
> Severity: grave
>
> magit-todos, as packaged in Debian, does not work. It seems to assume
> a magit version that is not present in Debian. When I run "M-x
> magit-todos" I get the error:
>
>m
Package: swi-prolog
Version: 8.1.26+dfsg-2
Severity: serious
Dear Maintainer,
current development version of swi-prolog fails to build from source
[log]:
[ 84%] Building C object
packages/xpce/CMakeFiles/plugin_pl2xpce.dir/swipl/pcecall.c.o
cd /<>/build/packages/xpce && /usr/bin/cc -Dplugin_pl2
Looks like, the bug is caused by openssl. Tests run fine with openssl
1.1.1d, but fail with openssl 1.1.1e (currently in unstable). Moreover,
looks like openssl 1.1.1e causes lots of regressions in other packages
[regressions].
[regressions] https://qa.debian.org/excuses.php?package=openssl
The problem is caused by ssl test. Disabling it makes build successful.
Unfortunately, I was not able to find Debian CI logs (typical URLs and
search for swi-prolog at [CI] give 404) for swi-prolog to figure out
which change led to the bug.
[CI] https://ci.debian.net/
Hmmm, looks like the bug is caused by undo-tree, since when
elpa-undo-tree 0.6.4-3 is installed tests are passed correctly.
Moreover, when new upstream version of undo-tree is used (0.7.4, not
currently in Debian) tests also are passed correctly.
Tags: help
Hi,
Вс 23 фев 2020 @ 13:56 Lucas Nussbaum :
> Source: emacs-bind-map
> Version: 1.1.1-4
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200222 ftbfs-bullseye
> During a rebuild of all packages in sid, your package failed to build
> o
?
Ouch, sorry for misleading comment. Version 6.3.26-3 worked properly and
it still works properly now (I've downgrade to it). I thought that
6.4.0~beta4-1 was in testing, but it was only in experimental.
Regards,
Lev Lamberov
Wed Feb 6 11:20:43 2019
fetchmail Wed Feb 6 11:41:49 2019
Changes in libc6 reflect my attempts to upgrade to glibc 2.28-6 and
changes in fetchmail reflect my attempts to downgrade (which I mentioned
before).
With regards,
Lev Lamberov
Hi Matthias,
this bug is closed now, but I'd still like to clarify a bit on the
topic.
First of all, 8.0.0 release of SWI-Prolog is a new stable release. It
will receive only security updates. Previous stable release, 7.6.4 (the
last revision of stable branch 7.6.0), was released in Jan 2018. It
I've ran tests against the source code from upstream's repository and
got even more failures:
Ran 532 tests, 523 results as expected, 7 unexpected, 2 skipped (2019-01-06
01:42:08+0500)
122 expected failures
7 unexpected results:
FAILED haskell-cabal-compute-checksum-1
FAILED haskell-caba
Чт 01 ноя 2018 @ 14:51 David Bremner :
> - add versioned depends on elpa-f to force it to upgrade to buster first
Hmmm, by the way... Maybe it's a good idea to always add versioned
depends (like >=) on other elpa-packages automatically by dh_elpa? Like
if during a given build there is, say 1.0-1
Sorry, for delay with my answer.
> I'm not sure I see the whole picture yet, but I guess that
>
> 1) elpa-f in stretch depends on s-el (instead of elpa-s)
> 2) elpa-vimish-fold in buster is a new style dh_elpa using package
> that only looks at elpa packages for depends.
>
> Maybe
Hi Benjamin,
Пт 27 апр 2018 @ 17:06 Benjamin Lorenz :
> It seems a fix for this bug was merged into the upstream stable
> repository some time ago:
> https://github.com/SWI-Prolog/swipl/commit/3923765d56e5
>
> I have an unstable i386 VM where I could reproduce these memory errors
> and adding thi
Hi Benjamin,
Ср 04 апр 2018 @ 12:31 Benjamin Lorenz :
> The configure script of the swi-prolog jpl package only checks whether
> lib/$arch/server or jre/lib/$arch/server exists but the $arch
> subdirectory was removed in openjdk9. Because of the failed check the
> LDFLAGS are missing the correct
Dear Jan,
building of SWI-Prolog with openjdk-9 fails with the error below. I
haven't yet looked into it, just want to let you know. I'll try to find
some time for it in the next few days.
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/swi-prolog.html
https://tests.reproducib
their Ubuntu's PPAs.
Regards,
Lev Lamberov
in
the Debian package. Which is a grave, so to speak.
With regards,
Lev Lamberov
[0] https://github.com/auto-complete/auto-complete/
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829589
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695278
[3] https://bugs.debian.org/c
Hi James,
Пт 17 ноя 2017 @ 17:15 James Cowgill :
> IMO the best solution is to remove all the ATOMIC_GENERATION_HACK code
> and use libatomic, but this will take some porting work because
> swi-prolog uses the old __sync primitives everywhere.
>
> I have attached a hack which marks _generation and
Hi Adrian,
Ср 15 ноя 2017 @ 08:06 Adrian Bunk :
> On Wed, Nov 15, 2017 at 12:55:12AM +0500, Lev Lamberov wrote:
>>...
>> The most strange thing is that 7.6.1-1 built successfully on mips. The
>> only difference between 7.6.1-1 and 7.6.1-2 is that java tests (only
>> t
Package: swi-prolog
Version: 7.4.2+dfsg-2
Severity: serious
Justification: fails to build from source
The mips build of swi-prolog failed:
Running scripts from core ...
E: Build killed with signal TERM after 360 minutes of inactivity
The bug can be reproduced
package, which should depend on elpa-helm, and after
some time should be removed from Debian. Alternative approach would be
to remove anything-el, and build transitional dummy package from helm
source package to allow migrations.
Cheers!
Lev Lamberov
[0] https://www.emacswiki.org/emacs/Anyt
Hi Sébastien,
11.02.2017 14:22, Sébastien Villemot пишет:
> If swi-prolog is removed from stretch, then several reverse
> dependencies will also go away (in particular sagemath and ppl
> maintained by the Debian Science Team, which is what prompted me to fix
> #852892).
>
> So I think you should
h of swi-prolog will be ready and I'll upload it to backports.
But if there are anyone who _really_ need swi-prolog in stretch, I'm
open to your suggestions and can manage with the first option. (In
this case, please, do not expect good level of support of swi-prolog
in stretch.)
Cheers,
Hi Sébastien,
05.02.2017 22:11, Lev Lamberov пишет:
> 05.02.2017 22:02, Sébastien Villemot пишет:
>> Hi Lev,
>>
>> Le dimanche 05 février 2017 à 20:03 +0500, Lev Lamberov a écrit :
>>
>>> 05.02.2017 18:37, Sébastien Villemot пишет:
>>>> O
05.02.2017 22:02, Sébastien Villemot пишет:
> Hi Lev,
>
> Le dimanche 05 février 2017 à 20:03 +0500, Lev Lamberov a écrit :
>
>> 05.02.2017 18:37, Sébastien Villemot пишет:
>>> On Sat, 28 Jan 2017 09:27:37 +0100 Lucas Nussbaum >>>
>>>
>>> wro
attached.
>
> Don’t hesitate to tell me if I should delay it longer (or instead
> shorten the delay).
Thank you very much for your help!
Sébastien, please, shorten the delay. Let the fix enter sid asap. ;-)
Thanks!
Cheers!
Lev Lamberov
signature.asc
Description: OpenPGP digital signature
Hi Hilko,
19.11.2016 22:11, Hilko Bengen пишет:
> Source: swi-prolog
> Version: 7.2.3+dfsg-4
> Severity: serious
> Tags: patch
>
> Dear Maintainer,
>
> after searching for "AC_CHECK_LIB(ssl, SSL_library_init" using
> codesearch.debian.net and rebuilding with OpenSSL 1.1, I found that the
> OpenSS
17.10.2016 02:00, Emilio Pozuelo Monfort пишет:
> make[3]: Leaving directory
> '/«BUILDDIR»/swi-prolog-7.2.3+dfsg/packages/jpl/src/java'
> if [ -r jpltest.jar ]; then \
>
> LD_LIBRARY_PATH="/usr/lib/jvm/java-8-openjdk-armel/jre/lib/arm/server:/usr/lib/jvm/java-8-openjdk-armel/jre/lib/arm"
Hi Emilio,
17.10.2016 02:00, Emilio Pozuelo Monfort пишет:
> Source: swi-prolog
> Version: 7.2.3+dfsg-1
> Severity: serious
>
> Your package failed to build on armel/armhf during a rebuild:
>
> make[3]: Leaving directory
> '/«BUILDDIR»/swi-prolog-7.2.3+dfsg/packages/jpl/src/java'
> if [ -r jplte
And here is the full log after cold start right before suspend, as
reported with journalctl -b.
boot.tar.gz
Description: application/gzip
Package: src:linux
Version: 4.4.6-1
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
running on HP Probook 655 G1 with the latest BIOS in legacy mode (not using
UEFI) I experience the following problem. If I close lid, the system correctly
suspends (seems like so, becaus
gcc -shared -rdynamic -Wl,-z,relro -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -pthread -L/«PKGBUILDDIR»/src/../lib/amd64
-L'/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/server'
-L'/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64' -o libjpl.so src/
uring Waiting for /dev to be fully populated
stage.
With 3.12.9-1 linux kernel everything works OK.
Cheers!
Lev Lamberov
-- Package-specific info:
** Version:
Linux version 3.13-1-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.2
(Debian 4.8.2-14) ) #1 SMP Debian 3.13.4-1 (2014-
2013/6/7 Holger Levsen
> control: tags -1 + moreinfo
> thanks
>
> Hi,
>
> you wrote "[wicd-curses] was working before some update, now it doesn't
> work."
> - just to confirm: it worked under wheezy still, but some update in the
> last
> days broke it. Right?
>
Right, some update in the last day
work. Fortunately,
wicd-cli and wicd by itself work properly.
I expect it to start and do its work.
Cheers!
Lev Lamberov
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1,
&
79 matches
Mail list logo
