• overriding package with older version in new queue

    From Peymaneh Nejad@21:1/5 to All on Tue Aug 10 13:30:01 2021
    Hi,

    I have had a dependency for a package I am working on uploaded by a sponsor to new queue.

    I realised later that this package actually break the build, and that this can be solved by packaging _older_ version of the dependency package (that's also what upstream does.

    I am wondering how to fix this the right way:
    Should I or my sponsor contact ftp masters and cancel the upload, and do a new on, or is it possible to overwrite the uploaded package even tho the version number would be lower? I imagine uploading an older version might be difficult, latest when in
    reaches unstable.

    If I should contact ftp masters, should this be done via bts pseudo package or directly via mail?

    kind regards,
    peymaneh

    PS: i am not subscribed to this ml, please keep me in cc when ansering ;)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul Wise@21:1/5 to All on Wed Aug 11 02:50:01 2021
    On Tue, Aug 10, 2021 at 11:24 AM Peymaneh Nejad wrote:

    I realised later that this package actually break the build, and that this can be solved by packaging _older_ version of the dependency package (that's also what upstream does.

    The best option is to send upstream a patch to fix the build when
    using the newer version of the dependency, then package the version
    that includes the patch. Eventually upgrading the dependency package
    will be needed so the build failure will need to be fixed sooner or
    later and fixing it sooner rather than later is better. If you take
    this approach it is a good idea to make the build work with both the
    old version and the new version, so that people stuck on the old
    version for whatever reason don't have to upgrade.

    Should I or my sponsor contact ftp masters and cancel the upload, and do a new on, or is it possible to overwrite the uploaded package even tho the version number would be lower? I imagine uploading an older version might be difficult, latest when in
    reaches unstable.

    If fixing the build failure isn't feasible right now, you could
    contact the ftp-masters and ask for a reject, then upload the older
    version. There is no other way to get an older version into Debian.
    Once the package is accepted there isn't any proper way to make the
    version become older. There are two hacky/bad ways though 1) discuss
    the case on debian-devel and if you get consensus you can add an epoch
    2) you can upload 0.1.1 as 0.1.2+really0.1.1 instead to make the
    version later than 0.1.2 but contain the code from 0.1.1. Both of
    these are not good ideas though.

    If I should contact ftp masters, should this be done via bts pseudo package or directly via mail?

    Usually on the #debian-ftp IRC channel on OFTC is a better option for
    this particular type of request.

    PS: i am not subscribed to this ml, please keep me in cc when ansering ;)

    Done.

    PS: In future, when asking questions, please include specific details, including package names and excerpts of build logs etc. Advice is
    almost always better when given more information as input.

    --
    bye,
    pabs

    https://wiki.debian.org/PaulWise

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Peymaneh Nejad@21:1/5 to All on Wed Aug 11 14:10:02 2021
    Hi Paul,

    thanks for the thorough answer :)


    PS: In future, when asking questions, please include specific details, >including package names and excerpts of build logs etc. Advice is
    almost always better when given more information as input.

    ACK

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)