https://labs.parabola.nu/https://labs.parabola.nu/favicon.ico?15367742552022-03-25T22:23:42ZParabola Issue TrackerPackages - Bug #3205: [mkinitcpio]: Local package newer than in libre but older than in corehttps://labs.parabola.nu/issues/3205?journal_id=169752022-03-25T22:23:42Zbill-auger
<ul><li><strong>Status</strong> changed from <i>unconfirmed</i> to <i>confirmed</i></li></ul><p>is this causing any noticeable problem?</p> Packages - Bug #3205: [mkinitcpio]: Local package newer than in libre but older than in corehttps://labs.parabola.nu/issues/3205?journal_id=169762022-03-26T12:48:10Zdoolio
<ul></ul><p>No, unless you think it could be why I'm unable to boot into my fully encrypted system (see forum post <br /><a class="external" href="https://labs.parabola.nu/boards/5/topics/1226">https://labs.parabola.nu/boards/5/topics/1226</a>).</p> Packages - Bug #3205: [mkinitcpio]: Local package newer than in libre but older than in corehttps://labs.parabola.nu/issues/3205?journal_id=169802022-03-28T10:21:30Zdoolio
<ul></ul><p>The mkinitcpio-30-2.parabola2 version is in my pacman cache so at some point it was updated to the 30-2.0 version on my system now. However, I don't understand where this version came from since the libre repo still has the version in my pacman cache and the version in the core repository is newer still.</p>
<p>But my feeling is this is the cause of why I can't boot into my encrypted system. Can I upgrade it to that in core even though it was installed as a dependency?</p> Packages - Bug #3205: [mkinitcpio]: Local package newer than in libre but older than in corehttps://labs.parabola.nu/issues/3205?journal_id=169812022-03-28T10:55:27Zdoolio
<ul></ul><p>Downgrading to mkinitcpio-30-2.parabola2 version resolved my problem. I can now boot into my encrypted system again.</p>
<p>I still would like to understand where the 30-2.0 version came from and why this package exists in both libre and core. To exist in libre suggests the Parabola team perform some work on the package. If that is the case shouldn't it then be excluded from core?</p> Packages - Bug #3205: [mkinitcpio]: Local package newer than in libre but older than in corehttps://labs.parabola.nu/issues/3205?journal_id=183512022-12-19T11:35:37Zwael
<ul><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li><li><strong>Status</strong> changed from <i>confirmed</i> to <i>in progress</i></li></ul> Packages - Bug #3205: [mkinitcpio]: Local package newer than in libre but older than in corehttps://labs.parabola.nu/issues/3205?journal_id=183532022-12-19T11:53:34Zbill-auger
<ul><li><strong>Parent task</strong> set to <i>#3372</i></li><li><strong>Assignee</strong> set to <i>bill-auger</i></li><li><strong>Subject</strong> changed from <i>Local mkinitcpio newer than in libre but older than in core</i> to <i>[mkinitcpio]: Local package newer than in libre but older than in core</i></li></ul><p>per <a class="issue tracker-1 status-2 priority-3 priority-default closed" title="Bug: Can't boot after upgrading lvm2 from 2.03.13-1 to 2.03.14-1 (fixed)" href="https://labs.parabola.nu/issues/3121">#3121</a> - it is nothing to be concerned about - the software should be identical in both packages</p>
<p>the rationale is explained in the PKGBUILD:</p>
<pre>
# parabola changes and rationale:
# - replace 'systemd' dep with 'udev'
# - emergency patch (mkinitcpio/udev patch #3121)
# normally we keep core/mkinitcpio
# !!! REMEMBER to db-remove libre/mkinitcpio !!!
</pre>
<p>so now, is probably that time to remember</p> Packages - Bug #3205: [mkinitcpio]: Local package newer than in libre but older than in corehttps://labs.parabola.nu/issues/3205?journal_id=183542022-12-19T12:15:17Zbill-auger
<ul><li><strong>Parent task</strong> deleted (<del><i>#3372</i></del>)</li></ul> Packages - Bug #3205: [mkinitcpio]: Local package newer than in libre but older than in corehttps://labs.parabola.nu/issues/3205?journal_id=184182022-12-21T17:00:39Zbill-auger
<ul><li><strong>Status</strong> changed from <i>in progress</i> to <i>fixed</i></li></ul>