WO2022148185A1

WO2022148185A1 - Data packet updating method and apparatus, electronic device, and readable storage medium

Info

Publication number: WO2022148185A1
Application number: PCT/CN2021/134428
Authority: WO
Inventors: 董世江
Original assignee: 苏州浪潮智能科技有限公司
Priority date: 2021-01-07
Filing date: 2021-11-30
Publication date: 2022-07-14
Also published as: CN112732300A

Abstract

A data packet updating method and apparatus, an electronic device, and a computer-readable storage medium. The method comprises: acquiring and parsing a re-compiling instruction to obtain a task number (S101); determining, according to the task number, a target RPM task that has been successfully executed (S102); deleting, from a database, data packet construction information corresponding to the target RPM task (S103); and re-executing the target RPM task to obtain a target RPM data packet, and replacing an original RPM data packet with the target RPM data packet (S104). According to the method, there is no need to modify source code, a target RPM task can be initialized by deleting data packet construction information, and the target RPM task is re-executed after the initialization, so as to complete updating of an RPM data packet, thereby avoiding errors and unnecessary workload caused by modifying source code.

Description

A data package update method, apparatus, electronic device and readable storage medium

This application claims the priority of the Chinese patent application filed on January 7, 2021, with the application number of 202110018516.9 and the invention titled "A data packet update method, device, electronic device and readable storage medium", which The entire contents of this application are incorporated by reference.

technical field

The present application relates to the technical field of operating systems, and in particular, to a data packet update method, a data packet update apparatus, an electronic device, and a computer-readable storage medium.

Background technique

RPM (Redhat Package Manager) data packages are pre-compiled and packaged files on the Linux system. The compilation and generation of RPM data packages depend on source code. An RPM data package can be built by relying on one or more RPM data packages. Therefore, when an RPM data package is updated due to changes in the source code, it depends on the RPM data package. Other RPM packages also need to be rebuilt. For a successfully constructed RPM data package, its source code cannot be rebuilt without modification. Therefore, the related technology needs to modify the source code when the RPM data package is updated, and the source code corresponding to these RPM data packages does not need to be modified. The code is easy to cause errors that did not exist in the original, and also increases the unnecessary workload. Therefore, the related art has the problem that the source code must be modified to be able to update the RPM data package.

Therefore, the problem existing in the related art that the RPM data package can be updated only by modifying the source code is a technical problem to be solved by those skilled in the art.

SUMMARY OF THE INVENTION

In view of this, the purpose of this application is to provide a data packet update method, a data packet update device, an electronic device and a computer-readable storage medium, which can update the RPM data packet without revising the source code, avoiding the need for modification of the source code. errors and unnecessary work.

In order to solve the above-mentioned technical problems, the present application provides a data package update method, including:

Get and parse the recompile instruction to get the task number;

Determine the successfully executed target RPM task according to the task number;

Delete the data package construction information corresponding to the target RPM task from the database;

Re-execute the target RPM task to obtain a target RPM data packet, and replace the original RPM data packet with the target RPM data packet.

Optionally, deleting the data package construction information corresponding to the target RPM task from the database includes:

Obtain the compilation sequence number corresponding to the target RPM task;

Use the compilation sequence number to screen a plurality of construction information in the database to obtain the data packet construction information;

Delete the packet build information.

Optionally, the described acquisition of the compilation sequence number corresponding to the target RPM task includes:

Utilize the task number to obtain the task information corresponding to the target RPM task;

The task information is parsed to obtain the compilation serial number.

Optionally, the target RPM task that has been successfully executed is determined according to the task number, including:

Utilize described task number to determine initial RPM task, and obtain the initial task information corresponding to described initial RPM task;

Analyze the initial task information to obtain a build field and a status field;

If the build field is not empty and the status field is successful, the initial RPM task is determined to be the target RPM task.

Optionally, after the described utilization of the target RPM data package to replace the original RPM data package, it also includes:

If the deletion instruction corresponding to the target RPM data package is detected, the target RPM data package is deleted, and the first data package construction information corresponding to the target RPM data package is deleted from the database.

Optionally, before deleting the target RPM data package, it also includes:

A backup data package corresponding to the target RPM data package is generated, and the backup data package is stored in a backup path.

Optionally, also include:

Obtain and parse the data packet recovery instruction to obtain the target data packet information;

Judging whether there is a target backup data packet corresponding to the target data packet information under the backup path;

If the target backup data package exists in the backup path, save the target backup data package to the original path;

Insert the second data package construction information corresponding to the target backup data package into the database.

The application also provides a data package update device, including:

The acquisition module is used to acquire and parse the recompilation instruction to obtain the task number;

A task determination module for determining the successfully executed target RPM task according to the task number;

A deletion module for deleting the data packet construction information corresponding to the target RPM task from the database;

A data packet generation module is used to re-execute the target RPM task, obtain a target RPM data packet, and replace the original RPM data packet with the target RPM data packet.

The application also provides an electronic device, including a memory and a processor, wherein:

the memory for storing computer programs;

The processor is configured to execute the computer program to implement the above-mentioned data packet update method.

The present application also provides a computer-readable storage medium for storing a computer program, wherein when the computer program is executed by a processor, the above-mentioned data packet updating method is implemented.

The data package update method provided by the present application obtains and parses the recompilation instruction to obtain the task number; determines the successfully executed target RPM task according to the task number; deletes the data package construction information corresponding to the target RPM task from the database; re-executes the target RPM task, get the target RPM data package, and replace the original RPM data package with the target RPM data package.

It can be seen that the method can determine the target RPM task when updating the RPM data package, and the target RPM task is the task of generating the target RPM data package. After determining the target RPM task, delete the corresponding data package construction information in the database. The data package construction information is used to record the construction information of the target RPM data package. By deleting the data package construction information, the target RPM data package can be successfully The build record is deleted, reverting to a state where the target RPM task was not executed. By re-executing the target RPM task, a new target RPM data package can be generated and used to replace the original original RPM package. The method does not need to modify the source code, the target RPM task can be initialized by deleting the data package construction information, and the target RPM task is re-executed after initialization to complete the update of the RPM data package and avoid errors caused by modifying the source code. And unnecessary workload, solves the problem existing in the related art that the source code must be modified to be able to update the RPM data package.

In addition, the present application also provides a data package update device, an electronic device and a computer-readable storage medium, which also have the above beneficial effects.

Description of drawings

In order to illustrate the technical solutions in the embodiments of the present application or related technologies more clearly, the following briefly introduces the accompanying drawings that are used in the description of the embodiments or related technologies. Obviously, the drawings in the following description are only the For the embodiments of the application, for those of ordinary skill in the art, other drawings can also be obtained according to the provided drawings without any creative effort.

1 is a flowchart of a method for updating a data packet provided by an embodiment of the present application;

FIG. 2 is a schematic structural diagram of an apparatus for updating data packets according to an embodiment of the present application;

FIG. 3 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed ways

In order to make the purposes, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments It is only a part of the embodiments of the present application, but not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

Please refer to FIG. 1 , which is a flowchart of a method for updating a data packet provided by an embodiment of the present application. The method includes:

S101: Obtain and parse the recompilation instruction to obtain the task number.

All or part of this embodiment can be executed by a designated electronic device, and the designated electronic device can be any electronic device that can perform RPM tasks and then generate RPM data packets, for example, can be a computer with a Linux system, the Linux system is a computer with The version of the RPM build system, for example, may be a Fedora version of the Linux system, and the corresponding RPM build system is the koji system. In this case, the various steps in this embodiment can be performed through the koji CLI commands employed by the koji system.

When the constructed data package needs to be updated, the recompilation instruction can be obtained and parsed, and the task number used to specify the target task can be obtained, and the specific content of the task number is not limited. This embodiment does not limit the parsing manner of the recompilation instruction, and the specific parsing manner may be different according to the format of the recompilation instruction. This embodiment does not limit the generation method of the recompilation instruction. For example, the user can input the recompilation instruction on the front-end page (such as the kojiwebtask page), and generate the recompilation instruction according to the input content; or the user can operate on the front-end page and generate the recompilation instruction according to the specific operation compilation instructions. Further, this embodiment does not limit the acquisition method of the recompilation instruction. For example, in a feasible implementation manner, when any instruction is acquired, it is determined as the initial instruction, and the initial task number is obtained by parsing it, and the initial task number is obtained by using the initial task number. The task number determines the corresponding task, and judges whether the status of the task is successfully executed. If the status of the task is successfully executed, it is determined that the initial instruction is a recompile instruction. Or after it is detected that the task status is successfully executed, it is further judged whether the initial instruction has operation selection information, if the initial instruction has operation selection information, or if the initial instruction has operation selection information and it selects the recompile operation, then determine. The initial instruction is a recompile instruction, and the initial task number is determined as the task number. In this embodiment, the task number may be represented by task_id.

S102: Determine the successfully executed target RPM task according to the task number.

After getting the task number, use the task number to determine the target RPM task. It should be noted that, since the constructed RPM data package is to be updated in this embodiment, the corresponding target RPM must be in a successfully executed state, that is, a successfully executed state. This embodiment does not limit the specific manner of determining the target RPM, for example, the target RPM can be obtained by filtering the task list by using the task number.

Specifically, in one embodiment, in order to prevent the wrong input of the task number in the recompilation instruction, making the subsequent steps become invalid steps and causing waste of computing resources, it is possible to determine whether the status of the target RPM task is successfully executed after determining the target RPM task. state. That is, the steps of determining the successfully executed target RPM task according to the task number may include:

Step 11: Determine the initial RPM task by using the task number, and obtain initial task information corresponding to the initial RPM task.

Step 12: Parse the initial task information to obtain a build field and a status field.

Step 13: If the build field is not empty and the status field is successful, the initial RPM task is determined as the target RPM task.

Specifically, after the task number is obtained by parsing, it is used to obtain the corresponding initial task information. For example, the instruction of kojitaskinfotask_id can be used to obtain the initial task information, and the initial task information can be parsed to obtain the build field (ie, the build field) and the state field (ie, the state field). field). If the build field is empty, it means that the initial RPM task is in the free state (ie 0 state, the corresponding state field is 0), the open state (ie 1 state, the corresponding state field is 1), the assigned state (ie 4 state, corresponding to The state field is 4), cancel state (that is, state 3, the corresponding state field is 3), the task does not build an RPM packet. In this case, the initial RPM task is not the target RPM task. If the build field is not empty and the state field is 5 (that is, the 5 state), it means that the initial task is in the execution failure state, and the initial RPM task is not the target RPM task. If the build field is not empty and the state field is 2 (that is, the 2 state), it means that the initial task is in the successful execution state, and the initial RPM task is the target RPM task.

It can be understood that, the present embodiment does not limit the processing manner of the initial RPM tasks whose states are 0, 1, 3, 4, and 5. For example, no processing may be performed. Or in a feasible implementation manner, for the initial RPM tasks in states 0, 1, and 4, the state can be modified to 3 and re-executed; for the initial RPM tasks in states 3 and 5, it can be directly re-executed.

S103: Delete the data package construction information corresponding to the target RPM task from the database.

During the execution of the target RPM task, the corresponding RPM data package will be constructed, and the data package construction information corresponding to the RPM data package will be recorded in the database. In order to initialize the target RPM task, the data package construction information in the database needs to be deleted, so that no information related to the target RPM task is recorded in the database, thereby ensuring that the target RPM task can be executed again. This embodiment does not limit the specific form of the database, for example, it may be a PostgreSQL database, a relational database. The database may include multiple data tables, some of which, or all of the data tables, may have packet construction information.

Specifically, since the target RPM task is used to build an RPM data package, the RPM data package obtained by the construction has a special number, and the number may be called a compilation sequence number, which may be specifically represented by build_id. Therefore, when deleting the data package construction information, the database can be filtered by the compilation serial number, and the data package construction information can be found and deleted. Specifically, the step of deleting the data package construction information corresponding to the target RPM task from the database may include:

Step 21: Obtain the compilation sequence number corresponding to the target RPM task.

Step 22: Screen multiple construction information in the database by using the compilation sequence number to obtain data packet construction information.

Step 23: Delete the packet build information.

When the database is a PostgreSQL database, you can use the psql command to search and delete the build information in the database. In a specific implementation manner, the database may include four data tables, namely buildroot_listing data table, rpmsigs data table, rpminfo data table, and tag_listing data table. Among them, the buildroot_listing data table can record information such as the serial number of the RPM data package and the update flag bit, the rpmsigs data table is used to record the signature information of the RPM data package, and the rpminfo data table is used to record the attribute information of the RPM data package, such as the source code path, etc. , the tag_listing data table is used to record the grouping information corresponding to the RPM data package. The following psql commands can be used to search and delete the packet construction information in the database:

Deletefrombuildroot_listing where rpm_id in(select id from rpminfo where build_id=input parameter);

Deletefromrpmsigs where rpm_id in(select id from rpminfo where build_id=input parameter);

Deletefromrpminfo where id in(select id from rpminfo where build_id=input parameter);

Deletefromtag_listing where wherebuild_id=input parameter;

Among them, the input parameter is the input compilation sequence number, and "build_id=input parameter" is used to assign the compilation sequence number to the build_id field, so that the build information whose content in the build_id field is the compilation sequence number is determined as the data package construction information and deleted. .

Further, the step of obtaining the compilation sequence number corresponding to the target RPM task may include:

Step 31: Obtain task information corresponding to the target RPM task by using the task number.

Step 32: Parse the task information to obtain a compilation serial number.

Since the task number in this application can determine the target RPM task that has been successfully executed, the target RPM task that has been successfully executed will inevitably build the corresponding RPM data package, so the corresponding task information must have a compilation sequence number, and this method can be fast and accurate. to obtain the compilation serial number.

S104: Re-execute the target RPM task to obtain the target RPM data package, and replace the original RPM data package with the target RPM data package.

After the data package construction information is deleted, the target RPM task is re-executed to obtain the corresponding target RPM data package, and the original original RPM data package is replaced by the target RPM data package to complete the update of the RPM data package. It should be noted that the source code corresponding to the target RPM data package and the original RPM data package are the same, and the data package names are also the same. The difference is that the content of the RPM data package they depend on is different. Under the koji build system, you can use kojiresubmittask_id to resubmit the target RPM task, and then re-execute the target RPM task. It should be noted that, before using the target RPM data package to construct the original RPM data package, the original RPM data package can also be backed up, for example, stored in the backup path, so that the backed up original RPM data package can be used for processing when needed. rollback.

Specifically, the steps of re-executing the target RPM task to obtain the target RPM data package may include:

Step 41: Compile the target source code corresponding to the target RPM task to obtain the target RPM data package.

Step 42: Add the first data package construction information corresponding to the target RPM data package in the database.

Specifically, when the target RPM task is executed, the corresponding target source code is first determined, and the target source code is used to compile and generate the target RPM data package, and its specific content is not limited. While generating the target RPM data package, it is also necessary to add the corresponding first data package construction information in the database to ensure that the target RPM data package can be used normally.

In a specific embodiment, after replacing the original RPM data package with the target RPM data package, it can also include:

In this application, the existing RPM data package may also be deleted. For example, in this embodiment, the target RPM data package can be deleted, and the corresponding first data package construction information can be deleted at the same time, so as to completely delete all the information corresponding to the target RPM data package. It should be noted that other RPM data packages specified by the deletion instruction can also be deleted by using the above method.

Further, corresponding to the delete operation, there may also be a restore operation for restoring the deleted RPM data package. For example, before deleting the target RPM data package, a backup data package corresponding to the target RPM data package may also be generated, and the backup data package may be stored in the backup path. Multiple backup data packages can be stored in the backup path, so that the backup data packages can be used to perform data package recovery operations when needed.

Among them, the data packet recovery operation may include:

Step 51: Acquire and parse the data packet recovery instruction to obtain target data packet information.

Step 52: Determine whether there is a target backup data packet corresponding to the target data packet information in the backup path.

Step 53: If the target backup data package exists in the backup path, save the target backup data package to the original path.

Step 54: Insert the second data package construction information corresponding to the target backup data package into the database.

It should be noted that the original path is the normal storage path when the target backup data package is used as the RPM data package. When acquiring the target data package information, you can first determine whether there is a target backup data package that you want to restore. If there is a target backup data package you want to restore, you can execute saving to the original path and inserting a second data package into the database to construct information steps. Specifically, the target backup data packet can be parsed to obtain the second data packet construction information, and inserted into the database.

A packet rollback operation can be formed by using the packet delete operation and the packet recovery operation. Specifically, if the original RPM data package is backed up before the target RPM data package is used to replace the original RPM data package, when the data package rollback instruction is received, the target data package and the corresponding first data package are first deleted by the delete operation Build the information, and use the backup corresponding to the original RPM data package to perform the data package recovery operation to complete the rollback of the data package.

By applying the data package update method provided by the embodiment of the present application, when updating the RPM data package, a target RPM task can be determined, and the target RPM task is the task of generating the target RPM data package. After determining the target RPM task, delete the corresponding data package construction information in the database. The data package construction information is used to record the construction information of the target RPM data package. By deleting the data package construction information, the target RPM data package can be successfully The build record is deleted, reverting to a state where the target RPM task was not executed. By re-executing the target RPM task, a new target RPM data package can be generated and used to replace the original original RPM package. The method does not need to modify the source code, the target RPM task can be initialized by deleting the data package construction information, and the target RPM task is re-executed after initialization to complete the update of the RPM data package and avoid errors caused by modifying the source code. And unnecessary workload, solves the problem existing in the related art that the source code must be modified to be able to update the RPM data package.

The following describes the data packet updating apparatus provided by the embodiments of the present application. The data packet updating apparatus described below and the data packet updating method described above may refer to each other correspondingly.

Please refer to FIG. 2. FIG. 2 is a schematic structural diagram of a data packet updating apparatus provided by an embodiment of the present application, including:

an acquisition module 110, used for acquiring and parsing the recompilation instruction to obtain the task number;

The task determination module 120 is used for determining the successfully executed target RPM task according to the task number;

A deletion module 130 is used to delete the data package construction information corresponding to the target RPM task from the database;

The data package generation module 140 is configured to re-execute the target RPM task, obtain the target RPM data package, and replace the original RPM data package with the target RPM data package.

Optionally, delete module 130, including:

The compilation sequence number obtaining unit is used to obtain the compilation sequence number corresponding to the target RPM task;

a screening unit, used for screening a plurality of construction information in the database by using the compilation sequence number to obtain data packet construction information;

Remove unit, used to remove packet build information.

Optionally, the compilation sequence number acquisition unit includes:

The task information acquisition subunit is used to obtain the task information corresponding to the target RPM task by using the task number;

The parsing subunit is used to parse the task information to obtain the compilation sequence number.

Optionally, the task determination module 120 includes:

A task information acquisition unit, used to determine the initial RPM task by using the task number, and obtain the initial task information corresponding to the initial RPM task;

The field acquisition unit is used to parse the initial task information to obtain the construction field and the status field;

The task determination unit is used to determine the initial RPM task as the target RPM task if the build field is not empty and the status field is successful.

Optionally, also include:

The deletion module is configured to delete the target RPM data package if the deletion instruction corresponding to the target RPM data package is detected, and delete the first data package construction information corresponding to the target RPM data package from the database.

Optionally, also include:

The backup module is used to generate a backup data package corresponding to the target RPM data package, and store the backup data package in the backup path.

Optionally, also include:

The recovery instruction acquisition module is used to acquire and parse the data packet recovery instruction to obtain the target data packet information;

an existence judgment module, used for judging whether there is a target backup data packet corresponding to the target data packet information under the backup path;

The original path saving module is used to save the target backup data package to the original path if the target backup data package exists in the backup path;

The construction information insertion module is used for inserting the second data packet construction information corresponding to the target backup data packet in the database.

The electronic device provided by the embodiments of the present application will be introduced below, and the electronic device described below and the data packet update method described above may refer to each other correspondingly.

Please refer to FIG. 3 , which is a schematic structural diagram of an electronic device according to an embodiment of the present application. The electronic device 100 may include a processor 101 and a memory 102 , and may further include one or more of a multimedia component 103 , an information input/information output (I/O) interface 104 and a communication component 105 .

Wherein, the processor 101 is used to control the overall operation of the electronic device 100 to complete all or part of the steps in the above-mentioned data packet update method; the memory 102 is used to store various types of data to support the operation of the electronic device 100, these Data may include, for example, instructions for any application or method to operate on the electronic device 100, as well as application-related data. The memory 102 may be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (Electrically Erasable Programmable Read-Only Memory) Erasable Programmable Read-Only Memory, EEPROM), Erasable Programmable Read-Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (Read- One or more of Only Memory, ROM), magnetic memory, flash memory, magnetic disk or optical disk.

Multimedia components 103 may include screen and audio components. Wherein the screen can be, for example, a touch screen, and the audio component is used for outputting and/or inputting audio signals. For example, the audio component may include a microphone for receiving external audio signals. The received audio signal may be further stored in the memory 102 or transmitted through the communication component 105 . The audio assembly also includes at least one speaker for outputting audio signals. The I/O interface 104 provides an interface between the processor 101 and other interface modules, and the above-mentioned other interface modules may be a keyboard, a mouse, a button, and the like. These buttons can be virtual buttons or physical buttons. The communication component 105 is used for wired or wireless communication between the electronic device 100 and other devices. Wireless communication, such as Wi-Fi, Bluetooth, Near Field Communication (NFC for short), 2G, 3G or 4G, or one or a combination of them, so the corresponding communication component 105 may include: Wi-Fi parts, Bluetooth parts, NFC parts.

The electronic device 100 may be implemented by one or more Application Specific Integrated Circuit (ASIC for short), Digital Signal Processor (DSP for short), Digital Signal Processing Device (DSPD for short), Programmable Logic Device (PLD for short), Field Programmable Gate Array (FPGA for short), controller, microcontroller, microprocessor or other electronic components are implemented for implementing the above embodiments The given packet update method.

The computer-readable storage medium provided by the embodiments of the present application is introduced below, and the computer-readable storage medium described below and the data packet update method described above may refer to each other correspondingly.

The present application further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the above-mentioned data packet updating method are implemented.

The computer-readable storage medium may include: U disk, removable hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk, etc. that can store program codes medium.

The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments, and the same or similar parts of the various embodiments may be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant part can be referred to the description of the method.

Those skilled in the art may further realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two, in order to clearly illustrate the hardware and software In the above description, the components and steps of each example have been generally described according to their functions. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods for implementing the described functionality for each particular application, but such implementations should not be considered beyond the scope of this application.

The steps of a method or algorithm described in connection with the embodiments disclosed herein may be directly implemented in hardware, a software module executed by a processor, or a combination of the two. The software module can be placed in random access memory (RAM), internal memory, read only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other in the technical field. in any other known form of storage medium.

Finally, it should also be noted that, in this context, relationships such as first and second, etc., are used only to distinguish one entity or operation from another, and do not necessarily require or imply these entities or that there is any such actual relationship or sequence between operations. Furthermore, the terms including, comprising or any other variation are intended to cover non-exclusive inclusion such that a process, method, article or device comprising a series of elements includes not only those elements but also other elements not expressly listed, or Yes also includes elements inherent to such a process, method, article or apparatus.

The principles and implementations of the present application are described herein by using specific examples. The descriptions of the above embodiments are only used to help understand the methods and core ideas of the present application. There will be changes in the specific implementation and application scope. To sum up, the content of this specification should not be construed as a limitation on the application.

Claims

A method for updating data packets, comprising:

Get and parse the recompile instruction to get the task number;

Determine the successfully executed target RPM task according to the task number;

Delete the data package construction information corresponding to the target RPM task from the database;

Re-execute the target RPM task to obtain the target RPM data package, and replace the original RPM data package with the target RPM data package.
The data package update method according to claim 1, wherein, the data package construction information corresponding to the target RPM task is deleted from the database, comprising:

Obtain the compilation sequence number corresponding to the target RPM task;

Use the compilation sequence number to screen a plurality of construction information in the database to obtain the data packet construction information;

Delete the packet build information.
The data packet update method according to claim 2, wherein the acquisition of the compilation sequence number corresponding to the target RPM task comprises:

Utilize the task number to obtain the task information corresponding to the target RPM task;

The task information is parsed to obtain the compilation serial number.
The data packet update method according to claim 1, wherein the determining of the successfully executed target RPM task according to the task number comprises:

Utilize described task number to determine initial RPM task, and obtain the initial task information corresponding to described initial RPM task;

Analyze the initial task information to obtain a build field and a status field;

If the build field is not empty and the status field is successful, the initial RPM task is determined to be the target RPM task.
The data package update method according to claim 1, characterized in that, after replacing the original RPM data package with the target RPM data package, further comprising:

If the deletion instruction corresponding to the target RPM data package is detected, the target RPM data package is deleted, and the first data package construction information corresponding to the target RPM data package is deleted from the database.
The data package update method according to claim 5, characterized in that, before deleting the target RPM data package, further comprising:

A backup data package corresponding to the target RPM data package is generated, and the backup data package is stored in a backup path.
The data packet update method according to claim 6, further comprising:

Obtain and parse the data packet recovery instruction to obtain the target data packet information;

Judging whether there is a target backup data packet corresponding to the target data packet information under the backup path;

If the target backup data package exists in the backup path, save the target backup data package to the original path;

Insert the second data package construction information corresponding to the target backup data package into the database.
A device for updating data packets, comprising:

The acquisition module is used to acquire and parse the recompilation instruction to obtain the task number;

A task determination module for determining the successfully executed target RPM task according to the task number;

A deletion module for deleting the data packet construction information corresponding to the target RPM task from the database;

A data packet generation module is used to re-execute the target RPM task, obtain a target RPM data packet, and replace the original RPM data packet with the target RPM data packet.
An electronic device, comprising a memory and a processor, wherein:

the memory for storing computer programs;

The processor is configured to execute the computer program to implement the data packet update method according to any one of claims 1 to 7.
A computer-readable storage medium, characterized in that it is used for storing a computer program, wherein when the computer program is executed by a processor, the data packet updating method according to any one of claims 1 to 7 is implemented.