What does “You have requested package `foo', but the package provides `foo'.” mean?

I know what this message means in general ("do not add path names in package names"), and my question is not a duplicate of You have requested package `include/foo' but the package provides `foo', where the two names differ (by the path name). In my case the package names are really identical (without path name in both cases)!

I'm working on MiKTeX 2.9, with latest updates (I refreshed FNDB). I get this with the latest moderncv package (version 2.0), MWE:

documentclass{moderncv}

moderncvtheme{classic}

name{Foo}{Bar}

begin{document}

end{document}

where I get

You have requested package `moderncvheadi', but the package provides `moderncvheadi'.

You have requested package `moderncvbodyi', but the package provides `moderncvbodyi'.

What does trigger this warning in this case and how can I solve it? Is it a bug in moderncv? The official source on https://github.com/xdanaux/moderncv looks fine to me.

edited Aug 9 '15 at 17:01

asked Aug 8 '15 at 20:39

Foo Bar

6,069104092

2

I get the same warning on TL 2015/Linux.

– user31729
Aug 8 '15 at 20:48

Same warning on TL 2016/Windows.

– Vesnog
Jul 31 '17 at 17:48

2

Bug is still there, tracked by github.com/xdanaux/moderncv/issues/1 github.com/xdanaux/moderncv/issues/7. The bug might be fixed on GitHub but not on CTAN (at least github.com/xdanaux/moderncv/issues/1#issuecomment-317167797 suggests so).

– Blaisorblade
Sep 13 '17 at 18:20

add a comment |

I'm working on MiKTeX 2.9, with latest updates (I refreshed FNDB). I get this with the latest moderncv package (version 2.0), MWE:

documentclass{moderncv}

moderncvtheme{classic}

name{Foo}{Bar}

begin{document}

end{document}

where I get

You have requested package `moderncvheadi', but the package provides `moderncvheadi'.

You have requested package `moderncvbodyi', but the package provides `moderncvbodyi'.

What does trigger this warning in this case and how can I solve it? Is it a bug in moderncv? The official source on https://github.com/xdanaux/moderncv looks fine to me.

edited Aug 9 '15 at 17:01

asked Aug 8 '15 at 20:39

Foo Bar

6,069104092

2

I get the same warning on TL 2015/Linux.

– user31729
Aug 8 '15 at 20:48

Same warning on TL 2016/Windows.

– Vesnog
Jul 31 '17 at 17:48

2

Bug is still there, tracked by github.com/xdanaux/moderncv/issues/1 github.com/xdanaux/moderncv/issues/7. The bug might be fixed on GitHub but not on CTAN (at least github.com/xdanaux/moderncv/issues/1#issuecomment-317167797 suggests so).

– Blaisorblade
Sep 13 '17 at 18:20

add a comment |

I'm working on MiKTeX 2.9, with latest updates (I refreshed FNDB). I get this with the latest moderncv package (version 2.0), MWE:

documentclass{moderncv}

moderncvtheme{classic}

name{Foo}{Bar}

begin{document}

end{document}

where I get

You have requested package `moderncvheadi', but the package provides `moderncvheadi'.

You have requested package `moderncvbodyi', but the package provides `moderncvbodyi'.

What does trigger this warning in this case and how can I solve it? Is it a bug in moderncv? The official source on https://github.com/xdanaux/moderncv looks fine to me.

edited Aug 9 '15 at 17:01

asked Aug 8 '15 at 20:39

Foo Bar

6,069104092

I'm working on MiKTeX 2.9, with latest updates (I refreshed FNDB). I get this with the latest moderncv package (version 2.0), MWE:

documentclass{moderncv}

moderncvtheme{classic}

name{Foo}{Bar}

begin{document}

end{document}

where I get

You have requested package `moderncvheadi', but the package provides `moderncvheadi'.

You have requested package `moderncvbodyi', but the package provides `moderncvbodyi'.

What does trigger this warning in this case and how can I solve it? Is it a bug in moderncv? The official source on https://github.com/xdanaux/moderncv looks fine to me.

packages moderncv warnings

edited Aug 9 '15 at 17:01

asked Aug 8 '15 at 20:39

Foo Bar

6,069104092

edited Aug 9 '15 at 17:01

asked Aug 8 '15 at 20:39

Foo Bar

6,069104092

edited Aug 9 '15 at 17:01

asked Aug 8 '15 at 20:39

Foo Bar

6,069104092

asked Aug 8 '15 at 20:39

Foo Bar

6,069104092

asked Aug 8 '15 at 20:39

Foo Bar

6,069104092

2

I get the same warning on TL 2015/Linux.

– user31729
Aug 8 '15 at 20:48

Same warning on TL 2016/Windows.

– Vesnog
Jul 31 '17 at 17:48

2

Bug is still there, tracked by github.com/xdanaux/moderncv/issues/1 github.com/xdanaux/moderncv/issues/7. The bug might be fixed on GitHub but not on CTAN (at least github.com/xdanaux/moderncv/issues/1#issuecomment-317167797 suggests so).

– Blaisorblade
Sep 13 '17 at 18:20

add a comment |

2

I get the same warning on TL 2015/Linux.

– user31729
Aug 8 '15 at 20:48

Same warning on TL 2016/Windows.

– Vesnog
Jul 31 '17 at 17:48

2

Bug is still there, tracked by github.com/xdanaux/moderncv/issues/1 github.com/xdanaux/moderncv/issues/7. The bug might be fixed on GitHub but not on CTAN (at least github.com/xdanaux/moderncv/issues/1#issuecomment-317167797 suggests so).

– Blaisorblade
Sep 13 '17 at 18:20

I get the same warning on TL 2015/Linux.

– user31729
Aug 8 '15 at 20:48

Same warning on TL 2016/Windows.

– Vesnog
Jul 31 '17 at 17:48

Bug is still there, tracked by github.com/xdanaux/moderncv/issues/1 github.com/xdanaux/moderncv/issues/7. The bug might be fixed on GitHub but not on CTAN (at least github.com/xdanaux/moderncv/issues/1#issuecomment-317167797 suggests so).

– Blaisorblade
Sep 13 '17 at 18:20

add a comment |

2 Answers
2

active

oldest

votes

its a bug in the class, looks like a recent change in the github log, can't test here, no tex, but the package name constructed by

expandafter moderncvromannumeral

which doesn't do the right thing expandafter does nothing there, you can ignore the warning until it's fixed.

Lines 315 to 333 of moderncv.cls should be changed into

% loads a header variant

% usage: moderncvhead[<optional head option>]{<header variant number>}

newcommand*{moderncvhead}[2]{%

  begingroupedefx{endgroup

    noexpandRequirePackage[#1]{moderncvheadifcase#2or ior iior iiior ivor vfi}%

  }x 

}



% loads a body variant

% usage: moderncvbody[<optional body option>]{<body variant number>}

newcommand*{moderncvbody}[2]{%

  begingroupedefx{endgroup

    noexpandRequirePackage[#1]{moderncvbodyifcase#2or ior iior iiior ivor vfi}%

  }x 

}



% loads a footer variant

% usage: moderncvfoot{<footer variant number>}

newcommand*{moderncvfoot}[1]{%

  begingroupedefx{endgroup

    noexpandRequirePackage{moderncvfootifcase#1or ior iior iiior ivor vfi}%

  }x

}

but it's not possible to add this code in a document, because the macros are already used by the class itself.

edited Aug 11 '15 at 20:58

answered Aug 8 '15 at 20:53

David Carlisle

497k4111441891

@egreg takes pity on a user with no tex on his computer:-) Thanks I just came back here to add that and saw you'd done it:-)

– David Carlisle
Aug 8 '15 at 21:35

5

I also fixed some missing %. ;-)

– egreg
Aug 8 '15 at 21:47

Thanks for the fix! Have you guys though confirmed it worked? I am still getting the nasty warnings after changing lines 315 to 333, but maybe it's somehow just me :(

– Xavier
Aug 11 '15 at 4:38

1

@Xavier never trust code from an untrusted source:-) I added a fix:-)

– David Carlisle
Aug 11 '15 at 6:51

Shouldn't or iorii be or ior ii (in all three cases)?

– clemens
Aug 11 '15 at 8:59

|
show 3 more comments

This bug has been fixed in the GitHub repo, but not yet (as of 2019-04-03) on CTAN: https://www.ctan.org/pkg/moderncv version:2.0.0 date:2015-07-28

answered 11 hours ago

davejagoda

1113

New contributor

add a comment |

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "85"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f260446%2fwhat-does-you-have-requested-package-foo-but-the-package-provides-foo-me%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

2 Answers
2

active

oldest

votes

2 Answers
2

active

oldest

votes

its a bug in the class, looks like a recent change in the github log, can't test here, no tex, but the package name constructed by

expandafter moderncvromannumeral

which doesn't do the right thing expandafter does nothing there, you can ignore the warning until it's fixed.

Lines 315 to 333 of moderncv.cls should be changed into

% loads a header variant

% usage: moderncvhead[<optional head option>]{<header variant number>}

newcommand*{moderncvhead}[2]{%

  begingroupedefx{endgroup

    noexpandRequirePackage[#1]{moderncvheadifcase#2or ior iior iiior ivor vfi}%

  }x 

}



% loads a body variant

% usage: moderncvbody[<optional body option>]{<body variant number>}

newcommand*{moderncvbody}[2]{%

  begingroupedefx{endgroup

    noexpandRequirePackage[#1]{moderncvbodyifcase#2or ior iior iiior ivor vfi}%

  }x 

}



% loads a footer variant

% usage: moderncvfoot{<footer variant number>}

newcommand*{moderncvfoot}[1]{%

  begingroupedefx{endgroup

    noexpandRequirePackage{moderncvfootifcase#1or ior iior iiior ivor vfi}%

  }x

}

but it's not possible to add this code in a document, because the macros are already used by the class itself.

edited Aug 11 '15 at 20:58

answered Aug 8 '15 at 20:53

David Carlisle

497k4111441891

@egreg takes pity on a user with no tex on his computer:-) Thanks I just came back here to add that and saw you'd done it:-)

– David Carlisle
Aug 8 '15 at 21:35

5

I also fixed some missing %. ;-)

– egreg
Aug 8 '15 at 21:47

Thanks for the fix! Have you guys though confirmed it worked? I am still getting the nasty warnings after changing lines 315 to 333, but maybe it's somehow just me :(

– Xavier
Aug 11 '15 at 4:38

1

@Xavier never trust code from an untrusted source:-) I added a fix:-)

– David Carlisle
Aug 11 '15 at 6:51

Shouldn't or iorii be or ior ii (in all three cases)?

– clemens
Aug 11 '15 at 8:59

|
show 3 more comments

its a bug in the class, looks like a recent change in the github log, can't test here, no tex, but the package name constructed by

expandafter moderncvromannumeral

which doesn't do the right thing expandafter does nothing there, you can ignore the warning until it's fixed.

Lines 315 to 333 of moderncv.cls should be changed into

% loads a header variant

% usage: moderncvhead[<optional head option>]{<header variant number>}

newcommand*{moderncvhead}[2]{%

  begingroupedefx{endgroup

    noexpandRequirePackage[#1]{moderncvheadifcase#2or ior iior iiior ivor vfi}%

  }x 

}



% loads a body variant

% usage: moderncvbody[<optional body option>]{<body variant number>}

newcommand*{moderncvbody}[2]{%

  begingroupedefx{endgroup

    noexpandRequirePackage[#1]{moderncvbodyifcase#2or ior iior iiior ivor vfi}%

  }x 

}



% loads a footer variant

% usage: moderncvfoot{<footer variant number>}

newcommand*{moderncvfoot}[1]{%

  begingroupedefx{endgroup

    noexpandRequirePackage{moderncvfootifcase#1or ior iior iiior ivor vfi}%

  }x

}

but it's not possible to add this code in a document, because the macros are already used by the class itself.

edited Aug 11 '15 at 20:58

answered Aug 8 '15 at 20:53

David Carlisle

497k4111441891

@egreg takes pity on a user with no tex on his computer:-) Thanks I just came back here to add that and saw you'd done it:-)

– David Carlisle
Aug 8 '15 at 21:35

5

I also fixed some missing %. ;-)

– egreg
Aug 8 '15 at 21:47

Thanks for the fix! Have you guys though confirmed it worked? I am still getting the nasty warnings after changing lines 315 to 333, but maybe it's somehow just me :(

– Xavier
Aug 11 '15 at 4:38

1

@Xavier never trust code from an untrusted source:-) I added a fix:-)

– David Carlisle
Aug 11 '15 at 6:51

Shouldn't or iorii be or ior ii (in all three cases)?

– clemens
Aug 11 '15 at 8:59

|
show 3 more comments

its a bug in the class, looks like a recent change in the github log, can't test here, no tex, but the package name constructed by

expandafter moderncvromannumeral

which doesn't do the right thing expandafter does nothing there, you can ignore the warning until it's fixed.

Lines 315 to 333 of moderncv.cls should be changed into

% loads a header variant

% usage: moderncvhead[<optional head option>]{<header variant number>}

newcommand*{moderncvhead}[2]{%

  begingroupedefx{endgroup

    noexpandRequirePackage[#1]{moderncvheadifcase#2or ior iior iiior ivor vfi}%

  }x 

}



% loads a body variant

% usage: moderncvbody[<optional body option>]{<body variant number>}

newcommand*{moderncvbody}[2]{%

  begingroupedefx{endgroup

    noexpandRequirePackage[#1]{moderncvbodyifcase#2or ior iior iiior ivor vfi}%

  }x 

}



% loads a footer variant

% usage: moderncvfoot{<footer variant number>}

newcommand*{moderncvfoot}[1]{%

  begingroupedefx{endgroup

    noexpandRequirePackage{moderncvfootifcase#1or ior iior iiior ivor vfi}%

  }x

}

but it's not possible to add this code in a document, because the macros are already used by the class itself.

edited Aug 11 '15 at 20:58

answered Aug 8 '15 at 20:53

David Carlisle

497k4111441891

its a bug in the class, looks like a recent change in the github log, can't test here, no tex, but the package name constructed by

expandafter moderncvromannumeral

which doesn't do the right thing expandafter does nothing there, you can ignore the warning until it's fixed.

Lines 315 to 333 of moderncv.cls should be changed into

% loads a header variant

% usage: moderncvhead[<optional head option>]{<header variant number>}

newcommand*{moderncvhead}[2]{%

  begingroupedefx{endgroup

    noexpandRequirePackage[#1]{moderncvheadifcase#2or ior iior iiior ivor vfi}%

  }x 

}



% loads a body variant

% usage: moderncvbody[<optional body option>]{<body variant number>}

newcommand*{moderncvbody}[2]{%

  begingroupedefx{endgroup

    noexpandRequirePackage[#1]{moderncvbodyifcase#2or ior iior iiior ivor vfi}%

  }x 

}



% loads a footer variant

% usage: moderncvfoot{<footer variant number>}

newcommand*{moderncvfoot}[1]{%

  begingroupedefx{endgroup

    noexpandRequirePackage{moderncvfootifcase#1or ior iior iiior ivor vfi}%

  }x

}

but it's not possible to add this code in a document, because the macros are already used by the class itself.

edited Aug 11 '15 at 20:58

answered Aug 8 '15 at 20:53

David Carlisle

497k4111441891

edited Aug 11 '15 at 20:58

answered Aug 8 '15 at 20:53

David Carlisle

497k4111441891

answered Aug 8 '15 at 20:53

David Carlisle

497k4111441891

answered Aug 8 '15 at 20:53

David Carlisle

497k4111441891

@egreg takes pity on a user with no tex on his computer:-) Thanks I just came back here to add that and saw you'd done it:-)

– David Carlisle
Aug 8 '15 at 21:35

5

I also fixed some missing %. ;-)

– egreg
Aug 8 '15 at 21:47

Thanks for the fix! Have you guys though confirmed it worked? I am still getting the nasty warnings after changing lines 315 to 333, but maybe it's somehow just me :(

– Xavier
Aug 11 '15 at 4:38

1

@Xavier never trust code from an untrusted source:-) I added a fix:-)

– David Carlisle
Aug 11 '15 at 6:51

Shouldn't or iorii be or ior ii (in all three cases)?

– clemens
Aug 11 '15 at 8:59

|
show 3 more comments

@egreg takes pity on a user with no tex on his computer:-) Thanks I just came back here to add that and saw you'd done it:-)

– David Carlisle
Aug 8 '15 at 21:35

5

I also fixed some missing %. ;-)

– egreg
Aug 8 '15 at 21:47

Thanks for the fix! Have you guys though confirmed it worked? I am still getting the nasty warnings after changing lines 315 to 333, but maybe it's somehow just me :(

– Xavier
Aug 11 '15 at 4:38

1

@Xavier never trust code from an untrusted source:-) I added a fix:-)

– David Carlisle
Aug 11 '15 at 6:51

Shouldn't or iorii be or ior ii (in all three cases)?

– clemens
Aug 11 '15 at 8:59

@egreg takes pity on a user with no tex on his computer:-) Thanks I just came back here to add that and saw you'd done it:-)

– David Carlisle
Aug 8 '15 at 21:35

I also fixed some missing %. ;-)

– egreg
Aug 8 '15 at 21:47

Thanks for the fix! Have you guys though confirmed it worked? I am still getting the nasty warnings after changing lines 315 to 333, but maybe it's somehow just me :(

– Xavier
Aug 11 '15 at 4:38

@Xavier never trust code from an untrusted source:-) I added a fix:-)

– David Carlisle
Aug 11 '15 at 6:51

Shouldn't or iorii be or ior ii (in all three cases)?

– clemens
Aug 11 '15 at 8:59

|
show 3 more comments

This bug has been fixed in the GitHub repo, but not yet (as of 2019-04-03) on CTAN: https://www.ctan.org/pkg/moderncv version:2.0.0 date:2015-07-28

answered 11 hours ago

davejagoda

1113

New contributor

add a comment |

This bug has been fixed in the GitHub repo, but not yet (as of 2019-04-03) on CTAN: https://www.ctan.org/pkg/moderncv version:2.0.0 date:2015-07-28

answered 11 hours ago

davejagoda

1113

New contributor

add a comment |

This bug has been fixed in the GitHub repo, but not yet (as of 2019-04-03) on CTAN: https://www.ctan.org/pkg/moderncv version:2.0.0 date:2015-07-28

answered 11 hours ago

davejagoda

1113

New contributor

This bug has been fixed in the GitHub repo, but not yet (as of 2019-04-03) on CTAN: https://www.ctan.org/pkg/moderncv version:2.0.0 date:2015-07-28

answered 11 hours ago

davejagoda

1113

New contributor

answered 11 hours ago

davejagoda

1113

New contributor

answered 11 hours ago

davejagoda

1113

answered 11 hours ago

davejagoda

1113

New contributor

davejagoda is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to TeX - LaTeX Stack Exchange!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Btukfyl