I've fixed the issue in Debian for Puppetserver with a patch that
refactors a script to regenerate the full suite of test certs [2], but
its a time-consuming process. My plan was to introduce a similar script
to ssl-utils-clojure at some point before the trixie freeze.
-- Jérôme
[0] https://www.pu
Control: tag -1 pending
Hello,
Bug #1091127 in jruby reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/java-team/jruby/-/commit/b312bd35f9d870c3fdf16fd5858e577c3c
ruby-selinux which reached testing.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079254
It's now fixed in sid.
-- Jérôme
ystem?
Thanks.
-- Jérôme
Control: tag -1 pending
Hello,
Bug #1094445 in puppet-agent reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/puppet-team/puppet-agent/-/commit/7398ce12512db72fae
close 1087902 8.7.0-1
thanks
Hello,
This is now fixed with the latest upload.
Thanks!
000)
libdrm.so.2 => /opt/amdgpu/lib/x86_64-linux-gnu/libdrm.so.2
(0x7fb11a107000)
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6
(0x7fb119e0)
[...]
A quick modification in the /etc/ld.so.conf.d directory and the bug is gone.
Sorry for the noise.
--
Jérôme Kieffer
Control: tag -1 pending
Hello,
Bug #1033316 in ruby-moneta reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/ruby-team/ruby-moneta/-/commit/b005584adbcf8036312a67
greSQL
17, if it can be fixed easily, and if I should just skip those tests
temporarily.
-- Jérôme
Control: tag -1 pending
Hello,
Bug #1080122 in powerline reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/python-team/packages/powerline/-/commit/81cf7f5d763ad46
examination of the build
logs demonstrate [1], but now it also errors-out.
Unless someone else wanting to work this chimes in, I'll make an upload
shortly that disables the tests again.
-- Jérôme
[0]
https://salsa.debian.org/python-team/packages/powerline/-/commit/6f7ac0633507bbd6beae
S}
E AttributeError: module 'mistune' has no attribute 'PLUGINS'
Until Lektor ships a markdown controller that supports mistune 3, or
Debian ships a mistune 2 package, I'm afraid it won't be possible to
keep Lektor in testing.
-- Jérôme
Package: puppet-agent
Severity: serious
Version: 8.4.0-1
Control: affects -1 puppetserver
In bug #1078911 [0], a user reported that a cron job responbile for
cleaning up old reports previously shipped in puppet-master was no
longer shipped in puppetserver. The consequence was an accumulation of
Control: tag -1 pending
Hello,
Bug #1077976 in puppetdb reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/puppet-team/puppetdb/-/commit/d7dda9f8a15139072576e753c5
Control: tag -1 pending
Hello,
Bug #1078360 in ruby-moneta reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/ruby-team/ruby-moneta/-/commit/2b1bc05ac08a178fc2c3cb
test ... instead of testing that
the software works.
Obviously, the test is not only checking which JDK version is running.
PuppetDB is simply emitting a warning about that on stderr, and the test
is just missing "Restriction: allow-stderr".
I'll fix that in the next upload.
-- Jérôme
able here: https://people.debian.org/~smcv/bug1070730/
(amd64 + i386 + source)
I can confirm these builds fix the input issues reported here on my system.
Thank you for moving so fast on this,
-- Jérôme
Hi Nilesh,
Le 2024-04-18 à 06 h 24, Nilesh Patra a écrit :
I will NMU this in a week or so if I see no activity. This package has been
going through in-attention for a while.
Please, you may upload the fix whenever you wish, it's fine with me.
-- Jérôme
Control: tag -1 pending
Hello,
Bug #1067209 in jruby reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/java-team/jruby/-/commit/1e0e33a4429ec76990cb8729df7e4b7bde
close 1042314 8.4.0-1
thanks
I believe this bug is now fixed in the latest version of jruby and puppetserver
uploaded to sid.
Thanks,
-- Jérôme
atest puppet-agent
package in Debian
I'm not a maintainer or uploader of this package, so if someone feels
like they're wearing one of those hats, please file a removal request [0].
Thanks,
-- Jérôme
[0] https://wiki.debian.org/ftpmaster_Removals#How_to_request_removal
close 1025078 5.0.3-1
thanks
With now both ruby-faraday and ruby-puppet-forge up to date in sid, this issue
is solved.
1.2.0, is now available in experimental.
It's working for me, but I'm waiting on some feedback before uploading
it to unstable.
Thanks,
-- Jérôme
Control: tags -1 + confirmed
Control: owner -1 !
Hello,
I'm preparing an update for this package which should fix the issue.
Thanks,
-- Jérôme
or do
anything bad, but you can also test it yourself on a copy of your
keyring, the signatures thus produces will be just as valid.
Another thing that would be nice to fix upstream, or in the package at
least.
-- Jérôme
Le 2023-12-09 à 17 h 29, tony mancill a écrit :
On Sat, Dec 09, 2023 at 04:39:35PM -0500, Jérôme Charaoui wrote:
On Mon, 30 Oct 2023 09:37:34 +0100 Andreas Beckmann wrote:
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in '
in
the first place, during the piuparts upgrade. It's not present in
testing, and it has currently zero reverse-dependencies.
I did my own testing and on a bare system with
"libtakari-polyglot-maven-java" installed, upgrading to sid does not
include an installation of "libtakari-polyglot-groovy-java".
Any idea what's going on?
Thanks,
-- Jérôme
close 1052722 2.6.0-1
thanks
Le 2023-11-25 à 06 h 30, Miguel Landaeta a écrit :
On Sat, Nov 25, 2023 at 12:29 AM Jérôme Charaoui wrote:
[...]
I've been working on a 9.4 release, you can see the progress here:
https://salsa.debian.org/lavamind/jruby
I plan to upload this version to experimental within a few da
Hi Miguel,
Le 2023-11-24 à 18 h 38, Miguel Landaeta a écrit :
Thomas and Jérôme,
Do you have any concerns with me uploading a fix for this issue?
I'm working with some folks here in Cambridge MiniDebConf and I
also have some cycles to spare to work on JRuby and maybe prepare
a new ups
ix the Puppet regression reported here, on our
buster systems.
Thanks,
-- Jérôme
the test failures by disabling the affected tests.
The logging problem is still present in puppetserver (and almost
certainly puppetdb) with the patched
trapperkeeper-webserver-jetty9-clojure package.
Thanks,
-- Jérôme
://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036250
In my view this is a bug in src:logback.
-- Jérôme
?
-- Jérôme
Le 2023-05-19 à 09 h 53, Markus Koschany a écrit :
Control: tags -1 patch
Hi,
I am attaching a patch for this issue. Somehow your package fell through the
cracks because it has no dependency on logback. Logback is pulled in by Jetty
though. While Logback and Jetty use the Jakarta servlet
raries, if that is even
possible.
Therefore, I would like to request assistance to find a solution.
The removal of this package would inevitably lead to the removal of
puppetserver from Debian, which would be highly unfortunate.
Thanks,
-- Jérôme
close to the release I'm not sure if it'll get through.
Thanks,
-- Jérôme
systems to bookworm (all created from d-i's debian-11.6.0-amd64-netinst.iso,
and “Encrypted LVM” partition scheme, on VMs with 1024M RAM).
Jérôme, what memory cost is the keyslot using? (Paste the output of
`cryptsetup luksDump /dev/vda5 | grep -A3 PBKDF:`.) Would also be
interested to see
cryptsetup: ERROR: vda5_crypt: cryptsetup failed, bad password or
options?
This machine was booting just fine before upgrading, under bullseye.
The problem appears to be perhaps related to #924560, but in this
instance, the issue causing an unbootable system post-upgrade.
Thanks,
-- Jérôme
Control: tag -1 pending
Hello,
Bug #1030427 in trapperkeeper-metrics-clojure reported by you has been fixed in
the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/clojure-team/trapperkeeper-metrics
Control: tag -1 pending
Hello,
Bug #1030428 in trapperkeeper-scheduler-clojure reported by you has been fixed
in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/clojure-team/trapperkeeper-sched
because that package will create a "puppet" user in the
environment.
Thanks,
-- Jérôme
rtant bits of the
configuration may likely be lost in translation (eg. auth.conf).
So considering all this I'm currently leaning towards adding a
transitional "puppet-master" and/or "puppet-master-passenger" package
for the purpose of shipping a NEWS file recommending that users migrate
to the puppetserver package manually.
-- Jérôme
:
https://github.com/lektor/lektor/pull/1051
I see the maintainer and Jérôme have worked on new versions but they
were never released.
Is there something missing?
And of course I've just noticed that python3-mistune0 now exists in
Debian, so maybe I can finally upload Lektor 3.3 ...
:
https://github.com/lektor/lektor/pull/1051
I see the maintainer and Jérôme have worked on new versions but they
were never released.
Is there something missing?
Since python-mistune has moved to 2.x in Debian, the Lektor 3.2 and 3.3
branches are no longer functional. Upstream has integrated
Hello,
According to the pgpainless upstream, this bug is fixed bouncycastle
1.72.1 and later versions.
Unfortunately, upstream does not appear to have tagged any version
beyond 1.72 in their git repository.
Thanks,
-- Jerome
Control: tag -1 pending
Hello,
Bug #1025442 in jruby reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/java-team/jruby/-/commit/456069f250320fc8b131d1446a73d2da8d
On Mon, 5 Dec 2022 22:04:06 +0100 Santiago Vila wrote:
Hi.
I attach an upload proposal for bullseye, in debdiff format against
version 1.3.610-4 (stable version), so you can upload it "as is" if
everything else is ok.
There is a stable point release around the corner, it would be wonderful
Package: pdfarranger
Version: 1.8.2-1
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: jeromerob...@gmx.com
Dear Maintainer,
pdfarranger depends on pikepdf. pikepdf 5.1.1 FTBS with libqpdf 11:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019694
Accordin
Hello,
This bug has been fixed by uploading core-async-clojure version
1.3.610-5 which includes this change:
https://salsa.debian.org/clojure-team/core-async-clojure/-/commit/afae424e1de2e423e1842dec6d23085f31a5bc9c
Thanks!
-- Jerome
Control: tag -1 pending
Hello,
Bug #1013662 in core-async-clojure reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/clojure-team/core-async-clojure/-/commit/9cbf1
Hello,
I'm unable to reproduce this bug locally.
When I diff, the build logs, the only relevant element I can find is
that in my build environment, the "clojure_1.10.3-1" package is
installed, whereas in the failing build log, it appears to be absent.
I think it would be worth it to attemp
Version: 1.3.1-4
The colorscheme patch was refreshed to fix the FTBFS bug.
-- Jeroime
bug happens only due to
> different transition times from unstable to testing. This cannot be
> tested in unstable before.
Is there a way to avoid this problem happen in the future?
--
Jérôme Pouiller
Thank you Adrian for reporting this.
We have fixes for this upstream:
commit *c94efd6390599a4a291b7fe8b3d2d62699247380*
Author: Jerome St-Louis
Date: Sun Sep 6 03:35:01 2020 -0400
compiler/bootstrap: Updated for GCC 10 Common fixes
commit *7d835dd5c6e17ad1626ec7b6f1725e0f7f8a9371*
Autho
ignal to child
➜ ~ /usr/bin/firefox
ExceptionHandler::GenerateDump cloned child 46533
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
Regards,
Jérôme.
On Thu, 23 Jan 2020 08:03:43 +0100 Mi
It seems a directory is missing :
---
Could not enumerate user data directory /var/lib/lightdm/data: Error opening
directory '/var/lib/lightdm/data': No such file or directory
---
I attached the last lines of my /var/log/syslog
Dec 24 15:31:43 l systemd[1]: anacron.service: Succeeded.
Dec 24 15:
Le 24/05/2019 à 17:00, Markus Koschany a écrit :
> Control: severity -1 grave
>
> On Fri, 24 May 2019 13:45:04 +0200 Bardot Jerome
> wrote:
> [...]
>> Can't find robocode.core-1.x.jar module near to robocode.jar
>> Class path: /usr/share/java/robocode.jar
> Thanks for reporting. This is another Ja
Thanks Ludovic, the updated version has been unblocked and has now
migrated to testing, this fixes the issue.
Le mer. 24 avr. 2019 à 17:10, Ludovic Rousseau
a écrit :
>
> Le 24/04/2019 à 15:51, Ludovic Rousseau a écrit :
> > debian-release will not accept to migrate 1.2.2 into testing.
>
> Maybe
Hi,
I am the main developper of pyFAI and we are aware there are issues
with python 3.7.0 (we have issues opened on github about that). We will
re-enable CI on python-3.7 as soon as 3.7.1 is out and our code can run
on it.
Would it be possible to get an extra month to setup a new release
supporti
Dear Sven,
Thank you for the notice.
It would be extremely helpful in solving this rapidly to have a
quick-link to the exact version of that stddef.h (possibly the other
libc headers as well if that line refers so something else...).
Were you suggesting those commits because there were __alig
Le Fri, 12 Jan 2018 11:13:20 +0100,
Rolf Leggewie a écrit :
> On 11.01.2018 21:49, Jérôme wrote:
> > QBirthday now has a setup.py which makes it easier to install. I
> > hope it also makes it easier to create a .deb from the sources.
> >
> > Rolf (or anyone), would yo
Hi Iain,
python3-trollius is still a dependency of python3-qtile, probably an
oversight!
Also, I would be glad to help you maintaining qtile if you need so -
even if I'm not yet a DD.
Thanks in advance,
Jérôme
signature.asc
Description: OpenPGP digital signature
Package: reportbug
Version: 7.1.10
Severity: grave
--- Please enter the report below this line. ---
Reportbug (gtk2 ui) crash when i select package.
The command line output :
Traceback (most recent call last):
File "/usr/bin/reportbug", line 2265, in
main()
File "/usr/bin/reportbug",
nce a qbirthday package is pushed, do you think you could
publish a transition package from gbirthday?
There will be a few breaking changes, so the update won't be 100%
transparent to the user, who may have to recreate his configuration,
but it is better than nothing.
Thanks.
--
Jérôme
Hello.
FYI,
I removed the libreoffice-wiki-publisher package. Next I achieved to use
Writer. However I experienced a crash when I tried to create a new LO Base file.
I reproduced this crash by following a slightly different use case.
At first, I saved a few memory (the host has only 256MB RAM).
The NetworkManager service is always disabled on this host.
As root the following command :
systemctl stop rsyslog.service
Next as normal user, I terminated the nm-a
Hello,
Do you have libreoffice-wiki-publisher installed?
yes I have, version 1.2.0+LibO5.2.7-1
To confirm, please send a gb backtrace; see
https://wiki.documentfoundation.org/QA/BugReport/Debug_Information
For each installed package of libreoffice, openjdk and libstdc++, I installed
the m
Package: libreoffice-writer
Version: 1:5.2.7-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I tried to launch Libreoffice Writer by the desktop menu entry, nothing
happends. However, I successfully ran Calc, Impress and Draw.
Next, I opened a terminal and launched th
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for the 0.44.15-1 release of my package
"ecere-sdk".
This closes 2 bugs including a serious one (FTBFS with GCC 6 which had
it removed from 'testing').
Closes #811957 (https://bugs.debian.org/cgi-bin/bu
We agree to rename 'ide' to 'ecere-ide' but we're hoping the decided
policy is to leave 'ide' alone for anyone. (We'll now have to setup
'ide' aliases in our bash configs)
It's true we don't enjoy the same popularity / awareness as that GNOME
project, but our IDE has been around since 2003.
What
Hi Ben, Hi Matt,
I can confirm as well that the latest package version 4.4.6-1 fixes
the issue on a Lenovo ThinkPad Tablet 8.
Thanks a lot,
Jérôme
rk around the problem?
Yes. The kernel boots fine with that parameter.
> - If you haven't already reported this, does the Linux 4.5-rc4 package
> from experimental have the same problem?
Yes, same problem with the current Linux (4.5-rc7) package from experimental.
Jérôme
This kernel is also affected : linux-image-2.6.32-5-686_2.6.32-48squeeze17
I believe this is fixed since v8.
--
Jérôme
Rolf, Mattia.
I just released v0.6.9 which includes the patch from Mattia.
Note you can drop the recommandation on evolution-data-server and
python-evolution since v0.6.8.
--
Jérôme
Le 2015-12-16 13:39, Mattia Rizzolo a écrit :
> On Wed, Dec 16, 2015 at 09:47:09AM +0100, Jérôme wrote:
> oh, that's what happens!
> I expected a full-sized window. My systry is really tiny, and I don't
> look at it (that's why is tity), so didn't notice the ne
ich was broken anyway).
> I want to try uploading a new upstream version in a NMU, if possible :)
I don't know what a NMU is, and neither my search engine nor wikipedia
helped.
>> Thanks.
>
> Thank you for being involved downstream! :)
Well, I'm a Debian user, so I'm taking care of myself in the process. Of
course I'm glad if Debian users and Debian derivatives benefit from it.
Thank you for your help.
--
Jérôme
debian
( https://github.com/ecere/ecere-sdk/archive/0.44.11-1.tar.gz )
Please let me know if you require my assistance.
Best regards,
Jerome
--------
*Jérôme Jacovella-St-Louis*
/Founder, Chief Technology Officer/
Ecere Corporation _h
Le Tue, 15 Dec 2015 13:30:36 +,
Mattia Rizzolo a écrit :
> On Tue, Dec 15, 2015 at 10:04:09AM +0100, Jérôme wrote:
> > Hi.
>
> Hi Jérôme!
> Please note that nor me nor anybody else but the maintainer receive
> emails from bug reports unless they have subscribed through
recation. I'm happy if I'm wrong.
- I hope to get a Qt version packageable for Stretch. Help welcome, of
course.
Have a nice day.
--
Jérôme
On Thu, 21 May 2015 12:14:15 +0800
Paul Wise wrote:
> On Wed, 20 May 2015 14:59:04 +0200 Jérôme Kieffer wrote:
>
> > jerome@patagonia:~$ sudo blkid -o value -s TYPE /dev/sdb4
> > jerome@patagonia:~$ echo $?
> > 0
>
> That is strange, what about just this?
&g
sincerely,
Jérôme Deuchnord
-- Package-specific info:
** Kernel log: boot messages should be attached
** Model information
not available
** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Atom Processor D2xxx/N2xxx DRAM
Controller [8086:0bf1] (rev 03)
Subsystem: ASUSTeK Co
kages from src:meta-gnome3 that
> need changes, or is there anything else?
>
> http://lists.debian.org/53863f46.2050...@pyro.eu.org
Indeed, this is the only issue.
task-gnome-desktop depends on gnome-core, but this will not prevent the
migration.
Regards,
-- Jérôme
--
To UNSUBS
Why not make it a transit package to unar, then ?
--
Jérôme
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
To clarify — the above-mentioned gist is not a workaround against the
issue, but a sample snippet to repair my machine after it becomes unusable
because of this bug. It's just remounting everything which was unmounted to
make the machine usable again. It's (obviously) specific to my system, but
it
Is there a way for us to build only this module ourselves, without messing
with the whole php5 packages suite?
Is this documented somewhere?
Thanks
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: libdrm2
Version: 2.4.5-2
Severity: serious
Hi,
After upgrading from 2.3.1-2 to 2.4.5-2, my Xorg failed to
work properly. After downgrading to 2.3.1-2, situation is
normal again.
I do use latest Xorg from unstable along with fglrx non-free
drivers, and kernel 2.6.26.
Regards,
--
To
Please ignore my previous mail. The culprit is libdrm2.
Regards,
- Mail Original -
De: "Debian Bug Tracking System"
À: "Jérôme Marant"
Envoyé: Samedi 28 Mars 2009 18:24:02 GMT +01:00 Amsterdam / Berlin / Berne /
Rome / Stockholm / Vienne
Objet: Bug#517005:
Hi,
I recenlty updated my system and Xorg won't start.
It looks like the problem is still around.
Regard,
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Hi,
Also, the patch is also included in the last version 2.1.6 (but not
yet available on debian)
Regards,
Jérôme
Christian Hammers wrote, the 26/08/2008 23:42 :
Hello Sebastian
What do you think of the latest patch proposal for this bug?
Currently there is NO version of easytag in
Hi,
In the version 2.1.1, there is a small mistake in the configure script
that may cause the problem of detection of MP3 support. This will be
fixed in the 2.1.2 version
In attachment, a patch from Thomas Klausner
Regards,
Jerome
--
EasyTAG - Tag editor for MP3 and Ogg Vorbis files
http://
myself and applied patches
that used to work.
Regards,
--
Jérôme Marant
ipsel
machine
which seems to be available), could you please help us investigating the
problem?
Thanks in advance.
--
Jérôme Marant
Le jeudi 21 décembre 2006 21:34, Rob Browning a écrit :
> Jérôme Marant <[EMAIL PROTECTED]> writes:
>
> > Rob, are you taking care of this, or should I?
>
> Please do, if you have the time.
I will only available till next Saturday so I guess someone will have to
take
Le samedi 16 décembre 2006 21:09, Rob Browning a écrit :
> Jérôme Marant <[EMAIL PROTECTED]> writes:
>
> > Shall we contact Ryan?
>
> Sounds like a good idea. Though I suppose there's another difference
> between vaughan and the buildd. On vaughan I wasn't
Le samedi 16 décembre 2006 19:08, Rob Browning a écrit :
> Jérôme Marant <[EMAIL PROTECTED]> writes:
>
> > It looks like it has been rescheduled for building yesterday and it
> > is still failing.
> >
> > Please note that vaughan is not the build machine. I
n rescheduled for building yesterday and it
is still failing.
Please note that vaughan is not the build machine. It is "rem" which
is maitained by Ryan Murray.
--
Jérôme Marant
Le vendredi 15 décembre 2006 16:45, Martin Michlmayr a écrit :
> * Jérôme Marant <[EMAIL PROTECTED]> [2006-12-15 16:08]:
> > Then I don't know. Why does it fail only on mipsel?
> > As I said no patch has been applied to the C code nor anything related
> > to it (
#x27;t know. Why does it fail only on mipsel?
As I said no patch has been applied to the C code nor anything related
to it (like autotools).
Dare I question the toolchain?
--
Jérôme Marant
quot;FTBFS". The autofiles-sync rule is run manually before
building the package.
--
Jérôme Marant
1 - 100 of 140 matches
Mail list logo