Page MenuHome GnuPG

scuteProject
ActivePublic

Members

  • This project does not have any members.
  • View All

Recent Activity

Sun, Apr 18

werner added a comment to T5394: scute: Build failure with slibtool.

t-link does not do antthing useful, anyway. I don't think it is justified to add dlopen stuff. Running real test is anyway a manual action; for a full test automation we would need to emulate all supported cards.

Sun, Apr 18, 7:40 PM · toolchain, Feature Request, scute

Sat, Apr 17

gouttegd added a comment to T5394: scute: Build failure with slibtool.

the t-link test should dlopen scute.so in runtime rather than link against it in build-time.

Sat, Apr 17, 4:15 PM · toolchain, Feature Request, scute

Apr 16 2021

midipix added a comment to T5394: scute: Build failure with slibtool.

As of slibtool commit 9c5ba5eb, scute now builds out of the box. I'd still recommend taking the above into consideration, though.

Apr 16 2021, 4:53 PM · toolchain, Feature Request, scute
midipix added a comment to T5394: scute: Build failure with slibtool.

For what it's worth, scute is in violation of gnu libtool's documentation. Building with gnu libtool:

Apr 16 2021, 10:21 AM · toolchain, Feature Request, scute

Apr 13 2021

midipix added a comment to T5394: scute: Build failure with slibtool.

Regarding slibtool: I would actually like to have an easier to maintain tool than libtool (of which we use our own version) for GnuPG related software. However, its requirement "the compiler should support -std=c99" is currently a no-starter for libgcrypt and some other libs.

Apr 13 2021, 9:13 PM · toolchain, Feature Request, scute
werner triaged T5394: scute: Build failure with slibtool as Normal priority.
Apr 13 2021, 8:13 AM · toolchain, Feature Request, scute
orbea added a comment to T5394: scute: Build failure with slibtool.

Regarding your patch, I am personally not opposed to it, but apparently Debian’s policy says the library/module should be called scute while Gentoo’s policy says it should be called libscute… What should an upstream developer do?

Apr 13 2021, 1:49 AM · toolchain, Feature Request, scute

Apr 12 2021

werner added a comment to T5394: scute: Build failure with slibtool.

Regarding slibtool: I would actually like to have an easier to maintain tool than libtool (of which we use our own version) for GnuPG related software. However, its requirement "the compiler should support -std=c99" is currently a no-starter for libgcrypt and some other libs.

Apr 12 2021, 11:25 PM · toolchain, Feature Request, scute
gouttegd added a project to T5394: scute: Build failure with slibtool: scute.
Apr 12 2021, 10:59 PM · toolchain, Feature Request, scute

Mar 31 2021

gouttegd closed T5360: scute: -fcommon needed when building with gcc-10 as Resolved.
Mar 31 2021, 6:53 PM · scute
cbiedl added a comment to T5360: scute: -fcommon needed when building with gcc-10.

Looks good to me: "make && make check" passes.

Mar 31 2021, 4:45 PM · scute
werner added a comment to T5360: scute: -fcommon needed when building with gcc-10.

FWIW, in GnuPG we use

Mar 31 2021, 9:10 AM · scute

Mar 30 2021

gouttegd changed the status of T5360: scute: -fcommon needed when building with gcc-10 from Open to Testing.

It should be fixed with 49ad2b0e05e3fcb8c8c2e23bb1c6063b390dee02, though I don’t have a gcc-10 to check. It does work with gcc-9.3 with -fno-common.

Mar 30 2021, 11:48 PM · scute

Mar 26 2021

gniibe added a comment to T5358: scute: Errors when building 1.7.

It's OK not supporting generation in PostScript format.
Thus, we can remove image_eps support.
Then, convert is not required any more.

Mar 26 2021, 8:25 AM · scute

Mar 25 2021

gouttegd claimed T5360: scute: -fcommon needed when building with gcc-10.
Mar 25 2021, 3:09 PM · scute
cbiedl created T5360: scute: -fcommon needed when building with gcc-10.
Mar 25 2021, 1:35 PM · scute
gouttegd closed T5358: scute: Errors when building 1.7 as Resolved.

Fixed with commit 4d95b7457d62bf785a2157bb2cfa002bde7ff8f5. It turned out the test the convert was already there, but its result was not used to decide whether to build the doc or not.

Mar 25 2021, 11:43 AM · scute

Mar 24 2021

gouttegd triaged T5358: scute: Errors when building 1.7 as Normal priority.
Mar 24 2021, 11:05 PM · scute
gouttegd claimed T5358: scute: Errors when building 1.7.

I agree about checking for convert (but maybe just skip building the doc instead of aborting everything if convert cannot be found).

Mar 24 2021, 11:03 PM · scute
cbiedl created T5358: scute: Errors when building 1.7.
Mar 24 2021, 10:39 PM · scute

Jan 7 2021

werner closed T5224: Release Scute 1.7.0 as Resolved.
Jan 7 2021, 4:00 PM · Release Info, scute
werner updated the task description for T5224: Release Scute 1.7.0.
Jan 7 2021, 4:00 PM · Release Info, scute
werner created T5224: Release Scute 1.7.0.
Jan 7 2021, 3:20 PM · Release Info, scute

Sep 13 2019

gouttegd closed T4697: Release Scute 1.6.0 as Resolved.
Sep 13 2019, 12:19 AM · Release Info, scute

Sep 11 2019

gouttegd added a comment to T4697: Release Scute 1.6.0.

I could not reproduce such a failure either under any conditions.

Sep 11 2019, 12:37 AM · Release Info, scute

Sep 10 2019

werner triaged T4703: Scute > 1.4.0 does not work with MacOS X as Normal priority.
Sep 10 2019, 4:18 PM · MacOS, scute
aheinecke added a comment to T4697: Release Scute 1.6.0.

In my debian buster pbuilder enviornment I got the following failure when packaging master (beta195):

Sep 10 2019, 11:26 AM · Release Info, scute

Sep 9 2019

gouttegd added a comment to T4697: Release Scute 1.6.0.

With the build problem on Mac OS now fixed with d551cf9, barring any last minute issue I plan to do the actual release by the end of the day tomorrow (10 September).

Sep 9 2019, 11:25 PM · Release Info, scute
gouttegd added a comment to T4703: Scute > 1.4.0 does not work with MacOS X.

If I understand correctly, the problem stems from the -module flag added to the LDFLAGS in commit dc2211179. It's that flag that instruct libtool to create a bundle (.so file) instead of a dynamically linked shared library (.dylib file). But that flag is needed to force automake to accept that the library is to be named scute instead of libscute (without that flag automake errors out, complaining that scute.la is not a standard libtool library name).

Sep 9 2019, 5:58 PM · MacOS, scute
werner added a project to T4703: Scute > 1.4.0 does not work with MacOS X: MacOS.

Given that 1.5 already had that problem, I would suggest to ignore that bug for the 1.6 release. We can work on that later.

Sep 9 2019, 5:12 PM · MacOS, scute
gouttegd created T4703: Scute > 1.4.0 does not work with MacOS X.
Sep 9 2019, 3:32 PM · MacOS, scute
gouttegd claimed T4697: Release Scute 1.6.0.

I just checked that Scute builds cleanly on Slackware, Debian, and in a cross-compilation setup against Mingw32.

Sep 9 2019, 1:31 AM · Release Info, scute

Sep 6 2019

werner created T4697: Release Scute 1.6.0.
Sep 6 2019, 11:49 AM · Release Info, scute

Jul 13 2017

justus added a comment to T3274: Scute tests fail in Jenkins "native" configuration.

"gouttegd (Damien Goutte-Gattat)" <noreply@dev.gnupg.org> writes:

I've just pushed the two fixes. `GNUPGHOME` is now set to the tests directory when running the tests and `gpg-connect-agent` is now looked for in `PATH` at runtime.

When the tests are run, Scute now contacts the agent intended for the tests instead of any agent running on behalf of the Jenkins user. And so the tests pass or skip appropriately.
Jul 13 2017, 11:25 AM · CI, scute

Jul 12 2017

gouttegd closed T3274: Scute tests fail in Jenkins "native" configuration as Resolved.

I've just pushed the two fixes. GNUPGHOME is now set to the tests directory when running the tests and gpg-connect-agent is now looked for in PATH at runtime.

Jul 12 2017, 12:53 PM · CI, scute

Jul 11 2017

gouttegd added a comment to T3274: Scute tests fail in Jenkins "native" configuration.

All build artifacts are accessible

Jul 11 2017, 8:50 PM · CI, scute
justus added a comment to T3274: Scute tests fail in Jenkins "native" configuration.

I see several problems here:

Jul 11 2017, 5:51 PM · CI, scute
justus claimed T3274: Scute tests fail in Jenkins "native" configuration.
Jul 11 2017, 5:19 PM · CI, scute
justus added a comment to T3274: Scute tests fail in Jenkins "native" configuration.

All build artifacts are accessible, e.g.: https://jenkins.gnupg.org/job/scute/ws/XTARGET/native/obj/tests/test-suite.log

Jul 11 2017, 5:18 PM · CI, scute
gouttegd created T3274: Scute tests fail in Jenkins "native" configuration in the S1 Public space.
Jul 11 2017, 5:03 PM · CI, scute

Jul 7 2017

gouttegd closed T3195: Scute does not reliably find the agent socket, especially if it is relocated to /run.... as Resolved.

OK, I pushed my fix into master.

Jul 7 2017, 4:35 PM · gnupg (gpg22), scute

Jul 6 2017

werner added a comment to T3195: Scute does not reliably find the agent socket, especially if it is relocated to /run.....

The canonical repo is git://git.gnupg.org . We have not yet mirrored it at dev.gnupg.org.

Jul 6 2017, 5:43 PM · gnupg (gpg22), scute
gouttegd added a comment to T3195: Scute does not reliably find the agent socket, especially if it is relocated to /run.....

Since there is no news for the last two weeks, I am wondering: am I the one blocking the situation here? Are you waiting for me to do something to make progress?

Jul 6 2017, 4:23 PM · gnupg (gpg22), scute

Jun 27 2017

justus reassigned T3195: Scute does not reliably find the agent socket, especially if it is relocated to /run.... from justus to werner.
Jun 27 2017, 11:19 AM · gnupg (gpg22), scute

Jun 23 2017

gouttegd added a comment to T3195: Scute does not reliably find the agent socket, especially if it is relocated to /run.....

Yes, I am ready to accept write access to the Scute repository.

Jun 23 2017, 5:15 PM · gnupg (gpg22), scute
werner assigned T3195: Scute does not reliably find the agent socket, especially if it is relocated to /run.... to justus.

Justus, please apply the patches.

Jun 23 2017, 4:49 PM · gnupg (gpg22), scute

Jun 22 2017

gouttegd added a comment to T3195: Scute does not reliably find the agent socket, especially if it is relocated to /run.....

I think the best method to make sure Scute can always find the socket is to use gpg-connect-agent to ask for the socket: we call gpg-connect-agent 'GETINFO socket_name' /bye and read the reply.

Jun 22 2017, 3:34 PM · gnupg (gpg22), scute
gouttegd added a watcher for scute: gouttegd.
Jun 22 2017, 11:12 AM

Jun 6 2017

justus created T3195: Scute does not reliably find the agent socket, especially if it is relocated to /run.....
Jun 6 2017, 9:46 AM · gnupg (gpg22), scute

Mar 30 2017

admin created scute.
Mar 30 2017, 6:42 PM