CN112732300A - Data packet updating method and device, electronic equipment and readable storage medium - Google Patents
Data packet updating method and device, electronic equipment and readable storage medium Download PDFInfo
- Publication number
- CN112732300A CN112732300A CN202110018516.9A CN202110018516A CN112732300A CN 112732300 A CN112732300 A CN 112732300A CN 202110018516 A CN202110018516 A CN 202110018516A CN 112732300 A CN112732300 A CN 112732300A
- Authority
- CN
- China
- Prior art keywords
- data packet
- task
- rpm
- target
- target rpm
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
- 238000000034 method Methods 0.000 title claims abstract description 49
- 238000010276 construction Methods 0.000 claims abstract description 62
- 238000004590 computer program Methods 0.000 claims description 10
- 238000011084 recovery Methods 0.000 claims description 8
- 238000012216 screening Methods 0.000 claims description 5
- 238000012986 modification Methods 0.000 abstract 1
- 230000004048 modification Effects 0.000 abstract 1
- 238000004891 communication Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 230000005236 sound signal Effects 0.000 description 4
- 238000004458 analytical method Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000004936 stimulating effect Effects 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
- G06F8/42—Syntactic analysis
- G06F8/427—Parsing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Abstract
The application discloses a data packet updating method, a data packet updating device, electronic equipment and a computer readable storage medium, wherein the method comprises the following steps: acquiring and analyzing a recompilation instruction to obtain a task number; determining a target RPM task which is successfully executed according to the task number; deleting data packet construction information corresponding to the target RPM task from the database; re-executing the target RPM task to obtain a target RPM data packet, and replacing the original RPM data packet with the target RPM data packet; according to the method, the source code does not need to be modified, the target RPM task can be initialized by deleting the data packet construction information, the target RPM task is executed again after initialization, the RPM data packet is updated, and errors and unnecessary workload caused by modification of the source code are avoided.
Description
Technical Field
The present disclosure relates to the field of operating systems, and in particular, to a data packet updating method, a data packet updating apparatus, an electronic device, and a computer-readable storage medium.
Background
The RPM (Redhat Package manager) data packet is a file that is compiled and packaged in advance on the linux system. The compiled generation of the RPM data packets depends on the source codes, one RPM data packet can be built depending on one or more other RPM data packets, and therefore when one RPM data packet is updated due to the change of the source codes, other RPM data packets depending on the RPM data packet also need to be rebuilt. For the RPM data packet which is successfully constructed, the source code of the RPM data packet cannot be reconstructed without being modified, so that the source code needs to be modified in the related art when the RPM data packet is updated, the source code corresponding to the RPM data packet does not need to be modified, the source code is modified, which easily causes no error originally, and unnecessary workload is increased. The related art has a problem in that the source code must be modified to be able to update the RPM data packet.
Therefore, the problem of the related art that the source code must be modified to update the RPM data packet is a technical problem to be solved by those skilled in the art.
Disclosure of Invention
In view of the above, an object of the present invention is to provide a packet updating method, a packet updating apparatus, an electronic device and a computer-readable storage medium, which can update an RPM packet without modifying a source code, thereby avoiding errors and unnecessary workload caused by modifying the source code.
In order to solve the above technical problem, the present application provides a data packet updating method, including:
acquiring and analyzing a recompilation instruction to obtain a task number;
determining a target RPM task which is successfully executed according to the task number;
deleting data packet construction information corresponding to the target RPM task from a database;
and re-executing the target RPM task to obtain a target RPM data packet, and replacing the original RPM data packet with the target RPM data packet.
Optionally, the deleting, from the database, the data packet construction information corresponding to the target RPM task includes:
acquiring a compiling serial number corresponding to the target RPM task;
screening a plurality of construction information in the database by using the compiling sequence number to obtain the data packet construction information;
and deleting the data packet construction information.
Optionally, the obtaining of the compiling sequence number corresponding to the target RPM task includes:
acquiring task information corresponding to the target RPM task by using the task number;
and analyzing the task information to obtain the compiling sequence number.
Optionally, the determining, according to the task number, a target RPM task that has been successfully executed includes:
determining an initial RPM task by using the task number, and acquiring initial task information corresponding to the initial RPM task;
analyzing the initial task information to obtain a construction field and a state field;
if the build field is not empty and the status field is successful, determining the initial RPM task as the target RPM task.
Optionally, after replacing the original RPM data packet with the target RPM data packet, further comprising:
and if a deleting instruction corresponding to the target RPM data packet is detected, deleting the target RPM data packet, and deleting first data packet construction information corresponding to the target RPM data packet from the database.
Optionally, before deleting the target RPM data packet, further comprising:
and generating a backup data packet corresponding to the target RPM data packet, and storing the backup data packet in a backup path.
Optionally, the method further comprises:
acquiring and analyzing a data packet recovery instruction to obtain target data packet information;
judging whether a target backup data packet corresponding to the target data packet information exists in the backup path or not;
if the target backup data packet exists, storing the target backup data packet to an original path;
and inserting second data packet construction information corresponding to the target backup data packet into the database.
The present application further provides a data packet updating apparatus, including:
the obtaining module is used for obtaining and analyzing the recompilation instruction to obtain a task number;
the task determining module is used for determining a target RPM task which is successfully executed according to the task number;
the deleting module is used for deleting the data packet construction information corresponding to the target RPM task from a database;
and the data packet generating module is used for re-executing the target RPM task to obtain a target RPM data packet and replacing the original RPM data packet with the target RPM data packet.
The present application further provides an electronic device comprising a memory and a processor, wherein:
the memory is used for storing a computer program;
the processor is configured to execute the computer program to implement the above-mentioned packet updating method.
The present application also provides a computer-readable storage medium for storing a computer program, wherein the computer program, when executed by a processor, implements the above-mentioned packet updating method.
According to the data packet updating method, a recompilation instruction is obtained and analyzed, and a task number is obtained; determining a target RPM task which is successfully executed according to the task number; deleting data packet construction information corresponding to the target RPM task from the database; and re-executing the target RPM task to obtain a target RPM data packet, and replacing the original RPM data packet with the target RPM data packet.
Therefore, when the RPM data packet is updated, the target RPM task can be determined, and the target RPM task is the task for generating the target RPM data packet. After the target RPM task is determined, deleting corresponding data packet construction information in the database, wherein the data packet construction information is used for recording construction information of the target RPM data packet, and deleting successfully constructed records of the target RPM data packet by deleting the data packet construction information to restore the state that the target RPM task is not executed. And by re-executing the target RPM task, a new target RPM data packet can be generated and used for replacing the original RPM data packet. According to the method, the source code does not need to be modified, the target RPM task can be initialized by deleting the data packet construction information, the target RPM task is re-executed after initialization, the updating of the RPM data packet is completed, errors and unnecessary workload caused by modifying the source code are avoided, and the problem that the RPM data packet can be updated only by modifying the source code in the related technology is solved.
In addition, the application also provides a data packet updating device, electronic equipment and a computer readable storage medium, and the beneficial effects are also achieved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments or related technologies of the present application, the drawings needed to be used in the description of the embodiments or related technologies are briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of a data packet updating method according to an embodiment of the present application;
fig. 2 is a schematic structural diagram of a packet update apparatus according to an embodiment of the present disclosure;
fig. 3 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Referring to fig. 1, fig. 1 is a flowchart illustrating a data packet updating method according to an embodiment of the present disclosure. The method comprises the following steps:
s101: and acquiring and analyzing the recompilation instruction to obtain a task number.
All or part of the present embodiment may be executed by a designated electronic device, where the designated electronic device may be any electronic device that can execute an RPM task and generate an RPM data packet, for example, a computer of a Linux system, where the Linux system is a version with an RPM building system, for example, a Fedora version of the Linux system, and a corresponding RPM building system is a koji system. In this case, the respective steps in the present embodiment may be performed by a koji CLI command employed by a koji system.
When the constructed data packet needs to be updated, the recompilation instruction can be acquired and analyzed to obtain a task number for specifying the target task, and the specific content of the task number is not limited. The embodiment does not limit the parsing manner of the recompiled instruction, and the specific parsing manner may be different according to the format of the recompiled instruction. The embodiment does not limit the generation manner of the recompilation instruction, and for example, the recompilation instruction may be generated according to the input content by inputting the recompilation instruction in a front-end page (for example, a kojiwebtask page) by a user; or the user operates on the front page, and a recompilation instruction is generated according to specific operation. Further, this embodiment does not limit the manner of obtaining the recompilation instruction, for example, in a feasible implementation manner, when any instruction is obtained, it is determined as an initial instruction, and an initial task number is obtained through analysis, and a corresponding task is determined by using the initial task number, and whether the state of the task is successfully executed is determined. If yes, the initial instruction is determined to be a recompile instruction. Or after the task state is detected to be successfully executed, further judging whether the initial instruction has operation selection information, if so, or if the initial instruction has the operation selection information and selects a recompilation operation, determining that the initial instruction is a recompilation instruction, and determining that the initial task number is a task number. In the present embodiment, the task number may be represented by task _ id.
S102: and determining the target RPM task which is successfully executed according to the task number.
And after the task number is obtained, determining a target RPM task by using the task number. It should be noted that, in the present embodiment, the constructed RPM data packet is intended to be updated, so that the corresponding target RPM is necessarily in a successfully executed state, that is, in a successfully executed state. The embodiment does not limit the specific way of determining the target RPM, and for example, the task list may be filtered by using the task number to obtain the target RPM.
Specifically, in one embodiment, in order to prevent the task number in the recompile instruction from being input incorrectly, so that the subsequent step is called as an invalid step, which results in the waste of computing resources, it may be determined whether the state of the target RPM task is a successfully executed state after the target RPM task is determined. That is, the step of determining the target RPM task that has been successfully executed according to the task number may include:
step 11: and determining an initial RPM task by using the task number, and acquiring initial task information corresponding to the initial RPM task.
Step 12: and analyzing the initial task information to obtain a construction field and a state field.
Step 13: 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.
Specifically, after the task number is obtained through analysis, the corresponding initial task information is obtained through the task number, for example, the initial task information may be obtained through a kojitask fotask _ id instruction, and the initial task information is analyzed to obtain a build field (i.e., a build field) and a state field (i.e., a state field). If the built field is empty, it indicates that the initial RPM task is in a free state (i.e., 0 state, and the corresponding state field is 0), an open state (i.e., 1 state, and the corresponding state field is 1), an asserted state (i.e., 4 state, and the corresponding state field is 4), and a cancel state (i.e., 3 state, and the corresponding state field is 3), and the task does not construct 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 (i.e. 5 state), i.e. failure, it indicates that the initial task is in an execution failure state, and the initial RPM task is not the target RPM task. If the built field is not empty and the state field is 2 (i.e. 2 state), i.e. success, it indicates that the initial task is in a successful execution state, and the initial RPM task is the target RPM task.
It is understood that the present embodiment does not limit the processing manner of the initial RPM task with the states 0, 1, 3, 4, and 5, and for example, may not perform any processing. Or in a possible embodiment, for the initial RPM task in the 0, 1, 4 state, its state may be modified to 3 and re-executed; for the initial RPM task in the 3, 5 state, it can be directly re-executed.
S103: and deleting the data packet construction information corresponding to the target RPM task from the database.
In the execution process of the target RPM task, a corresponding RPM data packet is constructed, and meanwhile, data packet construction information corresponding to the RPM data packet is recorded in a database. In order to initialize the target RPM task, the data packet construction information in the database needs to be deleted, so that no information related to the target RPM task is recorded in the database, and the target RPM task can be executed again. The present embodiment does not limit the specific form of the database, and may be, for example, a PostgreSQL database, a relational database. The database may include a plurality of data tables, wherein some or all of the data tables may have packet construction information.
Specifically, since the target RPM task is used to construct an RPM data packet, the constructed RPM data packet has a special number, which may be referred to as a compilation sequence number, and may be specifically denoted by build _ id. Therefore, when the data packet construction information is deleted, the database can be screened by using the compiling serial number, and the data packet construction information can be searched and deleted. Specifically, the step of deleting the data packet construction information corresponding to the target RPM task from the database may include:
step 21: and acquiring a compiling serial number corresponding to the target RPM task.
Step 22: and screening a plurality of construction information in the database by using the compiling sequence number to obtain the data packet construction information.
Step 23: and deleting the data packet construction information.
When the database is a PostgreSQL database, the psql command can be used to search and delete the constructed information in the database. In a specific embodiment, the database may include four data tables, which are respectively a build _ stability data table, an rpmsigs data table, an rpminfo data table, and a tag _ stability data table. The build _ stability data table may record information such as a sequence number and an update flag bit of an RPM data packet, the rpmsigs data table is used to record signature information of the RPM data packet, the rpminfo data table is used to record attribute information of the RPM data packet, such as a source code path, and the tag _ stability data table is used to record packet information corresponding to the RPM data packet. The packet building information in the database can be searched and deleted by the following psql command:
deletefrom build _ stability ground rpm _ id in (select id from rpminfo ground build _ id ═ input parameter);
deletefrmrpmsisis where rpm _ id in (select id from rpminfo where built _ id is an input parameter);
deletefrom rpminfo where id in (select id from rpminfo where built _ id ═ input parameter);
deletefrogmag _ stimulating where wherewield _ id is an input parameter;
the input parameter is the input compiling sequence number, and the "build _ id" is used for assigning the compiling sequence number to the build _ id field, so that the building information of which the content of the build _ id field is the compiling sequence number is determined as the data packet building information and is deleted.
Further, the step of acquiring the compiling sequence number corresponding to the target RPM task may include:
step 31: and acquiring task information corresponding to the target RPM task by using the task number.
Step 32: and analyzing the task information to obtain a compiling serial number.
Since the task number in the present application can determine the target RPM task that has been successfully executed, and the target RPM task that has been successfully executed necessarily constructs the corresponding RPM data packet, the compiling serial number is necessarily present in the corresponding task information, and the compiling serial number can be quickly and accurately obtained by this method.
S104: and re-executing the target RPM task to obtain a target RPM data packet, and replacing the original RPM data packet with the target RPM data packet.
And after the data packet construction information is deleted, re-executing the target RPM task to obtain a corresponding target RPM data packet, and replacing the original RPM data packet by using the target RPM data packet to complete the updating of the RPM data packet. It should be noted that the source codes corresponding to the target RPM data packet and the original RPM data packet are the same, and the names of the data packets are also the same, which is different from the content of the RPM data packet depended on the target RPM data packet and the original RPM data packet. Under the koji construction system, the target RPM task can be resubmitted by using the kojireuubmittask _ id, and then the target RPM task is re-executed. It should be noted that before the original RPM data packet is utilized, the original RPM data packet may also be backed up, for example, stored in the backup path, so as to be rolled back by utilizing the backed up original RPM data packet when needed.
Specifically, the step of re-executing the target RPM task to obtain the target RPM data packet may include:
step 41: and compiling the target source code corresponding to the target RPM task to obtain a target RPM data packet.
Step 42: and adding first data packet construction information corresponding to the target RPM data packet in the database.
Specifically, when the target RPM task is executed, the corresponding target source code is determined first, and the target source code is used for compiling and generating the target RPM data packet, and the specific content is not limited. When the target RPM data packet is generated, corresponding first data packet construction information needs to be added in the database, and the target RPM data packet can be normally used.
In a specific embodiment, after replacing the original RPM data packet with the target RPM data packet, the method may further include:
and if a deleting instruction corresponding to the target RPM data packet is detected, deleting the target RPM data packet, and deleting first data packet construction information corresponding to the target RPM data packet from the database.
In the application, the existing RPM data packet can be deleted. For example, in this embodiment, the target RPM data packet may be deleted, and the corresponding first data packet construction information is deleted at the same time, so that all information corresponding to the target RPM data packet is completely deleted. It should be noted that other RPM packets specified by the delete command may also be deleted by the above method.
Further, corresponding to the delete operation, there may also be a restore operation for restoring the deleted RPM data packet. For example, before deleting the target RPM data packet, a backup data packet corresponding to the target RPM data packet may be generated and stored in the backup path. A plurality of backup data packets may be stored under the backup path so as to perform a data packet recovery operation using the backup data packets when necessary.
The packet recovery operation may include:
step 51: and acquiring and analyzing the data packet recovery command to obtain target data packet information.
Step 52: and judging whether a target backup data packet corresponding to the target data packet information exists in the backup path.
Step 53: and if the target backup data packet exists, storing the target backup data packet to the original path.
Step 54: and inserting second data packet construction information corresponding to the target backup data packet into the database.
It should be noted that the original path is a normal storage path when the target backup data packet is used as an RPM data packet. When the target data packet information is acquired, whether a target backup data packet which is required to be restored exists or not can be judged, and if the target backup data packet exists, the steps of saving the target backup data packet to the original path and inserting second data packet construction information into a database can be executed. Specifically, the target backup data package may be analyzed to obtain second data package construction information, and the second data package construction information is inserted into the database.
Packet rollback operations may be configured using packet delete operations and packet restore operations. Specifically, if the original RPM data packet is backed up before the original RPM data packet is replaced by the target RPM data packet, when a data packet rollback instruction is received, the target RPM data packet and corresponding first data packet construction information are deleted by a deletion operation, and a data packet recovery operation is performed by using the backup corresponding to the original RPM data packet, so that rollback of the data packet is completed.
By applying the data packet updating method provided by the embodiment of the application, when the RPM data packet is updated, a target RPM task can be determined, and the target RPM task is a task for generating the target RPM data packet. After the target RPM task is determined, deleting corresponding data packet construction information in the database, wherein the data packet construction information is used for recording construction information of the target RPM data packet, and deleting successfully constructed records of the target RPM data packet by deleting the data packet construction information to restore the state that the target RPM task is not executed. And by re-executing the target RPM task, a new target RPM data packet can be generated and used for replacing the original RPM data packet. According to the method, the source code does not need to be modified, the target RPM task can be initialized by deleting the data packet construction information, the target RPM task is re-executed after initialization, the updating of the RPM data packet is completed, errors and unnecessary workload caused by modifying the source code are avoided, and the problem that the RPM data packet can be updated only by modifying the source code in the related technology is solved.
In the following, the packet update apparatus provided in the embodiment of the present application is introduced, and the packet update apparatus described below and the packet update method described above may be referred to correspondingly.
Referring to fig. 2, fig. 2 is a schematic structural diagram of a packet update apparatus according to an embodiment of the present application, including:
an obtaining module 110, configured to obtain and analyze a recompilation instruction to obtain a task number;
a task determining module 120, configured to determine, according to the task number, a target RPM task that has been successfully executed;
a deleting module 130, configured to delete the data packet construction information corresponding to the target RPM task from the database;
and a data packet generation module 140, configured 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.
Optionally, the deleting module 130 includes:
the compiling serial number acquiring unit is used for acquiring a compiling serial number corresponding to the target RPM task;
the screening unit is used for screening a plurality of construction information in the database by using the compiling serial number to obtain data packet construction information;
and the deleting unit is used for deleting the data packet construction information.
Optionally, the compilation sequence number obtaining unit includes:
the task information acquisition subunit is used for acquiring task information corresponding to the target RPM task by using the task number;
and the analysis subunit is used for analyzing the task information to obtain a compiling serial number.
Optionally, the task determining module 120 includes:
the task information acquisition unit is used for determining an initial RPM task by using the task number and acquiring initial task information corresponding to the initial RPM task;
the field acquisition unit is used for analyzing the initial task information to obtain a construction field and a state field;
and the task determination unit is used for determining the initial RPM task as the target RPM task if the construction field is not empty and the status field is successful.
Optionally, the method further comprises:
and the deleting module is used for deleting the target RPM data packet and deleting the first data packet construction information corresponding to the target RPM data packet from the database if a deleting instruction corresponding to the target RPM data packet is detected.
Optionally, the method further comprises:
and the backup module is used for generating a backup data packet corresponding to the target RPM data packet and storing the backup data packet in a backup path.
Optionally, the method further comprises:
the recovery instruction acquisition module is used for acquiring and analyzing a data packet recovery instruction to obtain target data packet information;
the existence judging module is used for judging whether a target backup data packet corresponding to the target data packet information exists in the backup path;
the original path storage module is used for storing the target backup data packet to the original path if the target backup data packet exists;
and the construction information inserting module is used for inserting second data packet construction information corresponding to the target backup data packet into the database.
In the following, the electronic device provided by the embodiment of the present application is introduced, and the electronic device described below and the data packet updating method described above may be referred to correspondingly.
Referring to fig. 3, fig. 3 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure. Wherein 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.
The processor 101 is configured to control the overall operation of the electronic device 100 to complete all or part of the steps in the above-mentioned packet updating method; the memory 102 is used to store various types of data to support operation at the electronic device 100, such data may include, for example, instructions for any application or method operating on the electronic device 100, as well as application-related data. The Memory 102 may be implemented by any type or combination of volatile and non-volatile Memory devices, such as one or more of Static Random Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read-Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic Memory, flash Memory, magnetic or optical disk.
The multimedia component 103 may include a screen and an audio component. Wherein the screen may 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 further be 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, such as a keyboard, mouse, buttons, etc. These buttons may 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), 2G, 3G, or 4G, or a combination of one or more of them, so that the corresponding Communication component 105 may include: Wi-Fi part, Bluetooth part, NFC part.
The electronic Device 100 may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic components, and is configured to perform the packet updating method according to the above embodiments.
The following describes a computer-readable storage medium provided in an embodiment of the present application, and the computer-readable storage medium described below and the data packet updating method described above may be referred to correspondingly.
The present application further provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the steps of the above-mentioned packet updating method.
The computer-readable storage medium may include: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The embodiments are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same or similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
Those of skill would further appreciate that the various illustrative components and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
Finally, it should also be noted that, herein, relationships such as first and second, etc., are intended only to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms include, or any other variation is intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
The principle and the implementation of the present application are explained herein by applying specific examples, and the above description of the embodiments is only used to help understand the method and the core idea of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.
Claims (10)
1. A method for updating a packet, comprising:
acquiring and analyzing a recompilation instruction to obtain a task number;
determining a target RPM task which is successfully executed according to the task number;
deleting data packet construction information corresponding to the target RPM task from a database;
and re-executing the target RPM task to obtain a target RPM data packet, and replacing the original RPM data packet with the target RPM data packet.
2. The method according to claim 1, wherein the deleting the packet construction information corresponding to the target RPM task from the database includes:
acquiring a compiling serial number corresponding to the target RPM task;
screening a plurality of construction information in the database by using the compiling sequence number to obtain the data packet construction information;
and deleting the data packet construction information.
3. The method according to claim 2, wherein the obtaining of the compilation sequence number corresponding to the target RPM task comprises:
acquiring task information corresponding to the target RPM task by using the task number;
and analyzing the task information to obtain the compiling sequence number.
4. The method for updating data packets according to claim 1, wherein the determining the target RPM task that has been successfully executed according to the task number comprises:
determining an initial RPM task by using the task number, and acquiring initial task information corresponding to the initial RPM task;
analyzing the initial task information to obtain a construction field and a state field;
if the build field is not empty and the status field is successful, determining the initial RPM task as the target RPM task.
5. The packet update method of claim 1, wherein after said replacing an original RPM packet with said target RPM packet, further comprising:
and if a deleting instruction corresponding to the target RPM data packet is detected, deleting the target RPM data packet, and deleting first data packet construction information corresponding to the target RPM data packet from the database.
6. The packet update method of claim 5, further comprising, prior to deleting the target RPM packet:
and generating a backup data packet corresponding to the target RPM data packet, and storing the backup data packet in a backup path.
7. The packet update method according to claim 6, further comprising:
acquiring and analyzing a data packet recovery instruction to obtain target data packet information;
judging whether a target backup data packet corresponding to the target data packet information exists in the backup path or not;
if the target backup data packet exists, storing the target backup data packet to an original path;
and inserting second data packet construction information corresponding to the target backup data packet into the database.
8. A packet update apparatus, comprising:
the obtaining module is used for obtaining and analyzing the recompilation instruction to obtain a task number;
the task determining module is used for determining a target RPM task which is successfully executed according to the task number;
the deleting module is used for deleting the data packet construction information corresponding to the target RPM task from a database;
and the data packet generating module is used for re-executing the target RPM task to obtain a target RPM data packet and replacing the original RPM data packet with the target RPM data packet.
9. An electronic device comprising a memory and a processor, wherein:
the memory is used for storing a computer program;
the processor is configured to execute the computer program to implement the packet update method according to any one of claims 1 to 7.
10. A computer-readable storage medium for storing a computer program, wherein the computer program, when executed by a processor, implements the packet update method according to any one of claims 1 to 7.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110018516.9A CN112732300A (en) | 2021-01-07 | 2021-01-07 | Data packet updating method and device, electronic equipment and readable storage medium |
| PCT/CN2021/134428 WO2022148185A1 (en) | 2021-01-07 | 2021-11-30 | Data packet updating method and apparatus, electronic device, and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110018516.9A CN112732300A (en) | 2021-01-07 | 2021-01-07 | Data packet updating method and device, electronic equipment and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112732300A true CN112732300A (en) | 2021-04-30 |
Family
ID=75590986
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110018516.9A Withdrawn CN112732300A (en) | 2021-01-07 | 2021-01-07 | Data packet updating method and device, electronic equipment and readable storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN112732300A (en) |
| WO (1) | WO2022148185A1 (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113721918A (en) * | 2021-08-06 | 2021-11-30 | 苏州浪潮智能科技有限公司 | Method and device for compiling and software source manufacturing based on koji |
| WO2022148185A1 (en) * | 2021-01-07 | 2022-07-14 | 苏州浪潮智能科技有限公司 | Data packet updating method and apparatus, electronic device, and readable storage medium |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116909619A (en) * | 2023-09-07 | 2023-10-20 | 北京四象爱数科技有限公司 | Satellite software on-orbit reconstruction method, device and medium |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105446759A (en) * | 2014-08-28 | 2016-03-30 | 阿里巴巴集团控股有限公司 | Rpm package updating method and equipment |
| US10083025B2 (en) * | 2015-11-20 | 2018-09-25 | Google Llc | Dynamic update of an application in compilation and deployment with warm-swapping |
| CN107820603A (en) * | 2016-12-30 | 2018-03-20 | 深圳配天智能技术研究院有限公司 | A kind of firmware update and controller |
| CN110990020A (en) * | 2019-11-24 | 2020-04-10 | 苏州浪潮智能科技有限公司 | Software compiling method and device, electronic equipment and storage medium |
| CN112732300A (en) * | 2021-01-07 | 2021-04-30 | 苏州浪潮智能科技有限公司 | Data packet updating method and device, electronic equipment and readable storage medium |
-
2021
- 2021-01-07 CN CN202110018516.9A patent/CN112732300A/en not_active Withdrawn
- 2021-11-30 WO PCT/CN2021/134428 patent/WO2022148185A1/en active Application Filing
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022148185A1 (en) * | 2021-01-07 | 2022-07-14 | 苏州浪潮智能科技有限公司 | Data packet updating method and apparatus, electronic device, and readable storage medium |
| CN113721918A (en) * | 2021-08-06 | 2021-11-30 | 苏州浪潮智能科技有限公司 | Method and device for compiling and software source manufacturing based on koji |
| CN113721918B (en) * | 2021-08-06 | 2023-08-04 | 苏州浪潮智能科技有限公司 | Method and device for compiling and making software source based on koji |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2022148185A1 (en) | 2022-07-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112732300A (en) | Data packet updating method and device, electronic equipment and readable storage medium | |
| US10353807B2 (en) | Application development management | |
| CN102934114B (en) | For the checkpoint of file system | |
| US9336023B2 (en) | Visual generation of mobile applications based on data models | |
| US9430228B2 (en) | Verification of backward compatibility of software components | |
| KR20060049879A (en) | Generating an optimized restore plan | |
| US8650532B2 (en) | Change notification and information update based on uncompiled software development project | |
| JPH08512152A (en) | Incremental generation system | |
| JP6119535B2 (en) | Trace method, processing program, and information processing apparatus | |
| US20170371631A1 (en) | Globalization template manager for automated globalization enablement on development operations | |
| CN112379940B (en) | Executable file processing method and device, electronic equipment and storage medium | |
| US20170371687A1 (en) | Automated globalization enablement on development operations | |
| US10678572B2 (en) | Framework for automated globalization enablement on development operations | |
| US10540163B2 (en) | System and method for automatic deployment of applications in an integrated development environment | |
| CN112416379A (en) | Application program installation method and device, computing equipment and readable storage medium | |
| CN108399068B (en) | Method for function program persistence, electronic device and storage medium | |
| US20130111344A1 (en) | Help creation support apparatus, help creation method, and storage medium storing help creation program | |
| CN109828781B (en) | Source code version positioning method, device, medium and equipment for problem troubleshooting | |
| KR102644170B1 (en) | Method for assisting select of screen components and collect of coordinate information | |
| JPWO2007097014A1 (en) | Information system operation check method, operation check program, recording medium, and operation check system | |
| CN113821204B (en) | Component generation method and device, electronic equipment and readable storage medium | |
| US11921688B2 (en) | Environment construction support device and environment construction support method | |
| US9703532B1 (en) | Dynamically updating class instances based on class definition changes | |
| JP6818568B2 (en) | Communication device, communication specification difference extraction method and communication specification difference extraction program | |
| CN115951870A (en) | Mirror image file compiling method, system, equipment and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20210430 |
|
| WW01 | Invention patent application withdrawn after publication |